Patent ID: 12232155

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This 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 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 other aspect of the disclosure. For example, an apparatus may be implemented or a method may 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 other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

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

It should be noted that while aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio 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).

FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (NR) network and/or an LTE network, among other examples. The wireless network100may include a number of base stations110(shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and may 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), or the like. Each BS may 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 this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown inFIG.1, a BS110amay be a macro BS for a macro cell102a, a BS110bmay be a pico BS for a pico cell102b, and a BS110cmay be a femto BS for a femto cell102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein.

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

Wireless network100may 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 may also be a UE that can relay transmissions for other UEs. In the example shown inFIG.1, a relay BS110dmay communicate with macro BS110aand a UE120din order to facilitate communication between BS110aand UE120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.

Wireless network100may 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 may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller130may couple to a set of BSs and may provide coordination and control for these BSs. Network controller130may communicate with the BSs via a backhaul. The BSs may also communicate with one another, directly or indirectly, via a wireless or wireline backhaul.

UEs120(e.g.,120a,120b,120c) may be dispersed throughout wireless network100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, or the like. A UE may 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, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs may 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 may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE). UE120may be included inside a housing that houses components of UE120, such as processor components and/or memory components. In some aspects, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, or the like. A frequency may also be referred to as a carrier, a frequency channel, or the like. Each frequency may 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 may be deployed.

In some aspects, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol or a vehicle-to-infrastructure (V2I) protocol), and/or a mesh network. In this case, the UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station110.

Devices of wireless network100may communicate using the electromagnetic spectrum, which may be subdivided based on frequency or wavelength into various classes, bands, channels, or the like. For example, devices of wireless network100may communicate using an operating band having a first frequency range (FR1), which may span from 410 MHz to 7.125 GHz, and/or may communicate using an operating band having a second frequency range (FR2), which may 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, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies less than 6 GHz, frequencies within FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and techniques described herein are applicable to those modified frequency ranges.

As indicated above,FIG.1is provided as an example. Other examples may differ from what is described with regard toFIG.1.

FIG.2is a diagram illustrating an example200of abase station110in communication with a UE120in a wireless network100, in accordance with the present disclosure. Base station110may be equipped with T antennas234athrough234t, and UE120may be equipped with R antennas252athrough252r, where in general T≥1 and R≥1.

At base station110, a transmit processor220may receive data from a data source212for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the 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 processor220may also process system information (e.g., for 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 processor220may 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) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs)232athrough232t. Each modulator232may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator232may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators232athrough232tmay be transmitted via T antennas234athrough234t, respectively.

At UE120, antennas252athrough252rmay receive the downlink signals from base station110and/or other base stations and may provide received signals to demodulators (DEMODs)254athrough254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector256may obtain received symbols from all R demodulators254athrough254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE120to a data sink260, and provide decoded control information and system information to a controller/processor280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a channel quality indicator (CQI) parameter, among other examples. In some aspects, one or more components of UE120may be included in a housing284.

Network controller130may include communication unit294, controller/processor290, and memory292. Network controller130may include, for example, one or more devices in a core network. Network controller130may communicate with base station110via communication unit294.

Antennas (e.g., antennas234athrough234tand/or antennas252athrough252r) may include, or may be included within, one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include a set of coplanar antenna elements and/or a set of non-coplanar antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components ofFIG.2.

On the uplink, at UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from controller/processor280. Transmit processor264may also generate reference symbols for one or more reference signals. The symbols from transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by modulators254athrough254r(e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station110. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD254) of the UE120may be included in a modem of the UE120. In some aspects, the UE120includes a transceiver. The transceiver may include any combination of antenna(s)252, modulators and/or demodulators254, MIMO detector256, receive processor258, transmit processor264, and/or TX MIMO processor266. The transceiver may be used by a processor (e.g., controller/processor280) and memory282to perform aspects of any of the methods described herein (for example, as described with reference toFIGS.5-7).

