A method for enabling / disabling upload transmission in full-duplex subbands using a spatial relationship-based download reference signal.

Abstract

A method for subband full-duplex communication by a wireless transceiver unit (WTRU) is described. The method includes receiving first configuration information for one or more downlink (DL) reference signals (RS), receiving first power control information and second configuration information indicating second power control information, and for each of the one or more DL RSs, indicating whether the DL RS is protected or not in a subband non-overlapping full-duplex (SBFD) symbol, and for DL ​​RSs not protected in an SBFD symbol, indicating whether the second configuration information adjusts the power of the associated UL transmission, and transmitting an UL transmission in a resource that overlaps with an unprotected SBFD symbol, including the first DL RS of one or more DL RSs.

Description

Technical Field

[0001] The present disclosure relates to a method for enabling / disabling uplink transmission in full duplex of subbands using a download reference signal based on spatial relationships.

Background Art

[0002] This application claims priority to U.S. Provisional Application No. 63 / 531,203, filed on August 7, 2023, the content of which is incorporated herein by reference.

[0003] In advanced wireless network systems, an uplink (UL) subband can be configured within a synchronization symbol block (SSB) symbol. In some scenarios, a wireless transmit and receive unit (WTRU) corresponding to subband full duplex (SBFD) can transmit in a UL subband that overlaps with the SSB symbol.

[0004] When a WTRU transmits UL at a time instance that overlaps with a symbol containing a reference signal (RS) (e.g., SSB and / or channel state information reference symbol (CSI-RS)), that UL transmission can cause a decrease in the SSB measurement accuracy of the WTRU itself. UL transmission within a symbol containing a DL RS can also cause WTRU-to-WTRU cross-link interference (CLI) to neighboring WTRUs that need to perform measurements as the RS (SSB or CSI-RS). Further, receiving UL within the same symbol as the DL RS can cause self-interference in the gNB, for example, due to different power control configurations in SSB transmission.

Brief Description of the Drawings

[0005] A more detailed understanding may be obtained from the following description, which is presented illustratively in conjunction with the accompanying drawings, where the same reference numerals in each drawing indicate the same components.

[0006] [Figure 1A]This is a system diagram showing an exemplary communication system in which one or more of the disclosed embodiments may be implemented. [Figure 1B] This is a system diagram showing an exemplary wireless transceiver unit (WTRU) that may be used in the communication system shown in Figure 1A, according to one embodiment. [Figure 1C] This is a system diagram showing an exemplary radio access network (RAN) and an exemplary core network (CN) that may be used in the communication system shown in Figure 1A according to one embodiment. [Figure 1D] This is a system diagram showing a further exemplary radio access network (RAN) and a further exemplary core network (CN) that may be used within the communication system shown in Figure 1A according to one embodiment. [Figure 2] This figure shows an example of an SBFD configuration in a TDD framework. [Figure 3] This figure shows an example of an SSB symbol overlapping with SBFD. [Figure 4] This is an illustrative diagram of protected and unprotected SSB symbols. [Figure 5] This is an illustrative diagram showing the relationship between the beam direction of the DL reference signal and the UL beam. [Figure 5A] This is an illustrative diagram showing the angles of arrival for multiple signals. [Figure 5B] This is an example diagram of the starting angle for UL transmission. [Figure 6] This figure shows examples of group instructions for protected and unprotected DL RS. [Figure 7] This diagram shows an exemplary process for transmitting UL on the SBFD subband. [Figure 8] This figure shows a further exemplary process for transmitting UL on the SBFD subband. [Figure 9] This figure shows further exemplary processing for dynamically updating the protection status of downlink reference symbols for transmitting ULs on the SBFD subband. [Modes for carrying out the invention]

[0007] The aspects, features, and advantages of the disclosed embodiments may address one or more of the aforementioned needs or requirements through methods and apparatus for generating and transmitting segmented compressed beamforming / channel quality index (CQI) reports, as described later.

[0008] In embodiments, a method implemented by a WTRU includes receiving first configuration information relating to one or more downlink (DL) reference signals (RS), receiving second configuration information indicating first and second power control information, and for each of one or more DL RSs, indicating whether the DL RS is protected or unprotected in a subband unsupervised full-duplex (SBFD) symbol, wherein for DL ​​RSs not protected in an SBFD symbol, the second configuration information indicates whether the WTRU should adjust the power of the associated UL transmission, and transmitting the UL transmission in a resource overlapping with an unprotected SBFD symbol, including the first DL RS among the one or more DL RSs. Additionally / alternatively, the method may include transmitting a UL transmission based on the first power control information, provided that it is decided to transmit the UL transmission without power adjustment and the first DL RS is unprotected. Additionally / alternatively, the method may include transmitting a UL transmit with power adjustment using resources based on second power control information, under the condition that it is decided to transmit a UL transmit and the first DL RS is not protected. Additionally / alternatively, the method may include deciding that no UL transmit is performed under the condition that the first DL RS is protected. Additionally / alternatively, the method may include receiving one or more indications regarding the protected or unprotected beam index. Additionally / alternatively, the method may include second configuration information indicating whether each DL RS is protected or unprotected being based on a bitmap indication. Additionally / alternatively, the method may include second configuration information indicating whether each DL RS is protected or unprotected being based on a set of protected DL RSs and a set of unprotected DL RSs. Additionally / alternatively, the method may include transmitting a report indicating that no UL transmit was performed. Additionally / alternatively, the method may include indicating that any of the DL RSs are protected based on the beam direction for the UL transmit.Additionally / alternatively, the method may include indicating that either DL RS is unprotected based on the beam direction for UL transmission.

[0009] In an embodiment, the WTRU includes a processor and a transceiver, the processor being configured to cause the transceiver to receive first configuration information relating to one or more downlink (DL) reference signals (RS), indicating first power control information and second power control information, and for each of one or more DL RSs, receiving second configuration information indicating whether the DL RS is protected or unprotected in a subband unsupervised full-duplex (SBFD) symbol, and for DL ​​RSs that are not protected in an SBFD symbol, the second configuration information indicating whether the WTRU should adjust the power of the associated UL transmission, and to cause the WTRU to transmit a UL transmission in a resource that overlaps with an unprotected SBFD symbol, including the first DL RS among the one or more DL RSs. Additionally / alternatively, the processor may be configured to cause the transceiver to transmit a UL transmission based on the first power control information under the condition that no power adjustment is required and the first DL RS is unprotected. Additionally / alternatively, the processor may be configured to cause the transceiver to perform a UL transmission based on second power control information, under the condition that power adjustment is required and the first DLRS is unprotected. Additionally / alternatively, the processor may be configured not to cause the transceiver to perform a UL transmission, under the condition that the first DLRS is protected. Additionally / alternatively, the method may include the processor being configured to cause the transceiver to receive one or more indications regarding the protected or unprotected beam index. Additionally / alternatively, the second configuration information indicating whether each DLRS is protected or unprotected may be based on a bitmap display. Additionally / alternatively, the second configuration information indicating whether each DLRS is protected or unprotected may be based on a set of protected DLRS and a set of unprotected DLRS. Additionally / alternatively, the processor may be configured to cause the transceiver to transmit a report indicating that a UL transmission was not performed. Additionally / alternatively, one of the DLRS may be indicated as protected based on the beam direction for UL transmission. Additionally / alternatively, one of the DL RSs may be indicated as unprotected based on beam direction for UL transmission.

[0010] Figure 1A is a system diagram showing a typical communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcast to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), quadrature FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtering OFDM, filter bank multicarrier (FBMC), etc.

[0011] As shown in Figure 1A, the communication system 100 may include radio transceiver units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the internet 110, and another network 112, but it will be understood that the disclosed embodiments assume any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a radio environment. For example, WTRU 102a, 102b, 102c, and 102d (all sometimes referred to as stations or STAs) are configured to transmit and / or receive radio signals and may include user equipment (WTRU), mobile stations, fixed or mobile subscriber equipment, subscriber-based equipment, pagers, mobile phones, PDAs (personal digital assistants), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches and other wearables, HMDs (head-mounted displays), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, and devices operating on commercial and / or industrial wireless networks. Any WTRU 102a, 102b, 102c, or 102d may be referred to interchangeably with WTRU.

[0012] The communication system 100 may include base stations 114a and / or base stations 114b. Each of the base stations 114a and 114b may be a device for facilitating access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112, of any type configured to wirelessly interface with at least one WTRU 102a, 102b, 102c, 102d. As an example, base stations 114a and 114b may be base transceiver stations (BTS), Node B, eNode B (eNB), Home Node B, Home eNode B, Next Generation Node B (gNB), New Radio (NR) Node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are shown as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0013] Base station 114a may be part of a radio access network (RAN) 104 and may include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), and relay nodes. Base stations 114a and / or base stations 114b may be configured to transmit and receive radio signals on one or more carrier frequencies (which may be called cells (not shown)). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of radio services to a particular geographic area that may be relatively fixed or change over time. A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers (i.e., one for each sector of the cell). In one embodiment, base station 114a may employ multi-input multi-output (MIMO) technology and utilize multiple transceivers for each sector of the cell or any sector. For example, beamforming can be used to transmit and receive signals in a desired spatial direction.

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

[0015] More specifically, as described above, the communication system 100 is a multiple access system and may adopt one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a and the WTRUs 102a, 102b, 102c within the RAN 104 may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) that can establish an 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).

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

[0017] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access and may establish an air interface 116 using NR.

[0018] In one embodiment, the base stations 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base stations 114a and the WTRUs 102a, 102b, 102c may implement both LTE radio access and NR radio access using, for example, the Dual Connectivity (DC) principle. Accordingly, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by transmissions that are sent and received between multiple types of radio access technologies and / or multiple types of base stations (e.g., eNB and gNB).

