Resource coordination configuration for cross-link interference management with sub-band full-duplex

Abstract

Various aspects of the present disclosure relate to resource coordination configuration (RCC) for cross-link interference (CLI) management with sub-band full-duplex (SBFD). An apparatus, such as a first base station (BS), obtains a first resource coordination configuration (RCC) that coordinates one or more resources with one or more base stations (BSs). The first BS also obtains a resource configuration that indicates a frequency sub-band for sub-band full-duplex (SBFD) operation. The first BS identifies a second BS from the one or more BSs, and the first BS coordinates use of at least one resource of the one or more resources by the second BS based on the resource configuration.

Description

RESOURCE COORDINATION CONFIGURATION FOR CROSS-LINK INTERFERENCE MANAGEMENT WITH SUB-BAND FULL-DUPLEXRELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 574,230 filed April 03, 2024 entitled “Resource Coordination Configuration for Cross-Link Interference Management with Sub-Band Full-Duplex,” the disclosure of which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to interference management of wireless communications.BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] The wireless communications system may support wireless communications, and may include one or more devices, such as UEs, base stations, network entities, satellites, and / or network equipment (NE), among other devices, that transmit and / or receive signaling. Some wireless communications between devices and / or network equipment may be subject to cross-linkinterference (CLI), such as between neighboring serving cells, where an uplink (UL) transmission in one serving cell may interfere with a downlink (DL) reception in another serving cell.SUMMARY

[0005] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0006] A first base station (BS) for wireless communication is described. The BS may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the BS may be configured to, capable of, or operable to obtain a first resource coordination configuration (RCC) that coordinates one or more resources with one or more base stations (BSs). The first BS obtains a resource configuration that indicates at least one frequency sub-band for sub-band full-duplex (SBFD) operation. The first BS identifies at least a second BS from the one or more BSs, and coordinates use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0007] A processor (e.g., a standalone processor chipset, or a component of a BS) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to obtain, at a first BS, a first RCC that coordinates one or more resources with one or more BSs; obtain, at the first BS, a resource configuration that indicates at least one frequency sub-band for SBFD operation; identify at least a second BS from the one ormore BSs; and coordinate use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0008] A method performed or performable by a BS for wireless communication is described. The method may include obtaining a first RCC that coordinates one or more resources with one or more BSs; obtaining a resource configuration that indicates at least one frequency sub-band for SBFD operation; identifying at least a second BS from the one or more BSs; and coordinating use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0009] In some implementations of the BS, the processor, and the method described herein, to obtain the first RCC, the BS, the processor, and the method may be configured to, capable of, or operable to at least one of receive the first RCC from a core network, a core network function, or an operations, administration, and management (0AM) entity; or receive the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface. In some implementations of the BS, the processor, and the method described herein, to obtain the resource configuration, the BS, the processor, and the method may be configured to, capable of, or operable to at least one of receive the resource configuration from a core network, a core network function, or an operations, administration, and management (0AM) entity; or receive the resource configuration from the at least second BS via one or more of a backhaul interface, or over an air interface.

[0010] In some implementations of the BS, the processor, and the method described herein, the at least one resource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain. In some implementations of the BS, the processor, and the method described herein, the at least one resource is indicated as one or more of a slot or a symbol. In some implementations of the BS, the processor, and the method described herein, the first RCC includes a first configuration identifier (ID); the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, where the second RCC includes a second configuration ID; and where, to identify the at least second BS, the BS, the processor, and the method may be configured to, capable of, or operable to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource. In some implementations of the BS, theprocessor, and the method described herein, the one or more BSs are indicated by one or more of a core network, a core network function, an operations, administration, and management (OAM) entity, by pre-configuration, or the at least second BS.

[0011] In some implementations of the BS, the processor, and the method described herein, the BS, the processor, and the method may be configured to, capable of, or operable to coordinate use of the at least one resource, the BS, the processor, and the method may be configured to, capable of, or operable to match a direction of the wireless communication of the at least one resource with the at least second BS based on at least one of: the direction of the wireless communication is configured as downlink by the first BS and the at least second BS; the direction of the wireless communication is configured as uplink by the first BS and the at least second BS; the direction of the wireless communication is configured as flexible by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS based on a first determination that a second frequency sub-band configured on the at least one resource by the at least second BS is one of identical to, a subset of, or a superset of the at least one frequency sub-band configured on the resource by the first BS; the at least one resource is fully unused or partially unused based on a second determination that the second frequency sub-band configured on the at least one resource by the at least second BS is not identical to, the subset of, or the superset of the at least one frequency sub-band configured on the resource by the first BS; or a boundary of the direction of the wireless communication is matched between the first BS and the at least second BS at a slot level, a symbol level, a sub-band level, or a combination thereof.

[0012] In some implementations of the BS, the processor, and the method described herein, the BS, the processor, and the method may be configured to, capable of, or operable to decline to match a direction of the wireless communication for the at least one resource with the at least second BS based on a signal or a channel that includes at least one of the signal or the channel with a high priority; one or more of a reference signal, a control channel, a semi-persistent scheduled channel, a configured-grant channel, or a random access channel; or the signal or the channel configured as an exception for resource coordination. In some implementations of the BS, the processor, and the method described herein, the BS, the processor, and the method may be configured to, capable of,or operable to coordinate use of the one or more resources to manage cross-link interference (CLI) between the first BS and the at least second BS.

[0013] A network equipment (NE) for wireless communication is described. The NE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the NE may be configured to, capable of, or operable to determine a first BS that causes CLI with at least a second BS; transmit, to the first BS, a first RCC that coordinates one or more resources with the at least second BS; and transmit, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0014] A processor (e.g., a standalone processor chipset, or a component of a NE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to determine a first BS that causes CLI with at least a second BS; transmit, to the first BS, a first RCC that coordinates one or more resources with the at least second BS; and transmit, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0015] A method performed or performable by an NE (e.g., a base station) for wireless communication is described. The method may include determining a first BS that causes CLI with at least a second BS; transmitting, to the first BS, a first RCC that coordinates one or more resources with the at least second BS; and transmitting, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0016] In some implementations of the NE, the processor, and the method described herein, one or more of the first BS or the at least second BS is identifiable based on one or more of: a geographical proximity of the first BS to the at least second BS; a first indication that the first BS configures a first SBFD operation on the one or more resources; a second indication that the at least second BS configures a second SBFD operation on the one or more resources; or a CLI report received from the at least second BS, the CLI report indicating the CLI with the first BS. In some implementations of the NE, the processor, and the method described herein, a third RCC coordinates one or more additional resources with a third BS; and the NE, the processor, and the method may be configured to, capable of, or operable to determine that the one or more resourcesshould not overlap with the one or more additional resources based on a determination that at least one cell of the third BS overlaps with at least one cell of the first BS or the second BS.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0018] Figure 2 illustrates an example of a wireless cell with a UE served by a base station (BS) (e.g., a gNB), in accordance with aspects of the present disclosure.

[0019] Figure 3 illustrates an example of sub-band full duplex (SBFD) resource configuration as compared to time division duplexing (TDD) configuration, in accordance with aspects of the present disclosure.

[0020] Figure 4 illustrates an example of BS-to-BS cross-link interference (CLI) and UE-to-UE CLI, in accordance with aspects of the present disclosure.

[0021] Figure 5 illustrates an example of gNBs and cells configured with multiple resource coordination configurations, in accordance with aspects of the present disclosure.

[0022] Figure 6 illustrates an example of resource slots of different resource coordination configurations do not overlap, in accordance with aspects of the present disclosure.

[0023] Figure 7 illustrates an example of resource slots of different resource coordination configurations or any gNB and / or cell do not overlap, in accordance with aspects of the present disclosure.

[0024] Figure 8 illustrates an example of downlink (DL), uplink (UL), and sub-band matching on indicated slots, in accordance with aspects of the present disclosure.

[0025] Figure 9 illustrates an example of DL, UL, and sub-band mismatch on indicated slots, in accordance with aspects of the present disclosure.

[0026] Figure 10 illustrates an example of ASN.l code for a core network signaling for resource coordination configuration, in accordance with aspects of the present disclosure.

[0027] Figure 11 illustrates another example of ASN.l code for a core network signaling for resource coordination configuration, in accordance with aspects of the present disclosure.

[0028] Figure 12 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0029] Figure 13 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0030] Figure 14 illustrates an example of an NE (e.g., a base station, gNB, cell) in accordance with aspects of the present disclosure.

[0031] Figure 15 illustrates a flowchart of a method performed by a BS in accordance with aspects of the present disclosure.

[0032] Figure 16 illustrates a flowchart of a method performed by an NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0033] A wireless communications system may support wireless communications for one or more devices, such as UEs, base stations, gNBs, NES, network entities, satellites, and / or other devices, supporting wireless communications (e.g., control information, data, packets, etc.). The wireless communication scenarios may include BS-to-BS communications, as well as UE-to-UE communications. However, some wireless communications between UEs and / or NEs may be subject to CLI, such as communication interference between neighboring serving cells. For example, an uplink (UL) transmission in one serving cell may interfere with a downlink (DL) reception in another serving cell.

[0034] In the wireless communications system, time division duplexing (TDD) refers to a communications scheme that splits radio resources among downlink and uplink transmissions in the time domain. At any point in time for a given frequency in a TDD system, a base station can transmit communication signals to one or more UEs (e.g., subscriber devices), or vice versa. In a conventional cellular system that utilizes TDD, patterns of TDD are synchronized and are typically identical so as to avoid CLI. A duplexing enhancement is sub-band full-duplex (SBFD), whereby one or multiple UEs may be configured to transmit uplink signals in a sub-band on downlinksymbols, or vice versa. A UE may not be expected to have full-duplex capability on the sub-band, however, the base station (e.g., a gNB) may utilize duplexing enhancements for communications on the sub-band.

[0035] Aspects of the disclosure are directed to CLI management, such as for BS-to-BS CLI management of communications, and for UE-to-UE CLI management of communications. The use of coordinated scheduling and beamforming in time, frequency, and / or spatial domains can be evaluated to address both BS-to-BS co-channel CLI management and UE-to-UE co-channel CLI management. In implementations for inter-cell CLI management, aspects of the described techniques are directed to dynamic information exchange among BSs, which is currently prohibitive with the conventional backhaul technologies. Accordingly, the present disclosure details aspects of resource coordination configuration (RCC) among BSs and / or serving cells in SBFD systems. Additionally, an over-the-air indication of resource allocation is an aspect of as a replacement for information exchange over backhaul.

[0036] The present disclosure is directed to RCC, which mitigates the need for dynamic information exchange over the backhaul. In one or more implementations, a base station can be configured to match resource configurations in time and / or frequency domains with other base stations in its vicinity over a multiple resources (e.g., time slots). This can include matching SBFD UL / DL directions and subbands on the time slots across the base stations. Multiple resource configurations may be applicable to multiple resources. By utilizing the described techniques, the need for dynamic information exchange for every scheduling decision is avoided, and instead enables coordination at larger time scales.

