Sensing-based interference mitigation in NR duplexing

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) measurements and respective resources for performing CLI measurements on each of the plurality of sub-bands. The processor may receive downlink control information (DCI) indicating resources associated with the first reference subband. The processor may perform CLI measurements on the first reference subband using one or more resources for performing CLI measurements on the first subband. The processor may perform a CLI measurement on at least one other sub-band of the plurality of sub-bands using a respective resource for performing a CLI measurement on the at least one other sub-band based on determining that the CLI measurement for the first sub-band is greater than a threshold. The processor may transmit an indication that the CLI measurement of the subband is greater than the threshold.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 334,991, filed on April 26, 2022, the entirety of which is incorporated herein by reference. Background Art

[0003] Wireless communication has become one of the most successful innovations in modern history. The demand for wireless data traffic is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (such as tablets, laptops, netbooks, e-book readers and machine-like devices) among consumers and enterprises. In order to meet the high growth of mobile data traffic and support new applications and deployments, it is critical to improve the efficiency and coverage of the radio interface. Summary of the invention

[0004] The present disclosure as a whole relates to devices, methods and systems for handling interference. More specifically, the present disclosure relates to mitigating interference in NR duplex. For example, the present disclosure provides subband-level channel and / or interference sensing at a disturbed wireless transmit / receive unit (WTRU), etc. In another example, the present disclosure provides subband post-sensing avoidance reporting (ARAS), etc. Moreover, the present disclosure provides post-sensing transmission avoidance, etc. at an disturber WTRU. In addition, the present disclosure also provides directional CLI sensing and measurement, etc.

[0005] In one or more aspects, the present invention relates to methods and apparatus implemented to mitigate interference in NR duplex. For example, a victim WTRU receives a measurement and reporting configuration for one or more reference subbands. In one example, the victim WTRU receives a trigger for sensing / measuring interference sensing / measurement. In one example, the victim WTRU measures a cross-link interference-received signal strength indicator (CLI-RSSI) or a sounding reference signal-reference signal received power (SRS-RSRP) on the configured frequency / subband resources. In one example, the victim WTRU reports the CLI-RSSI or SRS-RSRP measurement via L1 signaling. In one example, when the WTRU does not sense interference, the victim WTRU requests to switch to another reference subband.

[0006] In one example, in one or more aspects, an aggressor WTRU determines one or more reference subbands to which the WTRU may switch when causing CLI to a victim WTRU in an active SB. In one example, the aggressor WTRU performs event-based CLI / channel occupancy sensing in the active SB.

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

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

[0009] The processor may be configured to transmit information indicating a second subband. The indicated second subband is determined to have a lowest measured CLI among the plurality of subbands.

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

[0011] The corresponding resources for performing CLI measurement on each of the multiple subbands 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).

[0012] The DCI may include a downlink (DL) assignment indicating that the first reference subband schedules a physical downlink shared channel (PDSCH).

[0013] The processor may be configured to perform the CLI measurement on 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-level CLI measurement, and / or a variable CLI measurement. In some examples, the CLI measurement may include overlapping CLI, partially overlapping CLI, or non-overlapping subband CLI. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A more detailed understanding may be obtained from the following description, given by way of example with reference to the accompanying drawings, in which like reference numerals indicate similar elements.

[0015] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0016] Figure 1B is an example that can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown.

[0017] Figure 1C is an example that can be Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) for use within a communication system is shown.

[0018] Figure 1D is an example that can be Figure 1A A system diagram of another example RAN and another example CN used within the communication system shown.

[0019] Figure 2 is a diagram illustrating an example of cross-link interference (CLI) directional sensing.

[0020] Figure 3 is a diagram illustrating an example of Cross Division Duplex (XDD).

[0021] Figure 4 is a diagram illustrating an example of inter-gNB and inter-WTRU cross-link interference (CLI). DETAILED DESCRIPTION

[0022] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more 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 multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ 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 multi-carrier (FBMC), etc.

[0023] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should 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 may 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 (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-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 Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0025] The base station 114a may be part of the RAN 104 / 113, which may 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. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

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

[0027] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 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 (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

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

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

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

[0031] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio 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 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0032] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio 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 may implement a radio 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 may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0033] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the text and video, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0034] The CN 106 / 115 may also serve as a gateway for the 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 plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0036] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, 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, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0037] The processor 118 may be a general purpose processor, a special purpose 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 circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0039] Although the transmit / receive element 122 Figure 1B 1 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 over the air interface 116.

[0040] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

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

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

[0043] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0044] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 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, module, frequency modulation (FM) radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: 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.

[0045] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0046] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0047] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0048] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

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

[0050] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0051] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during an inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0052] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0053] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0054] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0055] In a representative embodiment, the other network 112 may be a WLAN.

[0056] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a target outside the BSS may be transmitted to the AP to be delivered to the corresponding target. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the target STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the target STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0057] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be a working channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) 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. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0058] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0059] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0060] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0061] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operation mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operation mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

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

[0063] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0064] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0065] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmit time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths over time).

[0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0067] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0068] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing in order to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0070] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0071] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0072] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0073] Given that Figures 1A to 1D as well as Figures 1A to 1D , one or more or all of the functions described herein for one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182ab, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0074] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.

[0075] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) can be used by the simulation device to send and / or receive data.