[0019] In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Specification 95 (IS-95), Interim Specification 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0020] The base station 114b shown in FIG. 1A may be, for example, a wireless router, a Home Node-B, a Home eNode-B, or an access point, and may utilize any suitable radio access technology (RAT) to facilitate wireless connectivity in a local area such as an office, a home, a vehicle, a campus, an industrial facility, an airport concourse (e.g., for drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology (e.g., 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 pico cell or a femto cell. 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 need to access the Internet 110 via the CN 106.

[0021] The Radio Access Network (RAN) 104 may communicate with the Core Network (CN) 106 and may be any type of network configured to provide voice, data, applications, and / or voice over the Internet Protocol (VoIP) services to one or more Wireless Terminal Units (WTRUs) 102a, 102b, 102c, and 102d. The data may have various quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106 may provide call control, billing services, mobile location services, prepaid calls, internet connectivity, video streaming, and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it is understood that the RAN 104 and / or the CN 106 may communicate directly or indirectly with another RAN employing the same Radio Access Technology (RAT) as the RAN 104 or a different RAT. For example, in addition to being connected to RAN104 which may be using NR radio technology, CN106 may also communicate with other RANs (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0022] CN106 may also function as a gateway for WTRU102a, 102b, 102c, and 102d to access PSTN108, the Internet 110, and / or another network 112. PSTN108 may include a circuit-switched telephone network providing conventional telephone services (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless networks owned and / or operated by another service provider. For example, network 112 may include another CN connected to one or more RANs, which may employ the same radio access technology (RAT) as RAN104 or a different RAT.

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

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

[0025] The processor 118 could be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors working with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be connected to a transceiver 120 which may be connected to a transceiver element 122. Although the processor 118 and the transceiver 120 are shown as separate components in Figure 1B, it will be understood that the processor 118 and the transceiver 120 may be integrated, for example, within an electronic package or chip.

[0026] The transmitting / receiving element 122 may be configured to transmit signals to a base station (e.g., base station 114a) or to receive signals from a base station via the radio interface 116. For example, in one embodiment, the transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmitting / receiving element 122 may be a light-emitting / photo-receiving element configured to transmit and / or receive, for example, infrared, ultraviolet, or visible light signals. In yet another embodiment, the transmitting / receiving element 122 may be configured to transmit and / or receive both RF signals and optical signals. It will be understood that the transmitting / receiving element 122 may be configured to transmit and / or receive any combination of radio signals.

[0027] In Figure 1B, the transmit / receive element 122 is shown as a single element, but 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 radio signals via the radio interface 116.

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

[0029] The processor 118 of the WTRU102 is connected to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Furthermore, the processor 118 can access information and store data from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a subscriber identification module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In another embodiment, the processor 118 may access information and store data from memory that is not physically located on the WTRU 102 (for example, on a server or home computer (not shown)).

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

[0031] The processor 118 may also be connected to a GPS chipset 136 which can be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or alternative to the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the radio interface 116 and / or determine its position based on the timing of signals received from two or more neighboring base stations. It will be understood that the WTRU 102 may acquire location information by any suitable positioning method while remaining consistent with this embodiment.

[0032] The processor 118 may be connected to other peripherals 138 and may further include one or more software and / or hardware modules that provide additional functions, performance, and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulation (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. Peripherals 138 may include one or more sensors. The sensors may include one or more gyroscopes, accelerometers, Hall effect sensors, magnetometers, compass sensors, proximity sensors, temperature sensors, time sensors, position sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, humidity sensors, and the like.

[0033] WTRU102 may include a full-duplex radio in which some or all of the signals (e.g., signals associated with specific subframes in both UL (e.g., for transmission) and DL (e.g., for reception)) are transmitted and / or received in parallel and / or simultaneously. This full-duplex radio includes an interference management unit that reduces and / or substantially eliminates self-interference through signal processing by hardware (e.g., chokes) or a processor (e.g., a separate processing unit (not shown) or processor 118). In one embodiment, WTRU102 may include a half-duplex radio in which some or all of the signals (e.g., signals associated with specific subframes in either UL (e.g., for transmission) or DL ​​(e.g., for reception)) are transmitted and received.

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

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

[0036] Each eNode-B160a, 160b, and 160c may be associated with a specific cell (not shown) and configured to handle decisions regarding radio resource management, handover decisions, and user scheduling on the uplink (UL) and / or downlink (DL). As shown in Figure 1C, the eNode-B160a, 160b, and 160 can communicate with each other via the X2 interface.

[0037] The CN106 shown in Figure 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. Although the aforementioned elements are shown as part of CN106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0038] The MME162 can be connected to each eNode-B162a, 162b, and 162c within RAN104 via the S1 interface and function as a control node. For example, the MME162 may be responsible for user authentication of WTRU102a, 102b, and 102c, enabling / disabling bearers, and selecting a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may also provide control surface functions for switching between RAN104 and another RAN (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0039] The SGW164 can be connected to each eNode-B160a, 160b, and 160c within RAN104 via the S1 interface. The SGW164 can generally route and forward user data packets to and from WTRU102a, 102b, and 102c. The SGW164 can perform other functions, such as anchoring the user plane during eNode-B handovers, triggering pazing when DL data becomes available for WTRU102a, 102b, and 102c, and managing and saving the context of WTRU102a, 102b, and 102c.

[0040] SGW164 is connected to PGW166, and PGW166 may provide WTRU102a, 102b, and 102c with access to packet-switched networks such as the Internet 110, in order to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0041] CN106 may facilitate communication with other networks. For example, CN106 may provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional fixed communication equipment. For example, CN106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN106 and PSTN108. Furthermore, CN106 may provide WTRU102a, 102b, and 102c with access to another network 112, which may include another wired and / or wireless network owned and / or operated by another service provider.

[0042] Although the WTRU is described as a wireless terminal in Figure 1A-1D, in certain representative embodiments, such a terminal may use a wired communication interface with a communication network (e.g., temporarily or permanently).

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

[0044] A wireless LAN (WLAN) in Infrastructure Basic Service Set (BSS) mode may have access points (APs) for the BSS and one or more stations (STAs) associated with those APs. The APs may have access to or interfaces with a distributed system (DS) or another type of wired / wireless network responsible for sending and receiving traffic to and from the BSS. Traffic sent from outside the BSS to an STA may arrive via the AP and be transmitted to the STA. Traffic sent from an STA to outside the BSS may be transmitted to the AP and then to its respective destination. Inter-STA traffic within the BSS may be transmitted via the AP, for example, with the source STA sending traffic to the AP, and the AP sending traffic to the destination STA. Inter-STA traffic within the BSS may be considered, or referred to as, peer-to-peer traffic, which may be transmitted between the source STA and the destination STA (e.g., directly) using a Direct Link Setup (DLS). In certain representative embodiments, the DLS may be an 802.11e DLS or an 802.11z Tunneled DLS (TDLS). A WLAN using Independent BSS (IBSS) mode may not have access points (APs), and STAs within or utilizing IBSS (e.g., all STAs) communicate directly with each other. In this specification, the IBSS communication mode is sometimes referred to as the "ad-hoc" communication mode.

[0045] When using the 802.11ac infrastructure operating mode or a similar operating mode, an AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be of a fixed width (e.g., a 20 MHz bandwidth) or a dynamically configured width. The primary channel may be the operating channel of the BSS, and an STA may be used to establish a connection with the AP. In a typical embodiment, for example, in an 802.11 system, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented. In CSMA / CA, STAs, including the AP (e.g., all STAs), may sense the primary channel. If a particular STA senses / detects or determines that the primary channel is occupied, that STA may backoff. In a particular BSS, only one STA (e.g., only one station) may transmit at any given time.

[0046] A high-throughput (HT) STA can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0047] Ultra-high-throughput (VHT) STAs may support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. 160 MHz channels can be formed by combining eight consecutive 20 MHz channels, or by combining two discontinuous 80 MHz channels, the latter sometimes referred to as an 80+80 configuration. In an 80+80 configuration, channel-encoded data may pass through a segment parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) and time-domain processing may be performed individually for each stream. The streams may be mapped to two 80 MHz channels, and data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the processing of the 80+80 configuration described above may be performed in reverse order, and the combined data may be sent to Media Access Control (MAC).

[0048] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. 802.11af and 802.11ah reduce the channel operating bandwidth and carrier compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV white space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using the non-TVWS spectrum. According to a typical embodiment, 802.11ah may support metered control / mechanical communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have limited functionality, including support for specific bandwidths and / or limited bandwidths (e.g., only support for those). MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0049] A WLAN system that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) may include a channel that can be designated as the primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be configured and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs in operation within the BSS. In the 802.11ah example, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or their other channel bandwidth operating modes, the primary channel may be 1MHz wide for an STA that supports only 1MHz mode (e.g., an MTC type device). The configuration of carrier sensing and / or network allocation vectors (NAVs) may depend on the state of the primary channel. For example, if the primary channel is occupied because an STA that supports only 1MHz operating mode is transmitting to an AP, the entire available frequency band may be considered occupied, even if a large portion of the available frequency band is available in an idle state.

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

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

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

[0053] WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using transmissions associated with scalable numerical systems. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may vary for different transmissions, different cells, and / or different parts of the radio transmission spectrum. WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using subframes or transmit time intervals (TTI) of varying or scalable lengths (e.g., those containing a variable number of OFDM symbols and / or those continuing absolute time of a variable length).

[0054] gNB180a, 180b, and 180c can be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with NB180a, 180b, and 180c without accessing another radio access network (e.g., eNode-B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c can use one or more gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using signals in an unlicensed bandwidth. In a non-standalone configuration, WTRU102a, 102b, and 102c can communicate with / connect to gNB180a, 180b, and 180c while simultaneously communicating with / connecting to other RANs such as eNode-B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c can implement DC principles and communicate substantially simultaneously with one or more gNB180a, 180b, and 180c and one or more eNode-B160a, 160b, and 160c. In a non-standalone configuration, eNode-B160a, 160b, and 160c function as mobility anchors for WTRU102a, 102b, and 102c, while gNB180a, 180b, and 180c may provide additional coverage and / or throughput in servicing WTRU102a, 102b, and 102c.

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

[0056] The CN106 shown in Figure 1D may include at least one AMF182a, 182b, at least one UPF184a, 184b, at least one Session Management Function (SMF)183a, 183b, and possibly a Data Network (DN)185a, 185b. While the aforementioned elements are shown as part of CN106, it should be noted that any of these elements may be owned and / or operated by entities other than the CN operator.

[0057] AMF182a and 182b may be connected to one or more of gNB180a, 180b, and 180c within RAN104 via the N2 interface and may function as control nodes. For example, AMF182a and 182b may be responsible for user authentication of WTRU102a, 102b, and 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selection of specific SMF183a and 183b, management of registration areas, termination of non-access tier NAS signaling, and mobility management. Network slicing may be used by AMF182a and 182b to customize CN support for WTRU102a, 102b, and 102c based on the types of services used by WTRU102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low-latency communication (URLLC) access, services that rely on enhanced large-scale mobile broadband (eMBB) access, and services for MTC access. The AMF182a and 182b may provide control plane functions for switching between RAN1104 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, and LTE-A Pro, and non-3GPP access technologies such as Wi-Fi.

[0058] SMF183a and 183b may be connected to AMF182a and 182b in CN106 via the N11 interface. SMF183a and 183b may also be connected to UPF184a and 184b in CN106 via the N4 interface. SMF183a and 183b may select and control UPF184a and 184b and configure the routing of traffic passing through UPF184a and 184b. SMF183a and 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, enforcing policies and controlling QoS, and providing DL data notifications. PDU session types may be IP-based, non-IP-based, Ethernet-based, etc.

[0059] UPF184a, 184b may be connected to one or more gNB180a, 180b, 180c in RAN104 via the N3 interface, for example, to provide WTRU102a, 102b, 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, 102c and IP-enabled devices. UPF184a, 184b may perform other functions such as packet routing and forwarding, application of user plane policies, support for multi-homed PDU sessions, processing of user plane QoS, buffering of DL packets, and providing mobility anchors.

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

[0061] Referring to Figures 1A-1D and the corresponding description, for WTRU102a-d, base stations 114a-b, eNode-B160a-c, MME162, SGW164, PGW166, gNB180a-c, AMF182a-b, UPF184a-b, SMF183a-b, DN185a-b, and / or any of its other devices described herein, one or more, or all, of the functions described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate some or all of the functions described herein. For example, an emulation device may be used to test another device and / or to simulate network and / or WTRU functions.

[0062] Emulation devices may be designed to implement one or more tests against another device in an experimental environment and / or a telecommunications carrier network environment. For example, one or more emulation devices may perform one or more functions, or all of them, to test another device in a communication network while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network. One or more emulation devices may perform one or more functions, or all of them, while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Emulation devices may be directly connected to another device for testing purposes, and tests may be performed using wireless airborne communications.

[0063] One or more emulation devices may perform one or more functions (including all of them) in a state where they are not implemented / deployed, for example, as part of a wired and / or wireless communication network. For example, emulation devices may be used to implement testing of one or more components in a test scenario in a test laboratory or in a non-deployed (e.g., for testing) wired and / or wireless communication network. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by emulation devices to transmit and / or receive data.

[0064] This specification describes the bidirectional communication operation of New Radio (NR). This technology can improve upon conventional TDD operation by expanding uplink coverage, increasing capacity, and reducing latency. Conventional TDD is based on dividing the time domain between uplink and downlink. Subband non-superimposed full-duplex (SBFD) in a gNB within the conventional TDD band is shown in Figure 2. Figure 2 shows a dedicated DL slot 210, a dedicated UL slot 216, a flexible slot 214, and an SBFD slot 212.

[0065] The UL subband may consist of SSB symbols. For example, in the scenario shown in Figure 3, an SBFD-enabled WTRU may transmit on UL subbands 324 and 334, which overlap with SSB symbols 322 and 332.

[0066] The problem with a WTRU transmitting a UL in a time instance that overlaps with a symbol containing a reference signal (RS) (e.g., an SSB and / or CSI-RS symbol) is that the UL transmission can degrade the accuracy of the WTRU's own SSB measurement. UL transmission in a symbol containing a DL RS can also cause inter-WTRU CLI to neighboring WTRUs that need to perform measurements as RS (SSB or CSI-RS). Furthermore, receiving a UL within the same symbol as a DL RS can cause self-interference in the gNB, for example, due to different power control configurations in the SSB transmission. Therefore, it is necessary to ensure that WTRUs can efficiently transmit ULs in symbols that overlap with one or more DL RSs.

[0067] A WTRU may transmit or receive a physical channel or reference signal according to at least one spatial domain filter. In this specification, the term “beam” may be used to refer to a spatial domain filter. A WTRU may transmit a physical channel or signal using the same spatial domain filter used for receiving an RS (such as CSI-RS) or SS block. In this specification, a transmission by a WTRU may be referred to as a “target,” and a received RS or SS block may be referred to as a “reference” or “source.” In this case, a WTRU may be said to transmit a target physical channel or signal according to its spatial relationship to the reference for the RS or SS block.

[0068] The WTRU may transmit the first physical channel or signal according to the same spatial domain filter used for transmitting the second physical channel or signal. The first and second transmissions may be called the “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 the spatial relationship with the reference to the second (reference) physical channel or signal.

[0069] Spatial relationships can be implicit, configured by the RRC, or signaled by MAC CE or DCI. For example, a WTRU may implicitly transmit PUSCH and its DM-RS according to the same spatial domain filter as an SRS indicated by an SRI directed to DCI, or configured by the RRC. As another example, a spatial relationship may be configured by the RRC for an SRS resource indicator (SRI) or signaled by MAC CE for a PUCCH. Such spatial relationships may also be called "beam indications."

[0070] The WTRU may receive the first (target) downlink channel or signal according to the same spatial domain filter or spatial receive parameters as the second (reference) downlink channel or signal. For example, such a relationship may exist between a physical channel such as PDCCH or PDSCH and its corresponding DM-RS. Such a relationship may exist when the WTRU is configured in quasi-co-location (QCL) assumption Type D between the corresponding antenna ports, provided that at least the first and second signals are reference signals. Such a relationship may be configured as a TCI (Transmit Configuration Indicator) state. The relationship between the CSI-RS or SS block and the DM-RS may be indicated by an index to a set of TCI states configured by the RRC and / or signaled by the MAC CE. Such indication may also be called a "beam indication".

[0071] In the following, the term "TRP" (e.g., Transmitter / Receiver Point) may be used interchangeably with one or more of the following: TP (Transmitter Point), RP (Receiver Point), RRH (Radio Remote Head), DA (Distributed Antenna), BS (Base Station), Sector (of a BS), and Cell (e.g., a geographical cell area served by a BS). In the following, Multi-TRP may be used interchangeably with MTRP, M-TRP, and one or more of the Multiple TRPs.

[0072] In the following, the term "subband" is used to refer to resources in the frequency domain. A subband can be characterized by a set of resource blocks (RBs), a set of resource block sets (RB sets) (for example, if the carrier has an intra-cell guard band), a set of interlaced resource blocks, a portion or part thereof of a bandwidth, or at least one of the carrier or part thereof. For example, a subband can be characterized by the starting resource block and the number of resource blocks for a contiguous set of resource blocks in a portion of the bandwidth. A subband can also be defined by the value of the frequency domain resource allocation field and the bandwidth portion index.

[0073] In the following, the term "XDD" is used to refer to subband-by-subband duplexing (e.g., using either UL or DL ​​per subband), which may be characterized by cross-division duplexing (e.g., subband-by-subband FDD within the TDD bandwidth), subband-non-supervised full duplexing (SBFD), subband-based full duplexing (e.g., full duplexing where both UL and DL are used / mixed per symbol / slot, but only either UL or DL ​​is used in each subband of that symbol / slot), frequency-domain multiplexing (FDM) of DL / UL transmissions in the TDD spectrum, subband-non-supervised full duplexing (e.g., non-supervised subband full duplexing), full duplexing other than same-frequency (e.g., spectral sharing, overlapping on a subband basis) full duplexing, or advanced duplexing schemes, e.g., at least one other than (pure) TDD or FDD.

[0074] In the following, the term “dynamic / flexible TDD” refers to a TDD system / cell that can dynamically (and / or flexibly) change / adjust / switch the direction of communication (e.g., downlink, uplink, or sidelink) within a time unit (e.g., slot, symbol, subframe, etc.). As an example, in a system employing dynamic / flexible TDD, a component carrier (CC) or bandwidth portion (BWP) may have one of the following types on a symbol / slot: “D”, “U”, or “F”, based on indications by Group Common (GC)-DCI (e.g., Format 2_0), including a slot type indicator (SFI). In a given time instance / slot / symbol, a first gNB (e.g., a cell, TRP) employing dynamic / flexible TDD may transmit a downlink signal to a first WTRU communicating with / associated with the first gNB, based on a tdd-UL-DL-config configured / instructed by the first SFI and / or the first gNB; or a second gNB (e.g., a cell, TRP) employing dynamic / flexible TDD may receive an uplink signal transmitted from a second WTRU communicating with / associated with the second gNB, based on a tdd-UL-DL-config configured / instructed by the second SFI and / or the second gNB. For example, the first WTRU may determine that the reception of the downlink signal is being interfered with by the uplink signal, where the interference caused by the uplink signal may refer to inter-WTRU cross-layer interference (CLI).

[0075] The WTRU may report some of the Channel Status Information (CSI) components, which may include at least the SI-RS Resource Indicator (CRI), SSB Resource Indicator (SSBRI), information about the panel used for reception at the WTRU (such as panel ID and group ID), measurements such as L1-RSRP, L1-SINR obtained from SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and at least the Rank Indicator (RI), Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Layer Index (LI), and / or other similar channel status information.

[0076] This specification describes the measurement of channels and / or interference. A WTRU may receive a synchronization signal / physical broadcast channel (SS / PBCH) block. An SS / PBCH block (SSB) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). A WTRU may monitor, receive, or attempt to decode the SSB during initial access, initial synchronization, radio link monitoring (RLM), cell lookup, cell switching, etc. A WTRU may measure and report channel status information (CSI), and the CSI in each connection mode may include, or consist of, one or more CSI reporting configurations, CSI-RS resource sets, and / or NZP CSI-RS resources. These configurations are described in more detail below.

