Perception-Based Interference Mitigation in NR Feedback

Abstract

A wireless transmit / receive unit (WTRU) may include a processor configured to receive configuration information indicating a plurality of sub-bands for cross-link interference (CLI) measurement and respective resources for performing CLI measurement for each of the plurality of sub-bands. The processor may receive downlink control information (DCI) indicating resources associated with a first reference sub-band. The processor may perform CLI measurement for the first reference sub-band using one or more resources for performing CLI measurement for the first sub-band. Based on determining that the CLI measurement value for the first sub-band is greater than a threshold, the processor may perform CLI measurement for at least one other sub-band of the plurality of sub-bands using respective resources for CLI measurement for at least one other sub-band. The processor may send an indication that the CLI measurement value for the sub-band is greater than the threshold.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 334,991, filed Apr. 26, 2022, which is hereby incorporated by reference in its entirety.

Background Art

[0002] Wireless communication has become one of the most successful innovations in modern history. Due to the increasing popularity among consumers and enterprises of smartphones and other mobile data devices such as tablets, notebook computers, netbooks, e - book readers, and machine - type devices, the demand for wireless data traffic has been increasing rapidly. To meet the high growth of mobile data traffic and support new applications and deployments, improving wireless interface efficiency and coverage is extremely important.

Summary of the Invention

[0003] The present disclosure generally relates to devices, methods, and systems for handling interference. More specifically, the present disclosure relates to mitigating interference in NR duplexing. For example, the present disclosure provides, among other things, sub - band - based channel and / or interference sensing in a victim wireless transmit / receive unit (WTRU). In another example, the present disclosure provides, among other things, avoidance reporting after sensing (ARAS). Further, the present disclosure provides, among other things, post - sensing transmission concession in an aggressor WTRU. Additionally, the present disclosure provides, among other things, directional CLI sensing and measurement.

[0004] In one or more aspects, the present disclosure relates to methods and apparatuses implemented to mitigate interference in NR retransmission. For example, a victim WTRU receives a measurement and reporting configuration for one or more reference sub-bands. The victim WTRU, in one example, receives a trigger to sense / measure interference sensing / measurement. The victim WTRU, in one example, measures a Cross Link Interference-Received Signal Strength Indicator (CLI-RSSI), or a Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP) over the configured frequency / sub-band resources as a whole. The victim WTRU, in one example, reports the CLI-RSSI or SRS-RSRP measurement via L1 signaling. The victim WTRU, in one example, requests to switch to another reference sub-band when the WTRU is not sensing interference.

[0005] In one or more aspects, an aggressor WTRU, in one example, determines one or more reference sub-bands to which the WTRU can switch when CLI is caused to the victim WTRU in the active SB. The aggressor WTRU, in one example, performs event-based CLI / channel occupancy sensing in the active SB.

[0006] In one or more aspects, the WTRU receives group common DCI. The WTRU, in one example, measures SRS-RSRP from one or more aggressor WTRUs based on directional measurements. The WTRU, in one example, reports directional CLI / channel sensing.

[0007] A wireless transmit / receive unit (WTRU) may include a processor configured to receive configuration information indicating a plurality of sub-bands for cross-link interference (CLI) measurement and respective resources for performing CLI measurement for each of the plurality of sub-bands. The processor may receive a downlink allocation and / or downlink control information (DCI) indicating resources associated with a first reference sub-band. The processor may perform CLI measurement for the first reference sub-band using one or more resources for performing CLI measurement for the first sub-band. Based on determining that the CLI measurement value for the first sub-band is greater than a threshold, the processor may perform CLI measurement for at least one other sub-band of the plurality of sub-bands using respective resources for CLI measurement for the at least one other sub-band. The processor may send an indication that the CLI measurement value for the sub-band is greater than the threshold.

[0008] The processor may be configured to send information indicating a second sub-band. The second sub-band indicated is determined to have the lowest measured CLI among the plurality of sub-bands.

[0009] The processor may be configured to perform CLI measurement for the first sub-band based on any combination of factors, such as the number of downlink data reception failures for the first sub-band exceeding a first threshold, the number of hybrid automatic repeat request negative acknowledgements (HARQ NACKs) sent by the WTRU for transmission in the first sub-band exceeding a second threshold, and / or an explicit indication received from the network.

[0010] Each respective resource for performing CLI measurements for each of a plurality of sub-bands may include one or more of a zero power channel state information reference signal (ZP-CSI-RS), a non-zero power channel state information reference signal (NZP-CSI-RS), or a sounding reference signal (SRS).

[0011] DCI may include a downlink (DL) allocation indicating a first reference sub-band for scheduling a physical downlink shared channel (PDSCH).

[0012] The processor may be configured to perform CLI measurements for at least one other sub-band by performing one or more of physical layer cross-link interference received signal strength indicator (L1-CLI-RSSI) measurements, sub-band unit CLI measurements, or delta CLI measurements. In some examples, the CLI measurements may include overlapping CLI, partially overlapping CLI, or non-overlapping sub-band CLI.

Brief Description of the Drawings

[0013] A more detailed understanding can be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals in the figures indicate like elements.

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 2

Figure 3

Figure 4

[0014] FIG. 1A is a diagram illustrating an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to a plurality of wireless users. The communication system 100 may enable a plurality of wireless users to access such content through sharing of system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC).

[0015] As shown in Figure 1A, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. It will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, which may each be referred to as a "station" and / or "STA," can be configured to transmit and / or receive wireless signals and can be user equipment (UE), a mobile station, a fixed subscriber unit or a mobile subscriber unit, a subscriber-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or a Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., for remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in an industrial and / or automated processing chain context), a home appliance device, a device operating in a commercial wireless network and / or an industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.

[0016] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks such as CN106 / 115, Internet 110, and / or other network 112. By way of example, base stations 114a, 114b may be a base transceiver station (BTS), Node B, eNode B, home Node B, home eNode B, gNB, NR Node B, site controller, access point (AP), wireless router, etc. Although base stations 114a, 114b are each depicted as a single element, it will be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0017] Base station 114a can be part of RAN 104 / 113 and can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. Base station 114a and / or base station 114b can be configured to transmit and / or receive radio signals at one or more carrier frequencies, which can be referred to as a cell (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectra. The cell can provide coverage of wireless services in a relatively fixed or time-varying specific geographic area. The cell can be further divided into cell sectors. For example, the cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a can include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a can employ multiple-input multiple-output (MIMO) technology and can utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0018] Base stations 114a, 114b can communicate with one or more of WTRUs 102a, 102b, 102c, 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

[0019] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a within RAN104 / 113 and the WTRUs 102a, 102b, 102c may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (WCDMA) to establish the air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0020] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish the air interface 116.

[0021] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access, which may use New Radio (NR) technology to establish the air interface 116.

[0022] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example, using the dual connectivity (DC) principle. Accordingly, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by transmissions sent to / from multiple types of radio access technologies and / or multiple types of base stations (e.g., eNBs and gNBs).

[0023] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard (IS)-2000, IS-95, IS-856, Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0024] The base station 114b in Fig. 1A can be, for example, a wireless router, a home node B, a home e-node B, or an access point, and can utilize any suitable RAT to facilitate wireless connections in a local area such as an office, a home, a vehicle, a campus, an industrial facility, an aerial corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a pico cell or a femto cell. As shown in Fig. 1A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0025] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. The data can have various quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video delivery, etc., and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that employ the same or a different radio access technology (RAT) as RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which can utilize New Radio (NR) radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0026] CN106 / 115 may also serve as a gateway for WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides a plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, and these networks and devices use a common communication protocol such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include a wired communication network and / or a wireless communication network that is owned and / or operated by another service provider. For example, the network 112 may include another CN connected to one or more RANs that may use the same RAT or a different RAT as the RAN 104 / 113.

[0027] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include a multimode function (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, the WTRU 102c shown in Figure 1A may be configured to communicate with a base station 114a that may employ a cellular-based wireless technology and a base station 114b that may employ IEEE 802 wireless technology.

[0028] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138. It will be understood that the WTRU 102 may include any partial combination of the foregoing elements while remaining consistent with one embodiment.

[0029] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuits (ASIC), a Field Programmable Gate Arrays (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to a transmit / receive element 122. Although Figure 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0030] The transmit / receive element 122 may be configured to transmit or receive signals to / from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR signals, UV signals, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF signals and optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0031] Although the transmit / receive element 122 is depicted in FIG. 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 116.

[0032] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have a multimode capability. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs such as, for example, NR and IEEE 802.11.

[0033] The processor 118 of the WTRU 102 can be coupled to the speaker / microphone 124, keypad 126, and / or display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit), and can receive data input by a user from these. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from any suitable type of memory, such as the non-removable memory 130 and / or the removable memory 132, and can store data in the memory. The non-removable memory 130 can include a random-access memory (RAM), read-only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc. In other embodiments, the processor 118 can access information from a memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and can store data in the memory.

[0034] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 can include one or more dry cells (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0035] Processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of WTRU 102. In addition to, or instead of, information from the GPS chipset 136, WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via air interface 116 and / or may determine its location based on the timing of signals received from two or more neighboring base stations. It will be understood that WTRU 102 may obtain location information by any suitable location determination method while remaining consistent with one embodiment.

[0036] Processor 118 may also be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connections. For example, peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality / Augmented Reality (VR / AR) device, an activity tracker, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0037] WTRU102 may include a full-duplex radio in which some or all of the transmission and reception of signals associated with a particular subframe (e.g., for both UL (e.g., for transmission) and downlink (e.g., for reception)) can be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference either through hardware (e.g., choke) or signal processing (e.g., through a separate processor (not shown) or through processor 118). In one embodiment, the WRTU102 may include a half-duplex radio for the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either UL (e.g., for transmission) or downlink (e.g., for reception)).

[0038] Figure 1C is a system diagram illustrating RAN104 and CN106 according to one embodiment. As described above, RAN104 may employ E-UTRA radio technology to communicate with WTRU102a, 102b, 102c via air interface 116. RAN104 may also communicate with CN106.

[0039] RAN104 may include eNodeBs 160a, 160b, 160c, although it will be understood that RAN104 may include any number of eNodeBs while remaining consistent with one embodiment. Each of eNodeBs 160a, 160b, 160c may include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 116. In one embodiment, eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, eNodeB 160a, for example, may transmit wireless signals to and / or receive wireless signals from WTRU102a using multiple antennas.

[0040] Each of the eNodeBs 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the UL and / or DL, etc. As shown in Figure 1C, the eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0041] CN 106 shown in Figure 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Each of the foregoing elements is depicted as part of CN 106, but it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0042] The MME 162 can be connected to each of the eNodeBs 162a, 162b, and 162c in the RAN 104 via the S1 interface and can function as a control node. For example, the MME 162 can authenticate users of the WTRUs 102a, 102b, 102c, activate / deactivate bearers, select a specific serving gateway during the initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 can provide control plane functions for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies such as GSM and / or WCDMA.

[0043] SGW164 can be connected to each of the eNodeBs 160a, 160b, and 160c in RAN104 via the S1 interface. SGW164 can generally route and transfer user data packets between the WTRUs 102a, 102b, and 102c. SGW164 can perform other functions such as the function of anchoring the user plane during handover between eNodeBs, the function of triggering paging when DL data is available to the WTRUs 102a, 102b, and 102c, and the function of managing and storing the contexts of the WTRUs 102a, 102b, and 102c.

[0044] SGW164 can be connected to PGW166, and PGW166 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, and 102c to facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0045] CN106 can facilitate communication with other networks. For example, CN106 can provide access to a circuit-switched network such as PSTN108 to the WTRUs 102a, 102b, and 102c to facilitate communication between the WTRUs 102a, 102b, and 102c and conventional landline communication devices. For example, CN106 can include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between CN106 and PSTN108. In addition, CN106 can provide the WTRUs 102a, 102b, and 102c with access to another network 112, which can include other wired and / or wireless networks owned and / or operated by other service providers.

[0046] The WTRU is described as a wireless terminal in FIGS. 1A - 1D, but in certain representative embodiments, it is contemplated that such a terminal can use (e.g., temporarily or permanently) a wired communication interface with the communication network.

[0047] In a representative embodiment, the other network 112 can be a WLAN.

[0048] A WLAN in infrastructure basic service set (BSS) mode can have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP can have access or an interface to another type of wired / wireless network that carries traffic entering and / or exiting the distribution system (DS) or BSS. Traffic destined for an STA that originates outside the BSS can reach and be delivered to the STA through the AP. Traffic originating from an STA and destined for a destination outside the BSS can be sent to the AP so as to be delivered to their respective destinations. Traffic between STAs within the BSS can be sent, for example, through the AP, where the source STA can send the traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between the source STA and the destination STA (e.g., directly between them) using direct link setup (DLS). In a particular representative embodiment, DLS can use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) can communicate directly with each other. The IBSS mode of communication can be referred to herein as the "ad hoc" communication mode.

[0049] When using the 802.11ac infrastructure operation mode or a similar operation mode, the AP may transmit beacons on a fixed channel such as the primary channel. The primary channel may have a fixed width (e.g., a 20 MHz bandwidth) or a width dynamically set via signaling. The primary channel may be the operating channel of the BSS, but can be used by the STA to establish a connection with the AP. In certain representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented. In the case of CSMA / CA, STAs including the AP (e.g., all STAs) may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. Only one STA (e.g., only one station) may transmit at any given time in a given BSS.

[0050] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, and this 40 MHz wide channel may be formed, for example, via a combination of the primary 20 MHz channel and an adjacent or non - adjacent 20 MHz channel.

