Managing cross-link interference for time division duplex and subband full duplex operation

Abstract

This disclosure provides systems, methods, and apparatuses for managing CLI (115) in a radio access network (101) that employs time division duplex (TDD) and subband full duplex (SBFD) operation. A first network entity (104) and a second network entity (106) can exchange CLI management information (130). For example, CLI management information can include TDD configuration, SBFD configuration and / or CLI assistance information (such as CLI measurement resource configuration(s), identification of cell(s) / beam(s) causing or experiencing CLI, CLI thresholds, CLI management parameters, and CLI handling parameters, among other examples). The network entities can exchange the CLI management information via setup messages (120) or update messages (140) over an interface (105, such as an Xn interface or F1 interface) between the network entities. Additionally, the network entities can implement a protocol for CLI mitigation, such as a CLI mitigation messages (160).

Description

Docket No. 14730815100PCTMANAGING CROSS-LINK INTERFERENCE FOR TIME DIVISION DUPLEX AND SUBBAND FULL DUPLEX OPERATIONRELATED APPLICATION

[0001] This application claims the priority benefit of U.S. Provisional Patent Application Serial No. 63 / 680.969, filed August 8, 2024, and U.S. Provisional Patent Application Serial No. 63 / 686,125, filed August 22, 2024, and both entitled “MANAGING CROSS-LINK INTERFERENCE FOR TIME DIVISION DUPLEX AND SUBBAND FULL DUPLEX OPERATION,” the entire contents of which are both hereby incorporated by reference herein.TECHNICAL FIELD

[0002] This disclosure relates generally to wireless communication and some aspects relate to managing cross-link interference (CLI) for time division duplex (TDD) and subband full duplex (SBFD) operation.BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] In a wireless communication system, a network entity (such as a base station, radio access network (RAN) node, etc.) and a user equipment (UE) communicate via wireless channels. For example, the network entity communicates downlink (DL) transmissions to the UE via various physical channels, such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH). The UE communicates uplink (UL) transmissions to the network entity via various uplink channels, such as a physical random access channel (PRACH), a physical uplink control channel (PUCCH), and a physical uplink shared channel (PUSCH). In addition to physical channels, the network entity and UE can transmit various reference signals, such as a downlink reference signal (DL-RS) or a sounding reference signal (SRS).

[0005] Typical wireless communication systems employ multiple-access technologies adopted in various telecommunication standards. An example telecommunication standard is 5G NewDocket No. 14730815100PCTRadio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP). Time-division duplex (TDD) communication is an example multiple-access technology widely deployed in commercial 5G NR systems. In a TDD system, the network splits time domain resources for DL, UL, or flexible (DL or UL) periods according to a TDD pattern. An inherent limitation of TDD is the division of the time domain resource between downlink and uplink communication. Uplink allocations with limited time durations can lead to reduced coverage, increased latency, and reduced capacity compared to frequency-division duplex (FDD) system.

[0006] To address the limitations of TDD, 3 GPP has introduced a new multiple-access technology, called subband full duplex (SBFD), which borrows concepts from TDD and FDD. SBFD allows for simultaneous downlink and uplink transmissions within a TDD carrier through strategic placement of SBFD subbands. It consists of creating a frequency region (refer to a subband) in a time domain resource, where the transmission direction is different from the configured / indicated TDD pattern. In some examples, the network entity can configure a UL subband to a slot / symbol that is configured, in the TDD pattern, as downlink or flexible. Likewise, the network entity can configure a DL subband to a slot / symbol that is configured, in the TDD pattern, as uplink or flexible. In some examples, the network entity can configure a flexible subband to a slot / symbol that is configured, in the TDD pattern, as downlink or uplink. In SBFD operation, a network entity can receive uplink (such as from a first UE) in one subband of a slot and can transmit downlink (such as to a second UE) in another subband of the same slot.

[0007] Cross-link interference (CLI) refers to interference that can occur when a transmission (from a UE or network entity) in one subband impacts reception (at another UE or the network entity) in another subband, or vice versa. For example, an UL transmission from a first UE in a first cell of a first network entity can overlap time / frequency domain resources of a DL transmission to a second UE (potentially in a second cell of a second network entity). Depending on the signal strengths of the UL / DL transmissions, the first network entity or the second UE can experience CLI impacting their ability to receive the respective UL / DL transmissions. CLI can degrade the overall network performance by causing increased error rates, reduced data throughput, and poorer quality of service.BRIEF SUMMARYDocket No. 14730815100PCT

[0008] The systems, methods, and apparatuses of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0009] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a first network entity. The method includes the first network entity operating a first cell with a first time division duplex (TDD) downlink (DL)-uplink (UL) configuration and a first subband full duplex (SBFD) configuration. The method includes the first network entity transmitting, to a second network entity, first crosslink interference (CLI) management information. The first CLI management information includes at least one of: the first TDD DL-UL configuration, the first SBFD configuration, or first CLI assistance information. The method includes the first network entity receiving, from the second network entity, second CLI management information. The second CLI management information including at least one of a second TDD DL-UL configuration of a second cell, a second SBFD configuration of the second cell, or second CLI assistance information.

