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

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the priority of U.S. Provisional Patent Application No. 63 / 334,991, filed on April 26, 2022, the entire content of which is incorporated herein by reference.

Background Art

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

Summary of the Invention

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

[0004] In one or more embodiments, the Disclosure relates to methods and apparatus implemented to mitigate interference in NR duplexing. For example, a victim WTRU receives a measurement and reporting configuration for one or more reference subbands. The victim WTRU, in one example, receives a trigger to sense / measure interference. The victim WTRU, in one example, measures a Cross Link Interference-Received Signal Strength Indicator (CLI-RSSI) or a Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP) across the entire configured frequency / subband resource. The victim WTRU, in one example, reports the CLI-RSSI or SRS-RSRP measurement via L1 signaling. The victim WTRU, in one example, requests to switch to another reference subband when the WTRU has not sensed interference.

[0005] In one or more embodiments, the Aggressor WTRU determines, for example, one or more reference subbands that the WTRU may switch to when a CLI is triggered against a victim WTRU in an active SB. The Aggressor WTRU performs event-based CLI / channel occupancy sensing in an active SB, for example.

[0006] In one or more embodiments, 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 directional CLI / channel sensing.

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

[0008] The processor may be configured to send information indicating a second subband. The indicated second subband is determined to have the lowest measured CLI among multiple subbands.

[0009] The processor may be configured to perform a CLI measurement for a first subband based on any combination of factors, such as the number of downlink data reception failures for the first subband exceeding a first threshold, the number of Hybrid Automatic Repeat Request Negative Acknowledgements (HARQ NACKs) sent by the WTRU for transmission in the first subband exceeding a second threshold, and / or explicit instructions received from the network.

[0010] Each resource for performing CLI measurements for each of the multiple subbands may include one or more of the following: zero-power channel state information reference signal (ZP-CSI-RS), non-zero-power channel state information reference signal (NZP-CSI-RS), or sounding reference signal (SRS).

[0011] DCI may include downlink (DL) allocations that designate a first reference subband for scheduling physical downlink shared channels (PDSCHs).

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

[0013] A more detailed understanding can be obtained from the following explanation, which is given as an example in conjunction with the attached drawings, where similar reference numbers in the drawings indicate similar elements. [Figure 1A] This is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented. [Figure 1B]Figure 1A is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used in the communication system illustrated in Figure 1A. [Figure 1C] Figure 1A is a system diagram illustrating exemplary radio access networks (RANs) and exemplary core networks (CNs) that may be used within the communication system shown. [Figure 1D] This is a system diagram illustrating further exemplary RANs and further exemplary CNs that may be used within the communication system shown in Figure 1A. [Figure 2] This diagram illustrates an example of crosslink interference (CLI) directional sensing. [Figure 3] This diagram illustrates an example of a Cross Division Duplex (XDD) scheme. [Figure 4] This diagram illustrates an example of cross-link interference (CLI) between gNBs and between WTRUs. [Modes for carrying out the invention]

[0014] Figure 1A illustrates an exemplary 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, message transmission, and broadcast to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique-word OFDM (UW-OFDM), resource block filtering OFDM, and filter bank multicarrier (FBMC).

[0015] As shown in Figure 1A, the communication system 100 may include radio transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments intend 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 radio environment. For example, WTRU102a, 102b, 102c, 102d, any of which may be referred to as “station” and / or “STA”, may be configured to transmit and / or receive radio signals and may include user equipment (UE), mobile stations, fixed subscriber units or mobile subscriber units, subscriber-based units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, radio sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other radio devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating on commercial radio networks and / or industrial radio networks, etc. WTRU102a, 102b, 102c, and 102d can all be referred to as UE for compatibility purposes.

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

[0017] Base station 114a may be part of 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), and relay nodes. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectra, unlicensed spectra, or combinations of licensed and unlicensed spectra. Cells may provide coverage of radio services to a particular geographic area that may be relatively fixed or change over time. Cells may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0018] Base stations 114a and 114b may communicate with one or more WTRUs 102a, 102b, 102c, and 102d via an air interface 116, which may be any suitable radio 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).

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

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

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

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

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

[0024] The base station 114b in Figure 1A may be, for example, a wireless router, home node B, home e-node B, or access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as offices, homes, vehicles, campuses, industrial facilities, aerial corridors (for use by drones, for example), roads, etc. In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base stations 114b and WTRUs 102c, 102d may establish picocells or femtocells using cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in Figure 1A, base station 114b may have a direct connection to the internet 110. Therefore, base station 114b may not need to access the internet 110 via CN 106 / 115.

[0025] RAN104 / 113 can communicate with CN106 / 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 WTRU102a, 102b, 102c, and 102d. The data may have various quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. CN106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN104 / 113 and / or CN106 / 115 may communicate directly or indirectly with other RANs employing the same or different RATs as RAN104 / 113. For example, in addition to being connected to RAN104 / 113 which can utilize NR radio technology, CN106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0026] CN106 / 115 may also function as a gateway for WTRU102a, 102b, 102c, 102d to access PSTN108, the Internet 110, and / or other networks 112. PSTN108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, which use common communication protocols such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the Internet protocol (IP) of the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN104 / 113 or a different RAT.

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

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

[0029] The processor 118 could be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple 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 coding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120 which can be coupled to a transmit / receive element 122. Figure 1B depicts the processor 118 and transceiver 120 as separate components, but it will be understood that the processor 118 and transceiver 120 can be integrated together in an electronic package or chip.

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

[0031] Although the transmit / receive element 122 is depicted as a single element in Figure 1B, 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 sending and receiving radio signals via the air interface 116.

[0032] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multimode capabilities. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0033] The processor 118 of the WTRU102 may be coupled to 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) and may receive user input from these. 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 any suitable type of memory, such as non-removable memory 130 and / or removable memory 132, and store data in such memory. The non-removable memory 130 may include random-access memory (RAM), 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 memory not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data in that memory.

[0034] The processor 118 may be configured to receive power from the power supply 134 and distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for supplying power to the WTRU 102. For example, the power supply 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.

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

[0036] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, compass sensor, proximity sensor, temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity sensor.

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

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

[0039] RAN104 may include e-nodes B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of e-nodes B while maintaining consistency with one embodiment. Each of e-nodes B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, e-nodes B160a, 160b, and 160c may implement MIMO technology. Thus, e-node B160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a.

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

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

[0042] The MME162 can be connected to each of the e-nodes B162a, 162b, and 162c in RAN104 via the S1 interface and can function as a control node. For example, the MME162 may perform roles such as authenticating users of WTRU102a, 102b, and 102c, activating / deactivating bearers, and selecting a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may provide control plane functionality for switching between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0043] The SGW164 can be connected to each of the e-nodes B160a, 160b, and 160c in RAN104 via the S1 interface. The SGW164 can generally route and forward user data packets to and from WTRU102a, 102b, and 102c. The SGW164 can also perform other functions, such as anchoring the user plane during e-node B handovers, triggering paging when DL data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

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

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

[0046] Although the WTRU is described as a wireless terminal in Figures 1A to 1D, in certain representative embodiments, such a terminal is intended to be able to use a wired communication interface with a communication network (for example, temporarily or permanently).

[0047] In a typical embodiment, the other network 112 may be a WLAN.