[0051] A Very High Throughput (VHT) STA may support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel may be formed by combining a plurality of adjacent 20 MHz channels. A 160 MHz channel may be formed by combining eight consecutive 20 MHz channels or by combining two non-adjacent 80 MHz channels, which may be referred to as an 80+80 configuration. In the case of the 80+80 configuration, after channel encoding, the data may pass through a segment parser that can divide the data into two streams. The Inverse Fast Fourier Transform (IFFT) process and the time domain process may be performed separately for each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0052] The sub-1 GHz operating mode is supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier frequency are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to an exemplary embodiment, 802.11ah may support meter type control / machine type communication, such as MTC devices within a macro communication range area. The MTC device may have limited capabilities, including certain capabilities, such as support for a certain and / or limited bandwidth (e.g., supporting only these). The MTC device may include a battery having a battery life above a threshold (e.g., to maintain a very long battery life).

[0053] A WLAN system that supports multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes channels that can be designated as primary channels. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in a BSS. The bandwidth of the primary channel can be set and / or restricted by an STA from among all STAs operating in a BSS that supports a minimum bandwidth operation mode. In an example of 802.11ah, the primary channel can be 1 MHz wide for an STA (e.g., an MTC type device) that supports (e.g., supports only) the 1 MHz mode even when an AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or Network Allocation Vector (NAV) setting can depend on the status of the primary channel. For example, due to an STA transmitting to an AP (supporting only the 1 MHz operation mode), when the primary channel is in operation, most of the frequency band remains in an operation pause and, even if it can be available, the entire available frequency band can be considered to be in operation.

[0054] In the United States, the available frequency band that can be used by 802.11ah is 902 MHz to 928 MHz. In Korea, the available frequency band is 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

[0055] FIG. 1D is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 113 can also communicate with CN 115.

[0056] RAN 113 may include gNBs 180a, 180b, 180c, but it will be understood that RAN 113 may include any number of gNBs while remaining consistent with one embodiment. Each of gNBs 180a, 180b, 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, 102c via air interface 116. In one embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, 180c. Thus, gNB 180a may transmit and / or receive radio signals to / from WTRU 102a using, for example, multiple antennas. In one embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of such component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmission from gNB 180a and gNB 180b (and / or gNB 180c).

[0057] WTRU 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable numerology. For example, the OFDM symbol interval and / or the OFDM sub-carrier interval can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using sub-frames or transmission time intervals (TTIs) of various or scalable lengths (e.g., including various numbers of OFDM symbols and / or having absolute times of various lengths).

[0058] gNBs 180a, 180b, and 180c may be configured to communicate with WTRUs 102a, 102b, and 102c in a stand-alone configuration and / or a non-stand-alone configuration. In a stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c, etc.). In a stand-alone configuration, WTRUs 102a, 102b, and 102c may utilize one or more of gNBs 180a, 180b, and 180c as mobility anchor points. In a stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with and connect to gNBs 180a, 180b, and 180c while also communicating with and connecting to another RAN such as eNodeBs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c may implement a DC principle for communicating with one or more gNBs 180a, 180b, and 180c and one or more eNodeBs 160a, 160b, and 160c substantially simultaneously. In a non-stand-alone configuration, eNodeBs 160a, 160b, and 160c may function as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, and 102c.

[0059] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decision-making, handover decision-making, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0060] As shown in FIG. 1D, CN 115 can include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and optionally data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of CN 115, it will be understood that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0061] AMF 182a and 182b can be connected to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can function as control nodes. For example, AMF 182a and 182b can play roles such as authentication of users of WTRUs 102a, 102b, and 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selection of specific SMFs 183a and 183b, management of registration areas, termination of NAS signaling, and mobility management. Network slices can be used by AMF 182a and 182b to customize the CN support for WTRUs 102a, 102b, and 102c based on the type of service being utilized by WTRUs 102a, 102b, and 102c. For example, different network slices can be established for different use cases such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, and services for machine type communication (MTC) access. AMF 162 can provide control plane functions for exchange between RAN 113 and other RANs (not shown) that use other radio technologies such as non-3GPP access technologies like LTE, LTE-A, LTE-A Pro, and / or WiFi.

[0062] SMF183a and 183b can be connected to AMF182a and 182b within CN115 via the N11 interface. SMF183a and 183b can also be connected to UPF184a and 184b within CN115 via the N4 interface. SMF183a and 183b can select and control UPF184a and 184b, and configure the routing of traffic passing through UPF184a and 184b. SMF183a and 183b can perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. The PDU session type can be IP-based, non-IP-based, Ethernet-based, etc.

[0063] UPF184a and 184b can be connected to one or more of gNB180a, 180b, and 180c within RAN113 via the N3 interface, thereby providing WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-corresponding devices. UPF184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-home PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0064] CN115 may facilitate communication with other networks. For example, CN115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between CN115 and PSTN108. Additionally, CN115 may provide access to other network 112 to WTRU102a, 102b, 102c, and this other network may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRU102a, 102b, 102c may be connected to local data network (DN) 185a, 185b through UPF184a, 184b via an N3 interface to UPF184a, 184b and an N6 interface between UPF184a, 184b and DN185a, 185b.

[0065] In view of FIGS. 1A - 1D and the corresponding descriptions thereof, one or more of the functions described herein with respect to one or more of WTRU102a - d, base stations 114a and b, eNode - Bs 160a - c, MME162, SGW164, PGW166, gNBs 180a - c, AMFs 182a - ab, UPFs 184a and b, SMFs 183a and b, DNs 185a and b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functionality.

[0066] An emulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, one or more emulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more emulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. An emulation device can be directly coupled to another device and / or use terrestrial wireless communication to perform tests for testing purposes.

[0067] One or more emulation devices can perform one or more functions including all while not being implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device can be utilized in a test scenario in a test laboratory and / or in a non-deployed (e.g., for testing) wired and / or wireless communication network to implement tests of one or more components. One or more emulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit (which can include one or more antennas) can be used by an emulation device to transmit and / or receive data.

[0068] In this specification, among others, the following abbreviations and acronyms are used: Subcarrier Spacing (Δf), NR Node B (gNB), Aperiodic (AP), Beam Failure Recovery (BFR), Beam Failure Detection - Reference Signal (BFD-RS), Block Error Rate (BLER), Bandwidth Part (BWP), Carrier Aggregation (CA), Contention-Based (CB) (e.g., access, channel, resource), Clear Channel Assessment (CCA), Code Division Multiplexing (CDM), Cell Group (CG), Cross-Link Interference (CLI), Coordinated Multi-Point transmission / reception (CoMP), Channel Occupancy Time (COT), Cyclic Prefix (CP). Common Phase Error (CPE), Conventional OFDM (relying on cyclic prefix) (CP-OFDM), Channel Quality Indicator (CQI), Core Network (e.g., LTE Packet Core or NR Core) (CN), Cyclic Redundancy Check (CRC), Channel State Information (CSI), Channel State Information-Reference Signal (CSI-RS), Central Unit (CU), Device to Device transmissions (D2D) (e.g., LTE sidelink), Dual Connectivity (DC), Downlink Control Information (DCI), Downlink (DL), Demodulation Reference Signal (DM-RS), Data Radio Bearer (DRB), Distributed Unit (DU), E-UTRA-NR Dual Connectivity (EN-DC), Evolved Packet Core (EPC), Frequency Domain-Code Division Multiplexing (FD-CDM), Frequency Division Duplexing (FDD), Frequency Division Multiplexing (FDM), Hybrid Automatic Repeat reQuest Negative ACK (HARQ NACK), Inter-Cell Interference (ICI), Inter-Cell Interference Cancellation (ICIC), Internet Protocol (IP), Listen-Before-Talk (LBT), Logical Channel (LCH), Logical Channel Identity (LCID), Logical Channel Prioritization (LCP), Low Latency Communication (LLC), Long Term Evolution (LTE) (e.g., 3GPP LTE Release 8 and later), Medium Access Control (MAC), Medium Access Control Control Element (MAC CE), Negative (ACK NACK), Multimedia Broadcast Multicast System (MBMS), Master Cell Group (MCG), Modulation and Coding Scheme (MCS), Multiple-Input Multiple-Output (MIMO), Machine-Type Communication (MTC), Multi-RAT Dual Connectivity (MR-DC), Non-Access Stratum (NAS), New candidate beam-Reference Signal (NCB-RS), NR-RAN-E-UTRA DualConnectivity, NE-DC), New Radio (NR), New Radio Dual Connectivity (NR-DC), Orthogonal Frequency-Division Multiplexing (OFDM), Out-Of-Band (OOB) (emission), total available WTRU power (Pcmax) at a given transmission interval, Primary Cell (Pcell) of the Master Cell Group, Primary Cell Group (PCG), Protocol Data Unit (PDU), Packet Error Rate (PER), Physical Layer (PHY), Public Land Mobile Network (PLMN), Packet Loss Rate (PLR), Physical Random-Access Channel (PRACH), Physical Resource Block (PRB), Positioning Reference Signal (PRS), Primary cell of a Secondary cell group (PScell), Primary Synchronization Signal (PSS), Phase Tracking-Reference Signal (PT-RS), Quality of Service (QoS) (from the perspective of the Physical Layer), Radio Access Bearer (RAB), Radio Access Network Paging Area (RAN PA), Random Access Channel (or procedure) (RACH), Random Access Response (RAR), Radio Access Technology (RAT), Resource Block (ResourceBlock, RB), Radio Access Network Central Unit (RCU), Radio Front End (RF), Resource Element (RE), Radio Link Failure (RLF), Radio Link Monitoring (RLM), Radio Network Identifier (RNTI), Random Access Occasion (RO), Read-Only Mode (ROM) (for MBMS), Radio Resource Control (RRC), Radio Resource Management (RRM), Reference Signal (RS), Round-Trip Time (RTT), Secondary Cell Group (SCG), Single Carrier Multiple Access (SCMA), Sub-Carrier Spacing (SCS), Service Data Unit (SDU), Spectrum Operation Mode (SOM), Semi-persistent (SP), Primary Cell (SpCell) of a master or secondary cell group, Signaling Radio Bearer (SRB), Synchronization Signal (SS), Sounding Reference Signal (SRS), Secondary Synchronization Signal (SSS), Supplemental UpLink (SUL), Switching Gap (SWG) (in a self-contained subframe), Transport Block (TB), Transport Block Size (TBS), Transmission Configuration Index (TCI), Time-Division Duplexing (TDD), Time-Division Multiplexing (TDM), Time Interval (TI) (an integer multiple of one or more symbols), Transmission Time Interval (TTI) (an integer multiple of one or more symbols), Transmission / Reception Point (TRP), Transmission / Reception Point Group (TRPG), Tracking Reference Signal (TRS), Transceiver (TRx), Uplink (UL), Ultra-Reliable Communication (URC), Ultra-Reliable and Low Latency Communications (URLLC), Vehicle-to-Everything (V2X), Wireless Local Area Network (WLAN) and related technologies (IEEE 802.xx area), and Cross-Division Duplexing (XDD).

[0069] In one embodiment, Awareness and Reporting after Sensing (ARAS) may be performed. For example, a potential victim WTRU may receive measurement and / or reporting configurations for a list of reference subbands (e.g., Ref_SB). In one example, the WTRU may receive the reference subbands (e.g., Ref_SB) via a subset of a time-frequency resource mask (e.g., a set of subbands or a set of symbols / slots). In one example, the measurement / sensing configuration may include one or a combination of a reference signal, RS time / frequency resources, etc. The reference signal may include, for example, but not limited to, zero-power channel state information reference signal (ZP-CSI-RS), non-zero-power channel state information reference signal (NZP-CSI-RS), SRS, etc. The RS time / frequency resources may include, for example, subbands. In one example, the WTRU reporting configuration may include one or both of a CSI quantity and a time / frequency reporting resource. The CSI quantity may include, for example, but not limited to, CLI-RSSI, SRS-RSRP, etc.

[0070] In one embodiment, the WTRU may receive a trigger for event-based interference sensing and / or measurement. The WTRU may receive a trigger for event-based interference sensing and / or measurement, such as a CLI. The WTRU may receive a trigger for event-based interference sensing and / or measurement for one or more of an active SB and a reference SB (e.g., Ref_SB). In one example, the event for triggering CLI sensing may be one or both of a WTRU request and / or a gNB indication. For example, the event for triggering CLI sensing may correspond to the victim WTRU determining one or more DL reception failures. For example, the victim WTRU may determine one or more DL reception failures, such as by transmitting N NACKs. In some cases, the victim WTRU may determine one or more DL reception failures based on a counter exceeding a threshold. For example, the victim WTRU may determine one or more DL reception failures based on a counter exceeding a threshold within a time window (e.g., a timer). In one example, the event for triggering CLI sensing may correspond to the need to avoid an SB and the need for the WTRU to communicate via another SB. For example, the WTRU may need to communicate via another SB as a complementary mechanism for XDD.

[0071] In one or more cases, the WTRU may receive a type of interference measurement. For example, the type of interference measurement may include, but is not limited to, overlapping CLI, partially overlapping CLI, and / or non-overlapping CLI. Overlapping CLI may be, for example, in-band CLI. Partially overlapping CLI may be, for example, inter-band CLI of a set of cells / TRPs having RBs that partially overlap between UL and DL. Non-overlapping CLI may be inter-band CLI.