[0037] In one or more implementations, multiple NEs (e.g., BSs, gNBs, and / or cells) can be configured with a RCC (also designated as ResCoordConfig herein), which includes an indication of one or more resources (e.g., multiple time slots). The NEs can then match SBFD configurations on the indicated resources. Matching a configuration on a slot may include an NE configures the slot as DL, UL, as SBFD with matching subbands, as SBFD and non-SBFD symbols on the slot with matching at the symbol level and matching subbands, or as unmatching sub-band configurations (where one NE (e.g., BS, gNB, cell) does not use the unmatching symbols or subbands). Conversely, examples of unmatched resource configurations may include a first NE configures the slot as non-SBFD, while a second NE configures the slot as SBFD; the first NEconfigures the slot as SBFD, however the frequency ranges of the sub-band do not match; or configurations of the NEs do not match at symbol level within the slot. In various examples, if the resources indicated by two (or more) configurations overlap, the NE may implement to accept both configurations if constraints on the resources are not conflicting, prioritize one configuration over another, neglect both configurations, and / or indicate an error case.

[0038] Aspects of the present disclosure are described in the context of a wireless communications system. In the wireless communications system, a UE and an NE (e.g., a base station, gNB, network entity, network node) may support wireless communication, including reception and / or transmission of wireless communication using time-frequency resources. For example, the UE and the NE may support communicating signals (e.g., carrying control information, data, or the like). It should be understood that various terms may be used interchangeably with “communicating,” such as “signaling,” “transmitting,” “receiving,” “outputting,” “forwarding,” “relaying,” “retrieving,” “obtaining,” and so forth.

[0039] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0040] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a networkfunction, a network entity, a network node, network infrastructure, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0041] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0042] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of- Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0043] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0044] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N6, or other network interface). In some implementations, the NE 102may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106). In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0045] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0046] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N6, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0047] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and theUEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0048] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0049] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0050] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, / =l , / r=2, / r=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may dependon a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0051] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0052] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0053] According to implementations, one or more of the NEs 102 and the UEs 104 are operable to implement various aspects of the techniques described with reference to the present disclosure. For example, an NE 102 (e.g., a first base station) obtains a first RCC that coordinates one or more resources with one or more BSs. The NE 102 obtains a resource configuration that indicates at least one frequency sub-band for SBFD operation. The NE 102 identifies at least asecond BS from the one or more BSs, and the NE 102 coordinates use of at least one resource of the one or more resources by the at least second BS based on the resource configuration. In a further example, an NE 102 determines a first BS that causes CLI with at least a second BS. The NE 102 transmits, to the first BS, a first RCC that coordinates one or more resources with the second BS, and the NE 102 transmits, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0054] In aspects of this disclosure, an agreement for candidate gNB-to-gNB co-channel CLI handling schemes is taken into consideration, including gNB-to-gNB co-channel CLI and / or channel measurements; spatial domain based schemes including beam nulling and beam pairing; coordinated scheduling in time and / or frequency; and power control based schemes including gNB transmit (Tx) power control and UE Tx power control. The gNB-to-gNB co-channel CLI and / or channel measurements can be the enablers for some of the described CLI handling schemes.

[0055] In aspects of this disclosure, an agreement for candidate UE-to-UE co-channel CLI handling schemes is taken into consideration, including UE-to-UE co-channel CLI measurement and reporting; coordinated scheduling in time and / or frequency; spatial domain based schemes; and power control based schemes. The UE-to-UE co-channel CLI measurement and reporting can be the enablers for some of the described CLI handling schemes.

[0056] With reference to remote interference management, an atmospheric ducting phenomenon is caused by lower densities at higher altitudes in the Earth's atmosphere, which causes a reduced refractive index, causing signals to bend back towards the Earth. A signal trapped in the atmospheric duct can reach distances far greater than normal. In TDD networks with the same UL / DL slot configuration, and in the absence of atmospheric ducting, a guard period is used to avoid the interference between UL and DL transmissions in different cells. However, when the atmospheric ducting phenomenon happens, radio signals can travel a relatively long distance, and the propagation delay exceeds the guard period. Consequently, the DL signals of an interfering cell can interfere with the UL signals of an interfered cell that is far away from the interfering cell. Such interference is termed as remote interference, and the further the interfering cell is to the interfered cell, the more UL symbols of the interfered cell will be impacted.

[0057] A remote interference scenario may involve a number of interfered and interfering cells, where the gNBs execute remote interference management (RIM) coordination on behalf of their respective cells. Interfering and interfered gNBs can be grouped into semi-static sets, where each cell is assigned a set ID, and is configured with a RIM reference signal (RIM-RS) and the radio resources associated with the set ID. Each interfering gNB can be configured with multiple set IDs and each interfered gNB can be configured with multiple set IDs, whereas each cell can have at most one interfered set ID and one interfering set ID. Consequently, each gNB can be an interfering gNB and an interfered gNB at the same time.

[0058] To mitigate remote interference, the network enables RIM frameworks for coordination between interfered and interfering gNBs. The coordination communication in RIM frameworks can be wireless- or backhaul-based. The backhaul-based RIM framework uses a combination of wireless and backhaul communication, while in the wireless framework, the communication is purely wireless. In both frameworks, all of the gNBs in an interfered set simultaneously transmit an identical RIM reference signal carrying the interfered set ID over the air. In the wireless framework, upon reception of the RIM reference signal from the interfered set, interfering gNBs undertake RIM measures, and send back a RIM reference signal carrying the interfering set ID. The RIM reference signal sent by the interfering gNB is able to provide information, such as whether the atmospheric ducting phenomenon exists. The interfered gNBs realize the atmospheric ducting phenomenon have ceased upon not receiving any reference signals sent from interfering gNBs.

[0059] In the RIM backhaul framework, upon reception of the RIM reference signal from the interfered set, interfering gNBs undertake RIM measures, and establish backhaul coordination towards the interfered gNB set. The backhaul messages are sent from individual interfering gNBs to an individual interfered gNB, where the signaling is transparent to the core network. The RIM backhaul messages from interfering to interfered gNBs carry the indication about the detection or disappearance of the RIM reference signal. Based on the indication from the backhaul message, the interfered gNBs can determine whether the atmospheric ducting and the consequent remote interference have ceased. In both frameworks, upon a determination that the atmospheric ducting has disappeared, the interfered gNBs stop transmitting the RIM reference signal.

[0060] With reference to a CLI management framework, when different TDD DL / UL patterns are used between neighboring cells, UL transmission in one cell may interfere with DL reception inanother cell, and this is referred to as CLI. To mitigate CLI, gNBs can exchange and coordinate their intended TDD DL-UL configurations over Xn and Fl interfaces, and the interfered UEs can be configured to perform CLI measurements. There are two types of CLI measurements, which include a sounding reference signal (SRS)-reference signal received power (RSRP) measurement in which the UE measures SRS-RSRP over SRS resources of interfering UE(s). The CLI measurements also include a CLI-received signal strength indicator (RSSI) measurement in which the UE measures the total received power observed over RSSI resources. Layer 3 filtering applies to CLI measurement results and both event triggered and periodic reporting are supported.

[0061] With reference to CLI measurements, SRS-RSRP is a linear average of the power contributions (in [W]) of the resource elements carrying SRS. The SRS-RSRP is measured over the configured resource elements within the considered measurement frequency bandwidth in the configured measurement time occasions. For frequency range 1, the reference point for the SRS-RSRP is the antenna connector of the UE. For frequency range 2, SRS-RSRP is measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SRS-RSRP value shall not be lower than the corresponding SRS-RSRP of any of the individual receiver branches. This is applicable for RRC_CONNECTED intra-frequency. The CLLRSSI is a linear average of the total received power (in [W]) observed only in the configured orthogonal frequency division multiplexing (OFDM) symbols of the configured measurement time resource(s), in the configured measurement bandwidth from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. For frequency range 1, the reference point for the RSSI is the antenna connector of the UE. For frequency range 2, CLLRSSI is measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported CLLRSSI value shall not be lower than the corresponding CLLRSSI of any of the individual receiver branches. This is also applicable for RRC_CONNECTED intra-frequency.

[0062] With reference to inter-UE CLI handling schemes specific for SBFD, methods for inter-UE inter-sub-band CLI measurement include a method#! for an interfered UE measures RSSI within a DL sub-band; a method#2 for an interfered UE measures RSRP of an interfering UE within an UL sub-band; and a method#3 for an interfered UE measures RSSI within an UL sub-band. Notethat the restriction (in Rel- 16) that CLI is only measured within a DL BWP does not forbid a UE to measure CLI in an UL sub-band when the UL sub-band is confined within the DL BWP.

[0063] Lor UE-to-UE CLI-RSSI measurement and report across downlink sub-bands, methods include Alt #1 for separate CLI-RSSI measurement resources and / or reports in each DL sub-band; Alt #2 for CLI-RSSI measure and / or report in one DL sub-band only; and Alt #3 for CLI-RSSI measurement and / or report based on non-contiguous CLI-RSSI resource across downlink subbands. The Alt #1 allows flexible configuration of measurement reporting in one DL sub-band or two DL sub-bands, but consumes multiple CLI-RSSI measurement resources from the UE capability budget. The Alt #2 restricts gNB configuration flexibility and does not account for whether or not the CLI is asymmetric across two DL sub-bands. This method does not consume multiple CLI-RSSI measurement resources from a UE capability point of view. The Alt #3 requires additional specification efforts to support non-contiguous CLI-RSSI resource allocation across downlink subbands. This method is similar to non-contiguous CSLRS resource allocation. A single CLI-RSSI report based on non-contiguous CLI-RSSI resource may be sufficient. This method does not consume multiple CLI-RSSI measurement resources from a UE capability point of view. Note that it does not imply whether LI or L2 based measurement is supported.

[0064] The method #2 and method #3 can be used for identifying the interfering UE(s) if orthogonal resources are allocated for different interfering UE(s). The method #2 and #3 can at least provide higher interference signal strength than inter-sub-band interference leakage based measurements in method #1. Eurthermore, such measurement is not subject to inter-cell DL interference. It is feasible for a UE to measure RSRP / RSSI within an UL sub-band if within an active DL BWP and receive DL in DL sub-band(s) simultaneously, similar as with simultaneous RSRP / RSSI measurement and DL reception. The existing CLI measurement and report framework can be reused to support RSRP / RSSI measurements within an UL sub-band when the UL sub-band is confined within an active DL BWP.

[0065] With reference to inter-gNB CLI handling schemes, potential enhancements to dynamic and / or flexible TDD and / or SBED include a potential enhancement method of gNB-to-gNB CLI handling, including gNB-to-gNB CLI measurement and reporting, coordinated scheduling, spatial domain enhancements, advanced receiver, UE and gNB transmission and reception timing, power control-based solution, potential enhancements to Rel- 16 RIM, and / or sensing-based mechanism.Note that whether particular scheme requires OTA or backhaul information exchange can be identified, and any other schemes for inter-gNB CLI handling are not precluded. RAN 1 deprioritized the discussion on both potential enhancement to Rel- 16 RIM and sensing-based mechanism for gNB-to-gNB co-channel CLI handling, which can be specific for dynamic and / or flexible TDD and / or common for both SBFD and dynamic and / or flexible TDD.