[0048] A WLAN in Basic Service Set (BSS) mode may have access points (APs) of the BSS and one or more stations (STAs) associated with the APs. APs may have access to or interfaces with other types of wired / wireless networks that carry traffic entering and / or leaving the Distribution System (DS) or BSS. Traffic originating outside the BSS and destined for an STA may reach and be delivered to the STA via an AP. Traffic originating from an STA and destined for an outside BSS destination may be sent to the AP so that it is delivered to its respective destination. Traffic between STAs within the BSS may be sent, for example, via an AP, where the source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between the source STA and the destination STA (for example, directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using Independent BSS (IBSS) mode may not have APs, and STAs within or using IBSS (e.g., all STAs) may communicate directly with one another. The IBSS mode of communication may be referred to herein as “ad hoc” communication mode.

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

[0050] High-throughput (HT) STAs may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

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

[0052] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using the non-TVWS spectrum. According to a typical embodiment, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within a macro communication range area. MTC devices may have limited performance, including certain performance characteristics, e.g., support for certain and / or limited bandwidths (e.g., supporting only these). MTC devices may include batteries with battery life exceeding a threshold (e.g., to maintain very long battery life).

[0053] A WLAN system capable of supporting multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes a channel that can be designated as the primary channel. 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 an STA from among all STAs operating in a BSS that support the minimum bandwidth operating mode. In an 802.11ah embodiment, the primary channel may be 1 MHz wide for an STA (e.g., an MTC type device) that supports (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. For example, if the primary channel is operational due to an STA (which only supports 1MHz operating mode) transmitting to the AP, the entire available frequency band may be considered operational, even though a large portion of the frequency band remains idle and could potentially be available.

[0054] In the United States, the available frequency band that can be used by 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.

[0055] Figure 1D is a system diagram illustrating RAN113 and CN115 according to one embodiment. As described above, RAN113 may employ NR radio technology to communicate with WTRU102a, 102b, and 102c via the air interface 116. RAN113 may also communicate with CN115.

[0056] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while maintaining consistency with one embodiment. Each of gNB180a, 180b, and 180c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, gNB180a, 180b, and 180c may implement MIMO technology. For example, gNB180a and 108b may use beamforming to transmit signals to and / or receive signals from gNB180a, 180b, and 180c. Thus, gNB180a may, for example, use multiple antennas to transmit and / or receive radio signals to and from WTRU102a. In one embodiment, gNB180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB180a may transmit multiple elemental carriers to WTRU102a (not shown). A subset of these elemental carriers may be on the unlicensed spectrum, while the remaining elemental carriers may be on the licensed spectrum. In one embodiment, gNB180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU102a may receive coordinated transmissions from gNB180a and gNB180b (and / or gNB180c).

[0057] WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using transmissions associated with scalable neurology. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or having varying absolute time durations).

[0058] gNB180a, 180b, and 180c can be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c without accessing other RANs (e.g., e-nodes B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c can utilize one or more of gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using signals in unauthorized bands. In a non-standalone configuration, WTRU102a, 102b, and 102c can communicate with and connect to gNB180a, 180b, and 180c, while also communicating with and connecting to other RANs such as enodes B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c can implement DC principles for substantially simultaneous communication with one or more gNB180a, 180b, and 180c and one or more enodes B160a, 160b, and 160c. In a non-standalone configuration, e-nodes B160a, 160b, and 160c can function as mobility anchors for WTRU102a, 102b, and 102c, and gNB180a, 180b, and 180c can provide additional coverage and / or throughput to service WTRU102a, 102b, and 102c.

[0059] Each of the gNB180a, 180b, and 180c may be associated with a specific cell (not shown) and may be configured to handle wireless resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a and 182b, and so on. As shown in Figure 1D, the gNB180a, 180b, and 180c may communicate with each other via the Xn interface.

[0060] The CN115 shown in Figure 1D may include at least one AMF182a, 182b, at least one UPF184a, 184b, at least one Session Management Function (SMF)183a, 183b, and optionally a Data Network (DN)185a, 185b. Although each of the aforementioned elements is depicted as part of the CN115, it will be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

[0061] AMF182a and 182b can be connected to one or more gNB180a, 180b, and 180c in RAN113 via the N2 interface and can function as control nodes. For example, AMF182a and 182b may perform roles such as user authentication for WTRU102a, 102b, and 102c, support network slicing (e.g., handling different PDU sessions with different requirements), selection of specific SMF183a and 183b, management of registration areas, termination of NAS signaling, and mobility management. Network slicing can be used by AMF182a and 182b to customize CN support for WTRU102a, 102b, and 102c based on the type of service utilizing WTRU102a, 102b, and 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 massive mobile broadband (eMBB) access, and services for machine type communication (MTC) access. AMF162 may provide control plane functionality for exchange between RAN113 and other RANs (not shown) using other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

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

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

[0065] In view of Figures 1A to 1D and their corresponding descriptions, one or more of the functions described herein with respect to one or more of the WTRU102a to d, base stations 114a and b, e-nodes-B160a to c, MME162, SGW164, PGW166, gNB180a to c, AMF182a to ab, UPF184a and b, SMF183a and b, DN185a and b, and / or any other devices described herein, may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0066] Emulation devices may be designed to implement testing of one or more other devices in a laboratory and / or carrier network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless network to test other devices in a communications network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless network. Emulation devices may be directly coupled to another device for testing purposes and / or may perform testing using terrestrial wireless communication.

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

[0068] In this specification, the following abbreviations and acronyms are used in particular: subcarrier spacing (Δf), NR node B (gNB), aperiodic (AP), beam failure recovery (BFR), beam failure detection-reference signal (BFD-RS), block error rate (BLER), bandwidth part (BWP), carrier aggregation (CA), contention-based (CB) (e.g., access, channel, resource), clear channel assessment (CCA), code division multiplexing (CDM), cell group (CG), crosslink interference (CLI), coordinated multi-point transmission / reception (CoMP), channel occupancy time (COT), cyclic prefix (CP), Common Phase Error (CPE), Conventional OFDM (relying on cyclic prefix, CP-OFDM), Channel Quality Indicator (CQI), Core Network (e.g., LTE packet core or NR core) (CN), Cyclic Redundancy Check (CRC), Channel State Information (CSI), Channel State Information-Reference Signal (CSI-RS), Central Unit (CU), Device-to-Device transmissions (D2D) (e.g., LTE sidelink), Dual Connectivity (DC), Downlink Control Information (DCI), Downlink (DL), Demodulation Reference Signal (DM-RS), Data Radio Bearer (DRB), Distributed Unit (DU), E-UTRA-NR Dual Connectivity (EN-DC), Evolved Packet Core (EPC), Frequency Domain-Code Division Multiplexing (FD-CDM), Frequency Division Duplexing (FDD), Frequency Division Multiplexing (FDM), Hybrid Automatic Retransmission Request Negative Response (HARQ NACK), Inter-Cell Interference (ICI), Inter-Cell Interference Cancellation (ICIC), Internet Protocol (IP), Listen-Before-Talk (LBT), Logical Channel (LCH), Logical Channel Identity (LCID), Logical Channel Prioritization (LCP), Low Latency Communication (LLC), Long Term Evolution (LTE) (e.g., 3GPP LTE R8 and later), Medium Access Control (MAC), Medium Access Control Control Element (MAC CE), Negative (ACK) NACK, Multimedia Broadcast Multicast System (MBMS), Master Cell Group (MCG), Modulation and Coding Scheme (MCS), Multiple Input Multiple Output (MIMO), Machine-Type Communication (MTC), Multi-RAT Dual Connectivity (MR-DC), Non-Access Stratum (NAS), New Candidate Beam-Reference Signal (NCB-RS), NR-RAN-E-UTRA Dual Connectivity (NR-RAN-E-UTRA DualConnectivity (NE-DC), New Radio (NR), New Radio Dual Connectivity (NR-DC), Orthogonal Frequency-Division Multiplexing (OFDM), Out-Of-Band (OOB) (radiation), Total available WTRU power (Pcmax) in a given transmission interval, Primary cell (Pcell) of a master cell group, Primary cell group (PCG), Protocol Data Unit (PDU), Packet Error Rate (PER), Physical Layer (PHY), Public Land Mobile Network (PLMN), Packet Loss Rate (PLR), Physical Random-Access Channel (PRACH), Physical Resource Block (PRB), Positioning Reference Signal (PRS), Primary cell of a secondary cell group Secondary cell group (PScell), Primary Synchronization Signal (PSS), Phase Tracking-Reference Signal (PT-RS), Quality of Service (QoS) (from a physical layer perspective), Radio Access Bearer (RAB), Radio Access Network Paging Area (RAN PA), Random Access Channel (or Procedure) (RACH), Random Access Response (RAR), Radio Access Technology (RAT), Resource Block (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 (ROM) (for MBMS), Radio Resource Control (RRC), Radio Resource Management (RRM), Reference Signal (RS), Round-Trip Time (RTT), Secondary Cell Group (SCG), Single Carrier Multiple Access (SCMA), Subcarrier Spacing (SCS), Service Data Unit (SDU), Spectrum Operation Mode (SOM), Semi-persistent (SP), primary cell (SpCell) of a master or secondary cell group, signaling radio bearer (SRB), synchronization signal (SS), sounding reference signal (SRS), secondary synchronization signal (SSS), supplemental uplink (SUL), switching gap (SWG) (in a self-contained subframe), transport block (TB), transport block size (TBS), transmission configuration index (TCI), time-division duplexing (TDD), time-division multiplexing (TDM), time interval (TI) (an integer multiple of one or more symbols), transmission time interval (TTI) (an integer multiple of one or more symbols), transmission / reception point Point (TRP), Transmission / Reception Point Group (TRPG), Tracking Reference Signal (TRS), Transceiver (TRx), Uplink (UL), Ultra-Reliable Communication (URC), Ultra-Reliable and Low Latency Communications (URLLC), Vehicle-to-Vehicle (V2X), Wireless Local Area Networks (WLANs) and related technologies (IEEE 802.xx domain), as well as cross-division duplexing (XDD).

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

[0070] In one embodiment, the WTRU may receive triggers for event-based interference sensing and / or measurement. The WTRU may receive triggers for event-based interference sensing and / or measurement, such as CLI. The WTRU may receive triggers for event-based interference sensing and / or measurement for one or more of the active SB and reference SBs (e.g., Ref_SB). In one example, an event to trigger CLI sensing may be one or both of a WTRU request and / or a gNB instruction. For example, an event to trigger CLI sensing may correspond to a victim WTRU determining one or more DL receive failures. For example, a victim WTRU may determine one or more DL receive failures along with sending, for example, N NACKs. In some cases, a victim WTRU may determine one or more DL receive failures based on a counter exceeding a threshold. For example, a victim WTRU may determine one or more DL receive failures based on a counter exceeding a threshold within a time window (e.g., a timer). For example, an event to trigger CLI sensing could correspond to the need to bypass a signal block (SB) and the need for the WTRU to communicate via another SB. For instance, the WTRU might need to communicate via another SB as a complementary mechanism for XDD.

[0071] In one or more cases, the WTRU may receive the type of interferometry. For example, the types of interferometry 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, inter-subband CLI of a set of cells / TRPs having RBs that partially overlap between UL and DL. Non-overlapping CLI may be inter-subband CLI.

[0072] In one example, a WTRU may measure CLI-RSSI and / or SRS-RSRP over a given short period of time across the entire configured frequency / subband resource. The measured values ​​may be reported via L1 signaling (e.g., L1-CLI-RSSI reported via PUCCH, PUSCH, RACH, SRS). For example, a WTRU may report the measured values. L1 signaling such as L1-CLI-RSSI may be reported via PUCCH, PUSCH, RACH, SRS, etc., but is not limited to these. In one example, a WTRU may receive a configuration for a delta CLI-RSSI measurement. In some cases, a WTRU may determine the delta CLI-RSSI. For example, a WTRU may determine the delta CLI-RSSI based on the difference between a first CLI-RSSI (e.g., CLI-RSSI1) and a second CLI-RSSI (e.g., CLI-RSSI2). For example, Delta CLI-RSSI = CLI-RSSI1 - CLI-RSSI2. In some cases, the first CLI-RSSI may be measured from a resource located in the center of the scheduled RB. In some cases, the second CLI-RSSI may be measured from a resource located on the edge of the scheduled RB. In one or more cases, WTRU may report Delta CLI-RSSI based on the fact that the scale Delta CLI-RSSI is greater than a threshold indicating the CLI of a potential edge RB. The CLI of a potential edge RB may be, for example, a non-overlapping CLI.

[0073] In cases where a WTRU detects / measures interference, the WTRU may report CLI detection / measurement. For example, a WTRU may report CLI detection measurement based on L1-CLI-RSSI and their respective thresholds. In one or more cases, the WTRU may send a flag in addition to the NACK transmission to indicate potential interference. For example, a flag may indicate that the NACK transmission is based on detecting interference. For example, detecting interference can occur when L1_CLI_RSSI is above its respective threshold. In another example, a flag may indicate that the NACK transmission is based on interference such as CLI. Based on the interference, the WTRU may request an SR for interference measurement (e.g., L1-CLI-RSSI). In one or more cases, the WTRU may request to switch to a different reference subband (e.g., from Ref_SB). For example, the WTRU may request to switch to a different reference subband where the WTRU may not have detected interference. For example, WTRU may require switching to another reference subband, such as L1-CLI-RSSI, which is lower than the respective threshold, although this is not limited to WTRU.

[0074] Transmit concessions may be performed after sensing. In some cases, a potential aggressor WTRU may determine a list of reference subbands (e.g., Ref_SB). A WTRU may switch to the list of reference subbands if, for example, a CLI could be triggered against a potential victim WTRU in the active SB. For example, a WTRU may receive a subset of a time-frequency resource mask, such as a set of subbands or a set of symbols / slots. In some cases, an aggressor WTRU may perform event-based CLI / channel occupancy sensing in the active SB. For example, an aggressor WTRU performs event-based CLI / channel occupancy sensing in the active SB if a victim WTRU determines one or more DL receive failures. A victim WTRU may determine one or more DL receive failures based on a counter exceeding a threshold. In some cases, a victim WTRU determines one or more DL receive failures, for example, by sending a NACK. In some cases, a victim WTRU may determine one or more receive failures based on a counter exceeding a threshold within a time window, such as a timer. In some cases, a WTRU may determine that a potential victim WTRU has a DL based on the aggressor WTRU detecting channel occupancy. In one example, a WTRU may propose a UL SB / BWP / CC that may not trigger a CLI for a potential victim UE by reporting one or more of the subbands to which it will switch. In some cases, alternatively or in conjunction with other actions, an aggressor WTRU may receive instructions to prevent it from transmitting on one or more configured permitted resources. An aggressor WTRU may receive instructions (e.g., permission cancellation) to prevent it from transmitting on one or more configured permitted resources due to interference. In one example, an aggressor WTRU may be prevented from transmitting on one or more permitted resources in one or more of the following slots / symbols, and the slot / symbol resources may be identified.In one or more cases, the Aggressor WTRU and / or Victim WTRU may receive a Group Common DCI. The Group Common DCI may, for example, indicate mutual interference and / or measurement, reporting, and / or SB unit avoidance, but is not limited to these.

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

[0076] Figure 2 illustrates a system 200 experiencing an example of crosslink interference (CLI) directional sensing. System 200 may include a serving cell 202, a non-aggressor cell (DL) 204, an aggressor WTRU (UL) 206, and a victim WTRU 208. The victim WTRU 208 may report directional CLI / channel sensing as shown in Figure 2.

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

[0078] Figure 4 illustrates an exemplary system 400 experiencing crosslink interference (CLI), between gNBs, and between WTRUs. Achieving XDD may be conditional on resolving challenges that may arise due to crosslink interference (CLI), as shown in Figure 4. For example, in an XDD framework, a potential aggressor cell may switch its transmit mode in one or more subbands (SBs) from UL to DL, or vice versa, which may, in one example, cause subband-level CLI on potential victim gNBs and WTRUs. In one example, CLI-RSSI measurements may be based on long-term measurements. In UL-DL CLI, CLI from an aggressor WTRU may cause strong interference on a victim WTRU in a particular SB, while other SBs may remain unaffected. CLI in XDD is not limited to WTRUs at the cell edge. Rather, WTRUs at the center and / or middle of the beam may experience CLI. Therefore, WTRUs may be configured to perform SB-level CLI measurements.

[0079] In some cases, CLI may be caused by another WTRU. When another WTRU causes CLI, CLI may depend on the direction of the transmitting beam. Furthermore, CLI may depend on sensing in all directions, which can lead to false detection of CLI. Different WTRU behavior may occur in the case of subband-level CLI in an XDD based on false detection of CLI. Therefore, WTRUs may be configured for channel sensing for potential subband-level CLI, CLI avoidance by switching to other SBs, and directional CLI sensing in an XDD, as described herein.

[0080] In one or more cases where CLI is sensed, the WTRU may be configured to determine and / or switch to an SB unaffected by CLI, as described herein. In one or more cases, the aggressor WTRU may be configured to consider interference caused to the victim WTRU. In one or more cases, the WTRU may be configured to find the optimal means of measuring 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 in the victim WTRU. In one or more cases, a subband post-sensing avoidance report (ARAS) may be performed. In one or more cases, a transmit concession may be performed after sensing in the aggressor WTRU. In one or more cases, directional CLI sensing and measurement may be performed.

[0081] In this specification, “a” and “an” and similar phrases should be interpreted as “one or more” and “at least one.” Similarly, any term ending in the suffix “(s)” should be interpreted as “one or more” and “at least one.” The term “may” should be interpreted as “for example, may.”

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

[0083] The WTRU may receive a first (e.g., target) downlink channel and / or signal according to the same spatial domain filter and / or spatial reception parameters as a second (e.g., reference) downlink channel or signal. For example, such an association may exist between physical channels such as a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH), and / or their respective DM-RS. In one example, such an association may exist when the WTRU is configured as a quasi-colocation (QCL) assumption type D between corresponding antenna ports, for example, when the first and second signals 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 or SS block and a DM-RS by index to a set of TCI states, which may be configured by the RRC and / or signaled by the MAC CE. Such indication may be referred to as a beam indication.

[0084] A Transmitting and Receiving Point (TRP) may be used interchangeably with one or more of the following: a transmission point (TP), a reception point (RP), a radio remote head (RRH), a distributed antenna (DA), a base station (BS), a sector (e.g., a sector of a BS), and / or a cell (e.g., a geographic cell area serviced by a BS). A multi-TRP may be used interchangeably with one or more of the following: MTRP, M-TRP, and / or multiple TRPs.

[0085] The terms “subband” and “sub-band” 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), e.g., a set of resource block sets (RB sets) when a carrier has an intra-cell guard band, a set of interlaced 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 the starting RB and / or the number of RBs for a set of consecutive RBs within a bandwidth portion. In another example, a subband may be defined by the value of the frequency domain resource allocation field and / or the bandwidth portion index.

[0086] The term "XDD" may be used to refer to a spatial domain filter. In one or more cases, either UL or DL ​​may be used per subband. An 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 same-frequency full duplexing, advanced duplexing methods, e.g., other than (pure) TDD or FDD. Cross-division duplexing may be, for example, subband-unit FDD within the TDD band. Subband-based full duplexing may be, for example, full duplexing where both UL and DL may be used / mixed on a symbol / slot, and either UL or DL ​​may be used per subband on a symbol / slot. Non-same-frequency full duplexing may include, for example, spectrum sharing, subband-unit overlap, etc.

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

[0088] A WTRU may report a subset of Channel Status Information (CSI) components. For example, a CSI component may correspond to one or more of the following: CSI-RS resource indicator (CRI), SSB resource indicator (SSBRI), panel indication used for reception in the WTRU (e.g., panel identification information or group identification information), measured values ​​such as L1-RSRP, L1-SINR taken from SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel status information. Other channel status information may include, for example, one or more of the following: rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), layer index (LI), etc.

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

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

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

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