[0072] In one example, the WTRU may measure CLI-RSSI and / or SRS-RSRP over a given short period across the configured frequency / sub-band resources. The measurement values may be reported via L1 signaling (e.g., L1-CLI-RSSI reported via PUCCH, PUSCH, RACH, SRS). For example, the WTRU may report the measurement values. Without limitation, L1 signaling such as L1-CLI-RSSI may be reported via PUCCH, PUSCH, RACH, SRS, etc. In one example, the WTRU may receive a configuration for delta CLI-RSSI measurement. In some cases, the WTRU may determine the delta CLI-RSSI. For example, the WTRU may determine the delta CLI-RSSI based on the difference between a first CLI-RSSI (e.g., CLI-RSSI1) and a second CLI-RSSI (e.g., CLI-RSSI2). For example, delta CLI-RSSI = CLI-RSSI1 - CL-RSSI2. In some cases, the first CLI-RSSI may be measured from a resource located at the center of the scheduled RB. In some cases, the second CLI-RSSI may be measured from a resource located at the edge of the scheduled RB. In one or more cases, the WTRU may report the delta CLI-RSSI based on the scaled delta CLI-RSSI being greater than a threshold indicating the CLI of a potential edge RB. The CLI of the potential edge RB may be, for example, a non-overlapping CLI.

[0073] For cases where the WTRU senses / measures interference, the WTRU may report CLI sensing / measurement. For example, the WTRU may report CLI sensing measurement based on L1-CLI-RSSI and respective thresholds. In one or more cases, the WTRU may send a flag in addition to the NACK transmission to indicate potential interference. For example, the flag may indicate that the NACK transmission may be based on sensing interference. For example, sensing interference may occur when the L1_CLI_RSSI is above the respective thresholds. In another example, the flag may indicate that the NACK transmission may be based on interference such as CLI. Based on the interference, the WTRU may request an SR for interference measurement (e.g., L1-CLI-RSSI). In one or more cases, the WTRU may request to switch to another reference subband (e.g., from Ref_SB). For example, the WTRU may request to switch to another reference subband where the WTRU may not be sensing interference. For example, the WTRU may request to switch to another reference subband with, but not limited to, an L1-CLI-RSSI lower than the respective thresholds.

[0074] Transmission concession may be performed after sensing. In some cases, a potential aggressor WTRU may determine a list of reference subbands (e.g., Ref_SB). The WTRU may switch to the list of reference subbands, for example, when a CLI can be triggered for a potential victim WTRU in the active SB. For example, the WTRU may receive a subset of a time-frequency resource mask, such as, but not limited to, a set of subbands or a set of symbols / slots. In some cases, the aggressor WTRU may perform event-based CLI / channel occupancy sensing in the active SB. For example, the aggressor WTRU performs event-based CLI / channel occupancy sensing in the active SB when the victim WTRU determines one or more DL reception failures. The victim WTRU may determine one or more DL reception failures based on a counter exceeding a threshold. In some cases, the victim WTRU determines one or more DL reception failures, for example, by transmitting a NACK. In some cases, the victim WTRU determines one or more reception failures based on a counter exceeding a threshold within a time window such as a timer. In some cases, the WTRU may determine that a potential victim WTRU has DL based on the aggressor WTRU detecting channel occupancy. In one example, the WTRU may report one or more of the target subbands and propose a UL SB / BWP / CC where a CLI may not be triggered for a potential victim UE. In some cases, alternatively or in combination, the aggressor WTRU may receive an indication to prevent the aggressor WTRU from transmitting on one or more configured permitted resources. The aggressor WTRU may receive an indication (e.g., grant cancellation) to prevent the aggressor WTRU from transmitting on one or more of the configured permitted resources due to interference. In one example, the aggressor WTRU may be prevented from transmitting on a permitted resource in one or more of the next slots / symbols, and the slot / symbol resources may be identified.In one or more cases, the aggressor WTRU and / or the victim WTRU may receive group common DCI. The group common DCI may indicate, for example, but not limited to, mutual interference and / or measurement, reporting, and / or SB unit avoidance.

[0075] CLI sensing / measurement may be based on the directional SRS-RSRP. In one or more cases, the potential victim WTRU may measure the SRS-RSRP from one or more potential aggressor WTRUs. The potential victim WTRU may measure the SRS-RSRP from one or more potential aggressor WTRUs based on directional measurements. In one example, the WTRU may determine a spatial region filter for receiving the SRS signal. The spatial region filter may be the same spatial region filter used for receiving the RS set indicated by the TCI-State for each CORESET used by the WTRU to monitor the PDCCH, for example. In one example, the WTRU may receive the SRS signal while measuring the SRS-RSRP using at least one spatial region filter. In one or more cases, the WTRU may accordingly report directional CLI / channel sensing.

[0076] FIG. 2 illustrates a system 200 experiencing an example of cross-link interference (CLI) directional sensing. The system 200 may include a serving cell 202, a non-aggressor cell (DL) 204, an aggressor WTRU (UL) 206, and a victim WTRU 208. The victim WTRU 208 may report directional CLI / channel sensing according to FIG. 2.

[0077] FIG. 3 is a diagram illustrating an example of cross-divided duplexing (XDD) 300. In one example, RAN items related to new radio (NR) duplexing operations may provide a basis for improving conventional TDD operations, such as by extending UL coverage, improving capacity, reducing latency, etc. TDD may be based on dividing the time domain between the uplink and the downlink. In one example, as shown in FIG. 3, full duplexing (e.g., cross-divided duplexing (XDD)) that is subband non-overlapping full duplexing on the gNB side within the TDD band can be achieved.

[0078] FIG. 4 is a diagram illustrating an exemplary system 400 experiencing cross-link interference (CLI), between gNBs, and between WTRUs. Achieving XDD may be conditional on solving the problems that may arise due to cross-link interference (CLI), as shown in FIG. 4. For example, in the XDD framework, a potential aggressor cell may switch the transmission mode in one or more subbands (SBs) from UL to DL, or vice versa, which may, in one example, cause subband-based CLI on the potential victim gNB and WTRU. In one example, CLI-RSSI measurements may be based on long-term measurements. In UL-DL CLI, the CLI from the aggressor WTRU may cause strong interference on the victim WTRU in a specific SB, while other SBs may not be affected. CLI in XDD may not be limited to WTRUs at the cell edge. Rather, WTRUs at the center and / or middle of the beam may experience CLI. Thus, a WTRU may be configured to perform subband-based CLI measurements.

[0079] In some cases, the CLI can be caused by another WTRU. For cases where another WTRU causes the CLI, the CLI can depend on the direction of the transmission beam. Further, the CLI can depend on sensing in all directions, which can result in misdetection of the CLI. For sub-band unit CLIs in XDD based on misdetection of the CLI, different WTRU behaviors can occur. Thus, the WTRU can be configured for channel sensing for potential sub-band unit CLIs, CLI avoidance by switching to other SBs, and directional CLI sensing in XDD as described herein.

[0080] In one or more cases where the CLI is sensed, the WTRU can be configured to determine and / or switch to an SB not affected by the CLI as described herein. In one or more cases, the aggressor WTRU can be configured to consider the interference caused to the victim WTRU. In one or more cases, the WTRU can be configured to discover the optimal means of measuring the CLI in the active SB and potential SBs for switching. In one or more cases, sub-band unit channel and / or interference sensing can be performed at the victim WTRU. In one or more cases, sub-band sensing after avoidance reporting (ARAS) can be performed. In one or more cases, transmission concessions can be performed after sensing at the aggressor WTRU. In one or more cases, directional CLI sensing and measurement can be performed.

[0081] As used herein, the terms "a" and "an" and similar phrases should be construed as "one or more" and "at least one." Similarly, any term ending with the suffix "(s)" should be construed as "one or more" and "at least one." The term "can" should be construed as "for example, can."

[0082] A WTRU may transmit and / or receive physical channels and / or reference signals. In one example, the WTRU may transmit or receive a physical channel or reference signal according to at least one spatial domain filter. In one or more cases, the term "beam" may be used to refer to a spatial domain filter. In one or more cases, the WTRU may transmit a physical channel and / or signal using the same spatial domain filter that is used to receive an RS (e.g., CSI-RS) or SS block. In one or more cases, the WTRU transmission may be referred to as "target". In one or more cases, the received RS and / or SS block may be referred to as "reference" or "source". In such cases, the WTRU may be configured to transmit a target physical channel and / or signal. In one example, the WTRU may be configured to transmit a target physical channel and / or signal according to the spatial relationship to such RS and / or SS block. In one or more cases, the WTRU may transmit a first physical channel and / or signal. The WTRU may be configured to transmit the first physical channel and / or signal according to the same spatial domain filter that is used to transmit a second physical channel and / or signal. In one example, the first and / or second transmissions may be referred to as "target" and "reference" (and / or "source"), respectively. In such cases, the WTRU may transmit the first (e.g., target) physical channel and / or signal according to the spatial relationship to the second (e.g., reference) physical channel and / or signal. In one or more cases, the spatial relationship may be implicit. In one or more cases, the spatial relationship may be configured by the RRC. In one or more cases, the spatial relationship may be signaled by MAC CE and / or DCI.For example, the WTRU may implicitly transmit a physical uplink shared channel (PUSCH) and a demodulation reference signal (DM-RS) of the PUSCH according to the same spatial region filter as the sounding reference signal (SRS) that may be indicated in the DCI and / or indicated by the SRI that may be configured by the RRC. In another example, the spatial relationship may be configured by the RRC for the SRS resource indicator (SRI) and / or signaled by the MAC CE for the physical uplink control channel (PUCCH). The spatial relationship may be referred to as a "beam indication".

[0083] The WTRU may receive a first (e.g., target) downlink channel and / or signal according to the same spatial region filter and / or spatial reception parameters as a second (e.g., reference) downlink channel or signal. For example, such an association may exist between physical channels such as a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH), and / or their respective DM-RSs. In one example, such an association may exist when the WTRU may be configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports, e.g., when the first and second signals are reference signals. In one example, such an association may be configured as a transmission configuration indicator (TCI) state. In one or more cases, the WTRU may be configured by the RRC and / or signaled by the MAC CE, and indicated by an index to a set of TCI states, as an association between a CSI-RS or SS block and a DM-RS. Such an indication may be referred to as a beam indication.

[0084] The transmission and reception point (TRP) can be used interchangeably with one or more of a transmission point (TP), a reception point (RP), a radio remote head (RRH), a distributed antenna (DA), a base station (BS), a sector (e.g., a sector of the BS), and / or a cell (e.g., a geographical cell area served by the BS). The multi-TRP can be used interchangeably with one or more of MTRP, M-TRP, and / or multiple TRPs.

[0085] The terms "sub-band" and "sub - band" can be used to refer to frequency domain resources and / or can be characterized by one or more of the following: a set of resource blocks (RBs), e.g., when a carrier has an in-cell guard band, a set of resource block sets (RB sets), a set of interleaved resource blocks, a bandwidth part, and / or a portion thereof, a carrier, and / or a portion thereof, etc. For example, a sub-band can be characterized by the starting RB and / or the number of RBs for a set of consecutive RBs within a bandwidth part. In another example, a sub-band can be defined by a frequency domain resource allocation field and / or the value of a bandwidth part index.

[0086] The term "XDD" can be used to refer to a spatial domain filter. In one or more cases, either UL or DL can be used per sub-band. XDD can be characterized by one or more of the following: cross-divided multiplexing, sub-band-based full duplexing, frequency-domain multiplexing (FDM) of DL / UL transmissions within the TDD spectrum, sub-band non-overlapping full duplexing, full duplexing other than the same frequency full duplexing, advanced duplexing methods, such as other than (e.g., pure) TDD or FDD. Cross-divided multiplexing can be, for example, sub-band unit FDD within the TDD band. Sub-band-based full duplexing can be, for example, full duplexing when both UL and DL can be used / mixed on a symbol / slot, and either UL or DL can be used per sub-band on the symbol / slot. Full duplexing other than the same frequency can include, for example, but not limited to, spectrum sharing, sub-band unit overlap, etc.

[0087] The terms "dynamic ( / flexible)" and "TDD" can be used to refer to a TDD system / cell. In one example, a TDD system / cell can dynamically (and / or flexibly) change, adjust, and / or switch the communication direction over a time instance. A TDD system / cell can dynamically (and / or flexibly) change, adjust, and / or switch a communication direction, such as, but not limited to, one or more of a downlink direction, an uplink direction, a sidelink direction, etc. A time instance can include, for example, but not limited to, one or more of a slot, a symbol, a subframe, etc. In one example, in a system employing dynamic / flexible TDD, a component carrier (CC) or a bandwidth part (BWP) can have a single type of one of "D", "U", and "F" on a symbol / slot based on an indication by a group-common (GC)-DCI (e.g., format 2_0) with a slot format indicator (SFI), and / or based on a tdd-UL-DL-config-common and / or dedicated configuration. In one example, at a given time instance, slot, and / or symbol, a first gNB (e.g., a cell, a TRP, etc.) employing dynamic and / or flexible TDD can communicate with a second gNB (e.g., a cell, a TRP, etc.) that can employ dynamic and / or flexible TDD and can receive an uplink signal transmitted from the second WTRU, and / or transmit a downlink signal to a first WTRU associated therewith, based on a first SFI and / or a tdd-UL-DL-config that can be configured and / or indicated by the first gNB. In one example, the second WTRU can communicate with a second gNB that can be based on a second SFI and / or a tdd-UL-DL-config that can be configured and / or indicated by the second gNB, and / or can be associated therewith. In one example, the first WTRU can determine that reception of a downlink signal is interfered with by an uplink signal.In one example, the interference that can be caused by an uplink signal may refer to WTRU - to - WTRU cross - link interference (CLI).

