Methods for enabling / disabling upload transmission in sub-band full duplex symbols with download reference signals based on spatial relation

EP4758984A1Pending Publication Date: 2026-06-17INTERDIGITAL PATENT HOLDINGS INC

Patent Information

Authority / Receiving Office
EP · EP
Patent Type
Applications
Current Assignee / Owner
INTERDIGITAL PATENT HOLDINGS INC
Filing Date
2024-08-07
Publication Date
2026-06-17

AI Technical Summary

Technical Problem

In advanced wireless network systems, uplink transmissions in sub-band full duplex (SBFD) scenarios can cause degradation of synchronization symbol block (SSB) measurements for the wireless transmit receive unit (WTRU) itself, inter-WTRU cross-link interference (CLI), and self-interference at the gNB due to overlapping with downlink reference signals (RS) in synchronization symbol blocks.

Method used

A method implemented in a WTRU to receive configuration information for downlink RSs and power control settings, and to adjust the power of uplink transmissions based on whether the associated downlink RS is protected or unprotected in SBFD symbols, allowing for efficient transmission in overlapping symbols.

Benefits of technology

The method enables efficient uplink transmission in SBFD symbols without degrading SSB measurements, reducing inter-WTRU CLI, and minimizing self-interference at the gNB, thereby improving overall network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2024041263_13022025_PF_FP_ABST
    Figure US2024041263_13022025_PF_FP_ABST
Patent Text Reader

Abstract

Methods are described for sub-band full duplex communication by a wireless transmit / receive unit (WTRU). The methods include receiving first configuration information for one or more downlink (DL) reference signals (RSs); receiving second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols, the second configuration information indicates whether to adjust power of an associated UL transmission; and transmitting an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs.
Need to check novelty before this filing date? Find Prior Art

Description

METHODS FOR ENABLING / DISABLING UPLOAD TRANSMISSION IN SUB-BAND FULL DUPLEXSYMBOLS WITH DOWNLOAD REFERENCE SIGNALS BASED ON SPATIAL RELATIONCROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 531 , 203 filed August 7, 2023, the contents of which are hereby incorporated by reference herein.BACKGROUND

[0002] In advanced wireless network systems, an uplink (UL) sub-band may be configured in a synchronization symbol block (SSB) symbol. In some scenarios a sub-band full duplex (SBFD)-aware wireless transmit receive unit (WTRU) may transmit in an UL sub-band that overlaps with an SSB symbol.

[0003] When a WTRU transmits UL in a time instance that overlaps with a symbol including a reference signal (RS) (e.g., SSB and / or channel state information reference symbol (CSI-RS)), the UL transmission may cause degradation on the SSB measurement for the WTRU itself. The UL transmission in a symbol that includes a DL RS may also result in inter-WTRU cross-link interference (CLI) for close by WTRUs that need to measure as RS (SSB or CSI-RS). Moreover, receiving UL in the same symbol as a DL RS may cause selfinterference at a gNB, for example due to the different power control settings for SSB transmission.SUMMARY

[0004] Aspects features and advantages of the disclosed embodiments, may address one or more of the foregoing needs or desires through methods and devices for preparing and transmitting a segmented compressed beamforming / channel quality indictor (CQI) report described hereinafter.

[0005] In embodiments a method implemented in a WTRU includes: receiving first configuration information for one or more downlink (DL) reference signals (RSs); receiving second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols the second configuration information indicates whether the WTRU shall adjust power of an associated UL transmission; and transmitting an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs. Additionally / alternatively, the method may include: wherein, on a condition that it is determined to transmit an UL transmission without a power adjustment and the first DL RS is unprotected, transmitting the UL transmission based on the first power control information. Additionally / alternatively, the method may include wherein, on a condition that it is determined to transmit an UL transmission with a power adjustment and the first DL RS is unprotected, transmitting the UL transmission using the resource based on the second power control information. Additionally / alternatively, the method may include, wherein, on acondition that the first DL RS is protected, it is determined that a UL transmission is not performed. Additionally / altematively, the method may include receiving one or more indications for beam indexes that are protected or unprotected. Additionally / altematively, the method may include wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a bitmap indication. Additionally / altematively, the method may include wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a set of protected DL RSs and a set of unprotected DL RSs. Additionally / altematively, the method may include transmitting a report indicating that the UL transmission was not performed. Additionally / altematively, the method may include wherein one of the DL RSs is indicated to be protected based on a beam direction for UL transmission. Additionally / altematively, the method may include wherein one of the DL RSs is indicated to be unprotected based on a beam direction for UL transmission.

[0006] In embodiments, a WTRU comprises: a processor and a transceiver, wherein the processor is configured to cause the transceiver to: receive first configuration information for one or more downlink (DL) reference signals (RSs); receive second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols the second configuration information indicates whether the WTRU shall adjust power of an associated UL transmission; and transmit an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs. Additionally / altematively, the processor is further configured to cause the transceiver to transmit the UL transmission based on the first power control information on a condition that no power adjustment is required and the first DL RS is unprotected. Additionally / altematively, the processor is further configured to cause the transceiver to transmit the UL transmission based on the second power control information on a condition that a power adjustment is required and the first DL RS is unprotected. Additionally / altematively, the processor is further configured to cause the transceiver to not transmit a UL transmission on a condition that the first DL RS is protected. Additionally / altematively the method may include processor is further configured to cause the transceiver to receive one or more indications for beam indexes that are protected or unprotected. Additionally / altematively, the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a bitmap indication. Additionally / altematively, the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a set of protected DL RSs and a set of unprotected DL RSs. Additionally / altematively, the processor is further configured to cause the transceiver to transmit a report indicating that the UL transmission was not performed. Additionally / altematively, one of the DL RSs is indicated to be protected based on a beam direction for UL transmission. Additionally / altematively, one of the DL RSs is indicated to be unprotected based on a beam direction for UL transmission.BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0008] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0009] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0010] 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 according to an embodiment;

[0011] FIG. 1 D 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. 1A according to an embodiment;

[0012] FIG. 2 is an example of SBFD configuration in TDD framework;

[0013] FIG. 3 is an example of SSB symbols overlapping with SBFD;

[0014] FIG. 4 is an example diagram of protected and unprotected SSB symbols;

[0015] FIG. 5 is an example diagram of beam direction relation between DL reference signals and UL beams;

[0016] FIG. 5A is an example diagram of angles of arrival of a plurality of signals;

[0017] FIG. 5B is an example diagram of an angle of departure of a UL transmission;

[0018] FIG. 6 is an example of group indication of protected and unprotected DL RSs;

[0019] FIG. 7 is an example process for transmitting UL in an SBFD sub-band;

[0020] FIG. 8 is a further example process for transmitting UL in an SBFD sub-band; and

[0021] FIG. 9 is a further example process for dynamic updating of protection status of downlink reference symbols for transmitting UL in an SBFD sub-band.DETAILED DESCRIPTION

[0022] FIG. 1A is a 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. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0023] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, 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. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive wireless signals and may include a user equipment (WTRU), 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 the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a WTRU.

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

[0025] The base station 114a may be part of the RAN 104, 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, and the like. 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. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in oneembodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

[0027] More specifically, as noted above, the 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. For example, the base station 114a in the RAN 104 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 (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

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

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

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, 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).

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

[0032] The base station 114b in FIG. 1A 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., foruse by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0033] The RAN 104 may be in communication with the CN 106, 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. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0034] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), 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. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0035] 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). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0036] FIG. 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0037] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), 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. 1B 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 in an electronic package or chip.

[0038] 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. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, 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.

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

[0040] 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. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, 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.

[0041] 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. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removablememory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, 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).

[0042] 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. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li- ion), etc.), solar cells, fuel cells, and the like.

[0043] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information 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.

[0044] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (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. The 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, a humidity sensor and the like.

[0045] 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 UL (e.g., for transmission) and DL (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). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some orall of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).

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

[0047] The RAN 104 may include 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. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

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

[0049] 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 the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0050] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, 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.

[0051] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring 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.

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

[0053] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, 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. In addition, 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.

[0054] Although the WTRU is described in FIGS. 1A-1 D 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.

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

[0056] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to 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). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z 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.

[0057] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, 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. 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. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in 802.11 systems. For CSMA / CA, 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.

[0058] 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 nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0059] Very High Throughput (VHT) STAs may support 20MHz, 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 noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 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. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0060] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control / Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. 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).

[0061] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11ac, 802.11af, and 802.11ah, 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. In the example of 802.11ah, 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, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0062] In the United States, the available frequency bands, which may be used by 802.11 ah, 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.11 ah is 6 MHz to 26 MHz depending on the country code.

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

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

[0065] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the 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., containing a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the 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). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration 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. For example, 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. In the non- standalone configuration, 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.

[0067] 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, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0068] The CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, 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 non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0070] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 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 DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

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

[0072] The CN 106 may facilitate communications with other networks. For example, 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. In addition, 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. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local 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.

[0073] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation 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.

[0074] 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. For example, 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 performing testing using over-the-air wireless communications.

[0075] 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. For example, 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.

[0076] New Radio (NR) duplex operation is described herein. This technology may improve conventional TDD operation by enhancing UL coverage, improving capacity, reducing latency, and so forth. Conventional TDD is based on splitting the time domain between the uplink and downlink. Sub-band non-overlapping full duplex (SBFD) at the gNB within a conventional TDD band is shown in FIG. 2, which shows dedicated DL slot 210, dedicated UL slot 216, a flexible slot 214 and SBFD slots 212.

[0077] An UL sub-band may be configured in an SSB symbol. In scenarios, shown, for example in FIG. 3, an SBFD-aware WTRU may transmit in an UL sub-band 324, 334 that overlaps with an SSB symbol 322, 332.

[0078] The problem with a WTRU transmitting UL in a time instance that overlaps with a symbol including a reference signal (RS) (e.g., SSB and / or CSI-RS symbol) is that the UL transmission may cause degradation on the SSB measurement for the WTRU itself. The UL transmission in a symbol that includes a DL RS may also result in inter-WTRU CLI for the close by WTRUs that need to measure as RS (SSB or CSI-RS). Moreover, receiving UL in the same symbol as a DL RS may cause self-interference at a gNB, for example, due to the different power control settings for SSB transmission. There is therefore a need for enabling a WTRU to transmit UL efficiently in symbols overlapping with one or more DL RSs.

[0079] 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 herein to refer to a spatial domain filter. A 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 CSI-RS) or a SS block. The WTRU transmission may be referred to herein as a “target”, and the received RS or SS block may be referred to as “a reference” or a “source”. In this case, 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.

[0080] A 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. In this case, 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.

[0081] A spatial relation may be implicit, configured by RRC or signaled by MAC CE or DCI. For example, a WTRU may implicitly transmit PUSCH and DM-RS of PUSCH according to the same spatial domain filter as an SRS indicated by an SRI indicated in DCI or configured by RRC. In another example, a spatial relation may be configured by RRC for an SRS resource indicator (SRI) or signaled by MAC CE for a PUCCH. Such spatial relation may also be referred to as a “beam indication”.

[0082] 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. For example, such association may exist between a physical channel such as PDCCH or PDSCH and its respective DM-RS. At least when the first and second signals are reference signals, such association may exist when the WTRU is configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports. Such association may be configured as a TCI (transmission configuration indicator) state. A WTRU may indicate an association between a CSI-RS or SS block and a DM-RS by an index to a set of TCI states configured by RRC and / or signaled by MAC CE. Such an indication may also be referred to as a “beam indication”.