[0093] WTRU may measure and / or report Channel Status Information (CSI). For example, CSI for each connection mode may include and / or consist of one or more of the following: CSI reporting configuration, CSI-RS resource set, and NZP-CSI-RS resource. For example, CSI reporting configuration may include one or more of the following: CSI reporting quantity, CSI reporting type, CSI reporting codebook configuration, and CSI reporting frequency. CSI reporting quantity may include, for example, Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), etc. CSI reporting type may include, for example, aperiodic, semi-permanent, periodic, etc. CSI reporting codebook configuration may include, for example, Type I, Type II, Type II port selection, etc. For example, CSI-RS resource set may include one or more CSI resource settings. CSI resource configurations may include, but are not limited to, NZP-CSI-RS resources for channel measurements, NZP-CSI-RS resources for interference measurements, and CSI-IM resources for interference measurements. NZP CSI-RS resources may include, but are not limited to, one or more of the following: NZP CSI-RS resource ID, periodicity and offset, QCL information and / or TCI status, and resource mapping (e.g., number of ports, density, CDM type, etc.).

[0094] A WTRU may indicate, determine, and / or consist of one or more reference signals. In one example, a WTRU may monitor, receive, and / or measure one or more parameters based on each reference signal. For example, the parameters may include one or more of the following: SS-RSRP, CSI-RSRP, SS-SINR, CSI-SINR, RSSI, CLI-RSSI, and SRS-RSRP. The parameters monitored, received, and / or measured by a 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 a reference signal measurement. For example, one or more of these parameters may be included in a reference signal measurement. In another example, other parameters may be included in a reference signal measurement.

