[go: up one dir, main page]

WO2025165819A1 - Procédés, architectures, appareils et systèmes de mesure d'interférence de liaison croisée réactive dans un multiplexage en duplex intégral sans chevauchement de sous-bande et multiplexage par répartition dynamique dans le temps - Google Patents

Procédés, architectures, appareils et systèmes de mesure d'interférence de liaison croisée réactive dans un multiplexage en duplex intégral sans chevauchement de sous-bande et multiplexage par répartition dynamique dans le temps

Info

Publication number
WO2025165819A1
WO2025165819A1 PCT/US2025/013515 US2025013515W WO2025165819A1 WO 2025165819 A1 WO2025165819 A1 WO 2025165819A1 US 2025013515 W US2025013515 W US 2025013515W WO 2025165819 A1 WO2025165819 A1 WO 2025165819A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
resources
dmrs
cli
cross
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/013515
Other languages
English (en)
Inventor
Nazli KHAN BEIGI
Jonghyun Park
Paul Marinier
Moon Il Lee
Janet Stern-Berkowitz
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025165819A1 publication Critical patent/WO2025165819A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present disclosure is generally directed to the fields of communications, software and encoding, including methods, architectures, apparatuses, and systems directed to reactive crosslink interference (CLI) measurement in sub-band non-overlapping full duplex (SBFD) and dynamic time division duplexing (TDD).
  • CLI reactive crosslink interference
  • SBFD sub-band non-overlapping full duplex
  • TDD dynamic time division duplexing
  • New radio (NR) duplex operation may allow to enhance conventional TDD operation.
  • Embodiments described herein have been designed with the foregoing in mind.
  • a first wireless transmit/receive unit (WTRU) is described.
  • the first WTRU may include circuitry including any of transmitter, a receiver, a processor, and a memory.
  • the first WTRU may be configured to receive cross-link configuration information indicating a plurality of cross-link interference (CLI) measurement resources.
  • the first WTRU may be configured to receive an indication to measure cross-link interference (CLI).
  • the indication may comprise scheduling information associated with a second WTRU.
  • the first WTRU may be configured to determine one or more CLI measurement resources from the plurality of CLI measurement resources based on the cross-link configuration information and the scheduling information associated with the second WTRU.
  • the one or more cross-link interference measurement resources may be determined from the plurality of cross-link interference measurement resources based on the one or more cross-link interference measurement resources any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) being at a range of the indicated scheduled resources.
  • the first WTRU may be configured to receive one or more reference signals associated with the second WTRU and to perform one or more CLI measurements in the one or more CLI measurement resources based on the one or more reference signals associated with the second WTRU.
  • the first WTRU may be configured to transmit report information indicating any of the one or more CLI measurements and the one or more CLI measurement resources.
  • a first method implemented in a first WTRU may include receiving cross-link configuration information indicating a plurality of crosslink interference (CLI) measurement resources.
  • the first method may include receiving an indication to measure cross-link interference (CLI).
  • the indication may comprise scheduling information associated with a second WTRU.
  • the first method may include determining one or more CLI measurement resources from the plurality of CLI measurement resources based on the cross-link configuration information and the scheduling information associated with the second WTRU.
  • the one or more cross-link interference measurement resources may be determined from the plurality of cross-link interference measurement resources based on the one or more cross-link interference measurement resources any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) being at a range of the indicated scheduled resources.
  • the first method may include receiving one or more reference signals associated with the second WTRU and performing one or more CLI measurements in the one or more CLI measurement resources based on the one or more reference signals associated with the second WTRU.
  • the first method may include transmitting report information indicating any of the one or more CLI measurements and the one or more CLI measurement resources.
  • a first WTRU may include circuitry including any of transmitter, a receiver, a processor, and a memory.
  • the first WTRU may be configured to receive cross-link configuration information indicating a plurality of cross-link interference (CLI) measurement resources.
  • the first WTRU may be configured to receive an indication to measure cross-link interference (CLI).
  • the indication may comprise scheduling information associated with a second WTRU.
  • the first WTRU may be configured to determine one or more CLI measurement resources from the plurality of CLI measurement resources based on the cross-link configuration information and the scheduling information associated with the second WTRU.
  • the first WTRU may be configured to receive one or more reference signals associated with the second WTRU and to perform one or more CLI measurements in the one or more CLI measurement resources based on the one or more reference signals associated with the second WTRU.
  • the first WTRU may be configured to perform an uplink transmission with a reduced transmission power based on the one or more CLI measurements performed in the one or more CLI measurement resources.
  • a second method implemented in a first WTRU may include receiving cross-link configuration information indicating a plurality of cross-link interference (CLI) measurement resources.
  • the second method may include receiving an indication to measure cross-link interference (CLI).
  • the indication may comprise scheduling information associated with a second WTRU.
  • the second method may include determining one or more CLI measurement resources from the plurality of CLI measurement resources based on the cross-link configuration information and the scheduling information associated with the second WTRU.
  • the second method may include receiving one or more reference signals associated with the second WTRU and performing one or more CLI measurements in the one or more CLI measurement resources based on the one or more reference signals associated with the second WTRU.
  • the second method may include performing an uplink transmission with a reduced transmission power based on the one or more cross-link interference measurements performed in the one or more cross-link interference measurement resources.
  • a first network element may include circuitry including any of transmitter, a receiver, a processor, and a memory.
  • the first network element may be configured to transmit to a first WTRU, cross-link interference configuration information indicating a plurality of cross-link interference measurement resources.
  • the first network element may be configured to transmit to the first WTRU, an indication to measure cross-link interference.
  • the indication may indicate scheduled resources for transmissions between a second WTRU and a second network element.
  • the first network element may be configured to receive from the first WTRU, report information indicating one or more cross-link interference measurements performed by the first WTRU in one or more cross-link interference measurement resources that may be any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) at a range of the indicated scheduled resources.
  • a third method implemented in a first network element may include transmitting to a first WTRU, cross-link interference configuration information indicating a plurality of cross-link interference measurement resources.
  • the third method may include transmitting to the first WTRU, an indication to measure cross-link interference.
  • the indication may indicate scheduled resources for transmissions between a second WTRU and a second network element.
  • the third method may include receiving from the first WTRU, report information indicating one or more cross-link interference measurements performed by the first WTRU in one or more cross-link interference measurement resources that may be any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) at a range of the indicated scheduled resources.
  • FIG. 1 A is a system diagram illustrating an example communications system
  • FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;
  • RAN radio access network
  • CN core network
  • FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;
  • FIG. 2 is a diagram illustrating an example of SBFD configuration in a TDD framework
  • FIG. 3 is a diagram illustrating an example of synchronization signal block (SSB) symbols overlapping with SBFD symbols.
  • SSB synchronization signal block
  • FIG. 4 is a diagram illustrating an example of intra-cell and inter-cell CLI
  • FIG. 5 is a diagram illustrating an example of CLI measurement and reporting based on DMRS in UL data
  • FIG. 6 is a diagram illustrating an example configuration for measuring CLI in DL subband based on DMRS in UL data
  • FIG. 7A and FIG. 7B are two diagrams illustrating two example configurations of aggressor WTRU and victim WTRU;
  • FIG. 8 is a diagram illustrating an example of table of parameters that may be included in a PHR configuration
  • FIG. 9 is a diagram illustrating an example of measurement based on the one or more DMRS in received DL;
  • FIG. 10 is a diagram illustrating an example method for CLI measurement and reporting based on DMRS, implemented in a first WTRU;
  • FIG. 11 is a diagram illustrating an example method for dynamic CLI mitigation based on DMRS-based CLI measurement, implemented in a first WTRU;
  • FIG. 12 is a diagram illustrating an example method for CLI measurement and reporting based on DMRS, implemented in a first network element; and [0026]
  • FIG. 13 is a diagram illustrating an example method for DMRS-based measurement based on scheduled downlink data, implemented in a WTRU.
  • the methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks.
  • An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.
  • FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA singlecarrier FDMA
  • ZT unique-word
  • DFT discrete Fourier transform
  • UW-OFDM unique word OFDM
  • resource block- filtered OFDM filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112.
  • the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE- Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (Wi-Fi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/114 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. IB is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other elements/peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/ detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122.
  • the WTRU 102 may employ MIMO technology.
  • the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), readonly 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.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134 and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity.
  • the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and/or augmented reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the elements/peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse fast fourier transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse fast fourier transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.
  • MAC medium access control
  • Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in
  • 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum
  • 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,
  • MTC meter type control/machine-type communications
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as
  • 802.1 In, 802.1 lac, 802.1 laf, and 802.1 lah include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 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. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • the available frequency bands which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.
  • FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPFs user plane functions
  • AMFs access and mobility management functions
  • the CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • AMF session management function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized by WTRUs 102a, 102b, 102c.
  • 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, services for MTC access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • the AMF 182a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP -based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, e.g., to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184a, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • base station may be used interchangeably to designate any network element such as e.g., a network element acting as a serving base station.
  • network may be used interchangeably to designate any network element such as e.g., a network element acting as a serving base station.
  • Embodiments described herein are not limited to gNBs and are applicable to any other type of base stations.
  • satisfying, failing to satisfy a condition, and configuring condition parameter(s) are described throughout embodiments described herein as relative to a threshold (e.g., greater, or lower than) a (e.g., threshold) value, configuring the (e.g., threshold) value, etc.
  • a threshold e.g., greater, or lower than
  • a (e.g., threshold) value e.g., configuring the (e.g., threshold) value
  • satisfying a condition may be described as being above a (e.g., threshold) value
  • failing to satisfy a condition may be described as being below a (e.g., threshold) value.
  • Embodiments described herein are not limited to threshold-based conditions. Any kind of other condition and param eter(s) (such as e.g., belonging or not belonging to a range of values) may be applicable to embodiments described herein.
  • (e.g., configuration) information may be described as received by a WTRU from the network, for example, through system information or via any kind of protocol message.
  • the same (e.g., configuration) information may be pre-configured in the WTRU (e.g., via any kind of pre-configuration methods such as e.g., via factory settings), such that this (e.g., configuration) information may be used by the WTRU without being received from the network.
  • the expression “the WTRU may be configured with a set of parameters” is equivalent or may be used interchangeably with “the WTRU may receive configuration information (e.g., from another network element (e.g., gNB)) indicating a set of parameters".
  • the expressions “the WTRU may report something”, and “the WTRU may be configured to report something”, is equivalent or may be used interchangeably with “the WTRU may transmit (e.g., reporting) information indicating something".
  • the expression “the WTRU may provide (/be provided) with a set of parameters (/something)” is equivalent or may be used interchangeably with “the WTRU may transmit (/receive) information indicating a set of parameters (/something)”.
  • “a” and “an” and similar phrases are to be interpreted as “one or more” and “at least one”.
  • any term which ends with the suffix "(s)” is to be interpreted as “one or more” and “at least one”.
  • the term “may” is to be interpreted as “may, for example”.
  • a symbol "/" (e.g., forward slash) may be used herein to represent “and/or”, where for example, "A/B” may imply “A and/or B”.
  • list of', set of and “one or more of may be used interchangeably.
  • identity and “identifier” may be used interchangeably to refer to how a network element (or a WTRU) may be identified.
  • an indication comprising scheduling information and an indication indicating scheduled resources may be used interchangeably.
  • a network element may refer to any kind of device including computing resources and networking capabilities, that may be connected to a network.
  • the terms network element and node may be used interchangeably.
  • a network element may be any kind of network infrastructure device and or a WTRU.
  • the architecture depicted at FIG. IB for a WTRU 102 may be applicable more generally to any kind of network element.
  • New radio (NR) duplex operation may allow to improve (e.g., conventional) TDD operation by enhancing UL coverage, improving capacity, reducing latency, and so forth.
  • the (e.g., conventional) TDD may be based on splitting the time domain between the uplink and downlink.
  • SBFD sub-band non-overlapping full duplex
  • FIG. 2 is a diagram illustrating an example of non-overlapping full duplex (SBFD) configuration in a time division duplexing (TDD) framework.
  • the configuration may include a DL slot 21, a set of SBFD slots 22, a flexible slot 23 and an UL slot 24.
  • SBFD cross-layer interferences
  • a first cell which may be referred to as (e.g., potential) aggressor cell
  • CLI cross-layer interferences
  • a second cell which may be referred to as (e.g., potential) victim gNBs and WTRUs
  • the UL transmission from first cell (e.g., aggressor) WTRUs may cause directional CLI at the second cell (e.g., victim) WTRUs.
  • FIG. 3 is a diagram illustrating an example of SSB symbols overlapping with SBFD symbols.
  • the CLI may be measured at the victim and/or aggressor WTRUs.
  • First UL and DL transmissions 311 occurring at a first cell 31 may create CLI with second UL and DL transmissions 322 occurring at a second cell 32.
  • CLI may comprise gNB to gNB CLI 33, gNB to WTRU CLI 34 and WTRU to WTRU CLI 35.
  • FIG. 4 is a diagram illustrating an example of intra-cell and inter-cell CLI.
  • a third WTRU 43 may operate in SBFD configuration and may be configured for DL reception.
  • the third WTRU 43 may experience two types of CLI: a first type of CLI (e.g., referred to as CLI1) from a first WTRU 41 in the serving cell, operating based on SBFD, that may be configured with UL transmission in UL SBs.
  • CLI1 first type of CLI
  • the second type of CLI (referred to as CLI2) from a second WTRU 42 in a neighbor cell, operating based on dynamic TDD (d-TDD), that may be configured with UL transmission in SBs that may overlap with DL sub-bands of the third WTRU 43.
  • the third WTRU 43 may perform WTRU-to-WTRU CLI measurement to identify the sources of interference.
  • WTRU-to-WTRU CLI measurement may be used for CLI mitigation in any of SBFD and d-TDD scenarios.
  • WTRU-to-WTRU CLI measurement may be based on SRS- RSRP and/or CLLRSSI measurements, where the former may be time consuming based on per- WTRU measurements and the latter may provide limited information on the source of the interference.
  • a demodulation reference signal may be associated with any of downlink and uplink channels, including PDSCH/PDCCH and PUSCH/PUCCH, respectively.
  • the DMRS may be used as a physical signal for downlink and uplink radio channel estimation e.g., for decoding PDSCH/PDCCH and PUSCH/PUCCH, respectively.
  • the downlink cell reference signal CRS
  • the DMRS may be used for decoding the corresponding physical channels.
  • Embodiments described herein may allow to improve resource utilization efficiency for WTRU-to-WTRU CLI measurements by reducing CLI measurement resource overhead.
  • reactive CLI measurement and reporting may be performed based on DMRS in UL or DL data that may be scheduled for another WTRU.
  • Duplicate DCI for dynamic resource indication for reactive CLI measurement may be performed.
  • dynamic CLI mitigation may be performed by power back-off at the aggressor WTRU based on CLI measurement performed based on DMRS in UL or DL data of victim WTRUs.
  • reactive CLI measurement and reporting may be performed based on DMRS in scheduled DL data.
  • the terms “aggressor” and “victim” are employed in embodiments described herein as a qualifier of any of a WTRU, a TRP and a cell to refer to a WTRU/gNB/cell that may be a source of a CLI (aggressor) or that may be disturbed by a CLI (victim).
  • a first WTRU may be configured with a (e.g., pilot) set of cross-link interference measurement (CL-IM) resources for measuring CLI based on UL DMRS signaling transmitted by (e.g., received from) other WTRUs (e.g., as part of other WTRUs’ PUSCH and/or PUCCH).
  • the first WTRU may receive indications on DMRS-based CLI measurement, including, for example, the type of CLI measurement and corresponding DMRS configurations.
  • CL-IM may be configured.
  • a first WTRU e.g., potential victim third WTRU 43 shown at FIG. 4
  • may receive configuration information (e.g., via any of RRC, MAC- CE, DCI) on (cross-link interference measurement) CL-IM resources for measuring inter-WTRU CLI.
  • the configuration information may include any of time and frequency for a set of (e.g., pilot) CL-IM resources.
  • the set of (e.g., pilot) CL-IM resources may be configured in one or more REs and symbols.
  • the CL-IM resources may be configured any of periodically, semi-persistently, and a-periodically.
  • the CL-IM resources may be in any of UL sub-bands, DL sub-bands, SBFD symbols and d-TDD symbols.
  • measurement may be triggered.
  • the first WTRU may receive an indication to measure and report CLI, where the indication may include (e.g., indicate) any of type of CLI measurement, a DMRS-based CLI enable, and a triggering indication.
  • a type of CLI measurement may indicate any of (i) DMRS-based CLI-RSRP, (ii) DMRS-based CLI-RSSI, (iii) SRS-RSRP, and (iv) CLI-RSSI.
  • the indication may include a (e.g., a DMRS-based CLI enable) flag indication to enable DMRS-based CLI measurement based on UL data from a second WTRU.
  • the WTRU may receive the indication to measure DMRS-based CLI via MAC-CE or DCI signaling for UL grants that may be semi-statically or dynamically, respectively, configured for a second WTRU.
  • the triggering indication e.g., DCI
  • the triggering indication may have (e.g., include, indicate) information on the reporting resources.
  • the indication may include one or more configuration information on the UL grant of a second WTRU (e.g., WTRU1/WTRU2) and the DMRS configuration and resources to be measured.
  • a second WTRU e.g., WTRU1/WTRU2
  • the configuration information may include any of an UL grant time allocation, an UL grant frequency allocation, a number of RBs configured for the UL grant, DMRS symbols, a DMRS position in frequency domain (REs), a DMRS type, a DMRS group, a DMRS length, a DMRS seed/pattern, and a DMRS CDM group, etc. for the PUSCH/PUCCH that may be scheduled for the second WTRU.
  • REs DMRS position in frequency domain
  • the configuration information may include (e.g., indicate) the beam direction, e.g., any of spatial filter, TCI-state, etc. for measuring the CLI (e.g., receiving beam direction of the third WTRU 43).
  • the beam direction may be associated with a first WTRU’s configured DL beam direction.
  • the beam direction may be indicated from a set of configured Rx beam directions.
  • CL-IM resources may be determined.
  • the first WTRU may determine the CL-IM resources based on any of a CLI measurement type and an UL grant/ schedule of the second WTRU.
  • the WTRU may select the resources for CLI measurement based on CL-IM resources in UL sub-band (e.g., to measure correlation-based RSRP based on DMRS). If the CLI measurement type is “DMRS-based CLL RSSI”, the WTRU may select the resources for CLI measurement based on CL-IM resources in DL sub-band (e.g., to measure the leakage/effect of the UL DMRS in DL sub-bands).
  • the first WTRU may determine the CL-IM resources based on the second WTRU’s UL grant/schedule.
  • the DMRS may be (e.g., received) in one or more first symbols and first REs. If a first CL-IM resource is (e.g., fully) included in the one or more first symbols (and e.g., first REs), the first WTRU may use (e.g., determine, select) the first CL-IM resource.
  • the first WTRU may use (e.g., select, determine) the second or third CL-IM resources. In such a case, the first WTRU may use scaling factors for determining the CLI based on the measurements.
  • measurement may be performed and reported.
  • the first WTRU may measure DMRS-based CLI in the determined CL-IM resources based on configured UL DMRS transmitted via (e.g., received from) the second WTRU.
  • the first WTRU may report (e.g., transmit report information indicating) the CL-IM resources used for the measurement.
  • the first WTRU may report (e.g., transmit report information indicating) the measured UL DMRS- based CLI.
  • the first WTRU may report an indication in case the measured CLI is higher or lower than a threshold (e.g., as part of the CSI, special SR, or along with NACK transmission). In case the gNB does not receive the indication, the gNB may expect that the CLI may be lower than the threshold and that the first/second WTRUs may not be causing strong CLI on the third WTRU.
  • a threshold e.g., as part of the CSI, special SR, or along with NACK transmission.
  • a first WTRU e.g., potential aggressor first/second WTRU 41, 42
  • the first WTRU may dynamically change or report the PHR based on the measured DMRS-based CLI e.g., as a CLI mitigation technique.
  • the first WTRU may receive one or more configuration information on CL-IM resources for measuring any of DMRS-based CLI-RSRP, CLI-RSSI, SINR, etc. based on one or more DMRSs that may be scheduled for a second WTRU (e.g., included in UL or DL data scheduled for a second WTRU, e.g., victim WTRU).
  • a second WTRU e.g., included in UL or DL data scheduled for a second WTRU, e.g., victim WTRU.
  • the first WTRU may receive an indication or trigger (e.g., from gNB or higher layers) to measure the DL or UL DMRS-based CLI-RSRP in the configured CL-IM resources.
  • the indication may include (e.g., indicate) any of a beam direction for measuring the CLI, information on the DMRS of the UL or DL signals/channels.
  • the first WTRU may receive the indication via any of MAC-CE, DCI, or a CLI measurement DCI.
  • dynamic WTRU-oriented CLI mitigation may be performed via changing or reporting PHR based on measurements.
  • the first WTRU may perform CLI mitigation for the next one or more UL transmissions based on a configured option (e.g., via any of RRC, MAC-CE, DCI), for example, during a configured time duration or until new commands may be received from the gNB.
  • the WTRU may determine the condition to trigger CLI mitigation based on a combination of the measured UL and/or DL DMRS-based CLI-RSRP and corresponding thresholds.
  • any of (1) UL power backoff, (2) cap the UL power to a (e.g., max) value, and (3) Power backoff of the PCMAX may apply.
  • the first WTRU may be configured to apply one or more configured (e.g., via any of RRC, MAC-CE, DCI) power backoff or reduced power rates or policies.
  • the power backoff or reduced power policies may depend on the measured DL and/or UL DMRS-based CLI-RSRP and one or more thresholds (configured via any of RRC, MAC-CE, DCI).
  • the first WTRU may be configured to reduce the UL power to a configured (e.g., max) value.
  • the first WTRU may indicate the changes to the UL Tx power by triggering the transmitting and reporting of PHR (e.g., via MAC-CE) to the gNB.
  • a (e.g., new) trigger for transmitting and reporting of PHR may be based on measured CLI and/or when the first WTRU has modified PCMAX value based on CLI.
  • CLLeffected PCMAX may be reported as part of (e.g., included in) PHR reporting.
  • the first WTRU may restore the PHR and may send an indication that the PCMAX may be increased (e.g., again).
  • PCMAX may be backoff/decreased.
  • CLI is strong (e.g., above a threshold)
  • PCMAX may be increased, etc.
  • the measured CLI may be reported. If the measured DL or UL DMRS- based CLI-RSRP is higher than a first or a second threshold, respectively, the first WTRU may report the measured CLI-RSRP e.g., to the gNB (e.g., via any of UCI, MAC-CE, etc.). The gNB may consider the (e.g., potential) aggressor and victim WTRUs in scheduling procedure. For example, the gNB may adapt the scheduling procedure for the first and second WTRUs based on measured CLI being reported for the first and second WTRUs.
  • a WTRU may receive DCI configuring "DMRS-based SINR measurement" based on DMRS received as part of a configured/ scheduled DL data that may be scheduled for the third WTRU 43.
  • the third WTRU 43 may perform CLI and SINR measurements based on the scheduled/configured PDCCH/PDSCH DMRS.
  • the measurement may be performed on resources configured to receive DL data; being different from the (e.g., legacy) CLI/SINR measurements that may be performed on separately configured and transmitted on NZP/ZP CSLRS, CSLIM resources.
  • a WTRU may receive one or more dynamic or configured assignments to receive one or more PDSCH.
  • the configurations may include information on one or more DMRS resources that may be included in the configured PDSCH.
  • the DMRS configuration (e.g., information) may include any of DMRS symbols, a DMRS position in frequency domain (e.g., REs), a DMRS type, a group, a length, a seed, a CDM group, etc.
  • the WTRU may receive an indication to (enable to) measure CLI and/or SINR based on the configured DMRS resources of the PDSCH.
  • the indication may include the number of DMRS resources and information on the DMRS resources to be used for the (e.g., configured) CLI and/or SINR measurement.
  • the indication may include one or more of time-windows, frequency-windows, and/or DMRS REs (e.g., exact DMRS REs) to be used for DMRS-based CLI and/or SINR measurement.
  • the WTRU may determine the number of DMRS resources and which ones to be used for measurement (e.g., for the purpose of accuracy). In such a case, the WTRU may report the number of DMRS that may be used and the ones that may be used as part of the report. [0128] In an example, the WTRU may measure any of RSRP and RSSI corresponding to the received DMRS (e.g., DMRS-based RSRP and DMRS-based RSSI, respectively) received along with the configured PDSCH.
  • RSRP and RSSI corresponding to the received DMRS
  • SINR RSRP / (RSSI - RSRP)
  • RSSI may include DMRS-based received power in addition to noise and interference (e.g., CLI).
  • the WTRU may report any of the measured DMRS-based RSRP, the measured DMRS-based RSSI, the calculated SINR, etc. (e.g., as part of any of CLI reporting, CSI reporting, SR, HARQ-ACK, etc ).
  • the WTRU may report a flag indication in case any of the measured RSRP, SINR, etc. are higher or lower than corresponding thresholds (e.g., via any of UCI, MAC-CE, or along with NACK transmission in an enhanced (e.g., modified) codebook).
  • ‘a’ and ‘an’ and similar phrases are to be interpreted as ‘one or more’ and ‘at least one’.
  • any term which ends with the suffix ‘(s)’ is to be interpreted as ‘one or more’ and ‘at least one’.
  • the term ‘may’ is to be interpreted as ‘may, for example’.
  • a symbol 7’ (e.g., forward slash) may be used herein to represent ‘and/or’, where for example, ‘A/B’ may imply ‘A and/or B’.
  • a WTRU may transmit or receive a physical channel or reference signal according to at least one spatial domain filter.
  • the term “beam” may be used to refer to a spatial domain filter.
  • the WTRU may transmit a physical channel or signal using the same spatial domain filter as the spatial domain filter used for receiving an RS (such as CSLRS) or a SS block.
  • the WTRU transmission may be referred to as “target”, and the received RS or SS block may be referred to as “reference” or “source”.
  • the WTRU may be said to transmit the target physical channel or signal according to a spatial relation with a reference to such RS or SS block.
  • the WTRU may transmit a first physical channel or signal according to the same spatial domain filter as the spatial domain filter used for transmitting a second physical channel or signal.
  • the first and second transmissions may be referred to as “target” and “reference” (or “source”), respectively.
  • the WTRU may be said to transmit the first (target) physical channel or signal according to a spatial relation with a reference to the second (reference) physical channel or signal.
  • a spatial relation may be implicit, e.g., configured by RRC and/or signaled by any of MAC CE and DCI.
  • a WTRU may implicitly transmit PUSCH and DMRS of PUSCH according to the same spatial domain filter as an SRS indicated by an SRI indicated in DCI and/or configured by RRC.
  • a spatial relation may be configured by RRC for an SRS resource indicator (SRI) and/or signaled by MAC CE for a PUCCH. Such spatial relation may be referred to as a “beam indication”.
  • the WTRU may receive a first (target) downlink channel or signal according to the same spatial domain filter or spatial reception parameter as a second (reference) downlink channel or signal.
  • a first (target) downlink channel or signal may exist between a physical channel such as PDCCH or PDSCH and its respective DMRS.
  • the WTRU is configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports.
  • QCL quasi-colocation
  • Such association may be configured as a transmission configuration indicator (TCI) state.
  • TCI transmission configuration indicator
  • a WTRU may be indicated an association between a CSI-RS or SS block and a DMRS by an index to a set of TCI states configured by RRC and/or signaled by MAC CE. Such indication may also be referred to as a “beam indication”.
  • a transmission and reception point may be interchangeably used with one or more of (i) transmission point (TP), (ii) reception point (RP), (iii) radio remote head (RRH), (iv) distributed antenna (DA), (v) base station (BS), (vi) a sector (of a BS), and (vii) a cell (e.g., a geographical cell area served by a BS), which (e.g., all) may be applicable to embodiments described herein.
  • TP transmission point
  • RP reception point
  • RRH radio remote head
  • DA distributed antenna
  • BS base station
  • BS base station
  • BS base station
  • a sector of a BS
  • a cell e.g., a geographical cell area served by a BS
  • Other types of reference signals may be applicable to embodiments described herein Any other types of transmission and reception points may be applicable to embodiments described herein.
  • multi-TRP may be interchangeably used with one or more of MTRP, M-TRP, and multiple TRPs. Any types of multiple transmission and reception points may be applicable to embodiments described herein.
  • sub-band and/or “sub-band” may be used to refer to a frequency-domain resource and may be characterized by (e.g., associated with) at least one of (i) a set of resource blocks (RBs), (ii) a set of resource block sets (RB sets), e.g. in case of a carrier with intra-cell guard bands, (iii) a set of interlaced resource blocks, (iv) a bandwidth part, or portion thereof, and (v) a carrier, or portion thereof.
  • RBs resource blocks
  • RB sets resource block sets
  • a sub-band may be characterized by (e.g., associated with) a starting RB and a number of RBs for a set of contiguous RBs within a bandwidth part.
  • a sub- band may be defined by (e.g., associated with) the value of a frequency-domain resource allocation field and bandwidth part index.
  • the term “XDD” may be used to refer to a sub-band- wise duplex (e.g., either UL or DL being used per sub-band) and may be characterized by (e.g., associated with) at least one of (i) cross division duplex (e.g., sub-band-wise FDD within a TDD band), (ii) sub-band non-overlapping full duplex (SBFD), (iii) sub-band-based full duplex (e.g., full duplex as (e.g., both) UL and DL may be used/mixed on a symbol/slot, and (e.g., either) UL or DL may be used per sub-band on the symbol/slot), (iv) frequency-domain multiplexing (FDM) of DL/UL transmissions within a TDD spectrum, (v) a full duplex other than a same-frequency (e.g., spectrum sharing, sub-band-wise-overlapped
  • dynamic(/flexible) TDD may be used to refer to a TDD system/cell which may dynamically (and/or flexibly) change/adjust/switch a communication direction (e.g., any of a downlink, an uplink, a sidelink, etc.) on a time instance (e.g., any of slot, symbol, subframe, and the like).
  • a communication direction e.g., any of a downlink, an uplink, a sidelink, etc.
  • time instance e.g., any of slot, symbol, subframe, and the like.
  • any of a component carrier(CC) and a bandwidth part (BWP) may have one (e.g., single) type among ‘D’, ‘U’, and ‘F’ on a symbol/slot, based on an indication by a group- common (GC)-DCI (e.g., format 2 0) comprising a slot format indicator (SFI), and/or based on tdd-UL-DL-config-common/dedicated configurations.
  • GC group- common
  • SFI slot format indicator
  • a first gNB (e.g., cell, TRP) employing dynamic/flexible TDD may transmit a downlink signal to a first WTRU being communicated/associated with the first gNB based on a first SFI and/or tdd-UL-DL-config configured/indicated by the first gNB
  • a second gNB (e.g., cell, TRP) employing dynamic/flexible TDD may receive an uplink signal transmitted from a second WTRU being communicated/associated with the second gNB based on a second SFI and/or tdd-UL-DL-config configured/indicated by the second gNB.
  • the first WTRU may determine that the reception of the downlink signal may be being interfered by the uplink signal, where the interference caused by the uplink signal may refer to a WTRU-to-WTRU cross-layer interference (CLI).
  • CLI cross-layer interference
  • a WTRU may report a subset of channel state information (CSI) components.
  • CSI components may correspond to any of a CSLRS resource indicator (CRI), a SSB resource indicator (SSBRI), an indication of a panel used for reception at the WTRU (such as any of a panel identity and a group identity), measurements such as any of Ll-RSRP, Ll-SINR taken from any of SSB and CSI-RS (e.g., any of cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel state information such as any of a rank indicator (RI), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a layer index (LI), and the like.
  • CRI CSLRS resource indicator
  • SSBRI SSB resource indicator
  • PMI precoding matrix indicator
  • LI layer index
  • a WTRU may receive a synchronization signal/physical broadcast channel (SS/PBCH) block.
  • the SS/PBCH block may include any of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and physical broadcast channel (PBCH).
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • PBCH physical broadcast channel
  • the WTRU may any of monitor, receive, or attempt to decode an SSB during any of initial access, initial synchronization, radio link monitoring (RLM), cell search, cell switching, and so forth.
  • RLM radio link monitoring
  • a WTRU may measure and report the channel state information (CSI).
  • the CSI for a connection mode (e.g., each connection mode) may include or be configured with one or more of (i) a CSI report configuration, (ii) a CSI-RS resource set, and (iii) NZP CSI-RS resources.
  • a CSI report configuration may include one or more of a (i) CSI report quantity, e.g., any of (a) channel quality indicator (CQI), (b) rank indicator (RI), (c) precoding matrix indicator (PMI), (d) CSI-RS resource indicator (CRI), (e) layer indicator (LI), etc., (ii) a CSI report type, e.g., aperiodic, semi persistent, periodic, (iii) a CSI report codebook configuration, e.g., Type I, Type II, Type II port selection, etc., (iv) a CSI report frequency.
  • a CSI report quantity e.g., any of (a) channel quality indicator (CQI), (b) rank indicator (RI), (c) precoding matrix indicator (PMI), (d) CSI-RS resource indicator (CRI), (e) layer indicator (LI), etc.
  • a CSI report type e.g., aperiodic, semi persistent, periodic
  • a CSI-RS resource set may include one or more of the following CSI resource settings: (i) NZP-CSI-RS resource for channel measurement, (ii) NZP-CSLRS resource for interference measurement, and (iii) CSI-IM resource for interference measurement.
  • NZP CSI-RS resources may include one or more of (i) a NZP CSI-RS resource ID, (ii) a periodicity and an offset, (iii) QCL Info and TCI-state, (iii) resource mapping (e.g., associations), e.g., number of ports, density, CDM type, etc.
  • resource mapping e.g., associations
  • a WTRU may indicate, determine, or be configured with one or more reference signals.
  • the WTRU may any of monitor, receive, and measure one or more parameters based on the respective reference signals. For example, one or more of the following may apply.
  • the following parameters are non-limiting examples of the parameters that may be included in reference signal(s) measurements. One or more of these parameters may be included.
  • Reference signal(s) measurements including other parameters may be applicable to embodiments described herein.
  • SS reference signal received power may be measured based on the synchronization signals (e.g., demodulation reference signal (DMRS) in PBCH or SSS). It may be (e.g., defined as) the linear average over the power contribution of the resource elements (RE) that may carry the respective synchronization signal.
  • DMRS demodulation reference signal
  • RE resource elements
  • CSI-RSRP may be measured based on the linear average over the power contribution of the resource elements (RE) that may carry the respective CSI-RS.
  • the CSI-RSRP measurement may be configured within measurement resources for the configured CSI-RS occasions.
  • SS signal to interference and noise ratio may be measured based on the synchronization signals (e.g., DMRS in PBCH or SSS). It may be (e.g., defined as) the linear average over the power contribution of the resource elements (RE) that may carry the respective synchronization signal divided by the linear average of the noise and interference power contribution.
  • the noise and interference power measurement may be accomplished based on resources configured by higher layers.
  • CSI-SINR may be measured based on the linear average over the power contribution of the resource elements (RE) that may carry the respective CSI-RS divided by the linear average of the noise and interference power contribution.
  • RE resource elements
  • the noise and interference power measurement may be accomplished based on resources configured by higher layers. Otherwise, the noise and interference power may be measured based on the resources that may carry the respective CSI-RS.
  • Received signal strength indicator may be measured based on the average of the (e.g., total) power contribution in configured OFDM symbols and bandwidth.
  • the power contribution may be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, and so forth).
  • Cross-layer interference received signal strength indicator may be measured based on the average of the (e.g., total) power contribution in configured OFDM symbols of the configured time and frequency resources.
  • the power contribution may be received from different resources (e.g., any of cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, and so forth).
  • Sounding reference signals RSRP may be measured based on the linear average over the power contribution of the resource elements (RE) that may carry the respective SRS.
  • SS-RSRQ Sounding reference signals
  • Secondary synchronization signal reference signal received quality may be measured based on measurements on the reference signal received power (SS-RSRP) and received signal strength (RSSI).
  • SS-RSRQ may be calculated as the ratio of N*SS-RSRP / NR carrier RSSI, where N may be determined based on the number of resource blocks that may be in the corresponding NR carrier RSSI measurement bandwidth. As such, the measurements to be used in the numerator and denominator may be over the same set of resource blocks.
  • CSI reference signal received quality may be measured based on measurements on the reference signal received power (CSI-RSRP) and received signal strength (RSSI).
  • CSI-RSRP reference signal received power
  • RSSI received signal strength
  • the SS-RSRQ may be calculated as the ratio of N*CSI-RSRP / CSI-RSSI, where N may be determined based on the number of resource blocks that may be in the corresponding CSI-RSSI measurement bandwidth.
  • the measurements to be used in the numerator and denominator may be over the same set of resource blocks.
  • a property of a grant or assignment may comprise any of (1) a frequency allocation, (2) an aspect of time allocation, such as a duration, (3) a priority, (4) a modulation and coding scheme, (5) a transport block size, (6), a number of spatial layers, (7) a number of transport blocks, (8) any of a TCI state, CRI or SRI, (9) a number of repetitions, (10) whether the repetition scheme is Type A or Type B, (11) whether the grant is a configured grant type 1, type 2 or a dynamic grant, (12) whether the assignment is a dynamic assignment or a semi- persistent scheduling (configured) assignment, (13) a configured grant index or a semi-persistent assignment index, (14) a periodicity of a configured grant or assignment, (15) a channel access priority class (CAPC), and (16) any parameter indicated in any of DCI, MAC and RRC for the scheduling of the grant or assignment.
  • a frequency allocation such as a duration
  • a priority such as a duration
  • a priority such as
  • an indication by DCI may comprise at least one of the following.
  • An indication by DCI may comprise an explicit indication by a DCI field or by RNTI used to mask or scramble the CRC of the DCI.
  • An indication by DCI may comprise an implicit indication by a property such as any of a DCI format, a DCI size, a Coreset or search space, an aggregation level, a first resource element of the received DCI (e.g., index of first control channel element), where the mapping (e.g., association) between the property and the value may be signaled (e.g., indicated) by RRC and/or MAC.
  • receiving or monitoring for a DCI with or using an RNTI may mean that (e.g., may be based on) the CRC of the DCI may be masked or scrambled with the RNTI.
  • a signal may be interchangeably used with one or more of (1) a sounding reference signal (SRS), (2) a channel state information - reference signal (CSI- RS), (3) a demodulation reference signal (DMRS), (4) a phase tracking reference signal (PT-RS), (5) a synchronization signal block (SSB) which (e.g., all) may be applicable to embodiments described herein.
  • SRS sounding reference signal
  • CSI- RS channel state information - reference signal
  • DMRS demodulation reference signal
  • PT-RS phase tracking reference signal
  • SSB synchronization signal block
  • Other types of reference signals may be applicable to embodiments described herein.
  • a channel may be interchangeably used with one or more of (1) a physical downlink control channel (PDCCH), (2) a physical downlink shared channel (PDSCH), (3) a physical uplink control channel (PUCCH), (4) a physical uplink shared channel (PUSCH), (5) a physical random-access channel (PRACH), which (e.g., all) may be applicable to embodiments described herein.
  • a physical downlink control channel (PDCCH)
  • PDSCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PRACH physical random-access channel
  • downlink reception may be used interchangeably with Rx occasion, PDCCH, PDSCH, SSB reception, which (e.g., all) may be applicable to embodiments described herein.
  • uplink transmission may be used interchangeably with Tx occasion, PUCCH, PUSCH, PRACH, SRS transmission, which (e.g., all) may be applicable to embodiments described herein.
  • RS may be interchangeably used with one or more of RS resource, RS resource set, RS port and RS port group, which (e.g., all) may be applicable to embodiments described herein.
  • RS may be interchangeably used with one or more of SSB, CSI-RS, SRS, and DMRS, which (e.g., all) may be applicable to embodiments described herein.
  • time instance, slot, symbol, and subframe may be used interchangeably, which (e.g., all) may be applicable to embodiments described herein.
  • the terms UL-only and DL-only Tx/Rx occasions may interchangeably be used with legacy TDD UL or legacy TDD DL, respectively, which (e.g., all) may be applicable to embodiments described herein.
  • the legacy TDD UL/DL Tx/Rx occasions may correspond to SBFD not being configured and/or to SBFD being disabled.
  • the terms received signal power, received signal energy, received signal strength, SSB EPRE, CSI EPRE, RSRP, RSSI, SINR, RSRQ, SS-RSRP, SS-RSSI, SS-SINR, SS-RSRQ, CSI-RSRP, CSI-RSSI, CSI-SINR, and CSI-RSRQ may be used interchangeably, which (e.g., all) may be applicable to embodiments described herein.
  • the term CLI may be used interchangeably with interference, which may be applicable to embodiments described herein.
  • non-SBFD may be used interchangeably with operation without SBFD, TDD, legacy TDD, which (e.g., all) may be applicable to embodiments described herein.
  • the terms ‘WTRU may be configured’, ‘WTRU may be indicated’, ‘WTRU may receive configuration’, and so forth, may imply that the configuration may be indicated for example ‘via any of RRC, MAC-CE, DCI, MIB, SIB, and so forth’, unless indicated otherwise, where for example, ‘WTRU may be configured’ may imply (e.g., may be used interchangeably with) ‘WTRU may be configured via any of RRC, MAC-CE, MIB, SIB, and so forth’ .
  • a ‘reactive’, ‘DMRS-based’, ‘RS-based’, and ‘sequence-based’ CLI measurement may be used interchangeably, which (e.g., all) may be applicable to embodiments described herein.
  • WTRU may imply (e.g., may be used interchangeably with) the “first WTRU” unless otherwise stated.
  • cross-link interference and “cross-layer interference” may be used interchangeably.
  • SBFD Sub-band non-overlapping Full Duplex
  • a WTRU may be configured with one or more types of slots within a bandwidth.
  • a first type of slot may be used or determined for a first direction (e.g., downlink)
  • a second type of slot may be used or determined for a second direction (e.g., uplink).
  • a third type of slot may have a first group of frequency resources within the bandwidth for a first direction and a second group of frequency resources within the bandwidth for a second direction.
  • the bandwidth may be interchangeably used with bandwidth part (BWP), carrier, sub-band, and system bandwidth.
  • BWP bandwidth part
  • the first type of slot (e.g., the slot for a first direction) may be referred to as downlink slot
  • the second type of slot e.g., slot for a second direction
  • the third type of slot may be referred to as sub-band (nonoverlapping) full duplex (SBFD) slot
  • the group of frequency resource for a first direction may be referred to as any of downlink sub-band, downlink frequency resource, or downlink RBs
  • the group of frequency resource for a second direction may be referred to as any of uplink sub-band, uplink frequency resource, or uplink RBs.
  • the group of frequency resource for a flexible direction may be referred to as flexible sub-band, flexible frequency resource, and flexible RBs.
  • the group of frequency resource between a first direction and a second direction may be referred to as any of guard band, guard frequency resource, and guard RBs.
  • a (SBFD-enabled) WTRU may receive or be configured with one or more SBFD UL or DL sub-bands in one or more DL/UL/flexible TDD time instances (e.g., any of symbols, slots, frames, and so forth).
  • the WTRU may be configured with one or more resource allocations for SBFD sub-bands.
  • the SBFD configuration may include a flag signal (e.g., enabled/disabled), where, for example, a first value (e.g., zero (0)) may indicate a first mode of operation (e.g., SBFD configuration), and a second value (e.g., one (1)) may indicate a second mode of operation (e.g., non-SBFD operation).
  • the modes of operation e.g., SBFD and/or non-SBFD
  • the WTRU may receive (e.g., may be allocated, indicated) the time resources (e.g., one or more symbols, slots, and so forth), for which the first mode of operation (e.g., SBFD) may be defined in for example one or more BWPs, sub-bands, component carriers (CC), cells, and so forth.
  • the WTRU may receive (e.g., may be allocated, indicated) the frequency resources (e.g., sub-bands/BWPs including one or more PRBs) within (active and/or linked) BWP, for which the first mode of operation (e.g., SBFD) may be configured.
  • the time instances may be indicated based on periodic, semi-persistent, or aperiodic configurations.
  • the time instances may be indicated via a bitmap configuration, where a bit (e.g., each bit) may correspond to a time instance (e.g., any of slot, symbol, subframe, etc.) and a bit indication (e.g., each bit indication) may indicate whether corresponding time instance may be used for the first or second mode of operation.
  • a WTRU may be configured with a DL TDD configuration for a component carrier (CC) or a BWP for one or more Rx occasions (e.g., via tdd-UL-DL-config- common/dedicated configurations, slot format indicator (SFI), and so forth).
  • CC component carrier
  • BWP BWP for one or more Rx occasions
  • the first mode of operation e.g., SBFD
  • one or more of the configured frequency resources e.g., sub-bands, PRBs, and/or BWPs
  • the configured frequency resources e.g., sub-bands, PRBs, and/or BWPs
  • the WTRU may be configured with an UL TDD configuration for a component carrier (CC) or a BWP for one or more Tx occasions (e.g., via tdd-UL-DL-config- common/dedicated configurations, slot format indicator (SFI), and so forth).
  • CC component carrier
  • BWP BWP for one or more Tx occasions
  • the first mode of operation e.g., SBFD
  • one or more of the configured frequency resources e.g., sub-bands, PRBs, and/or BWPs
  • the configured frequency resources e.g., sub-bands, PRBs, and/or BWPs
  • the WTRU may be configured with any of a DL, UL, and Flexible TDD configuration for a component carrier (CC) or a BWP for one or more Rx/Tx occasions (e.g., via tdd-UL-DL-config-common/dedicated configurations, slot format indicator (SFI), and so forth).
  • CC component carrier
  • BWP BWP for one or more Rx/Tx occasions
  • the first mode of operation e.g., SBFD
  • one or more of the configured frequency resources e.g., sub-bands, PRBs, and/or BWPs
  • the first mode of operation e.g., either UL transmission or DL reception based on the configurations.
  • the duplexing mode for the first mode of operation may be indicated via a flag indication, where for example a first value (e.g., zero (0)) may indicate a first mode (e.g., UL duplexing mode), and a second the value (e.g., one (1)) may indicate a second mode (e.g., DL duplexing model).
  • a first value e.g., zero (0)
  • a second the value e.g., one (1)
  • a second mode e.g., DL duplexing model
  • the duplexing mode configuration and/or flag for the first mode of operation may be configured as part of modes of operation configuration that may be semi-static (e.g., via RRC) or dynamic (e.g., via any of DCI, MAC-CE).
  • the duplexing mode configuration and/or flag for the first mode of operation may be configured as part of resource allocation configuration for a Tx/Rx occasion.
  • a WTRU may be configured, determined, or indicated to perform a measurement of cross-link interference (CLI) received signal strength indicator (RSSI) in a (e.g., given) time period.
  • CLI cross-link interference
  • RSSI received signal strength indicator
  • the (e.g., given) time period may be, for example, one or more slots, OFDM symbols, resource blocks (RBs), and/or resource elements (REs).
  • the CLI-RSSI which may be measured in a (e.g., given) time/frequency resource may be referred to as any of LI -CLI-RSSI, short-term CLI-RSSI, aperiodic CLI-RSSI, and so forth.
  • the WTRU may be configured, determined, or indicated to perform a measurement of reference signal received power (RSRP) based on one or more reference signals (e.g., SRS-RSRP) in the context of CLI measurement in a (e.g., given) time period.
  • the (e.g., given) time period may be one or more slots, OFDM symbols, resource blocks (RBs), and/or resource elements (REs).
  • the SRS-RSRP which may be measured in a (e.g., given) time/frequency resource may be referred to as any of LI -SRS- RSRP, short-term SRS-RSRP, aperiodic SRS-RSRP, SRS-RSRP-CLI, and so forth.
  • CLI-RSSI, LI -CLI-RSSI, CLI, interference signal strength, SINR, and RSSI may be interchangeably used, which (e.g., all) may be applicable to embodiments described herein.
  • SRS-RSRP, SRS-RSRP-CLI, LI -SRS-RSRP, and RSRP may be interchangeably used, which (e.g., all) may be applicable to embodiments described herein.
  • One or more RS SI (or RSRP) types may be used and a WTRU may be configured to perform one or more RSSI (or RSRP) types.
  • a first RSSI (or RSRP) type may be based on a measurement over a longer time period (e.g., more than one slot) and the measurement may be reported via a higher layer signaling (e.g., any of RRC, MAC), and a second RSSI (or RSRP) type may be based on a measurement over a shorter time period (e.g., any of one slot, within a slot, one or more OFDM symbols within a slot) and the measurement may be reported via a LI signaling (e.g., any of PUCCH, PUSCH, RACH, SRS).
  • RSSI may be interchangeably used with RSRP, RSRQ, and SINR.
  • CLLRSSI may be interchangeably used with SRS-RSRP and SINR.
  • the WTRU may be configured with a set of time/frequency resource to measure L 1 -CLL RSSI.
  • the time/frequency resource for LI -CLLRSSI measurement may be referred to as CLI- RSSI measurement resource (CRMR).
  • a CRMR may be a resource configured, determined, or defined (e.g., via any of RRC, MAC-CE, DCI) (e.g., via any of CLLResourceConfig, CLI-ResourceConfig-r-16, and so forth) with one or more of following properties:
  • a first example of properties may include a set of muted REs in downlink resource (e.g., PDSCH), wherein the muted REs may be rate-matched around or punctured for downlink reception and/or uplink transmission.
  • the set of muted REs may have a same pattern (e.g., same time/frequency location) in an RB (e.g., each RB).
  • the set of muted REs may have a different pattern based on the RB location. For example, a first pattern may be used for the RBs located in an edge of the scheduled RBs and a second pattern may be used for the RBs located in a center of the scheduled RBs.
  • the first pattern and the second pattern may have a different number of muted REs.
  • the muted REs may be in a form of (e.g., may comprise) zero-power resources (e.g., CSLRS and/or ZP-CSLRS).
  • a second example of properties may include a set of REs not being scheduled or used for the WTRU measuring CRMR.
  • a third example of properties may include a set of REs being located in an RB which may be configured or determined as guard band (or guard RB).
  • a guard band (or guard RB) may be located in between uplink and downlink resources. For example, a WTRU may skip receiving or transmitting a signal in guard band.
  • a fourth example of properties may include one or more reference signals (e.g., any of DMRS, SRS, sidelink CSI-RS, etc ).
  • a fifth example of properties may include a second set of DMRS REs within a second CDM group (e.g., within a scheduled downlink resource/RBs, e.g., of PDSCH), where a WTRU may receive a DCI, scheduling the PDSCH, indicating a first set of DMRS REs corresponding to a first CDM group to be used for receiving the PDSCH.
  • the WTRU may receive the DCI, scheduling the PDSCH, indicating a first set of DMRS REs corresponding to a first CDM group (based on an indicated ‘(DMRS) antenna port’ field of the DCI.
  • the WTRU may determine that a second set of DMRS REs within a second CDM group (other than the first CDM group) may be used as the CRMR (e.g., within the scheduled PDSCH).
  • a sixth example of properties of the CRMR may include being located within a scheduled resource (e.g., scheduled PDSCH RBs).
  • a CRMR may be configured commonly for a set of WTRUs (e.g., WTRUs in proximity).
  • a gNB may configure a CRMR for a group of WTRUs, which may share one or more of (1) a group-ID to receive a DCI (e.g., a group-RNTI), (2) a zone-ID, which may be determined based on a geographical location of the WTRU (e.g., GNSS), and (3) WTRUs paired for sidelink unicast (or groupcast) transmission.
  • a group-ID to receive a DCI
  • a zone-ID which may be determined based on a geographical location of the WTRU (e.g., GNSS)
  • WTRUs paired for sidelink unicast (or groupcast) transmission paired for sidelink unicast (or groupcast) transmission.
  • a Ll-CLI-RSSI measurement (including CRMR resource) may be considered as CSI reporting quantity and configured as a part of CSI reporting setting.
  • a first WTRU may be configured to measure SRS-RSRP in DL subbands on an SBFD configuration, where the SRS may be transmitted by a second WTRU in the UL sub-bands.
  • the first WTRU may measure SRS-RSRP based of the configured SRS signaling in the DL sub-bands.
  • the WTRU may measure the CLI-RSSI based on the configured SRS signaling in the UL sub-bands.
  • the WTRU may be configured, determined, or indicated to perform a delta CLI-RSSI, which may be based on a first CLI-RSSI measurement in a first time/frequency location and a second CLI-RSSI measurement in a second time/frequency location.
  • a delta CLI-RSSI which may be based on a first CLI-RSSI measurement in a first time/frequency location and a second CLI-RSSI measurement in a second time/frequency location.
  • the first CLI-RSSI may be measured from CRMR resources located in the edge of the scheduled RBs and the second CLI-RSSI may be measured from CRMR resources located in the middle of the scheduled RBs.
  • a WTRU may be configured with a first CRMR resource for the first CLI-RSSI measurement and a second CRMR resource for the second CLI-RSSI measurement.
  • a WTRU may (e.g., determine to) report CLI measurement related information if a measured delta-CLI-RSSI is larger than a threshold.
  • CLI reporting may be triggered based on delta-CLI-RSSI measurement being larger than a threshold.
  • the threshold may be predetermined or configured.
  • the WTRU may be configured or determined to measure CLI-RSSI per sub-band level.
  • a sub-band may be configured, or predetermined and a WTRU may perform CLI- RSSI measurement in a sub-band (e.g., each sub-band).
  • CLI-RSSI measurement e.g., each sub-band.
  • a sub-band size may be determined based on the number of scheduled RBs (e.g., for PDSCH).
  • the WTRU may report CLI-RSSI measurement for (e.g., all) subbands.
  • the WTRU may report a subset of CLI-RSSI.
  • the subset may be determined based on one or more conditions (e.g., CLI-RSSI value above threshold, subband location (e.g., edge of scheduled RBs), and/or sub-band index).
  • the WTRU may determine a bandwidth of beam measurement/reporting (e.g., wideband or sub-band) based on one or more of following condition.
  • a condition may be associated with a time unit type (e.g., SBFD or non-SBFD).
  • a WTRU may report wideband CRI (e.g., wideband beam index) in non-SBFD time units (e.g., symbol, slot, and so forth) and the WTRU may report sub-band CRI (e.g., sub-band beam index) in SBFD time units.
  • a condition may be associated with a presence of CLI-RSSI measurement.
  • the bandwidth of beam measurement/reporting may be determined based on whether CLI-RSSI may be measured in the same slot or not.
  • the WTRU may be indicated to perform CLI-RSSI measurement in a (e.g., specific) frequency location within a scheduled RBs (or non-scheduled RBs), wherein the (e.g., specific) frequency location may be one or more of sub-bands, RBs, and REs.
  • the indication may be in a DCI which may trigger the CLI-RSSI measurement (e.g., aperiodic CLI-RSSI measurement).
  • the (e.g., specific) frequency location may be indicated based on the CRMR resource frequency location.
  • one or more CRMR resources may be configured and a (e.g., each) CRMR resource may be located in a (e.g., specific) frequency location based on configuration.
  • the WTRU may be indicated to perform measurement on CRMR resource indicated in a DCI.
  • CL-IM may be configured.
  • a first WTRU e.g., potential victim third WTRU 43 shown at FIG. 4
  • may receive configuration information (e.g., via any of RRC, MAC- CE, DCI) on (cross-link interference measurement) CL-IM resources for measuring inter-WTRU CLI.
  • the configuration information may include any of time and frequency for a set of (e.g., pilot) CL-IM resources.
  • the set of (e.g., pilot) CL-IM resources may be configured in one or more REs and symbols.
  • the CL-IM resources may be configured any of periodically, semi-persistently, and a-periodically.
  • the CL-IM resources may be in any of UL sub-bands, DL sub-bands, SBFD symbols and d-TDD symbols.
  • measurement may be triggered.
  • the first WTRU may receive an indication to measure and report CLI, where the indication may include (e.g., indicate) any of type of CLI measurement, a DMRS-based CLI enable, and a triggering indication.
  • a type of CLI measurement may indicate any of (i) DMRS-based CLLRSRP, (ii) DMRS-based CLI-RSSI, (iii) SRS-RSRP, and (iv) CLI-RSSI.
  • the indication may include a (e.g., a DMRS-based CLI enable) flag indication to enable DMRS-based CLI measurement based on UL data from a second WTRU.
  • the WTRU may receive the indication to measure DMRS-based CLI via MAC-CE or DCI signaling for UL grants that may be semi-statically or dynamically, respectively, configured for a second WTRU.
  • the triggering indication e.g., DCI
  • the triggering indication may have (e.g., include, indicate) information on the reporting resources.
  • the indication may include one or more configuration information on the UL grant of a second WTRU (e.g., WTRU1/WTRU2) and the DMRS configuration and resources to be measured.
  • a second WTRU e.g., WTRU1/WTRU2
  • the configuration information may include any of an UL grant time allocation, an UL grant frequency allocation, a number of RBs configured for the UL grant, DMRS symbols, a DMRS position in frequency domain (REs), a DMRS type, a DMRS group, a DMRS length, a DMRS seed/pattern, and a DMRS CDM group, etc. for the PUSCH/PUCCH that may be scheduled for the second WTRU.
  • REs DMRS position in frequency domain
  • the configuration information may include (e.g., indicate) the beam direction, e.g., any of spatial filter, TCLstate, etc. for measuring the CLI (e.g., receiving beam direction of the third WTRU 43).
  • the beam direction may be associated with a first WTRU’s configured DL beam direction.
  • the beam direction may be indicated from a set of configured Rx beam directions.
  • CL-IM resources may be determined.
  • the first WTRU may determine the CL-IM resources based on any of a CLI measurement type and an UL grant/ schedule of the second WTRU.
  • the CLI measurement type is “DMRS-based CLI-RSRP”
  • the WTRU may select the resources for CLI measurement based on CL-IM resources in UL sub-band (e.g., to measure correlation-based RSRP based on DMRS).
  • the CLI measurement type is “DMRS-based CLL RSSI”
  • the WTRU may select the resources for CLI measurement based on CL-IM resources in DL sub-band (e.g., to measure the leakage/effect of the UL DMRS in DL sub-bands).
  • the first WTRU may determine the CL-IM resources based on the second WTRU’s UL grant/schedule.
  • the DMRS may be (e.g., received) in one or more first symbols and first Res. If a first CL-IM resource is (e.g., fully) included in the one or more first symbols (and e.g., first REs), the first WTRU may use (e.g., determine, select) the first CL-IM resource.
  • the first WTRU may use (e.g., select, determine) the second or third CL-IM resources. In such a case, the first WTRU may use scaling factors for determining the CLI based on the measurements.
  • measurement may be performed and reported.
  • the first WTRU may measure DMRS-based CLI in the determined CL-IM resources based on configured UL DMRS transmitted via (e.g., received from) the second WTRU.
  • the first WTRU may report (e.g., transmit report information indicating) the CL-IM resources used for the measurement.
  • the first WTRU may report (e.g., transmit report information indicating) the measured UL DMRS- based CLI.
  • the first WTRU may report an indication in case the measured CLI is higher or lower than a threshold (e.g., as part of the CSI, special SR, or along with NACK transmission). In case the gNB does not receive the indication, the gNB may expect that the CLI may be lower than the threshold and that the first/second WTRUs may not be causing strong CLI on the third WTRU.
  • a threshold e.g., as part of the CSI, special SR, or along with NACK transmission.
  • FIG. 5 is a diagram illustrating an example of CLI measurement and reporting based on DMRS in UL data.
  • a WTRU may receive first configuration information (e.g., via RRC) indicating a set of (e.g., pilot) CL-IM resources for measuring inter WTRU CLI.
  • the WTRU may receive an indication to measure and report CLI, including any of a type of CLI measurement and a reactive CLI enable indication.
  • the WTRU may receive second configuration information on an UL grant and the DMRS configuration and resources based on which the reactive CLI may be measured.
  • the WTRU may select from CL-IM resources in DL sub-bands. As shown at 544, if the CLI measurement type is DMRS-based CLI-RSRP, the WTRU may select from CL-IM resources in UL sub-bands. As shown at 548, the WTRU may select the CL-IM resources based on the combination of indicated DMRS resources and CL-IM resources, that may be any of fully overlapping, partially overlapping, and close to be overlapping, etc. As shown at 550, the WTRU may measure DMRS- based CLI and may report the CLI. The WTRU may report the used CL-IM resources.
  • a method for measuring CLI based on one or more DMRS signals is described herein, where a first WTRU may measure DMRS signals transmitted via (e.g., received from) a second WTRU (e.g., directed to another WTRU or to a gNB), or a first WTRU may measure DMRS signals transmitted toward (e.g., directed to) a second WTRU (e.g., received from a gNB).
  • the WTRU may select from a set (e.g., a plurality) of (pre)configured cross-link interference measurement (CL-IM) resources that may be configured in any of UL and DL sub-bands.
  • CL-IM cross-link interference measurement
  • the WTRU may select the CL-IM resources based on the indicated or determined type of CLI measurement, in combination with configured DMRS transmission and availability of CL-IM resources.
  • FIG. 6 is a diagram illustrating an example configuration for measuring CLI in DL subband based on DMRS in UL data.
  • a third WTRU 63 may be a (e.g., potential) victim WTRU, where a first WTRU 61 and a second WTRU 62 may be (e.g., potential) aggressor WTRUs.
  • the first WTRU 61 may be in the same serving cell 60 as the third WTRU 63.
  • the serving cell 60 may be configured with SBFD operation and UL transmission in UL sub-band, may be causing inter-sub-band CLI on the third WTRU 63.
  • FIG. 6 is a diagram illustrating an example configuration for measuring CLI in DL subband based on DMRS in UL data.
  • a third WTRU 63 may be a (e.g., potential) victim WTRU, where a first WTRU 61 and a second WTRU 62 may be (e.g., potential) aggr
  • the third WTRU 63 may be in the neighbor cell 65 of the second WTRU 62.
  • the neighbor cell 65 may be configured with dynamic and/or flexible TDD operation and UL transmission in UL slot, may be causing intra-sub-band CLI for the third WTRU 63.
  • the third WTRU 63 may be configured with a set of (pre)configured CL-IM resources 601 that may be in any of UL and DL sub-bands.
  • the third WTRU 63 may be configured to measure CLI-RSSI based on UL DMRS. As such, the third WTRU 63 may determine to use one or more of the CL-IM resources 601 in DL sub-band.
  • the third WTRU 63 may select the CL-IM resources 601 to be used for CLI measurement based on DMRS signals configured and/or scheduled for the first WTRU 61 and/or the second WTRU 62.
  • the third WTRU 63 may determine to use the first set 6011 of CL-IM resources 601 (e.g., REs) that may coincide in time with DMRS REs 602 transmitted via (e.g., received from) the first WTRU 61.
  • CL-IM resources 601 e.g., REs
  • the third WTRU 63 may measure a first CLI (referred to as CLI1) from the first WTRU 61 in CL-IM resources 601 that may coincide in time with DMRS resources 602 used by DMRS transmission in the first WTRU’s configured and/or scheduled PUSCH transmission.
  • CLI1 a first CLI
  • the third WTRU 63 may determine to use the second set 6012 of CL-IM resources 601 (e.g., REs) that may coincide in time with DMRS REs 602 transmitted via (e.g., received from) the second WTRU 62.
  • CL-IM resources 601 e.g., REs
  • the third WTRU 63 may measure a second CLI (referred to as CLI2) from the second WTRU 62 in CL-IM resources 601 that may coincide in time with DMRS resources 602 used by DMRS transmission in the second WTRU’s configured and/or scheduled PUSCH transmission.
  • CLI2 a second CLI
  • a first WTRU may be configured with CL-IM resources on which to perform CLI measurement.
  • the first WTRU may receive configuration (e.g., information) on CL-IM resources, for example, via any of SIB, RRC, MAC-CE, DCI, etc.
  • the first WTRU may be configured with CL-IM resources semi-statically (e.g., via any of RRC, MAC-CE, etc.).
  • One or more CL-IM resources may be added or removed from the list of (e.g., configured) CL-IM resources (e.g., via any of RRC, MAC-CE, DCI, etc ).
  • the first WTRU may be configured to perform CLI measurement on CL- IM resources based on one or more reference signals, where the reference signals may be one or more DMRS signals.
  • DMRS, RS, and reference signal may be used interchangeably.
  • the CL-IM configuration may include one or more of (1) a CL-IM resource configuration index, (2) CL-IM Resource set, (3) a frequency configuration, (4) a RE configuration, subcarrier location, (5) a time configuration, symbol location, (6) a CL-IM resource type and (7) a pattern configuration, etc.
  • the first WTRU may receive configuration information on one or more CL- IM resources, where the configuration information may include (e.g., indicate) a CL-IM resource configuration index, for example, CL-IM-Index.
  • the configuration information may include (e.g., indicate) a CL-IM resource configuration index, for example, CL-IM-Index.
  • the first WTRU may be configured with a CL-IM resource set, where the configuration may include (e.g., indicate) a CL-IM resource set index, in addition to the CL-IM resource indexes that may be included as part of the configured CL-IM resource set.
  • the first WTRU may receive indications to add or remove one or more CL-IM resources from one or more configured CL-IM resource sets.
  • the CL-IM resources may be configured in one or more sets of sub-bands, BWPs, CCs, group of frequency resources, resource blocks (RBs), resource elements (REs), etc.
  • the first WTRU may be configured with a BWP index (e.g., bwp-Id) where the CL-IM resources may be allocated.
  • the configured sub-bands may be configured for operation in one or more communication directions.
  • the CL-IM resources may be configured in a first set of sub-bands with a first direction, for example downlink sub-bands.
  • the CL-IM resources may be configured in a second set of sub-bands with a second direction, for example, uplink sub-bands.
  • the CL-IM resources may be configured in a third set of sub-bands with a third direction, for example, flexible sub-bands, and so forth.
  • the configured sub-bands may be configured in symbols configured with operation based on any of SBFD, non- SBFD, dynamic TDD, flexible TDD, etc.
  • the CL-IM resources may be configured in contiguous or non-contiguous REs within the configured frequency resources.
  • the CL-IM REs may be contiguous, where the WTRU may receive configurations on the first RE, last RE, and/or CL-IM RE durations.
  • the CL-IM REs may be configured in RE pairs that may take place every other REs.
  • the configured CL-IM RE pairs may be configured at the interval of a (pre)configured number (e.g., N) of REs.
  • the REs in a pair may be configured apart from the (e.g., each) other with the interval of a (pre)configured number (e.g., M) of REs.
  • the CM-IM RE pairs may be dispersed, spread, and/or distributed at every other REs within the configured frequency domain.
  • the first WTRU may be (pre)configured and/or receive one or more configuration information on the time and frequency resources corresponding to one or more CL-IM resources.
  • the first WTRU may be configured with CL-IM resources in a configured time period, where the configured time period may be one or more slots, OFDM symbols, etc.
  • the configuration on the CL-IM resources may include a periodicity of the configured and/or indicated CL-IM resources and/or CL-IM resource sets.
  • the CL-IM resources and/or CL-IM resource sets may be configured periodically, semi-persistently, and/or a-periodically.
  • the configuration may include any of a period time, a start time, and end time, and a time duration during which the CL-IM resources and/or CL-IM resource sets may be configured.
  • the first WTRU may be (pre)configured with one or more sets of patterns and pattern indexes for CL-IM resources.
  • the first WTRU may determine the subcarrier location and symbol location for the configured CL-IM resources based on the received pattern indexes.
  • a WTRU may determine the (e.g., maximum, upper bound) number of CL-IM resources that the WTRU may be configured with or based on which the WTRU may measure CLI.
  • the WTRU may determine the (e.g., maximum, upper bound) number of CL-IM resources that WTRU may be configured in a CL-IM resource set.
  • the WTRU may determine the (e.g., maximum, upper bound) number of CL-IM resource sets that WTRU may be configured with or based on which the WTRU may measure CLI, and so forth.
  • the WTRU may report the determined (e.g., maximum) values as part of WTRU capability reporting.
  • the CL- IM resources may be configured in association with one or more CSI-IM, ZP CSI-RS, and/or NZP CSI-RS resources.
  • the CL-IM resources may be configured as CSI-IM resources for interference management based on the configured DMRS or another RS that may be transmitted to or via another WTRU.
  • the CL-IM resources may be based on ZP CSI-RS resources, where the WTRU may measure CLI-RSSI based on the configured resources.
  • the CL-IM resources may be based on NZP CSI-RS resources, where the WTRU may measure CLI-RSRP, DMRS-based CLI-RSRP, etc. based on the configured resources and the configured reference signals.
  • a first WTRU may determine and/or receive one or more triggers, and/or indications, and/or configuration information to measure and/or report CLI (e.g., WTRU-to WTRU CLI, inter- WTRU CLI, etc.).
  • the first WTRU may receive the measurement indication and/or report configuration via any of RRC, MAC-CE, DCI, etc.
  • the CLI report configuration may include on or more of (1) a CL-IM resource index and/or a CL-IM resource set index, (2) an enable/disable indication for DMRS-based CLI measurement, (3) a type of CLI measurement, (4) a periodicity, (5) a measurement layer and (6) report resources.
  • the configuration information may include an indication on the CL-IM resource index and/or CL-IM resource set index to be used for measuring the DMRS-based CLI.
  • the first WTRU may receive (e.g., in the configuration information) an indication to enable or disable measuring CLI based on DMRS transmitted to or from a second WTRU.
  • the indication may be based on a flag indication, where a first value (e.g., value zero) may indicate disabling the DMRS-based CLI measurement, and a second value (e.g., value one) may indicate enabling the DMRS-based CLI measurement.
  • the indication may also include the start time, end-time, and/or a time duration to enable or disable the DMRS-based CLI measurement.
  • the indication may include the CL-IM resource index and/or CL-IM resource set index, for which the DMRS-based CLI measurement may be enabled or disabled.
  • the first WTRU may receive (e.g., in the configuration information) an indication (e.g., from a gNB) to measure CLI based on one or more of (1) DMRS-based CLI-RSRP (e.g., type), (2) DMRS-based CLI-RSSI (e.g., type), (3) SRS- RSRP (e.g., type), and (4) CLI-RSSI (e.g., type), etc.
  • the first WTRU may receive an indication to measure CLI-RSRP based on DMRS transmitted to or (e.g., received) from a second WTRU.
  • measuring RSRP based on one or more reference signals may be performed according to correlation-based average power of REs that may carry the configured reference signal within the configured frequency domain.
  • the first WTRU may receive an indication to measure CLI-RSSI based on DMRS transmitted to or (e.g., received) from a second WTRU.
  • measuring RSSI based on one or more reference signals may be performed according to (e.g., total) received wideband power corresponding to the configured reference signal.
  • the first WTRU may measure the leakage and/or effect of UL DMRS transmission, for example, from a second WTRU, in one or more (e.g., configured) DL sub-bands.
  • the first WTRU may receive an indication to measure (e.g., legacy) SRS- RSRP based on SRS transmitted (e.g., received) from a second WTRU.
  • an indication to measure e.g., legacy
  • SRS- RSRP based on SRS transmitted (e.g., received) from a second WTRU.
  • the first WTRU may receive an indication to measure (e.g., legacy) CLI- RSSI based on the configured time and frequency resources.
  • an indication to measure e.g., legacy
  • the first WTRU may receive configuration to measure and report DMRS-based CLI any of periodically, semi-persistently, and a-periodically.
  • the configuration information may include (e.g., indicate) any of a period time, a start time, an end time, and/or a time duration for reporting the measured DMRS-based CLI.
  • the first WTRU may receive (e.g., in the configuration information) an indication on whether the DMRS-based CLI may be based on LI or L3 measurements.
  • the first WTRU may receive configuration information on the time and frequency resources to be used for reporting the measure DMRS- based CLI.
  • the first WTRU may receive one or more (e.g., extra) configuration information to perform DMRS-based CLI measurements.
  • the (e.g., extra) configuration information may be received in the same message or in a different message from the message including the indication to perform DMRS-based CLI measurement.
  • the first WTRU may receive indication to measure CLI, where the CLI measurement type may be at least one of DMRS-based CLI-RSRP, DMRS-based CLI-RSSI, etc.
  • the first WTRU may receive configuration information to measure CLI, where the configuration information may include an indication that may enable DMRS-based CLI measurement.
  • the first WTRU may receive one or more pieces of configuration information regarding DMRS-based CLI measurement via any of SIB, RRC, MAC-CE, etc., e.g., in case the UL and/or DL transmission occasions are configured semi-statically, for example, for a second WTRU.
  • the first WTRU may receive one or more pieces of configuration information regarding DMRS-based CLI measurement via any of MAC-CE, DCI, etc., e.g., in case the UL and/or DL transmission occasions are configured dynamically, for example, for the second WTRU.
  • the received configuration information on DMRS-based CLI measurement may include (e.g., indicate) one or more of (1) UL/DL grant time and frequency allocations, (2) a number of RBs configured for the UL/DL grant, (3) DMRS configurations, and (4) a CLI measurement beam direction, etc.
  • the first WTRU may receive one or more pieces of information on the UL or DL grants/assignments that may be configured, for example, for a second WTRU, based on which the first WTRU may measure DMRS-based CLI.
  • the first WTRU may receive one or more TDRA and/or FDRA configurations on one or more PDCCH, PDSCH, etc. that may be configured and/or scheduled to be transmitted to the second WTRU.
  • the first WTRU may receive one or more TDRA and/or FDRA configurations on one or more PUCCH, PUSCH, etc. that may be configured and/or scheduled to be transmitted via (e.g., received from) the second WTRU.
  • the first WTRU may receive one or more pieces of information on the number of RBs that may be configured and/or scheduled for the UL or DL grants/assignments, for example, for a second WTRU, based on which the first WTRU may measure DMRS-based CLI.
  • the first WTRU may receive one or more pieces of configuration information on the DMRS that may be transmitted in DL or UL, for example, to or via the second WTRU, respectively, as part of configured and/or scheduled data.
  • the DMRS configuration information may include any of DMRS symbols, DMRS position in frequency domain (e.g., REs), DMRS type, DMRS group, DMRS length, DMRS seed, DMRS CDM group, etc.
  • the first WTRU may receive configuration information on the DMRS that may be transmitted, for example, by the second WTRU, as part of one or more configured and/or scheduled PUSCH, PUCCH, etc.
  • the first WTRU may receive configuration information on the DMRS that may be transmitted, for example, to the second WTRU, as part of one or more configured and/or scheduled PDSCH, PDCCH, etc.
  • the first WTRU may receive configuration information on the beam direction, based on which the first WTRU may measure DMRS-based CLI.
  • the first WTRU may receive (e.g., configuration information indicating) one or more of a spatial filter, a TCI-state, etc. to be used for measuring DMRS-based CLI.
  • the beam direction may be associated with first WTRU’s configured UL or DL beam direction.
  • the beam direction may be configured based on at least one of the BFD-RS set beams.
  • the first WTRU may receive indication to use a beam direction from a set and/or a list of (pre)configured beam directions.
  • the WTRU may determine the list of beam directions or receive the list, for example, via any of RRC, MAC-CE, DCI, etc., for example, from a gNB.
  • the first WTRU may be configured with a list including at least one beam direction, where the first WTRU may receive an indication to indicate the selected beam direction from the list, based on which the first WTRU may measure the DMRS- based CLI.
  • the first WTRU may receive any piece of information of the configurations described herein as part of at least one CSI reporting configuration and/or sub-configuration, where the at least one configuration or sub-configuration may correspond to a (e.g., specific) combination of parameters described herein.
  • a first (second) configuration of sub-configuration may correspond to a first (second) grant time and/or frequency configuration.
  • a (e.g., each) such CSI reporting configuration and/or sub-configuration may be associated to a (e.g., specific) CSI trigger state.
  • a first WTRU may find, select, and/or determine the CL-IM resources (e.g., out of multiple available CL-IM resources) to be used for measuring CLI based on one or more received pieces of configuration information.
  • the WTRU may determine the CL-IM resources to measure DMRS-based CLI.
  • the first WTRU may find, select, and/or determine the CL-IM resources to be used, based on any of a configured CLI measurement type, configured DMRS symbols in time and frequency, and so forth.
  • a first WTRU may find, select, and/or determine the CL-IM resources in sub-bands with the same direction as the configured reference signals for CLI-RSRP measurement. For example, the first WTRU may select the CL-IM resources from the configured set of CL-IM resources in the UL or DL sub-band, if the CLI measurement type is configured as DMRS-based CLI-RSRP, and if the DMRS is configured in UL or DL sub-bands, respectively. For example, the first WTRU may select the CL-IM resources that may fully or partially overlap with the configured DMRS in time and frequency.
  • a first WTRU may find, select, and/or determine the CL-IM resources in sub-bands with different direction as the configured reference signals for CLI-RSSI measurement.
  • the first WTRU may select the CL-IM resources from the configured set of CL-IM resources in the DL or UL sub-band, if the CLI measurement type is configured as DMRS-based CLI-RSSI, and if the DMRS is configured in UL or DL sub-bands, respectively.
  • a first WTRU may determine the CL-IM resources to be used for CLI measurement based on the combination of the available (e.g., configured) CL-IM resources and the (e.g., indicated) RS resources.
  • the first WTRU may use the indicated DMRS time and frequency resources, that may be, for example, configured and/or scheduled to be transmitted or received by a second WTRU, for finding, selecting, and/or determining the CL-IM resources to be used.
  • the first WTRU may determine the CL-IM resources to be used based on whether the CL-IM resources and configured DMRS resources fully overlap, partially overlap, or do not overlap.
  • a first WTRU may be configured to find and/or select CL-IM resources for measuring CLI that may fully overlap with configured RS resources. For example, in case a first WTRU has available configured CL-IM resources that fully overlap with the configured RS resources, the first WTRU may select the corresponding CL-IM resources for measuring the CLI.
  • the first WTRU may be configured and/or determine to measure, for example, correlation-based, DMRS-based CLI-RSRP based on the fully overlapping CL-IM and DMRS resources. For example, the first WTRU may measure DMRS-based CLI-RSRP by using the CL- IM resources that may fully overlap with the configured DMRS resources in time and frequency.
  • a first WTRU may be configured to find and/or select CL-IM resources for measuring CLI that may at least partially overlap with configured RS resources. For example, in case a first WTRU has available configured CL-IM resources that partially overlap with the configured RS resources, the first WTRU may select the corresponding CL-IM resources for measuring the CLI.
  • the first WTRU may (e.g., be configured and/or determine to) measure, for example, correlation-based, CLI-RSRP based on the partially overlapping CL-IM and DMRS resources.
  • the first WTRU may measure DMRS-based CLI-RSRP by using the CL-IM resources that may partially overlap with the configured DMRS resources in time and frequency.
  • the time and frequency resources corresponding to the selected CL-IM resources may have at least one symbol in time and one RE in frequency in common with the configured DMRS resources.
  • the first WTRU may be configured to select the CL-IM resources that may fully overlap with DMRS resources with higher (e.g., highest) priority.
  • the first WTRU may be configured to select the CL-IM resources that may partially overlap with DMRS resources with lower selection priority.
  • the first WTRU may consider (e.g., use) higher priority for the CL-IM resources that may have more and/or larger partial overlap with the configured DMRS resources compared to the CL-IM resources that may have less and/or smaller partial overlap with the configured DMRS resources.
  • the value of overlap may be measured (e.g., determined) based on the number of overlapping OFDM symbols in time and/or the number of overlapping REs in frequency domain.
  • the first WTRU may determine or be configured to (e.g., additionally) measure and report CLLRSSI in case of partially overlapping CL-IM resources with the configured DMRS resources.
  • a first WTRU may not (e.g., be able to) find and/or select CL-IM resources that may fully or partially overlap with the configured DMRS resources. In such a case, the first WTRU may not (e.g., be able to) measure DMRS-based CLI-RSRP. In an example, the first WTRU may determine to measure CLLRSSI based on the selected CL-IM resources.
  • a first WTRU may determine the CL-IM resources to be used for CLI measurement based on the combination of the available configured CL-IM resources and the indicated RS resources.
  • the first WTRU may use the indicated DMRS time and frequency resources, that may be, for example, configured and/or scheduled to be transmitted or received by a second WTRU, for finding, selecting, and/or determining the CL-IM resources to be used.
  • the first WTRU may determine the CL-IM resources to be used based on the resources that may be close to (e.g., closest to) the configured DMRS resources.
  • a first WTRU may be able to find and/or select CL-IM resources that may fully or partially overlap with configured RS resources. For example, in case a first WTRU has available configured CL-IM resources that fully overlap with the configured RS resources, the first WTRU may select the corresponding CL-IM resources for measuring the CLI. In another example, if the first WTRU is not able to find CL-IM resources that may fully overlap with the configured DMRS resources, the first WTRU may (e.g., be configured and/or determine to) select CL-IM resources that may partially overlap with the configured DMRS resources.
  • the first WTRU may be configured to select the CL-IM resources that may fully overlap with DMRS resources with higher priority (e.g., highest priority). In another example, the first WTRU may be configured to select the CL-IM resources that may partially overlap with DMRS resources with lower selection priority. In an example, the first WTRU may consider (e.g., use) higher priority for the CL-IM resources that may have more and/or larger partial overlap with the configured DMRS resources compared to the CL-IM resources that may have less and/or smaller partial overlap with the configured DMRS resources. The value of overlap may be measured (e.g., determined) based on the number of overlapping OFDM symbols in time and the number of overlapping REs in frequency domain.
  • a first WTRU may not (e.g., be able to) find and/or select CL-IM resources that may fully or partially overlap with the configured DMRS resources. In such a case, the first WTRU may select the CL-IM resources that may be closer to (e.g., closest to) the configured DMRS resources. In an example, the first WTRU may be configured or determine one or more time and frequency limits and/or ranges to select and/or determine CL-IM resources to be close to the configured DMRS resources.
  • the first WTRU may determine and/or be configured to consider (e.g., select) CL-IM resources that may be within a (pre)configured and/or (pre)determined time interval, time distance, time offset with the configured DMRS resources, as close by CL-IM resources in time.
  • the first WTRU may be configured to consider (e.g., select) the CL-IM resources within ⁇ n OFDM symbols from the configured DMRS resources as close by in time (“n” being referred to as an integer value).
  • the first WTRU may be configured or determine to give higher selection priority to the CL-IM resources that may be close by in time (e.g., within the configured time range) compared to the CL-IM resources that may be farther in time (e.g., outside of the configured time range).
  • the first WTRU may determine or be configured to measure the distance between the available CL-IM resources with the configured DMRS resources in time domain.
  • the first WTRU may consider (e.g., determine) the CL-IM resources with smaller distance as close by in time domain, where the first WTRU may consider (e.g., determine) the CL- IM resources with larger time distance as farther in time domain.
  • the UE may determine or configured to measure the distance in time domain based on number of symbols, slots, etc.
  • the first WTRU may determine or be configured to measure the distance between the available CL-IM resources with the configured DMRS resources in frequency domain.
  • the first WTRU may consider (e.g., determine) the CL-IM resources with smaller distance as close by in frequency domain.
  • the first WTRU may consider (e.g., determine) the CL-IM resources with larger frequency distance as farther in frequency domain.
  • the first WTRU may determine or be configured to measure the distance in frequency domain based on number of any of REs, RBs, etc.
  • a first WTRU may be configured or determine the order of time and frequency resources to select the closer CL-IM resources to the configured DMRS resources.
  • the first WTRU may be configured, indicated, and/or determine to select the CL-IM resources based on time-domain distance in ascending order first and then based on the frequency distance in ascending order with regards to the configured DMRS resources. For example, the first WTRU may first order the CL-IM resources based on the distance in time domain in ascending order, and then in case there are CL-IM resources with the same distance in time domain, the first WTRU may order them based on the ascending order distance in frequency domain. For example, the first WTRU may select the CL-IM resources that may be closer (e.g., closest) in time followed by frequency to the configured DMRS resources.
  • the first WTRU may be configured, indicated, and/or determine to select the CL-IM resources based on frequency-domain ascending order of distance first and then based on the time-domain ascending order of distance with regards to the configured DMRS resources. For example, the first WTRU may first order the CL-IM resources based on the ascending order of distance in frequency domain, and then in case there are CL-IM resources with the same distance in frequency domain, the first WTRU may order them based on the ascending order of distance in time domain. For example, the first WTRU may select the CL-IM resources that may be closer (e.g., closest) in frequency followed by time to the configured DMRS resources.
  • the first WTRU may receive an indication of a CL-IM resource(s) from a field (e.g., piece of information) of a DCI such as a CSI request.
  • the field e.g., piece of information
  • the field may indicate one of a set of CSI trigger states, where a CSI trigger state (e.g., each CSI trigger state) may be associated with a configuration and/or sub-configuration of a measurement resource as described herein.
  • the first WTRU may select CL-IM resources corresponding to such configuration.
  • a first WTRU may measure the configured CLI according to the selected CL-IM resources based on the configured DMRS occasions.
  • the first WTRU may measure any of DMRS-based CLI-RSRP, DMRS-based CLI-RSSI, SINR, CQI, etc.
  • the first WTRU may use a function (e.g., an equation, etc.) to determine the parameters to be reported based on measured values.
  • the first WTRU may measure any of DMRS-based CLI-RSRP, DMRS-based CLI-RSSI, SINR, CQI, etc.
  • the first WTRU may use a function (e.g., an equation, etc.) to interpolate, estimate, and/or determine the parameters to be reported based on measured values.
  • a first WTRU may be configured, indicated, and/or determine to report the measured and/or calculated CLI values in one or more configured time and frequency resources.
  • the first WTRU may report the CL-IM resources that may have been used for CLI measurement.
  • the first WTRU may report the CL-IM resource configuration index, e.g., CL-IM-Index, as part of the report.
  • the first WTRU may report the CLI type that may have been used to measure the reported CLI value.
  • the first WTRU may report the CLI type based on an indication, where a first value (e.g., value zero) may indicate that DMRS-based CLLRSRP may have been measured and may be reported, a second value (e.g., value one) may indicate that DMRS-based CLLRSSI may have been measured and may be reported, and so forth.
  • a first value e.g., value zero
  • a second value e.g., value one
  • CLLRSSI may have been measured and may be reported
  • the first WTRU may report the absolute value regarding the measured and/or calculated CLI.
  • the first WTRU may report an indication, for example, a flag indication, indicating whether the measured and/or calculated CLI is higher or lower than a (pre)configured and/or determined threshold.
  • the first WTRU may report measurement results as part of a CSI report included in the uplink grant.
  • a WTRU may perform one or more of the following.
  • a first WTRU may receive a DL or UL scheduling DCI (e.g., for a PDCCH transmission, a PDSCH transmission, a PUCCH transmission, a PUSCH transmission, etc.), where the DCI may include a flag indication, on whether the received DCI may be a CLI-measurement DCI or not.
  • a DL or UL scheduling DCI e.g., for a PDCCH transmission, a PDSCH transmission, a PUCCH transmission, a PUSCH transmission, etc.
  • the first WTRU may determine that the UL/DL scheduling may be addressed for (e.g., directed to) the first WTRU and the received DCI may be a grant scheduling DCI and may not be a CLI-measurement DCI.
  • the first WTRU may determine that the UL/DL scheduling may be addressed for (e.g., directed to) the first WTRU and the received DCI may be a grant scheduling DCI and may not be a CLI-measurement DCI.
  • the first WTRU may determine that the received DCI may be a CLI-measurement DCI and may not be a grant scheduling DCI.
  • the UL/DL scheduling in the DCI may not be addressed for (e.g., targeted to) the first WTRU.
  • a first TRP (referred to as TRP1) may send a first grant scheduling DCI to a second WTRU (e.g., the aggressor WTRU) and then a second TRP (referred to as TRP2) may send a pseudoduplicate of the first DCI for CLI-measurement to the first WTRU (e.g., victim WTRU referred to as the third WTRU 63 in FIG. 6).
  • TRP1 a first TRP
  • TRP2 may send a pseudoduplicate of the first DCI for CLI-measurement to the first WTRU (e.g., victim WTRU referred to as the third WTRU 63 in FIG. 6).
  • the CRC in the CLI-measurement DCI may be scrambled with C-RNTI that may correspond to the first WTRU.
  • the indication may include any of (i) a TDRA, (ii) a FDRA, (iii) configuration information on DMRS transmitted as part of the configured/scheduled DL/UL data, and (iv) one or more extra parameters corresponding to the first WTRU, e.g., reporting resources.
  • the TDRA for example, may be indicated via SLIV, and the FDRA may correspond to a configured/scheduled DL/UL grant, for example for a PUSCH, PUCCH, PDSCH, and/or PDCCH for the second WTRU.
  • the configuration information on DMRS transmitted as part of the configured/scheduled DL/UL data may indicate any of DMRS symbols, DMRS position in frequency domain (REs), DMRS type, DMRS group, DMRS length, DMRS seed/pattern, DMRS CDM group, etc.
  • the CLI-measurement DCI may not include parameters that may be specific to the second WTRU such as, e.g., beam direction of the second WTRU, TPC for UL for the second WTRU, etc.
  • the first WTRU may be (pre)configured with a set of more than one CL-IM resources (e.g., pilot resources) (e.g., based on configured CSLIM resources) (e.g., in DL/UL sub-bands) for measuring DMRS-based CLI.
  • CL-IM resources e.g., pilot resources
  • CSLIM resources e.g., based on configured CSLIM resources
  • the first WTRU may perform the DMRS-based CLI measurements and may report the measured parameters.
  • the first WTRU may be (pre)configured with set of PUCCH resources to report the measurements and/or the received CLI-measurement DCI may have information on the reporting resources.
  • a first WTRU may receive one or more DL or UL scheduling DCI, where the DCI may include a flag indication to indicate if the received DCI may be a “CLI-measurement” DCI.
  • the first WTRU may receive the scheduling DCI for scheduling any of PDCCH, PDSCH, PUCCH, PUSCH, etc.
  • the first WTRU may determine that the UL/DL scheduling may be addressed for (e.g., directed to) the first WTRU and the received DCI may be a (e.g., grant) scheduling DCI and may not be a CLI-measurement DCI.
  • the flag indication has a second value (e.g., one)
  • the first WTRU may determine that the received DCI may be a CLI-measurement DCI and may not be a (e.g., grant) scheduling DCI.
  • the UL/DL scheduling in the DCI may not be addressed for (e.g., directed to) the first WTRU and may be e.g., a duplicate of a scheduling DCI for a second WTRU.
  • a first TRP e.g., TRP1
  • a second WTRU e.g., an aggressor
  • a second TRP e.g., TRP2
  • the received CLI-measurement DCI at the first WTRU may include CRC that may be scrambled with C-RNTI that may correspond to the first WTRU.
  • a first WTRU may receive one or more configuration information and/or indications on one or more configured and/or scheduled grants that may have been configured and/or scheduled for a second WTRU.
  • the configuration information may include (e.g., indicate) one or more of (1) time and frequency configurations, (2) a DMRS configuration, (3) a beam direction, and (4) report configuration, etc.
  • the configuration information received via CLI-measurement DCI may include (e.g., indicate) one or more TDRA, SLIV configuration, FDRA, etc. corresponding to the configured and/or scheduled DL/UL grant, for example for a PUSCH, PUCCH, PDSCH, and/or PDCCH, for the second WTRU.
  • the configuration information received via CLI-measurement DCI may include (e.g., indicate) one or more indications and/or configuration information on the DMRS transmitted along with the configured and/or scheduled UL/DL data to or from the second WTRU.
  • the DMRS configuration information may include (e.g., indicate), for example, any of DMRS symbols, DMRS position in frequency domain (REs), DMRS type, DMRS group, DMRS length, DMRS seed, DMRS CDM group, etc.
  • the configuration information received via CLI- measurement DCI may include (e.g., indicate) a beam direction for the first WTRU to measure the DMRS-based CLI.
  • the configuration information received via CLI-measurement DCI may include (e.g., indicate) one or more indications that may correspond to the first WTRU.
  • the configuration information may include (e.g., indicate) reporting resources that may be configured for the first WTRU to report the measured DMRS-based CLI.
  • the first WTRU may be (pre)configured with a set of PUCCH resources to report the measurements.
  • the received CLI-measurement DCI may include indication on the reporting resources to be used by the first WTRU.
  • a first WTRU may determine a priority between an UL or DL occasion or a CLI measurement occasion. For example, in case the first WTRU receives a CLI measurement DCI and if the first WTRU is scheduled to receive or transmit a DL or UL, the first WTRU may determine the priority. In an example, the first WTRU may consider (e.g., determine) dynamic CLI measurement grant with higher priority compared to configured grant for UL or DL. In another example, the first WTRU may consider (e.g., determine) a configured grant for UL or DL with higher priority compared to configured CLI measurement occasions (e.g., configured via any of MAC-CE, RRC, etc.).
  • configured CLI measurement occasions e.g., configured via any of MAC-CE, RRC, etc.
  • the first WTRU may consider (e.g., determine) a dynamic CLI measurement grant (e.g., received via DCI) that may have been received before a dynamic UL or DL grant (e.g., received via DCI) to have a lower priority compared to the received dynamic UL or DL grant.
  • the first WTRU may consider (e.g., determine) a dynamic CLI measurement grant (e.g., received via DCI) that may have been received after a dynamic UL or DL grant (e.g., received via DCI) to have a higher priority compared to the received dynamic UL or DL grant.
  • the first WTRU may receive one or more configuration information on CL-IM resources for measuring any of DMRS-based CLI-RSRP, CLI-RSSI, SINR, etc. based on one or more DMRSs that may be scheduled for a second WTRU (e.g., included in UL or DL data scheduled for a second WTRU, e.g., victim WTRU).
  • a second WTRU e.g., included in UL or DL data scheduled for a second WTRU, e.g., victim WTRU.
  • the first WTRU may receive an indication or trigger (e.g., from gNB or higher layers) to measure the DL or UL DMRS-based CLI-RSRP in the configured CL-IM resources.
  • the indication may include (e.g., indicate) any of a beam direction for measuring the CLI, information on the DMRS of the UL or DL signals/channels.
  • the first WTRU may receive the indication via any of MAC-CE, DCI, or a CLI measurement DCI.
  • dynamic WTRU-oriented CLI mitigation may be performed via changing or reporting PHR based on measurements.
  • the first WTRU may perform CLI mitigation for the next one or more UL transmissions based on a configured option (e.g., via any of RRC, MAC-CE, DCI), for example, during a configured time duration or until new commands may be received from the gNB.
  • the WTRU may determine the condition to trigger CLI mitigation based on a combination of the measured UL and/or DL DMRS-based CLI-RSRP and corresponding thresholds.
  • any of (1) UL power backoff, (2) cap the UL power to a (e.g., max) value, and (3) Power backoff of the PCMAX may apply.
  • the first WTRU may be configured to apply one or more configured (e.g., via any of RRC, MAC-CE, DCI) power backoff or reduced power rates or policies.
  • the power backoff or reduced power policies may depend on the measured DL and/or UL DMRS-based CLI-RSRP and one or more thresholds (configured via any of RRC, MAC-CE, DCI).
  • the first WTRU may be configured to reduce the UL power to a configured (e.g., max) value.
  • the first WTRU may indicate the changes to the UL Tx power by triggering the transmitting and reporting of PHR (e.g., via MAC-CE) to the gNB.
  • a (e.g., new) trigger for transmitting and reporting of PHR may be based on measured CLI and/or when the first WTRU has modified PCMAX value based on CLI.
  • CLI-effected PCMAX may be reported as part of (e.g., included in) PHR reporting.
  • the first WTRU may restore the PHR and may send an indication that the PCMAX may be increased (e.g., again).
  • PCMAX may be backoff/decreased.
  • CLI is strong (e.g., above a threshold)
  • PCMAX may be increased, etc.
  • the measured CLI may be reported. If the measured DL or UL DMRS- based CLI-RSRP is higher than a first or a second threshold, respectively, the first WTRU may report the measured CLI-RSRP e.g., to the gNB (e.g., via any of UCI, MAC-CE, etc.). The gNB may consider the (e.g., potential) aggressor and victim WTRUs in scheduling procedure. For example, the gNB may adapt the scheduling procedure for the first and second WTRUs based on measured CLI being reported for the first and second WTRUs.
  • a first WTRU may be configured, indicated, and/or determine to measure CLI based on one or more reference signals transmitted to or from a second WTRU.
  • the first WTRU may be configured via any of RRC, MAC-CE, DCI, etc. to measure CLI.
  • the first WTRU may be configured to measure DMRS-based CLI based on DMRS transmitted as part of UL or DL data transmissions from or to the second WTRU, respectively.
  • the first WTRU may be, for example, a (e.g., potential) aggressor WTRU
  • the second WTRU may be, for example, a (e.g., potential) victim WTRU.
  • the first WTRU may be configured with a set of (pre)configured CL-IM resources, based on which the first WTRU may measure CLI.
  • the first WTRU may determine or be configured to measure DL DMRS-based CLI-RSRP based on one or more DL data transmissions to the second WTRU, for example, as part of any of PBCH, PDCCH, PDSCH, etc.
  • the first WTRU may measure the DL DMRS-based CLI-RSRP in one or more CL-IM resources in the DL subbands.
  • the first WTRU may determine or be configured to measure UL DMRS-based CLI-RSRP based on one or more UL data transmissions (e.g., received) from the second WTRU, for example, as part of any of PUCCH, PUSCH, etc.
  • the first WTRU may measure the UL DMRS-based CLI-RSRP in one or more CL-IM resources in the UL sub-bands.
  • the first WTRU may be configured or determine the beam direction to measure the CLI based on configured UL beam direction.
  • the first WTRU may determine the beam direction to measure UL DMRS-based CLI-RSRP based on any of a spatial filter, a beam direction, and a TCI state configured and/or determined for the scheduled and/or configured UL transmission.
  • the first WTRU may determine the beam direction to measure DL DMRS-based CLI-RSRP based on any of a spatial filter, a beam direction, and a TCI state that may correspond to any of the configured and/or determined spatial filter and/or beam direction, and/or TCLstate for the scheduled and/or configured UL transmission.
  • a first WTRU may perform CLI measurement based on one or more reference signals that may be transmitted toward a second WTRU (e.g., from a gNB). The first WTRU may determine if the second WTRU is close by the first WTRU based on the measured CLI values. In an example, a first WTRU may measure one or more DL quality parameters based on one or more reference signals transmitted to the second WTRU. For example, the first WTRU may measure any of CLI-RSRP, DMRS-based CLI-RSRP, etc. based on a DL reference signal sent to (e.g., directed to) the second WTRU.
  • the first WTRU may measure the quality parameters based on a beam direction that may correspond to the configured beam direction for UL transmission at the first WTRU. If the measured DL quality parameters (e.g., RSRP) are higher than a corresponding threshold, the first WTRU may determine that the second WTRU may be close by and in the same direction (e.g., with regards to the gNB) and/or within the LOS of the first WTRU. If the measured DL quality parameters (e.g., RSRP) are lower than the corresponding threshold, the first WTRU may determine that the second WTRU may not be close by and/or not in the same direction (e.g., with regards to the gNB) of the first WTRU.
  • the measured DL quality parameters e.g., RSRP
  • the first WTRU may determine that the second WTRU may be close by and/or in the LOS.
  • the first WTRU may measure one or more UL quality parameters based on one or more reference signals transmitted (e.g., received) from the second WTRU.
  • the first WTRU may measure any of SRS-RSRP, UL DMRS-based CLI-RSRP, etc. based on an UL reference signal (e.g., any of SRS, DMRS included in PUSCH, DMRS included in PUCCH, etc.) transmitted (e.g., received) from the second WTRU.
  • an UL reference signal e.g., any of SRS, DMRS included in PUSCH, DMRS included in PUCCH, etc.
  • the first WTRU may measure the quality parameters based on a beam direction that may correspond to the configured beam direction for UL transmission at the first WTRU. If the measured UL quality parameters (e.g., RSRP) are higher than a corresponding threshold, the first WTRU may determine that the first WTRU may be in between the second WTRU and, for example, a corresponding gNB. For example, the UL transmission from the first WTRU may not cause a very strong interference to the second WTRU. [0310] In another example, if the measured UL quality parameters (e.g., RSRP) are lower than the corresponding threshold, the first WTRU may determine that the second WTRU is in between the first WTRU and for example the gNB. For example, the UL transmission from the first WTRU may cause strong interference to the second WTRU.
  • the measured UL quality parameters e.g., RSRP
  • FIG. 7 A and FIG. 7B are two diagrams illustrating two example configurations of aggressor WTRU and victim WTRU.
  • FIG. 7 A shown an example, where the aggressor WTRU 711 may cause strong CLI for the close by victim WTRU 712.
  • FIG. 7B shown an example, where the aggressor WTRU 721 may not cause strong CLI for the close by victim WTRU 722.
  • the first WTRU may determine to lower the UL transmission power as a WTRU-oriented method to mitigate CLI caused for the second WTRU.
  • the first WTRU may be configured to reduce the transmission power or upper bound (e.g., maximum of) transmission power based on the determined strength of CLI that may be caused from the first WTRU to the second WTRU.
  • the aggressor WTRU 711 shown in FIG. 7A may determine to use a power backoff value, coefficient, etc. (e.g., referred to as Pl) for CLI mitigation toward the victim WTRU 712.
  • the aggressor WTRU 721 shown in FIG. 7B may determine to use a power backoff value, coefficient, etc. (e.g., referred to as P2) for CLI mitigation toward the victim WTRU 722, where P2 ⁇ PL
  • the first WTRU may report the measured CLI and the employed power backoff value (e.g., to a gNB), for example, via any of UCI, MAC-CE, RRC, etc.
  • the first WTRU may send the report as part of any of a CSI report, a CLI report, on (pre)configured set of PUCCH resources, a (e.g., special) SR, and as part of an enhanced HARQ-ACK codebook, etc.
  • the first WTRU may determine to use one or more configured and/or determined power backoff methods for a configured and/or determined time duration (e.g., referred to as TP Backoff) after detecting that an UL transmission of the first WTRU may (e.g., potentially) cause a (e.g., strong) CLI to a second WTRU.
  • the first WTRU may initiate a timer (e.g., TP Backoff) after reporting the measured CLI (e.g., to a gNB), during which the first WTRU may use the configured and/or determined power backoff for any configured and/or scheduled UL transmission.
  • the first WTRU may use the UL power backoff on the UL transmissions based on the beam directions based on which the first WTRU may have detected, estimated, and/or determined (e.g., strong) CLI being caused for the second WTRU.
  • the first WTRU may continue using power backoff methods for the configured and/or determined time duration (e.g., TP Backoff) or until the first WTRU may receive an instruction/command/indication (e.g., from the gNB) on the UL power control.
  • the first WTRU may determine and/or detect that an UL transmission of the first WTRU may not (e.g., potentially) cause a strong CLI to a second WTRU.
  • the first WTRU may indicate and/or report the measured CLI (e.g., to the gNB).
  • the first WTRU may stop using the configured and/or determined UL power backoff values. The first WTRU may indicate not using the UL power backoff values as part of the report.
  • a first WTRU may be configured, indicated, and/or determine to measure CLI.
  • the first WTRU may determine that the measured CLI may be higher than a corresponding threshold.
  • the first WTRU may measure CLI based on one or more signals, channels, and/or reference signals received from a second WTRU.
  • the first WTRU may be, for example, a (e.g., potential) aggressor WTRU and the second WTRU may be, for example, a (e.g., potential) victim WTRU.
  • the first WTRU may determine that based on measured CLI (e.g., any of WTRU-to-WTRU CLI, inter-WTRU CLI, etc.) if the first WTRU transmits one or more UL transmissions, the transmitted UL data may cause CLI for one or more second WTRUs.
  • measured CLI e.g., any of WTRU-to-WTRU CLI, inter-WTRU CLI, etc.
  • the first WTRU may receive configurations to measure the configured CLI, e.g., in addition to one or more thresholds, for example, via any of RRC, MAC-CE, DCI, etc.
  • the first WTRU may be configured to measure any of CLI-RSRP, CLI-RSSI, DMRS- based CLI-RSRP, DMRS-based CLI-RSSI, SRS-RSRP, etc., where the first WTRU may be configured or receive configurations including corresponding threshold values.
  • the first WTRU may be indicated, configured, and/or determine to decrease the UL transmission power to avoid causing interference (e.g., CLI) on one or more second WTRUs.
  • the first WTRU may dynamically determine the changes to the UL power control parameters and/or coefficients to dynamically mitigate for the (e.g., potential) CLI caused for the second WTRUs.
  • One or more of the following example methods may apply.
  • a first example method may be referred to as UL power backoff.
  • a first WTRU may be configured or determine to apply one or more power back off coefficients, rates, policies, etc.
  • the first WTRU may determine the power backoff coefficient to be used based on a combination of one or more CLI measurements.
  • the first WTRU may measure CLI in DL and UL sub-bands and may determine the UL power backoff ratio based on combination of UL and DL measured CLI values.
  • a second example method may be referred to as cap the UL power to a (e.g., max) value.
  • a first WTRU may be configured, indicated, and/or determine to cap the UL transmission power to a (pre)configured or determined power control maximum (e.g., PC-MAX) value.
  • the first WTRU may determine and/or calculate the PC-MAX value to be used based on one or more of the measured CLI values and corresponding thresholds.
  • a third example method may be referred to as maximum power reduction (MPR).
  • MPR maximum power reduction
  • a first WTRU may be configured, indicated, and/or determine to reduce the (e.g., maximum, upper bound) power for the UL power control.
  • the first WTRU may calculate and/or determine the CLI P-MPR value based on one or more of the measured CLI values and corresponding thresholds.
  • the WTRU may report and/or indicate the selected method and/or the parameters that may be used (e.g., to a gNB).
  • the WTRU may report the UL power backoff ratio in case the UL power backoff method is selected; the WTRU may report the determined and/or calculated PC-MAX, based on which the WTRU may cap the UL power, in case the method on capping the UL power is selected; the WTRU may report the MPR value in case the method on maximum power reduction is selected, and so forth.
  • the WTRU may apply at least one of the actions (e.g., example methods) described herein for uplink transmissions performed between times tO and tl, where tO and/or tl may depend on any of (1) the time when the WTRU may determine that the measurement condition may be satisfied, (2) the time when the WTRU may initiate transmission of a report indicating that the measurement condition may be satisfied, (3) a (e.g., minimum, lower bound) time delay from one of the times (1) or (2), where the a (e.g., minimum, lower bound) time delay may be pre-defined or configured by higher layers, and (4) a (e.g., minimum, lower bound) duration for applying the at least one action, where the (e.g., minimum, lower bound) duration may be pre-defined or configured by higher layers.
  • the actions e.g., example methods described herein for uplink transmissions performed between times tO and tl, where tO and/or tl may depend on any of (1) the time when the WT
  • a WTRU may be configured and/or be indicated and/or receive triggers and/or determine to measure, calculate, and/or report power headroom report (PHR) to indicate the power headroom corresponding to an UL occasion, for example, for a PUSCH transmission.
  • PHR power headroom report
  • FIG. 8 is a diagram illustrating an example of table of parameters that may be included in a PHR configuration.
  • the table shown in FIG. 8 is a non-limiting example of the parameters that may be included in the PHR configuration. One or more of those parameters may be included.
  • the choices for a (e.g., each) parameter are examples. Other choices and parameters may be included in the table.
  • maximum permissible exposure (MPE) may be one of the triggers for PHR reporting.
  • a (e.g., new) trigger for PHR reporting based on measured CLI is described herein.
  • a first WTRU may trigger a PHR if the selected and/or determined and/or configured, and/or indicated power backoff method due to (e.g., based on) power managementmaximum power reduction (P-MPR) may result in decrease in the values of PC-MAX and/or power headroom (PH).
  • P-MPR may be due to (e.g., based on) mitigating interference (e.g., CLI) caused for one or more second WTRUs.
  • mitigating interference e.g., CLI
  • the first WTRU may be configured with CLI-PHR-reporting, where the P-MPR may be due to (e.g., based on) one or more detected and/or measured CLI values being higher than a (pre)configured and/or determined threshold.
  • the first WTRU may receive configuration information on CLI-PHR- reporting, for example via any of RRC, MAC-CE, DCI, etc.
  • the first WTRU may receive the configuration information on CLI-PHR-reporting.
  • the configuration information may include (e.g., indicate) one or more thresholds on measured CLI values, e.g., in addition to indication on whether CLI-PHR-reporting may be enabled or disabled.
  • the first WTRU may determine that the measured, calculated, and/or determined CLI P-MPR that may be applied to mitigate the CLI (e.g., on second WTRUs) may be equal to or larger than a corresponding threshold (e.g., referred to as CLI-PHR- Threshold) since the last (e.g., a preceding) transmission of a PHR from the first WTRU.
  • a corresponding threshold e.g., referred to as CLI-PHR- Threshold
  • the first WTRU may determine that the measured, calculated, and/or determined CLI P-MPR that may be applied to mitigate the CLI (e.g., on second WTRUs) may have changed more than a (pre)configured value, threshold, and/or limit (e.g., referred to as phr- Tx-PowerF actorChange dB) since the last (e.g. a preceding) transmission of a CLI-PHR-report due to (e.g., based on) the measured CLI P-MPR being equal to or larger than corresponding threshold (e.g., CLI-PHR- Threshold).
  • a (pre)configured value, threshold, and/or limit e.g., referred to as phr- Tx-PowerF actorChange dB
  • the PHR may be referred to herein as 'CLI P-MPR report'.
  • the first WTRU may determine that the one or more measured CLI values may be lower than corresponding thresholds, implying that the caused CLI may not be strong.
  • the WTRU may include an indication, as part of the CLI-PHR-reporting, indicating whether the measured CLI may be strong or weak, e.g., indicating if the measured CLI values are higher or lower than corresponding threshold, respectively.
  • the first WTRU may report the measured CLI values as part of the CLI-PHR-reporting.
  • At least one example described herein may also be applicable for a general PHR behavior, e.g., where at least one mentioned CLI measurement result (e.g., being higher than a CLI-related threshold) may be used for triggering the (e.g., general) PH reporting (e.g., (e.g., actual) PHR and/or virtual PHR, etc.).
  • This may allow to improve efficiency of PHR by considering the (e.g., new) condition of the measured CLI-related condition (e.g., being higher than the CLI-related threshold), e.g., in addition to any of the pathloss change condition, the MPR change condition, and the MPE-related condition.
  • the first WTRU may determine to trigger the PH reporting in a case where the measured CLI-related condition is satisfied (e.g., the measured and/or calculated CLI is higher than a corresponding threshold).
  • This CLI-triggered PH reporting may take place (e.g., even) if other conditions (e.g., any of the pathloss change condition, the MPR change condition, and the MPE-related condition) are not met.
  • the first WTRU may report the PH at a first time unit (e.g., slot(s) and/or symbol(s)).
  • the first WTRU may determine, e.g., at a second time unit (e.g., after the first time unit) that the measured CLI-related condition may no longer be satisfied (e.g., based on a new (e.g., subsequent) CLI measurement, etc.).
  • the first WTRU may determine that the measured and/or calculated CLI may be lower than the corresponding threshold.
  • the first WTRU may restore the PHR and/or send an indication that the first WTRU may increase a WTRU Tx power level (e.g., the PC-MAX).
  • the WTRU may increase the WTRU Tx power level (e.g., the PC-MAX) to a (pre)configured, and/or (pre)indicated, and/or (pre)determined MAX value.
  • the WTRU may report and/or indicate the WTRU Tx power level (e.g., the PC-MAX) any of as part of PH report, as part of a following CSI report, via a specific SR, etc.
  • a WTRU may receive one or more dynamic or configured assignments to receive one or more PDSCH.
  • the configurations may include information on one or more DMRS resources that may be included in the configured PDSCH.
  • the DMRS configuration (e.g., information) may include any of DMRS symbols, a DMRS position in frequency domain (e.g., REs), a DMRS type, a group, a length, a seed, a CDM group, etc.
  • the WTRU may receive an indication to (enable to) measure CLI and/or SINR based on the configured DMRS resources of the PDSCH.
  • the indication may include the number of DMRS resources and information on the DMRS resources to be used for the (e.g., configured) CLI and/or SINR measurement.
  • the indication may include one or more of time-windows, frequency-windows, and/or DMRS REs (e.g., exact DMRS REs) to be used for DMRS-based CLI and/or SINR measurement.
  • the WTRU may determine the number of DMRS resources and which ones to be used for measurement (e.g., for the purpose of accuracy). In such a case, the WTRU may report the number of DMRS that may be used and the ones that may be used as part of the report.
  • the WTRU may measure any of RSRP and RSSI corresponding to the received DMRS (e.g., DMRS-based RSRP and DMRS-based RSSI, respectively) received along with the configured PDSCH.
  • the WTRU may report any of the measured DMRS-based RSRP, the measured DMRS-based RSSI, the calculated SINR, etc. (e.g., as part of any of CLI reporting, CSI reporting, SR, HARQ-ACK, etc ).
  • the WTRU may report a flag indication in case any of the measured RSRP, SINR, etc. are higher or lower than corresponding thresholds (e.g., via any of UCI, MAC-CE, or along with NACK transmission in an enhanced (e.g., modified) codebook).
  • a WTRU may (be configured to) measure one or more DMRS, associated with a DL signal or channel (e.g., PDSCH, PDCCH, etc.), for generating a measurement metric, e.g., any of CLI, DMRS-based RSRP, DMRS-based RSSI, SINR, etc., where the WTRU may receive the DL signal or channel based on receiving a scheduling grant, e.g., via any of a DCI, and a higher-layer signaling (e.g., any of configured-grant, semi-persistent-scheduling), etc.
  • a scheduling grant e.g., via any of a DCI
  • a higher-layer signaling e.g., any of configured-grant, semi-persistent-scheduling
  • Measuring the one or more DMRS for generating the measurement metric may be performed when at least one of the following conditions is satisfied.
  • the WTRU may perform the one or more DMRS measurement if the WTRU receives an explicit indication to perform measuring the one or more DMRS for generating the measurement metric, e.g., in addition to performing demodulation of the one or more DMRS to decode the received DL signal or channel (associated with the one or more DMRS).
  • the explicit indication may be received via the DCI scheduling the DL signal or channel.
  • the WTRU may perform the one or more DMRS measurement based on a rule (e.g., a rule-based determination for measuring the one or more DMRS), e.g., every N-th time (and/or within a configured window) of receiving a same type (e.g., PDSCH) of the DL signal or channel, where N may be an integer such as e.g., 2, 3, 5, 10, etc. being any of pre-indicated, determined, and pre-defined.
  • a rule e.g., a rule-based determination for measuring the one or more DMRS
  • N may be an integer such as e.g., 2, 3, 5, 10, etc. being any of pre-indicated, determined, and pre-defined.
  • the WTRU may determine a set of DMRS REs (e.g., corresponding to the one or more DMRS) to be used for the measurement (e.g., reactive CLI measurement) for generating the measurement metric.
  • the set of DMRS REs may be, for example, a subset of the whole DMRS REs associated with the DL signal or channel.
  • the WTRU may be scheduled to receive the DL signal or channel (e.g., PDSCH, PDCCH).
  • the WTRU may use the (e.g., whole) M DMRS REs for decoding the DL signal or channel and may use the (e.g., subset of) L REs for generating the measurement metric.
  • FIG. 9 is a diagram illustrating an example of measurement based on the one or more DMRS in received DL signal or channel (e.g., any of DL data, PDSCH, PDCCH, RS, etc.).
  • a first WTRU 91 and a second WTRU 92 may be (e.g., potential) aggressor WTRUs to impact to a third WTRU 93, e.g., causing CLI, when the first WTRU 91 and/or the second WTRU 92 transmit a UL signal or channel which may cause CLI for the third WTRU 93 to receive a DL signal or channel.
  • a WTRU e.g., the third WTRU 93
  • may receive a first DL scheduling grant e.g., via a DCI, or via a higher layer signaling
  • a first DL signal or channel e.g., PDSCH, PDCCH
  • the WTRU may receive the first DL signal or channel based on receiving first one or more DMRS associated with the first DL signal or channel, e.g., used for any of channel estimation, demodulation, decoding, and post-processing actions.
  • the WTRU may transmit an ACK (if the decoding is successful) or a NACK (if the decoding is not successful, etc.).
  • the WTRU may receive a second DL scheduling grant (e.g., via a DCI, or via a higher layer signaling) indicating to receive a second DL signal or channel (e.g., PDSCH, PDCCH).
  • a second DL scheduling grant e.g., via a DCI, or via a higher layer signaling
  • a second DL signal or channel e.g., PDSCH, PDCCH
  • the WTRU may receive the second DL signal or channel based on receiving second one or more DMRS (e.g., corresponding to M REs) associated with the second DL signal or channel, e.g., used for any of channel estimation, demodulation, decoding, and post-processing actions, and/or the WTRU may perform measurement (e.g., reactive CLI measurement) for generating the measurement metric (e.g., any of CLI, DMRS-based RSRP, DMRS-based RSSI, SINR, etc.) by using L REs of the second one or more DMRS (that may correspond to M REs), where L may be less than or equal to M.
  • DMRS e.g., corresponding to M REs
  • the WTRU may transmit an ACK (if the decoding is successful) or a NACK (if the decoding is not successful, etc.).
  • the WTRU may transmit (e.g., report) one or more measurement results (e.g., value(s) corresponding to the measurement metric) and/or perform an action for CLI handling based on the generated measurement metric.
  • the action for CLI handling may comprise a post-processing operation to mitigate or cancel the CLI when receiving a DL signal or channel.
  • the measurement metric may be an SINR.
  • the WTRU may (be configured to) derive the SINR to be based on a (e.g., desired) power term divided by an interference power term.
  • the WTRU may (be configured to) derive the (e.g., desired) power term based on a separate (e.g., different) measurement, e.g., channel measurement, etc., based on a DL RS (e.g., CSLRS).
  • the (e.g., desired) power term may be derived based on the NZP CSI-RS based channel measurement which may provide the RS-based RSRP value.
  • the WTRU may perform sequence-based correlation between a received signal and the known CSLRS (sequence) complex value on a RE (e.g., each RE) of the CSLRS resource.
  • the WTRU may derive a representative metric of the RS-based RSRP based on combining the correlation results from the (e.g., whole) REs of the CSLRS resource, which may suppress random noise components in the combining process and may generate a reliable representative value of RSRP that may correspond to the (e.g., desired) power term.
  • the WTRU may (be configured to) derive the (e.g., desired) power term based on the DMRS (e.g., corresponding to the L REs), e.g., out of the M REs.
  • the (e.g., desired) power term may be derived based on the DMRS which may provide the DMRS- based RSRP value.
  • the WTRU may perform sequence-based correlation between a received signal and the known DMRS complex value on a RE (e.g., each) RE of the L REs.
  • the WTRU may derive a representative metric of the DMRS-based RSRP based on combining the correlation results from the (e.g., whole) L REs, which may suppress random noise components in the combining process and may generate a reliable representative value of RSRP that may correspond to the (e.g., desired) power term.
  • the WTRU may (be configured to) derive the interference power term based on the DMRS-based sequence correlation components (e.g., by subtracting the DMRS-based sequence correlation components from the received signal on the L REs).
  • the subtraction of the DMRS-based sequence correlation components from the received signal on the L REs may represent left-over interference components on the L REs because the DL DMRS components may be subtracted out by the correlation process (due to (e.g., based on) the known sequence characteristics of the DMRS to the WTRU).
  • the interference power term may (e.g., further) be derived based on a CLI-RSSI (e.g., energy-based) measurement, e.g., measured on a configured CLI-measurement resource.
  • the WTRU may generate the SINR and may report the SINR (e.g., to a gNB).
  • the WTRU may receive the scheduling grant (e.g., the DCI) configuring "reactive CLI measurement" based on DMRS received as part of a configured/scheduled DL data (e.g., the DL signal or channel) that may be scheduled for the WTRU.
  • the WTRU may perform CLI and/or SINR measurements based on the scheduled/configured PDCCH/PDSCH DMRS.
  • the measurement may be performed on resources configured to receive DL data and may not be performed on a separate CLI/SINR measurement resource (e.g., any of NZP/ZP CSLRS, CSLIM resources, legacy CLI/SINR measurement resources, etc.), which may allow to reduce measurement resource overhead (e.g., via the “reactive” CLI measurement in response to the given scheduled signal or channel).
  • a separate CLI/SINR measurement resource e.g., any of NZP/ZP CSLRS, CSLIM resources, legacy CLI/SINR measurement resources, etc.
  • the WTRU may receive one or more dynamic or configured grants to receive one or more PDSCH.
  • the configurations may include information on one or more DMRS resources that may be included in the configured PDSCH.
  • the DMRS configuration may include any of DMRS symbols, DMRS position in frequency domain (REs), DMRS type, group, length, seed, CDM group, etc.
  • the WTRU may receive an (explicit) indication to (enable to) measure CLI and/or SINR based on the DMRS resources of the configured PDSCH.
  • the indication may include the number of DMRS resources and the information on the DMRS resources to be used for the configured CLI and/or SINR measurement.
  • the indication may include (e.g., indicate) one or more of time-windows, frequency -windows, and/or (e.g., exact) DMRS REs to be used for DMRS-based CLI and/or SINR measurement, e.g., as a part of the explicit indication for determining whether the at least one condition is met or not.
  • the WTRU may determine the number of DMRS resources (e.g., the L REs) and which ones to be used for measurement (e.g., for the purpose of accuracy).
  • the WTRU may report the number of DMRS (e.g., the L REs) that may be used and which ones that may be used as part of the report.
  • the WTRU may measure RSRP and/or RSSI corresponding to the received DMRS (e.g., DMRS-based RSRP and DMRS-based RSSI, respectively) received along with the configured PDSCH.
  • the WTRU may report any of the measured DMRS-based RSRP, DMRS-based RSSI, and calculated SINR, etc., e.g., as part of any of CLI reporting, CSI reporting, scheduling request (SR), HARQ-ACK feedback, etc.
  • the WTRU may (be configured to) report a flag indication in case the measured RSRP, SINR, etc.
  • a gNB that may receive the WTRU feedback, e.g., including the flag indication
  • the CLI measurements performed by the WTRU may be not based on extra measurement resource. Performing CLI measurements based on DMRS associated with a scheduled DL signal or channel may allow to reduce measurement resource overhead.
  • FIG. 10 is a diagram illustrating an example method 1000 for CLI measurement and reporting based on DMRS.
  • the method 1000 may be implemented in a first WTRU.
  • the first WTRU may include circuitry including any of transmitter, a receiver, a processor, and a memory.
  • the circuitry may be configured to carry out the method 1000.
  • the method 1000 may include receiving cross-link (e.g., interference) configuration information indicating a plurality of cross-link interference measurement resources.
  • the method 1000 may include receiving an indication to measure cross-link interference.
  • the indication may comprise scheduling information associated with a second WTRU.
  • the method 1000 may include determining one or more cross-link interference measurement resources from the plurality of cross-link interference measurement resources based on the cross-link (e.g., interference) configuration information and the scheduling information associated with the second WTRU.
  • the one or more cross-link interference measurement resources may be determined from the plurality of cross-link interference measurement resources based on the one or more cross-link interference measurement resources any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) being at a range of the indicated scheduled resources.
  • the method 1000 may include receiving one or more reference signals associated with the second WTRU.
  • the method 1000 may include performing one or more cross-link interference measurements in the (e.g., determined) one or more cross-link interference measurement resources based on the one or more reference signals associated with the second WTRU. As shown at 1060, the method 1000 may include transmitting report information indicating any of the one or more cross-link interference measurements and the (e.g., determined) one or more cross-link interference measurement resources.
  • the cross-link (e.g., interference) configuration information may indicate any of time resources and frequency resources for the plurality of cross-link interference measurement resources.
  • the plurality of cross-link interference measurement resources may be any of periodic and semi-persistent.
  • the plurality of cross-link interference measurement resources may be included in any of uplink sub-bands, downlink sub-bands, sub-band non-overlapping full duplex (SBFD) symbols and dynamic time division duplexing (d-TDD) symbols.
  • SBFD sub-band non-overlapping full duplex
  • d-TDD dynamic time division duplexing
  • the indication to measure cross-link interference may indicate a type of cross-link interference measurement.
  • the type of cross-link interference measurement may indicate any of a demodulation reference signal (DMRS)-based cross-link interference (CLI) reference signal received power (RSRP) and a DMRS-based CLI received signal strength indicator (RSSI).
  • DMRS demodulation reference signal
  • CLI cross-link interference
  • RSSI DMRS-based CLI received signal strength indicator
  • the one or more reference signals associated with the second WTRU may be received from the second WTRU.
  • the scheduling information (e.g., scheduled resources) associated with the second WTRU may indicate any of an uplink grant time, an uplink grant frequency, a number of configured resource blocks, one or more DMRS symbols, a DMRS position in frequency, a DMRS type, a DMRS group, a DMRS length, a DMRS seed, a DMRS pattern, and a DMRS code division multiplexing (CDM) group.
  • CDM code division multiplexing
  • the one or more reference signals associated with the second WTRU may be (e.g., received from a base station and) directed to the second WTRU.
  • the scheduling information (e.g., scheduled resources) associated with the second WTRU may indicate any of a downlink assignment time, a downlink assignment frequency, a number of configured resource blocks, one or more DMRS symbols, a DMRS position in frequency, a DMRS type, a DMRS group, a DMRS length, a DMRS seed, a DMRS pattern, and a DMRS code division multiplexing (CDM) group.
  • CDM DMRS code division multiplexing
  • the indication to measure cross-link interference may indicate a beam direction for performing the one or more cross-link interference measurements.
  • the beam direction may be associated with a downlink beam direction configured for the first WTRU.
  • the beam direction may be indicated from a plurality of receive beam directions configured for the first WTRU.
  • the one or more cross-link interference measurement resources may be determined in an uplink sub-band.
  • the one or more cross-link interference measurement resources may be determined in a downlink sub-band.
  • the one or more reference signals may be received in one or more first symbols, and determining one or more cross-link interference measurement resources from the plurality of cross-link interference measurement resources may comprise determining a first cross-link interference measurement resource based on the first cross-link interference measurement resource being included in the one or more first symbols.
  • the one or more reference signals may be received in one or more first symbols, and determining one or more cross-link interference measurement resources from the plurality of cross-link interference measurement resources may comprise determining a second cross-link interference measurement resource based on the second cross-link interference measurement resource being partially included in the one or more first symbols.
  • the method 1000 may comprise using one or more scaling factors for determining the cross-link interference based on the one or more cross-link interference measurements performed in the second cross-link interference measurement resource.
  • FIG. 11 is a diagram illustrating an example method 1100 for dynamic CLI mitigation based on DMRS-based CLI measurement.
  • the method 1100 may be implemented in a first WTRU.
  • the first WTRU may include circuitry including any of transmitter, a receiver, a processor, and a memory.
  • the circuitry may be configured to carry the method 1100.
  • the method 1100 may include receiving cross-link configuration information indicating a plurality of cross-link interference measurement resources.
  • the method 1100 may include receiving an indication to measure cross-link interference.
  • the indication may comprise scheduling information associated with a second WTRU.
  • the method 1100 may include determining one or more cross-link interference measurement resources from the plurality of cross-link interference measurement resources based on the cross-link configuration information and the scheduling information associated with the second WTRU. As shown at 1140, the method 1100 may include receiving one or more reference signals associated with the second WTRU. As shown at 1150, the method 1100 may include performing one or more cross-link interference measurements in the one or more cross-link interference measurement resources based on the one or more reference signals associated with the second WTRU. As shown at 1160, the method 1100 may include performing an uplink transmission with a reduced transmission power based on the one or more cross-link interference measurements performed in the one or more cross-link interference measurement resources.
  • the one or more reference signals associated with the second WTRU may be received from the second WTRU.
  • the one or more reference signals associated with the second WTRU may be (e.g., received from a base station and) directed to the second WTRU.
  • the one or more cross-link interference measurements may comprise demodulation reference signal (DMRS)-based reference signal received power (RSRP) measurements.
  • DMRS demodulation reference signal
  • RSRP reference signal received power
  • the method 1100 may further comprise determining that the one or more cross-link interference measurements may satisfy a condition.
  • the uplink transmission may be performed with the reduced transmission power based on the determination of that the one or more cross-link interference measurements may satisfy the condition.
  • performing an uplink transmission with a reduced transmission power may comprise applying an uplink power backoff method.
  • performing an uplink transmission with a reduced transmission power may comprise caping a transmission power to a (e.g., first) value.
  • performing an uplink transmission with a reduced transmission power may comprise reducing a maximum power of an uplink power control.
  • the method 1100 may further comprise triggering a power headroom report based on the one or more cross-link interference measurements.
  • FIG. 12 is a diagram illustrating an example method 1200 for CLI measurement and reporting based on DMRS.
  • the method 1200 may be implemented in a first network element such as e.g., a base station.
  • the first network element may include circuitry including a transmitter, a receiver, a processor, and a memory.
  • the circuitry may be configured to carry the method 1200.
  • the method 1200 may include transmitting to a first WTRU, cross-link interference configuration information indicating a plurality of cross-link interference measurement resources.
  • the method 1200 may include transmitting to the first WTRU, an indication to measure cross-link interference.
  • the indication may indicate scheduled resources for transmissions between a second WTRU and a second network element.
  • the method 1200 may include receiving from the first WTRU, report information indicating one or more cross-link interference measurements performed by the first WTRU in one or more cross-link interference measurement resources that may be any of (i) fully overlapping with the indicated scheduled resources, (ii) partially overlapping with the indicated scheduled resources and (iii) at a range of the indicated scheduled resources.
  • FIG. 13 is a diagram illustrating an example method 1300 for DMRS-based measurement based on scheduled downlink data.
  • the method 1300 may be implemented in a WTRU.
  • the WTRU may include circuitry including a transmitter, a receiver, a processor, and a memory.
  • the circuitry may be configured to carry the method 1300.
  • the method 1300 may include receiving information indicating one or more downlink resources for one or more downlink transmissions.
  • the one or more downlink resources may include one or more DMRS resources.
  • the method 1300 may include receiving an indication to measure cross-link interference in the one or more downlink resources.
  • the indication may indicate (i) a number of DMRS resources to use for cross-link interference measurement and (ii) which DMRS resources of the one or more DMRS resources to use for crosslink interference measurement.
  • the method 1300 may include performing one or more cross-link interference measurements in the one or more DMRS resources.
  • the method 1300 may include transmitting report information indicating the one or more cross-link interference measurements.
  • CN Core Network e.g. LTE packet core or NR core
  • CU Central Unit D2D Device to Device transmissions (e.g. LTE Sidelink) DC Dual Connectivity DCI Downlink Control Information DL Downlink DMRS Demodulation Reference Signal DRB Data Radio Bearer DU Distributed Unit EN-DC E-UTRA - NR Dual Connectivity EPC Evolved Packet Core FD-CDM Frequency Domain-Code Division Multiplexing FDD Frequency Division Duplexing FDM Frequency Division Multiplexing FDRA Frequency Division Resource Allocation ICI Inter-Cell Interference ICIC Inter-Cell Interference Cancellation IP Internet Protocol LBT Listen-Before-Talk LCH Logical Channel LCID Logical Channel Identity LCP Logical Channel Prioritization LLC Low Latency Communications LTE Long Term Evolution e.g.
  • any characteristic, variant or embodiment described for a method is compatible with an apparatus device comprising means for processing the disclosed method, with a device comprising circuitry, including any of a transmitter, a receiver, a processor and a memory, the circuitry being operable to process the disclosed method, with a computer program product comprising program code instructions and with a non-transitory computer-readable storage medium storing program instructions.
  • any characteristic, variant or embodiment described for a WTRU is compatible with an (e.g., infrastructure) network element of the cellular network.
  • infrared capable devices i.e., infrared emitters and receivers.
  • the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.
  • video or the term “imagery” may mean any of a snapshot, single image and/or multiple images displayed over a time basis.
  • the terms “user equipment” and its abbreviation “UE”, the term “remote” and/or the terms “head mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like.
  • WTRU wireless transmit and/or receive unit
  • any of a number of embodiments of a WTRU any of a number of embodiments of a WTRU
  • a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some
  • FIGs. 1 A-1D Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D.
  • various disclosed embodiments herein supra and infra are described as utilizing a head mounted display.
  • a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.
  • the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor.
  • Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
  • Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention.
  • the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims.
  • the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.
  • processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit (“CPU”) and memory.
  • CPU Central Processing Unit
  • memory In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being “executed,” “computer executed” or “CPU executed.”
  • an electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals.
  • the memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.
  • the data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU.
  • the computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.
  • any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium.
  • the computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.
  • a processor of a mobile unit may be executed by a processor of a mobile unit, a network element, and/or any other computing device.
  • the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs.
  • a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc.
  • a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities).
  • a typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
  • any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
  • the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
  • the terms “any of' followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include “any of,” “any combination of,” “any multiple of,” and/or “any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items.
  • the term “set” is intended to include any number of items, including zero.
  • the term “number” is intended to include any number, including zero.
  • the term “multiple”, as used herein, is intended to be synonymous with “a plurality”.
  • a range includes each individual member.
  • a group having 1-3 cells refers to groups having 1, 2, or 3 cells.
  • a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé mis en œuvre dans une première WTRU. Le procédé peut comprendre la réception d'une indication pour mesurer une interférence de liaison croisée (CLI). Dans divers modes de réalisation, l'indication peut comprendre des informations de planification associées à une seconde WTRU. Le procédé peut consister à déterminer une ou plusieurs ressources de mesure de CLI parmi la pluralité de ressources de mesure de CLI sur la base des informations de configuration de liaisons croisées et des informations de planification associées à la seconde WTRU. Le procédé peut consister à recevoir un ou plusieurs signaux de référence associés à la seconde WTRU et à effectuer une ou plusieurs mesures de CLI dans la ou les ressources de mesure de CLI sur la base du ou des signaux de référence associés à la seconde WTRU. Le procédé peut comprendre la transmission d'informations de rapport indiquant l'une quelconque de la ou des mesures de CLI et de la ou des ressources de mesure de CLI.