[0066] With reference to gNB-to-gNB co-channel CLI measurement and / or channel measurement, the feasibility and potential benefits of gNB-to-gNB co-channel CLI measurement for gNB-to-gNB CLI handling can be specific for dynamic and / or flexible TDD and / or common for both SBFD and dynamic and / or flexible TDD. This may include measurement resource configuration, measurement details, relevant information exchange, and / or usage of measurement. Also, for gNB-to-gNB co-channel CLI measurement, the potential benefit of uplink resources muting is considered.

[0067] With reference to measurement resource, performance matric, and relevant information exchange, for gNB-to-gNB co-channel CLI measurement, it is considered a baseline to reuse existing DL channel(s), signal(s), and / or measurement resource(s), for example, synchronization signal block (SSB), non-zero power (NZP) or zero power (ZP)-CSLRS, demodulation reference signal (DMRS) for physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH), CSI interference measurement (CSLIM), RSSI measurement resource, etc. The beam level (i.e., based on measurement results per SSB resource and / or per CSLRS resource) CLI measurement can be considered. Additionally, RAN 1 assumes that exchange of configuration for NZP CSLRS or SSB can be an enabler for gNB-to-gNB CLI measurement and / or channel measurement.

[0068] With reference to UL resource muting, and for enhancement of gNB-to-gNB co-channel CLI measurement and / or channel measurement, the options for UL resource muting include a first option for a transparent UL resource muting method (e.g., avoid the scheduling on measurement resource), and a second option for a non-transparent UL resource muting method (e.g., define UL resource muting pattern with one or more RE / RB muting patterns). With reference to reception timing misalignment, for gNB-to-gNB co-channel CLI measurement and / or channel measurement, the impact on system performance is studied because of CLI measurement inaccuracy at an interfered gNB due to misalignment between UL timing at the interfered gNB and DL receptiontiming at the interfered gNB of a CLI measurement resource transmitted from one or more interfering gNBs. The potential impact on UL performance is included.

[0069] With reference to inter-UE CLI handling schemes, enhancements to dynamic and / or flexible TDD and / or SBFD considers the candidates of a potential enhancement method of UE-to- UE CLI handling, including potential enhancements to UE-to-UE CLI measurement and reporting, coordinated scheduling, spatial domain enhancements, advanced receiver, UE and gNB transmission and reception timing, a power control based solution, and a sensing-based mechanism. Note that whether a particular scheme requires OTA or backhaul information exchange can be identified, and any other scheme(s) for UE-to-UE CLI handling are not precluded. Potential enhancements to dynamic and / or flexible TDD and / or SBFD can be utilized, and a sensing-based mechanism (i.e. LBT) and UE side advanced receiver for UE-to-UE co-channel CLI handling can be used, which can be specific for dynamic and / or flexible TDD and / or common for both SBFD and dynamic and / or flexible TDD.

[0070] With reference to UE-to-UE co-channel CLI measurement and reporting, a potential benefit is UE-to-UE co-channel CLI measurement and reporting, which can be specific for dynamic and / or flexible TDD and / or common for both SBFD and dynamic and / or flexible TDD. This can include measurement resource and reporting configuration, measurement and reporting details (including UE processing delay), relevant information exchange (between gNBs) if needed, and measurement use at a gNB. For UE-to-UE co-channel CLI measurement, reusing existing channel(s), signal(s) and / or measurement resource(s) is considered as a baseline. For example, SRS resources for SRS-RSRP measurement, and CLI-RSSI resources for CLI-RSSI measurement can be considered.

[0071] For UE-to-UE co-channel CLI handling, L1 / L2 based UE-to-UE CLI measurement and reporting is considered. Note that accounting for UE processing and reporting delay, the mechanism of L1 / L2 based CLI measurement and reporting can be provided, and the benefits of L1 / L2 based CLI measurement and reporting compared with existing L3 CLI / CSI measurement and report with evaluation result. Additionally, accounting for information exchange delay between gNBs (if applicable). For the purpose of UE-to-UE CLI mitigation, potential enhancements include L1 / L2 UE-to-UE CLI reporting, periodic, semi-persistent, aperiodic, or event triggered reporting; and for L1 / L2 UE-to-UE CLI measurement, periodic, semi-persistent, or aperiodic measurement resource.For L1 / L2 based UE-to-UE CLI measurement, SRS-RSRP and CLI-RSSI are considered for baseline metrics. For L1 / L2 based UE-to-UE co-channel CLI measurement, measurement resource for CLI-RSSI measurement and SRS resource for SRS-RSRP measurement can be considered. For L1 / L2 based UE-to-UE co-channel CLI measurement and reporting mechanism, the measurement and report framework can use existing CSI framework as the baseline, but others are not precluded.

[0072] Figure 2 illustrates an example of a wireless cell 200 with a UE served by a base station (BS) (e.g., a gNB), in accordance with aspects of the present disclosure. In this example, a UE 104 is connected to a base station 102 (e.g., gNB). The base station 102 may be a radio access network (RAN) node operating according to a 4G, 5G, or 6G standard (e.g., a transmission-reception point (TRP), a customer premise equipment (CPE), an integrated access and backhaul (IAB) node, a relay, or the like. In one or more implementations, the UE 104 is configured with a SBFD resource configuration. With SBFD, a sub-band in the bandwidth of the wireless link is configured to perform a communication in a direction that is different from the direction of communications in the rest of the bandwidth. For example, an UL sub-band on a DL symbol refers to a sub-band within the DL bandwidth that may be used for UL communications.

[0073] Figure 3 illustrates an example 300 of sub-band full duplex (SBFD) resource configuration as compared to time division duplexing (TDD) configuration, in accordance with aspects of the present disclosure. In this example, an UL sub-band within DL resources, at b) SBFD 302, is compared to a conventional TDD configuration, at a) TDD 304. In this example, an UL sub-band may split the bandwidth into two or three sub-bands, such as with one UL sub-band adjacent to one or two DL sub-bands. It should be noted that, in this example, the bandwidth is configured as DL (e.g., via a TDD configuration) and then the UL sub-band splits the bandwidth (e.g., indicated by a SBFD sub-band configuration). However, the remaining DL resources are also referred to as sub-bands in the present disclosure. This terminology allows a more flexible reference to sub-band configurations. For example, the following configurations may be referenced similarly: an UL sub-band configured in a DL bandwidth; two DL sub-bands and an UL sub-band all configured separately; and two DL sub-bands configured in an UL bandwidth.

[0074] Furthermore, a guard-band may be configured explicitly, or determined implicitly, between two adjacent sub-bands, particularly between adjacent sub-bands of different directions (e.g., between a DL sub-band and an UL sub-band). The guard-band may be configured ordetermined as a number of physical resource blocks (PRBs) on which the UE is expected neither to transmit nor to receive a signal.

[0075] Conventional wireless systems have been known to be half-duplex in nature, i.e., a wireless transceiver may either transmit or receive through a same antenna, one at a time, but not both simultaneously. However, with the advent of advanced duplexing schemes, it can be assumed that either or both the gNB and the UE may employ such schemes to communicate in both DL and UL simultaneously. Advanced duplexing methods such as dynamic and / or flexible TDD and SBFD allow cells in a vicinity to use same resources in time and / or frequency domains for downlink and uplink transmissions. That may lead to CLI among BSs and / or among UEs.

[0076] Figure 4 illustrates an example 400 of BS-to-BS cross-link interference (CLI) and UE- to-UE CLI, in accordance with aspects of the present disclosure. This example includes BSs 102 and UEs 104, and illustrates different types of CLI, namely BS-to-BS CLI 402 and UE-to-UE CLI 404. The BS-to-BS CLI 402 may result in degradation of the signal quality at a BS 102. Specifically, if a first BS (e.g., BS1) receives an uplink signal from a first UE (e.g., UE1) when a second BS (e.g., BS2) transmits a downlink signal to a second UE (e.g., UE2) on the same resources, the downlink signal may interfere with the uplink signal at the first BS, hence degrading the uplink signal quality. In aspects of the disclosure, some solutions are referred to as coordinated scheduling and beamforming, through which two or more BSs coordinate on the use of resources and / or beams so as to avoid excessive BS-to-BS CLI. Each BS may serve multiple UEs at a time, some of which may be legacy UEs operating according to conventional duplexing, such as TDD, and some of which may be enhanced, such as SBFD-aware UEs, operating according to enhanced duplexing, such as SBFD. Furthermore, different UEs may communicate on different resources (such as frequency resources, PRBs, and sub-bands) and / or through different beams, hence allowing degrees of freedom to the scheduler to utilize the coordinated scheduling and beamforming for CLI mitigation.

[0077] However, an obstacle to utilize coordinated scheduling and beamforming is the potential need for dynamic information exchange among the BSs. Scheduling, resource allocation, link adaptation, and beamforming are intrinsically dynamic due to UE mobility, and therefore coordination for these procedures is also dynamic. If the coordination requires dynamic information exchange in real time, it may be prohibitive in practical scenarios in the presence of nonidealbackhaul among base stations. Aspects of the present disclosure address this problem by allowing a coordinated scheduling and beamforming that does not require a real-time information exchange among the BSs. In various implementations, two or more BSs coordinate on the use of multiple resources and / or beams in the time domain, frequency domain, and / or spatial domain such that excessive CLI is avoided.

[0078] In one or more implementations, multiple NEs (e.g., BSs, gNBs, cells) operating in a TDD or SBFD carrier may be configured with a RCC, also referred to herein as ResCoordConfig. A ResCoordConfig may include indications of resources and / or beams in the time domain, frequency domain, and / or spatial domain. Additionally, a RCC may not necessarily be limited to just one coordination configuration, but rather, may be part of a new, different, and / or existing configuration. In a first example, a ResCoordConfig in a TDD or SBFD carrier may include an indication of multiple time slots. Then, it may be expected that TDD or SBFD configurations are coordinated by the NEs so as to avoid excessive CEI on the multiple time slots. In a TDD configuration, the coordination may imply to match TDD DE / UE directions among NEs on the time slots (i.e., the NEs are expected to configure a symbol as DL in all of the NEs on the multiple time slots, or as UL in all of the NEs on the multiple time slots). The coordination may be at slot level, symbol level, sub-band level, PRB level, or the like. Additionally, or alternatively, in a SBFD configuration, the coordination may imply to match sub-band directions among the NEs (i.e., matching SBFD sub-bands (fully or partially) or avoiding sub-band communications on the slots).