At base station110, the uplink signals from UE120and other UEs may be received by antennas234, processed by demodulators232, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by UE120. Receive processor238may provide the decoded data to a data sink239and the decoded control information to controller/processor240. Base station110may include communication unit244and communicate to network controller130via communication unit244. Base station110may include a scheduler246to schedule UEs120for downlink and/or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD232) of the base station110may be included in a modem of the base station110. In some aspects, the base station110includes a transceiver. The transceiver may include any combination of antenna(s)234, modulators and/or demodulators232, MIMO detector236, receive processor238, transmit processor220, and/or TX MIMO processor230. The transceiver may be used by a processor (e.g., controller/processor240) and memory242to perform aspects of any of the methods described herein (for example, as described with reference toFIGS.5-7).

Controller/processor240of base station110, controller/processor280of UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with time division duplexing (TDD) downlink-uplink configuration signaling, as described in more detail elsewhere herein. For example, controller/processor240of base station110, controller/processor280of UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, process600ofFIG.6, process700ofFIG.7, and/or other processes as described herein. Memories242and282may store data and program codes for base station110and UE120, respectively. In some aspects, memory242and/or memory282may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station110and/or the UE120, may cause the one or more processors, the UE120, and/or the base station110to perform or direct operations of, for example, process600ofFIG.6, process700ofFIG.7, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a first wireless node (e.g., BS110, and/or UE120) may include means for transmitting, to a second wireless node, a cross-link interference (CLI) management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats, means for communicating with one or more third wireless nodes in accordance with the order of slot formats indicated to the second wireless node, and/or the like. In some aspects, such means may include one or more components of UE120described in connection withFIG.2, such as controller/processor280, transmit processor264, TX MIMO processor266, MOD254, antenna252, DEMOD254, MIMO detector256, and/or receive processor258, among other examples. In some aspects, such means may include one or more components of BS110described in connection withFIG.2, such as antenna234, DEMOD232, MIMO detector236, receive processor238, controller/processor240, transmit processor220, TX MIMO processor230, MOD232, and/or antenna234, among other examples.

In some aspects, a second wireless node (e.g., BS110, and/or UE120) may include means for receiving, from a first wireless node, a CLI management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats, means for communicating with one or more third wireless nodes in accordance with the order of slot formats received from the first wireless node, and/or the like. In some aspects, such means may include one or more components of UE120described in connection withFIG.2, such as controller/processor280, transmit processor264, TX MIMO processor266, MOD254, antenna252, DEMOD254, MIMO detector256, and/or receive processor258, among other examples. In some aspects, such means may include one or more components of BS110described in connection withFIG.2, such as antenna234, DEMOD232, MIMO detector236, receive processor238, controller/processor240, transmit processor220, TX MIMO processor230, MOD232, and/or antenna234, among other examples.

While blocks inFIG.2are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor264, the receive processor258, and/or the TX MIMO processor266may be performed by or under the control of controller/processor280.

As indicated above,FIG.2is provided as an example. Other examples may differ from what is described with regard toFIG.2.

FIG.3is a diagram illustrating examples300of radio access networks, in accordance with the disclosure.

As shown by reference number305, a traditional (e.g., 3G, 4G, and/or LTE) radio access network may include multiple base stations310(e.g., access nodes (AN)), where each base station310communicates with a core network via a wired backhaul link315, such as a fiber connection. A base station310may communicate with a UE320via an access link325, which may be a wireless link. In some aspects, a base station310shown in3may be a base station110shown inFIG.1. In some aspects, a UE320shown in3may be a UE120shown inFIG.1.

As shown by reference number330, a radio access network may include a wireless backhaul network, sometimes referred to as an integrated access and backhaul (IAB) network. In an JAB network, at least one base station is an anchor base station335that communicates with a core network via a wired backhaul link340, such as a fiber connection. An anchor base station335may also be referred to as an JAB donor (or IAB-donor). The JAB network may include one or more non-anchor base stations345, sometimes referred to as relay base stations or JAB nodes (or IAB-nodes). The non-anchor base station345may communicate directly or indirectly with the anchor base station335via one or more backhaul links350(e.g., via one or more non-anchor base stations345) to form a backhaul path to the core network for carrying backhaul traffic. Backhaul link350may be a wireless link. Anchor base station(s)335and/or non-anchor base station(s)345may communicate with one or more UEs355via access links360, which may be wireless links for carrying access traffic. In some aspects, an anchor base station335and/or a non-anchor base station345shown inFIG.3may be a base station110shown inFIG.1. In some aspects, a UE355shown inFIG.3may be a UE120shown inFIG.1.