[0076] This document uses the following abbreviations and acronyms, among others: 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 (e.g., access, channel, resource) (CB); clear channel assessment (CCA); code division multiplexing (CDM); cell group (CG); cross-link interference (CLI); coordinated multipoint transmission / reception (CoMP); channel occupation time (COT); cyclic prefix (CP); common phase error (CPE); conventional OFDM (cyclic prefix dependent) (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 transmission (e.g., LTE sidelink) (D2D); 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 acknowledgement (HARQ NACK); Inter-cell interference (ICI); Inter-cell interference cancellation (ICIC); Internet Protocol (IP); Listen before talk (LBT); Logical channel (LCH); Logical channel identification (LCID); Logical channel prioritization (LCP); Low latency communication (LLC); Long Term Evolution (e.g., from 3GPP LTE R8 and higher) (LTE); Medium Access Control (MAC); Medium Access Control Control Element (MAC CE); Negative ACK (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 Dual Connectivity (NE-DC); New Radio (NR); New Radio Dual Connectivity (NR-DC); Orthogonal Frequency Division Multiplexing (OFDM); Out-of-Band (Transmit) (OOB); Total Available WTRU Power in a Given Transmission Interval (Pcmax); Primary Cell of a Primary Cell Group (Pcell); 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 (PSCell) of the Secondary Cell Group; Primary Synchronization Signal (PSS); Phase Tracking Reference Signal (PT-RS); Quality of Service (from the physical layer perspective) (QoS); Radio Access Bearer (RAB); Radio Access Network Paging Area (RAN The following are the terms used in this document: PA); Random Access Channel (or Procedure) (RACH); Random Access Response (RAR); Radio Access Technology (RAT); Resource Block (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 (for MBMS) (ROM); Radio Resource Control (RRC); Radio Resource Management (RRM); Reference Signal (RS); Round Trip Time (RTT); Secondary Cell Group (SCG); Single Carrier Multiple Access (SCMA); Subcarrier Spacing (SCS); Service Data Unit (SDU); Spectrum Operation Mode (SOM); Semi-Persistent (SP); Primary Cell (SCG) of a Primary Cell Group or a Secondary Cell Group pCell); signaling radio bearer (SRB); synchronization signal (SS); sounding reference signal (SRS); secondary synchronization signal (SSS); supplementary uplink (SUL); switching gap (in independent subframe) (SWG); transport block (TB); transport block size (TBS); transmit configuration index (TCI); time division duplex (TDD); time division multiplexing (TDM); time interval (in integer multiples of one or more symbols) (TI); transmit time interval (in integer multiples of one or more symbols) (TTI); transmit / receive point (TRP); transmit / receive point group (TRPG); tracking reference signal (TRS); transceiver (TRx); uplink (UL); ultra-reliable communication (URC); ultra-reliable low latency communication (URLLC); vehicular communication (V2X); wireless local area networks and related technologies (IEEE 802.xx domain) (WLAN); and cross-division duplexing (XDD). ;

[0077] In one embodiment, avoid using report after sensing (ARAS) may be performed. For example, a potential victim WTRU may receive measurement and / or reporting configuration for a series 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 the time-frequency resource mask (e.g., a set of subbands or a set of symbols / time slots). In one example, the measurement / sensing configuration may include one or a combination of reference signals, 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 CSI quantities and time / frequency reporting resources. The CSI quantities may include, for example, but not limited to, CLI-RSSI, SRS-RSRP, etc.

[0078] 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 CLI). The WTRU may receive a trigger for event-based interference sensing and / or measurement of one or more reference SBs in 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 a victim WTRU determining one or more DL reception failures. For example, the victim WTRU may determine one or more DL reception failures, for example, in addition to sending 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 a need to avoid using a certain SB and a need for the WTRU to communicate through another SB. For example, as a supplementary mechanism to XDD, the WTRU may need to communicate via another SB.

[0079] In one or more cases, the WTRU may receive certain types of interference measurements. For example, the types of interference measurements may include, but are not limited to: overlapping CLI, partially overlapping CLI, and / or non-overlapping CLI. Overlapping CLI may be, for example, intra-subband CLI. Partially overlapping CLI may be, for example, a set of cells / TRPs with partially overlapping RBs between UL and DL, which belongs to inter-subband CLI. Non-overlapping CLI may be inter-subband CLI.

[0080] In one example, the WTRU may measure CLI-RSSI and / or SRS-RSRP on the configured frequency / subband resources for a given short period of time. The measurement may be reported via L1 signaling (e.g., reporting L1-CLI-RSSI via PUCCH, PUSCH, RACH, SRS). For example, the WTRU may report the measurement. L1 signaling (such as but not limited to L1-CLI-RSSI) may be reported via PUCCH, PUSCH, RACH, SRS, etc. In one example, the WTRU may receive a configuration for variable CLI-RSSI measurement. In some cases, the WTRU may determine the variable CLI-RSSI. For example, the WTRU may determine the variable 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, a first CLI-RSSI may be measured from a resource located in the middle of a scheduled RB. In some cases, a second CLI-RSSI may be measured from a resource located at an edge of a scheduled RB. In one or more cases, the WTRU may report a variable CLI-RSSI based on the measured variable CLI-RSSI being greater than a threshold value indicating a potential edge RB CLI. The potential edge RB CLI may be, for example, a non-overlapping CLI.

[0081] For situations 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 a corresponding threshold. In one or more cases, in addition to NACK transmission, the WTRU may also transmit a mark to indicate potential interference. For example, the mark may indicate that the NACK transmission may be based on sensed interference. For example, when the L1-CLI-RSSI is greater than or equal to the corresponding threshold, sensed interference may occur. In another example, the mark may also indicate that the NACK transmission may be based on interference, such as CLI. Based on the interference, the WTRU may request an SR to perform interference measurements (e.g., L1-CLI-RSSI). In one or more cases, the WTRU may request (e.g., from Ref_SB) to switch to another reference subband. For example, the WTRU requests to switch to another reference subband in which the WTRU may not have sensed interference. For example, the WTRU may request to switch to another reference subband such as, but not limited to, L1-CLI-RSSI below a corresponding threshold.

[0082] Transmission avoidance may be performed after sensing. In some cases, the potential aggressor WTRU may determine a list of reference subbands (e.g., Ref_SB). For example, in the case where CLI may be caused to the potential victim WTRU in the active SB, the WTRU may switch to the reference subbands in the list. For example, the WTRU may receive a subset of the time-frequency resource mask, such as but not limited to a set of subbands or a set of symbols / time slots. In some cases, the aggressor WTRU may perform event-based CLI / channel occupancy sensing in the active SB. For example, when the victim WTRU determines one or more DL reception failures, the aggressor WTRU performs event-based CLI / channel occupancy sensing in the active SB. 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, in addition to sending 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 (e.g., a timer). In some cases, the WTRU may determine that a potential victim WTRU is using the DL based on the aggressor WTRU detecting channel occupancy. In one example, the WTRU may report one or more of the subbands to switch to, thereby suggesting UL SB / BWP / CC that may not cause CLI to the potential victim UE. In some cases, alternatively or in conjunction, the aggressor WTRU may receive an indication that prevents the aggressor WTRU from transmitting in one or more of the configured granted resources. The aggressor WTRU may receive an indication that prevents the aggressor WTRU from transmitting in one or more of the configured granted resources due to interference (e.g., grant cancellation). In one example, the aggressor WTRU may be prevented from transmitting in the granted resources in one or more of the upcoming slots / symbols (the slot / symbol resources may be identified therein). In one or more cases, the aggressor WTRU and / or the victim WTRU may receive a group common DCI. The group common DCI may indicate, for example, but not limited to, mutual interference and / or measurement, reporting, and / or SB level avoidance.

[0083] CLI sensing / measurement may be based on directional SRS-RSRP. In one or more cases, the potential victim WTRU may measure the SRS-RSRP from one or more potential interferer WTRUs. The potential victim WTRU may measure the SRS-RSRP from one or more potential interferer WTRUs based on directional measurements. In one example, the WTRU may determine a spatial domain filter for receiving SRS signals. The spatial domain filter may be, for example, the same spatial domain filter used to receive the RS set indicated by the TCI state for the corresponding CORESET, which is used by the WTRU to monitor the PDCCH. In one example, the WTRU may use at least one spatial domain filter to receive SRS signals during the measurement of SRS-RSRP. In one or more cases, the WTRU may report directional CLI / channel sensing accordingly.

[0084] Figure 2 2 is a diagram illustrating a system 200 performing exemplary 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. Figure 2 , the victim WTRU 208 may report directional CLI / channel sensing.

[0085] Figure 3 is a diagram illustrating an example of Cross-Split Duplex (XDD) 300. In one example, a RAN project on New Radio (NR) duplex operation can provide a basis for improving conventional TDD operation by enhancing UL coverage, increasing capacity, reducing latency, etc. TDD can be based on splitting the time domain between uplink and downlink. In one example, full duplex (e.g., Cross-Split Duplex (XDD)) belonging to sub-band non-overlapping full duplex can be implemented on the gNB side within the TDD band, such as Figure 3 shown.

[0086] Figure 4 is a diagram illustrating an example system 400 that is subject to inter-gNB and inter-WTRU cross-link interference (CLI). Implementing XDD may require addressing challenges that may arise due to cross-link interference (CLI), such as Figure 4As shown. For example, in an 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 cause subband-level CLI on the potential victim gNB and WTRU in one example. In one example, the CLI-RSSI measurement may be based on long-term measurements. In UL to DL CLI, the CLI from the aggressor WTRU may cause strong interference to the victim WTRU in a specific SB, while other SBs may not be affected. CLI in XDD may not be limited to WTRUs located at the edge of the cell. In contrast, WTRUs located in the center and / or middle of the beam may be affected by CLI. Therefore, the WTRU may be configured to perform SB-level CLI measurements.

[0087] In some cases, CLI may be caused by another WTRU. In the case where another WTRU causes CLI, the CLI may depend on the direction of the transmit beam. In addition, CLI may also depend on sensing in all directions, which may lead to CLI detection errors. Based on CLI detection errors, different WTRU behaviors may lead to situations where subband level CLI occurs in XDD. Therefore, the WTRU may be configured to perform channel sensing for potential subband level CLI, avoid CLI by switching to other SBs, and perform directional CLI sensing in XDD, as described herein.

[0088] In one or more cases where CLI is sensed, the WTRU may be configured to determine and / or switch to an SB that is not affected by CLI, as described herein. In one or more cases, the disturber WTRU may be configured to be responsible for the interference caused by the victim WTRU. In one or more cases, the WTRU may be configured to discover the optimal method to measure CLI in the active SB and the potential SB for switching. In one or more cases, subband level channel and / or interference sensing may be performed at the victim WTRU. In one or more cases, avoidance reporting after subband sensing (ARAS) may be performed. In one or more cases, avoidance may be sent after sensing at the disturber WTRU. In one or more cases, directional CLI sensing and measurement may be performed.

[0089] As used herein, "a" and "an" and similar phrases are interpreted as "one or more" and "at least one". Any term ending with the suffix "(s)" may be interpreted as "one or more" and "at least one". The term "may" may be interpreted as "may, for example".

[0090] The WTRU may send or receive a physical channel or reference signal. In one example, the WTRU may send or receive a physical channel or reference signal based on 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 use the same spatial domain filter as the spatial domain filter used to receive RS (e.g., CSI-RS) and / or SS blocks to send physical channels and / or signals. In one or more cases, the WTRU transmission may be referred to as a "target". In one or more cases, the received RS and / or SS blocks may be referred to as a "reference" and / or "source". In this case, the WTRU may be configured to send a target physical channel and / or signal. In one example, the WTRU may be configured to send a target physical channel and / or signal based on a spatial relationship with reference to such RS and / or SS blocks. In one or more cases, the WTRU may send a first physical channel and / or signal. In one example, the WTRU may be configured to send a first physical channel and / or signal based on the same spatial domain filter as the spatial domain filter used to send a second physical channel and / or signal. In one example, the first transmission and / or the second transmission may be referred to as a "target" and a "reference" (and / or, e.g., a "source"), respectively. In this case, the WTRU may transmit a first (e.g., target) physical channel and / or signal based on a spatial relationship with reference to a 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 RRC. In one or more cases, the spatial relationship may be signaled by a MAC CE and / or a DCI. For example, the WTRU may implicitly transmit a physical uplink shared channel (PUSCH) and / or a demodulation reference signal (DM-RS) for the PUSCH based on the same spatial domain filter as the SRS which may be indicated by an SRI, which may be indicated in the DCI and / or configured by RRC. In another example, the spatial relationship may be configured by RRC for an SRS resource indicator (SRI) and / or signaled by a MAC CE for a PUCCH. The spatial relationship may be referred to as a "beam indication."

[0091] The WTRU may receive a first (e.g., target) downlink channel and / or signal based on the same spatial domain filters 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 corresponding DM-RS. In one example, such an association may exist when the WTRU may be configured with a quasi-co-location (QCL) assumption type D between corresponding antenna ports, for example, when the first signal and the second signal are reference signals. In one example, such an association may be configured as a TCI (transmission configuration indicator) state. In one or more cases, the WTRU may be indicated as an association between a CSI-RS and / or SS block and a DM-RS by an index to a set of TCI states (which may be configured by RRC and / or signaled by a MAC CE). Such an indication may be referred to as a "beam indication".

[0092] Transmit and receive point (TRP) may be used interchangeably with one or more of a transmit point (TP), a receive point (RP), a radio remote head (RRH), a distributed antenna (DA), a base station (BS), a sector (e.g., a sector of a BS), and / or a cell (e.g., a geographic cell area served by a BS). Multi-TRP may be used interchangeably with one or more of MTRP, M-TRP, and / or multiple TRPs.

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

[0094] The term "XDD" may be used to refer to subband-level duplexing. In one or more cases, UL or DL ​​may be used per subband. XDD may be characterized by one or more of the following: cross-division duplexing; subband-based full duplexing; frequency domain multiplexing (FDM) of DL / UL transmissions within the TDD spectrum; subband non-overlapping full duplexing; full duplexing other than co-frequency full duplexing; advanced duplexing methods, such as other than (e.g., pure) TDD or FDD, etc. Cross-division duplexing may be, for example, subband-level FDD within a TDD band. Subband-based full duplexing may be, for example, full duplexing because both UL and DL may be used / mixed on a symbol / time slot, and UL or DL ​​therein may be used per subband on a symbol / time slot. Other full duplexing other than co-frequency full duplexing may include, for example, but not limited to, spectrum sharing, subband-level overlapping, etc.

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

[0096] 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 or group identification); measurements, such as L1-RSRP, L1-SINR obtained from SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR); other channel state information; and the like. 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); and the like.