[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a second network entity. The method includes the second network entity receiving, from a first network entity, first CLI management information. The first CLI management information includes at least one of a first TDD DL- UL configuration of a first cell, a first SBFD configuration of the first cell, or first CLI assistance information. The method includes the second network entity operating a second cell with a second TDD DL-UL configuration and a second SBFD configuration. The method includes the second network entity transmitting, to the first network entity, second CLI management information. The second CLI management information includes at least one of: the second TDD DL-UL configuration, the second SBFD configuration, or second CLI assistance information.

[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus that includes a communication unit and a processing system configured to control the communication unit to implement any one of the above-referenced methods.

[0012] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.BRIEF DESCRIPTION OF THE DRAWINGSDocket No. 14730815100PCT

[0013] Like reference numbers and designations in the various drawings indicate like elements. Note that the relative dimensions of the figures may not be drawn to scale. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0014] FIG. 1A shows an example wireless system with example operations to manage crosslink interference (CLI) for time division duplex (TDD) and subband full duplex (SBFD) operation.

[0015] FIG. IB shows an example TDD / SBFD pattern resulting in potential CLI.

[0016] FIG. 1C shows an example of CLI involving TDD / SBFD patterns of two network entities.

[0017] FIG. 2 shows a message flow diagram and operations for communicating CLI management information (e.g., TDD configuration, SBFD configuration, and / or CLI assistance information) and CLI mitigation information.

[0018] FIG. 3A shows a format of an example message including CLI management information.

[0019] FIG. 3B shows a format of an example message including CLI mitigation information.

[0020] FIG. 4A shows a message flow diagram of a first example setup procedure for communicating CLI management information.

[0021] FIG. 4B shows a message flow diagram of a second example setup procedure for communicating CLI management information.

[0022] FIG. 4C shows a message flow diagram of a third example setup procedure for communicating CLI management information.

[0023] FIG. 4D shows a message flow diagram of an update procedure for updating CLI management information.

[0024] FIG. 5 shows a message flow diagram of CLI mitigation.

[0025] FIG. 6A shows a message flow diagram in which a distributed base station implements a first example setup procedure similar to FIG. 4A.

[0026] FIG. 6B shows a message flow diagram in which a distributed base station implements a second example setup procedure similar to FIG. 4B.

[0027] FIG. 6C shows a message flow diagram in which a distributed base station implements a third example setup procedure similar to FIG. 4C.Docket No. 14730815100PCT

[0028] FIG. 7 shows a message flow diagram in which a distributed base station implements CLI mitigation.

[0029] FIG. 8 shows a message flow diagram of a distributed base station coordinating CLI mitigation with one or more other radio access network (RAN) nodes.

[0030] FIG. 9 shows a flow diagram of example operations of a first network entity providing CLI management information to a second network entity.

[0031] FIG. 10 shows a flow diagram of example operations of a network entity performing CLI mitigation based on CLI management information from a second network entity.

[0032] FIG. 11 shows a flow diagram of example operations of first network entity managing CLI measurements based on CLI management information from a second network entity.

[0033] FIG. 12A shows a flow diagram of example operations of a first network entity enabling CLI mitigation based on CLI mitigation request(s) from one or more other network entities.

[0034] FIG. 12B shows a flow diagram of example operations of first network entity enabling and disabling CLI mitigation based on CLI mitigation request(s) from a second network entity.

[0035] FIG. 13 shows a flow diagram of example operations of first network entity selectively accepting or rejecting a CLI mitigation request from a second network entity.

[0036] FIG. 14 is a block diagram of example distributed or disaggregated implementation of an example base station using a central unit (CU) and a distributed unit (DU).

[0037] FIG. 15 shows a message flow diagram with some potential variations for managing CLI with TDD / SBFD operation.

[0038] FIG. 16 shows a block diagram illustrating example configurations of a network entity and a user equipment.

[0039] FIG. 17 shows a block diagram of an example wireless communication system showing hardware features and communication interfaces.DETAILED DESCRIPTION

[0040] The following description is directed to certain implementations for the purpose of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless communication according to the 3rd Generation Partnership Project (3GPP) wireless standards, such as the 4th generationDocket No. 14730815100PCT(4G) Long Term Evolution (LTE) and 5th generation (5G) New Radio (NR) standards. However, the described implementations can be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802. 11 or 802. 16 wireless standards, or other known signals that are used to communicate within a wireless, cellular, or internet-of-things (loT) network, such as a system utilizing 4G, 5G, 6th generation (6G), ZigBee, Bluetooth, WiFi, or future radio technology.

[0041] A wireless communication system can implement time-division duplex (TDD) operation and subband full duplex (SBFD) operation (sometimes also referred to as subband nonoverlapping full duplex). TDD operation enables a network entity (such as a base station (BS)) to configure time domain resources according to a TDD pattern for uplink (UL), downlink (DL), or flexible (X, i.e., UL or DL) transmissions in various symbols / slots. SBFD operation enables the network entity to configure UL or DL transmissions in subband portions of a symbol / slot. The network entity can employ SBFD operation to schedule DL reception to some UEs and schedule UL transmissions from some other UEs in the same symbol / slot. SBFD operation provides advantages in decreasing latency and increasing flexibility of a TDD system. However, the use of SBFD operation can create cross-link interference (CLI). Furthermore, 5G NR has a variety of time / frequency resource configuration features such as bandwidth part (BWP) switching, dynamic TDD, etc., that might coexist with SBFD operation. It is desirable for network entities to communicate CLI management information and / or CLI mitigation information to avoid / mitigate CLI between cells of different network entities. For example, network entities should exchange information about the TDD / SBFD configurations and CLI- related information. Current techniques for managing CLI are inadequate to address the wide variety of network deployments and SBFD scenarios.

[0042] This disclosure provides systems, methods, and apparatuses for managing CLI in a wireless communication system that employs TDD / SBFD operation. In accordance with aspects of this disclosure, a first network entity and a second network entity can exchange CLI management information. CLI management information (sometimes referred to as TDD / SBFD / CLI information) can include TDD configuration, SBFD configuration, and / or CLI assistance information. Examples of CLI assistance information include CLI measurement resource configuration(s), identification of cell(s) / beam(s) causing or experiencing CLI, CLI thresholds, CLI management parameters, and CLI handling parameters, among other examples.Docket No. 14730815100PCTThe network entities can exchange the CLI management information via setup messages or update messages over an interface (such as an Xn interface or Fl interface) between the network entities. In some aspects, the network entities can implement a protocol for CLI mitigation, such as a CLI mitigation request, acknowledgement, and / or CLI mitigation results. A CLI mitigation request can include CLI mitigation information, such as an identification of cell(s) / beam(s) / resource(s), CLI measurement results, and / or CLI mitigation parameters.

[0043] In some aspects, network entities can exchange CLI management information as part of a setup procedure for establishing a connection over the interface between the network entities. For example, the setup procedure can include a setup request message (such as an Xn Setup Request message or F 1 Setup Request message) and setup response message (such as an Xn Setup Response message or Fl Setup Response message) that include CLI management information. Additionally, or alternatively, the network entities can exchange the CLI management information via update messages (such as NG-RAN node configuration update messages). The network entities can also communicate updated TDD / SBFD configuration(s) or CLI assistance information via update messages based on changes to CLI management information or changes to the amount of CLI.

[0044] Some aspects of this disclosure enable network entities of a distributed base station to communicate CLI management information and CLI mitigation information. A distributed base station can include a central unit (CU) and one or more distributed units (DUs). The CU and DU can communicate the CLI management information and CLI mitigation information via an Fl interface between the CU and the DU. According to aspects of this disclosure, a network entity (such as a base station or CU) can relay or coordinate information among multiple other network entities.

[0045] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. Network entities (such as BSs, CUs, DUs, or other RAN nodes) can better manage CLI and CLI mitigation techniques to improve overall system efficiency. CLI management / mitigation enables network entities to realize the advantages of SBFD operation while reducing potential negative impacts of CLI. Advantageously, some implementations of this disclosure use existing interfaces and RAN message types (with modifications), resulting in faster adoption of this technology easier and enabling backward compatibility.Docket No. 14730815100PCT

[0046] FIG. 1A shows an example wireless system 100A with example operations to manage cross-link interference (CLI) for time division duplex (TDD) and subband full duplex (SBFD) operation. The example wireless system 100A shows a first UE 102A ("UE1"), a second UE 102B ("UE2") communicating with a first network entity 104 operating a first cell 108A. The example wireless system 100A also shows a third UE 102C ("UE3") communicating with a second network entity 106 operating a second cell 108B. The second network entity 106 might connect to the same core network 110 as the first network entity 104 or might connect to a different core network (such as a different wireless service provider or different public land mobile network (PLMN)). Although illustrated as smartphones in FIG. 1, the UEs 102A, 102B, 102C may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, an Internet-of-things (loT) device (e.g., sensor node, controller / actuator node, combination thereof), and the like. The UEs may communicate with first network entity 104 using wireless links (not shown in FIG. 1), which may be implemented as any suitable type of wireless link. The wireless links may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3GPP LTE, 5G NR, and so forth. Multiple wireless links may be aggregated in a carrier aggregation to provide a higher data rate for communication between a UE and the first network entity 104.

[0047] As an example, each of the first network entity 104 and the second network entity 106 may be a base station, an Evolved Universal Terrestrial Radio Access Network Node B (E- UTRAN Node B), evolved Node B (eNodeB or eNB), Next Generation Node B (gNodeB or gNB), Next Generation E-UTRAN Node B (ng-eNB), access point, radio head or the like. The network entities may be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof. The network entities may be configured to use multiple-input- multiple-output (MIMO) communication to exchange wireless signals with the UEs.

[0048] The first network entity 104 supports wireless communication with one or more UEs, such as the first UE 102A and the second UE 102B, via radio frequency (RF) signaling using one or more applicable radio access technologies (RATs) as specified by one or more communications protocols or standards. The first network entity 104 may employ any of a variety of RATs, such as operating as aNodeB (or base transceiver station (BTS)) for a UniversalDocket No. 14730815100PCTMobile Telecommunications System (UMTS) RAT (also known as “3G”), operating as an eNB for a 3GPP LTE RAT, operating as a gNB for a 3GPP 5G NR RAT, and the like.

[0049] The first network entity 104 may be part of a radio access network (RAN 101), for example, an Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN, or NR RAN. The first network entity 104 may be connected to a core network 110. For example, the first network entity 104 may connect to the core network 110 through an NG2 interface for control-plane signaling and use an NG3 interface for user-plane data communications when connecting to a 5G core network or use an Si interface for control-plane signaling and user-plane data communications when connecting to an Evolved Packet Core (EPC) network. The first network entity 104 may communicate using an Xn Application Protocol (XnAP) through an Xn interface or using an X2 Application Protocol (X2AP) through an X2 interface to exchange userplane and control -plane data. A UE may connect, via the core network 110, to one or more wide area networks (WANs) or other packet data networks (PDNs), such as the Internet.

[0050] In some aspects, the functionality, and thus the hardware components, of a network entity such as first network entity 104 may be distributed across multiple network nodes or devices and may be distributed in a manner to perform the functions described herein. As one example, the functionality of a network entity (e.g., first network entity 104) may be distributed across a radio unit (RU), a distributed unit (DU), or a central unit (CU).

[0051] Communications between a network entity and a UE utilize an uplink (UL) transmission path for RF transmissions from a UE to the network entity and a downlink (DL) transmission path for RF transmissions from the network entity to a UE. For example, as shown in FIG. 1A, the first UE 102 A utilizes an UL transmission path for a UL transmission 114A from the first UE 102A to the first network entity 104. The second UE 102B utilizes a DL transmission path for a DL transmission 114B from the first network entity 104 to the second UE 102B. The first network entity 104 can configure a channel state information (CSI) report configuration for a UE (such as either or both of the first UE 102A and the second UE 102B) to use to report the CSI. For a CSI report, a UE may report at least one of rank indicator (RI), precoder matrix indicator (PMI), channel quality indicator (CQI), and layer indicator (LI). A UE may use RI and PMI to indicate the digital precoder; CQI to indicate the signal-to-interference plus noise (SINR) status to assist the network entity in determining the modulation and coding scheme (MCS); and LI to identify the strongest layer for the reported precoder indicated by RI and PMI. When reporting the CSI by long physical uplink control channel (PUCCH) (e.g., PUCCH with 4 or more symbols)Docket No. 14730815100PCT or PUSCH, the UE transmits the RI and CQI for the first codeword on CSI part 1 and the remaining components of the CSI report on CSI part 2. The payload size for the CSI components in CSI part 1 is fixed, and the payload size for the CSI components in CSI part 2 depends on the value of RI reported in CSI part 1. The first network entity 104 can also configure a CSI report configuration for a UE to use to report the layer 1 reference signal received power (Ll-RSRP) or layer 1 signal-to-interference plus noise ratio (Ll-SINR) for one or more synchronization signal block (SSB) resources or CSI-RS resources. The UE reports the SSB resource indicators (SSBRIs) or CSI-RS resource indicators (CRIs) and the corresponding Ll-RSRP or Ll-SINR in CSI part 1. The UE can perform the Ll-RSRP measurements on a configured SRS.

[0052] In SBFD operation, the first network entity 104 is capable of concurrently transmitting DL communication and receiving UL communication during the same symbol or slot. For example, the first network entity 104 can configure the first UE 102A to transmit the UL transmission 114A via a physical uplink shared channel (PUSCH) in one portion (e.g., subband) of an SBFD symbol / slot (such as the PUSCH 114A in SBFD symbol / slot 111 shown in FIG. IB). The first network entity 104 can transmit the DL transmission 114B to the second UE 102B via a physical downlink shared channel (PDSCH) in another portion / subband of the SBFD symbol / slot (such as the PDSCH 114B in SBFD symbol / slot 111 shown in FIG. IB).

[0053] There are at least two types of CLI 115 that can occur in SBFD operation. The first type is gNB-to-gNB CLI 115A which happens when a network entity (e.g., the first network entity 104) receiving an UL transmission from a UE (e.g., first UE 102A) experiences interference caused by a neighboring network entity (e.g., the second network entity 106) transmitting in DL (e.g., DL transmission 116 to a third UE 102C). In some implementations, this scenario takes place if two neighboring network entities are using different SBFD patterns or configuration, if they belong to two different operators, or if one network entity is a legacy non-SBFD gNB and the other one is an SBFD gNB, among other examples. The second type of CLI in SBFD operation is UE-to-UE CLI. And there are two types of UE-to-UE CLI, intra-cell UE-to-UE CLI 115B and inter-cell UE-to-UE CLI 115C. Intra-cell UE-to-UE CLI 115B can happen when a UE (such as the first UE 102A) is transmitting in UL and another UE (such as the second UE 102B) is receiving in DL on the same subband or cell. It is possible for the UL transmission 114A of the first UE 102 A to cause intra-cell UE-to-UE CLI 115B to the second UE 102B. In the context of UE-to-UE CLI, the first UE 102A can be referred to as an aggressor UE, and the second UE 102B can be referred to as a victim UE. The first UE 102A is creating intra-subband interference forDocket No. 14730815100PCT the second UE 102B. Inter-cell UE-to-UE CLI 115C can happen when the first UE 102A is transmitting in UL and the third UE 102C is receiving in DL on an adjacent subband or cell. The UE-to-UE interference can be intra-cell if the two UEs belong to the same cell (such as shown in FIG. IB) or inter-cell if the two UEs belong to two different cells (such as shown in FIG. 1C).

[0054] The first network entity 104 and the second network entity 106 may communicate with each other via an interface 105. As an example, the interface 105 can be referred to as an Xn interface. In other examples of this disclosure, the network entities are part of a distributed base station where a CU has an Fl interface to one or more DUs. The network entities transmit information between themselves as messages over the interface 105. It is noted that, in the context of an interface between network entities, the term "transmit" does not require over-the- air RF transmission but instead can refer to communication over a wired (or wireless) network. In this disclosure, the term “transmit” can be replaced with “communicate”, “provide”, “send”, or “obtain” to include all forms of network communication.

[0055] In accordance with aspects of this disclosure, the first network entity 104 and the second network entity 106 can coordinate CLI management information 130 and / or CLI mitigation information 190 via the interface 105. The network entities can transmit the CLI management information 130 via one or more setup messages 120 or one or more update messages 140. When CLI is detected by either network entity, it can communicate a CLI mitigation request 160 or other CLI mitigation messages(s) via the interface 105. A CLI mitigation request 160 can include CLI mitigation information 190 and optionally also include CLI management information 130.

[0056] For consistency in this disclosure, operations related to CLI management and handling are described in the context of the first network entity 104 and the second network entity 106. The terms “first” and “second” in relation to the network entities are prescribed for purposes of describing the features of the network entities communicating with each other. It should be understood that either or both of the network entities 104, 106 can implement the features and the terms “first” and “second” can be reversed without departing from the described features.

[0057] FIG. IB shows a diagram 100B of an example TDD / SBFD pattern 118 resulting in potential CLI 115. In the illustrated TDD pattern, there is one downlink slot (denoted “D”), followed by 3 flexible slots (denoted “X”), and then an uplink slot (denoted “U”). Thus, the example TDD pattern might be referred to as “DXXXU.” In the flexible slots, such as symbol / slot 111, uplink transmissions can occupy a subband and downlink transmissions occupy different subband(s). The division of a TDD slot into different uplink and downlink subbandsDocket No. 14730815100PCT enables SBFD operation. SBFD patterns extend the underlying TDD pattern. Thus, the pattern can be referred to as a TDD / SBFD pattern 118. It is common for the uplink subband to be in the middle of the slot bandwidth (as shown in FIG. IB). However, there are a myriad of different TDD / SBFD patterns, including patterns with greater or fewer number of flexible slots and with larger or smaller subband sizes within the SBFD slots. As shown in FIG. IB, an uplink channel (PUSCH 114A) and a downlink channel (PDSCH 114B) can occupy different subbands of the same symbol / slot 111. A receiving device (such as a network entity receiving the PUSCH 114A or a UE receiving the PDSCH 114B) can experience CLI 115 caused by concurrent UL or DL transmissions in the symbol / slot 111. FIG. IB is an example scenario that can result in intra-cell UE-to-UE CLI 115B as described with reference to FIG. 1A. Because two or more network entities can operate cells with scheduled UL / DL transmissions it is possible for UEs or network entities of other cells to cause a receiving device to experience CLI.

[0058] FIG. 1C shows a system 100C of an example of CLI 115 involving first TDD / SBFD pattern 118A and second TDD / SBFD pattern 118B of two network entities (104, 106). FIG. 1C can be an example of the gNB-to-gNB CLI 115A described with reference to FIG. 1A. In the example shown in FIG. 1C, the second network entity 106 can be referred to as an aggressor node and communicates in a PDSCH 116 to a UE (such as the third UE 102C in the second cell 108B as shown in FIG. 1A). The first network entity 104 can be referred to as a victim node because it experiences CLI 115 caused by the PDSCH 116 of the second network entity 106. The CLI 115 can impact the first network entity 104 receiving a PUSCH 114A (such as from the first UE 102A in the first cell 108 A as shown in FIG. 1A).

[0059] FIG. 2 shows a message flow diagram 200 and operations for communicating CLI management information 130 (e.g., TDD configuration, SBFD configuration, and / or CLI assistance information) and CLI mitigation information 190. In some implementations, a first network entity 104 operates a first cell and is preconfigured with a first TDD DL-UL configuration, a first SBFD configuration, and / or first CLI assistance information. The second network entity 106 operates a second cell and may be preconfigured with a second TDD DL-UL configuration, a second SBFD configuration, and / or second CLI assistance information. The first network entity 104 and the second network entity 106 can communicate via an interface 105 (such as an Xn interface or an Fl interface).

[0060] The first network entity 104 and the second network entity 106 participate in an interface setup procedure 220 to establish the interface 105. In the example shown in FIG. 2, the firstDocket No. 14730815100PCT network entity 104 transmits a setup request message 224 via the interface 105 to the second network entity 106. In response to the setup request message 224, the second network entity 106 transmits a setup response message 226 to the first network entity 104. In some implementations (such as described with reference to FIG. 4A), the setup request message 224 and the setup response message 226 can include CLI management information 130. In some implementations (such as described with reference to FIG. 4B and FIG. 4C), the interface setup procedure 220 can also include one or more configuration update messages to carry at least a portion of the CLI management information 130. For example, the first network entity 104 can transmit a configuration update message 234 to the second network entity 106 after the setup request / response messages. The second network entity 106 can transmit a configuration update acknowledgement message 236 to the first network entity 104. The configuration update acknowledgement message 236 can also carry CLI management information 130 about the second cell in operation at the second network entity 106.

[0061] After the interface setup procedure 220, one or both of the network entities might update the CLI management information 130, such as based on a change to the TDD configuration, SBFD configuration, and / or CLI assistance information. The network entities can communicate updates using an update procedure 240. In the update procedure 240, the first network entity 104 transmits a configuration update message 244 to the second network entity 106. The configuration update message 244 can be a similar format as the configuration update message 234, such that the same message type can be used to convey CLI management information 130 during the interface setup procedure 220 and the update procedure 240. The second network entity 106 can transmit a configuration update acknowledgement message 246 to the first network entity 104.

[0062] One or both of the network entities can perform CLI mitigation 260 using the CLI management information 130 and CLI mitigation information 190. In the example shown in FIG. 2, the first network entity 104 transmits a CLI mitigation request message 264 to the second network entity 106 based on CLI experienced by the first network entity 104 or a UE in the first cell of the first network entity 104. The CLI mitigation request message 264 can include CLI mitigation information 190 to enable CLI mitigation operations at the second network entity 106. In response, the second network entity 106 transmits a CLI mitigation request acknowledgement message 266 to the first network entity 104. In another example, the second network entity 106 transmits a CLI mitigation request message to the first network entity 104 based on CLIDocket No. 14730815100PCT experienced by the second network entity 106 or a UE in the second cell of the second network entity 106. The CLI mitigation request message can include CLI mitigation information 190 to enable CLI mitigation operations at the first network entity 104. In response, the first network entity 104 transmits a CLI mitigation request acknowledgement message to the second network entity 106.

[0063] Having described the overall architecture of the CLI management information and CLI mitigation information, some examples of CLI management and mitigation can be described in the context of FIG. 2. After receiving the CLI management information 130, the second network entity 106 can configure UE(s) in its cell(s) to perform CLI measurements on the CLI measurement resource(s) indicated in the CLI management information 130. The second network entity 106 transmits one or more CLI measurement reporting configuration to the UE(s) to configure the UE(s) to report CLI measurement results. Based on the measurement resource configuration(s) and / or the CLI measurement report configuration(s), the UE(s) perform CLI measurements on the CLI measurement resource(s), obtains CLI measurement results from the CLI measurements, and transmits the CLI measurement results to the second network entity 106. Thus, the second network entity 106 receives CLI measurement results for the CLI measurement resource(s) from the UE(s). In other implementations, the second network entity 106 performs CLI measurements on the CLI measurement resource(s) and obtain CLI measurement results based on the CLI measurements. Based on the CLI measurement result(s), the second network entity 106 can determine that CLI from the first network entity 104 in the first cell to the second cell. In some implementations, (each of) the CLI measurement results includes CLLReceived Signal Strength Indicator (RSSI), CLI-Reference Signal Received Power (RSRP) and / or Sounding Reference Signal (SRS)-RSRP. The CLI-RSSI might be a layer 1 CLI-RSSI or a layer 3 CLI-RSSI. The CLLRSRP might be a layer 1 CLLRSRP or a layer 3 CLLRSRP. The SRS- RSRP might be a layer 1 SRS-RSRP or a layer 3 SRS-RSRP.

[0064] In some implementations, the first network entity 104 transmits second measurement resource configuration(s) to UE(s) (e.g., the first UE 102A or the second UE 102B in FIG. 1A) and configure the UE(s) to perform CLI measurements on the CLI measurement resource(s). The first network entity 104 can transmit one or more CLI measurement reporting configuration to the UE(s) to configure the UE(s) to report CLI measurement results that the UE(s) obtains from the CLI measurements that the UE(s) performs on the CLI measurement resource(s). Thus, the first network entity 104 receives CLI measurement results for the CLI measurement resource(s)Docket No. 14730815100PCT from the UE(s). In other implementations, the first network entity 104 can perform CLI measurements on the CLI measurement resource(s) and obtain CLI measurement results based on the CLI measurements. Based on the CLI measurement result(s), the first network entity 104 can determine that CLI from the second network entity 106 in the second cell to the first cell.

[0065] In some implementations, the second network entity 106 enables or performs CLI mitigation based on one or more TDD DL-UL configurations, one or more SBFD configurations, and / or one or more CLI assistance information for one or more cells that the second network entity 106 receives from one or more other BSs including the first network entity 104. For example, the second network entity 106 can enable or perform CLI mitigation based on the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI assistance information received in the setup request message 224. In some implementations, the second network entity 106 determines UL radio resources and DL radio resources of the second cell that overlap with DL resources and UL resources of the first cell respectively, based on the first TDD DL-UL configuration, the first SBFD configuration, the second TDD DL-UL configuration, and / or the second SBFD configuration. In some implementations, the overlapping UL radio resources of the second cell include one or more physical resource blocks and / or one or more symbols. When scheduling UL transmissions from one or more UEs on the second cell, the second network entity 106 may skip all of the overlapping UL radio resources of the second cell to completely avoid CLI to DL transmissions of the first cell. Alternatively, when scheduling UL transmissions from one or more UEs on the second cell, the second network entity 106 may skip some of the overlapping UL radio resources to mitigate CLI to DL transmissions of the first cell. In some implementations, the second network entity 106 determines a certain amount of the overlapping UL radio resources to skip based on the first CLI assistance information (e.g., the first CLI threshold). In some implementations, when scheduling UL transmissions using the overlapping UL radio resources from one or more UEs on the second cell, the second network entity 106 might configure or control UL transmission power of the UL transmissions to not exceed a maximum transmission power, in order to mitigate CLI to DL of the first cell. The second network entity 106 can determine the maximum transmission power based on the first CLI assistance information (e.g., the first CLI threshold).

[0066] When scheduling DL transmissions to one or more UEs on the second cell, the second network entity 106 may skip all of the overlapping DL radio resources of the second cell to avoid CLI to UL of the first cell. Alternatively, when scheduling DL transmissions to one or more UEsDocket No. 14730815100PCT on the second cell, the second network entity 106 may skip some of the overlapping DL radio resources to mitigate CLI to UL of the first cell, based on the first CLI assistance information. In some implementations, the second network entity 106 determines a certain amount of the overlapping DL radio resources to skip based on the first CLI assistance information (e.g., the first CLI threshold). In some implementations, when scheduling DL transmissions using the overlapping DL radio resources to one or more UEs on the second cell, the second network entity 106 can configure or control DL transmission power of the DL transmissions to not exceed a maximum transmission power, in order to mitigate CLI to UL of the first cell. In some implementations, the second network entity 106 determines the maximum transmission power based on the first CLI assistance information (e.g., the first CLI threshold).

[0067] The first CLI assistance information from first network entity 104 to second network entity 106 can include information based on per set of time / frequency radio resources. In one embodiment, the level of the CLI may be indicated per resource block (RB) or per group of RBs (e.g., subband CLIs and / or wideband CLI). In another embodiment, the level of the CLI may be indicated per symbol / slot or a set of symbols / slots or a set of resources or per beam. In yet another embodiment, the level of the CLI may be indicated in the time / frequency dimensions, for example, a set of contiguous RBs in the frequency domain and a set of contiguous symbols in the time domain. Other units or resolutions for the CLI indication are not excluded. The CLI could be indicated per set of measurements resources and associated with a resource ID. One CLI measurement reporting might consist of a pair of information: indication of CLI measurement (CLI level, high / low CLI, ...) and measurement resource set ID. In another example, one CLI measurement reporting might consist of a pair of information: indication of CLI measurement (CLI level, high / low CLI, ...) and beam ID. BS 106 takes the CLI levels and the CLI resolutions into consideration for the scheduling of its associated UEs. BS 106 may skip the overlapping DL radio resources with the associated reported CLI identified as high CLI (e.g., above a specific threshold) in order to mitigate CLI to the UL of the first cell. BS 106 may stop using a specific beam with the associated reported CLI identified as high CLI (e.g., above a specific threshold). Second network entity 106 may adjust the power level on a specific beam with the associated reported CLI identified as high CLI (e.g., above a specific threshold).

[0068] Similarly, the first network entity 104 can enable or perform CLI mitigation based on one or more TDD DL-UL configurations, one or more SBFD configurations, and / or one or moreDocket No. 14730815100PCTCLI assistance information for one or more cells that the first network entity 104 receives from one or more other BSs including the second network entity 106.

[0069] In some implementations, the second network entity 106 broadcasts system information (e.g., a system information block (SIB)) including a TDD UL and DL configuration (e.g., TDD- UL-DL-ConfigurationCommon) via the second cell 108B (with reference to FIG. 1 A). The TDD UL-DL configuration includes configuration parameters for a TDD carrier frequency of the second cell 108B. The parameters include a subcarrier spacing (e.g., referenceSubcarrierSpacing) and a pattern. The pattern parameter includes a periodicity of the pattern, number of DL slots, number of DL symbols, number of UL slots, and / or number of UL symbols. The number of DL slots configures the number of consecutive DL slots from the beginning of the pattern. The number of DL symbols configures the number of consecutive DL symbols in the beginning of the slot following the last DL slot of the consecutive DL slots. The number of UL slots configures the number of consecutive UL slots from the end of the pattern. The number of UL symbols configures the number of consecutive UL symbols in the end of the slot preceding the first UL slot of the consecutive UL slots. In some implementations, the SIB includes SIB1. In some implementations, the TDD UL and DL configuration is the second TDD DL-UL configuration. In other implementations, the TDD UL and DL configuration includes the second TDD DL-UL configuration.

[0070] In some implementations, the first network entity 104 broadcasts system information (e.g., a system information block (SIB)) including a TDD UL and DL configuration (e.g., TDD- UL-DL-ConfigurationCommon) via the first cell 108A (with reference to FIG. 1A). The TDD UL-DL configuration includes configuration parameters for a TDD carrier frequency of the first cell 108 A. The parameters include a subcarrier spacing (e.g., referenceSubcarrierSpacing) and a pattern. The pattern parameter includes a periodicity of the pattern, number of DL slots, number of DL symbols, number of UL slots, and / or number of UL symbols. The number of DL slots configures the number of consecutive DL slots from the beginning of the pattern. The number of DL symbols configures the number of consecutive DL symbols in the beginning of the slot following the last DL slot of the consecutive DL slots. The number of UL slots configures the number of consecutive UL slots from the end of the pattern. The number of UL symbols configures the number of consecutive UL symbols in the end of the slot preceding the first UL slot of the consecutive UL slots. In some implementations, the SIB includes SIB1. In some implementations, the TDD UL and DL configuration is the first TDD DL-UL configuration. InDocket No. 14730815100PCT other implementations, the TDD UL and DL configuration includes the first TDD DL-UL configuration.

[0071] In some implementations, any of the messages between the first network entity 104 and the second network entity 106 (such as any of the messages in interface setup procedure 220, the update procedure 240, or the CLI mitigation 260) can include beam-specific information. For example, the beam-specific information can indicate a beam causing the highest amount of CLI. Alternatively, or additionally, the beam-specific information can indicate the strongest beam (e.g., highest signal strength) that a network entity measures from among the beams of the other network entity. The beam-specific information can include a CSI-RS resource indicator (CRI) for a CSI-RS associate with a beam. Additionally, or alternatively, the beam-specific information can include an SSB index of an SSB within a set of SSBs configured for the other network entity.

[0072] Any of the messages in interface setup procedure 220, the update procedure 240, or the CLI mitigation 260 can include information about the CSI-RS resources configured for cell or beam. For example, a message can indicate the NZP-CSI-RS-Resource and / or NZP-CSI-RS- ResourceSet of a cell or beam. In some implementations, the message can indicate the number A of CSI-RS resources within a set of resources.

[0073] FIG. 3A shows a format of an example message including example CLI management information 330. The example CLI management information 330 can include one or more of a TDD DL-UL configuration 331, an SBFD configuration 332, and CLI assistance information 333. In some implementations, the TDD DL-UL configuration 331 indicates the TDD pattern (e.g., U, D, X slots) for one or more cells. The SBFD configuration 332 can indicate a pattern or subband division of various symbols / slots. In some implementations, the TDD DL-UL configuration 331 and / or the SBFD configuration 332 can refer to pre-defined configurations / patterns specified by 3 GPP specifications.

[0074] CLI assistance information 333 can include one or more of configuration of UE-to-UE SRS resource(s) 337A, indication of beam(s) with highest CLI 337B, CLI measurement resource configuration(s) 337C, CLI threshold(s) 337D, and CLI management / handling parameter(s) 337E, among other examples. For example, the configuration of UE-to-UE SRS resource(s) 337A can indicate resources that are configured on one UE to transmit SRS such that the SRS can be measured for CLI by another UE. In some implementations, a first UE in one cell can transmit a UE-to-UE SRS to second UE in a second cell so that the second UE can measure and report CLI measurements. The indication of beam(s) with highest CLI 337B, when included inDocket No. 14730815100PCT the CLI assistance information 333, can enable a network entity to determine which of its transmissions are causing the greatest amount of CLI. Alternatively, the indication of beam(s) with highest CLI 337B can indicate which beams are experiencing the greatest amount of CLI from another network entity The number of beams with strong CLI to be reported from one network entity to another network entity can be specified or it can be indicated by the first network entity or the second network entity. In another example, the beams with CLI above a specified or configured CLI threshold are reported from one network entity to another network entity. The number of beams with strong CLI to be reported and / or the CLI thresholds for beam selection can be adapted depending on varying network conditions and / or resource constraints. The CLI thresholds, serving as the criterion for beam selection and reporting, can be semi- statically or dynamically adjusted based on real-time feedback mechanisms or predefined rules. This adaptability ensures efficient utilization of signaling resources while maintaining a focus on reporting the beams with strong CLI. In some implementations, a network entity can use a relative threshold, focusing on beams whose CLI significantly exceeds the average CLI of all measured beams. For scenarios with limited signaling resources, a network entity can use compressed reporting techniques. For example, instead of reporting individual CLI values for each beam, a network entity can report a delta with respect to the average CLI or with respect to another specified / configured / measured CLI value. The beams CLI reporting can be periodic, aperiodic or semi-persistent. The periodicity of the reporting may be specified or a network entity can configure the periodicity of reporting. In some implementations, the reporting can be event- triggered reporting. For instance, a network entity can report a beam's CLI when the CLI crosses a CLI threshold. In some implementations, a network entity can use a combination of periodic reporting and a threshold criterion, i.e., the beam’s CLI is reported periodically and when it crosses a CLI threshold. To reduce the signaling overhead, a network entity might report only the beam index of the beam with the strong CLI, reducing signaling overhead compared to reporting the full CLI information. In some implementations, instead of directly reporting CLI, the transmitting entity sends recommendations for alternative beams or beam steering commands to the receiving entity. The receiver network entity can use the recommendations to adjust its beam direction based on the transmitter's assessment of the optimal beam.

[0075] As an example, the indication of beam(s) with highest CLI 337B can include an index or identifier of a beam. In some implementations, the indication of beam(s) with highest CLI 337B can include an index or identifier of a reference signal (such as CSI-RS or SSB) or referenceDocket No. 14730815100PCT signal resource (such as a CSI RS indicator value (CRI) or SSB index). For example, a network entity can indicate the strongest beam or the beam with the strongest CLI by including the beam's associated CRI in the CLI management information 330. The CRI is an index ranging from 1 to N where N represents the number of CSI-RS resources within a resource set configured for the network entity. In some implementations, a network entity can indicate the strongest beam or the beam with the strongest CLI using the beam's associated SSB index. The SSB index serves as a unique identifier for each SSB within the set of SSBs configured for the network entity. A network entity can include the CRI or SSB index in a message that includes CLI management information or CLI mitigation information, such as an Xn setup request message, an Xn setup response message, an Xn configuration update messages, an NG-RAN node configuration update message, an Fl setup request, an Fl Setup Response message, and / or an Fl configuration update messages (including a DU configuration update message or a CU configuration update message).

[0076] In some implementations, a network entity can signal the NZP-CSLRS-Resource and / or NZP-CSLRS-ResourceSet in a message that includes CLI management information or CLI mitigation information, such as an Xn setup request message, an Xn setup response message, an Xn configuration update messages, an NG-RAN node configuration update message, an Fl setup request, an Fl Setup Response message, and / or an Fl configuration update messages (including a DU configuration update message or a CU configuration update message).

[0077] In some implementations, a network entity can signal (via any of the example messages for CLI management information or CLI mitigation information) the number N of CSI-RS resources within a set of resources. For example, a network entity can signal the number N of CSI-RS resources in an Xn setup request message, an Xn setup response message, an Xn configuration update messages, an NG-RAN node configuration update message, an Fl setup request, an Fl Setup Response message, and / or an Fl configuration update messages (including a DU configuration update message or a CU configuration update message).

[0078] The CLI measurement resource configuration(s) 337C can indicate CLI measurement configurations to enable measurement or reporting of CLI. In some implementations, the CLI measurement resource configuration(s) 337C are indexed to enable efficient communication of CLI measurement results between network entities. The CLI threshold(s) 337D can indicate what amount of CLI is considered a threshold criterion for initiating CLI mitigation. The CLI management / handling parameter(s) 337E can provide further information, such as mitigation options, policies, or rules for mitigating CLI.Docket No. 14730815100PCT

[0079] FIG. 3B shows a format of an example message (such as a CLI mitigation request message) including example CLI mitigation information 390. The example CLI mitigation information 390 can include one or more of cell ID(s) 391 A, indication of CLI measurement resource(s) for the cell ID(s) 39 IB, CLI measurement result(s) for the CLI measurement resource(s) 391C, indication of radio resources and / or beams 391D, and CLI mitigation parameter(s) 39 IE.

[0080] In some implementations, the indication of CLI measurement resource(s) 39 IB, CLI measurement result(s) 391C, and / or indication of radio resources / beams 391D are associated with the cell ID(s) 391 A. Each of the cell ID(s) indicates a cell. The cell ID might be a cell global identity (CGI) or a physical cell identity (PCI). A network entity that receives the example CLI mitigation information 390 can use the cell ID(s) to determine which cell(s) are associated with the indication of CLI measurement resource(s), CLI measurement result(s), and / or indication of radio resources. Additionally, or alternatively, the network entity can determine which radio resources and / or which beam(s) of the cell(s) to enable or perform CLI mitigation based on the indication of CLI measurement resource(s), CLI measurement result(s), and / or indication of radio resources. The radio resources can indicate time resources and / or frequency resources. For example, the time resources include DL symbols, DL slots, UL symbols and / or UL slots. In another example, the frequency resources include physical resource blocks, subcarriers and / or one or more SBs. Further description of the CLI mitigation information 390 is included with example scenarios described with reference to FIG. 5, FIG. 7, and FIG. 8.

[0081] Next, several example scenarios in which network entities (e.g., the first network entity 104 and the second network entity 106 of FIG. 1A) perform the techniques of this disclosure for managing CLI based on CLI management information and CLI mitigation information are discussed with reference to FIGS. 4A-15. Generally speaking, similar events in the figures are labeled with reference numbers that have the same lower-order digits. For brevity, similar messages or events are not discussed in detail in each instance, but the discussion of a certain event with reference to one of the figures also applies to similar messages or events in other figures. For example, blocks 220, 420A, 420B, 420C, 420, etc., refer to similar concepts such as providing CLI management information as part of or following an interface setup procedure.

[0082] FIG. 4A shows a message flow diagram 400A of a first example setup procedure for communicating CLI management information. The example in FIG. 4A shows that the setup messages of an interface setup procedure 420A between base stations (i.e., where the firstDocket No. 14730815100PCT network entity 104 and the second network entity 106 are gNBs) can include CLI management information. In FIG. 4A, the network entities can include SBFD configuration and CLI assistance information in Xn setup request and response messages. A potential technical advantage of this technique is that CLI-related information is exchanged with fewer messages at the initialization of the Xn interface.

[0083] In FIG. 4A, at block 404, the first network entity 104 is preconfigured with a first TDD DL-UL configuration, a first SBFD configuration, and / or first CLI assistance information. In some implementations, the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI configuration are included for a first cell (e.g., first cell 108 A with reference to FIG. 1A) operated by the first network entity 104. At block 406, the second network entity 106 is preconfigured with a second TDD DL-UL configuration, a second SBFD configuration, and / or second cross-link interference (CLI) assistance information. In some implementations, the second TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI configuration are included for a second cell (e.g., second cell 108B) operated by the second network entity 106.

[0084] The first network entity 104 initiates an Xn setup procedure 420 with the second network entity 106 by transmitting an Xn setup request message 424A to the second network entity 106. In the Xn setup request message 424A, the first network entity 104 includes the first TDD DL- UL configuration, the first SBFD configuration, and / or the first CLI information for CLI mitigation. In the Xn setup request message 424 A, the first network entity 104 can include a cell ID of the first cell that is associated with the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI assistance information. In some implementations, the first TDD DL-UL configuration includes a subcarrier spacing, a cyclic prefix and a TDD DL-UL slot configuration for the first cell. In some implementations, the first SBFD configuration includes SBFD time and frequency configurations such as SBFD UL / DL subbands, SBFD guard-bands, SBFD slots / symbols, one or more SBFD time patterns, and / or a SBFD pattern periodicity for each of the SBFD time pattern(s). In some implementations, the first CLI assistance information includes at least one first measurement resource configuration for CLI measurement. The first measurement resource configuration(s) might configure one or more CLI measurement resources for CLI measurement. For example, the first measurement resource configuration(s) might include one or more configurations of zero power (ZP)Znon-zero power (NZP) channel state information reference signal (CSLRS) resources, one or more CSLRS resource patterns, one orDocket No. 14730815100PCT more synchronization signal / physical broadcast channel (SSB) resource configurations, and / or one or more configurations of cell defining SSB (CD-SSB)ZNon cell defining SSB (NCD-SSB). The first measurement resource configuration(s) might include a measurement resource ID (e.g., index, identifier or identity). In some implementations, the first CLI assistance information includes a first CLI threshold for CLI mitigation.

[0085] In some implementations, the first network entity 104 includes, in the Xn setup request message 424A, a first additional TDD DL-UL configuration, a first additional SBFD configuration, and / or first additional CLI assistance information for a first additional cell operated by the first network entity 104. Examples and implementations for the first TDD DL- UL configuration, the first SBFD configuration, and / or the first CLI assistance information can apply to the first additional TDD DL-UL configuration, the first additional SBFD configuration, and / or the first additional CLI assistance information. The first TDD DL-UL configuration and the first additional TDD DL-UL configuration might be the same or different. The first SBFD configuration and / or the first additional SBFD configuration might be the same or different. The first CLI assistance information or the first CLI assistance information might be the same or different.

[0086] In response to the Xn setup request message 424A, the second network entity 106 transmits an Xn setup response message 426A to the first network entity 104. The second network entity 106 can include the second TDD DL-UL configuration, the second SBFD configuration, and / or the second CLI configuration in the Xn setup response message 426A. In the Xn setup response message 426A, the second network entity 106 can include a cell ID of the second cell that is associated with the second TDD DL-UL configuration, the second SBFD configuration, and / or the second CLI assistance information. In some implementations, the second TDD DL- UL configuration includes a subcarrier spacing, a cyclic prefix and a TDD DL-UL slot configuration for the second cell. In some implementations, the second SBFD configuration includes SBFD time and frequency configurations such as SBFD UL / DL subbands, SBFD guardbands, SBFD slots / symbols, one or more SBFD time patterns, and / or a SBFD pattern periodicity for reach of the SBFD time pattern(s). In some implementations, the second CLI assistance information includes at least one second measurement resource configuration for CLI measurement. The second measurement resource configuration(s) may include one or more configurations ofZP / NZP CSLRS resources, one or more CSLRS resource patterns, one or more SSB resource configurations, and / or one or more configurations of CD-SSB / NCD-SSB. TheDocket No. 14730815100PCT second measurement resource configuration(s) may include a measurement resource ID (e.g., index, identifier or identity). In some implementations, the second CLI assistance information includes a second CLI threshold for CLI mitigation.

[0087] In some implementations, the second TDD DL-UL configuration is different from the first TDD DL-UL configuration. In other implementations, the second TDD DL-UL configuration is the same as the first TDD DL-UL configuration. In some implementations, the first and second SBFD configuration might be the same or different. In some implementations, the first CLI assistance information and the second CLI assistance information might be the same or different.

[0088] FIG. 4A also shows an update procedure (at block 440). The update procedure 440 is used whenever either network entity changes a TDD configuration, SBFD configuration, and / or CLI assistance information. The update procedure is further described with reference to FIG. 4D.

[0089] FIG. 4B shows a message flow diagram 400B of a second example setup procedure 420B for communicating CLI management information. FIG. 4B is generally similar to FIG. 4A except that the messages in the setup procedure 420B differ from those in the setup procedure 420A in FIG. 4A. In FIG. 4B, the network entities can exchange SBFD configuration and CLI assistance information in configuration update messages after Xn setup request and response messages. A potential technical advantage of this technique is that the network entities can determine whether the SBFD configuration and / or CLI assistance information are needed after the Xn setup and response messages are used for initializing the Xn interface.

[0090] In FIG. 4B, the setup procedure 420B includes an Xn Setup Request 424B having the first TDD DL-UL configuration without the first SBFD configuration or first CLI assistance information. Instead, first network entity 104 includes the first SBFD configuration and / or the first CLI assistance information in a configuration update message (shown as NG-RAN node configuration update message 434A). Similarly, the second network entity 106 may include the second TDD DL-UL configuration in the Xn Setup Response message 426B and provide the second SBFD configuration and / or CLI assistance information in a configuration update message (shown as NG-RAN node configuration update (Ack) message 436A).

[0091] FIG. 4C shows a message flow diagram 400C of a third example setup procedure 420C for communicating CLI management information. FIG. 4C is generally similar to FIG. 4A and FIG. 4B, except for the setup procedure. In FIG. 4C, the network entities use legacy Xn setupDocket No. 14730815100PCT messages to establish the Xn interface before exchanging the TDD configuration, the SBFD configuration and CLI assistance information via configuration update messages. A potential technical advantage of this technique is that the network entities can use legacy messaging for initializing the Xn interface.

[0092] In FIG. 4C, the setup procedure 420C includes the first network entity 104 transmitting an Xn Setup Request 424C and the 106 transmitting an Xn Setup Response 426C according to legacy Xn interface setup message formats. After initializing the Xn interface, the first network entity 104 transmits a first NG-RAN node configuration update 434B including the first TDD DL-UL configuration, the first SBFD configuration and / or CLI assistance information. The second network entity 106 transmits an NG-RAN node configuration update acknowledgement message 436B. The second network entity 106 can include the second TDD DL-UL configuration, the second SBFD configuration and / or CLI assistance information in the NG-RAN node configuration update acknowledgement (Ack) message 436B.

[0093] FIG. 4D shows a message flow diagram 400D of an update procedure 440 for updating CLI management information. FIG. 4D is generally similar to FIG. 4A, FIG. 4B, and FIG. 4C with the differences discussed below. FIG. 4D begins with a setup procedure 420, which can be any of the setup procedures 220, 420A, 420B, or 420C described with reference to FIG. 2, 4A, 4B, or 4C.

[0094] After the setup procedure 420, the first network entity 104 makes a change to first TDD DL-UL configuration, first SBFD configuration, and / or first CLI assistance information (shown at block 421). Based on the change, the first network entity 104 initiates an update procedure 440. The first network entity 104 transmits a configuration update message (shown as NG-RAN node configuration update message 444) to the second network entity 106. The NG-RAN node configuration update message 444 can include new configuration(s) or incremental updates to the previous configuration(s). In FIG. 4D, the NG-RAN node configuration update message 444 includes third TDD DL-UL configuration, third SBFD configuration, and / or third CLI assistance information. In some implementations, the first network entity 104 transmits the configuration update message to update (e.g., replace) the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI information for CLI mitigation, respectively. After (e.g., in response to) receiving the third TDD DL-UL configuration, the third SBFD configuration, and / or the third CLI assistance information, the second network entity 106 can enable or perform CLIDocket No. 14730815100PCT mitigation based on the third TDD DL-UL configuration, the third SBFD configuration, and / or the third CLI assistance information, as described above.

[0095] Similarly, the second network entity 106 can transmit an NG-RAN node configuration update acknowledgment message 446 to the first network entity 104. In the acknowledgement (Ack) message 446, the second network entity 106 can include a fourth TDD DL-UL configuration, a fourth SBFD configuration, and / or fourth CLI assistance information. In some implementations, the second network entity 106 might do so to update (e.g., replace) the second TDD DL-UL configuration, the second SBFD configuration, and / or the second CLI information for CLI mitigation, respectively. After (e.g., in response to) receiving the fourth TDD DL-UL configuration, the fourth SBFD configuration, and / or the fourth CLI assistance information, the first network entity 104 can enable or perform CLI mitigation based on the fourth TDD DL-UL configuration, the fourth SBFD configuration, and / or the fourth CLI assistance information, as described above.

[0096] Although FIG. 4D shows the first network entity 104 detects a change and initiates the update procedure 440, it is also possible for the second network entity 106 to detect a change (not shown) and initiate an update procedure. For example, the second network entity 106 can transmit the configuration update message 444 to the first network entity 104, and the first network entity 104 can transmit the configuration update acknowledgment message 446 to the second network entity 106.

[0097] FIG. 5 shows a message flow diagram 500 of CLI mitigation. The first network entity 104 and the second network entity 106 perform an Xn interface setup procedure 420 and / or configuration update procedure 440, as described previously. Based on the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLI assistance information that the second network entity 106 receives from the first network entity 104, the second network entity 106 obtains one or more CLI measurement results for one or more CLI measurement resources of the first network entity 104 as described for FIG. 2. At block 550, the second network entity 106 detects the obtained CLI measurement result(s) is above a first CLI threshold. In response to the detection, the second network entity 106 transmits a CLI mitigation request 564 to the first network entity 104. For example, the CLI mitigation request 564 can include any of the information described with reference to FIG. 3B. In response, the first network entity 104 might transmit a CLI mitigation request acknowledgement 566 message to the second network entity 106. In some implementations, at block 585, the first network entity 104 enables or performs CLIDocket No. 14730815100PCT mitigation based on (e.g., in response to) the CLI mitigation request message. In some implementations, the first network entity 104 transmits the CLI mitigation request acknowledge message if the first network entity 104 accepts the CLI mitigation request message 564. In other implementations, if the first network entity 104 does not accept the CLI mitigation request message 564, the first network entity 104 might transmit a CLI mitigation reject message (not shown) to the second network entity 106. The first network entity 104 might do so because the first network entity 104 needs more capacity to serve UEs in order to meet quality of service (QoS) requirements for the UEs.

[0098] In some implementations, the second network entity 106 includes, in the CLI mitigation request message 564, a resource ID identifying each of the CLI measurement resource(s). In some implementations, the first network entity 104 assigns the resource ID(s) and transmits the resource ID(s) with corresponding measurement resource configuration(s) to the second network entity 106. In some implementations, the second network entity 106 receives the CLI measurement result(s) from one or more UEs as described above. In some implementations, the second network entity 106 receives the resource ID(s) associated with the CLI measurement result(s) from the UE(s). The first network entity 104 determines which radio resources and / or which DL beam(s) of the cell(s) to enable or perform CLI mitigation based on the resource ID(s). In some implementations, the first network entity 104 maintains association information indicating which corresponding radio resources and / or which beam(s) are associated with the resource ID(s). Based on the association information, the first network entity 104 determines radio resources and / or beam(s) of the cell(s) associated with the resource ID(s) and might enable or perform CLI mitigation at block 585 on the determined radio resources and / or beams(s).

[0099] In some implementations, the second network entity 106 includes, in the CLI mitigation request message 564, a report ID identifying each of the CLI measurement result(s). In some implementations, the first network entity 104 assigns the report ID(s) and transmits the report ID(s) with corresponding CLI measurement report configuration(s) to the second network entity 106. The first network entity 104 determines which radio resources and / or which DL beam(s) of the cell(s) to enable or perform CLI mitigation based on the report ID(s). In some implementations, the first network entity 104 maintains association information indicating which respective radio resources and / or which beam(s) are associated with the report ID(s). Based on the association information, the first network entity 104 determines radio resources and / orDocket No. 14730815100PCT beam(s) of the cell(s) associated with the report ID(s) and might enable or perform CLI mitigation on the determined radio resources and / or beams(s) at block 585.

[0100] In some implementations, the second network entity 106 maintains association information indicating which corresponding radio resources and / or which beam(s) are associated with the resource ID(s). Based on the association information, the second network entity 106 determines the first radio resources and / or first beam(s) of the cell(s) associated with the resource ID(s). In yet other implementations, the second network entity 106 maintains association information indicating which corresponding radio resources and / or which beam(s) are associated with the report ID(s). Based on the association information, the second network entity 106 determines the first radio resources and / or first beam(s) of the cell(s) associated with the report ID(s). The first network entity 104 might enable or perform CLI mitigation at block 585 on the first radio resources and / or the first beam(s) as described for FIG. 2.

[0101] After transmitting the CLI mitigation request message 564, the second network entity 106 may continue (at block 558) to obtain one or more CLI measurement results for one or more CLI measurement resources of the first network entity 104 as described above. The second network entity 106 can transmit CLI mitigation results 588 to the first network entity 104 to inform the first network entity 104 whether the CLI has abated or is still present. In some implementations, the CLI mitigation results 588 can included further CLI mitigation information to assist in the CLI mitigation. In some implementations, at block 558, the second network entity 106 detects whether the obtained CLI measurement result(s) is above or below the first CLI threshold. The second network entity 106 may transmit a second CLI mitigation request message when the obtained CLI measurement result(s) is above the first CLI threshold.

[0102] FIG. 6 A shows a message flow diagram 600A in which a distributed base station implements a first example setup procedure 620A similar to FIG. 4A. Referring first to FIG. 6A, a DU 674 is preconfigured with a first TDD DL-UL configuration, a first SBFD configuration, and / or first CLI assistance information (shown at block 604, similar to block 404 of FIG. 4A). The CU 676 might be preconfigured with a second TDD DL-UL configuration, a second SBFD configuration, and / or second cross-link interference (CLI) assistance information (shown at block 606, similar to block 406 of FIG. 4A).

[0103] As part of an Fl interface setup procedure 620A, the DU 674 transmits an Fl Setup Request message 624A to the CU 676. In the Fl Setup Request message 624A, the DU 674 includes the first TDD DL-UL configuration, the first SBFD configuration, and / or the first CLIDocket No. 14730815100PCT information for CLI mitigation. The CU 676 transmits an Fl Setup Response message 626A, optionally including the second TDD DL-UL configuration, the second SBFD configuration, and / or second CLI assistance information.

[0104] In some implementations, the DU 674 and / or the CU 676 can implement a configuration update procedure 640 to exchange updated TDD DL-UL configuration, SBFD configuration or CLI assistance information. For example, the DU 674 can transmit a DU configuration update message 644 to the CU 676. The DU configuration update message 644 includes updated TDD DL-UL configuration, a SBFD configuration, and / or CLI assistance information. Similarly, the CU 676 might transmit a CU configuration update message 646 to the DU 674 to provide its updated TDD / SBFD configuration and CLI assistance information. In addition to describing the network entities as CU 676 and DU 674, FIG. 6A provides an example of the messaging over Fl interface to exchange similar information as described with reference to FIG. 4A and FIG. 4D.

[0105] In FIG. 6A, it is noted that CU 676 might obtain the SBFD configuration for DU 674 (or other DUs) from other network elements or operations, administration, and maintenance (0AM) nodes. Alternatively, the CU 676 may first learn about the DU 674 configuration via the Fl setup request message 624A. While block 606 refers to the second TDD DL-UL configuration, second SBFD configuration, and second CLI assistance information of the CU 676, the CU 676 can also obtain similar information about other DUs (such as neighboring DUs, not shown). The CU 676 can include the SBFD / TDD configuration (e.g., TDD UL-DL configuration, SBFD configuration and / or CLI assistance information) for the other DUs in the Fl Setup Response message 626A and / or the CU configuration update message 646.

[0106] FIG. 6B shows a message flow diagram 600B in which a distributed base station implements a second example setup procedure 620B similar to FIG. 4B. FIG. 6B is generally similar to FIG. 6A (with respect to type of network entities and interface) and FIG. 4B (with respect to the setup procedure). The setup procedure 620B is similar to the setup procedure 420B described with reference to FIG. 4B, except for the names of the messages. The setup procedure 620B includes the DU 674 transmitting an F l setup request message 624B having the first TDD DL-UL configuration and a DU configuration update message 634A having the first SBFD configuration and the CLI assistance information. The CU 676 includes the second TDD DL- UL configuration in the Fl setup response message 626B and includes the second SBFD configuration and second CLI assistance information in the CU configuration update (Ack) message 636A.Docket No. 14730815100PCT

[0107] FIG. 6C shows a message flow diagram 600C in which a distributed base station implements a third example setup procedure 620C similar to FIG. 4C. FIG. 6C is generally similar to FIG. 6A (with respect to type of network entities and interface) and FIG. 4C (with respect to the setup procedure). The setup procedure 620C is similar to the setup procedure 420C described with reference to FIG. 4C, except for the names of the messages. The setup procedure 620C includes the DU 674 transmitting an Fl setup request message 624B not including the first TDD configuration, the first SBFD configuration, and / or first CLI assistance information. Instead, the DU 674 transmits the first TDD configuration, the first SBFD configuration and / or first CLI assistance information via a DU configuration update message 634B. Similarly, the CU 676 includes the second TDD DL-UL configuration, the second SBFD configuration, and the second CLI assistance information via a CU configuration update (Ack) message 636B after the Fl Setup Response message 626C.

[0108] FIG. 7 shows a message flow diagram 700 in which a distributed base station implements CLI mitigation. The DU 674 and the CU 676 perform an Fl interface setup procedure 620 (such as setup procedures 620A, 620B, or 620C) and / or node configuration update procedure 640 as described above. FIG. 7 describes the CLI mitigation that might occur exchanging the TDD / SBFD configuration and CLI assistance information.

[0109] The DU 674 obtains one or more CLI measurement results for one or more CLI measurement resources of the CU 676 (or a neighbor DU). At block 750, the DU 674 detects the obtained CLI measurement result(s) is above a CLI threshold. In response to the detection, the DU 674 transmits a CLI mitigation request message 764 to the CU 676. The CLI mitigation request message 764 can include information similar to the CLI mitigation request message 564 (of FIG. 5) or example CLI mitigation information 390 (of FIG. 3B). For brevity, the example information is omitted from the description of FIG. 7. In response, the CU 676 might transmit a CLI mitigation request acknowledgement message 766 to the DU 674. In some implementations, at block 785, the CU 676 enables or performs CLI mitigation based on (e.g., in response to) the CLI mitigation request message 764. At block 758, the DU 674 can obtain CLI measurement results of CLI measurement resources (such as by direct measurement or by obtaining CLI measurement results from a UE in the first cell of the DU 674). In some implementations, the DU 674 transmits CLI mitigation results 788 and / or further CLI mitigation request message(s) (not shown). The operations at events 785, 758, 788 can include any of the CLI mitigationDocket No. 14730815100PCT techniques described in this disclosure, such as those described with reference events 585, 558, and 588 of FIG. 5 or the measurement / mitigation techniques described with reference to Fig. 2.

[0110] FIG. 8 shows a message flow diagram 800 of a distributed base station coordinating CLI mitigation with one or more other RAN nodes. FIG. 8 shows a scenario that is generally similar to the CLI mitigation described with reference to FIG. 7. In the example of FIG. 8, at block 863, the CU 676 receives a CLI mitigation request from one or more other RAN node(s) (such as network entities, base stations, or DUs) that indicate CLI being caused by the DU 674. The CU 676 transmits to the DU 674 a CLI mitigation request message 864 including at least a portion of the CLI mitigation request from the other RAN node(s). A CLI mitigation request message 864 may include cell ID(s), indication of CLI measurement resources for the cell ID(s), CLI measurement result(s) for the CLI measurement resources and / or indication of radio resources and / or beams. The DU 674 may respond to the CLI mitigation request message 864 with a CLI mitigation request acknowledgment message 866. The CLI mitigation request acknowledgement message 866 and CLI mitigation at block 885 are similar to corresponding messages 566, 766 and blocks 585, 785 and the description is omitted for brevity.

[0111] FIG. 9 shows a flow diagram of example operations 900 of a first network entity providing CLI management information to a second network entity. At block 920 the first network entity performs an interface setup procedure to set up an interface connection with a second network entity. At block 940, the first network entity may perform a configuration update procedure with the second network entity to update configuration data. At block 924, the first network entity transmits CLI management information (e.g., (first TDD DL-UL configuration, first SBFD configuration, and / or first CLI assistance information} 1, ... , N for CLI mitigation to the second network entity, where N is an integer greater than zero). At block 944, the first network entity may transmit updated CLI management information (e.g., {new TDD DL-UL configuration, new SBFD configuration, and / or new CLI assistance information} 1, ... , M for CLI management to the second network entity, where M is an integer greater than zero).

[0112] FIG. 10 shows a flow diagram of example operations 1000 of a first network entity performing CLI mitigation based on CLI management information from a second network entity. The operations 1000 of FIG. 10 are generally similar to the operations 900 of FIG. 9 with the differences discussed below. At block 1026, the first network entity receives CLI management information (e.g., (TDD DL-UL configuration, SBFD configuration, and / or CLI assistance information} 1, . . ., K for CLI management from the second network entity, where K is an integerDocket No. 14730815100PCT greater than zero). At block 1085 the first network entity performs CLI mitigation based on the CLI management information.

[0113] FIG. 11 shows a flow diagram of example operations 1100 of a first network entity managing CLI measurements based on CLI management information from a second network entity. At block 1104, the first network entity operates a first cell with a first TDD UL-DL configuration and a first SBFD configuration. At block 1126, the first network entity receives, from a second network entity, a second TDD DL-UL configuration, second SBFD configuration, and / or CLI assistance information about a second cell of the second network entity.

[0114] At block 1152, the first network entity determines a CLI measurement resource configuration based on the first TDD UL-DL configuration, the first SBFD configuration, the second DL-UL configuration, the second SBFD configuration, and / or the CLI assistance information. At block 1 156, the first network entity may transmit the CLI measurement resource configuration to one or more UEs. At block 1158, the first network entity obtains CLI measurement results of one or more DL symbols, one or more UL symbols, SBFD symbols, and / or one or more SRSs associated with the CLI measurement configuration (obtained by CLI measurements at the network entity or from measurement results received from the one or more UEs).

[0115] At block 1159, the first network entity determines whether or not a CLI is above a threshold based on the CLI measurement results. If the first network entity determines the CLI is not above a threshold based on the CLI measurement results, the flow proceeds to block 1158, and the first network entity obtains CLI measurement results of one or more DL symbols, one or more UL symbols, SBFD symbols, and / or one or more SRSs associated with the CLI measurement configuration as stated above. If, at block 1159, the first network entity determines the CLI is above a threshold based on CLI measurement results, the flow proceeds to block 1164, and the first network entity transmits a CLI mitigation request to the second network entity.

[0116] FIG. 12A shows a flow diagram of example operations 1200A of a first network entity enabling CLI mitigation based on CLI mitigation request(s) from one or more other network entities. At block 1264, the first network entity receives a first CLI mitigation request from a second network entity requesting enabling CLI mitigation on at least one first radio resource and / or at least one first beam of a first cell operated by the first network entity. At block 1285, the first network entity enables CLI mitigation on the at least one first radio resource and / or the at least one first beam of the first cell.Docket No. 14730815100PCT

[0117] In some implementations, at block 1264(2), the first network entity may receive a second CLI mitigation request from a third network entity, requesting CLI mitigation on at least one second radio resource and / or at least one second beam of a second cell operated by the first network entity. At block 1285(2), the first network entity may enable CLI mitigation on the at least one second radio resource and / or the at least one second beam of the second cell. In some implementations, the CLI mitigation is based on an aggregation of CLI mitigation requests from multiple network entities. Alternatively, or additionally, the first network entity can perform CLI mitigation based on a CLI mitigation request that indicates the highest amount of CLI.

[0118] FIG. 12B shows a flow diagram of example operations 1200B of a first network entity enabling and disabling CLI mitigation based on CLI mitigation request(s) from a second network entity. Operations 1200B begin similarly to operations 1200A with blocks 1264 and 1285.

[0119] In some implementations, at block 1288, the first network entity may receive a second CLI mitigation request from the second network entity, requesting to disable CLI mitigation on (at least a portion of) the at least one first radio resource and / or (at least a portion of) the first cell. At block 1289, the first network entity may disable the CLI mitigation in response to the second CLI mitigation request.

[0120] FIG. 13 shows a flow diagram of example operations 1300 of a first network entity selectively accepting or rejecting a CLI mitigation request from a second network entity. At block 1364, the first network entity receives a CLI mitigation request from a second network entity. At decision block 1365, the first network entity determines whether or not to accept the CLI mitigation request. If the first network entity determines not to accept the CLI mitigation request, the flow proceeds to block 1387, and the first network entity transmits a CLI mitigation reject to the second network entity. If the first network entity does determine to accept the CLI mitigation request, the flow proceeds to block 1366, and the first network entity transmits a CLI mitigation request acknowledgement message to the second network entity.

[0121] FIG. 14 is a block diagram of example distributed or disaggregated implementation of an example base station (BS 1406) using a central unit (CU 1406A) and a distributed unit (DU(s) 1404). In this implementation, the BS 1406 includes a CU 1406A and one or more distributed units (DU(s) 1404). The CU 1406A includes processing hardware, such as one or more general- purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processor(s), and / or special-purpose processing units. For example, the CU 1406A can include a PDCP controller, an RRC controller and / or anDocket No. 14730815100PCTRRC inactive controller. In some implementations, the CU 1406A can include a radio link control (RLC) controller configured to manage or control one or more RLC operations or procedures. In further implementations, the CU 1406A does not include an RLC controller.

[0122] Each of the DU(s) 1404 also includes processing hardware that can include one or more general -purpose processors (e.g., CPUs) and computer-readable memory storing machine- readable instructions executable on the one or more general-purpose processors, and / or specialpurpose processing units. For example, the processing hardware can include a MAC controller configured to manage or control one or more MAC operations or procedures (e.g., a random access procedure), and / or an RLC controller configured to manage or control one or more RLC operations or procedures. The process hardware can also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0123] In some implementations, a RAN (supports Integrated Access and Backhaul (IAB) functionality. In some implementations, the DU(s) 1404 operates as an lAB-node, and the CU 1406A operates as an lAB-donor.

[0124] In some implementations, the CU 1406A can include a logical node CU control plane (CU-CP(s) 1407A) that hosts the control plane part of the PDCP protocol of the CU 1406A. The CU 1406A can also include logical node(s) referred to as a CU user plane (CU-UP(s) 1407B) that hosts the user plane part of the PDCP protocol and / or Service Data Adaptation Protocol (SDAP) protocol of the CU 1406A. The CU-CP(s) 1407A can transmit control information (e.g., RRC messages, Fl application protocol messages), and the CU-UP(s) 1407B can transmit the data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0125] The CU-CP(s) 1407A can be connected to multiple CU-UP(s) 1407B through the El interface. The CU-CP(s) 1407A selects the appropriate CU-UP(s) 1407B for the requested services for the UE (such as UE 102). In some implementations, a single CU-UP(s) 1407B can connect to multiple CU-CP(s) 1407A through the El interface. The CU-CP(s) 1407A can connect to one or more DU(s) 1404 through an Fl-C interface. The CU-UP(s) 1407B can connect to one or more DU(s) 1404 through the Fl-U interface under the control of the same CU-CP(s) 1407A. In some implementations, one of the DU(s) 1404 can connect to multiple CU-UP(s) 1407B under the control of the same CU-CP(s) 1407A. In such implementations, the connectivity between a CU-UP(s) 1407B and one of the DU(s) 1404 is established by the CU-CP(s) 1407A using Bearer Context Management functions.Docket No. 14730815100PCT