[0083] Hereinafter, the term “TRP” (e.g., transmission and reception point) may be interchangeably used with one or more of TP (transmission point), RP (reception point), RRH (radio remote head), DA (distributed antenna), BS (base station), a sector (of a BS), and a cell (e.g., a geographical cell area served by a BS). Hereinafter, Multi-TRP may be interchangeably used with one or more of MTRP, M-TRP, and multiple TRPs.

[0084] Hereinafter, the term “sub-band” and / or “sub-band” is used to refer to a frequency-domain resource and may be characterized by at least one of the following: a set of resource blocks (RBs); a set of resource block sets (RB sets), e.g. when a carrier has intra-cell guard bands; a set of interlaced resource blocks; a bandwidth part, or portion thereof; or a carrier, or portion thereof. For example, a sub-band may be characterized by a starting RB and number of RBs for a set of contiguous RBs within a bandwidth part. A subband may also be defined by the value of a frequency-domain resource allocation field and bandwidth part index.

[0085] Hereinafter, the term “XDD” is 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 at least one of the following: Cross Division Duplex (e.g., sub-band-wise FDD within a TDD band); sub-band non-overlapping full duplex (SBFD); sub-band-based full duplex (e.g., full duplex as both UL and DL are used / mixed on a symbol / slot, but either UL or DL being used per sub-band on the symbol / slot); frequency-domain multiplexing (FDM) of DL / UL transmissions within a TDD spectrum; a sub-band non-overlapping full duplex (e.g., non-overlapped sub-band full-duplex); a full duplex other than a same-frequency (e.g., spectrum sharing, sub-band-wise-overlapped) full duplex; or an advanced duplex method, e.g., other than (pure) TDD or FDD.

[0086] Hereinafter, the term “dynamic( / flexible) TDD” is used to refer to a TDD system / cell which may dynamically (and / or flexibly) change / adjust / switch a communication direction (e.g., a downlink, an uplink, or a sidelink, etc.) on a time instance (e.g., slot, symbol, subframe, and / or the like). In an example, in a system employing dynamic / flexible TDD, a component carrier(CC) or a bandwidth part (BWP) may have one single type among types “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. On a given time instance / slot / symbol, 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, and 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. In an example, the first WTRU may determine that the reception of the downlink signal is 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).

[0087] A WTRU may report a subset of channel state information (CSI) components, where CSI components may correspond to at least a CSI-RS resource indicator (CRI), a SSB resource indicator (SSBRI),an indication of a panel used for reception at the WTRU (such as a panel identity or group identity), measurements such as L1-RSRP, L1-SINR taken from SSB or CSI-RS (e.g. cri-RSRP, cri-SINR, ssb-lndex- RSRP, ssb-lndex-SINR), and other channel state information such as at least rank indicator (Rl), channel quality indicator (CQI), precoding matrix indicator (PMI), Layer Index (LI), and / or the like.

[0088] Channel and / or Interference Measurements are described herein. A WTRU may receive a synchronization signal / physical broadcast channel (SS / PBCH) block. The SS / PBCH block (SSB) may include a primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The WTRU may monitor, receive, or attempt to decode an SSB during initial access, initial synchronization, radio link monitoring (RLM), cell search, cell switching, and so forth. A WTRU may measure and report the channel state information (CSI), wherein the CSI for each connection mode may include or be configured with one or more of: a CSI Report Configuration; CSI-RS Resource Set; and / or NZP CSI-RS Resources. These configurations are described more fully below.

[0089] A CSI Report Configuration may include one or more of the following: CSI report quantity, e.g., Channel Quality Indicator (CQI), Rank Indicator (Rl), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), etc.; CSI report type, e.g., aperiodic, semi persistent, periodic; CSI report codebook configuration, e.g., Type I, Type II, Type II port selection, etc.; and CSI report frequency.

[0090] A CSI-RS Resource Set may include one or more of the following CSI Resource settings: NZP-CSI- RS Resource for channel measurement; NZP-CSI-RS Resource for interference measurement; and CSI-IM Resource for interference measurement.

[0091] NZP CSI-RS Resources may include one or more of the following: NZP CSI-RS Resource ID; Periodicity and offset; QCL Info and TCI-state; and Resource mapping, e.g., number of ports, density, CDM type, etc.

[0092] A WTRU may indicate, determine, or be configured with one or more reference signals. The WTRU may monitor, receive, and measure one or more parameters based on the respective reference signals. The following parameters are non-limiting examples of the parameters that may be included in reference signal(s) measurements: SS reference signal received power (SS-RSRP); CSI-RSRP; SS signal-to-noise and interference ration (SS-SINR); CSI-SINR; Received signal strength indicator (RSSI); Cross-Layer interference received signal strength indicator (CLI-RSSI); Sounding reference signals RSRP (SRS-RSRP); Secondary synchronization signal reference signal received quality (SS-RSRQ); and / or CSI reference signal received quality (CSI-RSRQ).These measurements are described more fully below.

[0093] SS-RSRP may be measured based on the synchronization signals (e.g., demodulation reference signal (DMRS) in PBCH or SSS). It may be defined as the linear average over the power contribution of the resource elements (RE) that carry the respective synchronization signal. In measuring the RSRP, power scaling for the reference signals may be required. In case SS-RSRP is used for L1-RSRP, the measurement may be accomplished based on CSI reference signals in addition to the synchronization signals.

[0094] CSI-RSRP may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective CSI-RS. The CSI-RSRP measurement may be configured within measurement resources for the configured CSI-RS occasions.

[0095] SS-SINR may be measured based on the synchronization signals (e.g., DMRS in PBCH or SSS). It may be defined as the linear average over the power contribution of the resource elements (RE) that carry the respective synchronization signal divided by the linear average of the noise and interference power contribution. In case SS-SINR is used for L1-SINR, the noise and interference power measurement may be accomplished based on resources configured by higher layers.

[0096] CSI-SINR may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective CSI-RS divided by the linear average of the noise and interference power contribution. In case CSI-SINR is used for L1-SINR, 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 carry the respective CSI-RS.

[0097] RSSI may be measured based on the average of the 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)

[0098] CLI-RSSI may be measured based on the average of the 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., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, and so forth)

[0099] SRS-RSRP may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective SRS.

[0100] SS-RSRQ may be measured based on measurements on the reference signal received power (SS- RSRP) and received signal strength (RSSI). In an example, the SS-RSRQ may be calculated as the ratio of NxSS-RSRP / NR carrier RSSI, where N may be determined based on the number of resource blocks that are 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.

[0101] CSI-RSRQ may be measured based on measurements on the reference signal received power (CSI-RSRP) and received signal strength (RSSI). In an example, the SS-RSRQ may be calculated as the ratio of NxCSI-RSRP / CSIRSSI, where N may be determined based on the number of resource blocks that are in the corresponding CSI-RSSI measurement bandwidth. As such, the measurements to be used in the numerator and denominator may be over the same set of resource blocks.

[0102] A property of a grant or assignment may consist of at least one of the following: a frequency allocation; an aspect of time allocation, such as a duration; a priority; a modulation and coding scheme; a transport block size; a number of spatial layers; a number of transport blocks; a TCI state, CRI or SRI; a numberof repetitions; whether the repetition scheme is Type A or Type B; whether the grant is a configured grant type 1 , type 2 or a dynamic grant; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; a configured grant index or a semi-persistent assignment index; a periodicity of a configured grant or assignment; a channel access priority class (CAPC); and any parameter provided in a DCI, by MAC or by RRC for the scheduling the grant or assignment.

[0103] An indication by DCI may consist of at least one of the following: an explicit indication by a DCI field or by RNTI used to mask or scramble the CRC of the DCI; and an implicit indication by a property such as DCI format, DCI size, Coreset or search space, Aggregation Level, first resource element of the received DCI (e.g., index of first Control Channel Element), where the mapping between the property and the value may be signaled by RRC or MAC. Receiving or monitoring for a DCI with or using an RNTI may mean that the CRC of the DCI is masked or scrambled with the RNTI.

[0104] Herein, a signal may be interchangeably used with one or more of following: a Sounding reference signal (SRS); Channel state information - reference signal (CSI-RS);Demodulation reference signal (DM-RS); a Phase tracking reference signal (PT-RS); and / or a Synchronization signal block (SSB).

[0105] Herein, a channel may be interchangeably used with one or more of following: a physical downlink control channel (PDCCH); a physical downlink shared channel (PDSCH); a physical uplink control channel (PUCCH); a physical uplink shared channel (PUSCH); and / or a physical random access channel (PRACH).

[0106] Herein, the term downlink reception may be used interchangeably with Rx occasion, PDCCH, PDSCH, and SSB reception. Herein, the term uplink transmission may be used interchangeably with Tx occasion, PUCCH, PUSCH, PRACH, SRS transmission. Herein, the term RS may be interchangeably used with one or more of RS resource, RS resource set, RS port and RS port group. Herein, the term RS may also be interchangeably used with one or more of SSB, CSI-RS, SRS, and DM-RS. Herein, the terms: time instance, slot, symbol, and subframe may be used interchangeably. Herein, the terms UL-only and DL-only Tx / Rx occasions may interchangeably be used with legacy TDD UL or legacy TDD DL, respectively, and still consistent with this disclosure. In an example, the legacy TDD UL / DL Tx / Rx occasions are the cases where SBFD is not configured and / or where SBFD is disabled. Herein, 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. Herein, the term CLI may be used interchangeably with interference. Herein, the term non-SBFD may be used interchangeably with operation without SBFD, TDD, legacy TDD. Herein, the terms WTRU is configured, WTRU is indicated, WTRU receives configuration, may imply that the configuration is indicated for example: via RRC, MAC-CE, DCI, MIB, SIB, and so forth, unless indicated otherwise, where, for example, WTRU is configured may imply WTRU is configured via RRC, MAC-CE, MIB, SIB, and so forth.

[0107] Embodiments for sub-band non-overlapping full duplex (SBFD) operation are described herein. In embodiments, a WTRU may be configured with one or more types of slots within a bandwidth, wherein a firsttype 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. Herein, the term bandwidth may be interchangeably used with bandwidth part (BWP), carrier, sub-band, and system bandwidth; 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) may be referred to as uplink slot; the third type of slot may be referred to as Sub-band (non-overlapping) Full Duplex (SBFD) slot; the group of frequency resource for a first direction may be referred to as downlink sub-band, downlink frequency resource, or downlink RBs; the group of frequency resource for a second direction may be referred to as uplink sub-band, uplink frequency resource, or uplink RBs; the group of frequency resource for a flexible direction (e.g., that can be configured for a first direction, second direction, etc.) may be referred to as flexible sub-band, flexible frequency resource, or flexible RBs; the group of frequency resource between a first direction and a second direction may be referred to as guard band, guard frequency resource, or guard RBs.