[0095] The SS reference signal received power (SS-RSRP) can be measured based on a synchronization signal. The synchronization signal may be, for example, a demodulation reference signal (DMRS) in a PBCH or SSS. In one example, SS-RSRP may be defined as a linear average across the power contributions of the resource elements (REs) that can carry each synchronization signal. Power scaling of the reference signal may be required when measuring RSRP. When SS-RSRP is used for L1-RSRP, the WTRU may perform the measurement based on a CSI reference signal in addition to the synchronization signal. In one or more cases, CSI-RSRP may be measured based on a linear average across the power contributions of the REs carrying each CSI-RS. In one example, the CSI-RSRP measurement may be configured within the measurement resources for the configured CSI-RS occasion. In one or more cases, the SS signal-to-noise and interference ration (SS-SINR) can be measured based on a synchronization signal. The synchronization signal may be, for example, a DMRS in a PBCH and / or SSS. The SS-SINR may be a linear average over the total power contributions of REs capable of carrying each synchronization signal, divided by a linear average of noise and interference power contributions. Noise and / or interference power measurements may be achieved, for example, when the SS-SINR is used for the L1-SINR, based on the resources that can be comprised by the higher layers. In one or more cases, the CSI-SINR may be measured based on a linear average over the total power contributions of REs capable of carrying each CSI-RS, divided by a linear average of noise and interference power contributions. Noise and interference power measurements may be achieved, for example, when the CSI-SINR is used for the L1-SINR, based on the resources that can be comprised by the higher layers. Alternatively, or in conjunction with, noise and / or interference power may be measured based on the resources that can carry each CSI-RS.In one or more cases, the Received Signal Strength Indicator (RSSI) may be measured based on the average of the total power contributions across the configured OFDM symbols and bandwidth. For example, power contributions may be received from different resources. These different resources may include, but are not limited to, same-channel serving and non-serving cells, adjacent channel interference, and thermal noise. In one or more cases, the Crosslink Interference Received Signal Strength Indicator (CLI-RSSI) may be measured based on the average of the total power contributions across the configured OFDM symbols of the configured time and / or frequency resources. For example, power contributions may be received from different resources. These different resources may include, for example, crosslink interference, same-channel serving and non-serving cells, adjacent channel interference, and thermal noise. In one or more cases, the Sounding Reference Signal (SRS-RSRP) may be measured based on a linear average across the total power contributions of the REs carrying each SRS.

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

[0097] DCI indications may include one or more of the following: explicit indications by DCI fields and / or RNTI, and implicit indications by properties. For example, explicit indications by DCI fields and / or RNTI may be used to mask the CRC of a PDCCH. For example, implicit indications by properties may be, for example, DCI format, DCI size, core set and / or search space, aggregation level, and the first resource element of the received DCI (e.g., index of the first control channel element). For example, mappings between properties and / or values ​​may be signaled by RRC and / or MAC.

[0098] 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 may be 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 may be consistent with the disclosed embodiments. In one or more cases, Interference may be used interchangeably with CLI, CLI-RSSI, and / or SRS-RSRP, and may be consistent with the disclosed embodiments.

[0099] In one or more cases, a Post-Sensing Avoidance Report (ARAS) may be performed. For example, the WTRU may receive one or more configuration parameters for CSI / beam reporting (e.g., from the gNB). One or more configuration parameters may include, for example, one or more DL RS (e.g., CSI-RS) resources. One or more DL RS resources may be for DL ​​measurements to derive and / or determine the CSI (and / or beam index and / or beam quality metric) that may be reported in a time instance for CSI / beam reporting. For example, the WTRU may receive beam / TCI indications and / or configurations (e.g., from the gNB). The beam / TCI indications and / or configurations may be used for receiving DL signals. For example, the beam / TCI indications and / or configurations may be determined by the gNB based on the CSI / beam reporting from the WTRU. For example, the WTRU may receive a grant (e.g., a DCI including DL allocation) to schedule the reception of DL signals. WTRU may receive DL signals using a spatial filter, which may be determined, for example, based on beam / TCI indication.

[0100] In one or more cases, interference may exist based on signals transmitted by a second WTRU (e.g., a nearby WTRU from the WTRU), which may affect (e.g., degrade and / or reduce) the DL signal receiving performance at the WTRU. In one or more cases, the presence of interference may not be known before granting. For example, the presence of interference may not be known before granting if the second WTRU may be associated with a different serving cell / TRP from the WTRU. In one example, the WTRU may fail to receive the DL signal due to interference. The interference may be, for example, a WTRU-WTRU CLI based on a second UL signal from the WTRU. In some cases, the interference may not be captured in the CSI / beam report. For example, the interference may not be captured in the CSI / beam report because one or more DL RS resources may reflect (e.g., be associated with) the UL signal transmission of the second WTRU. The DL signal may degrade DL performance in communication between the gNB and the WTRU, for example. In one or more cases, failures in receiving the DL signal may continue to occur. For example, a WTRU may fail to receive a DL signal if the DL signal is retransmitted by a gNB. A WTRU may also fail to receive a DL signal if an unexpected WTRU-WTRU CLI exists for a certain duration.

[0101] A WTRU (e.g., a potential victim WTRU) may determine a list of reference subbands (e.g., Ref_SB) that the WTRU can use or switch to. In one or more cases, the WTRU may be indicated and / or configured to have a list of reference subbands. For example, the WTRU may be instructed to switch to a subband, to use a subband for communication between the WTRU and the gNB, and / or to use a 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 list of reference subbands as a subset of the time-frequency resource mask (e.g., a set of subbands and / or a set of symbols / slots). The WTRU may receive a configuration for CLI sensing and / or measurement on Ref_SB.

[0102] A WTRU may receive triggers for CLI sensing and / or measurements on Ref_SB. For example, a WTRU may explicitly receive triggers and / or measurements. Measurements may include, for example, aperiodic channel sensing. In one or more cases, triggers may be based on an active (e.g., the current, currently communicating with the gNB / TRP, etc.) SB and / or one or more reference SBs (e.g., Ref_SB). The active SB may be, for example, the current SB, the SB currently communicating with the gNB / TRP, etc., but are not limited to these. In one or more cases, a 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 met. For example, based on the determination that at least one event and / or condition may be met, a WTRU may initiate (e.g., execute, start, perform, run, etc.) CLI sensing and / or measurement. In some cases, the WTRU may initiate CLI sensing and / or measurement based, for example, on at least one reference SB (e.g., Ref_SB), and / or at least one instruction, preconfiguration, and / or predetermined resource.

[0103] A WTRU may transmit (e.g., report) at least SB-related information content. This SB-related information content may include, for example, one or more SB indices, corresponding SB unit metrics, etc. SB unit metrics may include, for example, SB unit CLI-RSSI, SB unit quality metrics, etc. In one or more cases, a WTRU may transmit at least SB-related information content based on the fact that CLI sensing and / or measurement has been performed and / or taken. For example, a WTRU may transmit at least SB-related information content after CLI sensing and / or measurement has been performed and / or taken. Thus, a gNB may use the reported SB-related information content to circumvent a particular RB and communicate with the WTRU. This could be an example of a post-sensing circumvention reporting (ARAS) mechanism that may be applied in a WTRU (e.g., based on the configuration of the ARAS that may be received in the WTRU).

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

[0105] In another example, CLI sensing / measurement may be initiated when a WTRU (e.g., victim WTRU) determines that it has failed to receive one or more (e.g., K) DL data (e.g., PDSCH) and / or when the WTRU sends one or more NACKs in response to at least one failure when receiving one or more (e.g., scheduled) PDSCHs. For example, for 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 having determined that it has failed to receive a PDSCH (e.g., scheduled PDSCH). The NACKs could be, for example, a negative ACK, a negative response, etc., but are not limited to these. In another example, for the case where K=2 or K>2, at least one event / condition may be satisfied if the WTRU determines, for example, two (or K) occasions of PDSCH reception failure within a time window, and / or if the WTRU sends two (or K) NACKs based on at least two (or K) failures determined when receiving two (or K) scheduled PDSCHs within a time window. The parameter / value for the time window may be configured / indicated by the gNB.

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