[0126] The CU-CP(s) 1407A generates the carrier frequency configurations (such as frequency and timing information) in the system information messages (such as SIB2 or SIB4) and provides the system information messages to the DU(s) 1404. The DU(s) 1404 passes these SIBs to lower layers (such as a physical layer (PHY), baseband unit (BBU) or radio head unit (RRH)) for a broadcast transmission.

[0127] FIG. 15 shows a message flow diagram 1500 with some potential variations for managing CLI with TDD / SBD operation. FIG. 15 shows an intermediary node 1507 in addition to a first network entity 104 and a second network entity 106. In some implementations, the setup procedure 220 and update procedure 240 can include communication through the intermediary node 1507 (such as a core network function, another network element, or another RAN node). For example, an interface between the first network entity 104 and the second network entity 106 can include an interface 1505 A between the first network entity 104 and the intermediary node 1507 and another interface 1505B between the intermediary node 1507 and the second network entity 106.

[0128] In some implementations, the second network entity 106 transmits setup or update messages containing CLI management information 130 to intermediary node 1507. The intermediary node 1507 transmits at least a portion of the CLI management information 130 to the first network entity 104.

[0129] At block 1552, the first network entity 104 determines a CLI measurement configuration based on the CLI management information. The first network entity 104 transmits a CLI measurement configuration message 1556 (or a CLI measurement report configuration message) to a UE 102. The UE 102 performs measurements of a CLI measurement resource based on the CLI measurement configuration. In some implementations, the UE 102 transmits CLI measurement results to the first network entity 104. Alternatively, or additionally, the UE 102 transmits a CLI mitigation information message 1558 to the first network entity 104, where the CLI mitigation information message 1558 is based on the CLI measurement results. In some implementations, the CLI mitigation information includes measurement results, CLI handling parameters, a threshold, or other parameters. The first network entity 104 can prompt CLI mitigation at the second network entity 106 using a CLI mitigation request message 264. In some implementations, the first network entity 104 receives a CLI mitigation request acknowledgement message 266 in response to the CLI mitigation request message 264. In some implementations, the CLI mitigation request and acknowledgement messages (e.g., the CLIDocket No. 14730815100PCT mitigation request message 264 and the CLI mitigation request acknowledgement message 266) are communicated via an intermediary node 1507 - which may be the same intermediary node 1507 used for the setup procedure and update procedure, or may be a different intermediary node.