[0088] The WTRU may report a subset of channel state information (CSI) components. In one example, the CSI components may correspond to one or more of the following: CSI - RS resource indicator (CRI), SSB resource indicator (SSBRI), an indication of the panel used for reception at the WTRU (e.g., panel identification information or group identification information), measurements such as L1 - RSRP, L1 - SINR taken from SSB or CSI - RS (e.g., cri - RSRP, cri - SINR, ssb - Index - RSRP, ssb - Index - SINR), and other channel state information. The other channel state information may include, for example, one or more of the following: rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), layer index (LI), etc.

[0089] The WTRU may be configured to perform LBT channel sensing. In one example, in an operation using shared spectrum channel access, the WTRU may trigger an LBT failure indication. For example, the WTRU may trigger an LBT failure indication based on the measured received signal strength indicator (RSSI) in the active BPW being higher than a threshold. In one example, the WTRU may measure the RSSI. For example, the WTRU may measure the RSSI based on a RSSI measurement timing configuration (RMTC), for example, according to configured parameters. In one or more cases, the WTRU may be configured with one or more of the following parameters: RMTC periodicity, RMTC subframe offset, frequency resources for RSSI measurement, number of measurement symbols, and reference subcarrier spacing (SCS) and cyclic prefix (CP). In one example, the RMTC periodicity may be rmtc-Periodicity. In one example, the RMTC subframe offset may be rmtc-SubframeOffset. For example, the first symbol of each RMTC occasion may occur at the first symbol of the SFN and / or the NR subframe. The NR subframe may be based on a configured subframe offset in one example. In one example, the frequency resources for RSSI measurement may be rmtc-Frequency. In one example, the number of measurement symbols may be measDurationSymbols. The number of measurement symbols may indicate the number of consecutive symbols for RSSO measurement. In one example, the reference subcarrier spacing (SCS) and cyclic prefix (CP) may be used for RSSI measurement (e.g., ref-SCS-CP).

[0090] A WTRU may be configured with one or more parameters to detect consistent LBT failures. For example, the WTRU may be configured to detect consistent LBT failures such as lbt FailureRecoveryConfig. In one or more cases, the WTRU may be configured with one or more of the following parameters: LBT counter, LBT timer, and maximum count for LBT failure indication. The LBT counter may be, for example, LBT_COUNTER. In one or more cases, the LBT counter may be a counter for consistent uplink LBT failure detection. In one example, the LBT counter may be incremented by 1 for each LBT failure indication. The LBT timer may be, for example, lbt-FailureDetectionTimer. In one or more cases, the LBT timer may be a timer for consistent uplink LBT failure detection. In one example, the LBT timer may be started and / or restarted with an LBT failure indication. In one or more cases, the maximum value (i.e., maximum count) for LBT failure indication may be, for example, lbt-FailureInstanceMaxCount. In one example, the maximum counter may determine the maximum number of times an LBT failure indication may be expected to occur. For example, the maximum counter may determine the maximum number of times an LBT failure indication may be expected to occur before, for example, the WTRU triggers LBT failure recovery detection.

[0091] In some examples, when triggering and / or receiving an LBT failure indication in the active BWP within the serving cell, the WTRU may start and / or initiate an LBT detection timer (e.g., lbt_FailureDetectionTimer), and / or increment an LBT counter (e.g., LBT_COUNTER) by 1. In one or more cases, the WTRU may compare the LBT counter. In one example, for the case where the LBT counter is greater than or equal to the maximum count for LBT failure detection (e.g., LBT-FailureInstanceMaxCount), the WTRU may trigger a consistent LBT failure for the active BWP within the serving cell. In some cases, a consistent LBT failure for the active BWP within the serving cell may be triggered. In one example, the WTRU may determine whether a consistent LBT failure may be triggered for one or more BWPs. In some cases, one or more BWPs may be configured on the same carrier within the serving cell. For the case where a consistent LBT failure for the active BWP within the serving cell is triggered, the WTRU may determine whether a consistent LBT failure is triggered for all BWPs configured on the same carrier within the serving cell. In one or more cases, a consistent LBT failure may be triggered for one, multiple, or all BWPs configured on the same carrier within the serving cell. In one example, the WTRU may indicate the consistent LBT failure to the upper layer. For the case where a consistent LBT failure is triggered for all BWPs configured on the same carrier within the serving cell, the WTRU may indicate the consistent LBT failure to the upper layer. In one or more cases, a consistent LBT failure may not be triggered for one, multiple, or all BWPs configured on the same carrier within the serving cell. The WTRU may switch the active BWP to a BWP on the same carrier within the serving cell where a consistent LBT failure may not be triggered. In one example, for the case where a consistent LBT failure is not triggered for all BWPs configured on the same carrier within the serving cell, the WTRU may switch the active BWP to a BWP on the same carrier within the serving cell where a consistent LBT failure is not triggered.

[0092] A WTRU may receive a synchronization signal / physical broadcast channel (SS / PBCH) block. In one example, an SS / PBCH block (SSB) may include one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and / or a physical broadcast channel (PBCH). In one example, a WTRU may monitor, receive, and / or attempt to decode one or more of the SSBs during initial access, initial synchronization, radio link monitoring (RLM), cell search, cell handover, and other similar scenarios.

[0093] A WTRU may measure and / or report channel state information (CSI). In one example, the CSI for each connection mode may include and / or be composed of one or more of the following: CSI report configuration, CSI-RS resource set, and NZP-CSI-RS resource. In one example, the CSI report configuration may include one or more of the following: CSI report quantity, CSI report type, CSI report codebook configuration, and CSI report frequency. The CSI report quantity may include, for example, a channel quality indicator (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), etc. The CSI report type may include, for example, aperiodic, semi-persistent, periodic, etc. The CSI report codebook configuration may include, for example, type I, type II, type II port selection, etc. In one example, the CSI-RS resource set may include one or more CSI resource settings. The CSI resource setting may include, for example, but not limited to, the following: NZP-CSI-RS resources for channel measurement, NZP-CSI-RS resources for interference measurement, and CSI-IM resources for interference measurement. The NZP CSI-RS resource may include, for example, but not limited to, one or more of the following: NZP CSI-RS resource ID, periodicity and offset, QCL information and / or TCI state, and resource mapping (e.g., number of ports, density, CDM type, etc.).

[0094] A WTRU may indicate, determine, and / or be comprised of one or more reference signals. In one example, the WTRU may monitor, receive, and / or measure one or more parameters based on, for example, each reference signal. For example, the parameters may include one or more of the following: SS-RSRP, CSI-RSRP, SS-SINR, CSI-SINR, RSSI, CLI-RSSI, and SRS-RSRP. The parameters monitored, received, and / or measured by the WTRU (e.g., SS-RSRP, CSI-RSRP, SS-SINR, CSI-SINR, RSSI, CLI-RSSI, and / or SRS-RSRP) are non-limiting examples of parameters that may be included in reference signal measurements. For example, one or more of these parameters may be included in the reference signal measurements. In another example, other parameters may be included in the reference signal measurements.

[0095] The SS reference signal received power (SS-RSRP) can be measured based on a synchronization signal. The synchronization signal can be, for example, a demodulation reference signal (DMRS) in the PBCH or SSS. In one example, the SS-RSRP can be defined as a linear average over the total power contribution of the resource elements (REs) that can carry each synchronization signal. When measuring the RSRP, power scaling for the reference signal may be required. For the case where the SS-RSRP is used for L1-RSRP, the WTRU can perform measurements based on, for example, CSI reference signals in addition to the synchronization signal. In one or more cases, the CSI-RSRP can be measured based on a linear average over the total power contribution of the REs that carry each CSI-RS. In one example, the CSI-RSRP measurement can be configured within the measurement resources for the configured CSI-RS occasion. In one or more cases, the SS signal-to-noise and interference ratio (SS-SINR) can be measured based on a synchronization signal. The synchronization signal can be, for example, the DMRS in the PBCH and / or SSS. The SS-SINR can be a linear average over the total power contribution of the REs that can carry each synchronization signal, divided by the linear average of the noise and interference power contributions. The noise and / or interference power measurement can be achieved, for example, based on resources configured by a higher layer when the SS-SINR is used for L1-SINR. In one or more cases, the CSI-SINR can be measured based on a linear average over the total power contribution of the REs that can carry each CSI-RS, divided by the linear average of the noise and interference power contributions. The noise and interference power measurement can be achieved, for example, based on resources configured by a higher layer when the CSI-SINR is used for L1-SINR. Alternatively, or in combination, the noise and / or interference power can be measured based on the resources that can carry each CSI-RS.In one or more cases, the received signal strength indicator (RSSI) can be measured based on the average of the total power contribution in the configured OFDM symbol and bandwidth. In one example, the power contribution can be received from different resources. Different resources can include, for example, but not limited to, the same channel serving cell and non-serving cells, adjacent channel interference, thermal noise, etc. In one or more cases, the cross-link interference received signal strength indicator (CLI-RSSI) can be measured based on the average of the total power contribution in the configured OFDM symbol of the configured time and / or frequency resources. In one example, the power contribution can be received from different resources. Different resources can include, for example, cross-link interference, the same channel serving cell and non-serving cells, adjacent channel interference, thermal noise, etc. In one or more cases, the sounding reference signal (SRS-RSRP) can be measured based on the linear average over the entire power contribution of the REs carrying each SRS.

[0096] The properties of the grant and / or allocation can include one or more of the following: frequency allocation, time allocation pattern (e.g., duration); priority; modulation and coding scheme; transport block size; number of spatial layers; number of transport blocks; TCI state, CRI, and / or SRI; number of repetitions; determination of whether the repetition pattern is type A and / or type B; determination of whether the grant is a configured grant type 1, type 2, and / or dynamic grant; determination of whether the allocation is a dynamic allocation and / or semi-persistent scheduling (e.g., configured) allocation; configured grant index and / or semi-persistent allocation index; periodicity of the configured grant and / or allocation; channel access priority class (CAPC); and any parameters provided in the DCI by the MAC and / or RRC, for example, to schedule the grant and / or allocation.

[0097] The indication by DCI may include one or more of the following: explicit indication by a DCI field and / or by an RNTI, and implicit indication by a property. In one example, the explicit indication by a DCI field and / or by an RNTI may be used to mask the CRC of the PDCCH. In one example, the implicit indication by a property may be, for example, a DCI format, a DCI size, a core set and / or a search space, an aggregation level, the first resource element of the received DCI (e.g., the index of the first control channel element). In one example, the mapping between a property and / or a value may be signaled by RRC and / or MAC.

[0098] In one or more cases, the RS may be used interchangeably with one or more of an RS resource, an RS resource set, an RS port, and / or an RS port group and may conform to the disclosed embodiments. In one or more cases, the RS may be used interchangeably with one or more of an SSB, a CSI-RS, an SRS, and / or a DM-RS and may conform to the disclosed embodiments. In one or more cases, the interference may be used interchangeably with a CLI, a CLI-RSSI, and / or an SRS-RSRP and may conform to the disclosed embodiments.

[0099] In one or more cases, a Perceived Avoidance Report (ARAS) may be executed. In one example, the WTRU may receive one or more configuration parameters for CSI / beam reporting (e.g., from a gNB). The one or more configuration parameters may include, for example, but are not limited to, one or more DL RS (e.g., CSI-RS) resources. The one or more DL RS resources may be for DL measurements for deriving and / or determining CSI (and / or beam index and / or beam quality metric) that may be reported at a time instance for CSI / beam reporting. In one example, the WTRU may receive a beam / TCI indication and / or configuration (e.g., from a gNB). The beam / TCI indication and / or configuration may be used for reception of DL signals. In one example, the beam / TCI indication and / or configuration may be determined by the gNB based on CSI / beam reporting from the WTRU. In one example, the WTRU may receive a grant (e.g., DCI including a DL allocation) for scheduling reception of a DL signal. The WTRU may receive the DL signal using a spatial filter, which may be determined, for example, based on the beam / TCI indication.

[0100] In one or more cases, there may be interference that can be obtained based on signals transmitted by a second WTRU (e.g., a nearby WTRU from the WTRU), which can affect (e.g., degrade and / or reduce) the reception performance of DL signals at the WTRU. In one or more cases, the presence of the interference may not be known prior to the grant. For example, the presence of the interference may not be known prior to the grant when the second WTRU can be associated with a different serving cell / TRP from the WTRU. In one example, the WTRU may fail to receive a DL signal based on the interference. The interference may be, for example, an inter-WTRU CLI based on a second UL signal of the WTRU. In some cases, the interference may not be captured in CSI / beam reporting. For example, the interference may not be captured in CSI / beam reporting because one or more DL RS resources may reflect (e.g., be related to) the UL signal transmission of the second WTRU. The DL signal may, for example, degrade the DL performance in the communication between the gNB and the WTRU. In one or more cases, failures in receiving the DL signal may continue to occur. For example, the WTRU may fail to receive the DL signal when the DL signal is retransmitted by the gNB. The WTRU may fail to receive the DL signal for a duration in which there is an unexpected inter-WTRU CLI present.

[0101] A WTRU (e.g., a potential victim WTRU) may determine a list of reference subbands (e.g., Ref_SB) that the WTRU may use or may switch to a reference subband. In one or more cases, the WTRU may be shown and / or configured with a list of reference subbands. For example, the WTRU may be instructed to switch to a subband, may be instructed to use a subband for communication between the WTRU and the gNB, and / or may be instructed to use a subband for checking the CLI. The WTRU may check the CLI, for example, by measuring, estimating, and / or determining the CLI. In one or more cases, the WTRU may receive a list of reference subbands as a subset of a time - frequency resource mask (e.g., a set of subbands and / or a set of symbols / slots, etc.). The WTRU may receive a configuration for CLI sensing and / or measurement on the Ref_SB.