[0077] The CSI reporting configuration may include, for example, the number of items in the CSI report, such as Channel Quality Indicator (CQI), Rank Indicator (RI), Preprocessing Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), and Layer Indicator (LI); the type of CSI report, such as aperiodic, semi-persistent, or periodic; the CSI report codebook configuration, such as Type I, Type II, or Type II port selection; and one or more of the CSI reporting frequencies.

[0078] A CSI-RS resource set may include one or more CSI resource configurations, such as an NZP-CSI-RS resource for channel measurement, an NZP-CSI-RS resource for interference measurement, and a CSI-IM resource for interference measurement.

[0079] An NZP CSI-RS resource may include an NZP CSI-RS resource ID, periodicity and offset, QCL information and TCI status, and one or more resource mappings such as port count, density and CDM type.

[0080] A WTRU may indicate, determine, or constitute one or more reference signals. Based on each reference signal, a WTRU may monitor, receive, and measure one or more parameters. The parameters of SS reference signal received power (SS-RSRP), CSI-RSRP, SS signal-to-noise and interference ratio (SS-SINR), CSI-SINR, received signal strength indicator (RSSI), cross-layer interference received signal strength index (CLI-RSSI), RSRP of a sounding reference signal (SRS-RSRP), received quality of a secondary synchronization signal reference signal (SS-RSRQ), and / or received quality of a CSI reference signal (CSI-RSRQ) are non-limiting examples of parameters that may be included in the measurement of a reference signal. These measurements are described in more detail below.

[0081] SS-RSRP can be measured based on a synchronization signal (e.g., a demodulated reference signal (DMRS) in a PBCH or SSS). It can be defined as a linear average of the output contributions of the resource elements (REs) transmitting each synchronization signal. Output scaling of the reference signal may be necessary when measuring RSRP. If SS-RSRP can be used for L1-RSRP, the measurement may be based on a CSI reference signal in addition to the synchronization signal.

[0082] CSI-RSRP can be measured based on the linear average of the output contributions of the resource elements (REs) that transmit each CSI-RS. The measurement of CSI-RSRP can be configured within the measurement resources corresponding to the timing of the configured CSI-RS occurrences.

[0083] SS-SINR can be measured based on synchronization signals (e.g., DMRS or SSS in a PBCH). It can be defined as the linear average of the output contributions of the resource elements (REs) transmitting each synchronization signal, divided by the linear average of the output contributions of noise and interference. When SS-SINR is used as L1-SINR, noise and interference output measurements can be performed based on resources configured by higher layers.

[0084] The CSI-SINR can be measured based on the linear average of the output contributions of the resource elements (REs) transmitting each CSI-RS, divided by the linear average of the noise and interference power contributions. When the CSI-SINR is used as an L1-SINR, the noise and interference power can be measured based on the resources configured by the higher layer. Otherwise, the noise and interference power can be measured based on the resources transmitting each CSI-RS.

[0085] RSSI can be measured based on the average value of the total power contributions in the configured OFDM symbol and the bandwidth. Power contributions can be received from various resources (e.g., service-providing and non-service-providing cells in the same channel, adjacent channel interference, thermal noise, etc.).

[0086] CLI-RSSI can be measured based on the average total power contribution to the configured OFDM symbol across the configured time and frequency resources. Power contributions can be received from various resources (e.g., cross-layer interference, service-providing and non-service-providing cells on the same channel, adjacent channel interference, thermal noise, etc.).

[0087] SRS-RSRP can be measured based on the linear average of the output contributions of the resource elements (REs) that transmit each SRS.

[0088] SS-RSRQ can be measured based on measurements of the received power (SS-RSRP) and received signal strength (RSSI) of the reference signal. For example, SS-RSRQ can be calculated as the ratio N × SS-RSRP / NR carrier RSSI, where N can be determined based on the number of resource blocks within the corresponding NR carrier RSSI measurement bandwidth. Therefore, the measurements used in the numerator and denominator may span the same set of resource blocks.

[0089] CSI-RSRQ is measured based on the measurement of the received power (CSI-RSRP) and received signal strength (RSSI) of the reference signal. For example, SS-RSRQ can be calculated as the ratio N × CSI-RSRP / CSIRSSI, where N can be determined based on the number of resource blocks included in the corresponding CSI-RSSI measurement bandwidth. Therefore, the measurements used in the numerator and denominator may span the same set of resource blocks.

[0090] The characteristics of the grant or allocation include frequency allocation, time allocation methods such as period, priority, It may consist of at least one of the following parameters provided by DCI, MAC, or RRC for scheduling grants or assignments: modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks, TCI state, CRI or SRI, number of repetitions, whether the repetition scheme is Type A or Type B, whether the grant is a configured grant Type 1, Type 2, or dynamic grant, whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment, configured grant index or semi-persistent assignment index, periodicity of the configured grant or assignment, channel access priority class (CAPC), and any other parameters provided by DCI, MAC, or RRC for scheduling grants or assignments.

[0091] Instructions by DCI may consist of at least one of explicit instructions by DCI fields or by RNTI used to mask or scramble the CRC of DCI, and implicit instructions by properties such as DCI format, DCI size, core set or search space, aggregation level, and a first resource element of the received DCI (e.g., an index of a first control channel element), where the mapping between properties and values ​​may be communicated by RRC or MAC. Receiving or monitoring DCI with or using RNTI may mean that the CRC of DCI is masked or scrambled by RNTI.

[0092] In this specification, signals may be used interchangeably with one or more of the following: sounding reference signals (SRS), channel status information reference signals (CSI-RS), demodulation reference signals (DM-RS), phase tracking reference signals (PT-RS), and / or synchronization signal blocks (SSB).

[0093] In this specification, a channel may be used interchangeably with one or more of the following: a physical downlink control channel (PDCCH), a physical downlink sharing channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink sharing channel (PUSCH), and / or a physical random access channel (PRACH).

[0094] In this specification, the term “downlink receive” may be used interchangeably with “Rx event,” “PDCCH,” “PDSCH,” and “SSB receive.” In this specification, the term “uplink transmit” may be used interchangeably with “Tx event,” “PUCCH,” “PUSCH,” “PRACH,” and “SRS transmit.” In this specification, the term “RS” may be used interchangeably with one or more of “RS resource,” “RS resource set,” “RS port,” and “RS port group.” In this specification, the term “RS” may also be used interchangeably with one or more of “SSB,” “CSI-RS,” “SRS,” and “DM-RS.” In this specification, the terms “time instance,” “slot,” “symbol,” and “subframe” may be used interchangeably. In this specification, the terms “UL only” and “DL only” transmit / receive opportunities may be used interchangeably with conventional TDD UL or conventional TDD DL, respectively, and will still be consistent with this disclosure. For example, a conventional TDD UL / DL transmit / receive opportunity refers to a case where SBFD is not configured and / or SBFD is disabled. In this specification, 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. In this specification, the term CLI may be used interchangeably with interference. In this specification, the term non-SBFD may be used interchangeably with operation without SBFD, TDD, and conventional TDD. In this specification, the terms “WTRU is configured,” “WTRU is indicated,” and “WTRU receives configuration” may mean that the configuration is indicated through, for example, RRC, MAC-CE, DCI, MIB, SIB, etc., unless otherwise specified. For example, "WTRU is configured" could mean that the WTRU is configured through RRC, MAC-CE, MIB, SIB, etc.

[0095] This specification describes embodiments relating to subband non-superimposed full-duplex (SBFD) operation. In embodiments, the WTRU may be configured to have one or more types of slots within the bandwidth. Hereinafter, a first type of slot may be used or determined for a first direction (e.g., downlink), a second type of slot may be used or determined for a second direction (e.g., uplink), and a third type of slot may have a first group of frequency resources within the bandwidth for the first direction and a second group of frequency resources within the bandwidth for the second direction. In this specification, the term “bandwidth” may be used interchangeably with Bandwidth Part (BWP), Carrier, Subband, and System Bandwidth; a first type of slot (e.g., a slot for a first direction) may be called a downlink slot; a second type of slot (e.g., a slot for a second direction) may be called an uplink slot; a third type of slot may be called a subband (non-superimposed) full-duplex (SBFD) slot; a group of frequency resources for a first direction may be called a downlink subband, downlink frequency resource, or downlink RB; a group of frequency resources for a second direction may be called an uplink subband, uplink frequency resource, or uplink RB; a group of frequency resources for a flexible direction (e.g., configurable for a first direction, a second direction, etc.) may be called a flexible subband, flexible frequency resource, or flexible RB; and a group of frequency resources between a first direction and a second direction may be called a guard band, guard frequency resource, or guard RB.

[0096] For example, an SBFD-enabled WTRU may receive or configure one or more SBFD UL or DL ​​subbands in one or more DL / UL / Flexible TDD time instances (e.g., symbols, slots, frames). The WTRU may be configured with one or more resource allocations for the SBFD subband. For example, an SBFD configuration may include a flag signal (e.g., enabled / disabled), where a first value (e.g., zero (0)) indicates a first operating mode (e.g., SBFD configuration) and a second value (e.g., 1) indicates a second operating mode (e.g., non-SBFD operation). The operating mode (e.g., SBFD and / or non-SBFD) may be indicated through MIB, SIB, semi-static (e.g., via RRC), dynamic (e.g., via MAC-CE, DCI), etc. A WTRU may receive time resources (e.g., one or more symbols, slots, etc.) in which a first operating mode (e.g., SBFD) is defined, for example, in one or more BWPs, subbands, component carriers (CCs), cells, etc. A WTRU may receive frequency resources (e.g., subbands / BWPs including one or more PRBs) in a BWP (active and / or linked) in which the first operating mode (e.g., SBFD) is configured. Time instances (e.g., slots, symbols) may be indicated based on periodic, semi-permanent, or aperiodic configuration. As an example, time instances may be indicated via a bitmap configuration, where each bit corresponds to a time instance (e.g., slot, symbol, subframe, etc.), and the indication of each bit may indicate whether the corresponding time instance is available for the first or second operating mode.