[0079] In a second example, a ResCoordConfig in a TDD or SBFD carrier may include an indication of a sub-band, multiple PRBs or RBGs, or the like. Then, it may be expected that TDD and / or SBFD configurations are coordinated by the NEs so as to avoid excessive CLI on the sub-band or the multiple PRBs and / or RBGs. In a TDD configuration, the coordination may imply to match TDD DL / UL directions among NEs on the sub-band or the multiple PRBs and / or RBGs (i.e., the NEs are expected to configure a symbol as DL in all of the NEs on the sub-band or the multiple PRBs and / or RBGs, or as UL in all of the NEs on the sub-band or the multiple PRBs and / or RBGs). The coordination may be at slot level, symbol level, sub-band level, PRB level, or the like. Additionally, or alternatively, in a SBFD configuration, the coordination may imply to match sub-band directions among the NEs (i.e., matching SBFD sub-bands (fully or partially) or avoiding sub-band communications on the sub-band or multiple PRBs and / or RBGs).

[0080] In a third example, a combination of the above may be applied, i.e., a ResCoordConfig in a TDD or SBFD carrier may include an indication of multiple time slots, a sub-band, multiple PRBs, RBGs, and / or the like. Then, it may be expected that TDD and / or SBFD configurations are coordinated by the NEs so as to avoid excessive CLI on the slots, sub-band, or the multiple PRBs and / or RBGs. In a TDD configuration, the coordination may imply to match TDD DL / UL directions among NEs on the slots, sub-band, and / or the multiple PRBs and / or RBGs (i.e., the NEs are expected to configure a symbol as DL in all of the NEs on the slots, sub-band, and / or the multiple PRBs and / or RBGs, or as UL in all of the NEs on the slots, sub-band, and / or the multiple PRBs and / or RBGs. The coordination may be at slot level, symbol level, sub-band level, PRB level, or the like. Additionally, or alternatively, in a SBFD configuration, the coordination may imply to match sub-band directions among the NEs (i.e., matching SBFD subbands (fully or partially) or avoiding sub-band communications on the slots, sub-band, or the multiple PRBs and / or RBGs).

[0081] In one or more implementations, multiple NEs may share a ResCoordConfig comprising an indication of multiple resources and / or beams. The NEs may be considered a gNB and / or cell cluster with constraints applied to the multiple resources and / or beams. Considering this clustering interpretation and considering that clusters are associated with resource and / or beam constraints, it can be observed that overlapping clusters of gNBs and / or cells (i.e., clusters that share at least one gNB or cell) may not overlap in resources, and conversely, non-overlapping clusters (i.e., clusters that do not share a gNB or cell) may overlap in resources. Therefore, in various examples, if an NE (e.g., a gNB or cell) is configured with a first ResCoordConfig and a second ResCoordConfig, each with an indication of multiple resources, the resources may not overlap in the time domain, the frequency domain, the spatial domain, or a combination thereof. Overlapping in the time domain may mean that there is at least one symbol or slot that is indicated by multiple indications. Overlapping in the frequency domain may mean that there is at least one PRB, RBG, or sub-band that is indicated by multiple indications.

[0082] In various examples, if the resources indicated by two (or more) configurations overlap, the NE (e.g., gNB or cell) may do at least one of the following: if constraints on the resources are not conflicting, accept both configurations; prioritize one configuration over another (e.g., prioritize the configuration that is received earlier or earliest, prioritize the configuration that is received later or latest, prioritize a configuration based on an entity that has sent the configuration, prioritize aconfiguration based on a quality-of-service (QoS) associated with one or multiple resources in the resource indication comprised by the configuration; neglect both configurations; and / or raise an error case or follow an implementation. These one or more implementations are particularly useful at higher frequencies, such as for FR2 bands where analog beamforming of BSs towards UEs is a factor determining the CLI.

[0083] Figure 5 illustrates an example 500 of gNBs and cells configured with multiple resource coordination configurations, in accordance with aspects of the present disclosure. In this example, four gNBs and / or cells (e.g., at BSs 102) are configured by several ResCoordConfig referred to as config 1, config2, config3, and config4. Each of the configurations include an indication of multiple resources. The gNBl is configured with config 1 and config2; the gNB2 is configured with config 1 and config3; the gNB3 is configured with config3 and config4; and the gNB4 is configured with config2 and config4.

[0084] Figure 6 illustrates an example 600 of resource slots of different resource coordination configurations do not overlap, in accordance with aspects of the present disclosure. In an implementation, a gNB or cell may not expect to be configured with more than one ResCoordConfig on a resource in the time domain and / or the frequency domain. In a first example, a gNB or cell does not expect to be configured with more than one ResCoordConfig associated with a given slot. In this example (and referring to Figure 5), gNBl is configured with config 1 comprising an indication of resources that include slots 3 and 4, and configured with config2 comprising an indication of resources that include slots 8 and 9. The two sets of slots {3, 4} and {8, 9} are non-overlapping as gNBl expects.

[0085] Generally, resources such as slots indicated by a ResCoordConfig may be determined by multiple parameters, for example an indication of whether certain slots are included or excluded in multiple periodicities. In one example, slots 3 and 4 in every periodicity of 10 slots are associated with the ResCoordConfig, except every 5 periodicities (i.e., 50 slots). The exception, as indicated by an additional resource indication parameter, may serve to accommodate certain signals and / or channels such as SSB, CSI-RS, physical random access channel (PRACH), etc. that may impose other constraints, such as spatial (beamforming) constraints. By indicating the exception as an additional pattern element, the gNB or cell will have the freedom to use the resources (in every 50 slots in the example) for those signals and / or channels. As another example, slots 3 and 4 in everyperiodicity of 10 slots are indicated by a ResCoordConfig, in addition to slot 2 every 5 periodicities (i.e., 50 slots). In this example, the gNB or cell may secure a particular signal and / or channel on slot 2 from exposure to excessive CLI from other gNBs and / or cells in the vicinity.

[0086] Figure 7 illustrates an example 700 of resource slots of different resource coordination configurations or any gNB and / or cell do not overlap, in accordance with aspects of the present disclosure. In implementations, other ResCoordConfig (RCCs) may be associated with other sets of time slots. In this example (and referring to Figure 5), configl is associated with slots {3, 4}, config2 is associated with slots {8, 9}, config3 is associated with slots {6, 7, 8}, and config4 is associated with slots {2, 3}. Since configl and config4 are associated with overlapping slots, a gNB or cell may not expect to be configured with configl and config4. Similarly, a gNB or cell may not expect to be configured with config2 and config3. However, other combinations are possible in this example. For instance, gNB2 is configured with configl and config3. Accordingly, a TDD or SBFD configuration at gNB2 may be matched with gNBl on slots {3, 4}, matched with gNB3 on slots {6, 7, 8}, and / or satisfy similar conditions.

[0087] In another implementation, a gNB or cell may be configured with two or more ResCoordConfig indicating overlapping resources. Different behaviors may be specified for the gNB or cell. In an example, the gNB or cell may reject a new ResCoordConfig if the gNB or cell determines that the new ResCoordConfig comprises an indication of resources that overlap with resources indicated by an existing ResCoordConfig. For example, gNBl in the aforementioned example may reject to be configured with config4 as it indicates slots {2, 3} overlapping with slots {3, 4} indicated by configl.

[0088] In another example, the gNB or cell may accept the new ResCoordConfig, but the gNB or cell may apply a TDD or SBFD constraint (such as a matching constraint) only on resources that do not overlap with resources indicated by existing ResCoordConfig. For example, gNB 1 in the aforementioned example may accept config4, but match TDD or SBFD configurations with gNB3 and gNB4 only on slot 2, as its TDD or SBFD configuration is already matched with gNB2 on slot 3. In another example, the gNB or cell may accept the new ResCoordConfig and refrain to communicate on resources that impose conflicting constraints or configurations according to multiple ResCoordConfig. For example, gNB 1 in the aforementioned example may accept config4 and then refrain from communicating on any symbols or PRBs or sub-band in slot 3 that imposesconflicting DL / UL configurations by gNB2 (according to configl) versus gNB3 and gNB4 (according to config4).

[0089] In one or more implementations, certain signals and / or channels may be an exception, i.e., the gNB or cell may communicate on the resources configured for or allocated to the signals and / or channels even if the communication’s DL / UL direction does not match according to a ResCoordConfig-, other gNBs or cells configured with the ResCoordConfig-, a new ResCoordConfig-, other gNBs or cells that are configured with the new ResCoordConfig, or the like. For example, SSB, periodic CSLRS, PRACH, PDCCH or control resource set (CORESET), semi-persistent scheduling (SPS), configured grant physical uplink shared channel (CG-PUSCH), and / or other communication considered high-priority and / or semi-statically configured may be communicated, permanently or temporarily until the associated configuration is updated, even if it has a conflict with a DL / UL constraint. The configuration update of the signals and / or channels may be intended to avoid conflicts with the TDD and / or SBFD constraints of the ResCoordConfig, for example by either or both: allocating other resources to a DL signal or channel (SSB, CSLRS, PDCCH / CORESET, SPS, etc.) if the DL signal or channel is configured on a UL symbol, slot, or resource according to the TDD or SBFD constraints in accordance with the ResCoordConfig-, or allocating other resources to an UL signal or channel (PRACH, CG-PUSCH, etc.) if the UL signal or channel is configured on a DL symbol, slot, or resource according to the TDD or SBFD constraints in accordance with the ResCoordConfig.

[0090] The above examples are described for slot indications in the time domain. The techniques may also be employed for time resources (units) (e.g., OFDM symbols, a time interval described in milliseconds (ms), or a combination thereof). Furthermore, similar techniques may be employed for TDD or SBFD matching in association with resources in the frequency domain (e.g., a sub-band or multiple PRBs and / or RBGs). Then, similar rules and behaviors may be applied for scenarios with multiple ResCoordConfig when their associated resources overlap in the frequency domain.

[0091] Figure 8 illustrates an example 800 of downlink (DL), uplink (UL), and sub-band matching on indicated slots, in accordance with aspects of the present disclosure. In an implementation, if a first gNB or cell and a second gNB or cell are configured with a ResCoordConfig to coordinate SBFD or subbands on a slot, the first gNB or cell and the secondgNB or cell are expected to match DL, UL, and / or sub-band configurations on the slots, which may be indicated to UEs served by the gNB or cell either through RRC signaling (semi-static), L1 / L2 signaling (dynamic), or a combination thereof. This figure illustrates examples of DL, UL, and / or sub-band matching on slots that are indicated by the ResCoordConfig. Examples of the matching include both gNBs or both cells configure the slot as DL; both gNBs or both cells configure the slot as UL; both gNBs or both cells configure the slot as SBED with matching subbands; both gNBs or both cells configure SBED and non-SBED symbols on the slot with matching at the symbol level and matching sub-bands; and / or the gNBs and cells have unmatching sub-band configurations, but one gNB and / or cell does not use the unmatching symbols or subbands.

[0092] Figure 9 illustrates an example 900 of DL, UL, and sub-band mismatch on indicated slots, in accordance with aspects of the present disclosure. This figure illustrates examples of DL, UL, and sub-band mismatch on slots that are indicated by a ResCoordConfig. Examples of the mismatch include a first gNB or cell configures the slot as non-SBED while a second gNB or cell configures the slot as SBED; both gNBs or both cells configure the slot as SBED, but the frequency ranges of the sub-band do not match; and configurations of the gNBs and / or cells do not match at symbol level within the slot.

[0093] The techniques described herein may be extended to a combination of time and frequency resources (e.g., when a ResCoordConfig comprises an indication of one or multiple intervals described in slots, symbols, ms, etc. and a sub-band or a plurality of PRBs and / or RBGs, etc.). Then, similar rules and behaviors may be applied for scenarios with multiple ResCoordConfig when their associated resources overlap in either or both time and frequency domains. Note in this disclosure that a slot or OFDM symbol may be associated with a subcarrier spacing or a similar OFDM numerology parameter implicitly or explicitly configured or indicated by a signaling.

[0094] The described techniques can be implemented to determine behaviors for resources that are indicated by one or more ResCoordConfig. With respect to other resources, several implementations are also described in aspects of this disclosure. In an implementation, a gNB or cell may match a TDD or SBFD DL / UL configuration on resources not indicated by any ResCoordConfig that configures at least one of neighbor gNBs or cells indicated through an automatic neighbor relation (ANR) table; gNBs or cells in a vicinity (e.g., determined by their geographical locations and / or distance from the gNB or cell; or gNBs or cells detected to cause anexcessive interference (e.g., a gNB-to-gNB CLI exceeding a threshold). In another implementation, a gNB or cell may not expect to apply a constraint on a TDD or SBFD DL / UL configuration on resources not indicated by any ResCoordConfig. In another implementation, a gNB or cell may implement other mechanisms for determining whether to match a TDD or SBFD DL / UL configuration on resources not indicated by any ResCoordConfig.

[0095] In one or more implementations of the various techniques described above (e.g., with reference to Figures 5-9), and with reference to operations, administration, and management (0AM) (pre)configuration, ResCoordConfig (RCCs) are pre-configured by an 0AM entity. Static and / or planned parameters, such as the locations of gNBs, an expected DL / UL traffic load on each gNB, TDD, and SBFD configurations, and so on may be considered for the (pre)configurations. In some techniques, a ratio of resources, such as a certain number of slots in a periodicity, may be indicated by one or multiple ResCoordConfig. Different implementations can include a ratio of resources of each gNB may be indicated by one or multiple ResCoordConfig. For example, 3 slots in a periodicity of 10 slots may be indicated by one or multiple ResCoordConfig. In an example, a ratio of resources in each periodicity may be configured by each ResCoordConfig, such as each ResCoordConfig may indicate slots in a periodicity of 10 slots. Then, the number of slots indicated by one or multiple ResCoordConfig for a certain gNB may be determined based on the number of ResCoordConfig at a gNB, whether the indicated resources overlap, and so on. In another example, a minimum and / or maximum number of resources (slots, symbols, sub-bands, PRBs, etc.) may be indicated by a ResCoordConfig, such as the minimum and / or maximum may be constant or predetermined. Alternatively, the minimum and / or maximum may be a function of the type of gNBs (macro gNB vs. small-cell gNB), the number of gNBs configured by the ResCoordConfig, and so on. Furthermore, a gNB may be configured with one or multiple ResCoordConfig indicating resources based on geographical locations, expected mutual interference among gNBs, and so on. In some implementations, a gNB may be configured with at most a certain maximum number of ResCoordConfig.

[0096] In one or more implementations, and with reference to core network signaling, a ResCoordConfig is indicated by signaling with the core network. In an example, a core network function, such as an access and mobility management function (AMF), may configure each gNB with one or more ResCoordConfig via messages on a backhaul interface, such as an NG / N2. Then,gNBs configured with an identical ResCoordConfig (or gNBs configured with a ResCoordConfig that indicate identical or overlapping resources) may communicate directly, for example through Xn / X2 interfaces, or indirectly, for example through NG / N2 interfaces with a core network function, to match TDD and / or SBFD DL / UL configurations.

[0097] In one example implementation, association of configuration IDs with resources, such as slots and / or PRBs, may be signaled by the core network function. In another example, the association of configuration IDs with resources may be signaled among gNBs on Xn / X2 and / or NG / N2 interfaces. In another example, a core network function, such as an AMF, may signal to each gNB one or more configuration IDs, as well as TDD and / or SBFD DL / UL configurations on the resources associated with each configuration ID. Each gNB may then determine TDD and / or SBFD DL / UL constraints without having to communicate with other gNBs configured with an identical ResCoordConfig (or gNBs configured with ResCoordConfig that indicate identical or overlapping resources).

[0098] Figure 10 illustrates an example of ASN.l code 1000 for a core network signaling for resource coordination configuration, in accordance with aspects of the present disclosure. In this example to coordinate with other network nodes, a first configuration comprises a configuration ID and optionally an indication of multiple associated resources, such as one or more of multiple slots (indicated by the parameter slot List y. multiple SBFD configurations (indicated by the parameter sbfdConfigList multiple SBFD sub-bands (indicated by the parameter sbfdSubbandListy. and / or multiple PRBs (indicated by the parameter prbList). Then, a second configuration makes a reference to a ResCoordConfig by its configuration ID and indicates which RAN nodes (e.g., gNBs) are configured with the ResCoordConfig. Having obtained the information, a gNB may communicate with other gNBs configured with a same ResCoordConfig to match TDD and / or SBFD DL / UL configurations on the indicated resources.

[0099] Figure 11 illustrates another example of ASN.l code 1100 for a core network signaling for resource coordination configuration, in accordance with aspects of the present disclosure. In this alternative example, the core network signaling may indicate TDD and / or SBFD DL / UL configurations for the associated resources. A gNB configured with a ResCoordConfig indicating a slotList should match TDD DL / UL configurations with the indicated slotConfiguration-List on the slots indicated by slotList. The gNB may not match TDD DL / UL configurations on other slots evenif indicated by the core network signaling. Similarly, a gNB configured with a ResCoordConfig indicating a prbList should match TDD DL / UL configurations with the indicated slotConfiguration- List on the PRBs indicated by prbList. The gNB may not match TDD DL / UL configurations on other PRBs even if indicated by the core network signaling.

[0100] This applies to a combination of time and frequency resources as well, i.e., a gNB configured with a ResCoordConfig indicating a slotList and prbList should match TDD DL / UL configurations with the indicated slotConfiguration-List on the slots and / or PRBs indicated by slotList and / or prbList. The gNB may not match TDD DL / UL configurations on other slots and / or PRBs even if indicated by the core network signaling. Similarly, a gNB configured with a ResCoordConfig indicating a sbfdConfigList or sbfdSubbandList should match SBFD and / or subband configurations with the indicated sbfdConfiguration-List on the slots indicated by slotList. The gNB may not match SBFD and / or sub-band configurations on other slots even if indicated by the core network signaling. This applies to a combination of TDD and SBFD, as well as a gNB configured with a ResCoordConfig indicating a slotList and a sbfdConfigList, or sbfdSubbandList should match TDD DL / UL configurations with the indicated slotConfiguration-List on the slots and / or match SBFD or sub-band configurations with the indicated sbfdConfiguration-List. The gNB may not match TDD DL / UL configurations or SBFD and / or subband configurations on other slots even if indicated by the core network signaling.

[0101] In one or more implementations, and with reference to centralized inter-gNB signaling, resource coordination may be performed by signaling among gNBs directly, for example on Xn interfaces, or indirectly, for example on NG interfaces with a core network function. According to an implementation, one gNB is (pre)configured by an 0AM or signaled by a core network function as a coordinating gNB or entity. The coordinating gNB or entity may determine resources associated with the ResCoordConfig, SBFD / TDD configuration for the associated resources, and so on.

[0102] In one realization, upon determining the coordinating gNB or entity, a gNB may match SBFD / TDD configurations on the resources associated with the ResCoordConfig with an Intended SBFD Configuration IE or an Intended TDD UL-DL Configuration IE on those resources received from the coordinating gNB or entity. In another realization, the coordinating gNB or entity may signal associated resources and the SBFD / TDD configuration for the resources in a separatemessage / IE. In some examples, a first configuration comprises a configuration ID and optionally a plurality of associated slots and / or PRBs. Then, a second configuration makes a reference to a by its configuration ID and indicates which gNBs (RAN nodes, NG-RAN nodes) belong to the ResCoordConfig. Having obtained information of which gNBs belong to a ResCoordConfig, a gNB configured as a member of ResCoordConfig N associated with a plurality of resources (e.g., slots, PRBs, subbands, or a combination thereof) should match (or coordinate on) SBFD / TDD configurations. The gNB may not match SBFD / TDD configurations on other resources. It should be noted that throughout this disclosure, terms such as ‘belong to ResCoordConfig,' ‘join ResCoordConfig,' ‘leave ResCoordConfig,' and the like indicate that one or more gNBs are associated with the ResCoordConfig, and the configuration and the gNBs associated with the configuration are referenced herein interchangeably.

[0103] In one or more implementations, and with reference to distributed inter-gNB signaling, the ResCoordConfig may be performed by signaling among gNBs directly, for example on Xn interfaces, or indirectly, for example on NG interfaces through a core network function. According to this embodiment, gNBs belonging to a ResCoordConfig may perform direct signaling for determining SBFD / TDD constraints on the resources associated with the ResCoordConfig without the presence of a central coordinator such as a core network function or a coordinating gNB or entity. In one realization, a first gNB sends a first message / IE to a second gNB, where the first message / IE indicating a request to form or join a ResCoordConfig. The message / IE may further comprise a configuration ID and an associated plurality of resources such as slots, PRBs, subbands, or a combination thereof. In response, the second gNB may send a second message / IE to the first gNB indicating whether the second gNB is willing to form or a join the ResCoordConfig. The message / IE may further comprise the configuration ID and a parameter indicating whether the associated plurality of resources is accepted by the second gNB.

[0104] Alternatively, instead of the parameter, the second message / IE may comprise an alternative plurality of resources such as slots, PRBs, subbands, or a combination thereof. If different from those comprised by the first message / IE, the alternative plurality of resources may be interpreted as requested by the second gNB to be associated with the ResCoordConfig. In one example, the alternative plurality of resources may be a subset of the plurality of resources in the first message / IE. This may indicate to the first gNB that the second gNB may form or join theResCoordConfig if associated with not all the plurality of resources indicated by the first gNB in the first message / IE, but instead with the subset of the plurality of resources indicated by the second gNB in the second message / IE. The first message / IE may be called a ResCoordConfig Request IE and the second message / IE may be called a ResCoordConfig Response IE.

[0105] The above example is a two-way handshaking (i.e., when the second gNB sends the ResCoordConfig Response, both the first gNB and the second gNB are assumed members of the indicated ResCoordConfig). Upon forming a new ResCoordConfig or joining an existing ResCoordConfig, the second gNB may match (or coordinate on) SBFD / TDD configurations of its own with that of the first gNB on the plurality of resources indicated by the ResCoordConfig Request IE (or the ResCoordConfig Response IE if applicable). The SBFD / TDD configuration on the resources may be indicated by an Intended SBFD Configuration IE or an Intended TDD UL-DL Configuration IE from the first gNB. The second gNB may not match SBFD / TDD configurations on other resources.

[0106] An alternative to the two-way handshaking is a three-way handshaking whereby the first gNB sends a third message / IE indicating that the first gNB accepts association with the alternative plurality of resources indicated by the second gNB in the second message / IE. The third message / IE may be called an ResCoordConfig Ack IE. In this case, if the first gNB does not send a ResCoordConfig Ack IE, or if the first gNB sends another message / IE such as a ResCoordConfig Nack IE, the second gNB may interpret that as the ResCoordConfig not forming or the second gNB not joining an existing ResCoordConfig. In one example, the second gNB may send a ResCoordConfig Ack IE only if the ResCoordConfig is not existing. Otherwise, since accepting an alternative plurality of resources may result in inconsistency among gNBs that are already members of the ResCoordConfig, the second gNB may not send the ResCoordConfig Ack IE or it may send a ResCoordConfig Nack IE instead. In alternative realization, the first gNB may explicitly indicate, in the first message / IE, whether it requests to form a new ResCoordConfig or requests that the second gNB joins an existing ResCoordConfig. In the former case, the second gNB may indicate an alternative plurality of resources. However, in the latter case, the second gNB may indicate whether it accepts or rejects to join the ResCoordConfig.

[0107] In one or more implementations, and with reference to triggering ResCoordConfig Request / Response, a ResCoordConfig Request / Response handshaking may be triggered by a firstgNB detecting an excessive interference from a second gNB. In the case of gNB-to-gNB CLI, the first gNB may detect an interference from the second gNB that exceeds a threshold. The interference may be particularly excessive in one or more directions, hence not allowing the first gNB to communicate with UEs in those one or more directions. In this case, the first gNB may send a ResCoordConfig Request message to the second gNB such that by matching SBFD / TDD configurations on certain resources, the first gNB would be able to communicate with the UEs on those resources. Alternatively, in the case of UE-to-UE CLI, the first gNB may receive a CLI report (e.g., SRS-RSRP or CLI-RSSI) from a UE indicating an interference from a UE served by the second gNB. In this case, the first gNB may send a ResCoordConfig Request message to the second gNB such that by matching SBFD / TDD configurations on certain resources, the first gNB would be able to communicate with the UE on those resources. A similar principle may be applicable to centralized methods, such as signaling by the core network or a coordinating gNB or entity, with the difference that core network function or gNB or entity may receive CLI reports from other gNBs and / or UEs that trigger a signaling to form a new ResCoordConfig or add other (possibly interfering) gNBs to an existing ResCoordConfig.

[0108] In one or more implementations, and with reference to leaving or expiration of a ResCoordConfig, a gNB may leave a ResCoordConfig without notice. The gNB may change or update its SBFD / TDD configuration such that it no longer matches a coordinated SBFD / TDD configuration associated with the ResCoordConfig. This may imply leaving the ResCoordConfig without notice. No signaling may follow indicating to other gNBs, such as gNBs in the ResCoordConfig, that the gNB changes or updates its SBFD / TDD configuration. This method is simple to implement, but it may raise interference issues as other gNBs may not be informed of new upcoming interference.

[0109] In other implementations, a gNB may send to other gNBs a message indicating that the gNB is leaving the ResCoordConfig. The message may comprise a reference to the ResCoordConfig (e.g., a configuration ID, and an indication of leaving the ResCoordConfig). Then, other gNBs, such as neighbor gNBs or other gNBs in the ResCoordConfig, may infer that there may be new upcoming interference on the resources associated with the ResCoordConfig. In another implementation, a gNB may signal to other gNBs that it is leaving a ResCoordConfig by sending a changed or updated SBFD / TDD configuration that no longer matches a coordinated SBFD / TDDassociated with the ResCoordConfig. The changed or updated SBFD / TDD configuration may comprise an Intended SBFD Configuration IE and / or an Intended TDD UL-DL Configuration IE.

[0110] In one or more implementations, a ResCoordConfig may be timed or scheduled (i.e., the ResCoordConfig may be created or joined for a certain time interval). In this case, any or all of ResCoordConfig Request message, ResCoordConfig Response message, or other signaling may comprise a parameter that indicates a time interval for validity of the ResCoordConfig. Then, a gNB creating or joining the ResCoordConfig may start an expiration timer marking when the ResCoordConfig expires. Once the ResCoordConfig expires, its associated SBFD / TDD constraints on the associated resources will no longer be valid (i.e., the gNBs formerly a member of the ResCoordConfig may change or update DL / UL configurations of the associated resources or otherwise allocate the resources to signals or channels with arbitrary DL / UL directions).

[0111] In implementations, in order to avoid expiration of a ResCoordConfig, an entity may send a message renewing validity of the ResCoordConfig. The entity may be a core network function, a coordinating gNB or entity, a member of the ResCoordConfig, or the like. A gNB receiving the message may reset an associated expiration timer such that ResCoordConfig expires later. In another implementation, a gNB that is a member of a ResCoordConfig (that may not be originally timed or scheduled) may receive a message from another entity, such as a core network function or a coordinating gNB or entity, that the ResCoordConfig is being terminated. Upon receiving the message, the gNB may no longer match its SBFD / TDD configuration with that of the ResCoordConfig on the associated resources. Alternatively, the message may comprise an indication of a time interval after which the ResCoordConfig is going to be terminated. Upon receiving the message, the gNB may start an expiration timer associate with the ResCoordConfig. When the timer expires, the gNB may no longer match its SBFD / TDD configuration with that of the ResCoordConfig on the associated resources.

[0112] In one or more implementations, if a gNB joins or creates a ResCoordConfig, the gNB should remain in the ResCoordConfig for a minimum (and / or maximum) amount of time. The minimum (and / or maximum) may be specified by the standard, configured or signaled by the network, or determined by implementation. Similar to triggering conditions for creating or joining a ResCoordConfig, expiration or leaving a ResCoordConfig by a gNB may be triggered by certainconditions. In implementations, expiration or leaving a ResCoordConfig may be triggered by a first gNB no longer detecting an excessive interference from a second gNB.

[0113] In the case of gNB-to-gNB CLI, the first gNB may no longer detect an interference from the second gNB that exceeds a threshold. In this case, the first gNB may send to the second gNB a message indicating that the first gNB is leaving the ResCoordConfig. If the first gNB is a coordinating gNB or entity, it may send a message to gNB in the ResCoordConfig that the ResCoordConfig is terminating. The message may comprise an expiration period. Alternatively, if the first gNB is not a coordinating gNB or entity, it may send a message to a core network function of a coordinating gNB or entity that it no longer detects a large interference and / or it is requesting to leave the ResCoordConfig. The first gNB may then leave the ResCoordConfig wait for a response from the core network function or coordinating gNB or entity approving that the first gNB may leave the ResCoordConfig. The core network function or the coordinating gNB or entity may consider other factors, such as interference reports from other gNBs in the ResCoordConfig in order to accept the first gNB’s request to leave the ResCoordConfig.

[0114] Alternatively, in the case of UE-to-UE CLI, the first gNB may receive a CLI report (e.g., SRS-RSRP or CLI-RSSI) from a UE indicating that there is no longer an excessive interference from a UE served by the second gNB. In this case, the first gNB may send to the second gNB a message indicating that the first gNB is leaving the ResCoordConfig. If the first gNB is a coordinating gNB or entity, it may send a message to a gNB in the ResCoordConfig that the ResCoordConfig is terminating. The message may comprise an expiration period. Alternatively, if the first gNB is not a coordinating gNB or entity, it may send a message to a core network function or coordinating gNB or entity that it no longer detects a large interference and / or it is requesting to leave the ResCoordConfig. The first gNB may then leave the ResCoordConfig wait for a response from the core network function or coordinating gNB or entity approving that the first gNB may leave the ResCoordConfig. A similar principle may be applicable to centralized methods, such as signaling by the core network or a coordinating gNB or entity, with the difference that the core network function or coordinating gNB or entity may receive CLI reports from other gNBs and / or UEs that trigger a signaling to terminate a ResCoordConfig or allow a gNB to leave the ResCoordConfig.

[0115] In aspects of the present disclosure, the various techniques described for the example implementations may be permuted. Each configuration may be provided by one or multiple configurations in practice. An earlier configuration may provide a subset of parameters while a later configuration may provide another subset of parameters. Alternatively, a later configuration may override values provided by an earlier configuration or a pre-configuration. A configuration may be provided by an Xn / NG signaling, a radio resource control (RRC) signaling, a medium-access control (MAC) signaling, a physical layer signaling, such as a downlink control information (DCI) message, a combination thereof, or by other techniques. A configuration may include a (pre)configuration or a semi-static configuration provided by the standard, by the vendor, and / or by the network or operator (e.g., 0AM). Each parameter value received through a configuration or indication may override previous values for a similar parameter.

[0116] Additionally, L1 / L2 control signaling may refer to control signaling in layer 1 (physical layer) or layer 2 (data link layer). Particularly, an L1 / L2 control signaling may refer to an LI control signaling, such as a DCI message or a UCI message, an L2 control signaling such as a MAC message, or a combination thereof. A format and an interpretation of an L1 / L2 control signaling may be determined by the standard, a configuration, other control signaling, or a combination thereof.

[0117] In reference to a message or an information element (IE), and IE referred to in LTE and NR specifications refers to a configuration at layer 3 and higher. An IE may be comprised in a message from one layer to another layer, or from one entity to another entity. Alternatively, an IE may be comprised by another IE. In the present disclosure, the terms IE and message may be used interchangeably when the message comprises the IE directly or indirectly. Any parameter discussed in this disclosure may appear, in practice, as a linear function of that parameter in signaling or specifications.

[0118] In the present disclosure, reference to beam indication may refer to an indication of a reference signal by an ID or indicator, a resource associated with a reference signal, a spatial relation information comprising information of a reference signal or a reciprocal of a reference signal (in the case of beam correspondence). Despite reference to specific types of reference signals, such as CSI-RS, SRS, SSB, or the like, systems and methods are not limited in scope to the specific reference signals. In various implementations, other types of reference signals may be used, whichmay include reference signals specified for the purposes described in the present disclosure. Further, the terms parameter and value used herein for a parameter may be used interchangeably, and a parameter may be a sequence and / or array of parameters in various implementations.

[0119] Figure 12 illustrates an example of a UE 1200 in accordance with aspects of the present disclosure. The UE 1200 may include a processor 1202, a memory 1204, a controller 1206, and a transceiver 1208. The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0120] The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0121] The processor 1202 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202. The processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the UE 1200 to perform various functions of the present disclosure.

[0122] The memory 1204 may include volatile or non-volatile memory. The memory 1204 may store computer-readable, computer-executable code including instructions when executed by the processor 1202 cause the UE 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1204 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program fromone place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0123] In some implementations, the processor 1202 and the memory 1204 coupled with the processor 1202 may be configured to cause the UE 1200 to perform one or more of the functions described herein (e.g., executing, by the processor 1202, instructions stored in the memory 1204). For example, the processor 1202 may support wireless communication at the UE 1200 in accordance with examples as disclosed herein.

[0124] The controller 1206 may manage input and output signals for the UE 1200. The controller 1206 may also manage peripherals not integrated into the UE 1200. In some implementations, the controller 1206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1206 may be implemented as part of the processor 1202.

[0125] In some implementations, the UE 1200 may include at least one transceiver 1208. In some other implementations, the UE 1200 may have more than one transceiver 1208. The transceiver 1208 may represent a wireless transceiver. The transceiver 1208 may include one or more receiver chains 1210, one or more transmitter chains 1212, or a combination thereof.

[0126] A receiver chain 1210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1210 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 1210 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1210 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0127] A transmitter chain 1212 may be configured to generate and transmit signals(e.g., control information, data, packets). The transmitter chain 1212 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemeslike phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0128] Figure 13 illustrates an example of a processor 1300 in accordance with aspects of the present disclosure. The processor 1300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1300 may include a controller 1302 configured to perform various operations in accordance with examples as described herein. The processor 1300 may optionally include at least one memory 1304, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1300 may optionally include one or more arithmetic-logic units (ALUs) 1306. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0129] The processor 1300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1300) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0130] The controller 1302 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. For example, the controller 1302 may operate as a control unit of the processor 1300, generating control signals that manage the operation of various components of the processor 1300. These control signalsinclude enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0131] The controller 1302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1304 and determine subsequent instruction(s) to be executed to cause the processor 1300 to support various operations in accordance with examples as described herein. The controller 1302 may be configured to track memory addresses of instructions associated with the memory 1304. The controller 1302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1302 may be configured to manage flow of data within the processor 1300. The controller 1302 may be configured to control transfer of data between registers, ALUs 1306, and other functional units of the processor 1300.