[0108] In an example, an 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., symbols, slots, frames, and so forth). The WTRU may be configured with one or more resource allocations for SBFD sub-bands. For example, the SBFD configuration may include a flag signal (e.g., enabled / disabled), where for example a first value (e.g., zero (0)) indicates 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) may be indicated via MIB, SIB, semi-statically (e.g., via RRC), dynamic (e.g., via MAC-CE, DCI), and so forth. The WTRU may receive the time resources (e.g., one or more symbols, slots, and so forth), for which the first mode of operation (e.g., SBFD) is defined in for example one or more BWPs, sub-bands, component carriers (CC), cells, and so forth. The WTRU may receive 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) is configured. The time instances (e.g., slots, symbols) may be indicated based on periodic, semi-persistent, or aperiodic configurations. In an example, the time instances may be indicated via a bitmap configuration, where each bit corresponds to a time instance (e.g., slot, symbol, subframe, etc.) and each bit indication indicates whether corresponding time instance can be used for the first or second mode of operation.

[0109] In an example, 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). As such, if the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., sub-bands, PRBs, and / or BWPs) may be configured for the transmission in UL channels and / or Tx occasions.

[0110] In another example, 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 / dedicatedconfigurations, slot format indicator (SFI), and so forth). As such, if the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., sub-bands, PRBs, and / or BWPs) may be configured as the DL channels and / or Rx occasions.

[0111] In another example, the WTRU may be configured with a DL, UL, or 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). As such, if the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., sub-bands, PRBs, and / or BWPs) may be configured for the first mode of operation (e.g., either UL transmission or DL reception based on the configurations).

[0112] In embodiments, a duplexing mode for the first mode of operation (e.g., SBFD configuration (UL / DL)) 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).

[0113] In further embodiments, a duplexing mode configuration and / or flag for the first mode of operation (e.g., SBFD) may be configured as part of modes of operation that can be semi-static (e.g., via RRC) or dynamic (e.g., via DCI, MAC-CE).

[0114] In further embodiments, a duplexing mode configuration and / or flag for the first mode of operation (e.g., SBFD) may be configured as part of resource allocation configuration for a Tx / Rx occasion.

[0115] In embodiments, a WTRU may be configured, determined, or indicated to perform a measurement of cross-link interference (CLI) Received Signal Strength Indicator (RSSI) in a given time period, wherein the given time period may be one or more slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs). The CLI-RSSI , which may be measured in a given time / frequency resource, may be referred to as L1- CLI-RSSI, short-term CLI-RSSI, aperiodic CLI-RSSI, and so forth. Alternatively, 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 given time period, wherein the 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 given time / frequency resource may be referred to as L1 -SRS-RSRP, short-term SRS-RSRP, aperiodic SRS-RSRP, SRS-RSRP-CLI, and so forth. Herein, CLI-RSSI, L1-CLI-RSSI, and RSSI may be interchangeably used. Herein, SRS-RSRP, SRS-RSRP- CLI, L1 -SRS-RSRP, and RSRP may also be interchangeably used.

[0116] In embodiments, one or more RSSI (or RSRP) types may be used and a WTRU may be configured to perform one or more RSSI (or RSRP) types, wherein a first RSSI (or RSRP) type may be based on a measurement over a long time period (e.g., more than one slot) and the measurement is reported via a higher layer signaling (e.g., RRC, MAC) ; and a second RSSI (or RSRP) type may be based on a measurement over a short time period (e.g., one slot, within a slot, one or more OFDM symbols within a slot) and the measurementis reported via a L1 signaling (e.g., PUCCH, PUSCH, RACH, SRS). Herein, RSSI may be interchangeably used with RSRP, RSRQ, and SINR. CLI-RSSI may be interchangeably used with SRS-RSRP and SINR.

[0117] In embodiments, the WTRU may be configured with a set of time / frequency resource to measure L1 -CLI-RSSI, wherein the time / frequency resource for L1 -CLI-RSSI measurement may be referred to as CLI- RSSI Measurement Resource (CRMR). CRMR may be a resource configured, determined, or defined (e.g., via RRC, MAC-CE, DCI) (e.g., via CLI-ResourceConfig, CLI-ResourceConfig-r-16, and so forth) with one or more of following properties: a set of muted REs in downlink resource; a set of REs not scheduled or used for the WTRU measuring CRMR; a set of RE located in an RB; One or more reference signals; and / or a second set of DMRS Res. These properties are described more fully below.

[0118] A set of muted REs in a downlink resource (e.g., PDSCH), includes 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 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 zero-power resources (e.g., CSI-RS and / or ZP-CSI-RS)

[0119] A set of RE located in an RB 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. A WTRU may skip receiving or transmitting a signal in guard band.

[0120] One or more reference signals may include, for example, DMRS, SRS, and sidelink CSI-RS.

[0121] A second set of DMRS REs within a second CDM group (e.g., within a scheduled downlink resource / RBs, e.g., of PDSCH), may be included where a WTRU receives 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. In an example, 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. In response to receiving 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).

[0122] In embodiments, A CRMR may be located within a scheduled resource (e.g., scheduled PDSCH RBs).

[0123] In embodiments, a CRMR may be configured commonly for a set of WTRU (e.g., WTRU in proximity). For example, a gNB may configure a CRMR for a group of WTRUs, wherein the group of WTRUs may share one or more of following: a group-ID to receive a DCI (e.g., a group-RNTI); a zone-ID, wherein the zone-ID may be determined based on a geographical location of the WTRU (e.g., GNSS); and WTRUs paired for sidelink unicast (or groupcast) transmission

[0124] In embodiments, L1-CLI-RSSI measurement (including CRMR resource) may be considered as CSI reporting quantity and configured as a part of CSI reporting setting.

[0125] In embodiments, CRMR may be configured in a first sub-band type (e.g., DL sub-bands) to measure the (effect of) one or more reference signals received in a second sub-band type (e.g., UL sub-bands). As such, the reference signals may be received and measured in resources that can be identified as zero-power or muted resources. The WTRU may be configured, determined, or indicated to measure the effect of reference signals being transmitted in other resources (e.g., second type resources, e.g., UL sub-bands) in these resources (e.g., first type resources, e.g., DL sub-bands). For example, a first WTRU may be configured to measure SRS-RSRP in DL sub-bands on an SBFD configuration, where the SRS is transmitted by a second WTRU in the UL sub-bands. In an example, the first WTRU may measure SRS-RSRP based of the configured SRS signaling in the DL sub-bands. In another example, the WTRU may measure the CLI-RSSI based on the configured SRS signaling in the UL sub-bands.

[0126] In embodiments, a 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. In embodiments, one or more of following may apply: the delta CLI-RSSI (delta-CLI-RSSI) may be a difference between a first CLI-RSSI (e.g., CLI-RSSI1) and a second CLI-RSSI (e.g., CLI-RSSI2), e.g., delta-CLI-RSSI = CLI-RSSI1 - CL-RSSI2 (or delta-CLI-RSSI = CLI- RSSI2 - CL-RSSI1 , etc.); the first CLI-RSSI may be measured from CRMR resources located in the edge of the scheduled RBs while 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; and a WTRU may determine to report CLI measurement related information when a measured delta-CLI-RSSI is larger than a threshold. For example, CLI reporting may be triggered based on delta-CLI-RSSI measurement is larger than a threshold, wherein the threshold may be predetermined or configured.

[0127] In embodiments, a WTRU may be configured or determined to measure CLI-RSSI per sub-band level. For example, a sub-band may be configured, or predetermined and a WTRU may perform CLI-RSSI measurement in each sub-band. One or more of following may apply: 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 all subbands; the WTRU may report a subset of CLI-RSSI, wherein the subset may be determined based on one or more conditions (e.g., CLI-RSSI value above threshold, sub-band location (e.g., edge of scheduled RBs), and / or sub-band index).

[0128] In embodiments, the WTRU may determine a bandwidth of beam measurement / reporting (e.g., wideband or sub-band) based on one or more of following conditions: time unit type (e.g., SBFD or non-SBFD). For example, 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 timeunits; and presence of CLI-RSSI measurement. The bandwidth of beam measurement / reporting is determined based on whether CLI-RSSI is measured in the same slot or not.

[0129] A WTRU may be indicated to perform CLI-RSSI measurement in a specific frequency location within a scheduled RBs (or non-scheduled RBs), wherein the specific frequency location may be one or more of subbands, RBs, and REs. The indication may be in a DCI which may trigger the CLI-RSSI measurement (e.g., aperiodic CLI-RSSI measurement). The specific frequency location may be indicated based on the CRMR resource frequency location. For example, one or more CRMR resources may be configured and each CRMR resource may be located in a specific frequency location based on configuration. The WTRU may be indicated to perform measurement on CRMR resource indicated in a DCI.

[0130] Embodiments for enabli ng / di sabl i ng of UL transmission in SBFD symbols with DL reference signals based on spatial relation are described herein.

[0131] In embodiments, a WTRU is configured with WTRU-specific configurations per DL RS based on whether the DL RS is protected or unprotected. The WTRU may take corresponding actions for UL transmission in a DL RS symbol based on the configurations received forthat DL RS. In embodiments, a WTRU may receive configurations of one or more reference signals (RS) (e.g., SSBs / CSI-RSs) that may overlap with SBFD symbols, during which the WTRU might be able to send UL transmission in the UL sub-band.

[0132] In embodiments, a WTRU may receive WTRU-specific configuration information on association of one or more RS (beam, SSB index, CRI) and the mode of operation for UL transmission in SBFD UL sub-band, see FIG. 4 (e.g., when an RS is present). FIG. 4 shows base station 410 with protected SSBs 413, 414, 415 and unprotected SSBs 411, 412, 416 and 417. For example, the WTRU 420 receives indications per DL RS on whether the symbol corresponding to that RS is protected (413, 414, 415) or unprotected (411 , 412, 416, 417). In a scenario with protected RS: No UL transmission (422) should be made in the DL RS symbol, it is mandatory for the WTRU not to send a configured UL (e.g., via configured grant) and the WTRU may measure the DL RSs.

[0133] In embodiments with a unprotected RS, and a potential UL transmission in the DL RS symbol, one or more of the following options may apply: UL transmission; UL transmission with power-control and / or UL transmission is skipped or dropped. These options are described more fully below.

[0134] UL transmission: If UL is configured (DCI or configured grant and if the UL is in the UL sub-band) in the DL RS symbol: The WTRU may sends configured UL transmission in the DL RS symbols;

[0135] UL transmission with power-control: If UL is configured (in the UL SB) in the DL RS symbol and the WTRU receives a second power control configuration, one of the following options may apply: Option 1: the WTRU may receive indications to use the second power control configuration only for the symbols that overlap with the corresponding DL RS. In this case, the WTRU sends configured UL transmission in the DL RS symbols using the second power control configuration. Option 2: the WTRU may receive indications to use the second power control configuration for all the symbols corresponding to the configured UL transmission (e.g.,scheduled PUSCH). As such, the WTRU sends all symbols corresponding to the configured UL (even the symbols that do not overlap with the corresponding DL RS symbols) using the second power control configs. This may happen when the UL transmission is not causing interference for the WTRU itself but has the potential to cause interference on other WTRUs.

[0136] UL transmission is skipped or dropped: The WTRU may drop a configured UL transmission in an unprotected DL RS symbols due to one of more of the following conditions: Priority conditions: due to high- priority DL RS (e.g., WTRU-specific, aperiodic) (e.g., CSI-RS, TRS, etc.), high priority DL reception (e.g., PDCCH monitoring, DL dynamically scheduled by a DCI), etc. Beam or radio link conditions: due to BFD and the need to measure RS for BFR, out of sync, etc. The WTRU reports / sends feedback to gNB indicating that the UL was skipped / dropped, either implicitly: via sending a corresponding CSI report, or via reporting corresponding SSB-RSRP or explicitly: via sending a flag indication in a corresponding CSI report, or along with reporting corresponding SSB-RSRP.