PCT/US2025/013515 2024-02-01 2025-01-29 Procédés, architectures, appareils et systèmes de mesure d'interférence de liaison croisée réactive dans un multiplexage en duplex intégral sans chevauchement de sous-bande et multiplexage par répartition dynamique dans le temps Pending WO2025165819A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463627865P 2024-02-01 2024-02-01
US63/627,865 2024-02-01

Publications (1)

Publication Number Publication Date
WO2025165819A1 true WO2025165819A1 (fr) 2025-08-07

Family

ID=94733824

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/013515 Pending WO2025165819A1 (fr) 2024-02-01 2025-01-29 Procédés, architectures, appareils et systèmes de mesure d'interférence de liaison croisée réactive dans un multiplexage en duplex intégral sans chevauchement de sous-bande et multiplexage par répartition dynamique dans le temps

Country Status (1)

Country Link
WO (1) WO2025165819A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210144577A1 (en) * 2019-05-02 2021-05-13 Qualcomm Incorporated User equipment measurement for cross-link interference
US20220014954A1 (en) * 2020-07-10 2022-01-13 Qualcomm Incorporated Method and apparatus for cli reporting
US20230327787A1 (en) * 2022-04-07 2023-10-12 Qualcomm Incorporated Aspects for cross-link interference measurement

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210144577A1 (en) * 2019-05-02 2021-05-13 Qualcomm Incorporated User equipment measurement for cross-link interference
US20220014954A1 (en) * 2020-07-10 2022-01-13 Qualcomm Incorporated Method and apparatus for cli reporting
US20230327787A1 (en) * 2022-04-07 2023-10-12 Qualcomm Incorporated Aspects for cross-link interference measurement