[0132] The memory 1304 may include one or more caches (e.g., memory local to or included in the processor 1300 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1304 may reside within or on a processor chipset (e.g., local to the processor 1300). In some other implementations, the memory 1304 may reside external to the processor chipset (e.g., remote to the processor 1300).

[0133] The memory 1304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1300, cause the processor 1300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1302 and / or the processor 1300 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the processor 1300 to perform various functions. For example, the processor 1300 and / or the controller 1302 may be coupled with or to the memory 1304, the processor 1300, and the controller 1302, and may be configured to perform various functions described herein. In some examples, the processor 1300 may include multiple processors and the memory 1304 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiplememories, which may, individually or collectively, be configured to perform various functions herein.

[0134] The one or more ALUs 1306 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1306 may reside within or on a processor chipset (e.g., the processor 1300). In some other implementations, the one or more ALUs 1306 may reside external to the processor chipset (e.g., the processor 1300). One or more ALUs 1306 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1306 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1306 may be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1306 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1306 to handle conditional operations, comparisons, and bitwise operations.

[0135] The processor 1300 may support wireless communication in accordance with examples as disclosed herein. The processor 1300 may be configured to or operable to support at least one controller (e.g., the controller 1302) coupled with at least one memory (e.g., the memory 1304) and configured to cause the processor to obtain, at a first BS, a first RCC that coordinates one or more resources with one or more BSs; obtain, at the first BS, a resource configuration that indicates at least one frequency sub-band for SBFD operation; identify at least a second BS from the one or more BSs; and coordinate use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0136] Additionally, the processor 1300 may be configured to or operable to support any one or combination of to obtain the first RCC, the at least one controller is configured to cause the processor to at least one of: receive the first RCC from a core network, a core network function, or an 0AM entity; or receive the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface. To obtain the resource configuration, the at least one controller is configured to cause the processor to at least one of: receive the resource configuration from a core network, a core network function, or an 0AM entity; or receive the resource configuration from the at least second BS via one or more of a backhaul interface, or over an air interface. The at least oneresource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain. The at least one resource is indicated as one or more of a slot or a symbol. The first RCC includes a first configuration ID; the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, where the second RCC includes a second configuration ID; and where, to identify the at least second BS, the at least one processor is configured to cause the first BS to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource. The one or more BSs are indicated by one or more of a core network, a core network function, an OAM entity, by pre-configuration, or the at least second BS.