[0097] For example, a WTRU may be configured with a DL TDD configuration for a component carrier (CC), or a BWP for one or more Rx opportunities, for example, through a tdd-UL-DL-config-common / dedicated configuration or a slot format indicator (SFI). Thus, when a first operating mode (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured for transmission on UL channels and / or Tx opportunities.

[0098] As another example, a WTRU may be configured with a UL TDD configuration for component carriers (CCs), or a BWP for one or more Tx opportunities, for example, through a tdd-UL-DL-config-common / dedicated configuration, a slot format indicator (SFI), etc. Thus, when a first operating mode (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured as DL channels and / or Rx opportunities.

[0099] As another example, a WTRU may have DL, UL, or flexible TDD configurations for component carriers (CCs) or BWPs for one or more Rx / Tx opportunities, for example, through a tdd-UL-DL-config-common / dedicated configuration, a slot format indicator (SFI), etc. Thus, if a first operating mode (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and / or BWPs) may be configured for the first operating mode (e.g., either UL transmission or DL ​​reception, depending on the configuration).

[0100] In one embodiment, the duplexing mode of a first operating mode (e.g., SBFD configuration (UL / DL)) may be indicated by a flag indicator, for example, a first value (e.g., zero (0)) may indicate the first mode (e.g., UL duplexing mode), and a second value (e.g., 1) may indicate the second mode (e.g., DL duplexing mode).

[0101] In further embodiments, the duplexing mode configuration and / or flag of the first operating mode (e.g., SBFD) may be configured as part of an operating mode that can be configured semi-statically (e.g., via RRC) or dynamically (e.g., via DCI, MAC-CE).

[0102] In a further embodiment, the duplexing mode configuration and / or flags for the first operating mode (e.g., SBFD) may be configured as part of the resource allocation configuration for Tx / Rx events.

[0103] In embodiments, the WTRU may be configured, determined, or instructed to perform a measurement of the Crosslink Interference (CLI) Received Signal Strength Index (RSSI) over a predetermined time period, where the predetermined time period may be one or more slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs). The CLI-RSSI measured over a predetermined time / frequency resource may be referred to as L1-CLI-RSSI, short-term CLI-RSSI, aperiodic CLI-RSSI, etc. Alternatively, the WTRU may be configured, determined, or instructed to perform a measurement of the Reference Signal Received Power (RSRP) based on one or more reference signals (e.g., SRS-RSRP) in the context of CLI measurements over a predetermined time frame, where the predetermined time frame may be one or more slots, OFDM symbols, resource blocks (RBs), and / or resource elements (REs). SRS-RSRP measured within a given time / frequency resource may be called L1-SRS-RSRP, short-term SRS-RSRP, aperiodic SRS-RSRP, SRS-RSRP-CLI, etc. In this specification, CLI-RSSI, L1-CLI-RSSI, and RSSI may be used interchangeably, and SRS-RSRP, SRS-RSRP-CLI, L1-SRS-RSRP, and RSRP may also be used interchangeably.

[0104] In embodiments, one or more RSSI (or RSRP) types are used, and the WTRU may be configured to perform one or more RSSI (or RSRP) types, where the first RSSI (or RSRP) type is based on measurements over a long period (e.g., one or more slots), and the measurement results are reported via higher-level signaling (e.g., RRC, MAC), and the second RSSI (or RSRP) type is based on measurements over a short period (e.g., one slot, within a slot, one or more OFDM symbols within a slot), and the measurements may be reported via L1 signaling (e.g., PUCCH, PUSCH, RACH, SRS). In this specification, RSSI may be used interchangeably with RSRP, RSRQ, and SINR, and CLI-RSSI may be used interchangeably with SRS-RSRP and SINR.

[0105] In an embodiment, the WTRU may be configured to have a set of time / frequency resources for measuring L1-CLI-RSSI, where the time / frequency resources for L1-CLI-RSSI measurement may be referred to as the CLI-RSSI Measurement Resource (CRMR). The 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, etc.) to have one or more characteristics of a set of REs muted in the downlink resources, a set of REs not scheduled or used for the WTRU measuring the CRMR, a set of REs located in the RB, one or more reference signals, and / or a second set of DMRS resources. These characteristics are described in more detail below.

[0106] A set of muted REs for a downlink resource (e.g., PDSCH) may be rate-matched or punctured for downlink reception and / or uplink transmission. The set of muted REs may have the same pattern (e.g., the same time / frequency position) at each RB. Alternatively, the set of muted REs may have different patterns based on the location of the RB. For example, a first pattern might be used for RBs located at the ends of a scheduled RB, and a second pattern for RBs located in the middle of a scheduled RB. The first and second patterns may differ in the number of muted REs. Muted REs may take the form of zero-power resources (e.g., CSI-RS and / or ZP-CSI-RS).

[0107] A set of REs placed in an RB may be configured or determined as a guard band (or guard RB). The guard band (or guard RB) may be placed between the uplink resource and the downlink resource. The WTRU may skip receiving or transmitting signals within the guard band.

[0108] One or more reference signals may include, for example, DMRS, SRS, and side-link CSI-RS.

[0109] A second DMRS RE set within a second CDM group (e.g., within a scheduled downlink resource / RB of a PDSCH) may be included if the WTRU receives a DCI scheduling a PDSCH that indicates a first DMRS RE set corresponding to a first CDM group used to receive the PDSCH. For example, the WTRU may receive a DCI scheduling a PDSCH that indicates a first DMRS RE set corresponding to a first CDM group (based on the specified "(DMRS) antenna port" field of the DCI). In response to receiving the DCI, the WTRU may determine that a second DMRS RE set within a second CDM group (other than the first CDM group) is available as a CRMR (e.g., within a scheduled PDSCH).

[0110] In an embodiment, the CRM may be located within a scheduled resource (e.g., a scheduled PDSCH RB).

[0111] In an embodiment, CRMR may be configured in common for a set of WTRUs (e.g., adjacent WTRUs). For example, a gNB may configure CRMR for a group of WTRUs, the group of WTRUs may share a group ID for receiving DCI (e.g., group RNTI), a zone ID which may be determined based on the geographic location of the WTRUs (e.g., GNSS), and one or more WTRUs paired for sidelink unicast (or groupcast) transmission.

[0112] In embodiments, L1-CLI-RSSI measurements (including CRMR resources) may be considered CSI reporting quantities and may be configured as part of the CSI reporting configuration.

[0113] In embodiments, CRMR may be configured in a first subband type (e.g., DL subband) and measure one or more reference signals (and their influence) received in a second subband type (e.g., UL subband). Thus, the reference signals may be received and measured in resources identifiable as zero-power or muted resources. WTRUs may be configured, determined, or indicated to measure the influence of reference signals transmitted on other resources (e.g., second type resources, e.g., UL subband) on these resources (e.g., first type resources, e.g., DL subband). For example, the first WTRU may be configured to measure SRS-RSRP in the DL subband in an SBFD configuration, and the SRS may be transmitted in the UL subband by the second WTRU. As an example, the first WTRU may measure SRS-RSRP based on SRS signaling configured in the DL subband. As another example, the WTRU may measure CLI-RSSI based on SRS signaling configured in the UL subband.

[0114] In embodiments, the WTRU may be configured, determined, or instructed to perform a delta-CLI-RSSI based on a first CLI-RSSI measurement at a first time / frequency position and a second CLI-RSSI measurement at a second time / frequency position. In embodiments, the delta-CLI-RSSI may be the difference between a first CLI-RSSI (e.g., CLI-RSSI1) and a second CLI-RSSI (e.g., CLI-RSSI2), for example, delta-CLI-RSSI = CLI-RSSI1 - CLI-RSSI2 (or delta-CLI-RSSI = CLI-RSSI2 - One or more of the following may apply: the first CLI-RSSI (e.g., CL-RSSI1) may be measured from a CRMR resource located at the edge of the scheduled RB, the second CLI-RSSI may be measured from a CRMR resource located in the middle of the scheduled RB, the WTRU may be configured to allocate the first CRMR resource for the first CLI-RSSI measurement and the second CRMR resource for the second CLI-RSSI measurement, and the WTRU may decide to report CLI measurement-related information if the measured delta-CLI-RSSI is greater than a threshold. For example, CLI reporting may be triggered based on the measurement of delta-CLI-RSSI being greater than a threshold, where the threshold may be predetermined or configured.

[0115] In embodiments, the WTRU may be configured or determined to measure CLI-RSSI for each subband level. For example, subbands may be configured or predetermined, and the WTRU may perform CLI-RSSI measurements in each subband. It may be applied that the subband size may be determined based on the number of scheduled RBs (e.g., for PDSCH), the WTRU may report CLI-RSSI measurements for all subbands, and the WTRU may report a portion of the CLI-RSSI, where the portion may be determined based on one or more conditions (e.g., CLI-RSSI values ​​exceeding a threshold, subband location (e.g., the edge of a scheduled RB), and / or subband index).

[0116] In embodiments, the WTRU may determine the bandwidth of the beam measurement / report (e.g., broadband or subband) based on one or more of the following conditions (e.g., type of time unit (SBFD or non-SBFD)). For example, the WTRU may report broadband CRI (e.g., broadband beam index) in non-SBFD time units (symbol, slot, etc.) and report whether or not subband CRI (e.g., subband beam index) and CLI-RSSI measurements are performed in SBFD time units. The bandwidth of the beam measurement / report is determined based on whether the CLI-RSSI is measured in the same slot.

[0117] A WTRU may be instructed to perform a CLI-RSSI measurement at a specific frequency location of a scheduled RB (or an unscheduled RB), where the specific frequency location may be one or more of a subband, RB, and RE. The instruction may be in the DCI that triggers the CLI-RSSI measurement (e.g., aperiodic CLI-RSSI measurement). The specific frequency location may be instructed based on the frequency location of a CRMR resource. For example, one or more CRMR resources may be configured, and each CRMR resource may be located at a specific frequency location based on its configuration. A WTRU may be instructed to perform a measurement on the CRMR resource indicated in the DCI.

[0118] This specification describes embodiments for enabling / disabling UL transmission in SBFD symbols having a DL reference signal based on spatial relationships.

[0119] In one embodiment, the WTRU may be configured with a WTRU-specific configuration for each DL RS, based on whether the DL RS is protected or not. Based on the configuration received for the DL RS, the WTRU may take corresponding actions for UL transmissions in the DL RS symbol. In one embodiment, the WTRU may receive a configuration of one or more reference signal (RS) (e.g., SSB / CSI-RS) that may overlap with the SBFD symbol, while the WTRU can transmit UL transmissions in the UL subband.

[0120] In embodiments, the WTRU may receive WTRU-specific configuration information relating to the association of one or more RSs (beam, SSB index, CRI) and the operating mode of UL transmission in the SBFD UL subband (see Figure 4 (e.g., if RSs exist)). Figure 4 shows a base station 410 having protected SSBs 413, 414, 415 and unprotected SSBs 411, 412, 416, 417. For example, WTRU 420 receives instructions for each DL RS regarding whether the symbol corresponding to the RS is protected (413, 414, 415) or unprotected (411, 412, 416, 417). In scenarios with protected RSs, UL transmission (422) must not be performed on the DL RS symbol, the WTRU is obligated not to transmit configured ULs (e.g., via configured grants), and the WTRU may measure the DL RS.

[0121] In embodiments having an unprotected RS and where UL transmission may be performed with DL RS symbols, one or more of the following options may apply: UL transmission, UL transmission with power control, and / or UL transmission being skipped or discarded. These options are described in more detail below.

[0122] UL Transmission: If UL is configured in the DL RS symbol (DCI or configured grant and UL is in the UL subband), the WTRU may send UL transmissions configured in the DL RS symbol.

[0123] Power-controlled UL transmissions: When a UL is configured (within a UL SB) in a DL RS symbol and the WTRU receives a second power-controlled configuration, one of the following options may apply: Option 1: The WTRU may be instructed to use the second power-controlled configuration only for symbols that overlap with the corresponding DL RS. In this case, the WTRU transmits the configured UL transmission within the DL RS symbol using the second power-controlled configuration. Option 2: The WTRU may be instructed to use the second power-controlled configuration for all symbols corresponding to a configured UL transmission (e.g., a scheduled PUSCH). Therefore, the WTRU transmits all symbols corresponding to the configured UL (even symbols that do not overlap with the corresponding DL RS symbol) using the second power-controlled configuration. This may occur when a UL transmission does not cause interference to the WTRU itself but may cause interference to other WTRUs.

[0124] UL transmissions are skipped or discarded: The WTRU may discard a configured UL transmission in an unprotected DL RS symbol due to one or more of the following conditions: Priority conditions: due to high-priority DL RS (e.g., WTRU-specific, aperiodic) or high-priority DL reception (e.g., PDCCH monitoring, dynamic DL scheduling by DCI, etc.). Beam or radio link status: due to the need for RS measurements for BFD and BFR, synchronization errors, etc. The WTRU reports / feeds back to the gNB that a UL has been skipped or discarded. This can be done implicitly by sending a corresponding CSI report or reporting a corresponding SSB-RSRP, or explicitly by sending a flag indication within the corresponding CSI report or in conjunction with the reporting of the corresponding SSB-RSRP.

[0125] In one embodiment, the WTRU may receive information about whether the symbol corresponding to each DL RS is protected or not, based on one or more of the following: The WTRU may receive an instruction in bitmap format, in which case the WTRU receives a bitmap of length N (where N is the total number of RSs), where each bit corresponds to an RS index and indicates whether the RS is protected or not. The WTRU may receive an instruction in the form of one or more sets of DL RSs, for example, in the form of a first set (e.g., set 1, protected), a second set (e.g., set 2, not protected), a first subset (e.g., set 2-1, not protected with UL transmission), and a second subset (e.g., set 2-2, not protected with UL transmission with second power control)).