[0137] In an example embodiment, the WTRU may receive indications per DL RS on whether the symbol corresponding to that RS is protected or unprotected based on one or more of the following: The WTRU may receive the indications via a bitmap indication, where the WTRU receives a bitmap of length N (where N is the total number of RSs), where each bit corresponds to an RS index, indicating whether the RS is protected or unprotected. The WTRU may receive the indications in the form of one or more sets of DL RSs, that is for example a first set (e.g., Set 1 , protected), a second set (e.g., Set 2, unprotected), a first subset (e.g., Set 2-1 , unprotected with UL transmission), a second subset (e.g., Set 2-2, unprotected with UL transmission with a second power control).

[0138] In embodiments, a WTRU may receive configurations of one or more reference signals (RS) (e.g., SSBs / CSI-RSs) that may overlap with SBFD symbols, during which the WTRU might be able to send UL transmission in the UL sub-band.

[0139] In embodiments, a WTRU may receive WTRU -specific configuration information on association of one or more RS (beam, SSB index, CRI) and the mode of operation for UL transmission in SBFD UL sub-band. For example, the WTRU may receive indications per DL RS on whether the symbol corresponding to that RS is protected or unprotected.

[0140] In embodiments, in protected RS scenarios with no UL transmission in the DL RS symbol, it is mandatory for the WTRU to not send a configured UL (e.g., via configured grant) and the WTRU may measure the DL RSs.

[0141] In embodiments, in unprotected RS scenarios with potential UL transmission in the DL RS symbol, (Multi-level RS protections) one or more of the following options may apply: UL transmission: If UL is configured (DCI or configured grant and if the UL is in the UL sub-band) in the DL RS symbol: The WTRU sends configured UL transmission in the DL RS symbols; UL transmission with power-control. If UL is configured (in the UL SB) in the DL RS symbol and the WTRU receives a second power control configuration, one of the following optionsmay apply: Option 1 : The WTRU receives indications to use the second power control configuration only for the symbols that overlap with the corresponding DL RS. As such, the WTRU sends configured UL transmission in the DL RS symbols using the second power control configs. Option 2: The WTRU receives indications to use the second power control configuration for all the symbols corresponding to the configured UL transmission (e.g., scheduled PUSCH). As such, the WTRU sends all symbols corresponding to the configured UL (even the symbols that do not overlap with the corresponding DL RS symbols) using the second power control configs. This may happen when the UL transmission is not causing interference for the WTRU itself but has the potential to cause interference on other WTRUs.

[0142] In embodiments, in unprotected RS scenarios where UL transmission is skipped or dropped: the WTRU may drop a configured UL transmission in an unprotected DL RS symbols due to one of more of the following conditions: priority conditions: due to high-priority DL RS (e.g., WTRU -specific, aperiodic) (e.g., CSI- RS, TRS, etc.), high priority DL reception (e.g., PDCCH monitoring, DL dynamically scheduled by a DCI), etc.; and beam or radio link conditions: due to BFD and the need to measure RS for BFR, out of sync, etc. The WTRU may report / send feedback to the gNB indicating that the UL was skipped / dropped: implicitly: via sending corresponding CSI report, or via reporting corresponding SSB-RSRP; and explicitly: via sending a flag indication in corresponding CSI report, or along with reporting corresponding SSB-RSRP.

[0143] In an example, the WTRU receives the indications per DL RS on whether the symbol corresponding to that RS is protected or unprotected based on one or more of the following: the WTRU may receive the indications via a bitmap indication, where the WTRU receives a bitmap of length N (where N is the total number of RSs), where each bit corresponds to an RS index, indicating whether the RS is protected or unprotected; or the WTRU may receive the indications in the form of one or more sets of DL RSs, that is for example a first set (e.g., Set 1 , protected), a second set (e.g., Set 2, unprotected), a first subset (e.g., Set 2-1 , unprotected with UL transmission), a second subset (e.g., Set 2-2, unprotected with UL transmission with a 2nd power control), and so forth.

[0144] Embodiments wherein UL Transmission Coincides in Time with DL RS symbols are described herein.

[0145] In embodiments, a WTRU may receive configurations of one or more reference signals (RS). In an example, the configured reference signals may be based on DL reference signals. For example, the configured reference signals may be one or more of the SS / PBCH block (SSB), CSI-RS, TRS, PT-RS, and so forth. In an example, the configurations may include at least the reference signals, RS resource indexes (e.g., SSB index, CRI, etc.), time and frequency resources, repetition, periodicity (e.g., periodic, semi-persistent, aperiodic).

[0146] In embodiments, the WTRU may determine that one or more of the configured reference signals and / or corresponding repetition occasions may be configured in one or more SBFD time instances. The SBFD time instances may be one or more of symbols, slots, subframes and so forth. In an example, the WTRU maybe configured to receive the DL RSs in one or more of the DL sub-bands, flexible sub-bands, and / or UL subbands (if allowed) within the configured SBFD time instances.

[0147] In embodiments, the WTRU may determine that the WTRU may be configured with one or more UL transmission in one or more time-instances that may coincide with the same time instances that are configured for one or more DL RS resources. For example, the WTRU may be configured via one or more configured grant to transmit UL in one or more UL sub-bands within the configured time instances (e.g., SBFD time instances). In another example, the WTRU may be configured to transmit UL in one or more flexible and / or DL sub-bands within the SBFD time instances, if allowed by the NW.

[0148] In embodiments, a WTRU may determine or be configured on whether to transmit or drop an UL transmission in one or more configured and / or scheduled time instances that may coincide in time with one or more configured DL reference signals. Embodiments, for enabling or disabling UL transmission in SBFD symbols are described below, where one of more configured UL transmissions coincide in time with one or more DL reference signals. Embodiments are based on using Tx parameter(s) that are determined based on DL reference signals, by using spatial relations between the configured UL beam direction and the DL RS beam directions, in addition to the configured priorities for UL transmission and DL reception.

[0149] In embodiments, a WTRU may receive configuration information regarding the association of one or more DL RSs and the modes of operation for one or more UL transmissions in one or more UL beam directions that are configured in the same time instances as the DL RSs. For example, the WTRU may be configured with separate and / or different configuration information and modes of operation for each of the configured UL beam directions and per DL RSs.

[0150] In embodiments, the WTRU may be configured with a first mode of operation for a first configured UL beam direction that may coincide in time with a first configured DL RS, where the first mode of operation may be based on disabling UL transmission in the time instance that overlaps with the first DL RS symbol; the WTRU may be configured with a second mode of operation for the first configured UL beam direction that may coincide in time with a second configured DL RS, where the second mode of operation may be based on enabling UL transmission in the time instance that overlaps with the second DL RS symbol, and so forth.

[0151] In embodiments, the UL transmission and DL receptions may be configured in one or more SBFD time instances. In another example, the WTRU may receive the indication on the configured DL RSs based on the corresponding beam indexes, SSB index, CRI, and so forth. In an example, the WTRU may receive the configurations on the modes of operation for each configured UL beam direction and per DL RS based on semistatic and / or dynamic indication, for example from a gNB, for example via RRC, MAC-CE, and / or DCI signaling. The WTRU may receive the configurations via cell-specific, group-specific, and / or WTRU specific signaling.

[0152] Embodiments for protected and unprotected DL RSs are described herein.

[0153] In embodiments, a WTRU may receive configurations and / or indications per DL RS per configured UL beam direction on whether the time instance corresponding to the DL RS is protected or unprotected. Forexample, the WTRU may receive the configurations from a gNB and based on semi-static or dynamic indications via RRC, MAC-CE, and / or DCI. In an example, the WTRU may receive the indication as part of CSI-RS report configurations, where a flag indication may be used to indicate if the time instances corresponding to a CSI-RS are protected or unprotected. For example, the flag indication may be received as part of CSI-RS report configurations per UL beam direction. In another example, the WTRU may receive indications as part of UL grant and / or UL configuration and (specifically) for the configured UL beam direction and per DL RS (e.g., SSB, CSI-RS, etc.). In another example, the WTRU may receive the indications dynamically (e.g., via DCI and / or MAC-CE) indicating and / or updating the mode of operation for an UL beam direction and per DL RSs.

[0154] An example is provided in FIG. 4, where a WTRU 420 is shown with a configured UL beam direction 422 to the gNb 410. The WTRU may receive configurations based on the configured UL beam direction, where the configurations may include the status of protected and unprotected for one or more of the configured DL RSs, for example SSBs. In FIG. 4, the green beam may indicate the configured UL beam direction. Beams 413, 414, 415 indicate the protected SSBs, and beams 411 , 412, 416 and 417 indicate the unprotected SSBs.

[0155] In embodiments where there is a protected RS, the WTRU may receive indications that a first DL RS is configured to be protected based on a first beam direction for UL transmission. As such, the WTRU may determine that the WTRU may not transmit UL transmissions in the direction of the first beam direction in the time instances that coincide with the first DL RS symbols. In an example, the UL transmissions may be configured via a configured grant.

[0156] In embodiments where there is an unprotected RS, the WTRU may receive indications that a second DL RS is configured to be unprotected based on a first beam direction for UL transmission. As such, the WTRU may determine that the WTRU may (potentially) transmit an UL transmission based on the first beam direction, that is for example configured via a configured grant, in the time instances that may coincide with the second DL RS symbols.

[0157] In embodiments, a WTRU may determine to transmit the configured UL transmission in frequency resources, RBs, and / or sub-bands that are allowed for UL transmission. In an example, the WTRU may transmit the configured UL transmission in UL sub-bands in an SBFD time instance. In another example, the WTRU may transmit the configured UL transmission in DL and / or flexible sub-bands in an SBFD time instance, if permitted by the NW. In an example, the WTRU may consider a multi-level RS protection based on the received configurations, when one or more of the following options and protection levels may apply: UL transmission in unprotected DL RSs; UL transmission in unprotected DL RSs with power-control; and / or UL transmission is skipped or dropped: These options are described more fully below.

[0158] UL transmission in unprotected DL RSs: in embodiments, the WTRU may determine to transmit the configured UL transmission based on the configured UL beam direction in the time instances that may coincide with the second DL RS symbols.

[0159] UL transmission in unprotected DL RSswith power-control: In embodiments, theWTRU may receive indications that a third DL RS is configured to be unprotected based on a first beam direction for UL transmission, whereas the WTRU is configured with a second power control configurations that is associated with the third DL RS. For example, the WTRU may determine to use a second power control configuration for the UL transmissions with a first beam direction that coincide in time with the third DL RS. One of the following options may apply: In an example, the WTRU may receive indications (e.g., from gNB, via RRC, MAC-CE, DCI, e.g., via a flag indication) to use the second power control configurations for UL transmission only in the symbols that coincide with the third DL RS symbols. In this case, a WTRU may transmit the configured UL transmission in the DL RS symbols using the second power control configurations. In another example, the WTRU may receive indications (e.g., from gNB, via RRC, MAC-CE, DCI, e.g., via a flag indication) to use the second power control configuration for all the symbols corresponding to the configured UL transmission (e.g., scheduled PUSCH). The WTRU may transmit all symbols corresponding to the configured UL (even the symbols that may not overlap with the corresponding DL RS symbols) using the second power control configurations. In an example, this example may happen when the UL transmission may not cause interference for the WTRU itself but has the potential to cause interference on other WTRUs.