[0137] Additionally, or alternatively, to coordinate use of the at least one resource, the at least one controller is configured to cause the processor to match a direction of the wireless communication of the at least one resource with the at least second BS based on at least one of: the direction of the wireless communication is configured as downlink by the first BS and the at least second BS; the direction of the wireless communication is configured as uplink by the first BS and the at least second BS; the direction of the wireless communication is configured as flexible by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS based on a first determination that a second frequency sub-band configured on the at least one resource by the at least second BS is one of identical to, a subset of, or a superset of the at least one frequency sub-band configured on the resource by the first BS; the at least one resource is fully unused or partially unused based on a second determination that the second frequency sub-band configured on the at least one resource by the at least second BS is not identical to, the subset of, or the superset of the at least one frequency sub-band configured on the resource by the first BS; or a boundary of the direction of the wireless communication is matched between the first BS and the at least second BS at a slot level, a symbol level, a sub-band level, or a combination thereof.

[0138] Additionally, or alternatively, the at least one controller is configured to cause the processor to decline to match a direction of the wireless communication for the at least one resource with the at least second BS based on a signal or a channel that includes at least one of: the signal or the channel with a high priority; one or more of a reference signal, a control channel, a semi-persistent scheduled channel, a configured-grant channel, or a random access channel; or the signal or the channel configured as an exception for resource coordination. The at least one controller is configured to cause the processor to coordinate use of the one or more resources to manage CLI between the first BS and the at least second BS.