[0126] In one embodiment, the WTRU may receive a configuration of one or more reference signals (RS) (e.g., SSB / CSI-RS) that may overlap with the SBFD symbol, while the WTRU can perform UL transmission in the UL subband.

[0127] In embodiments, the WTRU may receive WTRU-specific configuration information relating to the relationships between one or more RSs (beam, SSB index, CRI) and the operating mode of UL transmission in the SBFD UL subband. For example, the WTRU may receive an indication for each DL RS whether the symbol corresponding to that RS is protected or not.

[0128] In an embodiment, in a protected RS scenario where no UL transmission occurs during DL RS symbol, the WTRU must not transmit a configured UL (e.g., via a configured grant), and the WTRU may measure DL RS.

[0129] In embodiments, in unprotected RS scenarios where UL converging may occur within a DL RS symbol (multilevel RS protection), one or more of the following options may apply: UL transmission: If a UL is configured within a DL RS symbol (it is a DCI or a configured grant and the UL is in the UL subband), the WTRU transmits a configured UL transmission, a UL transmission with power control, within the DL RS symbol. If a UL is configured within a DL RS symbol (in the UL subband) and the WTRU receives a second power control configuration, one of the following options may apply: Option 1: The WTRU is instructed to use the second power control configuration only for symbols that overlap with the corresponding DL RS. Thus, the WTRU uses the second power control configuration to perform the configured UL transmission within the DL RS symbol. Option 2: The WTRU is instructed to use the second power control configuration for all symbols corresponding to a configured UL transmission (e.g., a scheduled PUSCH). Thus, the WTRU transmits all symbols corresponding to a configured UL (even symbols that do not overlap with the corresponding DL RS symbol) using the second power control configuration. This can occur when a UL transmission does not cause interference to the WTRU itself, but may cause interference to other WTRUs.

[0130] In embodiments, in unprotected RS scenarios where a UL transmission is skipped or discarded, the WTRU may discard a UL transmission configured in an unprotected DL RS symbol due to one or 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 DCI, etc.), and beam or radio link conditions: due to the need for RS measurements for BFD and BFR, synchronization misalignment, etc. The WTRU may report or transmit feedback to the gNB indicating that the UL was skipped or discarded: implicitly: through the transmission of a corresponding CSI report or a corresponding SSB-RSRP report, and explicitly: through the transmission of a flag in a corresponding CSI report or in conjunction with a corresponding SSB-RSRP report.

[0131] For example, the WTRU receives an indication for each DL RS whether the symbol corresponding to the RS is protected or not, based on one or more of the following: The WTRU may receive the indication via a bitmap representation, in which case it receives a bitmap of length N (where N is the total number of RSs), where each bit corresponds to an RS index and indicates whether the RS is protected or not; or the WTRU may receive the indication in the form of one or more sets of DL RSs, for example, a first set (e.g., set 1, protected), a second set (e.g., set 2, not protected), a first subset (e.g., set 2-1, not protected with UL transmission), a second subset (e.g., set 2-2, not protected with UL transmission with second power control), and so on.

[0132] This specification describes embodiments in which UL transmissions coincide temporally with DL RS symbols.

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

[0134] In an embodiment, the WTRU may determine that one or more configured reference signals and / or corresponding repeating timings are configured in one or more SBFD time instances. An SBFD time instance may be one or more symbols, slots, subframes, etc. As an example, the WTRU may be configured to receive DL RS in one or more of the DL subband, flexible subband, and / or UL subband (if permitted) in the configured SBFD time instances.

[0135] In an embodiment, the WTRU may determine that it is configured to make one or more UL transmissions in one or more time instances that match the time instances configured for one or more DL RS resources. For example, the WTRU may be configured to transmit ULs in one or more UL subbands within a configured time instance (e.g., an SBFD time instance) via one or more configured grants. As another example, if permitted by the NW, the WTRU may be configured to transmit ULs in one or more flexible and / or DL ​​subbands within an SBFD time instance.

[0136] In embodiments, the WTRU may determine, or be configured to, transmit or discard UL transmissions in one or more configured and / or scheduled time instances, the time instances of which may coincide in time with one or more configured DL reference signals. Embodiments relating to enabling or disabling UL transmissions within an SBFD symbol when one or more configured UL transmissions coincide in time with one or more DL reference signals are described below. Embodiments rely on the use of a Tx parameter determined based on the DL reference signal, taking into account the spatial relationship between the configured UL beam direction and the DL RS beam direction, in addition to the configured priority for UL transmission and DL reception.

[0137] In an embodiment, the WTRU may receive configuration information relating to the association of one or more DL RSs and the operating modes of one or more UL transmissions in one or more UL beam directions configured in the same time instance as the DL RSs. For example, the WTRU may be configured with separate and / or different configuration information and operating modes for each configured UL beam direction and each DL RS.

[0138] In an embodiment, the WTRU may be configured with a first operating mode for a first configured UL beam direction that can temporally coincide with a first configured DL RS, wherein the first operating mode is based on disabling UL transmission in time instances that overlap with the first DL RS symbol; the WTRU may be configured with a second operating mode for a first configured UL beam direction that can temporally coincide with a second configured DL RS, wherein the second operating mode is based on enabling UL transmission in time instances that overlap with the second DL RS symbol, and so on.

[0139] In embodiments, UL transmission and DL reception may consist of one or more SBFD time instances. As another example, a WTRU may receive instructions regarding configured DL RSs based on the corresponding beam index, SSB index, CRI, etc. As an example, a WTRU may receive configurations regarding each configured UL beam direction and operating mode for each DL RS based on semi-static and / or dynamic instructions transmitted, for example, from a gNB via RRC, MAC-CE, and / or DCI signaling. A WTRU may receive configurations via cell-specific, group-specific, and / or WTRU-specific signaling.

[0140] This specification describes embodiments relating to protected DL RS and unprotected DL RS.

[0141] In an embodiment, the WTRU may receive configuration and / or instructions for each DL RS for each configured UL beam direction, regarding whether the time instance corresponding to that DL RS is protected or not. For example, the WTRU may receive configuration from the gNB and based on semi-static or dynamic instructions via the RRC, MAC-CE, and / or DCI. As an example, the WTRU may receive instructions as part of a CSI-RS reporting configuration, where a flag instruction is used to indicate whether the time instance corresponding to the CSI-RS is protected or not. For example, a flag instruction may be received as part of a CSI-RS reporting configuration for each UL beam direction. As another example, the WTRU may receive instructions as part of the UL grant and / or UL configuration, and (specifically) for each configured UL beam direction and DL RS (e.g., SSB, CSI-RS, etc.). As yet another example, the WTRU may dynamically (e.g., via DCI and / or MAC-CE) receive instructions indicating and / or updating the operating mode for each UL beam direction and DL RS.

[0142] An example is provided in Figure 4, where a WTRU 420 is shown with a UL beam direction 422 configured toward gNb 410. A WTRU may receive a configuration based on the configured UL beam direction, which may include protected and unprotected states for one or more configured DL RSs (e.g., SSBs). In Figure 4, the green beams indicate the configured UL beam directions. Beams 413, 414, and 415 indicate protected SSBs, while beams 411, 412, 416, and 417 indicate unprotected SSBs.

[0143] In embodiments where a protected RS exists, the WTRU may receive an instruction that the first DL RS is configured to be protected, based on a first beam direction for UL transmission. Thus, the WTRU may decide not to transmit a UL transmission to the first beam direction in a time instance that coincides with the first DL RS symbol. As an example, the UL transmission may be configured via a configured grant.

[0144] In embodiments where an unprotected RS exists, the WTRU may receive an instruction that a second DL RS is configured to be unprotected, based on a first beam direction for UL transmission. Thus, the WTRU may (potentially) transmit an UL transmission, based on the first beam direction configured, for example, via a configured grant, in a time instance that may coincide with the second DL RS symbol.

[0145] In embodiments, the WTRU may decide to transmit a configured UL transmit on frequency resources, RBs, and / or subbands where UL transmits are permitted. For example, the WTRU may transmit a configured UL transmit on a UL subband in an SBFD time instance. As another example, if permitted by the NW, the WTRU may transmit a configured UL transmit on a DL and / or flexible subband in an SBFD time instance. For example, the WTRU may consider multi-stage RS protection based on the received configuration, where one or more options and protection levels apply, such as UL transmits on unprotected DL RSs, UL transmits on unprotected DL RSs with power control, and / or UL transmits are skipped or discarded. These options are described in more detail below.

[0146] UL transmission in unprotected DL RS: In an embodiment, the WTRU may decide to transmit a configured UL transmission based on the configured UL beam direction in a time instance that can coincide with a second DL RS symbol.

[0147] UL transmissions in unprotected DL RS with power control: In one embodiment, the WTRU may receive instructions that a third DL RS is configured to be unprotected in a UL transmission based on a first beam direction, while the WTRU is configured with a second power control configuration associated with the third DL RS. For example, the WTRU may decide to use the second power control configuration for a UL transmission using a first beam direction that is temporally coincidental with the third DL RS. One of the following options may apply: As an example, the WTRU may receive instructions (e.g., from the gNB, via RRC, MAC-CE, DCI, e.g., by a flag instruction) to use the second power control configuration for UL transmissions only in symbols that are temporally coincidental with the third DL RS symbol. In this case, the WTRU may use the second power control configuration to transmit the configured UL transmission within the DL RS symbol. As another example, the WTRU may receive instructions (e.g., from the gNB, via RRC, MAC-CE, DCI, e.g., by a flag instruction) to use the second power control configuration for all symbols corresponding to a configured UL transmission (e.g., a scheduled PUSCH). A WTRU may transmit all symbols corresponding to a configured UL (even symbols that do not overlap with the corresponding DL RS symbol) using a second power control configuration. For example, this may occur when a UL transmission does not cause interference to the WTRU itself, but may cause interference to other WTRUs.

[0148] Skipping or discarding UL transmissions: In embodiments, the WTRU may decide to skip and / or discard a configured UL transmission based on a first UL beam direction in a time instance that coincides with an unprotected DL RS. Based on priority conditions, beam or radio link conditions, beam index indications, bitmap indications, set indications, QCL chains, valid TCI conditions, RS measurements, and / or one or more conditions for UL transmissions overlapping with DL, it may be decided to skip and / or discard a configured UL transmission. These conditions are described in more detail below.

[0149] Priority Criteria: In embodiments, a WTRU may decide to discard a UL transmission because it is configured for or has received a configuration for a scheduled high-priority DL reception. For example, a WTRU may receive a configuration from a gNB for a corresponding DL reception via DCI, MAC-CE, and / or RRC. As an example, a WTRU may receive a configured and / or dynamic authorization to receive high-priority DL RSs, including WTRU-specific DL RSs, aperiodic DL RSs, etc., where DL RSs may be CSI-RS, TRS, etc. As another example, a WTRU may receive instructions and / or configurations for PDCCH monitoring. As yet another example, a WTRU may receive a configuration for receiving DL signals and / or channels dynamically scheduled by DCI, where the scheduled DLs have a higher priority than configured ULs.

[0150] Beam or radio link conditions: In embodiments, a WTRU may decide to discard a UL transmission due to one or more beam and / or radio link failures. For example, a WTRU may decide to measure a DL RS that is time-matched to the configured UL instead of performing the UL transmission. In other words, a WTRU may decide to skip and / or discard a UL transmission in order to measure a DL RS that is time-matched to the corresponding UL transmission. As an example, a WTRU may decide to skip and / or discard a UL transmission if it detects a BFD event, in which case the WTRU may decide to measure the DL RS as part of a BFR procedure. As another example, a WTRU may decide to skip and / or discard a UL transmission if it detects an asynchronous event, in which case the WTRU may decide to measure the DL RS as part of a synchronous procedure.

[0151] In embodiments where a WTRU decides to skip and / or discard a configured UL transmission, the WTRU may decide to send a report indicating that the UL transmission was intentionally discarded by the WTRU. For example, the WTRU may send such instructions to the gNB via UCI and / or MAC-CE, or as part of a CSI report that includes implicit or explicit instructions. As an example, the WTRU may be configured to use explicit instructions indicating that a UL transmission was discarded, for example, by sending a flag instruction in the corresponding CSI report. As another example, the WTRU may be configured to implicitly indicate a UL drop by sending a CSI report corresponding to an unprotected DL RS. In other words, a WTRU that should not measure an unprotected DL RS and should send a UL in the corresponding time instance may implicitly indicate to the gNB that the UL transmission was dropped and the DL RS was measured instead by sending a CSI report for that DL RS.

[0152] In one embodiment, the WTRU may receive, for each configured UL beam direction, an indication (e.g., from the gNB via DCI, MAC-CE, RRC, etc.) regarding whether the time instance corresponding to the DL RS is protected or not against UL transmission, based on the configured UL beam direction. One or more of the following options may apply:

[0153] Beam Index Indication: In embodiments, the WTRU may receive protected and / or unprotected DL RS beam indices (e.g., SSB index, CRI, TCI status, etc.). As an example, the WTRU may receive only indications for protected DL RS beam indices. As another example, the WTRU may receive only indications for unprotected DL RS beam indices.

[0154] Bitmap Indication: In an embodiment, the WTRU may receive indications regarding protected DL RSs 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 an index of a DL RS and indicates whether that RS is protected or unprotected.

[0155] Set Instructions: For example, a WTRU may receive instructions in the form of one or more sets of DL RS. For example, a WTRU may receive a first set of DL RS (e.g., set 1), where the DL RS included in the first set may be protected; a WTRU may receive a second set of DL RS (e.g., set 2), where the DL RS included in the second set may not be protected; a WTRU may receive a first subset of DL RS (e.g., set 2-1), where the DL RS included in the first subset may not be protected in a first power control configuration; and a second subset of DL RS (e.g., set 2-2), where the DL RS included in the second subset may not be protected in a second power control configuration.

[0156] This specification describes embodiments illustrating the configuration of DL RS with respect to whether it is protected or not.

[0157] In an embodiment, the WTRU may receive one or more DL RS configurations that may overlap with SBFD symbols, where the configuration includes an indication of whether the symbol corresponding to each RS is protected or not. For example, this determination may be: This can be based on a set of beams designated as candidate beams for beam fault detection (BFD) and beam fault recovery (BFR), on the QCL chain, on an effective TCI state, on RS measurements, or on one of the UL transmissions overlapping with DL. These conditions are described in more detail below.

[0158] Based on the set of beams designated as candidate beams for beam fault detection (BFD) and beam fault recovery (BFR), the WTRU receives one or more sets of RS signals per BWP for monitoring and detecting beam faults (e.g., the set q0, q0,0, q0,1). The WTRU receives one or more sets of (candidate) RS signals per BWP for monitoring, measuring, and selecting resources for beam fault recovery (e.g., the set q1, q1,0, q1,1), and the WTRU determines that a first RS is protected if it is configured in a set of reference signals for beam fault detection; that a second RS is not protected if it is configured in a set of reference signals for a beam fault recovery candidate beam; or that a third RS is not protected if it is not configured in either a set of reference signals for beam fault detection or a set of reference signals for a beam fault recovery candidate beam.

[0159] Based on the QCL chain: A WTRU may determine that if the first RS (e.g., SSB) is protected, then any other RSs (e.g., CSI-RS) designated as QCL sources following the first RS are also protected.

[0160] Based on a valid TCI status: A WTRU may determine that an RS associated with a valid TCI status is protected.

[0161] WTRU can measure RS, and if RS is protected, WTRU can report the measured parameters.

[0162] WTRU may transmit UL transmissions that overlap with DL RS within an SBFD symbol if DL RS is not protected and UL transmission is permitted (for example, within the UL subband within an SBFD symbol).

[0163] In an embodiment, the WTRU may receive configurations of one or more DL RSs (e.g., SSB, CSI-RS, CSI-RS for tracking (TRS), DMRS, CORESET, etc.) that may overlap with the SBFD symbol, where the configurations may include indications as to whether the symbols corresponding to (e.g., each) RS of one or more DL RSs are protected or not.

[0164] In an embodiment, the WTRU may determine (e.g., implicitly) whether the symbols corresponding to (e.g., each) RS of one or more DL RSs are protected or not based on at least one of the following three exemplary rules:

[0165] Exemplary Rule 1: Based on a set of beams designated as candidate beams for beam fault detection (BFD) and beam fault recovery (BFR): The WTRU may receive one or more sets of RS for each BWP (or CC) for monitoring and detection of beam fault detection (e.g., the set q0, q0,0, q0,1). The WTRU may receive one or more sets of (candidate) RS for each BWP (or CC) for monitoring, measuring, and selecting resources for beam fault recovery (BFR) (e.g., the set q1, q1,0, q1,1). The WTRU may determine that a first RS (one of one or more DL RSs) is protected, provided that the first RS is configured (e.g., provided, included) with one or more sets (e.g., the set q0, q0,0, q0,1) for monitoring and detection of BFD. The WTRU may determine that a second RS is unprotected, provided that the second RS is configured (e.g., provided, included) for one or more sets (e.g., the set q1, q1,0, q1,1) for a BFR (e.g., a BFR candidate beam). The WTRU may determine that a third RS is unprotected, provided that the third RS is not configured for either a set of reference signals for a BFD or a set of reference signals for a BFR (e.g., a BFR candidate beam). Based on the determination, the WTRU may implement at least one embodiment based on protected and / or unprotected RS as described throughout this Spec.

[0166] Exemplary Rule 2: Based on QCL Chains: A WTRU may determine that if a first RS (e.g., an SSB) is protected (e.g., if the first RS is determined to be a protected RS), then other RSs (e.g., CSI-RSs) designated as QCL sources following the first RS are also protected. For example, a WTRU may determine that the first SSB index is protected (e.g., the first SSB index is a protected RS). A WTRU may determine that at least one parameter of the first CSI-RS resource (e.g., QCL information, TCI state, spatial relation parameter, etc.) indicates a (QCL source) RS that is homolocatically located with the first CSI-RS resource. A WTRU may determine that the (QCL source) RS is the first SSB index, the second RS whose QCL source is the first SSB index, or the third RS whose QCL source is the second RS. For example, the second RS may represent a QCL chain rule, in which case the second RS is both the QCL source of the first CSI-RS resource and the first SSB index. Based on the QCL chain rule, the WTRU may determine that the second RS is protected; for example, the second RS is a protected RS because its QCL source is the first SSB index. Based on the QCL chain rule, the WTRU may determine that the first CSI-RS resource is (likewise) protected; for example, the first CSI-RS resource is a protected RS because its QCL source is the second RS. For example, the third RS may represent a QCL chain rule, in which the third RS is both the QCL source of the first CSI-RS resource and the second RS. Based on the QCL chain rules, the WTRU may determine that the second RS is protected, for example, because the QCL source of the second RS is a protected RS which is the first SSB index.Based on the QCL chain rules, the WTRU may determine that the third RS is (similarly) protected, for example, because the QCL source of the third RS is the protected RS, which is the second RS. Based on the QCL chain rules, the WTRU may determine that the first CSI-RS resource is (similarly) protected, for example, because the first CSI-RS resource is the protected RS, which is the third RS, which is its QCL source. Based on these decisions, the WTRU may determine that the first CSI-RS resource is protected, for example, that the first CSI-RS resource is a protected RS based on the first SSB index whose top QCL source is protected (or is a protected RS), for example, based on QCL chain rules from the top QCL source (e.g., the first SSB index) to one or more target RSs (e.g., the first CSI-RS resource, or both the first CSI-RS resource and the second RS, or all of the first CSI-RS resource, the second RS, and the third RS based on QCL chain rules).

[0167] Exemplary Rule 3: Based on Valid TCI States: A WTRU may determine that an RS associated with a valid TCI state is protected. For example, a WTRU may be configured to have multiple TCI states (e.g., via RRC signaling). A WTRU may receive a TCI enable command (e.g., via a MAC-CE message) that enables one or more of the multiple TCI states. Based on the fact that one or more TCI states have been enabled by a TCI enable command, a WTRU may determine that one or more of those TCI states are valid TCI states (e.g., those mapped to code points in the DCI fields used for dynamic TCI state selection). Based on the determination that one or more TCI states are valid TCI states, a WTRU may determine that one or more (valid) TCI states are protected (e.g., one or more TCI states are protected RS).

[0168] The WTRU may measure (e.g., receive) the RS and / or report measurement parameters determined based on the RS, provided that the RS is protected. The WTRU may transmit UL transmissions (e.g., scheduled or directed) that overlap with the DL RS in the SBFD symbol, provided that the (DL) RS is not protected and / or UL transmissions are permitted (e.g., in the UL subband within the SBFD symbol).

[0169] This specification describes embodiments relating to the dynamic updating of protected / unprotected DL RS lists, primarily using a WTRU. In embodiments, the WTRU may perform one or more of the following:

[0170] The WTRU may receive one or more RS configurations that may overlap with the SBFD symbol, and instructions indicating whether each RS is protected or not.

[0171] A WTRU may receive a configuration of a scheduled UL transmit (e.g., a UL-configured grant) scheduled within an SBFD symbol that overlaps with one or more DL RS symbols. The configuration (or activation) of a scheduled UL transmit includes the UL beam direction of the UL transmit (e.g., TCI state, QCL type).

[0172] In embodiments for updating the list of unprotected DL RSs, the WTRU may decide to send instructions to the gNB to update the protected or unprotected status of one or more unprotected DL RSs based on one or more of the following conditions:

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

[0174] In embodiments based on beam direction conditions (e.g., AOA and AOD conditions), the WTRU may determine whether the measured AOA of an unprotected DL RS falls within the AOD range of the configured UL (e.g., the configured range) (e.g., based on the beam direction of the configured or enabled UL). The WTRU transmits an identification of the DL RS and a report indicating that the measured AOA for the RS falls within the AOD range of the configured UL.

[0175] In embodiments based on CLI conditions, a WTRU may measure directional CLI based on SRS received from one or more other WTRUs, depending on the beam direction of the DL RS. If the measured CLI is above a threshold, the WTRU reports the CLI and the identification of the corresponding DL RS. The report transmitted by the WTRU may recommend and / or suggest to the gNB that the unprotected status of the corresponding DL RS be updated to protected.

[0176] In embodiments for updating the list of protected DL RSs, the WTRU may decide to send an instruction to the gNB to update the protected or unprotected status of one or more protected DL RSs based on the RSRP status, beam direction conditions (e.g., based on AOA and AOD), and / or one or more CLI conditions. These conditions are described in more detail below.

[0177] RSRP Status: The WTRU may measure the RSRP for a protected DL RS. If the measured RSRP of a protected DL RS is lower than the corresponding threshold, the WTRU reports the identification and measurement of the corresponding DL RS to the gNB. The beam used to receive the DL RS and / or RSRP measurements may be based on the Rx beam configured or directed for the DL RS (e.g., TCI status). The beam used to receive the DL RS and / or RSRP measurements may be based on the direction of the configured or enabled UL beam.

[0178] Beam orientation conditions (e.g., based on AOA and AOD): The WTRU may determine whether the measured AOA of the protected DL RS is within the range of the configured UL's AOD. The WTRU will send a report indicating that the measured AOA for this RS is not within the range of the configured UL's AOD.

[0179] CLI Conditions: A WTRU may measure directional CLI based on the beam direction of the DL RS and based on SRS received from one or more other WTRUs. If the measured CLI is below a threshold, the WTRU reports the CLI and the identification of the corresponding DL RS. The report transmitted by the WTRU may recommend and / or suggest to the gNB that the protected status of the corresponding DL RS be updated to unprotected. The WTRU receives confirmation or instructions from the gNB to update or confirm the designated protected or unprotected DL RS.

[0180] Embodiments relating to triggers for measuring protected or unprotected RS are described below. In embodiments, the WTRU may perform measurements to determine any of the aforementioned conditions based on: an explicit instruction, on which the WTRU performs measurements based on a configured period (e.g., a longer-than-normal period); on a configured periodicity (e.g., if the period is longer than normal); or an implicit instruction, which may be event-based, for example, in the case of beam fault detection, on which the WTRU performs measurements for a configured time window or until the trigger event stops.

[0181] In embodiments, the WTRU may receive configuration and / or enable configurations for scheduled UL transmissions (e.g., via UL-configured grants) scheduled for one or more SBFD time instances where the DL RS symbols and times can coincide. The instructions, configuration information, and / or enablement for scheduled UL transmissions may include UL beam directions for the UL transmissions (e.g., via TCI status, QCL type). For each configured UL beam direction and each DL RS, the WTRU may receive instruction information regarding whether the corresponding DL RS is protected or not.

[0182] In one embodiment, the WTRU may determine that it may be necessary to update one or more configured unprotected DL RSs and change them to protected DL RSs. Alternatively, the WTRU may determine that it may be necessary to update one or more configured protected DL RSs and change them to unprotected DL RSs. As an example, the WTRU may decide to change and update each configured UL beam direction and DL RSs that are temporally consistent with the corresponding configured UL transmission.

[0183] This specification describes embodiments for updating the list of unprotected DL RS.

[0184] In an embodiment, a WTRU may decide and / or be configured to send instructions to update the status of one or more DL RSs from unprotected to protected, in a timely manner with a configured UL transmission. For example, a WTRU may send instructions to a gNB. For example, a WTRU may send instructions via UCI, MAC-CE, and / or RRC signaling. For example, a WTRU may send instructions as part of a CSI report scheduled to and / or configured for a WTRU.

[0185] In an embodiment, the WTRU may decide to send instructions to update the state of one or more DL RSs based on the state of a channel parameter (e.g., RSRP) and / or the state of the beam direction. These conditions are described in more detail below.