Similar Documents

Publication Publication Date Title
US20250038906A1 (en) Methods, apparatus, and systems for downlink (dl) power adjustment and ue behaviors/procedures for cross division duplex (xdd)
US20230318686A1 (en) Methods, architectures, apparatuses and systems for dynamic determination of processing time
US20240107525A1 (en) Pucch-related latency and coverage enhancement for subband non-overlapping full duplex
US20250203588A1 (en) Power control and link adaptation associated with cross-division duplex (xdd)
EP4497214A1 (fr) Atténuation de brouillage basée sur la détection dans une opération duplex nr
JP2025515449A (ja) Ｎｒデュプレックスにおける共同ビーム管理のための方法、アーキテクチャ、装置、及びシステム
EP4616548A1 (fr) Appareil et procédés de gestion de faisceau pour une liaison d'accès dans un répéteur commandé par réseau nouvelle radio (nr-ncr)
US20250279818A1 (en) Methods for beam failure detection and recovery
US20250202558A1 (en) Methods, architectures, apparatuses and systems for channel state information measurement and reporting in wireless communications
WO2024072772A1 (fr) Procédés, architectures, appareils et systèmes de configuration en duplex intégral sans chevauchement de sous-bande
EP4566232A1 (fr) Amélioration de latence et de couverture pour un duplex intégral sans chevauchement de sous-bande
WO2025165819A1 (fr) Procédés, architectures, appareils et systèmes de mesure d'interférence de liaison croisée réactive dans un multiplexage en duplex intégral sans chevauchement de sous-bande et multiplexage par répartition dynamique dans le temps
US20250344170A1 (en) Random Access for Estimation SSBs in AIML Systems
WO2025072455A1 (fr) Procédés, architectures, appareils et systèmes pour des mesures de blocage de liaison montante, de signal sur interférence plus bruit (sinr), et rapport dans des communications en duplex intégral sans chevauchement de sous-bande (sbfd) et duplex à répartition dans le temps (tdd) dynamiques
WO2025174693A1 (fr) Procédés, appareils et systèmes de configuration d'occasions de canal d'accès aléatoire dans des scénarios en duplex intégral sans chevauchement de sous-bande
WO2025072459A1 (fr) Procédés, architectures, appareils et systèmes pour des mesures conditionnelles de signal sur interférence plus bruit (sinr) de cellule non de desserte dans des communications en duplex intégral sans chevauchement de sous-bande (sbfd) et de duplexage par répartition dans le temps (tdd) dynamique
WO2025096497A1 (fr) Procédés, architectures, appareils et systèmes pour la sélection d'une séquence de signaux de réveil à faible puissance (lp-wus) en fonction de l'état du stockage d'énergie
WO2025034791A1 (fr) Procédés, architectures, appareils et systèmes de fonctionnement en duplex intégral sans chevauchement de sous-bande d'une unité de transmission-réception sans fil
WO2025072463A1 (fr) Procédés, architectures, appareils et systèmes pour des mesures de rapport signal sur interférences plus bruit (sinr) et d'interférences inter-couche (cli) dans des communications à duplex integral sans chevauchement de sous-bande (sbfd) et de duplexage par répartition dans le temps (tdd) dynamique
WO2024163442A1 (fr) Procédés, architectures, appareils et systèmes de sélection et de resélection de cellules à l'aide d'une interférence de liaison croisée (cli) pour un duplex intégral de sous-bande
WO2024233760A1 (fr) Dispositif et procédé de configuration de srs hiérarchique et de mesure d'interférence de liaison croisée (cli) sur des ressources partagées dans des systèmes de duplex intégral sans chevauchement de sous-bande (sbfd)
WO2024233757A1 (fr) Procédés de gestion de transmission apériodique de srs pour une mesure d'interférence de liaison croisée (cli) dans des systèmes de duplex intégral sans chevauchement de sous-bande (sbfd)
WO2024233755A1 (fr) Procédés d'association d'une transmission apériodique de srs et d'une mesure d'interférence de liaison croisée (cli) dans des systèmes de duplex intégral sans chevauchement de sous-bande (sbfd)
WO2025072656A1 (fr) Fonctionnement en duplex intégral avec restrictions de faisceaux
WO2025029944A1 (fr) Cadre de signalisation pour configuration de liaison montante à faisceaux multiples

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25707597

Country of ref document: EP

Kind code of ref document: A1