[0160] UL transmission is skipped or dropped: In embodiments, the WTRU may determine to skip and / or drop the configured UL transmission based on the first UL beam direction in time instances that coincide with an unprotected DL RS. The WTRU may determine to skip and / or drop the configured UL transmission based on one or more of the following conditions: Priority conditions; Beam or radio link conditions; Beam index indication; Bitmap indication; Set indication; Based on the set of beams indicated for beam failure detection (BFD) and beam failure recovery (BFR) candidate beams; Based on QCL-chain: Based on active TCI-state; measurement of an RS; and / or UL transmission overlapping with a DL. These conditions are described more fully below.

[0161] Priority conditions: In embodiments, the WTRU may determine to drop the UL transmission due to being configured or receiving configurations on a scheduled high-priority DL reception. For example, the WTRU may receive the configurations on the corresponding DL reception from a gNB, via DCI, MAC-CE, and / or RRC. In an example, the WTRU may receive a configured and / or dynamic grant to receive a high priority DL RS, including WTRU -specific DL RS, aperiodic DL RS, and so forth, where the DL RS may be a CSI-RS, TRS, and so forth. In another example, the WTRU may receive an indication and / or configuration on a PDCCH monitoring. In another exam pie, the WTRU may receive configurations on receiving a DL signal and / or channel, dynamically scheduled by a DCI, where the scheduled DL has a higher priority than the configured UL.

[0162] Beam or radio link conditions: In embodiments, the WTRU may determine to drop the UL transmission due one or more of the beam and / or radio link failure. For example, the WTRU may determine to measure the DL RS that coincides in time with the configured UL instead of performing the UL transmission. In other words, the WTRU may determine to skip and / or drop the UL transmission, to measure the DL RS that coincides in time with the corresponding UL transmission. In an example, the WTRU may determine skip and / ordrop an UL transmission in case the WTRU detects a BFD event, where the WTRU may determine to measure the DL RSs as part of the BFR procedure. In another example, the WTRU may determine to skip and / or drop an UL transmission in case the WTRU detects an out of sync event, where the WTRU may determine to measure the DL RSs as part of the synchronization procedure.

[0163] In embodiments where the WTRU determines to skip and / or drop the configured UL transmission, the WTRU may determine to send a report to indicate that the UL transmission was dropped intentionally and by WTRU. For example, the WTRU may send the indication to a gNB via UCI and / or MAC-CE, and / or as part of the CSI report via implicit or explicit indications. In an example, the WTRU may be configured to use an explicit indication via sending a flag indication, for example in the corresponding CSI report, to indicate that an UL transmission was dropped. In another example, the WTRU may be configured to implicitly indicate the UL drop by sending the CSI report corresponding to the unprotected DL RS. In other words, the WTRU that is supposed to not measure an unprotected DL RS and transmit UL in the corresponding time instance, may implicitly indicate to gNB that the UL transmission was dropped and instead the DL RS was measured, by sending the CSI report regarding that DL RS.

[0164] In embodiments, a WTRU may receive the indications for a configured UL beam direction per DL RS on whether the time instances corresponding to the DL RSs are protected or unprotected for UL transmission based on the configured UL beam direction (e.g., from a gNB, e.g., via DCI, MAC-CE, RRC). One or more of the following options may apply:

[0165] Beam index indication: In embodiments, WTRU may receive the DL RS beam indexes (e.g., SSB index, CRI, TCI-state, etc.) that are protected and / or unprotected. In an example, the WTRU may receive indications only on the DL RS beam indexes that are protected. In another example, the WTRU may receive indications only on the DL RS beam indexes that are unprotected.

[0166] Bitmap indication: In embodiments, the WTRU may receive the indications on protected and / or unprotected DL RSs based on a bitmap indication. The WTRU may receive a bitmap of length N (where N is the total number of RSs), where each bit corresponds to a DL RS index, indicating whether the RS is protected or unprotected.

[0167] Set indication: For example, the WTRU may receive the indications in the form of one or more sets of DL RSs. In an example, the WTRU may receive a first set of DL RSs (e.g., Set 1), where the DL RSs included in the first set may be protected; the WTRU may receive a second set of DL RSs (e.g., Set 2), where the DL RSs included in the second set may be unprotected; the WTRU may receive a first subset of DL RSs (e.g., Set 2-1), where the DL RSs included in the first subset may be unprotected with a first power control configuration, the WTRU may receive a second subset of DL RSs (e.g., Set 2-2), where the DL RSs included in the second subset may be unprotected with a second power control configuration.

[0168] Embodiments regarding configuration indication of protected or unprotected DL RSs are described herein.

[0169] In embodiments, a WTRU may receive configuration of one or more DL RSs that may overlap with SBFD symbols, where the configuration includes indications on whether the symbol corresponding to each RS is protected or unprotected. For example, the determination may be based on one of the following: Based on the set of beams indicated for beam failure detection (BFD) and beam failure recovery (BFR) candidate beams; Based on QCL-chain; Based on active TCI-state; measurement of an RS;.UL transmission overlapping with a DL. These conditions are described more fully below.

[0170] Based on the set of beams indicated for beam failure detection (BFD) and beam failure recovery (BFR) candidate beams: the WTRU receives one or more sets of RS per BWP for monitoring and detecting the beam failure detection (e.g., set of qO, q0,0, qO, 1 ). The WTRU receives one or more sets of (candidate) RS per BWP for monitoring, measuring, and selecting the resources for the beam failure recovery (e.g., set of q1 , q1 ,0, q1 ,1 ); the WTRU determines that a first RS is protected, if the first RS is configured in the set of reference signals for beam failure detection; the WTRU determines that a second RS is unprotected, if the second RS is configured in the set of reference signals for beam failure recovery candidate beams; or the WTRU determines that a third RS is unprotected, if the third RS is neither configured in the set of reference signals for beam failure detection, nor configured in the set of reference signals for beam failure recovery candidate beams.

[0171] Based on QCL-chain: The WTRU may determine that if a first RS (e.g., SSB) is protected, then any other RS (e.g., CSI-RS) that follows the first RS as QCL source is also protected.

[0172] Based on active TCI-state: The WTRU may determine that the RS associated with the active TCI- state is protected.

[0173] The WTRU may measure an RS: if the RS is protected and may report the measured parameters.

[0174] The WTRU may send UL transmission overlapping with a DL RS in an SBFD symbol, if the RS is unprotected and if the UL transmission is allowed (e.g., within the UL sub-band in SBFD symbol).

[0175] In embodiments, A WTRU may receive configuration of one or more DL RSs (e.g., SSB(s), CSI- RS(s), CSI-RS(s) for tracking (TRS), DMRS(s), CORESET(s), etc.) that may overlap with SBFD symbols, where the configuration may include indications on whether the symbol corresponding to an (e.g., each) RS of the one or more DL RSs is protected or unprotected.

[0176] In embodiments, a WTRU may (e.g., implicitly) determine whether a symbol corresponding to an (e.g., each) RS of the one or more DL RSs is protected or unprotected, based on at least one of the following three example rules.

[0177] Example rule 1: Based on the set of beams indicated for beam failure detection (BFD) and beam failure recovery (BFR) candidate beams: The WTRU may receive one or more sets of RS(s) per BWP (or CC) for monitoring and detecting the beam failure detection (e.g., set of qO, q0,0, qO, 1 ). The WTRU may receive one or more sets of (candidate) RS(s) per BWP (or CC) for monitoring, measuring, and selecting resources for beam failure recovery (BFR) (e.g., set of q1 , q1,0, q1 ,1). The WTRU may determine that a first RS (of the one or more DL RSs) is protected, on condition that the first RS is configured (e.g., being comprised, being included)in a set of the one or more sets for monitoring and detecting the BFD (e.g., set of qO, q0,0, q0,1 ). The WTRU may determine that a second RS is unprotected, on condition that the second RS is configured (e.g., being comprised, being included) in a set of the one or more sets for BFR (e.g., BFR candidate beams) (e.g., set of q1, q1 ,0, q1 ,1). The WTRU may determine that a third RS is unprotected, if the third RS is neither configured in the set of reference signals for BFD, nor configured in the set of reference signals for BFR (e.g., BFR candidate beams). Based on the determination, the WTRU may perform at least one example embodiment based on the protected RS and / or the unprotected RS, described throughout the disclosure.

[0178] Example rule 2: Based on QCL-chain: The WTRU may determine that if a first RS (e.g., SSB) is protected (e.g., the first RS is determined as a protected RS), then any other RS (e.g., CSI-RS) that follows the first RS as QCL source is also protected. In an example, the WTRU may determine a first SSB index is protected (e.g., the first SSB index is a protected RS). The WTRU may determine that at least one parameter (e.g., QCL-info, TCI-state, a spatial relation parameter, etc.) of a first CSI-RS resource indicates a (QCL-source) RS that is quasi co-located with the first CSI-RS resource. The WTRU may determine that the (QCL-source) RS is the first SSB index, or a second RS that has its QCL-source as the first SSB index, or a third RS that has its QCL-source as the second RS. In an example, the second RS may represent a QCL-chain rule, where the second RS is a QCL-source of the first CSI-RS resource and at the same time has its QCL source which is the first SSB index. Based on the QCL-chain rule, the WTRU may determine the second RS is protected, e.g., the second RS is a protected RS because its QCL-source is a protected RS that is the first SSB index. Based on the QCL-chain rule, the WTRU may determine the first CSI-RS resource is (also) protected, e.g., the first CSI- RS resource is a protected RS because its QCL-source is a protected RS that is the second RS. In an example, the third RS may represent a QCL-chain rule, where the third RS is a QCL-source of the first CSI-RS resource and at the same time has its QCL source which is the second RS. Based on the QCL-chain rule, the WTRU may determine the second RS is protected, e.g., the second RS is a protected RS because its QCL-source is a protected RS that is the first SSB index. Based on the QCL-chain rule, the WTRU may determine the third RS is (also) protected, e.g., the third RS is a protected RS because its QCL-source is a protected RS that is the second RS. Based on the QCL-chain rule, the WTRU may determine the first CSI-RS resource is (also) protected, e.g., the first CSI-RS resource is a protected RS because its QCL-source is a protected RS that is the third RS. Based on the determination(s), the WTRU may determine that the first CSI-RS resource is protected, e.g., the first CSI-RS resource is a protected RS, based on that the first CSI-RS resource has (e.g., is associated with) its top-QCL-source of the first SSB index that is protected (or is a protected RS), e.g., based on a QCL-chain rule from a top-QCL-source (e.g., the first SSB index) to one or more target RS(s) (e.g., the first CSI-RS resource, or both the first CSI-RS resource and the second RS, or all the first CSI-RS resource, the second RS, and the third RS based on the QCL-chain rule).

[0179] Example rule 3: Based on active TCI-state: The WTRU may determine that an RS associated with an active TCI-state is protected. In an example, the WTRU may be configured with a plurality of TCI-states (e.g., via RRC signaling). The WTRU may receive a TCI activation command (e.g., via a MAC-CE message)that activates one or more TCI-states of the plurality of TCI-states. The WTRU may determine that the one or more TCI-states are active TCI-states (e.g., and / or mapped to codepoint(s) of a DCI field to be used for dynamic TCI-state selection), based on that the one or more TCI-states has been activated by the TCI activation command. Based on the determining that the one or more TCI-states are active TCI-states, the WTRU may determine that the one or more (active) TCI-states are protected, e.g., the one or more TCI-states are protected RS(s).