[0097] The WTRU may be configured to perform LBT channel sensing. In one example, in operation with shared spectrum channel access, the WTRU may trigger an LBT failure indication. For example, the WTRU may trigger an LBT failure indication based on a received signal strength indicator (RSSI) measured in an 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 an 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 opportunity may appear at the first symbol of a subframe of an SFN and / or NR. In one example, a subframe of an NR may be based on a configured subframe offset. In one example, the frequency resource used 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 used for RSSO measurement. In one example, a reference subcarrier spacing (SCS) and a cyclic prefix (CP) may be used for RSSI measurement (e.g., ref-SCS-CP).

[0098] The WTRU may be configured with one or more parameters for detecting consecutive LBT failures. For example, the WTRU may be configured to detect consecutive LBT failures, such as lbt FailureRecoveryConfig. In one or more cases, the WTRU may be configured with one or more of the following parameters: an LBT counter, an LBT timer, and a maximum count of LBT failure indications. The LBT counter may be, for example, LBT_COUNTER. In one or more cases, the LBT counter may be a counter for consecutive uplink LBT failure detections. In one example, the LBT counter may increase by 1 with 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 consecutive uplink LBT failure detections. In one example, the LBT timer may be started and / or restarted using the LBT failure indication. In one or more cases, the maximum value (i.e., maximum count) of the LBT failure indication may be, for example, lbt-FailureInstanceMaxCount. In one example, the maximum counter may determine the maximum number of times the LBT failure indication is expected to occur. For example, the maximum counter may determine the maximum number of times the LBT failure indication is expected to occur (e.g., before the WTRU triggers LBT failure recovery detection).

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

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

[0101] The WTRU may measure and / or report channel state information (CSI). In one example, the CSI for each connection mode may include and / or be configured with 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 amount, CSI report type, CSI report codebook configuration, and CSI report frequency. The CSI report amount 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, non-periodic, 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, a CSI-RS resource set may include one or more CSI resource settings. The CSI resource settings may include, for example, but not limited to: NZP-CSI-RS resources for channel measurement; NZP-CSI-RS resources for interference measurement; and CSI-IM resources for interference measurement. NZP CSI-RS resources 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.).

[0102] The WTRU may indicate, determine and / or be configured with one or more reference signals. In one example, the WTRU may monitor, receive and / or measure one or more parameters, for example based on the corresponding reference signals. For example, these parameters may include one or more of the following: SS-RSRP; CSI-RSRP; SS-SINR; CSI-SINR; RSSI; CLI-RSSI; and SRS-RSRP. It should be noted that 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 the reference signal measurement. In one example, one or more of these parameters may be included in the reference signal measurement. In another example, other parameters may be included in the reference signal measurement.

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

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

[0105] The indication by DCI may include one or more of the following: an explicit indication by a DCI field and / or by an RNTI, and an implicit indication by an attribute. 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 an attribute may be, for example, a DCI format, a DCI size, a Coreset and / or a search space, an aggregation level, a first resource element of a received DCI (e.g., an index of a first control channel element). In one example, the mapping between attributes and values ​​may be signaled by RRC and / or MAC.

[0106] In one or more cases, RS may be used interchangeably with one or more of RS resources, RS resource sets, RS ports, and / or RS port groups, and consistent with the disclosed embodiments. In one or more cases, RS may be used interchangeably with one or more of SSB, CSI-RS, SRS, and / or DM-RS, and consistent with the disclosed embodiments. In one or more cases, interference may be used interchangeably with CLI, CLI-RSSI, and / or SRS-RSRP, and consistent with the disclosed embodiments.

[0107] In one or more cases, avoid using reporting after sensing (ARAS) may be performed. 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 not limited to, one or more DL RS (e.g., CSI-RS) resources. The one or more DL RS resources may be used for DL ​​measurements, for example, to derive and / or determine CSI (and / or beam index and / or beam quality metric), which may be reported in a time instance of a CSI / beam report. 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 gNB may determine the beam / TCI indication and / or configuration based on the CSI / beam report from the WTRU. In one example, the WTRU may receive a grant (e.g., including a DCI for DL ​​assignment) scheduling reception of DL signals. The WTRU may receive the DL signal using a spatial filter, which may be determined based on the beam / TCI indication, for example.

[0108] In one or more cases, there may be interference based on a signal transmitted by a second WTRU (e.g., a WTRU in the vicinity of the WTRU), and the interference may affect (e.g., degrade and / or reduce) the DL signal reception performance at the WTRU. In one or more cases, the existence of the interference may not be known before authorization. For example, in a case where the second WTRU may be associated with a different serving cell / TRP than the WTRU, the existence of the interference may not be known before authorization. In one example, the WTRU may fail to receive a DL signal based on the interference. For example, the interference may be a WTRU-to-WTRU CLI based on a second UL signal of the WTRU. In some cases, the interference may not be captured in the CSI / beam report. For example, because one or more DL RS resources may reflect (e.g., involve) an UL signal transmission by a second WTRU, the interference may not be captured in the CSI / beam report. For example, the DL signal may cause a degradation in the DL performance of the communication between the gNB and the WTRU. In one or more cases, the failure to receive the DL signal may continue to occur. For example, in the case where the gNB retransmits the DL signal, the WTRU may fail to receive the DL signal. In the case where the unexpected WTRU-to-WTRU CLI may exist for a period of time, the WTRU may fail to receive the DL signal.