[0186] Channel Parameters: For example, a WTRU may measure one or more channel parameters based on one or more unprotected DL RSs, and the WTRU may compare the measured parameters with one or more (pre-configured) thresholds. As an example, a WTRU may measure the RSRP of a DL RS. As an example, a WTRU may receive and measure channel parameters based on a DL RS using an Rx beam determined by the WTRU to receive the DL RS. For example, a WTRU may determine the Rx beam based on the configured TCI state of the corresponding DL RS. As another example, a WTRU may use a Tx beam determined by the WTRU to transmit a configured and / or enabled UL transmit in order to receive and measure channel parameters based on a DL RS. For example, a WTRU may determine the Tx beam based on the configured and / or enabled UL beam direction and / or the UL TCI state configured and / or determined for a configured UL transmit. A WTRU may compare measured channel parameters to corresponding (pre-configured) thresholds, where the thresholds are configured via RRC, MAC-CE, and / or DCI. For example, a WTRU may compare a measured RSRP based on DL RS to a (pre-configured) RSRP threshold. The WTRU may determine that a measured channel parameter (e.g., RSRP) based on at least one DL RS is higher than a (pre-configured) threshold and decide to send instructions and / or reports to the gNB, for example. As an example, the report may include the identification and / or index of the measured channel parameter (e.g., RSRP) and / or the corresponding DL RS. As an example, the identification and / or index of the DL RS may include the SSB index, CRI, beam index, etc. Furthermore, the report may include an indication of whether the channel parameters were measured based on the direction of the Rx beam and / or Tx beam in the WTRU. As an example, the report may include an indication (e.g., an indication by flag) that the measured parameter exceeded the corresponding threshold.

[0187] Beam direction conditions (e.g., based on the aiming angles of the UL Tx beam and DL Rx beam): In embodiments, the WTRU may measure the aiming angles of the UL Tx beam and the unprotected DL RS beam, and the WTRU may determine whether the measured aiming angles are within a (pre-configured) threshold range. As another example, the WTRU may measure the AOA of the unprotected DL RS, compare it to the AOD of the configured UL beam direction, and determine whether the measured AOA is within a (pre-configured) range of the measured AOD. The WTRU may receive a configuration and / or corresponding thresholds and / or range limits may be (pre-configured), the thresholds may be configured by RRC, MAC-CE, and / or DCI via gNB.

[0188] If the WTRU determines that the measured aiming angle is within a (pre-configured) threshold range and / or that the measured AOA is within a (pre-configured) range of the measured AOD, the WTRU may decide to send instructions and / or reports to, for example, the gNB. For example, the report may include the measured aiming angle, AOA, AOD, and / or the identification and / or index of the corresponding DL RS. For example, the identification and / or index of the DL RS may include the SSB index, CRI, beam index, TCI status, QCL type, etc. Furthermore, the report may include instructions that the measured aiming angle is within a threshold range and / or that the measured AOA is within the range of the measured AOD.

[0189] Figure 5 shows an exemplary embodiment of the beam direction relationship between the configured UL beam direction and the DL beam direction of one or more DL RSs. Beam 522 indicates the UL beam direction, and the DL RS beam directions are indicated by DL beams 511, 512, 513, 514, and 515. In Figure 5, the UL transmit is configured in the UL subband of the SBFD symbol, while one or more DL RS transmits are configured in the DL subband within the same symbol.

[0190] In an embodiment, as shown in Figure 5A, the WTRU may determine the AOA of the DL RS in addition to the aiming of the Rx beams 511, 512, 513, 514, and 515 corresponding to the DL RS. As shown in Figure 5B, the WTRU may also determine the AOD and aiming of the Tx beam 522 corresponding to the configured UL beam direction. Based on the determined AOA and aiming of the DL RS, the WTRU may identify DL RS where the measured aiming angle is within the range of the measured aiming, and / or DL ​​RS where the measured AOA is within the range of the measured AOD of the configured UL beam direction. For example, in Figure 5, DL RS 514 and 515 satisfy the beam direction condition based on the configured UL beam direction.

[0191] This specification describes embodiments relating to the measured CLI state. In embodiments, a WTRU may measure directional CLI based on one or more SRS signals received from one or more other WTRUs. A WTRU may decide to measure directional CLI based on one or more Rx spatial filters used to receive unprotected DL RS. For example, a WTRU may receive configuration information for receiving and measuring SRS signals, including time and frequency resources and corresponding SRI. For example, a WTRU may measure SRS-RSRP, or, for example, CLI-RSSI, based on the received SRS signaling.

[0192] In an embodiment, the WTRU may compare the measured directional CLI with a (pre-configured) threshold. For example, the WTRU may receive a configuration and / or a corresponding threshold may be (pre-configured), the threshold may be configured via RRC, MAC-CE, and / or DCI, for example, via gNB.

[0193] In embodiments where the WTRU determines that the measured directional CLI (e.g., SRS-RSRP) is higher than a (pre-configured) threshold, the WTRU may decide to send instructions and / or reports to, for example, the gNB. For example, the reports may include the identification and / or index of the measured directional CLI and / or the corresponding DL RS. For example, the identification and / or index of the DL RS may include the SSB index, CRI, beam index, TCI status, QCL type, etc. Furthermore, the reports may include instructions indicating that the measured directional CLI is above the threshold.

[0194] This specification describes embodiments of WTRUs relating to instruction reports. In embodiments, a WTRU may transmit a report containing requests, suggestions, and / or recommendations for switching a reported unprotected DL RS to a protected DL RS. For example, a WTRU may transmit a report as part of a CSI report. A WTRU may receive instructions and / or confirmations from, for example, a gNB, to update and / or confirm a reported protected DL RS or an unprotected DL RS.

[0195] This specification describes embodiments for updating the list of protected DL RSs. In embodiments, a WTRU may be configured to determine and / or transmit instructions to update the state of one or more DL RSs so as to coincide with the timing of a configured UL transmission transitioning from protected to unprotected. As an example, the WTRU may transmit the instructions to the gNB. In embodiments, the WTRU may transmit the instructions via UCI, MAC-CE, and / or RRC signaling. As an example, the WTRU may transmit the instructions as part of a CSI report scheduled to and / or configured for the WTRU. In embodiments, the WTRU may decide to transmit instructions based on one or more conditions of the state of channel parameters (e.g., RSRP), beam direction, and / or CLI. These conditions are described in more detail below.

[0196] State of channel parameters (e.g., RSRP): In embodiments, a WTRU may measure one or more channel parameters based on one or more protected DL RSs, where the WTRU may compare the measured parameters with one or more (pre-configured) thresholds. As an example, a WTRU may measure the RSRP of a DL RS. In embodiments, a WTRU may receive and measure channel parameters based on a DL RS using an Rx beam determined by the WTRU to receive the DL RS. For example, a WTRU may determine the Rx beam based on the configured TCI state of the corresponding DL RS. In embodiments, a WTRU may use a Tx beam determined by the WTRU to transmit a configured and / or enabled UL transmit in order to receive and measure channel parameters based on a DL RS. For example, a WTRU may determine the Tx beam based on a configured and / or enabled UL beam direction and / or a UL TCI state configured and / or determined for a configured UL transmit.

[0197] The WTRU may compare the measured channel parameters to corresponding (pre-configured) thresholds, which may be configured via RRC, MAC-CE, and / or DCI. For example, the WTRU may compare the RSRP measured based on DL RS to a (pre-configured) RSRP threshold. The WTRU may determine that a measured channel parameter (e.g., RSRP) based on at least one DL RS is lower than a (pre-configured) threshold and decide to send an instruction and / or report to, for example, the gNB. As an example, the report may include the identification and / or index of the measured channel parameter (e.g., RSRP) and / or the corresponding DL RS. As an example, the identification and / or index of the DL RS may include the SSB index, CRI, beam index, etc. Furthermore, the report may include an indication of whether the channel parameters were measured based on the direction of the Rx beam and / or Tx beam in the WTRU. As an example, the report may indicate that the measured parameter is below the corresponding threshold, for example, by a flag.

[0198] Beam Direction Conditions: In embodiments (e.g., based on the aiming angles of the UL transmit beam and DL receive beam), the WTRU may measure the aiming angles of the UL transmit beam and the protected DL receive beam, and the WTRU may determine whether the measured aiming angles are within a (pre-configured) threshold range. As another example, the WTRU may measure the AOA of the protected DL RS, compare it to the AOD of the configured UL beam direction, and determine whether the measured AOA is not within a (pre-configured) range of the measured AOD. The WTRU may receive a configuration and / or corresponding thresholds and / or range limits, where the thresholds may be received, for example, from a gNB, via RRC, MAC-CE, and / or DCI.

[0199] In embodiments where the WTRU determines that the measured boresight angle is not within a (pre-configured) threshold range and / or that the measured AOA is not within a (pre-configured) range of the measured AOD, the WTRU may decide to send instructions and / or a report to, for example, the gNB. For example, the report may include identification and / or indexes of the measured boresight, AOA, AOD, and / or the corresponding DL RS. For example, the identification and / or indexes of the DL RS may include the SSB index, CRI, beam index, TCI status, QCL type, etc. Furthermore, the report may include instructions indicating that the measured boresight angle is not within a threshold range and / or that the measured AOA is not within the range of the measured AOD.

[0200] CLI Status: In embodiments, a WTRU may measure directional CLI based on one or more SRS signals received from one or more other WTRUs. A WTRU may decide to measure directional CLI based on one or more Rx spatial filters used to receive protected DL RS. For example, a WTRU may receive configuration information for receiving and measuring SRS signals, including time and frequency resources and corresponding SRIs. For example, a WTRU may measure SRS-RSRP, or CLI-RSSI, etc., based on received SRS signaling. A WTRU may compare the measured directional CLI to (pre-configured) thresholds. For example, a WTRU may receive and / or (pre-configured) a configuration with corresponding thresholds, where the thresholds may be configured via RRC, MAC-CE, and / or DCI, for example, via a gNB. In embodiments where a WTRU determines that the measured directional CLI (e.g., SRS-RSRP) is lower than a (pre-configured) threshold, the WTRU may decide to send instructions and / or reports to, for example, a gNB. In embodiments, the report may include identification and / or indexing of the measured directional CLI and / or corresponding DL RS. For example, the DL RS identification and / or index may include SSB index, CRI, beam index, TCI status, QCL type, etc. Furthermore, the report may include an indication that the measured directional CLI is below a threshold.

[0201] In embodiments, reports that a WTRU may transmit may include requests, suggestions, and / or recommendations to switch a reported protected DL RS to an unprotected DL RS. For example, a WTRU may transmit a report as part of a CSI report. A WTRU may receive instructions and / or confirmations, for example, from a gNB, to update and / or verify a specified protected DL RS or unprotected DL RS.

[0202] This specification describes embodiments of triggers for measuring protected or unprotected DL RS.

[0203] In embodiments, the WTRU may be determined or configured to perform measurements to determine one or more of the aforementioned conditions based on one or more of the explicit and / or implicit instructions, these indicators of which are described below.

[0204] Explicit Instructions: In embodiments, the WTRU may be determined or configured to periodically measure one or more parameters. The WTRU may receive time intervals for measuring parameters based on configuration information received, for example, from the gNB, via DCI, MAC-CE, and / or RRC signaling. As an example, this time interval may be longer than the time configured for CSI-RS measurements.

[0205] Implicit Instructions: In embodiments, the WTRU may be determined or configured to perform measurements based on the detection of one or more events. For example, the WTRU may detect beam fault events, mis-synchronization events, etc. Thus, the WTRU may decide to perform measurements, where it may perform measurements over a (pre-configured) time window based on counters and / or until the trigger event stops and is no longer detected. The WTRU may receive time windows, maximum counter limits, and / or other configurations based on configuration information received, for example, from the gNB, via DCI, MAC-CE, and / or RRC signaling.

[0206] This specification describes embodiments for reporting the measured RSRP of DL RS based on the direction of the Tx beam.

[0207] In some embodiments, the WTRU performs one or more of the following:

[0208] WTRU may receive one or more RS configurations that overlap with SBFD symbols.

[0209] A WTRU may receive a scheduled UL transmission configuration scheduled with an SBFD overlapping one DL RS symbol. The configuration may include the direction of the UL beam (e.g., TCI state, QCL type).

[0210] The WTRU may measure RSRP based on one or more DL RS beams, based on the Tx beam direction used for the configured UL beam direction. The following steps may be performed: The WTRU determines the Tx spatial filter for the configured UL transmit based on the configured UL beam direction, TCI state, and QCL type. The WTRU receives the DL RS using the determined transmit spatial filter (coefficient) (e.g., based on beam correspondence or reciprocity). For example, the WTRU may select the Rx spatial filter and / or TCI state used to receive the DL RS so as to match, map, correspond, and / or relate to the determined Tx spatial filter and / or TCI state used by the WTRU for transmitting the configured UL signal and / or channel. In yet another example, the WTRU may select the receive beam direction used to receive the DL RS so that the angle of arrival of the selected receive beam is within the (configured) range of the transmit angle of the configured UL beam direction. The WTRU measures the “directional” RSRP from one or more downlink DL RS using the selected receive spatial filter and / or beam direction. WTRU reports the measured RSRP to gNB.

[0211] In an embodiment, the WTRU may report a QCL-Type E relationship between one or more DL RSs and configured ULs if the measured “directional” RSRP is higher than a threshold. The WTRU indicates the correspondence between DL RSs and configured UL beams via QCL-Type E for DL ​​RSs. QCL-Type E is different from QCL TYPE D. QCL-Type E is not used for UL transmission. QCL-Type E indicates DL beam directions that are correlated with UL beam directions. QCL-Type E indicates DL beam directions whose correlation with UL beam directions exceeds a threshold. For example, in Figure 5, configured ULs are correlated with DL RS 4 and DL RS 5 by QCL-Type E. The WTRU reports a list of determined QCL-Type E DL RS resources / pairs correlated with configured ULs (e.g., DL RS, DL TCI state, DL and UL TCI state pairs, or DL ​​RS and UL SRI pairs).