[0180] The WTRU may measure (e.g., receive) an RS on a condition that the RS is protected and / or may report the measured parameters determined based on the RS. The WTRU may send UL transmission (e.g., being scheduled or indicated) overlapping with a DL RS in an SBFD symbol, if the (DL) RS is unprotected and / or if the UL transmission is allowed (e.g., within the UL sub-band in SBFD symbol).

[0181] Embodiments for WTRU-oriented dynamic updating of the list of protected / unprotected DL RSs are described herein. In embodiments, a WTRU may perform one or more of the following:

[0182] A WTRU may receive configuration of one or more RSs that may overlap with SBFD symbols and indications per RS on whether the RS is protected or unprotected.

[0183] The WTRU may receive configuration for a scheduled UL transmission (e.g., UL configured grant), scheduled in SBFD symbols that overlaps with one or more DL RS symbols. The configuration (or activation) of the scheduled UL transmission includes the UL beam direction (e.g., TCI-state, QCL-Type) for the UL transmission.

[0184] In embodiments for updating a list of unprotected DL RSs, the WTRU may determine to send an indication to a gNB for updating the protected or unprotected status of one or more unprotected DL RSs based on one or more of the following conditions:

[0185] In embodiments based on RSRP condition, the WTRU may measure the RSRP for an unprotected DL RSs. If the measured RSRP for the unprotected DL RS is higher than a configured threshold, the WTRU sends a report to the gNB including the identification of the corresponding DL RS and the measurement. The beam used for receiving the DL RS and / or RSRP measurement may be based on the configured or indicated Rx beam (e.g., TCI state) for the DL RS. The beam used for receiving the DL RS and / or RSRP measurement may be based on the configured (or activated) UL beam direction.

[0186] In embodiments based on a beam direction condition (e.g., AOA and AOD condition), the WTRU may determine if the measured AOA of an unprotected DL RS is within a range (e.g., a configured range) of the AOD of the configured UL (e.g., based on the configured or activated UL beam direction). The WTRU sends a report indicating the identification of the DL RS, and that for this RS, the measured AOA is within the range of the AOD of this configured UL.

[0187] In embodiments based on CLI conditions, the WTRU may measure directional CLI based on SRS received from one or more other WTRUs, according to DL RS beam direction. If the measured CLI is higher than a threshold, the WTRU reports the CLI and the identification of the corresponding DL RS. The report thatthe WTRU sends may recommend and / or suggest to the gNB to update the unprotected status of the corresponding DL RS to protected.

[0188] In embodiments for updating a list of protected DL RSs: a WTRU may determine to send an indication to a gNB for updating the protected or unprotected status of one or more protected DL RSs based on one or more of the following conditions: RSRP condition; Beam direction conditions (e.g., based on AOA and AOD); and / or CLI conditions. These conditions are described more fully below.

[0189] RSRP condition: the WTRU may measure the RSRP for the protected DL RSs. If the measured RSRP of the protected DL RS is lower than a corresponding threshold, the WTRU reports the identification of the corresponding DL RS and the measurements to gNB. The beam used for receiving the DL RS and / or RSRP measurement may be based on the configured or indicated Rx beam (e.g., TCI state) for the DL RS. The beam used for receiving the DL RS and / or RSRP measurement may be based on the configured or activated UL beam direction.

[0190] Beam direction conditions (e.g., based on AOA and AOD): The WTRU may determines if the measured AOA of a protected DL RS is not within a range of the AOD of the configured UL. The WTRU sends a report indicating that for this RS, the measured AOA is not within the range of the AOD of this configured UL.

[0191] CLI conditions: The WTRU may measure directional CLI based on SRS received from one or more other WTRUs, according to DL RS beam direction. If the measured CLI is lower than a threshold, the WTRU reports the CLI and the identification of the corresponding DL RS. The report that the WTRU sends may recommend and / or suggest to the gNB to update the protected status of the corresponding DL RS to unprotected. The WTRU receives confirmation or indications from the gNB for updating or confirming the indicated protected or unprotected DL RSs.

[0192] Embodiments for triggers to measure the protected or unprotected RSs are described herein. In embodiments, a WTRU may perform measurements to determine any of the abovementioned conditions based on: an explicit indication, wherein the WTRU measures the parameters periodically, based on a configured periodicity (e.g., period is longer than normal) or an implicit indication, which may be event-based, for example in case of beam failure detection: the WTRU performs measurements for a configured time window or until the triggering event has stopped.

[0193] In embodiments, a WTRU may receive configuration information and / or activation configuration for a scheduled UL transmission (e.g., via UL configured grant), scheduled in one or more SBFD time instances that may coincide in time with one or more DL RS symbols. The indication, configuration and / or or activation of the scheduled UL transmission may include UL beam direction (e.g., via TCI-state, QCL-Type) for the UL transmission. The WTRU may receive indication information for each of the configured UL beam directions and per DL RSs on whether the corresponding DL RSs are protected or unprotected.

[0194] In embodiments, a WTRU may determine that the one or more of the configured unprotected DL RSs may need to be updated and changed to protected DL RSs. Alternatively, the WTRU may determine thatthe one or more of the configured protected DL RSs may need to be updated and changed to unprotected DL RSs. In an example, the WTRU may determine the changes and updates for each of the configured UL beam directions and the DL RSs that coincide in time with the corresponding configured UL transmissions.

[0195] Embodiments for updating a list of unprotected DL RSs are described herein.

[0196] In embodiments, a WTRU may determine and / or be configured to send an indication for updating the status of one or more DL RSs that coincide in time with a configured UL transmission from unprotected to protected. In an example, the WTRU may send the indication to a gNB. For example, the WTRU may send the indication via UCI, MAC-CE, and / or RRC signaling. In an example, the WTRU may send the indication as part of CSI reporting scheduled and / or configured for the WTRU.

[0197] In embodiments, a WTRU may determine to send the indication for updating the status of one or more DL RSs based on one or more of the following conditions: Channel Parameters (e.g., RSRP) Condition and / or Beam Direction Condition. These conditions are described more fully below.

[0198] Channel Parameters; For example, the WTRU may measure one or more channel parameters based on one or more unprotected DL RSs, where the WTRU may use one or more (pre)configured thresholds to compare with the measured parameters. In an example, the WTRU may measure RSRP of the DL RSs. In an example, the WTRU may use the Rx beam that the WTRU has determined for receiving the DL RSs for receiving and measuring the channel parameters based on the DL RSs. For example, the WTRU may determine the Rx beam based on the configured TCI-state of the corresponding DL RSs. In another example, the WTRU may use the Tx beam that the WTRU has determined for transmitting the configured and / or activated UL transmission for receiving and measuring the channel parameters based on the DL RSs. For example, the WTRU may determine the Tx beam based on the configured and / or activated UL beam direction and / or UL TCI-state configured and / or determined for the configured UL transmission. The WTRU may compare the measured channel parameters with corresponding (pre) configured thresholds, where the threshold may be configured via RRC, MAC-CE, and or DCI. For example, the WTRU may compare the measured RSRP based on the DL RSs and compare with a (pre)configured RSRP threshold. The WTRU may determine that the measured channel parameter (e.g., RSRP) based on at least one of the DL RSs may be higher than the (pre)configured threshold, where the WTRU may determine to send an indication and / or report, for example, to a gNB. In an example, the report may include the measured channel parameter (e.g., RSRP) and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, and so forth. Moreover, the report may include an indication on whether the channel parameters were measured based on the Rx beams and / or Tx beam directions at the WTRU. In an example, the report may indicate an indication, for example flag indication, that the measured parameters were higher than the corresponding thresholds.

[0199] Beam Direction Condition (e.g., based on boresight angle of UL Tx Beam and DL Rx beam): In embodiments, a WTRU may measure the boresight angle of UL Tx Beam and an unprotected DL RS beam,where the WTRU may determine whether the measured boresight angles are within a (pre)configured threshold. In another example, the WTRU may measure the AOA of an unprotected DL RS and compares it with the AOD of a configured UL beam direction, where the WTRU may determine if the measured AOA is within a (pre)configured range of the measured AOD. The WTRU may receive configurations and / or be (pre)configured with the corresponding threshold and / or range limit, where the threshold may be configured via RRC, MAC-CE, and or DCI, via a gNB.

[0200] In a case where the WTRU determines that the measured boresight angles are within the (pre)configured threshold, and / or the measured AOA is within the (pre)configured range of the measured AOD, the WTRU may determine to send an indication and / or report, for example, to the gNB. In an example, the report may include the measured boresights, AOA, AOD, and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, TCI- state, QCL Type, and so forth. Moreover, the report may include an indication that the measured boresight angles are within the threshold, and / or the measured AOA is within the range of the measured AOD.

[0201] An example embodiment of a beam direction relation between configured UL beam direction and one or more of DL RSs’ DL beam directions is provided in FIG. 5. Beam 522 indicates the UL beam direction, and the DL RS beam directions are indicated via DL beams 511 , 512, 513, 514, 515. In FIG. 5, the UL transmission in configured in the UL sub-band of an SBFD symbol, where one more DL RS transmissions are configured in DL sub-bands in the same symbol.

[0202] In embodiments, as shown in FIG. 5A, the WTRU may determine the AOA of the DL RSs in addition to the boresight of the Rx beams 511 , 512, 513, 514, 515 corresponding to the DL RSs. As shown in FIG 5B, the WTRU may also determine the AOD and the boresight of the Tx beams 522 corresponding to the configured UL beam direction. Based on the determined AOA and boresight of the DL RSs, the WTRU may determine the DL RSs, for which the measured boresight angles are within the range of the measured boresight, and / or the measured AOA is within the range of the measured AOD of the configured UL beam direction. For example, in FIG. 5, DL RSs 514 and 515 satisfy the beam direction conditions based on the configured UL beam direction.

[0203] Embodiments regarding measured CLI Condition are described herein. In embodiments, a WTRU may measure the directional CLI based on one or more received SRS signals from one or more other WTRUs. The WTRU may determine to measure the directional CLI based on the Rx spatial filter used for receiving one or more unprotected DL RSs. For example, the WTRU may receive configuration information to receive and measure the SRS signals, including time and frequency resources and corresponding SRIs. For example, the WTRU may measure SRS-RSRP, or for example CLI-RSSI, based on the received SRS signaling.

[0204] In embodiments, a WTRU may compare the measured directional CLI with a (pre)configured threshold. For example, the WTRU may receive configurations and / or be (pre)configured with the corresponding threshold, where the threshold may be configured via RRC, MAC-CE, and or DCI, e.g., via a gNB.

[0205] In embodiments where the WTRU determines that the measured directional CLI (e.g., SRS-RSRP) is higher than the (pre)configured threshold, the WTRU may determine to send an indication and / or report, for example, to the gNB. In an example, the report may include the measured directional CLI and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, TCI-state, QCL Type, and so forth. Moreover, the report may include an indication that the measured directional CLI is higher than the threshold.

[0206] Embodiments WTRU regarding indication reporting are described herein. In embodiments a WTRU may transmit a report that may include a request, suggestion, and / or recommendation for switching the reported unprotected DL RS to a protected DL RS. In an example, the WTRU may transmit the report as part of a CSI reporting. The WTRU may receive an indication and / or confirmation, for example from the gNB, for updating and / or confirming the indicated protected or unprotected DL RSs.