As shown by reference number365, in some aspects, a radio access network that includes an JAB network may utilize millimeter wave technology and/or directional communications (e.g., beamforming) for communications between base stations and/or UEs (e.g., between two base stations, between two UEs, and/or between a base station and a UE). For example, wireless backhaul links370between base stations may use millimeter wave signals to carry information and/or may be directed toward a target base station using beamforming, among other examples. Similarly, the wireless access links375between a UE and a base station may use millimeter wave signals and/or may be directed toward a target wireless node (e.g., a UE and/or a base station). In this way, inter-link interference may be reduced.

The configuration of base stations and UEs inFIG.3is shown as an example, and other examples are contemplated. For example, one or more base stations illustrated in3may be replaced by one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network, and/or a device-to-device network). In this case, an anchor node may refer to a UE that is directly in communication with a base station (e.g., an anchor base station or a non-anchor base station).

As indicated above,FIG.3is provided as an example. Other examples may differ from what is described with regard toFIG.3.

FIG.4is a diagram illustrating an example400of an JAB network architecture, in accordance with the disclosure.

As shown inFIG.4, an JAB network may include an JAB donor405(shown as IAB-donor) that connects to a core network via a wired connection (shown as a wireline backhaul). For example, an Ng interface of an JAB donor405may terminate at a core network. Additionally, or alternatively, an JAB donor405may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). In some aspects, an JAB donor405may include a base station110, such as an anchor base station, as described above in connection withFIG.3. As shown, an JAB donor405may include a central unit (CU), which may perform access node controller (ANC) functions, and/or AMF functions, among other examples. The CU may configure a distributed unit (DU) of the JAB donor405and/or may configure one or more JAB nodes410(e.g., a mobile termination (MT) and/or a DU of an JAB node410) that connect to the core network via the JAB donor405. Thus, a CU of an JAB donor405may control and/or configure the entire JAB network that connects to the core network via the JAB donor405, such as by using control messages and/or configuration messages (e.g., a radio resource control (RRC) configuration message, and/or an F1 application protocol (F1AP) message).

As further shown inFIG.4, the JAB network may include JAB nodes410(shown as IAB-node1, IAB-node2, and IAB-node3) that connect to the core network via the JAB donor405. As shown, an JAB node410may include MT functions (also sometimes referred to as UE functions (UEF)) and may include DU functions (also sometimes referred to as access node functions (ANF)). The MT functions of an JAB node410(e.g., a child node) may be controlled and/or scheduled by another JAB node410(e.g., a parent node of the child node) and/or by an JAB donor405. The DU functions of an JAB node410(e.g., a parent node) may control and/or schedule other JAB nodes410(e.g., child nodes of the parent node) and/or UEs120. Thus, a DU may be referred to as a scheduling node or a scheduling component, and an MT may be referred to as a scheduled node or a scheduled component. In some aspects, an JAB donor405may include DU functions and not MT functions. That is, an JAB donor405may configure, control, and/or schedule communications of JAB nodes410and/or UEs120. A UE120may include only MT functions, and not DU functions. That is, communications of a UE120may be controlled and/or scheduled by an JAB donor405and/or an JAB node410(e.g., a parent node of the UE120).