[0130] FIG. 16 shows a block diagram illustrating example configurations of a network entity 1604 and a UE 1602. Note that the depicted hardware configurations represent the processing components and communication components of a network entity 1604. Network entity 1604 may be an implementation of the first network entity 104 or second network entity 106 of FIG. 1A or DU 674 or CU 676 of FIG. 6A. The UE 1602 may be an implementation of the first UE 102A, second UE 102B, or third UE 102C of FIG. 1A. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like.

[0131] The UE 1602 includes antennas 1603 A, a radio frequency front end (RF front end 1603B), and radio-frequency transceivers (e.g., an LTE transceiver 1603D and a 5G NR transceiver 1603C) for communicating with the network entity 1604. The RF front end 1603B includes one or more modems configured for the corresponding RAT(s) employed (for example, 3GPP 5G NR), one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), signal processors, and the like. In the example illustrated in FIG. 16, the RF front end 1603B of the UE 1602 may couple or connect the 5G NR transceiver 1603C to the antennas 1603 A to facilitate various types of wireless communication. The RF front end 1603B operates, in effect, as a physical (PHY) transceiver interface to conduct and process signaling between the one or more processor(s) 1603E and antennas 1603 A so as to facilitate various types of wireless communication.

[0132] The antennas 1603 A of the UE 1602 include an array of multiple antennas that may be tuned to one or more frequency bands associated with a corresponding RAT. The antennas 1603 A and the RF front end 1603B are tuned to, and / or be tunable to, one or more frequency bands defined by the 3GPP 5G NR communication standards and implemented by the 5G NR transceiver 1603C. Additionally, the antennas 1603 A, the RF front end 1603B, and / or the 5G NR transceiver 1603C can be configured to support beamforming for the transmission and reception of communications with the network entity 1604. By way of example and not limitation, the antennas 1603 A and the RF front end 1603B may be implemented for operation in sub-gigahertz bands, sub-6 GHz bands, and / or above 6 GHz bands that are defined by the 3 GPP LTE and 5G NR communication standards.Docket No. 14730815100PCT