[0207] Embodiments for updating a list of protected DL RSs are described herein. In embodiments, a WTRU may determine and / or be configured to send an indication for updating the status of one or more DL RSs that coincide in time with a configured UL transmission from protected to unprotected. In an example, the WTRU may send the indication to a gNB. In embodiments, a WTRU may send the indication via UCI, MAC- CE, and / or RRC signaling. In an example, the WTRU may send the indication as part of CSI reporting scheduled and / or configured for the WTRU. In embodiments, a WTRU may determine to send the indication based on one or more ofthe following conditions: Channel Parameters (e.g., RSRP) Condition; Beam Direction Condition; and / or CLI Condition. These conditions are described more fully below.

[0208] Channel Parameters (e.g., RSRP) Condition: In embodiments a WTRU may measure one or more channel parameters based on one or more protected DL RSs, where the WTRU may use one or more (pre)configured thresholds to compare with the measured parameters. In an example, the WTRU may measure RSRP of the DL RSs. In embodiments the WTRU may use the Rx beam that the WTRU has determined for receiving the DL RSs for receiving and measuring the channel parameters based on the DL RSs. For example, the WTRU may determine the Rx beam based on the configured TCI-state of the corresponding DL RSs. In embodiments, the WTRU may use the Tx beam that the WTRU has determined for transmitting the configured and / or activated UL transmission for receiving and measuring the channel parameters based on the DL RSs. For example, the WTRU may determine the Tx beam based on the configured and / or activated UL beam direction and / or UL TCI-state configured and / or determined for the configured UL transmission.

[0209] The WTRU may compare the measured channel parameters with corresponding (pre) configured thresholds, where the threshold may be configured via RRC, MAC-CE, and or DCI. For example, the WTRU may compare the measured RSRP based on the DL RSs and compare with a (pre)configured RSRP threshold. The WTRU may determine that the measured channel parameter (e.g., RSRP) based on at least one of the DL RSs may be lower than the (pre)configured threshold, where the WTRU may determine to send an indication and / or report, for example, to a gNB. In an example, the report may include the measured channel parameter(e.g. , RSRP) and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, and so forth. Moreover, the report may include an indication on whether the channel parameters were measured based on the Rx beams and / or Tx beam directions at the WTRU. In an example, the report may indicate an indication, for example flag indication, that the measured parameters were lower than the corresponding thresholds.

[0210] Beam Direction Condition: (e.g., based on boresight angle of UL Tx Beam and DL Rx beam) In embodiments, a WTRU may measure the boresight angle of UL Tx Beam and a protected DL RS beam, where the WTRU may determine if the measured boresight angles are not within a (pre)configured threshold. In another example, the WTRU may measure the AOA of a protected DL RS and compares it with the AOD of a configured UL beam direction, where the WTRU may determine if the measured AOA is not within a (pre)configured range of the measured AOD. The WTRU may receive configurations and / or be (pre)configured with the corresponding threshold and / or range limit, where the threshold may be received via RRC, MAC-CE, and or DCI, e.g., from a gNB.

[0211] In embodiments where a WTRU determines that the measured boresight angles are not within the (pre)configured threshold, and / or the measured AOA is not within the (pre)configured range of the measured AOD, the WTRU may determine to send an indication and / or report, for example, to the gNB. In an example, the report may include the measured boresights, AOA, AOD, and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, TCI-state, QCL Type, and so forth. Moreover, the report may include an indication that the measured boresight angles are not within the threshold, and / or the measured AOA is not within the range of the measured AOD.

[0212] CLI Condition: In embodiments, a WTRU may measure the directional CLI based on one or more received SRS signals from one or more other WTRU. The WTRU may determine to measure the directional CLI based on the Rx spatial filter used for receiving one or more protected DL RSs. For example, the WTRU may receive configuration information to receive and measure the SRS signals, including time and frequency resources and corresponding SRIs. For example, the WTRU may measure SRS-RSRP, or for example CLI- RSSI, based on the received SRS signaling. The WTRU may compare the measured directional CLI with a (pre)configured threshold. For example, the WTRU may receive configurations and / or be (pre)configured with the corresponding threshold, where the threshold may be configured via RRC, MAC-CE, and or DCI, e.g., via a gNB. In embodiments where the WTRU determines that the measured directional CLI (e.g., SRS-RSRP) is lower than the (pre)configured threshold, the WTRU may determine to send an indication and / or report, for example, to the gNB. In embodiments, the report may include the measured directional CLI and / or corresponding DL RS’s identification and / or index. In an example, the DL Rs’s identification and / or indexes may include SSB index, CRI, beam index, TCI-state, QCL Type, and so forth. Moreover, the report may include an indication that the measured directional CLI is lower than the threshold.

[0213] In embodiments, the report that the WTRU may transmit may include a request, suggestion, and / or recommendation for switching the reported protected DL RS to an unprotected DL RS. In an example, the WTRU may transmit the report as part of a CSI reporting. The WTRU may receive an indication and / or confirmation, for example from the gNB, for updating and / or confirming the indicated protected or unprotected DL RSs.

[0214] Embodiments for triggers to measure the protected or unprotected DL RSs are described herein.

[0215] In embodiments, a WTRU may determine or be configured to perform measurements to determine one or more of the abovementioned conditions based on one or more of the following indications: an explicit indication and / or an implicit indication, which are both described more fully below.

[0216] Explicit indication: in embodiments, the WTRU may determine or be configured to measure one or more parameters periodically. The WTRU may receive the time period to measure the parameters, for example based on configuration information received from a gNB, for example via DCI, MAC-CE, and / or RRC signaling. In an example, the time period may be longer than the configured time for CSI-RS measurements.

[0217] Implicit indication: in embodiments, the WTRU may determine or be configured to perform measurements based on the detection of one or more events. In an example, the WTRU may detect a beam failure event, an out of sync event, and so forth. As such, the WTRU may determine to perform measurements, where the WTRU may perform measurements for a (pre)configured time window, based on a counter, and / or until the triggering event has stopped and it is no more detected. The WTRU may receive the time window, maximum counter limit, and / or other configurations, for example based on configuration information received from the gNB, for example via DCI, MAC-CE, and / or RRC signaling.

[0218] Embodiments for reporting the measured RSRP of DL RSs based on Tx beam direction are described herein

[0219] In embodiments, a WTRU performs one or more of the following:

[0220] A WTRU may receive configurations of one or more RSs that overlap with SBFD symbols.

[0221] The WTRU may receive configuration for a scheduled UL transmission, scheduled in SBFD that overlaps with one or more DL RS symbols. The configuration may include the UL beam direction (e.g., TCI- state, QCL-Type)

[0222] The WTRU may measure RSRP based on one or more DL RS beams based on the Tx beam direction that is used for the configured UL beam direction. The following procedure may be performed: The WTRU determines a Tx spatial filter at the WTRU for a configured UL transmission based on configured UL beam direction, TCI-state, and QCL-type. The WTRU uses the determined Tx spatial filters (coefficients) for receiving DL RSs (e.g., based on beam correspondence or reciprocity). For example, the WTRU may select the Rx spatial filter and / or TCI-states used for receiving the DL RSs so that it matches, maps, corresponds, and / or associates with the determined Tx spatial filter and / or TCI-state that the WTRU uses for transmitting theconfigured UL signal and / or channel. In a further example, the WTRU selects the Rx beam direction used for receiving the DL RSs so that the angle of arrival for selected Rx beam is within a (configured) range of the angle of departure for the configured UL beam direction. The WTRU measures “directional” RSRP from one or more DL RSs using the selected Rx spatial filter and / or beam direction. The WTRU reports the measured RSRP to gNB.

[0223] In embodiments, the WTRU may report a QCL-Type E relation between one or more DL RSs and the configured UL, if the measured “directional” RSRP is higher than a threshold. The WTRU indicates the correlation in terms of the correspondence of the DL RSs with the configured UL beam via QCL Type-E for the DL RSs. QCL-Type E is different from QCL Type D. QCL-Type E is not used for UL transmission. QCL-Type E indicates the DL beam directions that are correlated with an UL beam direction. QCL-Type E indicates the DL beam directions for which the correlation with an UL beam direction is higher than a threshold. E.g., In FIG. 5, the configured UL is QCL-ed Type E with DL RS 4 and DL RS 5. The WTRU reports the list of determined QCL-Type E DL RS resources / pairs with the configured UL (e.g., DL RSs, DL TCI states, pairs of DL and UL TCI states, or pairs of DL RSs and UL SRIs).

[0224] In embodiments a WTRU may receive configuration information and / or activation configuration for a scheduled UL transmission (e.g., via UL configured grant), scheduled in one or more SBFD time instances that may coincide in time with one or more DL RS symbols. The indication, configuration and / or or activation of the scheduled UL transmission may include UL beam direction (e.g., via TCI-state, QCL-Type) for the UL transmission. The WTRU may receive indication information for each of the configured UL beam directions and per DL RSs on whether the corresponding DL RSs are protected or unprotected.

[0225] In embodiments, the WTRU may determine or be configured to measure one or more channel parameters based on one or more DL RSs, according to the Tx beam direction that is used for the UL transmission in the direction of the configured UL beam direction. In an example, the WTRU may receive the configuration information from a gNB, for example via DCI, MAC-CE, and / or RRC signaling. In another example, the WTRU may measure one or more channel parameters that may include RSRP, SINR, RSRQ, and so forth. Herein, the terms RSRP, SINR, RSRQ, and channel parameters may be used interchangeably, but still consistent with this disclosure.

[0226] In embodiments, the WTRU may measure directional RSRP based on one or more DL RS beams based on the Tx beam direction that is used for the configured UL beam direction. The procedure may include one or more of the following steps:

[0227] In embodiments, the WTRU may determine a Tx spatial filter at the WTRU for a configured UL transmission based on configured UL beam direction, TCI-state, and / or QCL-type.

[0228] In embodiments, the WTRU may use the determined Tx spatial filters (coefficients) for receiving DL RSs.

[0229] In embodiments, the WTRU may determine the Rx spatial filter based on beam correspondence and / or reciprocity and according to the determined Tx spatial filter.

[0230] In embodiments, the WTRU may select the Rx spatial filter and / or TCI-states used for receiving the DL RSs so that it may match, map, correspond, and / or associate with the determined Tx spatial filter and / or TCI-state that the WTRU may use for transmitting the configured UL signal and / or channel.

[0231] In embodiments, the WTRU may select the Rx beam direction used for receiving the DL RSs so that the angle of arrival for selected Rx beam is within a (pre)configured range of the angle of departure for the configured UL beam direction.

[0232] In embodiments, the WTRU may report the measured directional RSRP to the gNB, via UCI, MAC- CE, and / or RRC signaling. In further embodiments, the WTRU may report the measured directional RSRP as part of a configured CSI reporting.

[0233] Embodiments regarding the relationship between uplink and downlink beams are described herein. In embodiments, a relationship between uplink beam and one or more downlink beams may be determined, defined, or used, wherein the relationship may be at least one of following: Beam alignment level (e.g., boresight angle of UL Tx Beam and DL Rx beam within a certain threshold); Beam correlation level (e.g., UL Tx beam and DL Rx beam correlation level); CLI beam interference level (e.g., interference from a UL Tx beam to a DL Rx beam); and Tx beam power level toward a specific Rx beam direction.