[0107] A WTRU may receive triggers (e.g., explicitly or implicitly) for measuring one or more types of interference (e.g., CLI) measurements. A WTRU may receive indications and / or configurations of one or more of the following types of interference measurements: overlapping CLI, partially overlapping CLI, and overlapping CLI. An overlapping CLI may be, for example, an intra-subband CLI. In one example, an overlapping CLI may correspond to a CLI across an entire set of RBs that overlap between DL reception (region) and UL transmission (region). For example, an overlapping CLI may span an entire set of RBs that overlap between DL reception and UL transmission, for example, in a cell / TRP or a set of cells / TRPs. A set of cells / TRPs may be, for example, a set of geographically dispersed cells / TRPs.

[0108] A partially overlapping CLI can be a CLI that spans an entire set of RBs that partially overlap between DL reception (region) and UL transmission (region). For example, a partially overlapping CLI can be a CLI that spans an entire set of RBs that partially overlap between DL reception and UL transmission, for example, in a cell / TRP or in a set of cells / TRPs. A set of cells / TRPs can be, for example, a set of geographically dispersed cells / TRPs. A partially overlapping CLI can be a CLI that spans an entire set of RBs where a first set of RBs and a second set of RBs may partially overlap. For example, a partially overlapping CLI can be a CLI between (i.e., an occurrence) in a cell / TRP or in a set of cells / TRPs where a first set of RBs and a second set of RBs may partially overlap. A set of cells / TRPs can be, for example, within a set of geographically dispersed cells / TRPs.

[0109] Non-overlapping CLIs can be, for example, inter-subband CLIs. A non-overlapping CLI can be a CLI between (i.e., occurring) a first set of RBs for DL ​​reception (region) and a second set of RBs for UL transmission (region), where the first set of RBs and the second set of RBs do not overlap. The first set of RBs and the second set of RBs do not overlap, for example, when there is an M(≧0)RB gap between the DL reception region and the UL transmission region. A non-overlapping CLI can be a CLI in a cell / TRP, or in a set of cells / TRPs, between a first set of RBs for DL ​​reception and a second set of RBs for UL transmission. In one example, the set of cells / TRPs could be, for example, a set of geographically dispersed cells / TRPs. A non-overlapping CLI can also occur when the first set of RBs and the second set of RBs do not overlap (for example, there may be an M(≧0)RB gap between the DL reception region and the UL transmission region).

[0110] The WTRU may be configured, determined, and / or instructed to perform a measurement of the CLI Received Signal Strength Indicator (RSSI) over a given period. A given period may, for example, include, one or more slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs), but is not limited to these. In one example, the CLI-RSSI may be measured over a given time / frequency resource. The CLI-RSSI may be referred to as L1-CLI-RSSI, short-term CLI-RSSI, aperiodic CLI-RSSI, etc. It should be noted that CLI-RSSI, L1-CLI-RSSI, and / or RSSI may be used interchangeably when describing the embodiments disclosed herein.

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

[0112] In one or more cases, the CRMR may be a resource composed of, determined, and / or defined by one or more of the following characteristics: a set of muted REs in a downlink resource, a set of REs 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 in a second CDM group, and / or located in a scheduled resource. The one or more reference signals may be, for example, DMRS, SRS, sidelink CSI-RS, etc. A CRMR resource located in a scheduled resource may be, for example, a scheduled PDSCH RB.

[0113] In one example, a set of muted REs in a downlink resource (e.g., PDSCH) can be rate-matched and / or punctured for downlink reception and / or uplink transmission. In one example, the set of muted REs may have the same pattern (e.g., the same time / frequency position) at each RB. In another example, the set of muted REs may have different patterns based on RB location. 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 and second patterns may have, for example, different numbers of muted RESs. In another example, the muted Ress may take the form of zero-power CSI-RSs (e.g., ZP-CSI-RSs).

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

[0115] A second set of DMRS REs within a second CDM group could, for example, be within a PDSCH, e.g., a Scheduled Downlink Resource / RB. The second set of DMRS REs within a second CDM group could correspond to a WTRU receiving a DCI that schedules a PDSCH, which may indicate a first set of DMRS REs corresponding to the first CDM group. The first CDM group may be used to receive the PDSCH. In one example, the WTRU may receive a DCI that schedules a PDSCH, which indicates a first set of DMRS REs corresponding to the first CDM group. The WTRU may receive a DCI that schedules a PDSCH, which indicates a first set of DMRS REs corresponding to the first CDM group, based, for example, the indicated antenna port (e.g., DMRS antenna port) field of the DCI. Based on having received the DCI, the WTRU may determine that a second set of DMRS REs within a second CDM group can be used as a CRMR. In one or more cases, the second CDM group may be a group other than the first CDM group. In one or more cases, the WTRU may determine that a second set of DMRS REs within a second CDM group can be used as CRMR, for example, within a scheduled PDSCH.

[0116] In one or more cases, CRMR may be configured in common for a set of WTRUs (e.g., adjacent WTRUs). For example, a gNB may configure CRMR for a group of WTRUs. A group of WTRUs may share one or more of the following: a group ID for receiving DCI, a zone ID, and / or WTRUs paired for sidelink unicast (and / or, e.g., groupcast) transmissions. The group ID for receiving DCI may be, for example, group RNTI. The zone ID may be determined based on the geographical location of the WTRUs, such as GNSS, but is not limited to these. In one or more cases, an L1-CLI-RSSI metric (including, for example, CRMR resources) may be considered a CSI reporting quantifiable and / or configured as part of a CSI reporting setup.

[0117] The WTRU may be configured, determined, and / or instructed to perform delta-CLI-RSSI. Delta-CLI-RSSI may be based, for example, on a first CLI-RSSI measurement at a first time / frequency position and a second CLI-RSSI measurement at a second time / frequency position. One or more of the following may apply: In one or more cases, delta-CLI-RSSI (i.e., delta-CLI-RSSI) may be the difference between the first CLI-RSSI (i.e., CLI-RSSI1) and the second CLI-RSSI (i.e., CLI-RSSI2). For example, delta-CLI-RSSI = CLI-RSSI1 - CLI-RSSI2. In another example, delta-CLI-RSSI = CLI-RSSI2 - CLI-RSSI1. In one or more cases, the first CLI-RSSI may be measured from CRMR resources located at the edge of the scheduled RB, while the second CLI-RSSI may be measured from CRMR resources located in the center of the scheduled RB. Thus, radio resource overhead can be reduced, for example, by having the first and second CLI-RSSIs not have to be configured on REs separated from the scheduled RB. In one example, the first and second CLI-RSSIs may not have to be configured on REs separated from the scheduled RB, based on the fact that the delta CLI-RSSI was determined based on CLI-RSSI1-CL-RSSI2, and may represent, capture, and / or reflect the amount of CLI. Delta CLI-RSSI can represent, capture, and / or reflect the amount of CLI, since CLI-RSSI1 may primarily represent and / or include general downlink intra-cell / inter-cell interference, and CLI-RSSI2 may represent and / or include greater CLI leakage interference (e.g., inter-subband CLI) than CLI-RSSI1 (in addition to general DL interference).For example, when a UL transmission from an aggressor WTRU (e.g., a UL transmission that causes a CLI) occurs on an adjacent RB (e.g., a nearby RB) to 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 greater than CLI-RSSI1. In one or more cases, the WTRU may consist of a first CRMR resource for a first CLI-RSSI measurement and a second CRMR resource for a second CLI-RSSI measurement. In one or more cases, the WTRU may decide to report CLI measurement-related information when the measured delta CLI-RSSI is greater than a threshold. For example, CLI reporting 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.

[0118] The WTRU may be configured or determined to measure CLI-RSSI for each subband level. For example, 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, the first subband size may be used when the scheduled RBs are greater than X. In yet another example, the second subband size may be used when the scheduled RBs are less than or equal to X. In one or more cases, the WTRU may report CLI-RSSI measurements for one, more, or all subbands. In one or more cases, the WTRU may report a subset of CLI-RSSIs. The subset may be determined based on one or more conditions, but are not limited to, such as CLI-RSSI values ​​exceeding a threshold, subband location (e.g., scheduled RB edges), and subband index.

[0119] In one or more cases, the bandwidth of beam measurement and / or reporting (e.g., broadband and / or subband) may be determined based on one or more conditions (e.g., by the WTRU). Conditions may include, but are not limited to, slot type and the presence of CLI-RSSI measurements. In one example, the slot type may be an XDD slot and / or a non-XDD slot. For example, a WTRU may report a broadband CRI (e.g., broadband beam index) in a non-XDD slot (e.g., no uplink and downlink resources in the same slot (e.g., due to duplex operation)). In another case, a WTRU may report a subband CRI (e.g., subband beam index) in an XDD slot (e.g., uplink and downlink resources are in the same slot, e.g., due to duplex operation). With respect to the presence of CLI-RSSI measurements, the bandwidth of beam measurement and / or reporting may be determined based on whether CLI-RSSI is measured in the same slot.