[0102] The WTRU may receive a trigger for CLI sensing and / or measurement on the Ref_SB. In one example, the WTRU may receive the trigger and / or measurement explicitly. The measurement may include, for example, an aperiodic channel sensing. In one or more cases, the trigger may be based on an active (e.g., current, currently communicating with the gNB / TRP, etc.) SB and / or one or more reference SBs (e.g., Ref_SB). The active SB may be, for example, but not limited to, the current SB, the SB currently communicating with the gNB / TRP, etc. In one or more cases, the WTRU may determine that at least one event and / or condition (e.g., an event and / or condition corresponding to CLI sensing and / or measurement) may be satisfied. In one example, the WTRU may start (e.g., perform, begin, do, execute, etc.) CLI sensing and / or measurement based on determining that at least one event and / or condition may be satisfied. In some cases, the WTRU may start CLI sensing and / or measurement based on, for example, at least one reference SB (e.g., Ref_SB), and / or at least one instruction, pre - configuration, and / or pre - determined resource.

[0103] The WTRU may transmit (e.g., report) at least SB-related information content. The SB-related information content may include, for example, but is not limited to, one or more SB indexes, corresponding SB unit metrics, etc. The SB unit metric may include, for example, but is not limited to, SB unit CLI-RSSI, SB unit quality metric, etc. In one or more cases, the WTRU may transmit at least SB-related information content based on CLI sensing and / or measurement being performed and / or having occurred. For example, the WTRU may transmit at least SB-related information content after CLI sensing and / or measurement has been performed and / or executed. Thus, the gNB may utilize the reported SB-related information content to avoid a particular RB and communicate with the WTRU. This may be an example of a post-sensing avoidance reporting (ARAS) mechanism applicable at the WTRU (e.g., based on the configuration of the ARAS that may be received at the WTRU).

[0104] At least one event / condition for starting CLI sensing / measurement may include one or more of the following examples. For example, CLI sensing / measurement may start when the WTRU (e.g., victim WTRU) determines one or more (e.g., K) DL data (e.g., PDSCH) reception failures. In some cases, K may be a counter parameter configured and / or indicated by the gNB. For example, for the case of K = 1, at least one event / condition may be satisfied when the WTRU fails to receive the scheduled PDSCH. In another example, for the case of K = 2 or K > 2, at least one event / condition may be satisfied when the WTRU determines, for example, two (or K) occasions of PDSCH reception failure within a time window. In some cases, the parameter / value for the time window may be configured / indicated from the gNB.

[0105] In another example, CLI sensing / measurement may start when a WTRU (e.g., a victim WTRU) determines one or more (e.g., K) DL data (e.g., PDSCH) reception failures and / or when the WTRU transmits one or more NACKs in response to at least one failure when receiving one or more (e.g., scheduled) PDSCHs. For example, for the case of K = 1, at least one event / condition may be satisfied when the WTRU fails to receive a scheduled PDSCH and / or when the WTRU transmits a NACK based on determining a failure when receiving a PDSCH (e.g., a scheduled PDSCH). The NACK may be, for example, but not limited to, a negative ACK, a negative response, etc. In another example, for the case of K = 2 or K>2, at least one event / condition may be satisfied when the WTRU determines two (or K) occasions of PDSCH reception failure, e.g., within a time window, and / or when the WTRU transmits two (or K) NACKs based on at least two (or K) failures determined when receiving two (or K) scheduled PDSCHs, e.g., within a time window. The parameter / value for the time window may be configured / instructed from the gNB.

[0106] In another example, CLI sensing / measurement may start when an explicit indication that SB needs to be avoided is received. For example, the explicit indication that SB should be avoided may include an indication to the WTRU for communicating via another SB. In another example, CLI sensing / measurement may start when an implicit indication that SB needs to be avoided is identified (and / or, e.g., received and / or determined). For example, the implicit indication may instruct the WTRU to communicate via another SB. The implicit indication may be a predefined and / or preconfigured rule based on one or more of measurement, reception, detection, etc. of DL signals.

[0107] The WTRU may receive (e.g., explicitly or implicitly) a trigger to measure one or more types of interference (e.g., CLI) measurements. The WTRU may receive one or more indications and / or configurations of the following types of interference measurements: overlapping CLI, partially overlapping CLI, and overlapping CLI. The overlapping CLI may be, for example, but not limited to, in-band CLI. In one example, the overlapping CLI may correspond to the CLI over the entire set of RBs that overlap between the DL reception (region) and the UL transmission (region). For example, the overlapping CLI may be, for example, in a cell / TRP or in a set of cells / TRPs, over the entire set of RBs that overlap between the DL reception and the UL transmission. The set of cells / TRPs may be, for example, a set of geographically distributed cells / TRPs.

[0108] The partially overlapping CLI may be the CLI over the entire set of RBs that partially overlap between the DL reception (region) and the UL transmission (region). For example, the partially overlapping CLI may be, for example, in a cell / TRP or in a set of cells / TRPs, the CLI over the entire set of RBs that partially overlap between the DL reception and the UL transmission. The set of cells / TRPs may be, for example, a set of geographically distributed cells / TRPs. The partially overlapping CLI may be the CLI over the entire set of RBs where a first set of RBs and a second set of RBs may partially overlap. For example, the partially overlapping CLI may be, for example, in a cell / TRP or in a set of cells / TRPs where a first set of RBs and a second set of RBs may partially overlap, the CLI (i.e., that occurs) between the first set of RBs for DL reception (region) and the second set of RBs for UL transmission (region). The set of cells / TRPs may be, for example, within a set of geographically distributed cells / TRPs.

[0109] A non-overlapping CLI can be, for example, but is not limited to, an inter-subband CLI. A non-overlapping CLI can be a CLI between a first set of RBs for DL reception (region) and a second set of RBs for UL transmission (region) (i.e., occurring), and the first set of RBs and the second set of RBs do not overlap. The first set of RBs and the second set of RBs do not overlap, for example, when there is an M (≥0) RB gap between the DL reception region and the UL transmission region. A non-overlapping CLI can be a CLI between a first set of RBs for DL reception and a second set of RBs for UL transmission in a cell / TRP or in a set of cells / TRPs. In one example, the set of cells / TRPs can be, for example, a set of geographically distributed cells / TRPs. A non-overlapping CLI can be the case where the first set of RBs and the second set of RBs do not overlap (e.g., there can be an M (≥0) RB gap between the DL reception region and the UL transmission region).

[0110] A WTRU can be configured, determined, and / or instructed to perform measurements of CLI received signal strength indicator (RSSI) over a given period. The given period can include, for example, but is not limited to, one or more slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs). In one example, CLI-RSSI can be measured at a given time / frequency resource. CLI-RSSI can be referred to as L1-CLI-RSSI, short-term CLI-RSSI, aperiodic CLI-RSSI, etc. Note that CLI-RSSI, L1-CLI-RSSI, and / or RSSI can be used interchangeably when describing the embodiments disclosed herein.

[0111] In one or more cases, one or more RSSI types may be used. In one or more cases, the WTRU may be configured to perform one or more RSSI types. In one example, the first RSSI type may be based on measurements over a long period (e.g., two or more slots). The measurements may be reported via upper layer signaling (e.g., RRC and / or MAC). In another example, the second RSSI type may be based on measurements over a short period (e.g., one slot, within a slot, one or more OFDM symbols within a slot, etc.). The measurements may be reported via L1 signaling such as, but not limited to, PUCCH, PUSCH, RACH, SRS, etc. Note that RSSI may be used interchangeably with RSRP, RSRQ, and / or SINR. In one or more cases, the WTRU may be configured with a set of time / frequency resources. The WTRU may use the set of time / frequency resources to measure L1-CLI-RSSI. In one example, the time / frequency resources for L1-CLI-RSSI measurement may be referred to as CLI-RSSI measurement resources (CRMR).

[0112] In one or more cases, the CRMR may be a resource configured, determined, and / or defined by one or more of the following characteristics: a set of muted REs in a downlink resource, a set of REs that the WTRU is not scheduled or used to measure the CRMR, a set of REs located within an RB that may be configured or determined as a guard band or guard RB, one or more reference signals, a second set of DMRS REs within a second CDM group, and / or located within a scheduled resource. The one or more reference signals may be, for example, but not limited to, DMRS, SRS, sidelink CSI-RS, etc. The CRMR resource located within the scheduled resource may be, for example, a scheduled PDSCH RB.

[0113] In one example, the set of muted REs in the downlink resource (e.g., PDSCH) can be rate matched and / or punctured for downlink reception and / or uplink transmission. In one example, the set of muted REs can have the same pattern (e.g., the same time / frequency position) in each RB. In another example, the set of muted REs can have different patterns based on the RB position. For example, the first pattern can be used for the RBs located at the edge of the scheduled RBs, and the second pattern can be used for the RBs located at the center of the scheduled RBs. The first pattern and the second pattern can have, for example, different numbers of muted RES. In another example, the muted Res can be in the form of zero-power CSI-RS (e.g., ZP-CSI-RS).

[0114] In one example, the set of REs located within an RB can be configured and / or determined as a guard band or a guard RB. In one example, the guard band or the guard RB can be located between the uplink resource and the downlink resource. In one example, the WTRU can skip receiving and / or transmitting signals in the guard band.

[0115] The second set of DMRS REs within the second CDM group may be, for example, within the PDSCH, for example, within the scheduled downlink resource / RB. The second set of DMRS REs within the second CDM group may correspond to the case where the WTRU may receive DCI scheduling the PDSCH that may indicate the first set of DMRS REs corresponding to the first CDM group. The first CDM group may be used to receive the PDSCH. In one example, the WTRU may receive DCI scheduling the PDSCH that indicates the first set of DMRS REs corresponding to the first CDM group. The WTRU may receive DCI scheduling the PDSCH that indicates the first set of DMRS REs corresponding to the first CDM group, based on, for example, the indicated antenna port (e.g., DMRS antenna port) field of the DCI. Based on receiving the DCI, the WTRU may determine that the second set of DMRS REs within the second CDM group may be used as CRMR. In one or more cases, the second CDM group may be a group other than the first CDM group. In one or more cases, the WTRU may determine that the second set of DMRS REs within the second CDM group may be used as CRMR, for example, within the scheduled PDSCH.

[0116] In one or more cases, the CRMR may be configured commonly for a set of WTRUs (e.g., neighboring WTRUs). For example, the gNB may configure the CRMR for a group of WTRUs. The group of WTRUs may share one or more of the following: a group ID for receiving DCI, a zone ID, and / or WTRUs paired for sidelink unicast (and / or, for example, groupcast) transmission. The group ID for receiving DCI may be, for example, a group RNTI. The zone ID may be determined based on the geographical location of the WTRU, such as, but not limited to, GNSS. In one or more cases, the L1-CLI-RSSI measurement (e.g., including the CRMR resource) may be considered as a CSI reporting quantity and / or may be configured as part of the CSI reporting setting.

[0117] The WTRU may be configured, determined, and / or instructed to perform delta CLI-RSSI. The delta CLI-RSSI may be based on, for example, a first CLI-RSSI measurement at a first time / frequency position and a second CLI-RSSI measurement at a second time / frequency position. One or more of the following may apply. In one or more cases, the delta CLI-RSSI (i.e., the delta CLI-RSSI) may be the difference between a first CLI-RSSI (i.e., CLI-RSSI 1 ) and a second CLI-RSSI (i.e., CLI-RSSI 2 ). For example, delta-CLI-RSSI = CLI-RSSI 1 - CL-RSSI 2 . In another example, delta-CLI-RSSI = CLI-RSSI 2 - CL-RSSI 1 . In one or more cases, the first CLI-RSSI may be measured from a CRMR resource located at the edge of the scheduled RB, while the second CLI-RSSI may be measured from a CRMR resource located at the center of the scheduled RB. Thus, for example, the radio resource overhead can be reduced in that the first CLI-RSSI and the second CLI-RSSI may not be configured on REs separated from the scheduled RB. In one example, the first CLI-RSSI and the second CLI-RSSI may not be configured on REs separated from the scheduled RB based on the determination that the delta CLI-RSSI is based on CLI-RSSI 1 - CL-RSSI 2 , and may represent, capture, and / or reflect the amount of CLI. The delta CLI-RSSI may be such that CLI-RSSI 1 may mainly represent and / or include common downlink intra-cell / inter-cell interference, and CLI-RSSI 2 may be (e.g., in addition to common DL interference) CLI-RSSI 1It may represent, and / or include, leakage interference of a larger CLI (e.g., inter-subband CLI), and thus may represent, capture, and / or reflect the amount of CLI. In one example, when a UL transmission from an aggressor WTRU (e.g., a UL transmission that causes CLI) occurs on an adjacent RB (e.g., a nearby RB) of a scheduled RB, CLI-RSSI 1 may mainly represent, and / or include, general downlink intra-cell / inter-cell interference, and CLI-RSSI 2 is CLI-RSSI 1 may represent, and / or include, leakage interference of a CLI larger than CLI-RSSI. In one or more cases, the WTRU may be composed of a first CRMR resource for a first CLI-RSSI measurement and a second CRMR resource for a second CLI-RSSI measurement. In one or more cases, the WTRU may determine to report CLI measurement related information when the measured delta CLI-RSSI is greater than a threshold. For example, the CLI report may be triggered based on the delta-CLI-RSSI measurement value being greater than a threshold. In some cases, the threshold may be pre-determined and / or configured.