[0133] The UE 1602 also includes processor(s) 1603E and computer-readable storage media (CRM 1603F). The processor(s) 1603E may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 1603E may include an application processor (AP) utilized by the UE 1602 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 1603B. The CRM 1603F may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), nonvolatile RAM (NVRAM), read-only memory (ROM), Flash memory, solid-state drive (SSD) or other mass-storage devices, and the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processor(s) 1603E and other components of the UE 1602 to perform the various functions described herein and attributed to the UE 1602. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 1603E to enable user-plane communication, control-plane signaling, and user interaction with the UE 1602.

[0134] The processor(s) 1603E along with other processors of the UE 1602 that are used to implement the techniques described herein may be individually or collectively referred to as “a processing system.” One or more of RF front end 1603B, 5G NR transceiver 1603C, and LTE transceiver 1603D may be individually or collectively referred to as a “communication unit.”

[0135] Turning to the hardware of the network entity 1604, it is noted that although FIG. 16 illustrates an implementation of the network entity 1604 as a single network node (for example, a 5G NR Node B, or “gNB”), the functionality, and thus the hardware components, of the network entity 1604 instead may be distributed across multiple network nodes or devices and may be distributed in a manner to perform the functions described herein. As one example, the functionality of network entity 1604 may be distributed across a radio unit (RU), distributed unit (DU), or central unit (CU).