[0139] Figure 14 illustrates an example of an NE 1400 in accordance with aspects of the present disclosure. The NE 1400 may include a processor 1402, a memory 1404, a controller 1406, and a transceiver 1408. The processor 1402, the memory 1404, the controller 1406, or the transceiver 1408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces. As described herein, an NE may include any one or combination of a BS, a gNB, a cell, core network equipment, and / or any other types of devices and network equipment in a wireless communications system.

[0140] The processor 1402, the memory 1404, the controller 1406, or the transceiver 1408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0141] The processor 1402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1402 may be configured to operate the memory 1404. In some other implementations, the memory 1404 may be integrated into the processor 1402. The processor 1402 may be configured to execute computer-readable instructions stored in the memory 1404 to cause the NE 1400 to perform various functions of the present disclosure.

[0142] The memory 1404 may include volatile or non-volatile memory. The memory 1404 may store computer-readable, computer-executable code including instructions when executed by the processor 1402 cause the NE 1400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1404 or another type ofmemory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0143] In some implementations, the processor 1402 and the memory 1404 coupled with the processor 1402 may be configured to cause the NE 1400 to perform one or more of the functions described herein (e.g., executing, by the processor 1402, instructions stored in the memory 1404). For example, the processor 1402 may support wireless communication at the NE 1400 in accordance with examples as disclosed herein. The NE 1400 may be configured to or operable as a BS to support a means for obtaining a first RCC that coordinates one or more resources with one or more BSs; obtaining a resource configuration that indicates at least one frequency sub-band for SBFD operation; identifying at least a second BS from the one or more BSs; and coordinating use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0144] Additionally, the NE 1400 may be configured to or operable to support any one or combination of to obtain the first RCC, the method further comprising at least one of: receiving the first RCC from a core network, a core network function, or an 0AM entity; or receiving the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface. To obtain the resource configuration, the method further comprising at least one of: receiving the resource configuration from a core network, a core network function, or an 0AM entity; or receiving the resource configuration from the at least second BS via one or more of a backhaul interface, or over an air interface. The at least one resource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain. The at least one resource is indicated as one or more of a slot or a symbol. The first RCC includes a first configuration ID; the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, where the second RCC includes a second configuration ID; and where, to identify the at least second BS, the method further comprising causing the first BS to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource. The one or more BSs areindicated by one or more of a core network, a core network function, an OAM entity, by preconfiguration, or the at least second BS.

[0145] Additionally, or alternatively, to coordinate use of the at least one resource, the method further comprising matching a direction of a wireless communication of the at least one resource with the at least second BS based on at least one of: the direction of the wireless communication is configured as downlink by the first BS and the at least second BS; the direction of the wireless communication is configured as uplink by the first BS and the at least second BS; the direction of the wireless communication is configured as flexible by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS based on a first determination that a second frequency sub-band configured on the at least one resource by the at least second BS is one of identical to, a subset of, or a superset of the at least one frequency sub-band configured on the resource by the first BS; the at least one resource is fully unused or partially unused based on a second determination that the second frequency sub-band configured on the at least one resource by the at least second BS is not identical to, the subset of, or the superset of the at least one frequency sub-band configured on the resource by the first BS; or a boundary of the direction of the wireless communication is matched between the first BS and the at least second BS at a slot level, a symbol level, a sub-band level, or a combination thereof.

[0146] Additionally, or alternatively, the method further comprising declining to match a direction of a wireless communication for the at least one resource with the at least second BS based on a signal or a channel that includes at least one of: the signal or the channel with a high priority; one or more of a reference signal, a control channel, a semi-persistent scheduled channel, a configured-grant channel, or a random access channel; or the signal or the channel configured as an exception for resource coordination. The method further comprising coordinating use of the one or more resources to manage CLI between the first BS and the at least second BS.

[0147] Additionally, or alternatively, the NE 1400 may support at least one memory (e.g., the memory 1404) and at least one processor (e.g., the processor 1402) coupled with the at least one memory and configured to cause the NE (e.g., a first BS) to obtain a first RCC that coordinates one or more resources with one or more BSs; obtain a resource configuration that indicates at least onefrequency sub-band for SBFD operation; identify at least a second BS from the one or more BSs; and coordinate use of at least one resource of the one or more resources by the at least second BS based on the resource configuration.

[0148] Additionally, the NE 1400 may be configured to support any one or combination of to obtain the first RCC, the at least one processor is configured to cause the first BS to at least one of: receive the first RCC from a core network, a core network function, or an 0AM entity; or receive the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface. To obtain the resource configuration, the at least one processor is configured to cause the first BS to at least one of: receive the resource configuration from a core network, a core network function, or an 0AM entity; or receive the resource configuration from the at least second BS via one or more of a backhaul interface, or over an air interface. The at least one resource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain. The at least one resource is indicated as one or more of a slot or a symbol. The first RCC includes a first configuration ID; the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, where the second RCC includes a second configuration ID; and where, to identify the at least second BS, the at least one processor is configured to cause the first BS to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource. The one or more BSs are indicated by one or more of a core network, a core network function, an 0AM entity, by pre-configuration, or the at least second BS.