[0120] The WTRU may be instructed to perform CLI-RSSI measurements at specific frequency locations within a scheduled RB. In one or more cases, the WTRU may be instructed to perform CLI-RSSI measurements at specific frequency locations within a scheduled RB. In one or more cases, the WTRU may be instructed to perform CLI-RSSI measurements at specific frequency locations within both scheduled and unscheduled RBs. The specific frequency locations may correspond to one or more of the subbands, RBs, and REs. In one or more cases, the instruction may be in a DCI that can trigger the CLI-RSSI measurement. The CLI-RSSI measurement may be, for example, a periodic CLI-RSSI measurement. In one or more cases, the specific frequency locations may be instructed based on the frequency locations of CRMR resources. For example, based on the configuration, one or more CRMR resources may be configured, and / or each CRMR resource may be located at a specific frequency location. The WTRU may be instructed to perform measurements on the CRMR resources instructed in the DCI.

[0121] A WTRU may be configured, determined, or instructed to report channel and / or interference measurements. A WTRU may report the measured intensity and / or power of a reference signal (e.g., CLI-RSSI, SRS-RSRP, L1-CLI-RSSI) at a configured resource. In one or more cases, a WTRU may report the level of the measured intensity and / or power of the reference signal based on one or more configured and / or determined thresholds. For example, a WTRU may report the potential presence of interference if the measured power and / or intensity is higher than a configured and / or determined threshold. In another example, a WTRU may report the potential presence of partial and / or subband edge interference (e.g., CLI) if the difference between measurements at one or more resources is higher than a configured and / or determined threshold. Alternatively, a WTRU may report and / or require that one or more subbands are reliable for switching if, for example, the measured interference power and / or intensity is lower than a configured and / or determined threshold.

[0122] A WTRU may indicate at least one type of information content (e.g., CLI-related) discussed throughout this disclosure (e.g., via transmission, sending, reporting, etc.). For example, the information content may correspond to one or more of the following: interference level, CLI level, subband unit CLI, measurement result / metric based on measuring CRMR, delta CLI-RSSI, etc. A WTRU may indicate at least one type of information content, for example, via a Negative Response (NACK) transmission. For example, a WTRU may indicate at least one type of information content with a NACK transmission, in addition to the NACK transmission, based on a HARQ-ACK codebook which includes one or more (e.g., additional) bits to indicate at least one type of information content. In one or more cases, a NACK transmission may be performed in response to a scheduled PDSCH reception failure. In one example, a WTRU may send a flag signal with a NACK transmission. For example, a WTRU may send a flag signal with a NACK transmission in response to a scheduled PDSCH reception failure. A flag signal accompanying a NACK transmission may, for example, indicate that the power and / or intensity of interference has been measured, and that the measured power and / or intensity is higher than configured and / or determined thresholds. For example, L1-CLI-RSSI values ​​above each threshold may indicate the potential presence of interference. In another case, a WTRU may, for example, in response to a failed reception of a scheduled PDSCH, send a flag signal along with a NACK transmission to indicate that the NACK may be potentially caused by interference (e.g., CLI). For example, a WTRU may send a flag along with a NACK to request a scheduling request (SR) for channel and / or interference measurements (e.g., L1-CLI-RSSI measurements). In one or more cases, a WTRU may be configured to measure and / or sense interference power / intensity (e.g., CLI via L1-CLI-RSSI) in one or more reference subbands.

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

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

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

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

[0127] A WTRU may be configured with operating modes involving dynamic and / or semi-static authorized resource determination. For example, a WTRU may use one or more operating modes (e.g., dynamic and / or semi-static determination) to decide to use, avoid, and / or switch to authorized resources. The number of configured authorized resources (e.g., maximum number) may be determined based on the operating modes to be decided, 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, and the operating mode may be determined based on WTRU capability and / or gNB configuration, for example, based on WTRU capability reporting. In one example, a WTRU may determine the operating mode based on the configuration and / or the number of authorized resources indicated for dynamic operation. For example, a gNB may indicate and / or configure one or more authorized resources. In some cases, a WTRU may decide to use a semi-static determination mode. In other cases, a WTRU may decide to use a dynamic determination mode. When a gNB designates and / or configures one authorized resource, the WTRU may decide to use semi-static decision mode. When a gNB designates and / or configures two or more authorized resources, the WTRU may decide to use dynamic decision mode. In another example, the decision may be based on WTRU capability and / or gNB configuration based on WTRU capability reporting. In one or more cases, the WTRU may designate one or more authorized resources as WTRU capability. In one or more cases, the WTRU may decide to use semi-static decision mode and / or dynamic decision mode. When a WTRU designates one authorized resource as WTRU capability, the WTRU may decide to use semi-static decision mode. When a WTRU designates two or more authorized resources as WTRU capability, the WTRU may decide to use dynamic decision mode. In one or more cases, gNB configuration may be performed based on reported WTRU capability.

[0128] In one or more cases, the WTRU may request a preferred operating mode to be determined from among the permitted resources. The WTRU may be capable of supporting one or both operating modes. The WTRU may instruct the gNB of one or more preferred operating modes. If the WTRU can support both operating modes, the WTRU may instruct the gNB of a preferred operating mode. In one or more cases, the WTRU may determine a preferred operating mode based on one or more of the following: interference intensity, channel quality, and / or traffic.

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

[0130] A WTRU can determine a preferred operating mode based on channel quality. For example, a WTRU may measure channel quality for one or more of the permitted resources. A WTRU may measure channel quality such as CQI, RSRP, SINR, path loss, and probability of blockage. In one example, a WTRU may decide to use a dynamic decision mode if the measured channel quality for one or more of the permitted resources is below their respective thresholds. Thus, a WTRU can dynamically report, request, and / or switch permitted resources based on channel quality.

[0131] A WTRU may determine a preferred mode of operation based on traffic (e.g., the amount of data received and / or transmitted). For example, a WTRU may decide to use a dynamic decision mode when traffic exceeds a certain threshold. Thus, a WTRU may dynamically report, request, and / or switch authorized resources based on traffic.

[0132] In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may use the instructed and / or configured authorized resources to transmit and / or receive channels and / or signals, and to sense, process, and measure one or more channels and / or signals. In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may use the instructed and / or configured authorized resources to transmit and / or receive channels and / or signals. In one or more cases, in a first operating mode (e.g., semi-static determination), the WTRU may use the instructed and / or configured authorized resources to sense, process, and / or measure one or more channels and / or signals. In one or more cases, in a second operating mode (e.g., dynamic determination), the WTRU may determine authorized resources from one or more authorized resources based on one or more of the following: gNB instructions, WTRU requests / reports, or a combination of gNB instructions and WTRU requests / reports.

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

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

[0135] In one or more cases, a WTRU may receive instructions for authorized resources based on instructions for frequency and / or time resources. For example, a WTRU may consist of a first authorized resource and a second authorized resource in the configured time resources. The first authorized resource in the configured time resources may be located in, for example, a first set of subbands. The second authorized resource may be located in a second set of subbands. A WTRU may receive instructions for frequency subbands / resources based on its configuration. A WTRU may receive instructions for a set of subbands, for example, via one or more of DCI, MAC CE, and RRC. If a WTRU receives instructions for a set of subbands, it may determine the first authorized resource. If a WTRU receives instructions for a second set of subbands, it may determine the second authorized resource.

[0136] In one or more cases, a WTRU may receive instructions for authorized resources based on instructions for TCI states, CRIs, and / or SRIs. For example, a WTRU may consist of a first TCI state, CRI, and / or SRI, and a second TCI state, CRI, and / or SRI. The first TCI state, CRI, and / or SRI may be associated with, for example, a first authorized resource. The second TCI state, CRI, and / or SRI may be associated with, for example, a second authorized resource. A WTRU may receive instructions for TCI states, CRIs, and / or SRIs (for example, the first TCI state, CRI, and / or SRI, or the second TCI state, CRI, and / or SRI) via, for example, one or more of DCI, MAC CE, and RRC. If the WTRU receives a first TCI state, CRI, and / or SRI instruction, the WTRU may determine a first authorized resource. If the WTRU receives a second TCI state, CRI, and / or SRI instruction, the WTRU may determine a second authorized resource.

[0137] In one or more cases, a WTRU may receive instructions for an authorized resource based on a PDCCH transmission in a dedicated CORESET. For example, a WTRU may consist of a first CORESET associated with a first authorized resource and a second CORESET associated with a second authorized resource. In another example, a WTRU may consist of a first CORESET associated with a first authorized resource. In yet another example, a WTRU may consist of a second CORESET associated with a second authorized resource. When a WTRU receives a PDCCH via the first CORESET, the WTRU may determine the first authorized resource. When a WTRU receives a PDCCH via the second CORESET, the WTRU may determine the second authorized resource.

[0138] In one or more cases, the WTRU may determine the permitted resource from one or more of the permitted resources based on the gNB instructions. The WTRU may determine the permitted resource based on one or more of the following: priority, modulation and coding scheme, transport block size, number of space layers, number of transport blocks, number of iterations and / or iteration 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.