[0136] The network entity 1604 includes antennas 1607A, a radio frequency front end (RF front end 1607B), and one or more 5G NR transceiver(s) 1607C for communicating with the UE 1602. The RF front end 1607B of the network entity 1604 may couple or connect the 5G NR transceiver(s) 1607C to the antennas 1607A to facilitate various types of wireless communication. Similar to RF front end 1603B, the RF front end 1607B includes one or moreDocket No. 14730815100PCT modems, one or more ADCs, one or more DACs, and the like. RF front end 1607B receives the one or more RF signals, for example, RF signals from UE 1602, and pre-processes the one or more RF signals to generate data from the RF signals that is provided as input to processes and / or applications executing on network entity 1604. This pre-processing may include, for example, power amplification, conversion of band-pass signaling to baseband signaling, initial analog-to- digital conversion, and the like.

[0137] The antennas 1607A of the network entity 1604 may be configured individually and / or as one or more arrays of multiple antennas. The antennas 1607A and the RF front end 1603B may be tuned to, and / or be tunable to, one or more frequency band defined by the 3GPP 5G NR communication standards and implemented by the 5G NR transceiver(s) 1607C. Additionally, the antennas 1607A, the RF front end 1607B, and the 5G NR transceiver(s) 1607C may be configured to support beamforming, such as Massive-MIMO, for the transmission and reception of communications with the UE 1602.