[0118] The WTRU may be configured or determined to measure CLI-RSSI for each sub-band level. For example, the sub-bands may be configured and / or pre-determined. In one or more cases, the WTRU may perform CLI-RSSI measurements in each sub-band. One or more of the following may apply. In one or more cases, the sub-band size may be determined based on the number of scheduled RBs (e.g., for PDSCH). For example, when the number of scheduled RBs is greater than X (e.g., 12), a first sub-band size (e.g., 4) may be used, and when the number of scheduled RBs is less than or equal to X, a second sub-band size (e.g., 2) may be used. In another example, the first sub-band size may be used when the number of scheduled RBs is greater than X. In another example, the second sub-band size may be used when the number of scheduled RBs is less than or equal to X. In one or more cases, the WTRU may report CLI-RSSI measurements for one, multiple, or all sub-bands. In one or more cases, the WTRU may report a subset of the CLI-RSSI. The subset may be determined based on one or more conditions, including but not limited to, the CLI-RSSI value exceeding a threshold, the sub-band location (e.g., the edge of the scheduled RBs), the sub-band index, etc.

[0119] In one or more cases, the bandwidth of beam measurement and / or reporting (e.g., wideband and / or sub-band) can be determined (e.g., by the WTRU) based on one or more conditions. The conditions can include, for example, but are not limited to, slot type, presence of CLI-RSSI measurement, etc. In one example, the slot type can be an XDD slot and / or a non-XDD slot. For example, the WTRU can report a wideband CRI (e.g., wideband beam index) in a non-XDD slot (e.g., when there are no uplink and downlink resources (e.g., due to a duplex operation) in the same slot). In another case, the WTRU can report a sub-band CRI (e.g., sub-band beam index) in an XDD slot (e.g., when the uplink and downlink resources are in the same slot, e.g., based on a duplex operation). Regarding the presence of CLI-RSSI measurement, the bandwidth of beam measurement and / or reporting can be determined based on whether the CLI-RSSI is measured in the same slot.

[0120] The WTRU can be instructed to perform CLI-RSSI measurements at specific frequency positions within the scheduled RBs. In one or more cases, the WTRU can be instructed to perform CLI-RSSI measurements at specific frequency positions within the scheduled RBs. In one or more cases, the WTRU can be instructed to perform CLI-RSSI measurements at specific frequency positions within the scheduled and unscheduled RBs. The specific frequency positions can correspond to one or more of a sub-band, an RB, and an RE. In one or more cases, the instruction can be in DCI that can trigger the CLI-RSSI measurement. The CLI-RSSI measurement can be, for example, an aperiodic CLI-RSSI measurement. In one or more cases, the specific frequency positions can be instructed based on the CRMR resource frequency positions. For example, based on the configuration, one or more CRMR resources can be configured and / or each CRMR resource can be located at a specific frequency position. The WTRU can be instructed to perform measurements on the CRMR resources indicated in the DCI.

[0121] A WTRU may be configured, determined, or instructed to report channel and / or interference measurements. The WTRU may report the measured reference signal strength and / or power (e.g., CLI-RSSI, SRS-RSRP, L1-CLI-RSSI) in a configured resource. In one or more cases, the WTRU may report the level of the measured reference signal strength and / or power based on one or more of the configured and / or determined thresholds. In one example, the WTRU may report the potential presence of interference when the measured power and / or strength is higher than the configured and / or determined threshold. In another example, the WTRU may report the potential presence of partial and / or sub-band edge interference (e.g., CLI) when the difference between measurements in one or more of the resources is higher than the configured and / or determined threshold. Alternatively, the WTRU may report and / or request that one or more of the sub-bands can be trusted to switch when, for example, the measured interference power and / or strength is lower than the configured and / or determined threshold.

[0122] A WTRU may indicate (e.g., via transmission, sending, reporting, etc.) at least one type of (e.g., CLI-related) information content discussed throughout the present disclosure. For example, the information content may correspond to one or more of the level of interference, level of CLI, sub-band unit CLI, measurement results / metrics based on measuring CRMR, delta CLI-RSSI, etc. The WTRU may indicate at least one type of information content, e.g., via negative acknowledgment (NACK) transmission. For example, the WTRU may, along with the NACK transmission, in addition to the NACK transmission, be associated with the NACK transmission and / or based on a HARQ-ACK codebook including one or more (e.g., additional) bits, etc. for indicating at least one type of information content, indicate at least one type of information content level. In one or more cases, the NACK transmission may be performed in response to the reception failure of a scheduled PDSCH. In one example, the WTRU may send a flag signal along with the NACK transmission. For example, the WTRU may send a flag signal along with the NACK transmission in response to the reception failure of a scheduled PDSCH. The flag signal accompanied by the NACK transmission may indicate, for example, that the power and / or intensity of interference is measured and that the measured value of the power and / or intensity is higher than a configured and / or determined threshold. For example, L1-CLI-RSSI being above each respective threshold may indicate the potential presence of interference. In another case, the WTRU may send, along with the NACK transmission, a flag signal for indicating that the NACK may potentially be caused by interference (e.g., CLI) in response to the reception failure of a scheduled PDSCH. For example, the WTRU may send a flag along with the NACK to request a scheduling request (SR) for channel and / or interference measurement (e.g., L1-CLI-RSSI measurement). In one or more cases, the WTRU may be configured to measure and / or sense the interference power / intensity (e.g., CLI via L1-CLI-RSSI) in one or more reference sub-bands.

[0123] The WTRU may construct a list. The list may include, for example, but not limited to, interference measurement results in one or more of the reference sub-bands. In some cases, the list may be ordered in ascending order (e.g., Ref_SB_ordered). In one or more cases, the WTRU may determine and / or detect interference in the active SB (e.g., L1-CLI-RSSI > threshold). The WTRU may send a request including one or more of the sub-bands that the WTRU prefers to switch to (e.g., communicate with the gNB) if the WTRU determines and / or detects interference (e.g., L1-CLI-RSSI > threshold) in the active SB. The WTRU may select, determine, and / or identify one or more of the preferred sub-bands. The WTRU may select, determine, and / or identify one or more of the preferred sub-bands, for example, based on the measured interference power / intensity. The measured interference power / intensity may be the minimum (or, for example, less than a threshold) in the determined list (e.g., Ref_SB_ordered). Thus, the WTRU may report and / or request to switch to a sub-band, BWP, and / or component carrier (CC) if, for example, data transmission and / or reception can be reliably achieved.

[0124] In one or more other cases, the WTRU may construct a list including interference measurement results in one or more of the reference SBs, for example, after the WTRU measures and / or senses interference in the active SB. Thus, the WTRU may report and / or request to switch to a sub-band, BWP, and / or component carrier (CC) when data transmission and / or reception can be reliably achieved (e.g., measured L1_CLI_RSSI < threshold). In one or more cases, the WTRU may determine that the measured interference power and / or intensity (e.g., L1-CLI_RSSI) in one or more of the reference SBs is lower than the configured and / or determined threshold. In one or more cases, the WTRU may determine that the measured interference power and / or intensity (e.g., L1-CLI_RSSI) is not lower than the configured and / or determined threshold in any of the reference SBs. Thus, the WTRU may send a report and / or request to measure one or more other BWPs, a set of RBs, other non-activated CCs, etc. The WTRU may send a report and / or measurement request, for example, to perform a preferred BWP / CC / SB report. In some cases, the BWP in the report and / or request to measure may be, for example, a non-activated BWP.

[0125] The permitted resources, sub-bands, RBs, and scheduled RBs can be used interchangeably and may be consistent with the embodiments disclosed herein. In one or more cases, the WTRU may have multiple grant configurations. The WTRU may determine, identify, and / or be configured by one or more permitted resources. In one or more cases, the WTRU may sense, measure, and / or determine interference signals in one or more of the permitted resources. The WTRU may dynamically select to use or avoid one or more of the permitted resources. Thus, the WTRU may use or avoid one or more of the permitted resources and / or switch between the permitted resources accordingly. For example, the WTRU may use or avoid one or more of the permitted resources based on the level of interference signals and / or switch between the permitted resources accordingly.

[0126] In one or more cases, the determination of the permitted resources to be used and / or switched can be used to perform one or more of the following operations: receiving channels and signals, transmitting channels and signals, etc. For example, the WTRU may be used to determine the permitted resources to receive and / or switch, such as one or more of PDCCH, PDSCH, CSI-RS, SSB (including PBCH for example), PRS, DM-RS, etc. Another example, the WTRU may be used to determine the permitted resources to transmit and / or switch, such as one or more of PRACH, PUCCH, PUSCH, SRS, DM-RS, etc.

[0127] A WTRU may be configured in an operation mode involving dynamic permitted resource determination and / or semi-static permitted resource determination. For example, the WTRU may use one or more operation modes (e.g., dynamic and / or semi-static determination) to determine to use, avoid, and / or switch to permitted resources. The number of configured permitted resources (e.g., the maximum number) may be determined based on the determined, used, and / or configured operation mode. In one or more cases, one or both of the following may apply: the operation mode may be determined based on the number of permitted resources for dynamic operation, and the operation mode may be determined based on the WTRU capabilities and / or gNB configuration, e.g., based on a WTRU capabilities report. In one example, the WTRU may determine the operation mode based on the configured and / or indicated number of permitted resources for dynamic operation. For example, the gNB may indicate and / or configure one or more permitted resources. In some cases, the WTRU may determine to use the semi-static determination mode. In other cases, the WTRU may determine to use the dynamic determination mode. In the case where the gNB indicates and / or configures one permitted resource, the WTRU may determine to use the semi-static determination mode. In the case where the gNB indicates and / or configures two or more permitted resources, the WTRU may determine to use the dynamic determination mode. In another example, it may be determined based on the WTRU capabilities and / or the gNB configuration based on the reported WTRU capabilities. In one or more cases, the WTRU may indicate one or more permitted resources as WTRU capabilities. In one or more cases, the WTRU may determine to use the semi-static determination mode and / or the dynamic determination mode. In the case where the WTRU indicates one permitted resource as WTRU capabilities, the WTRU may determine to use the semi-static determination mode. In the case where the WTRU indicates two or more permitted resources as WTRU capabilities, the WTRU may determine to use the dynamic determination mode. In one or more cases, the gNB configuration may be performed based on the reported WTRU capabilities.

[0128] In one or more cases, the WTRU may request a preferred mode of operation for determining from among the authorized resources. The WTRU may be capable of supporting one or both modes of operation. The WTRU may indicate one or more preferred modes of operation to the gNB. In the case where the WTRU can support both modes of operation, the WTRU may indicate the preferred mode of operation to the gNB. In one or more cases, the WTRU may determine a preferred mode of operation based on one or more of the following: interference intensity, channel quality, and / or traffic.

[0129] The WTRU may determine one or more preferred modes of operation based on interference intensity. For example, the WTRU may determine, identify, and / or configure resources for measuring interference (e.g., CLI) in one or more of the authorized resources. The determined, identified, and / or configured resources may be, for example, but not limited to, NZP-CSI-RS for IMR, ZP-CSI-RS for IMR, SRS resources for SRS-RSRP, etc. Thus, the WTRU may determine to use the dynamic decision mode when the measured interference intensity and / or quality in one or more of the authorized resources is higher than their respective thresholds. In one example, the WTRU may dynamically report, request, and / or switch the authorized resources based on interference intensity.

[0130] The WTRU may determine a preferred mode of operation based on channel quality. For example, the WTRU may measure the channel quality for one or more of the authorized resources. The WTRU may measure channel quality such as CQI, RSRP, SINR, path loss, probability of blockage, etc. In one example, the WTRU may determine to use the dynamic decision mode when the measured channel quality in one or more of the authorized resources is lower than their respective thresholds. Thus, the WTRU may dynamically report, request, and / or switch the authorized resources based on channel quality.

[0131] The WTRU may determine a preferred operating mode based on traffic (e.g., the amount of data received and / or transmitted). The WTRU may determine the traffic (e.g., the amount of data received and / or transmitted). In one example, the WTRU may determine to use a dynamic determination mode for cases where the traffic is higher than respective thresholds. Thus, the WTRU may dynamically report, request, and / or switch permitted resources based on the traffic.

[0132] In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may use permitted resources that are indicated and / or configured for transmitting and / or receiving channels and / or signals and for sensing, processing, and measuring one or more channels and / or signals. In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may transmit and / or receive channels and / or signals using permitted resources that are indicated and / or configured. In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may sense, process, and / or measure one or more channels and / or signals using permitted resources that are indicated and / or configured. In one or more cases, in a second operating mode (e.g., dynamic determination), the WTRU may determine permitted resources from among one or more of the permitted resources based on one or more of the following: gNB indication, WTRU request / report, or a combination of gNB indication and WTRU request / report.

[0133] In one or more cases, in a second operating mode (e.g., dynamic determination), the WTRU may determine permitted resources from among one or more of the permitted resources based on, for example, a gNB indication. In one example, the WTRU may receive an indication of permitted resources based on one or more of the following: indication of a configured grant index, indication of frequency and / or time resources, indication of a TCI state, CRI, and / or SRI, PDCCH transmission in a dedicated CORESET, and / or gNB indication.

[0134] In one or more cases, the WTRU may receive an indication of the authorized resources based on an indication of the configured grant index. For example, the WTRU may be composed of a first authorized resource and a second authorized resource. In one or more cases, the WTRU may be composed of a first authorized resource having a first grant index and a second authorized resource having a second grant index.