[0139] In one or more cases, a WTRU may use, receive, and / or consist of one or more operating modes for an authorized resource. For example, one or more operating modes may be determined based on using, switching to, and / or avoiding one or more of the authorized resources. A WTRU may receive instructions for authorized resources and / or their respective operating modes. In one example, a WTRU may decide to use and / or switch to an indicated authorized resource in a first operating mode. In another example, a WTRU may decide to avoid an indicated authorized resource in a second operating mode. For example, a WTRU may decide to avoid an indicated authorized resource, for example, by revoking a grant.

[0140] In one or more cases, the use, avoidance, and / or prevention of one or more permitted resources may be based on one or more of the following: reports from potential victim WTRUs and / or reports from aggressor WTRUs. For example, a WTRU may decide to use, avoid, and / or prevent one or more permitted resources based on a report from a potential victim WTRU. For example, one or more victim WTRUs may sense and / or measure the channel or interference (e.g., CLI) quality in one or more permitted resources. One or more victim WTRUs may each determine that the measured amount is below and / or above their respective thresholds. One or more potential victim WTRUs may report and / or send a request to the WTRU to avoid permitted resources that have channel quality below the threshold and / or interference levels above their respective thresholds. A WTRU may decide to use, avoid, and / or prevent one or more permitted resources based on a report from aggressor WTRUs. In one example, one or more aggressor WTRUs may sense and / or measure channel or interference (e.g., CLI) quality on one or more permitted resources. One or more aggressor WTRUs may compare their measurements to their respective thresholds. One or more potential aggressor WTRUs may determine that channel and / or signal transmission and / or reception on the sensed permitted resources could cause interference (e.g., CLI) on a potential victim WTRU. Thus, one or more potential aggressor WTRUs may report and / or send requests to the WTRUs to circumvent their respective permitted resources.

[0141] In one or more cases, in a second operating mode (e.g., dynamic decision), the WTRU may, based on the WTRU request, determine which resources to use from one or more of the permitted resources. For example, the WTRU may request to use, avoid, and / or switch to a permitted resource. The WTRU may decide to use and / or avoid one or more of the permitted resources based on one or more of the following: the WTRU senses and / or measures interference in one or more of the permitted resources; the potential aggressor WTRU senses and / or measures interference (CLI) in one or more of the permitted resources; and the potential aggressor WTRU receives a trigger (e.g., based on one or more events) to sense and / or measure channel and / or interference quality in one or more of the permitted resources.

[0142] A WTRU may decide to use and / or avoid one or more of the permitted resources based on the fact that the WTRU has sensed and / or measured interference in one or more of the permitted resources. For example, a WTRU may use non-zero power CSI-RS (e.g., NZP-CSI-RS) and / or zero power CSI-RS (e.g., ZP-CSI-RS) as interference measurement resources (IMR). In one example, a WTRU may sense and / or measure CLI based on CLI-RSSI and / or SRS-RSRP. In another example, alternatively or in conjunction, a WTRU may measure CLI based on L1-CLI-RSSI. If the measured interference (e.g., CLI) is higher than the respective threshold in one or more of the permitted resources, the WTRU may request to use and / or switch to a different set of one or more permitted resources. WTRU may require the use and / or switching to a different set of one or more permitted resources where the measured interference (e.g., CLI) is below the respective threshold.

[0143] A WTRU may decide to use and / or avoid one or more of the permitted resources based on the fact that a potential aggressor WTRU has sensed and / or measured interference (e.g., CLI). A potential aggressor WTRU may sense and / or measure interference in one or more of the permitted resources. For example, a potential aggressor WTRU may use NZP-CSI-RS and / or ZP-CSI-RS for IMR. In another example, a WTRU may sense and / or measure CLI based on CLI-RSSI and / or L1-CLI-RSSI. In one or more cases, channel and / or interference measurements may be based on periodic, semi-permanent, and / or aperiodic sensing and / or measurement. In another example, alternatively or in conjunction, a potential aggressor WTRU may be configured to receive SRS signals from one or more potential victim WTRUs and / or measure SRS-RSRP. In one example, if the measured SRS-RSRP is higher than the respective threshold, the potential aggressor WTRU may request the prevention and / or avoidance of the respective permitted resources. In another example, the potential victim WTRU may transmit beamformed SRS signals to the potential aggressor WTRU. In one or more cases, SRS-based measurements may be based on periodic, semi-permanent, and / or aperiodic sensing and / or measurement.

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

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

[0146] A WTRU may send a request to the gNB to use and / or switch to an authorized resource based on explicit signaling. A WTRU may send a request to the gNB based on explicit signaling, for example, via one or more of PUCCH, PUSCH, MAC CE, and PRACH. For example, a WTRU may consist of one or more authorized resources. A WTRU may request an authorized resource from one or more authorized resources based on its configuration. In one example, the instruction corresponding to the request may be one or more of the following: an instruction for the authorized index, and / or an instruction for a subband and / or frequency resource.

[0147] A WTRU may send a request to the gNB to use and / or switch to an authorized resource based on its associated uplink resource. In one example, a WTRU may consist of a first uplink resource associated with a first authorized resource. In another example, a WTRU may consist of a second uplink resource associated with a second authorized resource. In yet another example, a WTRU may consist of a first uplink resource associated with a first authorized resource and a second uplink resource associated with a second authorized resource. When a WTRU transmits an uplink signal over the first uplink, the WTRU and the gNB may determine the first authorized resource. When a WTRU transmits an uplink signal over the second uplink resource, the WTRU and / or the gNB may determine the second authorized resource. The uplink signal may be, for example, one or more of the following: a scheduling request, a HARQ ACK / NACK, and / or a PRACH.

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

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

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

[0151] WTRUs and gNBs may determine authorized resources based on a first channel and / or interference report and a second channel and / or interference report. For example, if the first channel quality of the first CSI report is less than or equal to the second channel quality of the second CSI report, WTRUs and gNBs may determine a second authorized resource. In another example, if the first channel quality is higher than the second quality, WTRUs and gNBs may determine a first authorized resource. The first and second channel qualities may be one or more of the following, but are not limited to, CQI, L1-RSRP, L1-SINR, etc. In another example, if the first interference quality of the first interference report is greater than or equal to the second interference quality of the second interference report, WTRUs and gNBs may determine a second authorized resource. In yet another example, if the first interference quality is lower than the second quality, WTRUs and gNBs may determine a first authorized resource. The first and second interference qualities may be one or more of the following, but are not limited to, CLI-RSSI, SRS-RSRP, L1-CLI-RSSI, etc.

[0152] The first and second configurations may be one or more of the following: CSI reporting configuration, CSI-RS resource, CSI-RS resource set, BWP and / or subband for CSI reporting. If there is one or more, the first and second configurations may be one or more of the following: SRS reporting configuration, SRS resource, SRS resource set, BWP and / or subband for SRS reporting. If there is one or more, the first and second configurations may be one or more of the following: CLI reporting configuration, CLI resource, CLI resource set, BWP and / or subband for CLI reporting. If there is one or more, the first and second configurations may be one or more of the following: CSI reporting configuration, CSI-RS resource, CSI-RS resource set, BWP and / or subband for CSI reporting, SRS reporting configuration, SRS resource, SRS resource set, BWP and / or subband for SRS reporting, CLI reporting configuration, CLI resource, CLI resource set, BWP and / or subband for CLI reporting.

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

[0154] In a second mode of operation (e.g., dynamic determination), the WTRU may determine an authorized resource from one or more authorized resources based on a combination of gNB instructions and WTRU reports / requests. In cases of one or more, a combination of gNB instructions and WTRU reports may be supported. For example, one or more of the following may apply: the WTRU may receive instructions from the gNB for one or more authorized resources; the WTRU may request one or more authorized resources from the gNB. For example, the WTRU may receive instructions for one or more authorized resources, for example, by instructing the gNB to provide a group of authorized resources. The WTRU may request an authorized resource from one or more authorized resources based on the instructions. For example, the WTRU may request an authorized resource from one or more authorized resources, for example, by one or more of the following: explicit signaling, associated uplink resources, channels and / or interference reporting. In another example, a WTRU may request one or more authorized resources from a gNB through one or more means, such as explicit signaling, associated uplink resources, channels, and / or interference reporting. Based on the request, the WTRU may receive a request for one of the authorized resources among the one or more authorized resources.

[0155] In one or more cases, the WTRU may consist of counters and / or timers for switching to permitted resources. The WTRU may use, receive, and / or consist of counters and / or timers for switching to one or more of the permitted resources. In one example, the WTRU may be configured to use one or more of the permitted resources, as well as counters and / or timers. In another example, the WTRU may be configured to bypass one or more of the permitted resources, as well as counters and / or timers.

[0156] A WTRU may switch from a first authorized resource to a second authorized resource based on a decision. For example, a WTRU may switch from a first authorized resource to a second authorized resource based on a decision in response to a gNB instruction and / or WTRU request. A WTRU may apply a counter after a decision, for example. For example, a WTRU may increment the value of a counter by a certain number (e.g., by 1) when it transmits and / or receives one or more channels and / or signals. If 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, the maximum value of the counter. If 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 examples, the initial value of the counter may be zero. In some cases, the counter may be started and / or reset when the WTRU switches authorized resources. In some cases, the counter and threshold may be predefined. In some cases, counters and thresholds may be indicated, for example, via MAC CE and / or DCI. In some cases, counters and thresholds may be RRC configured. In some cases, counters and thresholds may be predefined, indicated, and / or RRC configured.