[0138] The network entity 1604 also includes processor(s) 1607D and computer-readable storage media (CRM 1607E). The processor(s) 1607D may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 1607D may include an application processor (AP) utilized by the network entity 1604 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 1607B to enable communication with the UE 1602. In at least some aspects, the processor(s) 1607D configures the 5G NR transceiver(s) 1607C for communication with the UE 1602, TRPs, and radio units via fronthaul interface 1609, as well as communication with a core network. In some aspects, the network entity 1604 includes an inter-network entity interface 1605, such as an Xn and / or X2 interface, which the processor(s) 1607D configures to exchange user-plane and control-plane data with another network entity, to manage the communication of the network entity 1604 with the UE 1602. The network entity 1604 includes a core network interface 1610 that the processor(s) 1607D configures to exchange user-plane and control-plane data with core network functions and entities.

[0139] The processor(s) 1607D along with other processors of the network entity 1604 that are used to implement the techniques described herein may be individually or collectively referred to as “a processing system.” One or more of RF front end 1607B, 5G NR transceiver(s) 1607C,Docket No. 14730815100PCT fronthaul interface 1609, inter-network entity interface 1605, and core network interface 1610 may be individually or collectively referred to as a “communication unit.”

[0140] FIG. 17 shows a block diagram of an example wireless communication system 1700 showing hardware features and communication interfaces. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like. The example wireless communication system 1700 includes the same elements as described with reference to FIG. 1A, including the UE 102, the first network entity 104, the second network entity 106 and the core network 110. In some implementations, the UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the first network entity 104. The first network entity 104 connects to the core network 110 via an interface (e.g., SI or NG interface). The first network entity 104 can connect to other base stations (including the second network entity 106) via an interface (e g., X2 or Xn interface) for interconnecting NG RAN nodes. In FIG. 17, the second network entity 106 operates a terrestrial network (TN) second cell 108B.

[0141] The first network entity 104 is equipped with processing hardware 1704 that can include a receiver 1707B configured to receive data in the uplink direction. The processing hardware 1704 can also include a transmitter 1707A configured to transmit data in the downlink direction. The processing hardware further can one or more general-purpose processor(s) 1707C (e.g., CPUs) and a non-transitory computer-readable memory (CRM 1707D) storing instructions that the one or more general-purpose processors execute. Additionally, or alternatively, the processing hardware 1704 can include special -purpose processing units. The processor 1707C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs), and the like. CRM 1707D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory usable to store device data of the first network entity 104.

[0142] The UE 102 is equipped with processing hardware 1702 that can include one or more general -purpose processors such as CPUs and non-transitory computer-readable memory 1703D storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The processing hardware 1702 can also include a transmitter 1703 A configured to transmit data in the uplink direction. The processing hardware further can include a receiver 1703B configured to receive data in the downlink direction. TheDocket No. 14730815100PCT processing hardware 1702, in an example implementation, includes a processor 1703C to process data that the UE 102 will transmit in the uplink direction or process data received by UE 102 in the downlink direction. The processor(s) 1703C may include, for example, one or more central processing units, GPUs, or other ASICs, and the like. To illustrate, the processor(s) 1703C may include an application processor (AP) utilized by the UE 102 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor. The CRM 1703D may include any suitable memory or storage device such as RAM, SRAM, DRAM, NVRAM, ROM, Flash memory, SSD or other mass-storage devices, and the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processor(s) 1703C and other components of the processing hardware 1702 to perform the various functions described herein and attributed to the UE 102. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 1703C to enable user-plane communication, control-plane signaling, and user interaction with the UE 102.

[0143] The core network 110 can be an Evolved Packet Core (EPC) and / or a 5G core (5GC). Among other components, the EPC can include a Serving Gateway (SGW), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), and a Packet Data Network Gateway (PGW). The SGW in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME is configured to manage authentication, registration, paging, and other related functions. The PGW provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC includes a User Plane Function (UPF), a Unified Data Management (UDM), an Access and Mobility Management Function (AMF), and / or Session Management Function (SMF). Generally speaking, the UPF is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF is configured to manage authentication, registration, paging, and other related functions, and the SMF is configured to manage PDU sessions. The HSS and the UDM store and maintain subscription information regarding the UE 102. The core network 110 can be implemented by one or more processing elements (shown as processing hardware 1710). The processing hardware 1710 can include a transmitter 1711A, a receiver 171 IB, a processor 1711C,Docket No. 14730815100PCT and a CRM 171 ID, similar to corresponding components described with reference to processing hardware 1702 and 1704.

[0144] The transmitters 1703A, 1707A, and 1711A and receivers 1703B, 1707B, and 171 IB are examples of a communication unit. The processors 1703C, 1707C, and 1711C can also be referred to as a processing system. Other examples of a communication unit and a processing system are possible, including some examples that are commonly used in a wireless communication system. The first network entity 104, UE 102, second network entity 106, and core network 110 can include other components not illustrated in FIG. 17. Similarly, the UE 102 can include a system information interpretation unit capable of interpreting any of the example system information described in this disclosure. The UE 102 can also include an RRC management unit that can operate an RRC INACTIVE or RRC SUSPENDED based on information from the second network entity 106 to transition to an RRC suspended state. The system information interpretation unit and / or the RRC management unit can be implemented by a processing system and communication unit of the UE 102.

[0145] FIG. 1 A through FIG. 17 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims, some implementations may perform additional operations, fewer operations, operations in parallel or in a different order, and some operations differently.

[0146] Aspects of the subject matter described in this disclosure can be implemented as a computer-readable medium having stored therein instructions which, when executed by a processor, causes the processor to perform any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as a system having means for implementing any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as an apparatus having one or more processors configured to perform one or more operations from the following functionalities (enumerated as clauses for clarity).

[0147] Clause 1 : A method for wireless communication by a first network entity (104), comprising: operating a first cell with a first time division duplex (TDD) downlink (DL)-uplink (UL) configuration and a first subband full duplex (SBFD) configuration; transmitting, to a second network entity (106), first cross-link interference (CLI) management information (130, 330), the first CLI management information including at least one of: the first TDD DL-ULDocket No. 14730815100PCT configuration, the first SBFD configuration, or first CLI assistance information; and receiving, from the second network entity (106), second CLI management information (130, 330), the second CLI management information including at least one of a second TDD DL-UL configuration of a second cell, a second SBFD configuration of the second cell, or second CLI assistance information.

[0148] Clause 2: The method of clause 1, further comprising: setting up an interface between the first network entity and the second network entity; and communicating the first CLI management information and the second CLI management information via the interface.

[0149] Clause 3: The method of clause 1 or 2, wherein the transmitting the first CLI management information includes transmitting the first CLI management information via an Xn Setup Request message or an Fl Setup Request message as part of an interface setup procedure; and wherein the receiving the second CLI management information includes receiving the second CLI management information via an Xn Setup Response message or an Fl Setup Response as part of the interface setup procedure.

[0150] Clause 4: The method of clause 1 or 2, wherein the transmitting the first CLI management information includes: transmitting a first portion of the first CLI management information via a setup request message; and transmitting a second portion of the first CLI management information via a configuration update message update after the setup request message.

[0151] Clause 5: The method of clause 4, wherein the configuration update message is a next generation (NG)-radio access network (RAN) node configuration update message formatted to include at least the first SBFD configuration or the first CLI assistance information.

[0152] Clause 6: The method of clause 1 or 2, wherein the transmitting the first CLI management information includes: transmitting a setup request message as part of an interface setup procedure, wherein the setup request message does not include the first CLI management information; and transmitting the first CLI management information via a configuration update message update after the setup request message.

[0153] Clause 7: The method of any one of clauses 1 to 6, further comprising, after the transmitting the first CLI management information: transmitting, to the second network entity, updated CLI management information via a configuration update message to update at least a portion of the first CLI management information.Docket No. 14730815100PCT

[0154] Clause 8: The method of any one of clauses 1 to 7, further comprising: receiving, from the second network entity, a first CLI mitigation request that includes CLI mitigation information, wherein the CLI mitigation information includes at least one of: an identification of the first cell, an indication of one or more CLI measurements resources of the first cell, CLI measurement result for the one or more CLI measurement resources of the first cell, an identification of radio resources or beams of the first cell causing CLI, a channel state information reference signal (CSI-RS) resource indicator (CRI) identifying a CSI-RS associated with a first beam of the first cell having the strongest signal or causing the strongest CLI; a synchronization signal block resource indicators (SSBRI) associated with an SSB of the first beam; an SSB index associated with the SSB of the first beam; or one or more CLI mitigation parameters.

[0155] Clause 9: The method of clause 8, further comprising: determining whether to accept the first CLI mitigation request; and transmitting a CLI mitigation request acknowledgement message if the CLI mitigation request is accepted; and transmitting a CLI mitigation rejection message if the CLI mitigation request is not accepted.

[0156] Clause 10: The method of clause 8 or 9, further comprising: enabling CLI mitigation based on the first CLI mitigation request and the CLI mitigation information.

[0157] Clause 11 : The method of any one of clauses 8 to 10, further comprising: receiving, from the second network entity, a second CLI mitigation request that indicates CLI has abated; and disabling the CLI mitigation based on the second CLI mitigation request.

[0158] Clause 12: The method of any one of clauses 1 to 11, further comprising: receiving, from one or more network entities, CLI mitigation requests associated with a plurality of cells of the first network entity; and enabling CLI mitigation on one or more cells of the plurality of cells based on the CLI mitigation requests.

[0159] Clause 13 : The method of any one of clauses 1 to 7, further comprising: determining a CLI measurement resource configuration based on the first CLI management information and the second CLI management information; obtaining a CLI measurement result based on the CLI measurement resource configuration; and transmitting, to the second network entity, a first CLI mitigation request when the CLI measurement result is above a CLI threshold.

[0160] Clause 14: The method of clause 13, wherein the obtaining the CLI measurement result includes: transmitting, to a user equipment (UE) in the first cell, a CLI measurement configuration based on the CLI measurement resource configuration; and receiving, from the UE, the CLI measurement result.Docket No. 14730815100PCT

[0161] Clause 15 : The method of clause 13, wherein the obtaining the CLI measurement result includes: measuring, at the first network entity, a resource of the second cell based on the CLI measurement resource configuration.

[0162] Clause 16: The method of any one of clauses 1 to 7, further comprising: receiving, from a third network entity, a CLI mitigation request associated with the second cell of the second network entity; and transmitting, to the second network entity, at least a portion of the CLI mitigation request.

[0163] Clause 17: The method of any one of clauses 1 to 16, further comprising: managing CLI between the first cell and the second cell based on the first CLI management information and the second CLI management information, wherein the managing the CLI includes at least one of: adjusting the first TDD DL-UL configuration or the first SBFD configuration based on the second CLI management information; reducing a power level of at least one resource of the first cell based on the second CLI assistance information; or coordinating a CLI measurement resource configuration of a user equipment (UE) in the first cell to monitor the CLI.

[0164] Clause 18: The method of any one of clauses 1 to 17, wherein the second CLI assistance information includes at least one of: a resource configuration of a user equipment (UE)-to-UE sounding reference signal (SRS) for CLI measurement; an indication of one or more beams with CLI; a CLI measurement resource configuration; a CLI threshold; one or more CLI management parameters; or one or more CLI handling parameters.

[0165] Clause 19: The method of any one of clauses 1 to 18, wherein the first network entity is a first next generation base station (gNb) and the second network entity is a second gNb.

[0166] Clause 20: The method of any one of clauses 1 to 18, wherein the first network entity is a distributed unit (DU) of a base station and the second network entity is a central unit (CU) of the base station.

[0167] Clause 21 : The method of any one of clauses 1 to 20, wherein at least one of the first CLI management information or the second CLI management information includes at least one of: a channel state information reference signal (CSLRS) resource indicator (CRI) identifying a CSI-RS associated with a first beam of the first cell having the strongest signal or causing the strongest CLI; a synchronization signal block resource indicators (SSBRI) associated with an SSB of the first beam; or an SSB index associated with the SSB of the first beam; a non-zero power ( NZP) CSI-RS-Resource; or an NZP-CSI-RS-ResourceSet.Docket No. 14730815100PCT