When a first node controls and/or schedules communications for a second node (e.g., when the first node provides DU functions for the second node's MT functions), the first node may be referred to as a parent node of the second node, and the second node may be referred to as a child node of the first node. A child node of the second node may be referred to as a grandchild node of the first node. Thus, a DU function of a parent node may control and/or schedule communications for child nodes of the parent node. A parent node may be an JAB donor405or an JAB node410, and a child node may be an JAB node410or a UE120. Communications of an MT function of a child node may be controlled and/or scheduled by a parent node of the child node.

As further shown inFIG.4, a link between a UE120(e.g., which only has MT functions, and not DU functions) and an JAB donor405, or between a UE120and an IAB node410, may be referred to as an access link415. Access link415may be a wireless access link that provides a UE120with radio access to a core network via an JAB donor405, and optionally via one or more JAB nodes410. Thus, the network illustrated inFIG.4may be referred to as a multi-hop network or a wireless multi-hop network.

As further shown inFIG.4, a link between an JAB donor405and an JAB node410or between two JAB nodes410may be referred to as a backhaul link420. Backhaul link420may be a wireless backhaul link that provides an JAB node410with radio access to a core network via an JAB donor405, and optionally via one or more other JAB nodes410. In an JAB network, network resources for wireless communications (e.g., time resources, frequency resources, and/or spatial resources) may be shared between access links415and backhaul links420. In some aspects, a backhaul link420may be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link may be used if a primary backhaul link fails, becomes congested, and/or becomes overloaded, among other examples. For example, a backup link between IAB-node2and IAB-node3may be used for backhaul communications if a primary backhaul link between IAB-node2and IAB-node1fails. As used herein, “node” or “wireless node” may refer to an JAB donor405or an JAB node410.

As indicated above,FIG.4is provided as an example. Other examples may differ from what is described with regard toFIG.4.

Some communications systems may include cross-link interference (CLI) mitigation techniques. For example, on an F1-application protocol (F1-AP) interface between a DU and a CU, the DU may provide an intended time division duplexing (TDD) configuration of one or more cells of the DU. The DU may provide the intended TDD configuration to the CU via an F1 setup message, and/or a gNB-DU configuration update message, among other examples. Similarly, the CU may provide information identifying a TDD configuration of one or more neighboring cells of the CU. The CU may provide the intended TDD configuration to the DU via a gNB-CU configuration update message. An intended TDD configuration (e.g., an intended TDD downlink (DL)-uplink (UL) configuration) may use a message format associated with a TDD dedicated configuration message. The CU may communicate with other CUs over an Xn interface to exchange information related to the intended TDD configuration.

However, some slot formats, which may be used by cells neighboring a CU or cells of a DU, are not compatible with intended TDD configuration signaling. For example, a format of an intended TDD configuration message may not allow indication of slot formats of a format:[N1UL symbols, N2flexible (F) symbols, N3DL symbols]

where N1, N2, and N3are positive integers and where N1, N2, and N2are quantities of symbols in an ordered set of symbols. In other words, an intended TDD configuration message may not enable indication of a slot format that includes a first quantity of uplink symbols, followed by a second quantity of flexible symbols, followed by a third quantity of downlink symbols.

Moreover, some other types of slot formats may not be supported in an intended TDD configuration message, such as when N1>0, N2=0, and N3>0; when N1>0, N2>0, and N3=0; and/or when N1=0, N2>0, and N3>0; among other examples. Some slot formats which cannot be indicated using an intended TDD configuration message may be indicatable using a TDD dedicated configuration message or a slot format indicator. However, using a slot format indicator or a TDD dedicated configuration message may not enable dynamic configuration to reduce CLI.

Moreover, the intended TDD configuration message may not support other indications that may be used to reduce CLI, such as indications identifying whether resources are available or not available, indications of other types of slot formats (e.g., slot formats of full-duplex symbols or bidirectional symbols), and/or indications on a per-transmit receive point (TRP) basis, among other examples. Thus, some aspects described herein provide enhancements for intended TDD configuration messages. For example, some aspects described herein provide additional information elements (IEs) in an intended TDD configuration message to identify the aforementioned slot formats, and/or indicate whether resources are available, indicate additional symbol types in some slot formats, among other examples.

In this way, wireless nodes, such as a CU or a DU, may communicate intended TDD configuration messages to reduce CLI relative to intended TDD configuration messages that do not have IEs described herein. Moreover, the wireless nodes may provide per-TRP configuration information in the TDD configuration messages, thereby enabling different TDD configurations for different TRPs associated with a cell. In this way, the wireless nodes enable improved flexibility in configuring TRPs associated with a cell, thereby improving a utilization of network resources.

FIG.5is a diagram illustrating an example500of TDD DL-UL configuration signaling, in accordance with the present disclosure. As shown inFIG.5, example500includes a first wireless node505, a second wireless node510, and a third wireless node515.

As further shown inFIG.5, and by reference number520, the first wireless node505may determine a slot format. For example, a DU may determine a slot format for one or more cells of the DU. Additionally, or alternatively, a CU may determine a slot format for one or more neighbor cells of the CU (e.g., one or more cells of a DU of a CU that neighbors the CU). In some aspects, the first wireless node505may determine the slot format based at least in part on a network traffic characteristic. For example, the first wireless node505may schedule one or more symbols as uplink symbols, downlink symbols, and/or flexible symbols, among other examples, based at least in part on a level of network traffic for an uplink or a downlink in a cell of first wireless node505.

As further shown inFIG.5, and by reference number525, the first wireless node505may transmit a CLI management configuration message identifying a slot format. For example, the first wireless node505may transmit, to the second wireless node510, an intended TDD DL-UL configuration message including one or more IEs to identify a slot format. In some aspects, the first wireless node505may include a permutation indicator in the CLI management configuration message. For example, the first wireless node505may transmit an intended TDD DL-UL configuration message with an information element (IE) that identifies whether a slot format is a downlink-flexible-uplink (DFU) slot format (e.g., a slot format with symbols assigned, in order, as, for example, [D, . . . , D, F, . . . , F, U, . . . U], where a quantity, N1, N2, and N3of symbols assigned as D, F, and U, respectively, are each greater than or equal to 0). In other words, the IE may indicate a first quantity of downlink symbols, followed by a second quantity of flexible symbols, followed by a third quantity of uplink symbols. Additionally, or alternatively, the IE may include information identifying an uplink-flexible-downlink (UFD) slot format (e.g., a slot format with symbols assigned, in order, as, for example, [U, . . . , U, F, . . . , F, D, . . . D]). Additionally, or alternatively, the IE may include information identifying another type of slot format.

In some aspects, the IE may be a bit indicator. For example, the first wireless node505may include one or more bits set to a particular value to identify a type of slot format. In this way, the second wireless node510may use the one or more bits to identify the type of slot format and one or more other IEs of the TDD DL-UL configuration message to determine a slot format of the identified type of slot format (e.g., values for N1, N2, and N3). For example, the first wireless node505may include a first IE identifying a quantity of downlink symbols, a second IE identifying a quantity of uplink symbols, and a third IE identifying a slot format type. Based at least in part on the three IEs, the second wireless node510may infer (e.g., determine) a quantity of flexible symbols and determine an order of the uplink, downlink, and flexible symbols. Additionally, or alternatively, the first wireless node505may include one or more IEs identifying other types of symbol assignments, such as a full-duplex or a bidirectional symbol assignment.

In some aspects, the first wireless node505may include information identifying an availability of one or more resources. For example, when the first wireless node505is a CU and the second wireless node510is a DU, the first wireless node505may indicate whether one or more resources are available or not available based at least in part on a presence of another DU in a neighbor cell for which the first wireless node505is providing an intended TDD DL-UL configuration. In this case, the second wireless node510may identify one or more resources that are not available for communication based at least in part on the intended TDD DL-UL configuration indicating whether the one or more resources are hard-assigned, soft-assigned, or not-available-assigned. In some cases, the first wireless node505may group hard-assigned resources and soft-assigned resources into a single ‘available’ category and include an IE identifying whether one or more resources are ‘available’ (e.g., hard-assigned or soft-assigned) or ‘not available’ (e.g., not-available-assigned). In some aspects, the first wireless node505may identify a symbol assignment (e.g., downlink, and/or uplink flexible) of not available resources and/or of available resources.

In some aspects, the first wireless node505may include per-TRP configuration information in the CLI management configuration message. For example, when a plurality of TRPs are deployed in the same cell with different configurations, the first wireless node505may include a plurality of intended TDD DL-UL configurations and associated IEs for the plurality of TRPs. In this case, the first wireless node505may include a different identifier to identify each TRP of the plurality of TRPs. For example, the first wireless node505may include a physical cell identifier, a TRP identifier, a beam direction identifier, and/or a beam identifier, among other examples, and the second wireless node510may use included identifiers to determine which TRP is associated with which intended TDD DL-UL configuration and associated IEs.

As further shown inFIG.5, and by reference number530, the first wireless node505and/or the second wireless node510may communicate with one or more third wireless nodes515in accordance with an identified slot format. For example, the first wireless node505may communicate with a first UE120using the identified slot format, and the second wireless node510may communicate with a second UE120using a different slot format selected to avoid CLI with communications between the first wireless node505and the first UE120.

As indicated above,FIG.5is provided as an example. Other examples may differ from what is described with respect toFIG.5.

FIG.6is a diagram illustrating an example process600performed, for example, by a first wireless node, in accordance with the present disclosure. Example process600is an example where the first wireless node (e.g., UE120, BS110, and/or first wireless node505) performs operations associated with TDD downlink-uplink configuration signaling.

As shown inFIG.6, in some aspects, process600may include transmitting, to a second wireless node, a CLI management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats (block610). For example, the first wireless node (e.g., using controller/processor240, transmit processor220, TX MIMO processor230, MOD232, antenna234, controller/processor280, transmit processor264, TX MIMO processor266, MOD254, and/or antenna252) may transmit, to a second wireless node, a CLI management configuration message including a permutation indicator, as described above. In some aspects, the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats.

As further shown inFIG.6, in some aspects, process600may include communicating with one or more third wireless nodes in accordance with the order of slot formats indicated to the second wireless node (block620). For example, the first wireless node (e.g., using controller/processor240, transmit processor220, TX MIMO processor230, MOD232, antenna234, controller/processor280, transmit processor264, TX MIMO processor266, MOD254, antenna252, DEMOD232, MIMO detector236, receive processor238, DEMOD254, MIMO detector256, and/or receive processor258) may communicate with one or more third wireless nodes in accordance with the order of slot formats indicated to the second wireless node, as described above.

Process600may include additional 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.

In a first aspect, the CLI management configuration message includes an availability indicator corresponding to one or more resources identified in the CLI management configuration message, where the availability indicator indicates that the one or more resources are available or not available.

In a second aspect, alone or in combination with the first aspect, a hard allocated resource or a soft allocated resource, of the one or more resources, is assigned an available value for the availability indicator.

In a third aspect, alone or in combination with one or more of the first and second aspects, the CLI management configuration message indicates, for a resource, of the one or more resources, associated with a not available value for the availability indicator, whether the resource is assigned as a downlink resource, an uplink resource, or a flexibly assigned resource.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the CLI management configuration message includes an indicator for a full-duplex or includes a bidirectional symbol slot format.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the CLI management configuration message includes a plurality of per-transmit receive point (TRP) configurations associated with a plurality of TRP identifiers or beam direction identifiers.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the CLI management configuration message is at least one of: an intended time division duplexing downlink-uplink configuration message, a configuration update message, an F1-AP interface message, or an Xn interface message.

AlthoughFIG.6shows example blocks of process600, in some aspects, process600may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.6. Additionally, or alternatively, two or more of the blocks of process600may be performed in parallel.

FIG.7is a diagram illustrating an example process700performed, for example, by a second wireless node, in accordance with the present disclosure. Example process700is an example where the second wireless node (e.g., BS110, UE120, and/or second wireless node510) performs operations associated with TDD downlink-uplink configuration signaling.

As shown inFIG.7, in some aspects, process700may include receiving, from a first wireless node, a CLI management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats (block710). For example, the second wireless node (e.g., using antenna234, DEMOD232, MIMO detector236, receive processor238, controller/processor240, antenna252, DEMOD254, MIMO detector256, receive processor258, and/or controller/processor280) may receive, from a first wireless node, a CLI management configuration message including a permutation indicator, as described above. In some aspects, the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats.

As further shown inFIG.7, in some aspects, process700may include communicating with one or more third wireless nodes in accordance with the order of slot formats received from the first wireless node (block720). For example, the second wireless node (e.g., using controller/processor240, transmit processor220, TX MIMO processor230, MOD232, antenna234, controller/processor280, transmit processor264, TX MIMO processor266, MOD254, antenna252, DEMOD232, MIMO detector236, receive processor238, DEMOD254, MIMO detector256, and/or receive processor258) may communicate with one or more third wireless nodes in accordance with the order of slot formats received from the first wireless node, as described above.

Process700may include additional 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.

In a first aspect, the CLI management configuration message includes an availability indicator corresponding to one or more resources identified in the CLI management configuration message, where the availability indicator indicates that the one or more resources are available or not available.

In a second aspect, alone or in combination with the first aspect, a hard allocated resource or a soft allocated resource, of the one or more resources, is assigned an available value for the availability indicator.

In a third aspect, alone or in combination with one or more of the first and second aspects, the CLI management configuration message indicates, for a resource, of the one or more resources, associated with a not available value for the availability indicator, whether the resource is assigned as a downlink resource, an uplink resource, or a flexibly assigned resource.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the CLI management configuration message includes an indicator for a full-duplex or includes a bidirectional symbol slot format.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the CLI management configuration message includes a plurality of per-TRP configurations associated with a plurality of TRP identifiers or beam direction identifiers.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the CLI management configuration message is at least one of: an intended time division duplexing downlink-uplink configuration message, a configuration update message, an F1-AP interface message, or an Xn interface message.

AlthoughFIG.7shows example blocks of process700, in some aspects, process700may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.7. Additionally, or alternatively, two or more of the blocks of process700may be performed in parallel.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a first wireless node, comprising: transmitting, to a second wireless node, a cross-link interference (CLI) management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats; and communicating with one or more third wireless nodes in accordance with the order of slot formats indicated to the second wireless node.

Aspect 2: The method of Aspect 1, wherein the CLI management configuration message includes an availability indicator corresponding to one or more resources identified in the CLI management configuration message, wherein the availability indicator indicates that the one or more resources are available or not available.

Aspect 3: The method of Aspect 2, wherein a hard allocated resource or a soft allocated resource, of the one or more resources, is assigned an available value for the availability indicator.

Aspect 4: The method of any of Aspects 2-3, wherein the CLI management configuration message indicates, for a resource, of the one or more resources, associated with a not available value for the availability indicator, whether the resource is assigned as a downlink resource, an uplink resource, or a flexibly assigned resource.

Aspect 5: The method of any of Aspects 1-4, wherein the CLI management configuration message includes an indicator for a full-duplex or includes a bidirectional symbol slot format.

Aspect 6: The method of any of Aspects 1-5, wherein the CLI management configuration message includes a plurality of per-transmit receive point (TRP) configurations associated with a plurality of TRP identifiers or beam direction identifiers.

Aspect 7: The method of any of Aspects 1-6, wherein the CLI management configuration message is at least one of: an intended time division duplexing (TDD) downlink-uplink (DL-UL) configuration message, a configuration update message, an F1-AP interface message, or an Xn interface message.

Aspect 8: A method of wireless communication performed by a second wireless node, comprising: receiving, from a first wireless node, a cross-link interference (CLI) management configuration message including a permutation indicator, wherein the permutation indicator indicates that an order of slot formats is an uplink-flexible-downlink order of slot formats or indicates that the order of slot formats is a downlink-flexible-uplink order of slot formats; and communicating with one or more third wireless nodes in accordance with the order of slot formats received from the first wireless node.

Aspect 9: The method of Aspect 8, wherein the CLI management configuration message includes an availability indicator corresponding to one or more resources identified in the CLI management configuration message, wherein the availability indicator indicates that the one or more resources are available or not available.

Aspect 10: The method of Aspect 9, wherein a hard allocated resource or a soft allocated resource, of the one or more resources, is assigned an available value for the availability indicator.

Aspect 11: The method of any of Aspects 9-10, wherein the CLI management configuration message indicates, for a resource, of the one or more resources, associated with a not available value for the availability indicator, whether the resource is assigned as a downlink resource, an uplink resource, or a flexibly assigned resource.

Aspect 12: The method of any of Aspects 8-11, wherein the CLI management configuration message includes an indicator for a full-duplex or includes a bidirectional symbol slot format.

Aspect 13: The method of any of Aspects 8-12, wherein the CLI management configuration message includes a plurality of per-transmit receive point (TRP) configurations associated with a plurality of TRP identifiers or beam direction identifiers.

Aspect 14: The method of any of Aspects 8-13, wherein the CLI management configuration message is at least one of: an intended time division duplexing (TDD) downlink-uplink (DL-UL) configuration message, a configuration update message, an F1-AP interface message, or an Xn interface message.

Aspect 15: An apparatus for wireless communication at a device, 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-7.

Aspect 16: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more Aspects of Aspects 1-7.

Aspect 17: An apparatus for wireless communication, comprising at least one means for performing the method of one or more Aspects of Aspects 1-7.

Aspect 18: 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-7.

Aspect 19: 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-7.

Aspect 20: An apparatus for wireless communication at a device, 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 8-14.

Aspect 21: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more Aspects of Aspects 8-14.

Aspect 22: An apparatus for wireless communication, comprising at least one means for performing the method of one or more Aspects of Aspects 8-14.

Aspect 23: 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 8-14.

Aspect 24: 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 8-14.

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

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly 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 apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. 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 with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may 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 may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).