[0157] A WTRU may switch from a first authorized resource to a second authorized resource based on a decision. For example, a WTRU may switch from a first authorized resource to a second authorized resource based on a decision in response to a gNB instruction and / or WTRU request. A WTRU may apply a timer after the decision, for example. In one example, if the timer has not expired, the WTRU may use the second authorized resource. In another example, if the timer has expired, the WTRU may switch from the second authorized resource to the first authorized resource. In some cases, a timer may be started and / or initiated when the WTRU switches authorized resources. In some cases, a timer may be predefined. In some cases, a timer may be instructed, for example, via MAC CE and / or DCI. In some cases, a timer may be RRC configured. In some cases, a timer may be predefined, instructed, and / or RRC configured.

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

[0159] A WTRU may be configured to prevent band-edge CLI. A WTRU (e.g., a potential aggressor WTRU) may determine and / or receive an indication that the WTRU is causing interference. For example, a WTRU may determine and / or receive an indication based on gNB indications and / or WTRU sensing / measurements. A WTRU may determine and / or receive an indication that the WTRU is causing interference (e.g., CLI) to one or more victim WTRUs (e.g., band-edge CLIs) in one or more of the configured subbands. Therefore, the WTRU may decide to take preventive action to reduce the interference. In one or more cases, a WTRU may decide to take preventive action based on gNB indications and / or WTRU requests based on sensing and / or measurements.

[0160] A WTRU may be configured to switch from a first authorized resource to a second authorized resource, or may require such a switch. For example, the second authorized resource may contain a larger data allocation. Thus, interference (e.g., band-edge CLI) may be reduced due to the larger BWP / subbands contained in the second authorized resource.

[0161] The WTRU may determine, use, and / or configure a first power-saving / reduced power mode for a first authorized resource. In one or more cases, the WTRU may determine, use, and / or configure a second power-saving / reduced power mode for a second authorized resource. In one or more cases, the WTRU may determine, use, and / or configure a first power-saving / reduced power mode for a first authorized resource and a second power-saving / reduced power mode for a second authorized resource. The WTRU may be configured and determined to operate and / or use one or more power-saving / reduced power modes when one or more authorized resources are in use. For example, the first power-saving / reduced power mode (e.g., WTRU power-saving mode) may be a normal mode in which the WTRU can transmit and / or receive signals on one or more of the authorized resources. A WTRU may transmit and / or receive signals on one or more of the authorized resources, based on the configuration of each authorized resource. For example, a first configuration for a first authorized resource may indicate the WTRU transmit and / or receive behavior on the first authorized resource. That is, based on the first configuration of the first authorized resource, the WTRU may determine the transmit and / or receive behavior on the first authorized resource. In another example, a second configuration for a second authorized resource may indicate the WTRU transmit and / or receive behavior on the second authorized resource. That is, based on the second configuration of the second authorized resource, the WTRU may determine the transmit and / or receive behavior on the second authorized resource. Therefore, authorized resources for power saving and / or reduced power may not be associated. In one or more cases, a second power saving and / or reduced power mode may be a power saving and / or reduced power mode in which the WTRU transmits and / or receives signals on the first authorized resource. A WTRU may transmit / receive signals on a first authorized resource based, for example, on one or more conditions in each authorized resource (e.g., interference, CLI, band-edge CLI).

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

[0163] A WTRU may be configured for CLI sensing and / or measurement based on directional SRS-RSRP. In one example, a WTRU may be configured for sensing and / or measuring interference, and / or for SRS reception and measurement, and / or for receiving signaling indicating one or more TCI states. Interference may include, for example, CLI, L1-CLI-RSSI, SRS-RSRP, etc. In one or more cases, the signaling indicating one or more TCI states may consist of DCI, MAC CE, and / or RRC. For example, a WTRU may receive, sense, and / or measure each reference signal using at least one spatial domain filter. In one example, a WTRU may receive TCI states and / or SRS resource indicators (SRIs) to measure each 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 victim WTRU) may determine and / or be configured to use a spatial filter. The spatial filter may be, for example, the same spatial filter used to receive the reference signal set indicated by the TCI state for each CORESET that the WTRU uses to monitor the PDCCH. In another example, a WTRU (e.g., a potential aggressor WTRU) may determine and / or be configured to use a spatial filter to measure the potential effects and / or interference that the spatial filter may cause. For example, a WTRU may determine and / or be configured to use a spatial filter to measure the potential effects and / or interference that the spatial filter may cause 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 measurement to the gNB.

Claims

1. A wireless transmitter / receiver unit (WTRU), Transceiver and, The processor comprises, The transceiver receives configuration information indicating a plurality of subbands for crosslink interference (CLI) measurements and corresponding resources for performing CLI measurements for each of the plurality of subbands. The transceiver receives downlink control information indicating a resource associated with a first reference subband among the plurality of subbands. Using the corresponding resources for performing the CLI measurement on the first reference subband, perform the CLI measurement on the first reference subband. Based on the determination that the CLI measurement for the first reference subband is greater than the threshold, the CLI measurement for at least one other subband is performed using the corresponding resources for performing the CLI measurement for at least one other subband among the plurality of subbands. A WTRU is configured to send an instruction via the transceiver that the CLI measurement for the first reference subband is greater than the threshold.

2. The aforementioned processor, The lowest measured CLI among the multiple measured CSIs corresponding to the multiple subbands is determined, and the lowest measured CLI is associated with the second subband among the multiple subbands. The WTRU according to claim 1, configured to send a request via the transceiver for the WTRU to switch to using the second subband associated with the lowest measured CLI for transmission or reception.

3. The WTRU according to claim 1, wherein the corresponding resource for performing the CLI measurement includes one or more of the following: 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).

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

5. The WTRU according to claim 4, wherein the processor is configured to perform the CLI measurement for the first reference subband based on the number of Hybrid Auto Retransmission Request (HARQ) Negative Responses (NACKs) sent by the WTRU for transmission in the first reference subband exceeding a second threshold.

6. The WTRU according to claim 1, wherein the processor is configured to perform one or more of the following for performing the CLI measurement: a first layer (L1)-CLI reference signal intensity indicator (RSSI) measurement, a subband unit CLI measurement, or a delta CLI measurement.

7. The WTRU according to claim 1, wherein the processor is configured to send scheduling requests via the transceiver to request resources for CLI reporting.

8. The WTRU according to claim 1, wherein the CLI measurement includes overlapping CLI, partially overlapping CLI, or non-overlapping subband CLI.

9. The WTRU according to claim 1, wherein the downlink control information includes a downlink assignment indicating the first reference subband for scheduling a physical downlink shared channel (PDSCH).

10. The WTRU according to claim 1, wherein the processor is configured to perform the CLI measurement for the first reference subband based on explicit instructions from the network.

11. A method performed by a wireless transmit / receive unit (WTRU), the method comprising receiving configuration information indicating a plurality of subbands for crosslink interference (CLI) measurements and corresponding resources for performing CLI measurements for each of the plurality of subbands, Receiving downlink control information indicating a resource associated with a first reference subband among the plurality of subbands, Performing a CLI measurement on the first reference subband using the corresponding resources for performing the CLI measurement on the first reference subband, Based on the determination that the CLI measurement for the first reference subband is greater than a threshold, the CLI measurement for at least one other subband is performed using the corresponding resources for performing the CLI measurement for at least one other subband among the plurality of subbands, A method comprising sending an instruction that the CLI measurement for the first reference subband is greater than the threshold.

12. Determining the lowest measured CLI among a plurality of measured CSIs corresponding to the plurality of subbands, wherein the lowest measured CLI is associated with a second subband among the plurality of subbands. The method according to claim 11, further comprising sending a request for the WTRU to switch to using the second subband associated with the lowest measured CLI for transmission or reception.

13. The method according to claim 11, wherein the corresponding resource for performing the CLI measurement includes one or more of the following: zero-power channel state information reference signals (ZP-CSI-RS), non-zero-power channel state information reference signals (NZP-CSI-RS), or sounding reference signals (SRS).

14. The method according to claim 13, wherein the CLI measurement for the first reference subband is performed based on the number of downlink data reception failures for the first reference subband exceeding a first threshold.

15. The method according to claim 14, wherein the CLI measurement for the first reference subband is performed based on the number of Hybrid Automatic Retransmission Request (HARQ) Negative Responses (NACKs) sent by the WTRU for transmission in the first reference subband exceeding a second threshold.

16. The method according to claim 11, further comprising performing one or more of the following in order to perform the CLI measurement: a first layer (L1)-CLI reference signal intensity indicator (RSSI) measurement, a subband unit CLI measurement, or a delta CLI measurement.

17. The method according to claim 11, further comprising sending a scheduling request to request resources for CLI reporting.

18. The method according to claim 11, wherein the CLI measurement includes overlapping CLI, partially overlapping CLI, or non-overlapping subband CLI.

19. The method according to claim 11, wherein the downlink control information includes a downlink assignment indicating the first reference subband for scheduling a physical downlink shared channel (PDSCH).

20. The method according to claim 11, wherein the CLI measurement for the first reference subband is performed based on explicit instructions from the network.

Images