[0168] Clause 22: A method for wireless communication by a second network entity (106), comprising: receiving, from a first network entity (104), first cross-link interference (CLI) management information (130, 330), the first CLI management information including at least one of: a first time division duplex (TDD) downlink (DL)-uplink (UL) configuration of a first cell, a first subband full duplex (SBFD) configuration of the first cell, or first CLI assistance information; operating, by the second network entity (106), a second cell with a second TDD DL-UL configuration and a second SBFD configuration; and transmitting, to the first network entity (104), second CLI management information, the second CLI management information including at least one of: the second TDD DL-UL configuration, the second SBFD configuration, or second CLI assistance information.

[0169] Clause 23 : The method of clause 22, further comprising: setting up an interface between the first network entity and the second network entity; and communicating the first CLI management information and the second CLI management information via the interface, wherein the communicating the first CLI management information and the second CLI management information includes at least one of: receiving the first CLI management information via an Xn Setup Request message or an Fl Setup Request message as part of an interface setup procedure; transmitting the second CLI management information via an Xn Setup Response message or an Fl Setup Response as part of the interface setup procedure; receiving a first portion of the first CLI management information via a setup request message; receiving a second portion of the first CLI management information via a configuration update message update after the setup request message; transmitting, to the first network entity, updated CLI management information via a configuration update message to update at least a portion of the second CLI management information; or receiving, from the first network entity, updated CLI management information that updates at least a portion of the first CLI management information.

[0170] Clause 24: The method of clause 22 or 23, further comprising: determining a CLI measurement resource configuration based on the first CLI management information and the second CLI management information; obtaining, by the second network entity or from a user equipment in the second cell, a CLI measurement result based on the CLI measurement resource configuration; and transmitting, to the first network entity, a CLI mitigation request when the CLI measurement result is above a CLI threshold, the CLI mitigation request including at least one of: an identification of the first cell or the second cell, an indication of one or more CLI measurements resources of the first cell, CLI measurement result for the one or more CLIDocket No. 14730815100PCT measurement resources of the first cell, an identification of radio resources or beams of the first cell causing CLI, or one or more CLI mitigation parameters.

[0171] Clause 25: The method of clause 24, further comprising: detect that CLI of the second cell has abated after the CLI mitigation request; and transmitting, to the first network entity, an indication that the CLI has abated.

[0172] Clause 26: The method of any one of clauses 22 to 25, wherein the first network entity is a first next generation base station (gNb) or distributed unit (DU) of a base station; and wherein and the second network entity is a second gNb or a central unit (CU) of the base station.

[0173] Clause 27: An apparatus, comprising: a communication unit; and a processing system configured to control the communication unit to implement any one of the methods of any one of clauses 1 to 26.

[0174] The following additional considerations may apply to the foregoing and the following discussions. Generally speaking, description for one of the above figures can apply to another of the above figures. Any event or block described above can be optional. For example, an event or block with dashed lines can be optional. In some implementations, “message” is used and can be replaced by “information element (IE),” and vice versa. In some implementations, “IE” is used and can be replaced by “field,” and vice versa. In some implementations, “subband” can be replaced with “sub-band.” In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters,” and vice versa. In some implementations, “some” means “one or more.” In some implementations, “at least one” means “one or more.” The “eNB” can be replaced by “base station,” “gNB,” “6G base station,” “evolved gNB,” or 6G gNB. “MME” can be replaced by AMF or evolved AMF or 6G AMF. “Core network (CN)” can be replaced by EPC, 5GC or 6GC.

[0175] Some examples of this disclosure refer to RRC messages for illustrative purposes. In the various figures and descriptions, some RRC messages can be replaced by other examples. For example, “RRC Connection Request message” can be replaced by “RRC Setup Request message.” “RRC Connection Setup message” can be replaced by “RRC Setup message.” “RRC Connection Setup Complete message” can be replaced by “RRC Setup Complete message.” “RRC Connection Reconfiguration message” can be replaced by “RRC Reconfiguration message.” “RRC Connection Reestablishment Request message” can be replaced by “RRC Reestablishment Request message.” “RRC Connection Reestablishment message” can be replaced by “RRC Reestablishment message.” “RRC Connection Reestablishment CompleteDocket No. 14730815100PCT message” can be replaced by “RRC Reestablishment Complete message.” “RRC Connection Resume Request message” can be replaced by “RRC Resume Request message.” “RRC Connection Resume message” can be replaced by “RRC Resume message.” “RRC Connection Resume Complete message” can be replaced by “RRC Resume Complete message.” “NAS Attach Request message” or “TAU Request message” can be replaced by “Registration Request message.” “NAS Attach Accept message” or “TAU Accept message” can be replaced by “Registration Accept message.”

[0176] Unless defined otherwise, technical and scientific terms used herein have the same meaning as is commonly understood by one of ordinary skill in the art to which this specification belongs. The terms “first,” “second,” and the like, as used herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The use of terms “including,” “comprising” or “having” and variations thereof herein are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “connected” and “coupled” are not restricted to physical or mechanical connections or couplings and can include electrical connections or couplings, whether direct or indirect. Furthermore, terms “circuit” and “circuitry” and “control unit” may include either a single component or a plurality of components, which are either active and / or passive and are connected or otherwise coupled together to provide the described function. In addition, the term operationally coupled as used herein includes wired coupling, wireless coupling, electrical coupling, magnetic coupling, radio communication, software based communication, or combinations thereof.

[0177] Some or all of the foregoing or the following implementations can be jointly combined or formed to be a new or another one implementation. The foregoing or the following techniques can be used to solve at least (but not limited to) the issue(s) or scenario(s) mentioned in this disclosure. Any two or more than two of the foregoing or the following paragraphs, (sub)-bullets, points, actions, or claims described in each method / technique / implementation may be combined logically, reasonably, and properly to form a specific method. Any sentence, paragraph, (sub)- bullet, point, action, or claim described in each of the foregoing or the following technique(s) / implementation(s) / concept(s) may be implemented independently and separately to form a specific method. Dependency, such as “based on,” “more specifically,” “where” or etc., in technique(s) / implementation(s) / concept(s) mentioned in this disclosure is just one possible implementation which would not restrict the specific method.Docket No. 14730815100PCT

[0178] As used herein, the terms “user device”, “user equipment” (for example, UE 102), “wireless communication device”, “mobile communication device”, “communication device”, or “mobile device” refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, Internet-of-Things (loT) devices, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, display sub-systems, driver assistance systems, vehicle controllers, vehicle system controllers, vehicle communication system, infotainment systems, vehicle telematics systems or subsystems, vehicle display systems or subsystems, vehicle data controllers, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media-streaming dongles or another personal media devices, wearable devices such as smartwatches, wireless hotspots, femtocells, broadband routers or other types of routers, and similar electronic devices which include a programmable processor and memory and circuitry configured to perform operations as described herein. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0179] Certain techniques are described in this disclosure as including logic or a number of components or modules. Modules can be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general -purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.Docket No. 14730815100PCT

[0180] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general -purpose processors or one or more specialpurpose processors.

[0181] As used herein, the terms “component” and “module” are intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on.”

[0182] As used herein, a phrase referring to a list of items separated by “or” refers to any combination of those items, including single members. For example, “a, b, or c” is intended to cover the possibilities of a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0183] In this disclosure, an expression of “X / Y” may include meaning of any of the following: “X or Y” or “X and Y” or “X and / or Y." An expression of “(A) B” or “B (A)” may include concept of “only B.” An expression of “(A) B” or “B (A)” may include the concept of “A+B” or “B+A.”

[0184] In this disclosure, the term "can" indicates a capability, or alternatively indicates a possible implementation option. The term "may" indicates a permission or a possible implementation option.

[0185] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may 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.

[0186] The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether suchDocket No. 14730815100PCT functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.

[0187] As described above, some aspects of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor-executable or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or to control the operation of, a data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

[0188] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0189] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0190] The drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustratedDocket No. 14730815100PCT operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0191] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes.

Claims

Docket No. 14730815100PCTCLAIMSWhat is claimed is:

1. A method for wireless communication by a first network entity (104), comprising: operating a first cell with a first time division duplex (TDD) downlink (DL)-uplink (UL) configuration and a first subband full duplex (SBFD) configuration; transmitting, to a second network entity (106), first cross-link interference (CLI) management information (130, 330) via an Xn interface or an Fl interface, the first CLI management information including at least one of: the first TDD DL-UL configuration, the first SBFD configuration, or first CLI assistance information; and receiving, from the second network entity (106), second CLI management information (130, 330) via an Xn interface or an Fl interface, the second CLI management information including at least one of: a second TDD DL-UL configuration of a second cell, a second SBFD configuration of the second cell, or second CLI assistance information.

2. The method of claim 1, further comprising: setting up an interface between the first network entity and the second network entity; and communicating the first CLI management information and the second CLI management information via the interface.

3. The method of claim 1 or 2, wherein the transmitting the first CLI management information includes: transmitting the first CLI management information via an Xn Setup Request message or an Fl Setup Request message as part of an interface setup procedure, wherein the receiving the second CLI management information includes receiving the second CLI management information via an Xn Setup Response message or an F l Setup Response as part of the interface setup procedure; transmitting a first portion of the first CLI management information via a setup request message; and transmitting a second portion of the first CLI management information via a configuration update message after the setup request message, wherein the configuration update message is a next generation (NG)-radio access network (RAN) node configuration update message formatted to include at least the first SBFD configuration or the first CLI assistance information.Docket No. 14730815100PCT4. The method of claim 1 or 2, wherein the transmitting the first CLI management information includes: transmitting a setup request message as part of an interface setup procedure, wherein the setup request message does not include the first CLI management information; and transmitting the first CLI management information via a configuration update message update after the setup request message.

5. The method of any one of claims 1 to 4, further comprising, after the transmitting the first CLI management information: transmitting, to the second network entity, updated CLI management information via a configuration update message to update at least a portion of the first CLI management information.

6. The method of any one of claims 1 to 5, further comprising: receiving, from the second network entity, a first CLI mitigation request that includes CLI mitigation information, wherein the CLI mitigation information includes at least one of: an identification of the first cell, an indication of one or more CLI measurements resources of the first cell, a CLI measurement result for the one or more CLI measurement resources of the first cell, an identification of radio resources or beams of the first cell causing CLI, a channel state information reference signal (CSLRS) resource indicator (CRI) identifying a CSI-RS associated with a first beam of the first cell having the strongest signal or causing the strongest CLI; a synchronization signal block resource indicators (SSBRI) associated with an SSB of the first beam; an SSB index associated with the SSB of the first beam; or one or more CLI mitigation parameters.

7. The method of claim 6, further comprising: determining whether to accept the first CLI mitigation request; transmitting a CLI mitigation request acknowledgement message if the CLI mitigation request is accepted;Docket No. 14730815100PCT transmitting a CLI mitigation rejection message if the CLI mitigation request is not accepted; and enabling CLI mitigation based on the first CLI mitigation request and the CLI mitigation information.

8. The method of claim 6 or 7, further comprising: receiving, from the second network entity, a second CLI mitigation request that indicates CLI has abated; and disabling the CLI mitigation based on the second CLI mitigation request.

9. The method of any one of claims 1 to 8, further comprising: receiving, from one or more network entities, CLI mitigation requests associated with a plurality of cells of the first network entity; and enabling CLI mitigation on one or more cells of the plurality of cells based on the CLI mitigation requests.

10. The method of any one of claims 1 to 5, further comprising: determining a CLI measurement resource configuration based on the first CLI management information and the second CLI management information; obtaining a CLI measurement result based on the CLI measurement resource configuration, wherein the obtaining the CLI measurement result includes at least one of: transmitting, to a user equipment (UE) in the first cell, a CLI measurement configuration based on the CLI measurement resource configuration, receiving, from the UE, the CLI measurement result, or measuring, at the first network entity, a resource of the second cell based on theCLI measurement resource configuration; and transmitting, to the second network entity, a first CLI mitigation request when the CLI measurement result is above a CLI threshold.

11. The method of any one of claims 1 to 5, further comprising: receiving, from a third network entity, a CLI mitigation request associated with the second cell of the second network entity; and transmitting, to the second network entity, at least a portion of the CLI mitigation request.

12. The method of any one of claims 1 to 11, further comprising:Docket No. 14730815100PCT managing CLI between the first cell and the second cell based on the first CLI management information and the second CLI management information, wherein the managing the CLI includes at least one of adjusting the first TDD DL-UL configuration or the first SBFD configuration based on the second CLI management information; reducing a power level of at least one resource of the first cell based on the second CLI assistance information; or coordinating a CLI measurement resource configuration of a user equipment (UE) in the first cell to monitor the CLI.

13. The method of any one of claims 1 to 12, wherein the second CLI assistance information includes at least one of: a resource configuration of a user equipment (UE)-to-UE sounding reference signal (SRS) for CLI measurement; an indication of one or more beams with CLI; a CLI measurement resource configuration; a CLI threshold; one or more CLI management parameters; or one or more CLI handling parameters.

14. The method of any one of claims 1 to 13, wherein at least one of the first CLI management information or the second CLI management information includes at least one of a channel state information reference signal (CSI-RS) resource indicator (CRI) identifying a CSI-RS associated with a first beam of the first cell having the strongest signal or causing the strongest CLI; a synchronization signal block resource indicators (SSBRI) associated with an SSB of the first beam; or an SSB index associated with the SSB of the first beam; a non-zero power (NZP) CSI-RS-Resource; or an NZP-CSI-RS-ResourceSet.

15. An apparatus, comprising: a communication unit; andDocket No. 14730815100PCT a processing system configured to control the communication unit to implement any one of the methods of any one of claims 1 to 14.

Images