[0109] 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 switch to. In one or more cases, the reference subband list may be indicated to the WTRU and / or configured. For example, the WTRU may be instructed to switch to a subband, the WTRU may be instructed to use the subband for communication between the WTRU and the gNB, and / or the WTRU may be instructed to use the subband to check the CLI. The WTRU may check the CLI by, for example, measuring, estimating, and / or determining the CLI. In one or more cases, the WTRU may receive a reference subband list as a subset of a time-frequency resource mask (e.g., a set of subbands and / or a set of symbols / time slots, etc.). The WTRU may receive a configuration for performing CLI sensing and / or measurement on the Ref_SB.

[0110] The WTRU may receive a trigger to perform CLI sensing and / or measurement on a Ref_SB. In one example, the WTRU may explicitly receive the trigger and / or measurement. For example, the measurement may include non-periodic channel sensing. In one or more cases, the trigger may be based on an active (e.g., current, currently communicating with a 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, a current SB, an SB currently communicating with a 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 initiate (e.g., implement, start, conduct, and / or perform, 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 initiate CLI sensing and / or measurement based on, for example, at least one reference SB (e.g., Ref_SB) and / or at least one indicated, pre-configured, and / or predetermined resource.

[0111] The WTRU may send (e.g., report) at least SB-related information content. The SB-related information content may include, for example, but not limited to, one or more SB indices, corresponding SB-level metrics, etc. The SB-level metrics may include, for example, but not limited to, SB-level CLI-RSSI, SB-level quality metrics, etc. In one or more cases, the WTRU may send at least SB-related information content based on CLI sensing and / or measurement being performed and / or implemented. For example, the WTRU may send at least SB-related information content after performing and / or implementing CLI sensing and / or measurement. In this way, the gNB can use the reported SB-related information content to avoid using certain RBs and communicate with the WTRU. This can be used as an example of a post-sensing avoidance report (ARAS) mechanism, which can be applied at the WTRU (e.g., based on an ARAS configuration that may be received at the WTRU).

[0112] The at least one event / condition for initiating CLI sensing / measurement may include one or more of the following examples. For example, when the WTRU (e.g., the victim WTRU) determines that one or more (e.g., K times) DL data (e.g., PDSCH) reception fails, CLI sensing / measurement may be initiated. In some cases, K may be a counter parameter indicated by the gNB and / or pre-configured. For example, for the case of K=1, when the WTRU fails to receive the scheduled PDSCH, at least one event / condition may be satisfied. In another example, for the case of K=2 or K>2, when the WTRU determines that, for example, PDSCH reception fails twice (or K times) within a time window, at least one event / condition may be satisfied. In some cases, the parameters / values ​​of the time window may be configured / indicated from the gNB.

[0113] In another example, CLI sensing / measurement may be initiated when a WTRU (e.g., a victim WTRU) determines that one or more (e.g., K) DL data (e.g., PDSCH) receptions have failed, and / or when the WTRU sends one or more NACKs in response to at least one failure to receive 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 sends a NACK based on a determination that a PDSCH (e.g., scheduled PDSCH) has failed to be received. The NACK may be, for example, but not limited to, a negative ACK, a negative acknowledgement, 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 that two (or K) PDSCH receptions have failed, for example, within a time window, and / or when the WTRU sends two (or K) NACKs based on a determination that two (or K) scheduled PDSCHs have failed to be received, for example, at least twice (or K times) within a time window, for example. The parameters / values ​​of this time window may be configured / indicated from the gNB.

[0114] In another example, CLI sensing / measurement may be initiated when an explicit indication is received that the use of an SB should be avoided. For example, the explicit indication that the use of an SB should be avoided may include an indication for the WTRU to communicate through other SBs. In another example, CLI sensing / measurement may be initiated when an implicit indication is identified (and / or, for example, received and / or determined) that the use of an SB should be avoided. For example, the implicit indication may instruct the WTRU to communicate through other SBs. The implicit indication may be a predefined and / or preconfigured rule based on one or more of measuring, receiving, detecting DL signals, etc.

[0115] The WTRU may (e.g., explicitly or implicitly) receive a trigger to measure one or more types of interference (e.g., CLI) measurements. The WTRU may receive an indication and / or configuration of one or more of the following types of interference measurements: overlapping CLI; partially overlapping CLI; and non-overlapping CLI. Overlapping CLI may be, for example, but not limited to, intra-subband CLI. In one example, overlapping CLI may correspond to CLI on a set of RBs that overlap between DL reception (area) and UL transmission (area). For example, overlapping CLI may exist on a set of RBs that overlap between DL reception and UL transmission, for example, in one cell / TRP or in a set of cells / TRPs. For example, the set of cells / TRPs may be a set of cells / TRPs that are geographically dispersed.

[0116] Partially overlapping CLI may be CLI on a group of RBs that partially overlap between DL reception (area) and UL transmission (area). For example, partially overlapping CLI may be CLI on a group of RBs that partially overlap between DL reception and UL transmission, for example, in one cell / TRP or in a group of cells / TRPs. For example, this group of cells / TRPs may be a group of cells / TRPs that are geographically dispersed. Partially overlapping CLI may be CLI on a group of RBs, wherein a first group of RBs may partially overlap with a second group of RBs. For example, partially overlapping CLI may be CLI between (i.e., generated by) a first group of RBs for DL ​​reception (area) and a second group of RBs for UL transmission (area), for example, in one cell / TRP or in a group of cells / TRPs, wherein the first group of RBs may partially overlap with the second group of RBs. For example, this group of cells / TRPs may be located in a group of cells / TRPs that are geographically dispersed.

[0117] The non-overlapping CLI may be, for example, but not limited to, an inter-subband CLI. The non-overlapping CLI may be a CLI between (i.e., generated by) a first group of RBs for DL ​​reception (area) and a second group of RBs for UL transmission (area), wherein the first group of RBs does not overlap with the second group of RBs. For example, when the RB gap between the DL reception area and the UL transmission area is M (>=0), the first group of RBs does not overlap with the second group of RBs. The non-overlapping CLI may be a CLI between a first group of RBs for DL ​​reception and a second group of RBs for UL transmission in one cell / TRP or in a group of cells / TRPs. In one example, the group of cells / TRPs may be, for example, a group of cells / TRPs that are geographically dispersed. The non-overlapping CLI may be a case where the first group of RBs does not overlap with the second group of RBs (e.g., when there may be an RB gap M (>=0) between the DL reception area and the UL transmission area).

[0118] The WTRU may be configured, determined, and / or instructed to perform measurements of a CLI received signal strength indicator (RSSI) within a given time period. The given time period may include, for example, but not limited to, one or more time slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs). In one example, the CLI-RSSI may be measured within a given time / frequency resource. The CLI-RSSI may 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 may be used interchangeably to describe the embodiments disclosed herein.

[0119] 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 longer period of time (e.g., more than one time slot). The measurements may be reported via higher layer signaling (e.g., RRC and / or MAC). In another example, the second RSSI type may be based on measurements over a shorter period of time (e.g., one time slot, within a time slot, one or more OFDM symbols within a time 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 this set of time / frequency resources to measure L1-CLI-RSSI. In one example, the time / frequency resources used for L1-CLI-RSSI measurements may be referred to as CLI-RSSI measurement resources (CRMR).

[0120] In one or more cases, the CRMR may be a resource configured, determined, and / or defined using one or more of the following attributes: a set of muted REs in a downlink resource; a set of REs that are not scheduled or used by the WTRU to measure the CRMR; a set of REs located in 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.

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

[0122] In one example, a group of REs located in an RB may be configured and / or determined as a guard band or a guard RB. In one example, the guard band or the guard RB may be located between uplink resources and downlink resources. In one example, the WTRU may skip receiving and / or transmitting signals in the guard band.

[0123] The second group of DMRS REs within the second CDM group may, for example, be located within a scheduled downlink resource / RB, such as a PDSCH. The second group of DMRS REs within the second CDM group may correspond to the following situation: the WTRU may receive a DCI, scheduling a PDSCH, which may indicate a first group of DMRS REs corresponding to the first CDM group. The first CDM group may be used to receive a PDSCH. In one example, the WTRU may receive a DCI, scheduling a PDSCH, indicating a first group of DMRS REs corresponding to the first CDM group. The WTRU may receive a DCI, scheduling a PDSCH, indicating a first group of DMRS REs corresponding to the first CDM group, for example, based on an antenna port (e.g., DMRS antenna port) field indicated by the DCI. The WTRU may determine, based on receiving the DCI, that the second group of DMRS REs within the second CDM group may be used as a CRMR. In one or more cases, the second CDM group may be a group different from the first CDM group. In one or more cases, the WTRU may determine that the second group of DMRS REs within the second CDM group may be used as a CRMR, such as within a scheduled PDSCH.

[0124] In one or more cases, the CRMR may be configured commonly for a group of WTRUs (e.g., neighboring WTRUs). For example, the gNB may configure the CRMR for a group of WTRUs. A group of WTRUs may share one or more of: a group ID for receiving DCI; a zone ID; and / or WTRUs paired for sidelink unicast (and / or, for example, multicast) transmissions. The group ID for receiving DCI may be, for example, a group RNTI. The zone ID may be determined based on the geographic location of the WTRU (e.g., but not limited to GNSS). In one or more cases, the L1-CLI-RSSI measurement (e.g., including CRMR resources) may be considered a CSI reporting quantity and / or configured as part of the CSI reporting settings.

[0125] The WTRU may be configured, determined, and / or instructed to perform a variable CLI-RSSI. The variable CLI-RSSI may be, for example, based on a first CLI-RSSI measurement in a first time / frequency position and a second CLI-RSSI measurement in a second time / frequency position. One or more of the following may apply. In one or more cases, the variable CLI-RSSI (i.e., delta-CLI-RSSI) may be the difference between a first CLI-RSSI (i.e., CLI-RSSI1) and a second CLI-RSSI (i.e., CLI-RSSI2). For example, delta-CLI-RSSI=CLI-RSSI1–CL-RSSI2. In another example, delta-CLI-RSSI=CLI-RSSI2–CL-RSSI1. In one or more cases, the first CLI-RSSI may be measured from a CRMR resource located at the edge of a scheduled RB, and the second CLI-RSSI may be measured from a CRMR resource located at the center of the scheduled RB. This may reduce radio resource overhead, for example, because the first CLI-RSSI and the second CLI-RSSI may not be configured on separate REs of the scheduled RB. In one example, the first CLI-RSSI and the second CLI-RSSI may not be configured on separate REs of the scheduled RB based on a variable CLI-RSSI, which is determined according to CLI-RSSI1–CL-RSSI2 and may represent, capture and / or reflect the amount of CLI. The variable CLI-RSSI may represent, capture and / or reflect the amount of CLI because CLI-RSSI1 may primarily represent and / or include general downlink intra-cell / inter-cell interference, and because CLI-RSSI2 may represent and / or include (e.g., in addition to general DL interference) leakage interference (e.g., inter-subband CLI) of CLI that is higher than CLI-RSSI1. In one example, when an UL transmission from an interfering WTRU (e.g., an UL transmission that causes CLI) occurs on a neighboring RB (e.g., a nearby RB) of a scheduled RB, CLI-RSSI1 may primarily represent and / or include general downlink intra-cell / inter-cell interference, and CLI-RSSI2 may represent and / or include leakage interference of CLI that is higher than CLI-RSSI1. In one or more cases, the WTRU may be configured with 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, when the measured delta-CLI-RSSI is greater than a threshold, the WTRU may determine to report CLI measurement related information. For example, a CLI report may be triggered based on the delta-CLI-RSSI measurement being greater than a threshold. In some cases, the threshold may be predetermined and / or configured.

[0126] The WTRU may be configured or determined to measure CLI-RSSI at each subband level. For example, the subbands may be configured and / or predetermined. In one or more cases, the WTRU may perform CLI-RSSI measurements in each subband. One or more of the following may apply. In one or more cases, the subband size may be determined based on the number of scheduled RBs (e.g., for PDSCH). For example, when the scheduled RBs are greater than X (e.g., 12), a first subband size (e.g., 4) may be used, and when the scheduled RBs are less than or equal to X, a second subband size (e.g., 2) may be used. In another example, when the scheduled RBs are greater than X, a first subband size may be used. In another example, when the scheduled RBs are less than or equal to X, a second subband size may be used. In one or more cases, the WTRU may report CLI-RSSI measurements for one, multiple, or all subbands. In one or more cases, the WTRU may report a subset of CLI-RSSI. The subset may be determined based on one or more conditions, such as, but not limited to, a CLI-RSSI value above a threshold, a subband location (eg, an edge of a scheduled RB), a subband index, and the like.

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

[0128] The WTRU may be instructed to perform CLI-RSSI measurements at a specific frequency location within a scheduled RB. In one or more cases, the WTRU may be instructed to perform CLI-RSSI measurements at a specific frequency location within a non-scheduled RB. In one or more cases, the WTRU may be instructed to perform CLI-RSSI measurements at a specific frequency location within a scheduled RB and a non-scheduled RB. The specific frequency location may correspond to one or more of a subband, an RB, and an RE. In one or more cases, the indication may be within a DCI, which may trigger a CLI-RSSI measurement. The CLI-RSSI measurement may be, for example, a non-periodic CLI-RSSI measurement. In one or more cases, a specific frequency location may be indicated based on a CRMR resource frequency location. For example, one or more CRMR resources may be configured, and / or each CRMR resource may be positioned at a specific frequency location based on the configuration. The WTRU may be instructed to perform measurements on the CRMR resources indicated in the DCI.

[0129] The WTRU may be configured, determined, or instructed to report channel and / or interference measurements. The WTRU may report the strength and / or power of reference signals measured in the configured resources (e.g., CLI-RSSI, SRS-RSRP, L1-CLI-RSSI). In one or more cases, the WTRU may report the strength and / or power level of the measured reference signals based on one or more of the configured and / or determined thresholds. In one example, if the measured power and / or strength is higher than the configured and / or determined threshold, the WTRU may report that interference may exist. In another example, if the difference between the measurements in one or more of the resources is higher than the configured and / or determined threshold, the WTRU may report that partial and / or subband edge interference (e.g., CLI) may exist. Alternatively, for example, in the case where the measured interference power and / or strength is lower than the configured and / or determined threshold, the WTRU may report and / or request one or more of the subbands to be reliably switched to.

[0130] The WTRU may indicate (e.g., by sending, transmitting, reporting, etc.) at least one type of (e.g., CLI-related) information content introduced throughout the present disclosure. For example, the information content may correspond to one or more of an interference level, a CLI level, a subband-level CLI, a measurement result / metric based on a CRMR measurement, a delta-CLI-RSSI, etc. The WTRU may indicate at least one type of information content via, for example, a negative acknowledgement (NACK) transmission. For example, in addition to the NACK transmission, the WTRU may also indicate at least one type of information content associated with the NACK transmission together with the NACK transmission and / or based on a HARQ-ACK codebook including one or more (e.g., additional) bits indicating at least one type of information content. In one or more cases, the NACK transmission may be performed in response to a scheduled PDSCH reception failure. In one example, the WTRU may transmit a marker signal together with the NACK transmission. For example, the WTRU may transmit a marker signal together with the NACK transmission in response to a scheduled PDSCH reception failure. A marker signal sent along with the NACK may indicate, for example, that the power and / or strength of the interference has been measured, and that the measured value of the power and / or strength is above a configured and / or determined threshold. For example, an L1-CLI-RSSI greater than or equal to a corresponding threshold may indicate that interference may be present. In another example, the WTRU may transmit a marker signal along with the NACK, for example in response to a scheduled PDSCH reception failure, to indicate that the NACK may be caused by interference (e.g., CLI). For example, the WTRU may transmit a marker along with the NACK to request a scheduling request (SR) for channel and / or interference measurements (e.g., L1-CLI-RSSI measurements). In one or more cases, the WTRU may be configured to measure and / or sense interference power / strength in one or more reference subbands (e.g., measuring CLI via L1-CLI-RSSI).

[0131] The WTRU may construct a list. The list may include, for example, but not limited to, interference measurement results in one or more reference subbands in the reference subbands. In some cases, the list may be sorted 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). For example, when the WTRU determines and / or detects interference in the active SB (e.g., L1-CLI-RSSI>threshold), the WTRU may transmit a request including one or more subbands in the subbands to which the WTRU prefers to switch (e.g., communicate with the gNB). The WTRU may select, determine and / or identify one or more preferred subbands in the preferred subbands. The WTRU may select, determine and / or identify one or more preferred subbands in the preferred subbands, for example based on the measured interference power / strength. The measured interference power / strength may be the smallest (or, for example, less than the threshold) in the determined list (e.g., Ref_SB_ordered). In this way, the WTRU may report and / or request a handover to, for example, a sub-band, BWP and / or component carrier (CC) where data transmission and / or reception may be reliably accomplished.

[0132] In one or more other cases, such as after the WTRU has measured and / or sensed interference in an active SB, the WTRU may construct a list of interference measurement results in one or more of the reference SBs. In this way, the WTRU may report and / or request a switch to a subband, BWP, and / or component carrier (CC) in which data transmission and reception can be reliably completed (e.g., measured L1-CLI-RSSI < threshold). In one or more cases, the WTRU may determine that the interference power and / or strength (e.g., L1-CLI_RSSI) measured in one or more of the reference SBs is below a configured and / or determined threshold. In one or more cases, the WTRU may determine that the interference power and / or strength (e.g., L1-CLI_RSSI) measured in all reference SBs is not below a configured and / or determined threshold. In this way, the WTRU may transmit a report and / or request to measure one or more other BWPs, a set of RBs, other deactivated CCs, etc. The WTRU may transmit a measurement report and / or request, for example, to perform a preferred BWP / CC / SB report. In some cases, the BWP in the measurement report and / or request may be, for example, a deactivated BWP.

[0133] Authorized resources, subbands, RBs, and scheduled RBs may be used interchangeably and are consistent with the embodiments disclosed herein. In one or more cases, the WTRU may have multiple authorized configurations. The WTRU may determine, identify, and / or be configured with one or more authorized resources. In one or more cases, the WTRU may sense, measure, and / or determine interference signals in one or more of the authorized resources. The WTRU may dynamically choose to use or avoid using one or more authorized resources. In this way, the WTRU may use or avoid using one or more of the authorized resources, and / or switch between the authorized resources accordingly. For example, the WTRU may use or avoid using one or more of the authorized resources, and / or switch between the authorized resources accordingly based on the level of the interference signal.

[0134] In one or more cases, the determination of granted resources to use and / or switch to may be performed to perform one or more of the following operations: reception of channels and signals, transmission of channels and signals, etc. For example, the WTRU may determine granted resources to use and / or switch to receive one or more channels and signals, such as, but not limited to, one or more of PDCCH, PDSCH, CSI-RS, SSB (e.g., including PBCH), PRS, DM-RS, etc. In another example, the WTRU may determine granted resources to use and / or switch to transmit one or more channels and signals, such as, but not limited to, one or more of PRACH, PUCCH, PUSCH, SRS, DM-RS, etc.

[0135] The WTRU may be configured with an operating mode that dynamically determines authorized resources and / or semi-statically determines authorized resources. For example, the WTRU may use one or more operating modes (e.g., dynamic and / or semi-static determination) to determine to use, avoid use, and / or switch to authorized resources. The number of configured authorized resources (e.g., a maximum number) may be determined based on the operating mode determined, used, and / or configured. In one or more cases, one or both of the following may apply: the operating mode may be determined based on the number of authorized resources for dynamic operation; the operating mode may be determined based on WTRU capabilities and / or gNB configuration, such as based on WTRU capability reports. In one example, the WTRU may determine the operating mode based on the number of authorized resources configured and / or indicated for dynamic operation. For example, the gNB may indicate and / or configure one or more authorized resources. In some cases, the WTRU may determine to use a semi-static determination mode. In other cases, the WTRU may determine to use a dynamic determination mode. For the case where the gNB indicates and / or configures one authorized resource, the WTRU may determine to use a semi-static determination mode. For the case where the gNB indicates and / or configures more than one authorized resource, the WTRU may determine to use a dynamic determination mode. In another example, the operating mode may be determined based on WTRU capabilities and / or gNB configuration, for example, based on WTRU capability reports. In one or more cases, the WTRU may indicate one or more authorized resources as WTRU capabilities. In one or more cases, the WTRU may determine to use a semi-static determination mode and / or a dynamic determination mode. For the case where the WTRU indicates one authorized resource as a WTRU capability, the WTRU may determine to use a semi-static determination mode. For the case where the WTRU indicates more than one authorized resource as a WTRU capability, the WTRU may determine to use a dynamic determination mode. In one or more cases, the gNB configuration may be performed based on the reported WTRU capabilities.

[0136] In one or more cases, the WTRU may request a preferred operation mode for determining granted resources. The WTRU may be capable of supporting one or both operation modes. The WTRU may indicate one or more preferred operation modes to the gNB. For cases where the WTRU is capable of supporting both operation modes, the WTRU may indicate the preferred operation mode to the gNB. In one or more cases, the WTRU may determine the preferred operation mode based on one or more of: interference strength; channel quality; and / or traffic.

[0137] The WTRU may determine one or more preferred operating modes based on the 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. Therefore, if the interference intensity and / or quality measured in one or more of the authorized resources is higher than the corresponding threshold, the WTRU may determine to use a dynamically determined mode. In one example, the WTRU may dynamically report, request authorized resources and / or switch between authorized resources based on the interference intensity.

[0138] The WTRU may determine a preferred mode of operation based on channel quality. For example, the WTRU may measure the channel quality of one or more of the granted resources. The WTRU may measure channel quality, such as but not limited to CQI, RSRP, SINR, path loss, blocking probability, etc. In one example, for a situation where the channel quality measured in one or more of the granted resources is below a corresponding threshold, the WTRU may determine to use a dynamically determined mode. In this way, the WTRU may dynamically report, request granted resources, and / or switch between granted resources based on channel quality.

[0139] The WTRU may determine a preferred mode of operation based on traffic volume (e.g., the amount of data to be received and / or sent). The WTRU may determine the traffic volume (e.g., the amount of data to be received and / or sent). In one example, the WTRU may determine to use a dynamically determined mode for situations where the traffic volume is above a corresponding threshold. In this way, the WTRU may dynamically report, request authorized resources, and / or switch between authorized resources based on the traffic volume.

[0140] In one or more cases, in a first mode of operation (e.g., semi-static determination), the WTRU may use the indicated and / or configured granted resources to send and / or receive channels and / or signals and sense, process, and measure one or more channels and / or signals. In one or more cases, in a first mode of operation (e.g., semi-static determination), the WTRU may use the indicated and / or configured granted resources to send and / or receive channels and / or signals. In one or more cases, in a first mode of operation (e.g., semi-static determination), the WTRU may use the indicated and / or configured granted resources to sense, process, and / or measure one or more channels and / or signals. In one or more cases, in a second mode of operation (e.g., dynamic determination), the WTRU may determine the granted resources from one or more of the granted resources based on one or more of the following: gNB indication, WTRU request / report, or a combination of gNB indication and WTRU request / report.

[0141] In one or more cases, in the second mode of operation (e.g., dynamically determined), the WTRU may determine the granted resource from one or more of the granted resources based on, for example, a gNB indication. In one example, the WTRU may receive an indication of the granted resource based on one or more of: an indication of a configured grant index; an indication of frequency and / or time resources; an indication of TCI status, CRI, and / or SRI; a PDCCH transmission in a dedicated CORESET; and / or a gNB indication.

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

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

[0144] In one or more cases, the WTRU may receive an indication of a granted resource based on an indication of a TCI state, CRI, and / or SRI. For example, the WTRU may be configured with 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, for example, be associated with a first granted resource. The second TCI state, CRI, and / or SRI may, for example, be associated with a second granted resource. The WTRU may receive an indication of a TCI state, CRI, and / or SRI (e.g., a first TCI state, CRI, and / or SRI; or a second TCI state, CRI, and / or SRI) via one or more of, for example, a DCI, a MAC CE, and an RRC. For a case where the WTRU receives an indication of a first TCI state, CRI, and / or SRI, the WTRU may determine a first granted resource. For a case where the WTRU receives an indication of a second TCI state, CRI, and / or SRI, the WTRU may determine a second granted resource.

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

[0146] In one or more cases, the WTRU may determine the granted resource from one or more of the granted resources based on the gNB indication. The WTRU may determine the granted resource based on one or more of the following: priority, modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks, number of repetitions and / or repetition scheme (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.

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

[0148] In one or more cases, one or more of the authorized resources may be used, avoided, and / or blocked from use based on one or more of the following: a report from a potential victim WTRU and / or a report from an aggressor WTRU. In one example, the WTRU may determine to use, avoid, and / or block from use one or more of the authorized resources based on the report from the potential victim WTRU. 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 authorized resources. One or more of the victim WTRUs may determine that the measured amount is below and / or above a corresponding threshold, respectively. One or more of the potential victim WTRUs may report and / or transmit a request to the WTRU to avoid using the authorized resources whose channel quality is below a threshold and / or whose interference level is above a corresponding threshold. The WTRU may determine to use, avoid, and / or block from use one or more of the authorized resources based on the report from the aggressor WTRU. In one example, one or more of the disturber WTRUs may sense and / or measure the quality of a channel or interference (e.g., CLI) in one or more of the granted resources. The one or more disturber WTRUs may compare the measurements to corresponding thresholds. One or more potential disturber WTRUs may determine that sending and / or receiving a channel and / or signal on the sensed granted resources may cause interference (e.g., CLI) to a potential victim WTRU. Therefore, one or more of the potential disturber WTRUs may report and / or transmit a request to the WTRU to avoid using the corresponding granted resources.

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

[0150] The WTRU may determine to use and / or avoid using one or more of the authorized resources based on the WTRU sensing and / or measuring interference in one or more of the authorized resources. For example, the WTRU may use a non-zero power CSI-RS (e.g., NZP-CSI-RS) and / or a 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 conjunction, the WTRU may measure CLI based on L1-CLI-RSSI. For a situation where the interference (e.g., CLI) measured in one or more of the authorized resources is higher than a corresponding threshold, the WTRU may request to use and / or switch to another set of one or more authorized resources. The WTRU may request to use and / or switch to another set of one or more authorized resources in which the interference (e.g., CLI) measured is lower than a corresponding threshold.

[0151] The WTRU may determine to use and / or avoid using one or more of the authorized resources based on the potential disturber WTRU sensing and / or measuring interference (e.g., CLI). The potential disturber WTRU may sense and / or measure interference in one or more of the authorized resources. For example, the potential disturber 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 measurement may be based on periodic, semi-persistent and / or non-periodic sensing and / or measurement. In another example, alternatively or in conjunction, the potential disturber WTRU may be configured to receive SRS signals and / or measure SRS-RSRP from one or more of the potential disturbed WTRUs. In one example, for a case where the measured SRS-RSRP is higher than a corresponding threshold, the potential disturber WTRU may request to prevent the use and / or avoid the use of the corresponding authorized resources. In another example, the potential victim WTRU may send 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.

[0152] The WTRU may determine to use and / or avoid using one or more of the authorized resources based on a trigger received by the potential interferer WTRU based on one or more events sensing and / or measuring the channel and / or interference quality in one or more of the authorized resources. In one or more cases, the event-based trigger of sensing and / or measuring may be based on, for example, receiving one or more NACK signals from the potential victim WTRU at the gNB. In one example, the potential interferer WTRU may receive an indication of one or more NACK signals from its serving gNB / TRP, where, for example, the serving gNB / TRP of the potential interferer WTRU may receive the indication from a second serving gNB / TRP of the potential victim WTRU. The serving gNB / TRP of the potential interferer WTRU may receive the indication from the 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 a situation where the number of NACK signals received from one or more of the potential victim WTRUs within a time period (e.g., based on a timer) reaches a threshold (e.g., a maximum number of NACK signals), the gNB may trigger event-based channel sensing and / or measurement for one or more potential aggressor WTRUs. In one or more situations, the potential aggressor WTRU may be triggered to measure reference signals based on a non-periodic resource configuration. The reference signals may include, for example, but not limited to, ZP-CSI-RS, NZP-CSI-RS, CLI-RSSI, L1-CLI-RSSI, and / or SRS.

[0153] The WTRU may transmit a request to the gNB to use and / or switch to granted resources based on one or more of: explicit signaling; associated uplink resources; channel and / or interference reports; and / or receipt of an acknowledgment of the WTRU request from the gNB.

[0154] The WTRU may transmit a request to the gNB to use and / or switch to a granted resource based on explicit signaling. The WTRU may transmit the request to the gNB based on explicit signaling, for example, via one or more of PUCCH, PUSCH, MAC CE, and PRACH. In one example, the WTRU may be configured with one or more granted resources. The WTRU may request a granted resource from the one or more granted resources based on the configuration. In one example, the indication corresponding to the request may be one or more of: an indication of a granted index; and / or an indication of a subband and / or frequency resource.

[0155] The WTRU may transmit a request to the gNB to use and / or switch to a granted resource based on the associated uplink resources. In one example, the WTRU may be configured with a first uplink resource associated with a first granted resource. In another example, the WTRU may be configured with a second uplink resource associated with a second granted resource. In another example, the WTRU may be configured with a first uplink resource associated with the first granted resource and a second uplink resource associated with the second granted resource. For the case where the WTRU sends an uplink signal via the first uplink, the WTRU and the gNB may determine the first granted resource. For the case where the WTRU sends an uplink signal via the second uplink resource, the WTRU and / or the gNB may determine the second granted resource. The uplink signal may be, for example, but not limited to, one or more of the following: a scheduling request, a HARQ ACK / NACK, and / or a PRACH.

[0156] The WTRU may transmit a request to the gNB to use and / or switch to authorized resources based on channel and / or interference reports. In one example, the WTRU may be configured with a first configuration associated with a first authorized resource. In another example, the WTRU may be configured with 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 a second authorized resource. 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 the authorized resources.

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

[0158] 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 a 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 a second configuration.

[0159] The WTRU and the gNB may determine the granted resources based on the first channel and / or interference report and the second channel and / or interference report. For example, for the case where the first channel quality of the first CSI report is lower than or equal to the second channel quality of the second CSI report, the WTRU and the gNB may determine the second granted resources. In another example, for the case where the first channel quality is higher than the second quality, the WTRU and the gNB may determine the first granted 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, for the case where the first interference quality of the first interference report is higher than or equal to the second interference quality of the second interference report, the WTRU and the gNB may determine the second granted resources. In another example, for the case where the first interference quality is lower than the second quality, the WTRU and the gNB may determine the first granted resources. The first interference quality and the second interference quality may be, for example, but not limited to, one or more of CLI-RSSI, SRS-RSRP, L1-CLI-RSSI, etc.

[0160] The first configuration and the second configuration may be one or more of the following: CSI report configuration, CSI-RS resource, CSI-RS resource set, BWP and / or subband for CSI reporting. In one or more cases, the first configuration and the second configuration may be one or more of the following: SRS report configuration, SRS resource, SRS resource set, BWP and / or subband for SRS reporting. In one or more cases, the first configuration and the second configuration may be one or more of the following: CLI report configuration, CLI resource, CLI resource set, BWP and / or subband for CLI reporting. In one or more cases, the first configuration and the second configuration may be one or more of the following: CSI report configuration, CSI-RS resource, CSI-RS resource set, BWP and / or subband for CSI reporting; SRS report configuration, SRS resource, SRS resource set, BWP and / or subband for SRS reporting; CLI report configuration, CLI resource, CLI resource set, BWP and / or subband for CLI reporting.

[0161] The WTRU may receive an acknowledgment of the WTRU request from the gNB. In one example, the WTRU may receive an acknowledgment PDCCH. For example, the WTRU may receive an acknowledgment PDCCH via a dedicated CORESET and / or MAC CE for gNB acknowledgment. In one or more cases, there may be a time gap between the WTRU and the PDCCH reception. The time gap may be, for example, X symbols / timeslot / milliseconds. For cases where there is a time gap between the WTRU and the PDCCH reception (e.g., the first symbol or the last symbol of the PDCCH reception), the WTRU may use, avoid use, and / or switch to the requested granted resources for WTRU operation.

[0162] In a second mode of operation (e.g., dynamically determined), the WTRU may determine the granted resource from one or more of the granted resources based on a combination of a gNB indication and a WTRU report / request. In one or more cases, a combination of a gNB indication and a 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 granted resources from the gNB; the WTRU may request the one or more granted resources from the gNB. For example, the WTRU may receive an indication of one or more granted resources via, for example, an indication of a set of granted resources from the gNB. The WTRU may request the granted resource from the one or more granted resources based on the indication. For example, the WTRU may request the granted resource from the one or more granted resources via, for example, one or more of explicit signaling, associated uplink resources, channel and / or interference reports, etc. In another example, the WTRU may request the one or more granted resources from the gNB via, for example, one or more of explicit signaling, associated uplink resources, channel and / or interference reports, etc. The WTRU may receive an indication of the granted resource from the one or more granted resources based on the indication.

[0163] In one or more cases, the WTRU may be configured with a counter and / or timer for switching to a granted resource. The WTRU may use, receive, and / or be configured with a counter and / or timer for switching to one or more of the granted resources. In one example, the WTRU may be configured to use one or more of the granted resources and be configured with a counter and / or timer. In another example, the WTRU may be configured to avoid using one or more of the granted resources and be configured with a counter and / or timer.

[0164] The WTRU may switch from a first authorized resource to a second authorized resource based on a determination. For example, the WTRU may switch from a first authorized resource to a second authorized resource based on a determination corresponding to a gNB indication and / or a WTRU request. For example, after the determination, the WTRU may apply a counter. For example, when the WTRU sends and / or receives one or more channels and / or signals, the WTRU may increase the value of the counter by a number (e.g., increase the value by one). For a case where the value of the counter is less than or equal to a threshold, the WTRU may use the second authorized resource. The threshold may be, for example, a maximum value of the counter. For a case where the value of the counter is greater than the threshold, the WTRU may switch from the second authorized resource to the first authorized resource. In some cases, the initial value of the counter may be zero. In some cases, when the WTRU switches the authorized resource, the counter may be initiated and / or reset. In some cases, the counter and the threshold may be predefined. In some cases, the counter and the threshold may be indicated via, for example, a MAC CE and / or a DCI. In some cases, the counter and the threshold may be configured by RRC. In some cases, the counter and the threshold may be predefined, indicated, and / or configured by RRC.

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

[0166] The 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. The reception of channels and signals may correspond to, for example, the reception of one or more of PDCCH, PDSCH, CSI-RS, SSB (including PBCH), PRS, DM-RS, etc. The transmission of channels and signals may correspond to, for example, the transmission of one or more of PRACH, PUCCH, PUSCH, SRS, DM-RS, etc.

[0167] The WTRU may be configured to prevent band edge CLI. A WTRU (e.g., a potential interferer WTRU) may determine and / or receive an indication that the WTRU is causing interference. For example, the WTRU may determine and / or receive an indication based on a gNB indication and / or WTRU sensing / measurement. The WTRU may determine and / or receive an indication that the WTRU is causing interference (e.g., CLI) (e.g., band edge CLI) on one or more victim WTRUs in one or more of the configured subbands. In this way, the WTRU may determine to take preventive measures to reduce the interference. In one or more cases, the WTRU may determine to take preventive measures based on, for example, a gNB indication and / or a WTRU request based on sensing and / or measurement.

[0168] The WTRU may be configured or request to switch from a first granted resource to a second granted resource. In one example, the second granted resource may include a larger data allocation. Therefore, interference (e.g., band edge CLI) may be reduced due to the inclusion of a larger BWP / subband in the second granted resource.

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

[0170] The WTRU may be configured with a group common indication to manage the granted resources. For example, the WTRU may receive a group common indication of potential interference on one or more granted resources, RB sets and / or subbands. In one example, a group common indication may be sent to a group of WTRUs. This group of WTRUs may include at least a first group of WTRUs (e.g., potential interfered party WTRUs) and / or a second group of WTRUs (e.g., potential interferer WTRUs). In one or more cases, the WTRU may measure the configured channel and / or interference measurements and / or report measurements in the configured resources. For example, upon receiving a group common indication (e.g., a group common DCI), the WTRU may measure the configured channel and / or interference measurements and / or report measurements in the configured resources. In some cases, the WTRU (e.g., a potential interfered party WTRU) may determine to avoid using the granted resources and / or subbands. For example, the WTRU may determine to avoid using the granted resources and / or subbands based on the received indication and / or based on the performed measurements. In some cases, the WTRU may determine to switch to other granted resources and / or subbands. In some cases, a WTRU (e.g., a potential interferer WTRU) may determine to avoid using authorized resources and / or subbands. For example, the WTRU may determine to avoid using authorized resources and / or subbands based on received indications and / or based on performed measurements. In some cases, the WTRU may determine to use preventive measures. For example, the WTRU may determine to use preventive measures by switching to other authorized resources and / or subbands and / or reducing power techniques. In one or more cases, the WTRU may receive WTRU-specific indications and / or group-common indications when the WTRU's role changes. For example, the WTRU's role change may be, for example, a victim WTRU becomes a interferer WTRU, or vice versa. In some cases, the WTRU may use channel and / or interference measurement results to avoid causing interference and / or being affected by interference (e.g., from a potential interferer WTRU).

[0171] The WTRU may be configured for CLI sensing and / or measurement based on directional SRS-RSRP. In one example, the WTRU may be configured and / or receive signaling indicating one or more TCI states for sensing and / or measuring interference and / or for SRS reception and measurement. Interference may include, for example, but 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 the corresponding reference signal. In one example, the WTRU may receive a TCI state and / or an SRS resource indicator (SRI) to measure the corresponding SRS signal (e.g., SRS-RSRP). In one or more cases, one or more of the following may apply. For example, a WTRU (e.g., a potential interfered party WTRU) may determine and / or be configured to use a spatial filter. The spatial filter may be the same spatial filter used to receive the reference signal set indicated by the TCI state for the corresponding CORESET, for example, the corresponding CORESET used by the WTRU to monitor the PDCCH. In another case, the WTRU (e.g., a potential interferer WTRU) may determine and / or be configured to use the spatial filter to measure the potential impact and / or interference that the spatial filter may cause. For example, the WTRU may determine and / or be configured to use the spatial filter to measure the potential impact and / or interference that the spatial filter may cause, for example, in the direction indicated by the configured TCI state. In one or more cases, the WTRU may report directional channel and / or interference sensing and / or measurements to the gNB.

Claims

1. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising: A processor, the processor being configured to: receiving configuration information indicating a plurality of subbands for cross-link interference (CLI) measurement and corresponding resources for performing the CLI measurement on each of the plurality of subbands; receiving downlink control information (DCI) indicating resources associated with a first reference subband; performing CLI measurements on the first reference subband using one or more resources used to perform CLI measurements on the first subband; Based on determining that the CLI measurement of the first subband is greater than a threshold, performing CLI measurement on at least one other subband of the plurality of subbands using the corresponding resource for performing CLI measurement on the at least one other subband; and An indication is transmitted that the CLI measure for the subband is greater than the threshold.

2. The WTRU of claim 1 , wherein the processor is further configured to transmit information indicating a second sub-band.

3. The WTRU of claim 2, wherein the indicated second sub-band is determined to have a lowest measured CLI among the plurality of sub-bands.

4. The WTRU of claim 1 , wherein the processor is further configured to perform the CLI measurement on the first subband based on a number of downlink data reception failures of the first subband exceeding a first threshold.

5. The WTRU of claim 1 , wherein the processor is further configured to perform the CLI measurement on the first subband based on a number of hybrid automatic repeat request negative acknowledgements (HARQ NACKs) transmitted by the WTRU for transmissions in the first subband exceeding a second threshold.

6. The WTRU of claim 1 , wherein the processor is further configured to perform the CLI measurement on the first subband based on an explicit indication from a network.

7. The WTRU of claim 1, wherein the corresponding resources for performing CLI measurements on each of the multiple subbands 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).

8. The WTRU of claim 1, wherein the received DCI includes a downlink (DL) assignment indicating that the first reference subband schedules a physical downlink shared channel (PDSCH).

9. The WTRU of claim 1, wherein the processor is further configured to perform the CLI measurement on 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 level CLI measurement, or a variable CLI measurement.

10. The WTRU of claim 9, wherein the CLI measurement comprises overlapping CLI, partially overlapping CLI, or non-overlapping sub-band CLI.

11. A method comprising: receiving configuration information indicating a plurality of subbands for cross-link interference (CLI) measurement and corresponding resources for performing the CLI measurement on each of the plurality of subbands; receiving downlink control information (DCI) indicating resources associated with a first reference subband; performing CLI measurements on the first reference subband using one or more resources used to perform CLI measurements on the first subband; Based on determining that the CLI measurement of the first subband is greater than a threshold, performing CLI measurement on at least one other subband of the plurality of subbands using the corresponding resource for performing CLI measurement on the at least one other subband; and An indication is transmitted that the CLI measure for the subband is greater than the threshold.

12. The method according to claim 11, further comprising: Information indicating the second subband is transmitted.

13. The method of claim 12, wherein the indicated second sub-band is determined to have a lowest measured CLI among the plurality of sub-bands.

14. The method according to claim 11, further comprising: Based on the number of downlink data reception failures of the first subband exceeding a first threshold, the CLI measurement is performed on the first subband.

15. The method according to claim 11, further comprising: The CLI measurement is performed on the first subband based on a number of hybrid automatic repeat request negative acknowledgements (HARQ NACKs) transmitted by the WTRU for transmissions in the first subband exceeding a second threshold.

16. The method according to claim 11, further comprising: Based on an explicit indication from a network, the CLI measurement is performed on the first subband.

17. The method of claim 11, wherein the corresponding resources for performing CLI measurements on each of the multiple subbands 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).

18. The method of claim 11, wherein the received DCI comprises a downlink (DL) assignment indicating that the first reference subband schedules a physical downlink shared channel (PDSCH).

19. The method according to claim 11, further comprising: The CLI measurement is performed on 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 level CLI measurement, or a variable CLI measurement.

20. The method of claim 19, wherein the CLI measurement comprises overlapping CLI, partially overlapping CLI, or non-overlapping sub-band CLI.

Images