[0212] In embodiments, the WTRU may receive configuration information and / or enable configuration for scheduled UL transmissions (e.g., via UL-configured grants) scheduled for one or more SBFD time instances where the DL RS symbols and times can coincide. The instructions, configuration, and / or enablement for scheduled UL transmissions may include UL beam directions for the UL transmissions (e.g., via TCI status, QCL type). For each configured UL beam direction and each DL RS, the WTRU may receive instruction information regarding whether the corresponding DL RS is protected or not.

[0213] In embodiments, the WTRU may be configured to determine or measure one or more channel parameters based on one or more DL RSs, depending on the Tx beam direction used for UL transmission to the configured UL beam direction. For example, the WTRU may receive configuration information from the gNB, for example, via DCI, MAC-CE, and / or RRC signaling. In another example, the WTRU may measure one or more channel parameters, including RSRP, SINR, RSRQ, etc., where the terms RSRP, SINR, RSRQ, and channel parameters may be used interchangeably but not inconsistent with the content of this disclosure.

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

[0215] In one embodiment, the WTRU may determine the configured Tx spatial filter for UL transmission based on the configured UL beam direction, TCI state, and / or QCL type.

[0216] In one embodiment, the WTRU may use the determined transmit spatial filter (coefficient) to receive the downlink RS.

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

[0218] In an embodiment, the WTRU may select an Rx spatial filter and / or TCI state to be used to receive DL RS, and may match, map, correspond to, and / or associate with a determined Tx spatial filter and / or TCI state that the WTRU can use to transmit configured UL signals and / or channels.

[0219] In the embodiment, the WTRU may select the direction of the Rx beam used to receive DL RS, and the arrival angle of the selected Rx beam is within a (pre-configured) range of the transmission angle of the configured UL beam direction.

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

[0221] Embodiments relating to the relationship between uplink beams and downlink beams are described herein. In embodiments, the relationship between an uplink beam and one or more downlink beams may be determined, defined, or used, and the relationship may be at least one of the beam alignment level (e.g., the aiming angles of the UL Tx beam and DL Rx beam within a given threshold), the beam correlation level (e.g., the correlation level between the UL transmit beam and the DL receive beam), the CLI beam interference level (e.g., interference from the UL transmit beam to the DL receive beam), and the power level of the Tx beam for a particular Rx beam direction.

[0222] The relationships may be referred to as QCL Type E, Tx-Rx beam correspondence level, Tx-Rx beam correlation level, Tx-Rx beam matching level, Tx beam power level, CLI beam interference level, and Tx-Rx beam related level. Hereinafter, the terms 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 related level may be used interchangeably, but will still be consistent with the present invention.

[0223] In the following context, SBFD may be used in compatibility with full-duplex systems where uplink and downlink signals overlap using the same time / frequency resources.

[0224] The WTRU may determine relationships based on one or more of the following: uplink beam information for uplink transmission (e.g., SRI, TCI, QCL Type-D), a set of downlink beams configured for measurement (e.g., CSI-RS, SSB, and associated QCL Type-D), and one or more thresholds for determining the level of relationship (e.g., thresholds for determining correlation level, CLI, power level, angular matching, etc.).

[0225] A WTRU may decide to report one or more QCL Type E if one or more of the following conditions are met: WTRU may be authorized to perform UL transmissions with a specific UL beam index (e.g., SRI, TCI state) and the Tx-Rx beam correlation level exceeds a threshold in at least one DL beam; WTRU may be configured to report a list of DL beams whose Tx-Rx beam correlation level exceeds a threshold; WTRU may decide to report one or more DL beam indices whose CLI interference level exceeds a threshold when a UL beam is used; UL beams may be designated beams from gNB for UL transmissions, or a list of candidate UL transmission beams potentially used for UL transmissions from the WTRU; WTRU may be configured to transmit UL signals within SBFD symbols (or full-duplex symbols); and WTRU may have the capability to perform full-duplex operation (e.g., simultaneous transmit / receive, or transmit / receive on the same time / frequency resources).

[0226] In embodiments, one or more classes of QCL types may be used or defined, the first class of QCL types may be used to determine or indicate channel characteristics (e.g., delay spread, Doppler shift, Doppler spread, mean delay, and spatial receive filter) based on their 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 their association with one or more downlink signals and one or more uplink signals. The 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 association with both at least one downlink reference signal and at least one uplink reference signal (e.g., {CRI,SRI}), and a WTRU may use the first class of QCL types for DL ​​reception or UL transmission on a first type of time resource (e.g., non-SBFD symbols, non-SBFD slots, semi-duplex symbols, semi-duplex slots), and a WTRU may use the second class of QCL types for DL ​​reception or UL transmission on a second type of time resource (e.g., SBFD symbols, SBFD slots, full-duplex symbols, full-duplex slots).

[0227] This specification describes embodiments relating to group instruction and updating of protected and unprotected DL RSs. In embodiments, a WTRU may receive configuration information and / or enable configuration for scheduled UL transmissions (e.g., via UL configured grants) scheduled for one or more SBFD time instances where one or more DL RS symbols and times can coincide. The instruction, configuration, and / or enablement of scheduled UL transmissions may include UL beam directions for UL transmissions (e.g., via TCI status, QCL type). For each configured UL beam direction and each DL RS, the WTRU may receive instruction information regarding whether the corresponding DL RS is protected or unprotected.

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

[0229] In embodiments, the WTRU may monitor to receive changes and / or updates to the list of protected and / or unprotected RS for a first configured group. For example, the WTRU may monitor to receive group commands, for example, via a group DCI, where the CRC in the DCI is scrambled, for example, using a first G-RNTI. Using the received group commands, the WTRU may disable and / or enable configured UL transmissions based on the updated configuration of protected and / or unprotected RS. For example, Figure 6 shows a gNb410 with seven DL RS beam directions (611, 612, 613, 614, 615, 616, 617). Figure 6 shows an example of a WTRU420 that can be configured in a first group and / or active group, where one or more DL RSs may be configured as protected DL RSs (e.g., DL RS612, 613, and 614) and one or more DL RSs may be configured as unprotected DL RSs (e.g., DL RS611, 615, 616, and 617).

[0230] This specification describes embodiments relating to group switching. In embodiments, the WTRU may monitor a list of protected DL RSs and unprotected DL RSs and receive configurations relating to updates and / or changes in a second or more candidate groups. In one embodiment, the WTRU may monitor to receive group commands, for example, via a group DCI, where the CRC in the DCI is scrambled, for example, using a second G-RNTI.

[0231] In a further embodiment, the WTRU may measure one or more channel parameters based on one or more protected DL RSs and / or unprotected DL RSs included in the first and second DL RS groups, and the WTRU may determine a preferred list of protected and unprotected DL RSs based on the measured parameters and one or more conditions. In an embodiment, the WTRU may determine a preferred list of protected and unprotected RSs based on the measured RSRP, beam direction, CLI, etc., as described above.

[0232] In a further embodiment, based on the determined list of preferred protected and unprotected RSs, the WTRU may determine that the DL RS configuration in at least one second candidate group is closer to the list of preferred protected and unprotected RSs determined by the WTRU. In an embodiment, the WTRU may determine, based on, for example, measured RSRP, beam direction, CLI, etc., that the second candidate group includes all protected DL RSs preferred by the WTRU. Thus, the WTRU may send a request, proposal, and / or recommendation to switch to the second group as the valid group of protected and unprotected DL RSs. In one embodiment, the WTRU may send a request to the gNB via UCI, MAC-CE, and / or RRC signaling. In a further embodiment, the WTRU may send a request as part of a configured CSI report and via flag instructions and / or instructions regarding the second group determined by the WTRU as the target of the switch. In one embodiment, the WTRU may receive confirmation or instructions from the gNB to update or confirm the designated valid group and / or first group to which the WTRU may switch.

[0233] Figure 7 is a flowchart illustrating an example of a process performed by a WTRU to enable / disable UL transmissions in an SBFD symbol containing a DL reference signal based on spatial relationships, according to embodiments described herein. In 710, the process includes receiving first configuration information relating to one or more downlink (DL) reference signals (RS). In 712, the process includes receiving second configuration information indicating first power control information and second power control information, and for each of the one or more DL RSs, indicating whether each DL RS is protected or unprotected in a subband non-superimposed full-duplex (SBFD) symbol, and for unprotected DL RSs in an SBFD symbol, the second configuration information indicates whether to adjust the power of the associated UL transmission. In 714, the process includes transmitting a UL transmission in a resource overlapping with an unprotected SBFD symbol, including the first DL RS of the one or more DL RSs.

[0234] Figure 8 is an example flowchart of the process performed by the WTRU to enable / disable upload transmissions in SBFD symbols containing DL reference symbols based on the protection status of the reference symbols. At 810, the process includes receiving a configuration of one or more download reference symbols (DL RS) that overlap with a subband full-duplex (SBFD) symbol. At 812, the process includes determining that the first DL RS is protected for the SBFD symbol. At 814, the process includes determining that the second DL RS is not protected for the SBFD symbol. At 816, the process includes uplink (UL) transmission in the subband of the SBFD symbol that overlaps with the unprotected DL RS.

[0235] Figure 9 is a flowchart illustrating an example of a process performed at a WTRU to dynamically update the protection status of downlink reference symbols (DL RSs). At 910, the process includes receiving first configuration information for one or more downlink reference symbols (DL RSs) that overlap with one or more subband full-duplex (SBFD) symbols. At 912, the process includes receiving WTRU-specific information for each DL RS indicating whether the RS symbol is protected or unprotected. At 914, the process includes transmitting an updated instruction to the base station regarding the protected or unprotected status of at least one DL RS, based on the condition that the measured crosslink interference (CLI) is higher than a predetermined CLI threshold.

[0236] While the features and components of the present invention are described in specific combinations in preferred embodiments, each feature or component can be used alone without other features or components of the preferred embodiments, or in various combinations with or without other features or components of the present invention. Although the embodiments described herein may assume specific protocols, it should be understood that the solutions described herein are not limited to this scenario and are applicable to other wireless systems.

Claims

1. A method implemented in WTRU, wherein the method is Receiving first configuration information for one or more downlink (DL) reference signals (RS), Receiving second configuration information indicating first power control information and second power control information, wherein for each of the one or more DLRSs, the DLRS is protected or not protected in a subband non-overlapping full-duplex (SBFD) symbol, and for DLRSs not protected in an SBFD symbol, the second configuration information indicates whether the WTRU should adjust the power of the associated UL transmission. Sending a UL transmission in a resource that overlaps with an unprotected SBFD symbol, including the first DL RS of the one or more DL RSs, A method that includes [a certain feature].

2. The method according to claim 1, wherein it is decided to transmit a UL transmission without power adjustment and the first DL RS is not protected, and the UL transmission is transmitted based on the first power control information.

3. The method according to claim 1, wherein it is decided to transmit a UL transmission with power adjustment, and the first DL RS is not protected, and the UL transmission is transmitted using a resource based on the second power control information.

4. The method according to claim 1, wherein it is determined that no UL transmission is performed under the condition that the first DL RS is protected.

5. The method according to any one of claims 1 to 4, further comprising receiving one or more indications for protected or unprotected beam indices.

6. The method according to any one of claims 1 to 4, wherein the second configuration information indicating whether each DL RS is protected or not is based on a bitmap indication.

7. The method according to any one of claims 1 to 4, wherein the second configuration information indicating whether each DL RS is protected or not is based on a set of protected DL RSs and a set of unprotected DL RSs.

8. The method according to claim 4, further comprising sending a report indicating that the UL transmission was not performed.

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

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

11. It is WTRU, Processor and Transmitter and receiver, Equipped with, The aforementioned processor, Receiving first configuration information for one or more downlink (DL) reference signals (RS), Receiving second configuration information indicating first power control information and second power control information, wherein for each of the one or more DLRSs, the DLRS is protected or not protected in a subband non-overlapping full-duplex (SBFD) symbol, and for DLRSs not protected in an SBFD symbol, the second configuration information indicates whether the WTRU should adjust the power of the associated UL transmission. Sending a UL transmission in a resource that overlaps with an unprotected SBFD symbol, including the first DL RS of the one or more DL RSs, A WTRU configured to cause the aforementioned transceiver to perform this operation.

12. The WTRU according to claim 11, wherein the processor is further configured to cause the transceiver to transmit the UL transmission based on the first power control information, under the conditions that power adjustment is not required and the first DL RS is not protected.

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

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

15. The WTRU according to any one of claims 11 to 14, wherein the processor is further configured to cause the transceiver to receive one or more instructions regarding protected or unprotected beam indices.

16. The second configuration information indicating whether each DL RS is protected or not is a WTRU according to any one of claims 11 to 14, based on a bitmap indication.

17. The WTRU according to any one of claims 11 to 14, wherein the second configuration information indicating whether each DL RS is protected or not is based on a set of protected DL RSs and a set of unprotected DL RSs.

18. The WTRU according to 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 according to claim 11, wherein one of the DL RSs is indicated as protected based on the beam direction of the UL transmission.

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

Images