[0149] Additionally, or alternatively, to coordinate use of the at least one resource, the at least one processor is configured to cause the first BS to match a direction of the wireless communication of the at least one resource with the at least second BS based on at least one of: the direction of the wireless communication is configured as downlink by the first BS and the at least second BS; the direction of the wireless communication is configured as uplink by the first BS and the at least second BS; the direction of the wireless communication is configured as flexible by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS; the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS based on a first determination that a second frequency sub-band configured on the at least one resource by the at least second BS is one ofidentical to, a subset of, or a superset of the at least one frequency sub-band configured on the resource by the first BS; the at least one resource is fully unused or partially unused based on a second determination that the second frequency sub-band configured on the at least one resource by the at least second BS is not identical to, the subset of, or the superset of the at least one frequency sub-band configured on the resource by the first BS; or a boundary of the direction of the wireless communication is matched between the first BS and the at least second BS at a slot level, a symbol level, a sub-band level, or a combination thereof.

[0150] Additionally, or alternatively, the at least one processor is configured to cause the first BS to decline to match a direction of the wireless communication for the at least one resource with the at least second BS based on a signal or a channel that includes at least one of: the signal or the channel with a high priority; one or more of a reference signal, a control channel, a semi-persistent scheduled channel, a configured-grant channel, or a random access channel; or the signal or the channel configured as an exception for resource coordination. The at least one processor is configured to cause the first BS to coordinate use of the one or more resources to manage CLI between the first BS and the at least second BS.

[0151] In another example, the processor 1402 may support wireless communication at the NE 1400 in accordance with examples as disclosed herein. The NE 1400 may be configured to or operable as a core network entity to support a means for determining a first BS that causes CLI with at least a second BS; transmitting, to the first BS, a first RCC that coordinates one or more resources with the at least second BS; and transmitting, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0152] Additionally, the NE 1400 may be configured to or operable to support any one or combination of one or more of the first BS or the at least second BS is identifiable based on one or more of: a geographical proximity of the first BS to the at least second BS; a first indication that the first BS configures a first SBFD operation on the one or more resources; a second indication that the at least second BS configures a second SBFD operation on the one or more resources; or a CLI report received from the at least second BS, the CLI report indicating the CLI with the first BS. A third RCC coordinates one or more additional resources with a third BS; and the method further comprising determining that the one or more resources should not overlap with the one or moreadditional resources based on a determination that at least one cell of the third BS overlaps with at least one cell of the first BS or the second BS.

[0153] Additionally, or alternatively, the NE 1400 may support at least one memory (e.g., the memory 1404) and at least one processor (e.g., the processor 1402) coupled with the at least one memory and configured to cause the NE (e.g., a core network entity) to determine a first BS that causes CLI with at least a second BS; transmit, to the first BS, a first RCC that coordinates one or more resources with the at least second BS; and transmit, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

[0154] Additionally, the NE 1400 may be configured to support any one or combination of the one or more of the first BS or the at least second BS is identifiable based on one or more of: a geographical proximity of the first BS to the at least second BS; a first indication that the first BS configures a first SBFD operation on the one or more resources; a second indication that the at least second BS configures a second SBFD operation on the one or more resources; or a CLI report received from the at least second BS, the CLI report indicating the CLI with the first BS. A third RCC coordinates one or more additional resources with a third BS; and the at least one processor is configured to cause the NE to determine that the one or more resources should not overlap with the one or more additional resources based on a determination that at least one cell of the third BS overlaps with at least one cell of the first BS or the second BS.

[0155] The controller 1406 may manage input and output signals for the NE 1400. The controller 1406 may also manage peripherals not integrated into the NE 1400. In some implementations, the controller 1406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1406 may be implemented as part of the processor 1402.

[0156] In some implementations, the NE 1400 may include at least one transceiver 1408. In some other implementations, the NE 1400 may have more than one transceiver 1408. The transceiver 1408 may represent a wireless transceiver. The transceiver 1408 may include one or more receiver chains 1410, one or more transmitter chains 1412, or a combination thereof.

[0157] A receiver chain 1410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1410 may include one ormore antennas to receive a signal over the air or wireless medium. The receiver chain 1410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1410 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0158] A transmitter chain 1412 may be configured to generate and transmit signals(e.g., control information, data, packets). The transmitter chain 1412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0159] Figure 15 illustrates a flowchart of a method 1500 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a BS as described herein. In some implementations, the BS may execute a set of instructions to control the function elements of the BS to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0160] At 1502, the method may include obtaining a first RCC that coordinates one or more resources with one or more BSs. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a BS as described with reference to Figure 14.

[0161] At 1504, the method may include obtaining a resource configuration that indicates at least one frequency sub-band for SBFD operation. The operations of 1504 may be performed inaccordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a BS as described with reference to Figure 14.

[0162] At 1506, the method may include identifying at least a second BS from the one or more BSs. The operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed a BS as described with reference to Figure 14.

[0163] At 1508, the method may include coordinating use of at least one resource of the one or more resources by the at least second BS based on the resource configuration. The operations of 1508 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1508 may be performed a BS as described with reference to Figure 14.

[0164] Figure 16 illustrates a flowchart of a method 1600 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0165] At 1602, the method may include determining a first BS that causes CLI with at least a second BS. The operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by an NE as described with reference to Figure 14.

[0166] At 1604, the method may include transmitting, to the first BS, a first RCC that coordinates one or more resources with the at least second BS. The operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by an NE as described with reference to Figure 14.

[0167] At 1606, the method may include transmitting, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS. The operations of 1606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1606 may be performed an NE as described with reference to Figure 14.

[0168] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A first base station (BS) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the first BS to: obtain a first resource coordination configuration (RCC) that coordinates one or more resources with one or more base stations (BSs); obtain a resource configuration that indicates at least one frequency sub-band for sub-band full-duplex (SBFD) operation; identify at least a second BS from the one or more BSs; and coordinate use of at least one resource of the one or more resources by the at least second BS based at least in part on the resource configuration.

2. The first BS of claim 1, wherein, to obtain the first RCC, the at least one processor is operable to cause the first BS to at least one of: receive the first RCC from a core network, a core network function, or an operations, administration, and management (OAM) entity; or receive the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface.

3. The first BS of claim 1, wherein, to obtain the resource configuration, the at least one processor is operable to cause the first BS to at least one of: receive the resource configuration from a core network, a core network function, or an operations, administration, and management (OAM) entity; or receive the resource configuration from the at least second BS via one or more of a backhaul interface, or over an air interface.

4. The first BS of claim 1, wherein the at least one resource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain.

5. The first BS of claim 1, wherein the at least one resource is indicated as one or more of a slot or a symbol.

6. The first BS of claim 1, wherein: the first RCC includes a first configuration identifier (ID); the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, wherein the second RCC includes a second configuration ID; and wherein, to identify the at least second BS, the at least one processor is operable to cause the first BS to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource.

7. The first BS of claim 1, wherein the one or more BSs are indicated by one or more of a core network, a core network function, an operations, administration, and management (OAM) entity, by pre-configuration, or the at least second BS.

8. The first BS of claim 1, wherein, to coordinate use of the at least one resource, the at least one processor is configured to cause the first BS to match a direction of the wireless communication of the at least one resource with the at least second BS based on the direction of the wireless communication is configured as the SBFD by the first BS and the at least second BS.

9. The first BS of claim 1, wherein the at least one processor is operable to cause the first BS to decline to match a direction of the wireless communication for the at least one resource with the at least second BS based at least in part on a signal or a channel that includes at least one of: the signal or the channel with a high priority; one or more of a reference signal, a control channel, a semi-persistent scheduled channel, a configured-grant channel, or a random access channel; or the signal or the channel configured as an exception for resource coordination.

10. The first BS of claim 1, wherein the at least one processor is operable to cause the first BS to coordinate use of the one or more resources to manage cross-link interference (CLI) between the first BS and the at least second BS.

11. A method performed by a first base station (BS), the method comprising: obtaining a first resource coordination configuration (RCC) that coordinates one or more resources with one or more base stations (BSs); obtaining a resource configuration that indicates at least one frequency sub-band for sub-band full-duplex (SBFD) operation; identifying at least a second BS from the one or more BSs; and coordinating use of at least one resource of the one or more resources by the at least second BS based at least in part on the resource configuration.

12. The method of claim 11, wherein: to obtain the first RCC, the method further comprising at least one of: receiving the first RCC from a core network, a core network function, or an operations, administration, and management (0AM) entity; or receiving the first RCC from the at least second BS via one or more of a backhaul interface, or over an air interface; and to obtain the resource configuration, the method further comprising at least one of: receiving the resource configuration from a core network, a core network function, or the 0AM entity; or receiving the resource configuration from the at least second BS via one or more of the backhaul interface, or over the air interface.

13. The method of claim 11, wherein the at least one resource is indicated in one or more of a time domain, a frequency domain, a spatial domain, or a code domain, and wherein the at least one resource is indicated as one or more of a slot or a symbol.

14. The method of claim 11, wherein: the first RCC includes a first configuration identifier (ID); the at least second BS is configured with a second RCC that coordinates one or more additional resources with the one or more BSs, wherein the second RCC includes a second configuration ID; and wherein, to identify the at least second BS, the method further comprising causing the first BS to determine that the first configuration ID is identical to the second configuration ID, and determine that the one or more additional resources include the at least one resource.

15. The method of claim 11, wherein the one or more BSs are indicated by one or more of a core network, a core network function, an operations, administration, and management (OAM) entity, by pre-configuration, or the at least second BS.

16. A network equipment (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the NE to: determine a first base station (BS) that causes cross-link interference (CLI) with at least a second BS; transmit, to the first BS, a first resource coordination configuration (RCC) that coordinates one or more resources with the at least second BS; and transmit, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

17. The NE of claim 16, wherein one or more of the first BS or the at least second BS is identifiable based at least in part on one or more of: a geographical proximity of the first BS to the at least second BS; a first indication that the first BS configures a first sub-band full-duplex (SBFD) operation on the one or more resources; a second indication that the at least second BS configures a second SBFD operation on the one or more resources; or a CEI report received from the at least second BS, the CEI report indicating the CEI with the first BS.

18. The NE of claim 16, wherein: a third RCC coordinates one or more additional resources with a third BS; and the at least one processor is configured to cause the NE to determine that the one or more resources should not overlap with the one or more additional resources based at least in part on a determination that at least one cell of the third BS overlaps with at least one cell of the first BS or the second BS.

19. A method performed by a network equipment (NE), the method comprising: determining a first base station (BS) that causes cross-link interference (CLI) with at least a second BS; transmitting, to the first BS, a first resource coordination configuration (RCC) that coordinates one or more resources with the at least second BS; and transmitting, to the at least second BS, a second RCC that coordinates the one or more resources with the at least second BS.

20. The method of claim 19, wherein one or more of the first BS or the at least second BS is identifiable based at least in part on one or more of: a geographical proximity of the first BS to the at least second BS; a first indication that the first BS configures a first sub-band full-duplex (SBFD) operation on the one or more resources; a second indication that the at least second BS configures a second SBFD operation on the one or more resources; or a CLI report received from the at least second BS, the CLI report indicating the CLI with the first BS.

Images