[0135] In one or more cases, the WTRU may receive an indication of the authorized resources based on an indication of the frequency and / or time resources. For example, the WTRU may be composed of a first authorized resource and a second authorized resource within the configured time resources. The first authorized resource within the configured time resources may be located, for example, in a first set of subbands. The second authorized resource may be located in a second set of subbands. The WTRU may receive an indication of the frequency subband / resource based on the configuration. The WTRU may receive an indication of a set of subbands, for example, via one or more of DCI, MAC CE, and RRC. In the case where the WTRU receives an indication of a set of subbands, the WTRU may determine a first authorized resource. In the case where the WTRU receives an indication of a second set of subbands, the WTRU may determine a second authorized resource.

[0136] In one or more cases, the WTRU may receive an indication of the authorized resources based on an indication of the TCI state, CRI, and / or SRI. For example, the WTRU may be composed of a first TCI state, CRI, and / or SRI, and a second TCI state, CRI, and / or SRI. The first TCI state, CRI, and / or SRI may be associated with, for example, a first authorized resource. The second TCI state, CRI, and / or SRI may be associated with, for example, a second authorized resource. The WTRU may receive an indication of the TCI state, CRI, and / or SRI (e.g., the first TCI state, CRI, and / or SRI, or the second TCI state, CRI, and / or SRI) via, for example, one or more of DCI, MAC CE, and RRC. In the case where the WTRU receives an indication of the first TCI state, CRI, and / or SRI, the WTRU may determine the first authorized resource. In the case where the WTRU receives an indication of the second TCI state, CRI, and / or SRI, the WTRU may determine the second authorized resource.

[0137] In one or more cases, the WTRU may receive an indication of the authorized resources based on the PDCCH transmission in the dedicated CORESET. For example, the WTRU may be composed of a first CORESET associated with a first authorized resource and a second CORESET associated with a second authorized resource. In another example, the WTRU may be composed of a first CORESET associated with a first authorized resource. In another example, the WTRU may be composed of a second CORESET associated with a second authorized resource. In the case where the WTRU receives the PDCCH via the first CORESET, the WTRU may determine the first authorized resource. In the case where the WTRU receives the PDCCH via the second CORESET, the WTRU may determine the second authorized resource.

[0138] In one or more cases, the WTRU may determine the permitted resources from among one or more of the permitted resources based on a gNB indication. The WTRU may determine the permitted resources based on one or more of priority, modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks, number of repetitions and / or repetition pattern (e.g., type A or type B), configured grant type (e.g., type 1, type 2, or dynamic grant), channel access priority class (CAPC), etc.

[0139] In one or more cases, the WTRU may use, receive, and / or be configured with one or more operating modes for the permitted resources. For example, the one or more operating modes may be determined based on using, switching, and / or avoiding one or more of the permitted resources. The WTRU may receive an indication of the permitted resources and / or each operating mode. In one example, the WTRU may determine to use and / or switch to the indicated permitted resources in a first operating mode. In another example, the WTRU may determine to avoid the indicated permitted resources in a second operating mode. For example, the WTRU may determine to avoid the indicated permitted resources, e.g., via grant cancellation.

[0140] In one or more cases, the use, avoidance, and / or prevention of one or more of the permitted resources may be based on one or more of the following: reports from potential victim WTRUs, and / or reports from aggressor WTRUs. In one example, the WTRU may determine to use, avoid, and / or prevent one or more of the permitted resources based on reports from potential victim WTRUs. In one example, one or more of the victim WTRUs may sense and / or measure the channel or interference (e.g., CLI) quality in one or more of the permitted resources. One or more victim WTRUs may each determine that the measured amount is lower and / or higher than their respective thresholds. One or more of the potential victim WTRUs may report and / or send a request to the WTRU to avoid permitted resources having a channel quality lower than the threshold and / or an interference level higher than their respective thresholds. The WTRU may determine to use, avoid, and / or prevent one or more of the permitted resources based on reports from aggressor WTRUs. In one example, one or more of the aggressor WTRUs may sense and / or measure the channel or interference (e.g., CLI) quality in one or more of the permitted resources. One or more aggressor WTRUs may compare the measured values to their respective thresholds. One or more of the potential aggressor WTRUs may determine that the transmission and / or reception of channels and / or signals on the sensed permitted resources may cause interference (e.g., CLI) on potential victim WTRUs. Accordingly, one or more of the potential aggressor WTRUs may report and / or send a request to the WTRU to avoid their respective permitted resources.

[0141] In one or more cases, in a second mode of operation (e.g., dynamic determination), the WTRU may determine a permitted resource from one or more of the permitted resources based on a WTRU request. For example, the WTRU may request to use, avoid, and / or switch to a permitted resource. The WTRU may determine to use and / or avoid one or more of the permitted resources based on one or more of the following: the WTRU sensing and / or measuring interference at one or more of the permitted resources, a potential aggressor WTRU sensing and / or measuring co-channel interference (CLI) at one or more of the permitted resources, and the potential aggressor WTRU receiving a trigger to sense and / or measure channel and / or interference quality at one or more of the permitted resources (e.g., based on one or more events).

[0142] The WTRU may determine to use and / or avoid one or more of the permitted resources based on the WTRU sensing and / or measuring interference at one or more of the permitted resources. For example, the WTRU may use non-zero power CSI-RS (e.g., NZP-CSI-RS) and / or zero power CSI-RS (e.g., ZP-CSI-RS) for interference measurement resources (IMR). In one example, the WTRU may sense and / or measure CLI based on CLI-RSSI and / or SRS-RSRP. In another example, alternatively or in combination, the WTRU may measure CLI based on L1-CLI-RSSI. For cases where the measured interference (e.g., CLI) is higher than respective thresholds at one or more of the permitted resources, the WTRU may request to use and / or switch to another set of one or more permitted resources. The WTRU may request to use and / or switch to another set of one or more permitted resources where the measured interference (e.g., CLI) is lower than respective thresholds.

[0143] The WTRU may determine to use and / or avoid one or more of the authorized resources based on the potential aggressor WTRU sensing and / or measuring interference (e.g., CLI). The potential aggressor WTRU may sense and / or measure interference in one or more of the authorized resources. For example, the potential aggressor WTRU may use NZP-CSI-RS and / or ZP-CSI-RS for IMR. In another example, the WTRU may sense and / or measure CLI based on CLI-RSSI and / or L1-CLI-RSSI. In one or more cases, the channel and / or interference measurements may be based on periodic, semi-persistent, and / or aperiodic sensing and / or measurements. In another case, alternatively or in combination, the potential aggressor WTRU may be configured to receive SRS signals from one or more of the potential victim WTRUs and / or measure SRS-RSRP. In one example, for cases where the measured SRS-RSRP is higher than respective thresholds, the potential aggressor WTRU may request to prevent and / or avoid respective authorized resources. In another example, the potential victim WTRU may transmit a beamformed SRS signal to the potential aggressor WTRU. In one or more cases, the SRS-based measurements may be based on periodic, semi-persistent, and / or aperiodic sensing and / or measurements.

[0144] Based on one or more events, the WTRU may determine to use and / or avoid one or more of the authorized resources based on the potential aggressor WTRU receiving a trigger to sense and / or measure the channel and / or interference quality in one or more of the authorized resources. In one or more cases, the event-based trigger for sensing and / or measuring may be based on, for example, the reception of one or more NACK signals from a potential victim WTRU at the gNB. In one example, the potential aggressor WTRU may receive an indication of one or more NACK signals from its serving gNB / TRP. For example, the serving gNB / TRP of the potential aggressor WTRU may receive an indication from a second serving gNB / TRP of the potential victim WTRU. The serving gNB / TRP of the potential aggressor WTRU may receive an indication from a second serving gNB / TRP of the potential victim WTRU via, for example, backhaul signaling (e.g., exchange) between the serving gNB / TRP and the second gNB / TRP. For example, for the case where the number of NACK signals received from one or more of the potential victim WTRUs reaches a threshold (e.g., the maximum number of NACK signals) within a duration (e.g., based on a timer), the gNB may trigger event-based channel sensing and / or measurement for one or more potential aggressor WTRUs. In one or more cases, the potential aggressor WTRU may be triggered to measure a reference signal based on an aperiodic resource configuration. The reference signal may include, for example, but not limited to, ZP-CSI-RS, NZP-CSI-RS, CLI-RSSI, L1-CLI-RSSI, and / or SRS.

[0145] Based on one or more of the following, the WTRU may send a request to the gNB to use and / or switch to an authorized resource: explicit signaling, associated uplink resources, channel and / or interference reports, and / or receiving an acknowledgement from the gNB for the WTRU request.

[0146] The WTRU may send a request to the gNB to use and / or switch to an authorized resource based on explicit signaling. The WTRU may send the request to the gNB based on explicit signaling, for example, via one or more of PUCCH, PUSCH, MAC CE, and PRACH. For example, the WTRU may be composed of one or more authorized resources. The WTRU may request an authorized resource among one or more authorized resources based on the configuration. In one example, the indication corresponding to the request may be one or more of the following: an indication of a grant index, and / or an indication of a sub-band and / or a frequency resource.

[0147] The WTRU may send a request to the gNB to use and / or switch to an authorized resource based on an associated uplink resource. In one example, the WTRU may be composed of a first uplink resource associated with a first authorized resource. In another example, the WTRU may be composed of a second uplink resource associated with a second authorized resource. In another example, the WTRU may be composed of a first uplink resource associated with a first authorized resource and a second uplink resource associated with a second authorized resource. For the case where the WTRU transmits an uplink signal via the first uplink, the WTRU and the gNB may determine the first authorized resource. For the case where the WTRU transmits an uplink signal via the second uplink resource, the WTRU and / or the gNB may determine the second authorized resource. The uplink signal may be, for example, but not limited to, one or more of a scheduling request, a HARQ ACK / NACK, and / or a PRACH.

[0148] The WTRU may send a request to the gNB to use and / or switch to an authorized resource based on channel and / or interference reports. In one example, the WTRU may be configured in a first configuration associated with a first authorized resource. In another example, the WTRU may be configured in a second configuration associated with a second authorized resource. In another example, the WTRU may be configured with a first configuration associated with a first authorized resource and a second configuration associated with the second authorized resource(s). In one example, based on the configuration, one or more of the following may apply: The WTRU may report a preferred configuration between the first configuration and the second configuration. The WTRU may report a first channel and / or interference report. The WTRU and the gNB may determine an authorized resource.

[0149] The WTRU may report a preferred configuration between the first configuration and the second configuration. For example, in the case where the WTRU reports the first configuration, the WTRU and the gNB may determine the first authorized resource. In another example, in the case where the WTRU reports the second configuration, the WTRU and the gNB may determine the second authorized resource.

[0150] The WTRU may report a first channel and / or interference (e.g., CSI, SRS, CLI, etc.) report. For example, the WTRU may report a first channel and / or interference report based on the first configuration. In one or more cases, the WTRU may report a second channel and / or interference report. For example, the WTRU may report a second channel and / or interference report based on the second configuration.

[0151] The WTRU and the gNB may determine the permitted resources based on the first channel and / or interference report and the second channel and / or interference report. For example, in the case where the first channel quality of the first CSI report is less than or equal to the second channel quality of the second CSI report, the WTRU and the gNB may determine the second permitted resources. In another example, in the case where the first channel quality is higher than the second quality, the WTRU and the gNB may determine the first permitted resources. The first channel quality and the second channel quality may be, for example, but not limited to, one or more of CQI, L1-RSRP, L1-SINR, etc. In another example, in the case where the first interference quality of the first interference report is greater than or equal to the second interference quality of the second interference report, the WTRU and the gNB may determine the second permitted resources. In another example, in the case where the first interference quality is lower than the second quality, the WTRU and the gNB may determine the first permitted resources. The first and second interference qualities may be, for example, but not limited to, one or more of CLI-RSSI, SRS-RSRP, L1-CLI-RSSI, etc.

[0152] The first configuration and the second configuration can be one or more of the following: CSI report configuration, CSI-RS resource, CSI-RS resource set, BWP and / or sub-band for CSI reporting. In the case of one or more, the first configuration and the second configuration can be one or more of the following: SRS report configuration, SRS resource, SRS resource set, BWP and / or sub-band for SRS reporting. In the case of one or more, the first configuration and the second configuration can be one or more of the following: CLI report configuration, CLI resource, CLI resource set, BWP and / or sub-band for CLI reporting. In the case of one or more, the first configuration and the second configuration can be one or more of the following: CSI report configuration, CSI-RS resource, CSI-RS resource set, BWP and / or sub-band for CSI reporting, SRS report configuration, SRS resource, SRS resource set, BWP and / or sub-band for SRS reporting, CLI report configuration, CLI resource, CLI resource set, BWP and / or sub-band for CLI reporting.

[0153] The WTRU may receive confirmation from the gNB in response to a WTRU request. In one example, the WTRU may receive a confirmation PDCCH. For example, the WTRU may receive the confirmation PDCCH via a dedicated CORESET for gNB confirmation and / or MAC CE. In the case of one or more, the WTRU may experience a time gap from PDCCH reception. The time gap can be, for example, X symbols / slots / ms. For the case where the WTRU experiences a time gap from PDCCH reception (e.g., from the first symbol or the last symbol of PDCCH reception), the WTRU may use, avoid, and / or switch to the required and permitted resources for the operation of the WTRU.