[0234] The relationship may be referred to as QCL type-E, Tx-Rx beam correspondence level, Tx-Rx beam correlation level, Tx-Rx beam alignment level, Tx beam power level, CLI beam interference level, and Tx-RX beam association level. Hereafter, relationship, Tx-Rx beam relationship, QCL Type-E, Tx-Rx beam correspondence level, Tx-Rx beam correlation level, Tx-RX beam alignment level, CLI beam interference level, and Tx-RX beam association level may be interchangeably used but still consistent with the invention.

[0235] Hereafter, SBFD may be interchangeably used with full duplex symbol in which uplink signal and downlink signal may be overlapped at the same time / frequency resource.

[0236] A WTRU may determine the relationship based on one or more of following: an uplink beam information for an uplink transmission (e.g., SRI, TCI, QCL Type-D); a set of downlink beams configured for measurement (e.g., CSI-RS, SSB, and its associated QCL Type D); one or more thresholds to determine the level of the relationship (e.g., threshold to determine the level of correlation, CLI, power level, angle alignment, etc.).

[0237] A WTRU may determine or be indicated to report one or more QCL Type-E when one or more of following conditions are met: a WTRU may be granted for a UL transmission with a specific UL beam index (e.g., SRI, TCI-state) and at least one of DL beam has the Tx-Rx beam correlation level higher than a threshold; a WTRU may be configured to report a list of DL beams for which Tx-Rx beam correlation level is higher than a threshold; a WTRU may determine to report one or more DL beam index for which the CLI interference level is higher than a threshold when a UL beam is used, wherein the UL beam may be an indicated beam from agNB for UL transmission or a list of candidate UL Tx beams which potentially used for a UL transmission from the WTRU; a WTRU may be configured to transmit a UL signal in a SBFD symbol (or full duplex symbol); and a WTRU may have a capability to perform full duplex operation (e.g., transmit / receive at the same time or at the same time / frequency resource).

[0238] In embodiments, one or more class of QCL types may be used or defined, wherein the first class of QCL types QCL types may be used to determine or indicate channel characteristics (e.g., delay spread, Doppler shift, Doppler spread, average delay, and spatial Rx filter) based on an association with a downlink signal or an uplink signal; and the second class of QCL types may be used to determine or indicate channel characteristics based on an association between one or more downlink signals and one or more uplink signals. A first class of QCL types may indicate an association with a downlink reference signal (e.g., CSI-RS, SSB) or an uplink reference signal (e.g., SRS). A second class of QCL types may indicate an association with both at least one downlink reference signal and at least one uplink reference signal (e.g., {CRI, SRI}) A WTRU may use a first class of QCL types for DL reception or UL transmission in a first type of time resource (e.g., non- SBFD symbol, non-SBFD slot, half-duplex symbol, half-duplex slot); and the WTRU may use a second class of QCL types for DL reception or UL transmission in a second type of time resource (e.g., SBFD symbol, SBFD slot, full-duplex symbol, full-duplex slot).

[0239] Embodiments for Group indication and updating of protected and unprotected DL RSs are described herein. In embodiments, a WTRU may receive configuration information and / or activation configuration for a scheduled UL transmission (e.g., via UL configured grant), scheduled in one or more SBFD time instances that may coincide in time with one or more DL RS symbols. The indication, configuration and / or or activation of the scheduled UL transmission may include UL beam direction (e.g., via TCI-state, QCL-Type) for the UL transmission. The WTRU may receive indication information for each of the configured UL beam directions and per DL RSs on whether the corresponding DL RSs are protected or unprotected.

[0240] In embodiments, a WTRU may receive configurations or be (pre)configured with at least a first group including a first list of protected and unprotected DL RSs with a first group-ID (G-RNTI) and one or more second candidate groups including a second list of protected and unprotected DL RSs with second group-IDs. In embodiments, the WTRU may be configured or receive configurations from a gNB, via DCI, MAC-CE, and / or RRC signaling. In embodiments, the list of the protected and / or unprotected DL RSs may be based on the configured UL beam direction for the WTRU.

[0241] In embodiments, a WTRU may monitor to receive changes and / or updates to the list of protected and / or unprotected RSs for the first configured group. In an example, the WTRU may monitor to receive group commands, for example via group DCI, where the CRC in the DCI is scrambled with, for example first G-RNTI. The WTRU may use the received group commands on the updated configuration on protected and / or unprotected RSs for disabling and / or enabling the configured UL transmission. In an example, FIG. 6 shows a gNb 410 with seven, DL RSs beam directions, 611 , 612, 613, 614, 615, 616, 617. FIG. 6 provides an exampleof a WTRU 420 that may be configured with a first and / or an active group, where one or more the DL RSs are configured as protected DL RSs (e.g., DL RSs 612, 613, and 614) and one or more the DL RSs are configured as unprotected DL RSs (e.g., DL RSs 611 , 615, 616, and 617).

[0242] Embodiments for group switching are described herein. In embodiments, a WTRU may monitor the list of protected and unprotected DL RSs and receive configurations on the updates and / or changes in a second one or more candidate groups. In embodiments, the WTRU may monitor to receive group commands, for example via group DCI, where the CRC in the DCI is scrambled with, for example second G-RNTI.

[0243] In further embodiments, a WTRU may measure one or more channel parameters based on one or more protected and / or unprotected DL RSs in a first and a second group of DL RSs and the WTRU may determine a list of preferred protected and unprotected DL RSs based on the measured parameters and one or more conditions. In embodiments, the WTRU may determine list of preferred protected and unprotected RSs based on measured RSRP, beam direction and CLI and so forth, as described above.

[0244] In further embodiments, based on the determined list of preferred protected and unprotected RSs, the WTRU may determine that the configuration of DL RSs in at least one of the second candidate groups is closer to the WTRU’s determined list of preferred protected and unprotected RSs. In embodiments, the WTRU may determine that a second candidate group includes all protected DL RSs that are preferred by the WTRU, for example based on measured RSRP, beam direction, CLI, and so forth. As such, the WTRU may send a request, suggestion, and / or recommendation to switch to the second group as the active group of the protected and unprotected DL RSs. In embodiments, the WTRU may send the request to the gNB, via UCI, MAC-CE, and / or RRC signaling. In further embodiments, the WTRU may send the request as part of a configured CSI- report and via a flag indication and / or an indication on the second group that the WTRU has determined to switch to. In embodiments, the WTRU may receive confirmation or indications from the gNB for updating or confirming the indicated active and / or first group to which the WTRU may switch.

[0245] FIG. 7 is an example flow chart for a process performed in a WTRU for enabling / disabling of UL transmission in SBFD symbols with DL reference signals based on spatial relation according to embodiments described herein. At 710 the process includes receiving first configuration information for one or more downlink (DL) reference signals (RS). At 712, the process includes receiving second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols, the second configuration information indicates whether to adjust power of an associated UL transmission; At 714, the process includes transmitting an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs.

[0246] FIG. 8 is an example flow chart for a process performed in a WTRU for enabling / disabling upload transmission in SBFD symbols with DL reference symbols based on reference symbol protection status. At810, the process includes receiving a configuration of one or more download reference symbols (DL RSs) that overlap with sub-band full duplex (SBFD) symbols. At 812, the process includes determining that a first DL RS is protected with respect to the SBFD symbols. At 814 the process includes determining that a second DL RS is unprotected with respect to the SBFD symbols. At 816, the process includes transmitting an uplink (UL) transmission in a sub-band of a SBFD symbol that overlaps with an unprotected DL RS.

[0247] FIG. 9 is an example flow chart for a process performed in a WTRU for dynamic updating of protection status of downlink reference symbols. At 910, the process includes receiving first configuration information for one or more download reference symbols (DL RSs) that overlap with one or more sub-band full duplex (SBFD) symbols; At 912, the process includes receiving WTRU-specific information for each DL RS indicating whether a respective RS symbol is protected or unprotected; At 914, the process includes based on a condition that a measured cross link interference (CLI) is higher than a predetermined CLI threshold, transmitting, to a base station, an updated indication of protected or unprotected status of at least one DL RS.

[0248] Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. Although the embodiments described herein may consider specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

Claims

CLAIMSWhat is Claimed:

1. A method implemented in a WTRU, the method comprising: receiving first configuration information for one or more downlink (DL) reference signals (RSs); receiving second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols the second configuration information indicates whether the WTRU shall adjust power of an associated UL transmission; and transmitting an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs.

2. The method of claim 1 , wherein, on a condition that it is determined to transmit an UL transmission without a power adjustment and the first DL RS is unprotected, transmitting the UL transmission based on the first power control information.

3. The method of claim 1 , wherein, on a condition that it is determined to transmit an UL transmission with a power adjustment and the first DL RS is unprotected, transmitting the UL transmission using the resource based on the second power control information.

4. The method of claim 1 , wherein, on a condition that the first DL RS is protected, it is determined that a UL transmission is not performed.

5. The method of any of claims 1 -4, further comprising: receiving one or more indications for beam indexes that are protected or unprotected.

6. The method of any of claims 1-4, wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a bitmap indication.

7. The method of any of claims 1-4, wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a set of protected DL RSs and a set of unprotected DL RSs.

8. The method of claim 4, further comprising: transmitting a report indicating that the UL transmission was not performed.

9. The method of claim 1 , wherein one of the DL RSs is indicated to be protected based on a beam direction for UL transmission.

10. The method of claim 1, wherein one of the DL RSs is indicated to be unprotected based on a beam direction for UL transmission.

11. A WTRU comprising: a processor and a transceiver, wherein the processor is configured to cause the transceiver to: receive first configuration information for one or more downlink (DL) reference signals (RSs); receive second configuration information that indicates first power control information and second power control information, and that indicates for each of the one or more DL RSs whether a respective DL RS is protected or unprotected in sub-band non-overlapping full duplex (SBFD) symbols, and for DL RSs that are unprotected in SBFD symbols the second configuration information indicates whether the WTRU shall adjust power of an associated UL transmission; and transmit an UL transmission in a resource that overlaps an unprotected SBFD symbol that includes a first DL RS of the one or more DL RSs.

12. The WTRU of claim 11, wherein, the processor is further configured to cause the transceiver to transmit the UL transmission based on the first power control information on a condition that no power adjustment is required and the first DL RS is unprotected.

13. The WTRU of claim 12, wherein, the processor is further configured to cause the transceiver to transmit the UL transmission based on the second power control information on a condition that a power adjustment is required and the first DL RS is unprotected.

14. The WTRU of claim 11, wherein, the processor is further configured to cause the transceiver to not transmit a UL transmission on a condition that the first DL RS is protected.

15. The WTRU of any of claims 11-14, wherein processor is further configured to cause the transceiver to receive one or more indications for beam indexes that are protected or unprotected.

16. The WTRU of any of claims 11-14, wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a bitmap indication.

17. The WTRU of any of claims 11-14, wherein the second configuration information that indicates whether a respective DL RS is protected or unprotected is based on a set of protected DL RSs and a set of unprotected DL RSs.

18. The WTRU of claim 14, wherein, the processor is further configured to cause the transceiver to transmit a report indicating that the UL transmission was not performed.

19. The WTRU of claim 11, wherein one of the DL RSs is indicated to be protected based on a beam direction for UL transmission.

20. The WTRU of claim 11, wherein one of the DL RSs is indicated to be unprotected based on a beam direction for UL transmission.