[0154] In a second operation mode (e.g., dynamic determination), the WTRU may determine a permitted resource from one or more of the permitted resources based on a combination of gNB indication and WTRU report / request. In the case of one or more, a combined method of gNB indication and WTRU report may be supported. For example, one or more of the following may apply: The WTRU may receive an indication of one or more permitted resources from the gNB. The WTRU may request one or more permitted resources from the gNB. For example, the WTRU may receive an indication of one or more permitted resources, for example, via an indication of a group of permitted resources from the gNB. The WTRU may request a permitted resource among one or more permitted resources based on the indication. For example, the WTRU may request a permitted resource among one or more permitted resources, for example, via one or more of explicit signaling, associated uplink resources, channels, and / or interference reports. In another example, the WTRU may request one or more permitted resources from the gNB, for example, via one or more of explicit signaling, associated uplink resources, channels, and / or interference reports. The WTRU may receive an indication of a permitted resource among one or more permitted resources based on the indication.

[0155] In the case of one or more, the WTRU may be composed of a counter and / or a timer for permitted resource switching. The WTRU may use, receive, and / or be composed of a counter and / or a timer to switch to one or more of the permitted resources. In one example, the WTRU may be configured to use one or more of the permitted resources, as well as a counter and / or a timer. In another example, the WTRU may be configured to avoid using one or more of the permitted resources, as well as a counter and / or a timer.

[0156] The WTRU may switch from a first permitted resource to a second permitted resource based on a decision. For example, the WTRU may switch from a first permitted resource to a second permitted resource based on a decision corresponding to a gNB indication and / or a WTRU request. The WTRU may apply a counter, for example, after the decision. For example, the WTRU may increment the value of the counter by a certain number (e.g., increment the value by 1) when the WTRU transmits and / or receives one or more channels and / or signals. For the case where the value of the counter is below a threshold, the WTRU may use the second permitted resource. The threshold may be, for example, the maximum value of the counter. For the case where the value of the counter is greater than the threshold, the WTRU may switch from the second permitted resource to the first permitted resource. In some examples, the initial value of the counter may be zero. In some cases, the counter may be started and / or reset when the WTRU switches the permitted resource. In some cases, the counter and the threshold may be pre-defined. In some cases, the counter and the threshold may be indicated, for example, via a MAC CE and / or DCI. In some cases, the counter and the threshold may be RRC-configured. In some cases, the counter and the threshold may be pre-defined, indicated, and / or RRC-configured.

[0157] The WTRU may switch from a first permitted resource to a second permitted resource based on a decision. For example, the WTRU may switch from a first permitted resource to a second permitted resource based on a decision corresponding to a gNB indication and / or a WTRU request. The WTRU may apply a timer, for example, after the decision. In one example, if the timer has not expired, the WTRU may use the second permitted resource. In another example, if the timer has expired, the WTRU may switch from the second permitted resource to the first permitted resource. In some cases, the timer may be started and / or initiated when the WTRU switches the permitted resource. In some cases, the timer may be pre-defined. In some cases, the timer may be indicated, for example, via a MAC CE and / or DCI. In some cases, the timer may be RRC-configured. In some cases, the timer may be pre-defined, indicated, and / or RRC-configured.

[0158] Transmission / reception of one or more channels and / or signals may be one or more of the following: reception of channels and signals, and transmission of channels and signals. Reception of channels and signals may correspond to reception of one or more of, for example, PDCCH, PDSCH, CSI-RS, SSB (including PBCH), PRS, DM-RS, etc. Transmission of channels and signals may correspond to transmission of one or more of, for example, PRACH, PUCCH, PUSCH, SRS, DM-RS, etc.

[0159] The WTRU can be configured to prevent band-edge CLI. The WTRU (e.g., a potential aggressor WTRU) can determine and / or receive an indication that the WTRU is causing interference. For example, the WTRU can determine and / or receive the indication based on gNB indication and / or WTRU sensing / measurement. The WTRU can determine and / or receive an indication that the WTRU is causing interference (e.g., CLI) to one or more victim WTRUs (e.g., band-edge CLI) in one or more of the configured sub-bands. Accordingly, the WTRU can determine to take a prevention action to reduce the interference. In one or more cases, the WTRU can determine to take the prevention action based on, for example, gNB indication and / or WTRU request based on sensing and / or measurement.

[0160] The WTRU can be configured to switch from a first permitted resource to a second permitted resource or can request to switch. In one example, the second permitted resource can include a larger data allocation. Accordingly, the interference (e.g., band-edge CLI) can be reduced due to the larger BWP / sub-band included in the second permitted resource.

[0161] The WTRU may determine, use, and / or be configured with a first power saving / low power mode for a first permitted resource. In one or more cases, the WTRU may determine, use, and / or be configured with a second power saving / low power mode for a second permitted resource. In one or more cases, the WTRU may determine, use, and / or be configured with a first power saving / low power mode for a first permitted resource and a second power saving / low power mode for a second permitted resource. The WTRU may be configured and determined to operate and / or use one or more power saving / low power modes when, for example, one or more permitted resources are used. In one example, the first power saving / low power mode (e.g., the WTRU power saving mode) may be a normal mode in which the WTRU may perform signal transmission and / or reception in one or more of the permitted resources. The WTRU may perform signal transmission and / or reception in one or more of the permitted resources based on each configuration for the permitted resources. For example, a first configuration for a first permitted resource may indicate WTRU transmission and / or reception behavior in the first permitted resource. That is, based on the first configuration of the first permitted resource, the WTRU may determine transmission and / or reception behavior in the first permitted resource. In another example, a second configuration for a second permitted resource may indicate WTRU transmission and / or reception behavior in the second permitted resource. That is, based on the second configuration of the second permitted resource, the WTRU may determine transmission and / or reception behavior in the second permitted resource. Thus, permitted resources for power saving and / or low power may not be associated. In one or more cases, the second power saving and / or low power mode may be a power saving and / or low power mode in which the WTRU performs signal transmission and / or reception in the first permitted resource. The WTRU may perform signal transmission / reception in the first permitted resource based on one or more conditions (e.g., interference, CLI, band edge CLI) in each of the permitted resources, for example.

[0162] The WTRU may be configured with group common instructions for managing permitted resources. For example, the WTRU may receive group common instructions regarding one or more permitted resources, RB sets, and / or potential interference on a sub-band. In one example, the group common instructions may be sent to a group of WTRUs. The group of WTRUs may include at least a first set of WTRUs (e.g., potential victim WTRUs), and / or a second set of WTRUs (e.g., potential aggressor WTRUs). In one or more cases, the WTRU may measure and / or report configured channel and / or interference measurements in the configured resources. For example, upon receipt of a group common instruction (e.g., group common DCI), the WTRU may measure and / or report configured channel and / or interference measurements in the configured resources. In some cases, the WTRU (e.g., potential victim WTRU) may determine to avoid a permitted resource and / or sub-band. For example, the WTRU may determine to avoid a permitted resource and / or sub-band based on the received instruction and / or based on the measurements performed. In some cases, the WTRU may determine to switch to other permitted resources and / or sub-bands. In some cases, the WTRU (e.g., potential aggressor WTRU) may determine to avoid a permitted resource and / or sub-band. For example, the WTRU may determine to avoid a permitted resource and / or sub-band based on the received instruction and / or based on the measurements performed. In some cases, the WTRU may determine to use prevention actions. For example, the WTRU may determine to use prevention actions by switching to other permitted resources and / or sub-bands and / or by power reduction techniques. In one or more cases, the WTRU may receive WTRU-specific and / or group common instructions regarding a change in the role of the WTRU. For example, a change in the role of the WTRU may be, for example, a victim WTRU changing to an aggressor WTRU and vice versa.In some cases, the WTRU may use channel and / or interference measurement results to cause interference and / or avoid being affected (e.g., by interference from a potential aggressor WTRU).

[0163] The WTRU may be configured for CLI sensing and / or measurement based on directional SRS-RSRP. In one example, the WTRU may be configured to sense and / or measure interference and / or for SRS reception and measurement, and / or may receive signaling indicating one or more TCI states. Interference may include, for example, but is not limited to, CLI, L1-CLI-RSSI, SRS-RSRP, etc. In one or more cases, the signaling indicating one or more TCI states may be configured by DCI, MAC CE, and / or RRC. For example, the WTRU may use at least one spatial domain filter to receive, sense, and / or measure each reference signal. In one example, the WTRU may receive a TCI state and / or an SRS resource indicator (SRI) to measure each SRS signal (e.g., SRS-RSRP). In one or more cases, one or more of the following may apply. For example, the WTRU (e.g., a potential victim WTRU) may determine and / or be configured to use a spatial filter. The spatial filter may be, for example, the same spatial filter used to receive a set of reference signals indicated by the TCI state for each CORESET used by the WTRU to monitor the PDCCH. In another case, the WTRU (e.g., a potential aggressor WTRU) may use a spatial filter to determine and / or measure the potential effects and / or interference that the spatial filter may cause, and / or may be configured to measure. For example, the WTRU may use a spatial filter to determine and / or measure the potential effects and / or interference that the spatial filter may cause in a direction indicated by, for example, a configured TCI state, and / or may be configured to measure. In one or more cases, the WTRU may report directional channel and / or interference sensing and / or measurement to the gNB.

Claims

Claim 1 A wireless transmit / receive unit (WTRU) comprising a processor, the processor receiving configuration information indicating a plurality of sub-bands for cross-link interference (CLI) measurement and respective resources for performing CLI measurement for each of the plurality of sub-bands, receiving downlink control information (DCI) indicating resources associated with a first reference sub-band, performing CLI measurement for the first reference sub-band using one or more resources for performing CLI measurement for the first sub-band, and based on determining that the CLI measurement value for the first sub-band is greater than a threshold, performing CLI measurement for at least one other sub-band of the plurality of sub-bands using the respective resources for CLI measurement for the at least one other sub-band, and configured to send an indication that the CLI measurement value for the sub-band is greater than the threshold. Claim 2 The WTRU according to claim 1, wherein the processor is further configured to send information indicating a second sub-band. Claim 3 The WTRU according to claim 2, wherein the indicated second sub-band is determined to have the lowest measured CLI among the plurality of sub-bands. Claim 4 The WTRU according to claim 1, wherein the processor is further configured to perform the CLI measurement for the first sub-band based on the number of downlink data reception failures for the first sub-band exceeding a first threshold. Claim 5 The WTRU according to claim 1, wherein the processor is further configured to perform the CLI measurement for the first sub-band based on the number of hybrid automatic repeat request negative acknowledgments (HARQ NACKs) sent by the WTRU for transmission in the first sub-band exceeding a second threshold. Claim 6 The WTRU according to claim 1, wherein the processor is further configured to perform the CLI measurement for the first sub-band based on an explicit indication from the network. Claim 7 ​ ​ ​ ​ ​ ​ For each of the plurality of sub - bands, each of the resources for performing a CLI measurement includes one or more of a zero - power channel state information reference signal (ZP - CSI - RS), a non - zero - power channel state information reference signal (NZP - CSI - RS), or a sounding reference signal (SRS), the WTRU according to claim 1. Claim 8 The received DCI includes a downlink (DL) allocation indicating the first reference sub - band for scheduling a physical downlink shared channel (PDSCH), the WTRU according to claim 1. Claim 9 The processor is further configured to perform the CLI measurement for the at least one other sub - band by performing one or more of a physical layer cross - link interference received signal strength indicator (L1 - CLI - RSSI) measurement, a sub - band - unit CLI measurement, or a delta CLI measurement, the WTRU according to claim 1. Claim 10 The CLI measurement includes an overlapping CLI, a partially overlapping CLI, or a non - overlapping sub - band CLI, the WTRU according to claim 9. Claim 11 A method comprising: Receiving configuration information indicating a plurality of sub - bands for cross - link interference (CLI) measurement and respective resources for performing a CLI measurement for each of the plurality of sub - bands; Receiving downlink control information (DCI) indicating resources associated with a first reference sub - band; Performing a CLI measurement for the first reference sub - band using one or more resources for performing a CLI measurement for the first sub - band; Based on determining that the CLI measurement value for the first sub - band is greater than a threshold, performing a CLI measurement for at least one other sub - band of the plurality of sub - bands using the respective resources for the CLI measurement of the at least one other sub - band; Sending an indication that the CLI measurement value for the sub - band is greater than the threshold. Claim 12 The method according to claim 11, further comprising sending information indicating a second sub - band. Claim 13 The method according to claim 12, wherein the second subband shown is determined to have the lowest measured CLI among the plurality of subbands.

14. The method according to claim 11, further comprising performing the CLI measurement for the first subband based on the number of downlink data reception failures for the first subband exceeding a first threshold.

15. The method according to claim 11, further comprising performing the CLI measurement for the first subband based on the number of hybrid automatic repeat request negative acknowledgments (HARQ NACKs) sent by the WTRU for transmission in the first subband exceeding a second threshold.

16. The method according to claim 11, further comprising performing the CLI measurement for the first subband based on an explicit instruction from the network.

17. The method according to claim 11, wherein each of the respective resources for performing the CLI measurement for each of the plurality of subbands includes one or more of a zero-power channel state information reference signal (ZP-CSI-RS), a non-zero-power channel state information reference signal (NZP-CSI-RS), or a sounding reference signal (SRS).

18. The method according to claim 11, wherein the received DCI includes a downlink (DL) allocation indicating the first reference subband for scheduling a physical downlink shared channel (PDSCH).

19. The method according to claim 11, further comprising performing the CLI measurement for the at least one other subband by performing one or more of a physical layer cross-link interference received signal strength indicator (L1-CLI-RSSI) measurement, a subband unit CLI measurement, or a delta CLI measurement.

20. The method according to claim 19, wherein the CLI measurement includes an overlapping CLI, a partially overlapping CLI, or a non-overlapping subband CLI.

Images