WO2025029944A1

WO2025029944A1 - Signaling framework for multi-beam uplink configuration

Info

Publication number: WO2025029944A1
Application number: PCT/US2024/040424
Authority: WO
Inventors: Nazli KHAN BEIGI; Jonghyun Park; Paul Marinier; Moon Il Lee
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2023-08-02
Filing date: 2024-07-31
Publication date: 2025-02-06
Anticipated expiration: 2026-02-02

Abstract

A signaling framework for multi-beam uplink (UL) configuration may be disclosed herein. A WTRU may be configured with multi-beam configuration for UL transmission, where the signaling framework may be provided via different methods for efficient management on radio resources. The WTRU may receive configuration for a configured or dynamic UL grant (e.g., via DCI) indicating the time and frequency resources. The WTRU may determine to use a first beam direction or a second beam direction for an UL transmission associated with the configured and/or dynamic grant, based on CLI measurements. The WTRU may transmit the UL transmission using the determined first or second beam direction, for example based on one or more primary and/or secondary TCI states and/or an evolved QCL type.

Description

SIGNALING FRAMEWORK FOR MULTI-BEAM UPLINK CONFIGURATION

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent Application No. 63/517,243, filed on August 2, 2023, the entire contents of which are incorporated herein by reference.

BACKGROUND

[0002] New Radio (NR) duplex operation may be used. This technology may be a foundation in improving conventional time-division duplexing (TDD) operation by enhancing uplink (UL) coverage, improving capacity, reducing latency, etc. The conventional TDD may be based on splitting the time domain between the uplink and downlink. The feasibility of allowing full duplex (e.g., subband non-overlapping full duplex (SBFD)) at the gNB within a conventional TDD band may be investigated. FIG. 2 illustrates an example of an SBFD configuration in a TDD framework.

[0003] The realization of SBFD may be subject to resolving the key challenges raised due to cross-layer interferences (CLI). In an SBFD (e.g., or dynamic/flexible TDD) framework, a potential aggressor cell may switch from UL to DL or vice-versa, causing CLI on potential victim gNBs and wireless transmit/receive units (WTRUs). In UL-to-DL CLI, the UL transmission from aggressor WTRUs may cause directional CLI at the victim WTRUs (e.g., as shown in FIG. 3). FIG. 3 shows an example of CLI, including inter-gNB CLI, inter-WTRU CLI, and CLI between WTRUs and gNBs. The CLI can be measured at both the victim and/or aggressor WTRUs.

SUMMARY

[0004] A signaling framework for multi-beam uplink (UL) configuration may be disclosed herein. A wireless transmit/receive unit (WTRU) may be configured with multi-beam configuration for UL transmission, where the signaling framework may be provided via different methods for efficient management on radio resources. The WTRU may receive configuration for a configured or dynamic UL grant (e.g., via DCI) indicating the time and frequency resources. The WTRU may determine to use a first beam direction or a second beam direction for an UL transmission associated with the configured and/or dynamic grant, based on CLI measurements. The WTRU may transmit the UL transmission using the determined first or second beam direction, for example based on one or more primary and/or secondary TCI states and/or an evolved QCL type. [0005] In an example related to multiple CG PLISCH transmission, the WTRU may receive configuration of multiple CG PUSCH transmission occasions (e.g., time and/or frequency resources) in a (e.g., each) period of the configured CG PUSCH. The WTRU may select a CG PUSCH transmission occasion associated with or based on the selected TCI state or the selected beam with evolved QCL Type. The WTRU may transmits the UL transmission using the selected TCI state/beam direction and the determined CG PUSCH transmission occasion. The WTRU may report the determined TCI state and/or corresponding patterns via UCI to the gNB. The WTRU may transmit the UL based on the determined and reported TCI state, e.g., using the one or more patterns of configured time and freq, resources, on condition that the UE determines the pattern has an association with the TCI state.

[0006] For example, the WTRU may receive (e.g., via DCI) a configuration for a configured or dynamic uplink (UL) grant indicating one or more time and frequency resources from a network (e.g., a gNB). The WTRU may determine to use a first beam direction or a second beam direction for a UL transmission associated with the configured or dynamic grant based on one or more cross-link interference (CLI) measurements. For example, the WTRU may use the beam direction having the lower measured CLI. The WTRU may select the second beam direction based on one or more of a transmission configuration index (TCI) mapping and a quasi-colocation (QCL) type. The WTRU may transmit, to the network, the UL transmission using the determined beam direction.

[0007] For example, the WTRU may select the second beam direction based on a TCI mapping. In this example, the WTRU may receive an indication of the first beam direction as a primary beam direction based on a configured or activated TCI state, a set of beam directions comprising the second beam direction, and a mapping between TCI states and respective beam directions, and may select the second beam direction from the set of beam directions based on the mapping between TCI states and respective beam directions and the CLI measurements. Additionally and/or alternatively, the WTRU may select the second beam direction based on a QCL type. In this example, the WTRU may receive an indication of the first beam direction as a primary beam direction (e.g., where the first beam direction is associated with a first QCL type), a set of beam directions comprising the second beam direction, and a mapping between the set of beam directions and respective QCL types. The WTRU may select the second beam direction from the set of beam directions based on the second beam direction being associated with a second QCL type and the CLI measurements. The first QCL type may be QCL-Type D and the second QCL type may be QCL-Type E. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0010] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.

[0011] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.

[0012] FIG. 2 illustrates an example of an SBFD configuration in a TDD framework.

[0013] FIG. 3 shows an example of CLI, including inter-gNB CLI, inter-WTRU CLI, and CLI between WTRUs and gNBs.

[0014] FIG. 4 illustrates an example of WTRU-oriented UL beam selection (e.g., for interference avoidance).

DETAILED DESCRIPTION

[0015] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0016] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and/or a “STA”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE. [0017] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the I nternet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0018] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

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

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

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

[0022] I n an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).

[0023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g, a eNB and a gNB).

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

[0025] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

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

[0027] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.

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

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

[0030] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

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

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

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

[0037] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

[0038] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

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

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

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

[0042] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

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

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

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

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

[0047] Although the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

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

[0049] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11 e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.

[0050] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g, 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g, every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g, only one station) may transmit at any given time in a given BSS. [0051] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0052] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0053] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control/Machine- Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0054] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0055] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

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

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

[0058] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time). [0059] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0060] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

[0062] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. [0063] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

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

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

[0066] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

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

[0068] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0069] While measuring the cross-link interference (CLI) at victim WTRUs may be considered as a means of measuring and mitigating CLI, the one-to-one WTRU-to-WTRU CLI measurement per aggressor WTRU may cause large overhead and complexity for victim WTRUs, especially in scenarios with multiple aggressor WTRUs. On the other hand, the victim WTRUs may need to report the measured CLI to the gNB for the CLI mitigation methods, whereas the aggressor WTRUs may perform CLI mitigation techniques (e.g, CLI avoidance) at the aggressor WTRUs resulting in faster actions. Thus, enhancements on the procedures to measure and mitigate the CLI at the aggressor WTRUs are required. One or more embodiments for allowing a potential aggressor WTRU to avoid causing WTRU-to-WTRU CLI in SBFD configurations may be disclosed herein.

[0070] As used herein, the terms “a,” “an,” and/or similar phrases are to be interpreted as “one or more” and/or “at least one.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “one or more” and/or “at least one.” The term “may” is to be interpreted as “may, for example.” A symbol ” (e.g, a forward slash) may be used herein to represent “and/or”, where, for example, “A/B” may mean “A and/or B.” [0071] A wireless transmit/receive unit (WTRU) may transmit or receive a physical channel or reference signal according to at least one spatial domain filter. The term “beam” may be used herein to refer to a spatial domain filter.

[0072] The WTRU may transmit a physical channel or signal using the same spatial domain filter as the spatial domain filter used for receiving an RS (such as CSI-RS) or a SS block. The WTRU transmission may be referred herein to as “target”, and the received RS or SS block may be referred to as “reference” or “source”. In such case, the WTRU may be said to transmit the target physical channel or signal according to a spatial relation with a reference to such RS or SS block.

[0073] The WTRU may transmit a first physical channel or signal according to the same spatial domain filter as the spatial domain filter used for transmitting a second physical channel or signal. The first and second transmissions may be referred to as “target” and “reference” (or “source”), respectively. In such case, the WTRU may be said to transmit the first (e.g., target) physical channel or signal according to a spatial relation with a reference to the second (e.g., reference) physical channel or signal.

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

[0075] The WTRU may receive a first (e.g., target) downlink channel or signal according to the same spatial domain filter or spatial reception parameter as a second (e.g., reference) downlink channel or signal. For example, such association may exist between a physical channel, such as PDCCH or PDSCH, and its respective DM-RS. Such association may exist when the WTRU is configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports (e.g., when the first and second signals are reference signals). Such association may be configured as a TCI (transmission configuration indicator) state. A WTRU may be indicated an association between a CSI-RS or SS block and a DM-RS by an index to a set of TCI states configured by RRC and/or signaled by MAC CE. Such indication may also be referred to as a “beam indication” herein.

[0076] As used herein, the terms “transmission and reception point’7”TRP” may be used interchangeably with one or more of “transmission point7”TP”, “reception point”/”RP”, “radio remote head”/”RRH”, “distributed antenna”/“DA”, “base station”/“BS”, “sector” (e.g., of a BS), and/or “cell” (e.g., a geographical cell area served by a BS), consistent with the embodiments described herein. Further, the term “multi-TRP” may be used interchangeably herein with one or more of “MTRP,” “M-TRP,” and/or “multiple TRPs,” consistent with the embodiments described herein.

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

[0078] As used herein, the term “XDD” may be used to refer to a subband-wise duplex (e.g., either UL or DL being used per subband) and may be characterized by one or more of the following: cross division duplex (e.g., subband-wise FDD within a TDD band), Subband non-overlapping full duplex (SBFD), Subband-based full duplex (e.g., full duplex as both UL and DL are used/mixed on a symbol/slot, but either UL or DL being used per subband on the symbol/slot), Frequency-domain multiplexing (FDM) of DL/UL transmissions within a TDD spectrum, a full duplex other than a same-frequency (e.g., spectrum sharing, subband-wise-overlapped) full duplex, and/or an advanced duplex method (e.g., other than (pure) TDD or FDD).

[0079] As used herein, the term “dynamic(/flexi ble) TDD” may refer to a TDD system/cell which may dynamically (e.g., and/or flexibly) change/adjust/switch a communication direction (e.g., a downlink, an uplink, or a sidelink, etc.) on a time instance (e.g., slot, symbol, subframe, and/or the like). In a system employing dynamic/flexible TDD, a component carrier (CC) or a bandwidth part (BWP) may have a (e.g., single) type among ‘D’, ‘U’, and ‘F’ on a symbol/slot, based on an indication by a group-common (GC)-DCI (e.g., format 2_0) comprising a slot format indicator (SFI), and/or based on tdd-UL-DL-config- common/dedicated configurations. On a given time instance/slot/symbol, a first gNB (e.g, cell, TRP) employing dynamic/flexible TDD may transmit a downlink signal to a first WTRU being communicated/associated with the first gNB based on a first SFI and/or tdd-UL-DL-config configured/indicated by the first gNB, and a second gNB (e.g, cell, TRP) employing dynamic/flexible TDD may receive an uplink signal transmitted from a second WTRU being communicated/associated with the second gNB based on a second SFI and/or tdd-UL-DL-config configured/indicated by the second gNB. In an example, the first WTRU may determine that the reception of the downlink signal is being interfered by the uplink signal, where the interference caused by the uplink signal may be WTRU-to-WTRU cross-layer interference (CLI). [0080] A WTRU may report a subset of channel state information (CSI) components, where CSI components may correspond to one or more of a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of a panel used for reception at the WTRU (e. g. , a panel identity or group identity), measurements such as L1-RSRP, L1-SINR taken from SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-lndex-RSRP, ssb-lndex-SINR), and/or other channel state information such as rank indicator (Rl), channel quality indicator (CQI), precoding matrix indicator (PMI), Layer Index (LI), and/or the like.

[0081] Channel and/or interference measurements may be performed. A WTRU may receive a synchronization signal/physical broadcast channel (SS/PBCH) block. The SS/PBCH block (SSB) may include a primary synchronization signal (PSS), secondary synchronization signal (SSS), and/or physical broadcast channel (PBCH). The WTRU may monitor, receive, or attempt to decode an SSB during initial access, initial synchronization, radio link monitoring (RLM), cell search, cell switching, etc.

[0082] A WTRU may measure and report the channel state information (CSI), wherein the CSI for a (e.g., each) connection mode may include or be configured with one or more of following: a CSI Report Configuration, a CSI-RS Resource Set, and/or one or more NZP CSI-RS resources. The CSI Report Configuration may include one or more of a CSI report quantity (e.g., Channel Quality Indicator (CQI), Rank Indicator (Rl), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), etc.), a CSI report type (e.g., aperiodic, semi persistent, periodic), a CSI report codebook configuration (e.g., Type I, Type II, Type II port selection, etc.), and/or a CSI report frequency. The CSI-RS Resource Set may include one or more of the following CSI Resource settings: NZP-CSI-RS Resource for channel measurement, NZP-CSI-RS Resource for interference measurement, and/or CSI-IM Resource for interference measurement. The NZP CSI-RS resources may include one or more of the following: an NZP CSI-RS Resource ID, a periodicity and/or offset, QCL information and/or TCI-state, and/or resource mapping (e.g., number of ports, density, CDM type, etc.).

[0083] A WTRU may indicate, determine, and/or be configured with one or more reference signals. The WTRU may monitor, receive, and/or measure one or more parameters based on the respective reference signals. The following parameters are non-limiting examples of the parameters that may be included in reference signal(s) measurements: SS-RSRP, CSI-RSRP, SS-SINR, CSI-SINR, RSSI, CLI-RSSI, SRS- RSRP, SS-RSRQ, and/or CSI-RSRQ. One or more of these parameters may be included. Other parameters may be included.

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

[0085] CSI-RSRP may be included in reference signal(s) measurements. CSI-RSRP may be measured based on the linear average over the power contribution of the REs that carry the respective CSI-RS. The CSI-RSRP measurement may be configured within measurement resources for the configured CSI-RS occasions.

[0086] SS-SINR may be included in reference signal(s) measurements. SS signal-to-noise and interference ratio (SS-SINR) may be measured based on the synchronization signals (e.g., DMRS in PBCH or SSS). It may be defined as the linear average over the power contribution of the REs that carry the respective synchronization signal divided by the linear average of the noise and interference power contribution. If SS-SINR is used for L1 -SI NR, the noise and interference power measurement may be accomplished based on resources configured by higher layers.

[0087] CSI-SINR may be included in reference signal(s) measurements. CSI-SINR may be measured based on the linear average over the power contribution of the REs that carry the respective CSI-RS divided by the linear average of the noise and interference power contribution. If CSI-SINR is used for LISI NR, the noise and interference power measurement may be accomplished based on resources configured by higher layers. Otherwise, the noise and interference power may be measured based on the resources that carry the respective CSI-RS.

[0088] RSSI may be included in reference signal(s) measurements. Received signal strength indicator (RSSI) may be measured based on the average of the total power contribution in configured OFDM symbols and bandwidth. The power contribution may be received from different resources (e.g, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0089] CLI-RSSI may be included in reference signal(s) measurements. Cross-Layer interference received signal strength indicator (CLI-RSSI) may be measured based on the average of the total power contribution in configured OFDM symbols of the configured time and frequency resources. The power contribution may be received from different resources (e.g, cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.). [0090] SRS-RSRP may be included in reference signal(s) measurements. Sounding reference signals RSRP (SRS-RSRP) may be measured based on the linear average over the power contribution of the resource elements (RE) that carry the respective SRS.

[0091] SS-RSRQ may be included in reference signal(s) measurements. Secondary synchronization signal reference signal received quality (SS-RSRQ) may be measured based on measurements on the reference signal received power (SS-RSRP) and received signal strength (RSSI). In an example, the SS- RSRQ may be calculated as the ratio of NxSS-RSRP I NR carrier RSSI, where N may be determined based on the number of resource blocks that are in the corresponding NR carrier RSSI measurement bandwidth. As such, the measurements to be used in the numerator and denominator may be over the same set of resource blocks.

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

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

[0094] An indication by DCI may include one or more of the following: an explicit indication by a DCI field or by RNTI used to mask or scramble the CRC of the DCI, and/or an implicit indication by a property such as DCI format, DCI size, Coreset or search space, Aggregation Level, first resource element of the received DCI (e.g., index of first Control Channel Element), where the mapping between the property and the value may be signaled by RRC or MAC.

[0095] Receiving or monitoring for a DCI with or using an RNTI may mean that the CRC of the DCI is masked or scrambled with the RNTI. [0096] As used herein, the term “signal” may be used interchangeably with one or more of the following: SRS, CSI-RS, demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS), and/or synchronization signal block (SSB), consistent with the embodiments disclosed herein.

[0097] As used herein, the term “channel” may be used interchangeably with one or more of the following: Physical downlink control channel (PDCCH), Physical downlink shared channel (PDSCH), Physical uplink control channel (PUCCH), Physical uplink shared channel (PUSCH), Physical random access channel (PRACH), etc., consistent with the embodiments disclosed herein.

[0098] As used herein, the term “downlink reception” may be used interchangeably with “Rx occasion,” “PDCCH,” “PDSCH,” and/or “SSB reception,” consistent with the embodiments disclosed herein.

[0099] As used herein, the term “uplink transmission” may be used interchangeably with “Tx occasion,” “PUCCH,” “PUSCH,” “PRACH,” and/or “SRS transmission,” etc., consistent with the embodiments disclosed herein.

[00100] As used herein, the term “reference signal” may be used interchangeably with “RS,” “RS resource,” “RS resource set,” “RS port” and/or “RS port group,” etc., consistent with the embodiments disclosed herein.

[00101] As used herein, the terms “time instance,” “slot,” “symbol,” and/or “subframe” may be used interchangeably, consistent with the embodiments disclosed herein.

[00102] As used herein, “UL-only Tx/Rx occasions” and “DL-only Tx/Rx occasions” may interchangeably be used with “legacy TDD UL” and “legacy TDD DL,” respectively, consistent with the embodiments disclosed herein. In an example, the legacy TDD UL/DL Tx/Rx occasions may be cases where SBFD is not configured and/or where SBFD is disabled.

[00103] As used herein, the terms “received signal power,” “received signal energy,” “received signal strength,” “SSB EPRE,” “CSI EPRE,” “RSRP,” “RSSI,” “SINR,” “RSRQ,” “SS-RSRP,” “SS-RSSI,” “SS- SINR,” “SS-RSRQ,” “CSI-RSRP,” “CSI-RSSI,” “CSI-SINR,” and/or “CSI-RSRQ” may be used interchangeably, consistent with the embodiments disclosed herein.

[00104] Inter-WTRU (e.g., WTRU-to-WTRU) inter-subband CLI measurement and reporting at a first WTRU (e.g., SBFD-capable potential aggressor WTRU) based on signaling (e.g., SRS) reception from a second WTRU (e.g., SBFD-capable potential victim WTRU) in a first mode of operation (e.g., SBFD operation) is considered herein. However, the embodiments described herein may be used for any kind of interference measurement and reporting, based on any reference signals, in any types of BWP or subbands, and any modes of operation. That is, the embodiments for inter-subband CLI in SBFD configuration may be used for intra-subband CLI in TDD frameworks (e.g., flexible and/or dynamic TDD). The embodiments described herein for mitigating and handling the CLI in SBFD framework may be used in any system with imposed interference.

[00105] As used herein, the terms “CLI,” “inter-WTRU-CU,” “WTRU-to-WTRU CLI,” “inter-subband CLI,” “intra-subband CLI,” and/or “interference” may be used interchangeably, consistent with the embodiments disclosed herein.

[00106] As used herein, the term “non-SBFD” may be used interchangeably with “operation without SBFD,” “TDD,” and/or “legacy TDD,” consistent with the embodiments disclosed herein.

[00107] As used herein, the terms “WTRU is configured,” “WTRU is indicated,” “WTRU receives configuration,” etc., may imply that the configuration is indicated, for example, “via RRC, MAC-CE, DCI, MIB, and/or SIB, etc.,” unless indicated otherwise. Therefore, “WTRU is configured” may imply “WTRU is configured via RRC, MAC-CE, DCI, MIB, and/or SIB, etc.”

[00108] As used herein, the terms “victim WTRU” and “aggressor WTRU” may refer to any kind of WTRU, consistent with the embodiments disclosed herein.

[00109] As used herein, the terms “beam resource,” “beam direction,” “TCI-state,” and/or “spatial filter” may be used interchangeably, consistent with the embodiments disclosed herein, where the terms “beam resource,” “beam direction,” and “spatial filter” may consist of a TCI state, CSI-RS, SSB, etc. for downlink, an SRS resource, TCI state, etc. for uplink.

[00110] Subband non-overlapping full duplex (SBFD) may be used. A WTRU may be configured with one or more types of slots within a bandwidth, wherein a first type of slot may be used or determined for a first direction (e.g., downlink); a second type of slot may be used or determined for a second direction (e.g., uplink); a third type of slot may have a first group of frequency resources within the bandwidth for a first direction and a second group of frequency resources within the bandwidth for a second direction.

[00111] The term “bandwidth” may be interchangeably used with “bandwidth part (BWP),” “carrier,” “subband,” and/or “system bandwidth.” The first type of slot (e.g., the slot for a first direction) may be referred to as a downlink slot. The second type of slot (e.g, slot for a second direction) may be referred to as an uplink slot. The third type of slot may be referred to as a Sub-Band (non-overlapping) Full Duplex (SBFD) slot. The group of frequency resource for a first direction may be referred to as downlink subband, downlink frequency resource, or downlink RBs. The group of frequency resource for a second direction may be referred to as uplink subband, uplink frequency resource, or uplink RBs. [00112] A (e.g., SBFD-enabled) WTRU may receive or be configured with one or more SBFD UL or DL subbands in one or more DL/UL/flexible TDD time instances (e.g., symbols, slots, frames, etc.). The WTRU may be configured with one or more resource allocations for SBFD subbands.

[00113] For example, the SBFD configuration may include a flag signal (e.g., enabled/disabled), where a first value (e.g., zero (0)) may indicate a first mode of operation (e.g., SBFD configuration), and a second value (e.g., one (1)) may indicate a second mode of operation (e.g., non-SBFD operation). The modes of operation (e.g., SBFD vs. non-SBFD) may be indicated via MIB, SIB, semi-statically (e.g., via RRC), dynamic (e.g., via MAC-CE, DCI), etc. The WTRU may receive the time resources (e.g., one or more symbols, slots, etc.), for which the first mode of operation (e.g., SBFD) is defined in, for example, one or more BWPs, subbands, component carriers (CC), cells, etc. The WTRU may receive the frequency resources (e.g., subbands/BWPs including one or more PRBs) within (e.g., active and/or linked) BWP, for which the first mode of operation (e.g., SBFD) is configured. The time instances (e.g., slots, symbols) may be indicated based on periodic, semi-persistent, or aperiodic configurations. In an example, the time instances may be indicated via a bitmap configuration.

[00114] A WTRU may be configured with a DL TDD configuration for a component carrier (CC) or a BWP for one or more Rx occasions (e.g., via tdd-UL-DL-config-common/dedicated configurations, slot format indicator (SFI), etc.). As such, if the first mode of operation (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 transmission in UL channels and/or Tx occasions.

[00115] The WTRU may be configured with an UL TDD configuration for a component carrier (CC) or a BWP for one or more Tx occasions (e.g., via tdd-UL-DL-config-common/dedicated configurations, slot format indicator (SFI), etc.). As such, if the first mode of operation (e.g., SBFD) is configured, one or more of the configured frequency resources (e.g., subbands, PRBs, and/or BWPs) may be configured as the DL channels and/or Rx occasions.

[00116] The WTRU may be configured with a DL, UL, or Flexible TDD configuration for a component carrier (CC) or a BWP for one or more Rx/Tx occasions (e.g., via tdd-UL-DL-config-common/dedicated configurations, slot format indicator (SFI), etc.). As such, if the first mode of operation (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 mode of operation (e.g., either UL transmission or DL reception based on the configurations). [00117] The duplexing mode for the first mode of operation (e.g., SBFD configuration (UL/DL)) may be indicated via a flag indication, where, for example, a first value (e.g., zero (0)) may indicate a first mode (e.g., UL duplexing mode), and a second the value (e.g., one (1)) may indicate a second mode (e.g., DL duplexing model).

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

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

[00120] CLI measurement may be performed. A WTRU may be configured, determined, or indicated to perform a measurement of cross-link interference (CLI) Received Signal Strength Indicator (RSSI) in a given time period, wherein the given time period may be one or more slots, OFDM symbols, resource blocks (RBs), and/or resource elements (REs). The CLI-RSSI that may be measured in a given time and/or 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 indicated to perform a measurement of Reference Signal Received Power (RSRP) based on one or more reference signals (e.g., SRS-RSRP) in the context of CLI measurement in a given time period, wherein the given time period may be one or more slots, OFDM symbols, resource blocks (RBs), and/or resource elements (REs). The SRS-RSRP that may be measured in a given time/frequency resource may be referred to as L1 -SRS-RSRP, short-term SRS- RSRP, aperiodic SRS-RSRP, SRS-RSRP-CLI, etc.

[00121] Hereafter, CLI-RSSI, L1-CLI-RSSI, and RSSI may be interchangeably used, consistent with the embodiments disclosed herein. Hereafter, SRS-RSRP, SRS-RSRP-CLI, L1-SRS-RSRP, and RSRP may be interchangeably used, consistent with the embodiments disclosed herein.

[00122] L1/L2 CLI measurement may be performed. One or more RSSI (e.g., or RSRP) types may be used and a WTRU may be configured to perform one or more RSSI (or RSRP) types, wherein a first RSSI (or RSRP) type may be based on a measurement over a long time period (e.g., more than one slot) and the measurement is reported via a higher layer signaling (e.g., RRC, MAC). A second RSSI (or RSRP) type may be based on a measurement over a short time period (e.g., one slot, within a slot, one or more OFDM symbols within a slot) and the measurement is reported via a L1 signaling (e.g., PUCCH, PUSCH, RACH, SRS). RSSI may be interchangeably used with RSRP, RSRQ, and SI NR. CLI-RSSI may be interchangeably used with SRS-RSRP and SINR. [00123] Time and/or frequency resources may be used herein. The WTRU may be configured with a set of time/frequency resource to measure L1-CLI-RSSI, wherein the time/frequency resource for L1-CLI-RSSI measurement may be referred to as CLI-RSSI Measurement Resource (CRMR). CRMR may be a resource configured, determined, or defined (e.g., via RRC, MAC-CE, DCI) (e.g., via CLI-ResourceConfig, CLI- ResourceConfig-r-16, etc.) with one or more of following properties: a set of muted REs in downlink resource (e.g., PDSCH), where the muted REs may be rate-matched around or punctured for downlink reception and/or uplink transmission; a set of REs not scheduled or used for the WTRU measuring CRMR; one or more reference signals (e.g., DMRS, SRS, sidelink CSI-RS, etc.); a second set of DMRS REs within a second CDM group (e.g., within a scheduled downlink resource/RBs, e.g., of PDSCH), where a WTRU may receive a DCI, scheduling the PDSCH, indicating a first set of DMRS REs corresponding to a first CDM group to be used for receiving the PDSCH; and/or located within a scheduled resource (e.g., scheduled PDSCH RBs). For example, the time/frequency resources for CPMR may be (e.g., implicitly) determined based on CDM groups. A WTRU that is configured to receive a PDSCH based on a first CDM group may determine to use the second CDM group as the resources for CPMR.

[00124] CRMR may be a resource configured, determined, or defined with a set of muted REs in downlink resource (e.g., PDSCH), wherein the muted REs may be rate-matched around or punctured for downlink reception and/or uplink transmission. The set of muted REs may have a same pattern (e.g., same time/frequency location) in one or more (e.g., each) RBs. The set of muted REs may have a different pattern based on the RB location. For example, a first pattern may be used for the RBs located in an edge of the scheduled RBs and a second pattern may be used for the RBs located in a center of the scheduled RBs. The first pattern and the second pattern may have a different number of muted REs. The muted REs may be in a form of zero-power resources (e.g., CSI-RS and/or ZP-CSI-RS).

[00125] A set of REs may be located in an RB which may be configured or determined as guard band (or guard RB). A guard band (or guard RB) may be located in between uplink and downlink resources. A WTRU may skip receiving or transmitting a signal in guard band.

[00126] CRMR may be a resource configured, determined, or defined with a second set of DMRS REs within a second CDM group (e.g., within a scheduled downlink resource/RBs, e.g., of PDSCH), where a WTRU may receive a DCI, scheduling the PDSCH, indicating a first set of DMRS REs corresponding to a first CDM group to be used for receiving the PDSCH. In an example, the WTRU may receive the DCI, scheduling the PDSCH, indicating a first set of DMRS REs corresponding to a first CDM group (e.g., based on an indicated ‘(DMRS) antenna port’ field of the DCI). In response to receiving the DCI, the WTRU may determine that a second set of DMRS REs within a second CDM group (e.g., other than the first CDM group) may be used as the CRMR (e.g., within the scheduled PDSCH).

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

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

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

[00130] Delta-CLI measurement may be performed. The WTRU may be configured, determined, or indicated to perform a delta CLI-RSSI, which may be based on a first CLI-RSSI measurement in a first time/frequency location and a second CLI-RSSI measurement in a second time/frequency location. One or more of the following may apply.

[00131] The delta CLI-RSSI (e.g, delta-CLI-RSSI) may be a difference between a first CLI-RSSI (e.g, CLI- RSS11) and a second CLI-RSSI (e.g, CLI-RSSh), e.g, delta-CLI-RSSI = CLI-RSSI1 - CL-RSSI2 (e.g, or delta-CLI-RSSI = CLI-RSSI2 - CL-RSSI1, etc. The first CLI-RSSI may be measured from CRMR resources located in the edge of the scheduled RBs while the second CLI-RSSI may be measured from CRMR resources located in the middle of the scheduled RBs. A WTRU may be configured with a first CRMR resource for the first CLI-RSSI measurement and a second CRMR resource for the second CLI-RSSI measurement. The WTRU may determine to report CLI measurement related information when a measured delta-CLI-RSSI is larger than a threshold. For example, CLI reporting may be triggered based on delta-CLI-RSSI measurement is larger than a threshold, wherein the threshold may be predetermined or configured.

[00132] Bandwidth and/or subband configurations for CLI measurements may be used. The WTRU may be configured or determined to measure CLI-RSSI per subband level. For example, a subband may be configured, or predetermined and a WTRU may perform CLI-RSSI measurement in a (e.g., each) subband. Subband size may be determine d based on the number of scheduled RBs (e.g., for PDSCH). The WTRU may report CLI-RSSI measurement for one or more (e.g., all) subbands. The WTRU may report a subset of CLI-RSSI, wherein the subset may be determined based on one or more conditions (e.g., CLI-RSSI value above threshold, subband location (e.g., edge of scheduled RBs), and/or subband index).

[00133] The WTRU may determine a bandwidth of beam measurement/reporting (e.g., wideband or subband) based on a time unit type and/or a presence of a CLI-RSSI measurement. The time unit type may be SBFD or non-SBFD. For example, a WTRU may report wideband CRI (e.g., wideband beam index) in non-SBFD time units (e.g., symbol, slot, and so forth) and the WTRU may report subband CRI (e.g., subband beam index) in SBFD time units. The bandwidth of beam measurement/reporting may be determined based on whether CLI-RSSI is measured in the same slot or not.

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

[00135] One or more SRS types may be used. The WTRU may be configured or indicated to transmit one or more SRSs, where an SRS resource of the one or more SRSs may be configured for a particular purpose of at least one of: beam management, channel acquisition (e.g., based on channel reciprocity), link adaptation, and/or antenna switching, etc. The mentioned particular purpose may be interpreted to be for a communication link between the WTRU and a gNB (e.g., its serving gNB, cell, TRP, etc.), which may be denoted by a first SRS type. The first SRS type may be a non-limiting example of a type of SRS that may be used for or to support a communication link between the WTRU and its serving cell, TRP, and/or gNB. [00136] The WTRU may be configured or indicated to transmit second one or more SRS resources at least for CLI measurement purpose at a receiver side, which may be denoted by a second SRS type (e.g, CLI- SRS). The second SRS type may be a non-limiting example of a type of SRS that may be used for or to support at least the CLI measurements at a receiver side (e.g., other WTRU(s), gNB(s), or another communication device and/or node in the network). Any other type of transmission may be substituted for the transmission based on the second SRS type and still be consistent with the embodiments disclosed herein. The CLI measurements at the receiver side (e.g., a second WTRU) may comprise at least one of: an energy-level or power-level measurement (e.g., CLI-RSSI) on a configured or indicated DL resource (e.g., a form of zero-power resource, a configured CLI-measurement resource, and/or the like), a sequence-based and/or correlation-based RS power measurement (e.g., SRS-RSRP) on a configured or indicated RS sequence and/or resource (e.g., SRS resource which may be transmitted from the WTRU causing the CLI to the second WTRU), an SINR or CQI type of channel quality metric derivation to be reported, etc.

[00137] As used herein, the terms “CLI-SRS” and “SRS” may be used interchangeably consistent with the embodiments disclosed herein.

[00138] WTRU-oriented UL beam selection (e.g., for interference avoidance) may be performed. For example a WTRU may perform one or more of the following actions.

[00139] A WTRU may receive a configuration for a dynamic (or configured) UL grant (e.g., via DCI) indicating one or more time and/or frequency resources. The WTRU may receive (e.g., an indication of) a first beam direction for UL transmission (e.g., via a primary beam, beam with QCL-Type-D, beam associated with a first pattern of time and frequency resources). The WTRU may receive (e.g., an indication of) a set of (e.g., second) beam directions including at least a second beam direction for UL transmission (e.g, via secondary beams, beams with evolved QCL-Type (e.g, QCL-Type-E), or via second time and frequency patterns associated with second TCI-states). The WTRU may receive (e.g, an indication of) configurations including one or more threshold values for CLI, Maximum Permissible Exposure (MPE), range of AOA, etc. For example, the WTRU may receive an indication of a CLI threshold. The WTRU may receive the indication(s) via DCI. The WTRU may determine whether to use the first beam direction or a second beam direction for the UL transmission (e.g, where the second beam direction is in the set of second beam directions) based on one or more of the following conditions: an SBFD/CLI condition, an AoA/AoD condition, an MPE condition, and/or one or more events and/or indications from the gNB. For example, the WTRU may determine to use the second beam direction for the UL transmission based on one or a combination of the conditions.

[00140] The WTRU may determine whether to use the first beam direction or a second beam direction for the UL transmission (e.g., where the second beam direction is in the set of second beam directions) based on an SBFD/CLI condition. The condition associated with SBFD or CLI may be satisfied when the WTRU (e.g., potential aggressor WTRU) determines that the measured WTRU-to-WTRU CLI based on the first beam direction is higher than a CLI threshold (or in combination with another threshold, e.g., MPE, by a function/rule) and/or that the measured WTRU-to-WTRU CLI based on the second beam direction is less (e.g., not greater) than the CLI threshold. The WTRU may measure the CLI using reference signal(s) (RS) as described herein. The WTRU (e.g., SBFD-capable and/or potential aggressor WTRU) may be configured with SBFD operation, where the WTRU measures WTRU-to-WTRU CLI (e.g., SRS-RSRP) based on nearby potential victim WTRUs. The WTRU may determine the best and worst UL (e.g., SRS) beam directions by which the WTRU may cause the least and the most CLI on the nearby victim WTRUs, respectively. When the condition is satisfied, the WTRU may determine to switch to the second beam direction for UL transmission, and/or may select a second UL beam direction, where the CLI is lower than the threshold, and has the least value among beams from the second set of beam directions. For example, the WTRU may select the second beam direction based on the second beam direction having a lowest CLI measurement value among the set of second beam directions. The WTRU may transmit the uplink based on the selected second UL beam direction or the first beam direction (e.g., if the measured WTRU-to- WTRU CLI on the first beam direction is less (e.g., not greater) than the CLI threshold.

[00141] For example, a WTRU may receive (e.g., via DCI), from a network (e.g., a gNB), an indication of a cross-link interference (CLI) threshold, an indication of a first beam direction for an uplink (UL) transmission, an indication of one or more subband non-overlapping full-duplex (SBFD) resources for the UL transmission, and an indication of a set of one or more candidate beam directions. The WTRU may measure respective CLIs associated with the first beam direction and one or more (e.g., each) beam directions of the set of one or more candidate beam directions in an SBFD slot. The WTRU may determine whether to use the first beam direction or a second beam direction from the set of one or more candidate beam directions based on the respective measured CLIs and the CLI threshold. For example, the WTRU may determine that a measured CLI associated with the first beam direction is not greater than the CLI threshold, and determine to use the first beam direction for the UL transmission based on the determination that the measured CLI associated with the first beam direction is not greater than the CLI threshold. Alternatively, the WTRU may determine that a measured CLI associated with the first beam direction is greater than the CLI threshold and that a measured CLI associated with the first beam direction is greater than the CLI threshold, and may determine to use the second beam direction for the UL transmission based on the determination that the measured CLI associated with the first beam direction is greater than the CLI threshold and the determination that the measured CLI associated with the second beam direction is less than the CLI threshold. The second beam direction may be a beam direction among the set of one or more candidate beam directions that has a lowest CLI measurement value. The WTRU may transmit the UL transmission using the determined first beam direction or second beam direction and the one or more SBFD resources. The SBFD resources may be associated with the beam directions.

[00142] As disclosed herein, the WTRU may further determine whether to use the first beam direction or the second beam direction based on one or more of an angle of arrival (AoA) of one or more downlink (DL) beams, an angle of departure (AoD) of one or more UL beams, a measured maximum permissible exposure (MPE), a detected event, or a received indication from the network. The detected event may be, for example, a request for retransmission or a received NACK. The first beam direction may be associated with a first beam that is associated with a first TCI state and a first quasi co-location (QCL) type, and the second beam direction may be associated with a second beam that is associated with a second TCI state and a second QCL type. The WTRU may measure the respective CLIs associated with the beam directions by measuring a CLI associated with a first reference signal on the first beam direction and measuring respective CLIs associated with respective reference signals on one or more (e.g., each) beam direction of the set of one or more beam directions.

[00143] The WTRU may determine whether to use the first beam direction or a second beam direction for the UL transmission (e.g., where the second beam direction is in the set of second beam directions) based on an AoA/AoD condition. The condition associated with AOA or AOD may be satisfied when the WTRU (e.g., SBFD-capable and/or potential aggressor WTRU) receives information on the TCI-states used for the DL (e.g., by other WTRUs) at the same symbol that the WTRU (e.g., the aggressor WTRU) is scheduled for UL transmission, and the WTRU determines that the AOA of (e.g., of one or more of) the configured DL beams are within a configured range with the AOD for UL transmission based on the first beam direction.

[00144] In an example, the WTRU may measure a first value for the AOA of a DL beam (e.g., DL reference signal, TCI-state, etc.). The WTRU may measure a second value for the AOD of an UL beam (e.g., UL reference signal, TCI-state, etc.). The WTRU may calculate the difference between the measured first and second values. If the difference is smaller than a corresponding (pre-)configured threshold, the WTRU may determine that the measured AOA of the corresponding DL beam is within the range of the measured AOD of the corresponding UL beam. Otherwise, if the difference is larger than a corresponding (pre-)configured threshold, the WTRU may determine that the measured AOA of the corresponding DL beam is not within the range (e.g., is out of range) of the measured AOD of the corresponding UL beam.

[00145] When the AoA/AoD condition is satisfied, the WTRU may determine to switch to the second beam direction for UL transmission, and/or may select a second UL beam direction, where the AOD is not within the configured range from the AOA of the configured DL beams (e.g., of the configured DL beams for which the condition is met). The WTRU may transmit the uplink based on the selected second UL beam direction. When the condition is not satisfied, the WTRU may transmit the uplink based on the first UL beam direction.

[00146] The WTRU may determine to use a second beam direction for the UL transmission (e.g., where the second beam direction is in the set of second beam directions) based on an MPE condition. The condition associated with MPE may be satisfied when the WTRU determines that the measured MPE based on the first beam direction is higher than the MPE threshold (or in combination with other threshold, e.g., CLI, by a function/rule). When the condition is satisfied, the WTRU may determine to switch to the second beam direction for UL transmission, and/or may select a second UL beam direction, where the MPE is lower than the threshold and it has the least value. The WTRU may transmit the uplink based on the selected second UL beam direction.

[00147] The WTRU may determine to use a second beam direction for the UL transmission (e.g., where the second beam direction is in the set of second beam directions) based on one or more events and/or indications from the gNB. When the WTRU detects an event on the first beam (e.g., one or more requests for retransmission or NACK) and/or receives an indication (e.g, group-common DCI) to trigger an event or indicate to use the secondary beam, where one or more parameters and thresholds are indicated, the WTRU may select a second UL beam direction, where the measured parameters are within the indicated or configured ranges and thresholds. The WTRU may transmit the uplink based on the selected second UL beam direction. The gNB may check and/or monitor one or more (e.g, all) configured first and second beam directions in the UL grant resources to receive the UL.

[00148] A WTRU may receive one or more configurations (e.g, dynamic grant, e.g, via DCI, MAC-CE) or be configured and/or scheduled (e.g, configured grant, e.g, via RRC) with one or more UL grants for one or more UL transmissions (e.g, PUSCH, PUCCH, SRS transmission), where the configurations may include one or more of the following: time and/or frequency resource allocations; a priority level; a TCI state, CRI or SRI; and/or a number of repetitions.

[00149] The configurations may include time and/or frequency allocations. For example, the WTRU may receive configurations on the time and/or frequency resources to be used for the transmission of the configured and/or scheduled UL transmission(s).

[00150] The configurations may include a priority level. For example, the WTRU may receive the priority level for the scheduled and/or configured UL transmission with regards to other UL transmissions. In another example, the WTRU may receive the priority level for the scheduled and/or configured UL transmission with regards to DL transmissions.

[00151] The configurations may include a TCI state, CRI or SRI. For example, the WTRU may receive one or more TCI states (e.g., beam direction) applicable to at least one of PUCCH or PUSCH transmission(s). For example, the configuration of a TCI state may include an identity of an associated RS resource set and/or CSI-RS reporting configuration. Upon reception of MAC or DCI signaling indicating a TCI state, the WTRU may change the state of the associated RS resource set to an Active state and change the state of other RS resource sets to an Inactive or Monitoring state.

[00152] The configurations may include a number of repetitions. For example, the WTRU may receive configurations on the number of repetitions for the scheduled and/or configured UL transmission.

[00153] The WTRU may receive one or more configurations (e.g., via DCI, MAC-CE, RRC) or be (pre- )configured (e.g., via SIB, RRC) including one or more threshold values corresponding to one or more parameters. In an example, the WTRU may receive configurations including one or more threshold values for CLI, Maximum Permissible Exposure (MPE), range of AOA, etc.

[00154] A WTRU may receive configuration information on a first beam direction and a set of second beam directions for a UL transmission (e.g., via DCI). The set of second beam directions may include at least a second beam direction for UL transmission. The configured and/or indicated second beam direction may be considered as second candidate beam direction. The second beam direction may be the beam direction among the set of second beam directions that has a lowest measured CLI value.

[00155] The first beam direction may be indicated via a primary beam direction, a beam with QCL-Type-D, a beam associated with a first pattern of time and/or frequency resources, etc. In another example, the second candidate beam direction may be indicated via a secondary beam direction, a beam with evolved QCL-Type (e.g., QCL-Type-E), or via second pattern of time and/or frequency resources.

[00156] FIG. 4 illustrates an example of WTRU-oriented UL beam selection (e.g., for interference avoidance). As shown in FIG. 4, there may be a first WTRU (e.g, WTRU #1) that is configured and/or scheduled for UL transmission. The first WTRU may be configured to transmit UL in the UL subband in an SBFD configuration. As shown in FIG. 4, there may be a second WTRU (e.g, WTRU #2) that is configured and/or scheduled for a DL reception in the DL subband of the same SBFD time instance (e.g, symbol, slot, subframe, etc.). FIG. 4 shows the first beam direction configured for UL transmission of the first WTRU (e.g, blue beam) and the second beam direction (e.g, green beam) configured as the candidate beam direction for the UL transmission of the first WTRU. FIG. 4 also shows the DL beam direction for the DL reception for the second WTRU. [00157] The WTRU that is configured and/or scheduled for UL transmission may determine whether to use the first beam direction or a second beam direction for the UL transmission, where the WTRU may select the second beam direction from the set of candidate second beam directions. In an example, the WTRU that is configured to use a first beam direction for the configured and/or scheduled UL transmission may determine to use a candidate second beam direction instead.

[00158] The gNB may check and/or monitor the configured first and second beam directions that were configured via the UL grant resources to receive the corresponding UL transmission from the WTRU. [00159] The WTRU may determine to use the second candidate beam direction based on one or more conditions, which include, but are not limited to: conditions based on interference; conditions based on AoA and/or AoD; conditions based on MPE; and/or conditions based on gNB indication(s).

[00160] The WTRU may determine whether to use the first beam direction or the second candidate beam direction based on one or more conditions based on interference. A first WTRU that is configured and/or scheduled for UL transmission may determine that the interference (e.g. , caused by the first WTRU) (e.g., CLI) based on the configured first beam direction is higher than a corresponding configured and/or received threshold (e.g., a CLI threshold). The threshold (e.g., an indication thereof) may be received from the network in DCI. In an example, the first WTRU may be configured and/or scheduled in an SBFD and/or dynamic TDD configuration. The first WTRU may determine that the measured WTRU-to-WTRU CLI is higher than the corresponding threshold. The first WTRU may measure the WTRU-to-WTRU CLI based on directional and/or beam-based CLI measurements based on one or more reference signals (e.g., SRS and/or CLI-SRS) received from one or more second WTRUs, where the second WTRUs may be located nearby the first WTRU.

[00161] The first WTRU may measure the CLI from one or more second WTRUs based on the configured first beam direction. As such, the first WTRU (e.g., SBFD-capable potential aggressor WTRU) may determine that the measured CLI in the direction of the first beam direction is higher than the corresponding CLI threshold. That is, if the first WTRU transmits UL based on the first beam direction, the first WTRU may cause strong CLI (e.g., CLI that is higher than corresponding threshold) on one or more nearby second WTRUs (e.g., SBFD-capable potential victim WTRUs).

[00162] Moreover, the first WTRU may measure the CLI from one or more second WTRUs based on one or more configured beam directions from the second set of beam directions. In an example, if the first WTRU determines that the measured CLI in the direction of the first beam direction is higher than the corresponding CLI threshold, the first WTRU may determine to measure the CLI in the direction of the second set of beam directions. The first WTRLI (e.g., SBFD-capable potential aggressor WTRU) may determine that the measured CLI in the direction of at least a second beam direction is lower than (e.g., not greater than) the corresponding CLI threshold and that the measured CLI for the second beam direction has the lowest value among the other beam directions in the set of candidate second beam directions. The first WTRU may select the second beam direction from the set of candidate second beam directions for the UL transmission. That is, if the first WTRU transmits UL based on the second beam direction, the first WTRU may cause the lowest CLI on the nearby second WTRUs (e.g., SBFD-capable potential victim WTRUs). In another example, the first WTRU may select the second beam direction if the measured CLI in the second beam direction is lower than a corresponding threshold.

[00163] Therefore, the first WTRU may determine to use and/or switch to the selected second beam direction for the configured and/or scheduled UL transmission. The first WTRU may transmit the configured and/or scheduled UL transmission based on the selected second beam direction.

[00164] Alternatively, the first WTRU that is configured and/or scheduled for UL transmission (e.g., in an SBFD configuration) may determine that the measured interference (e.g., WTRU-to-WTRU CLI) based on the configured first beam direction is lower than the corresponding configured and/or received threshold. As such, the first WTRU may determine to use the configured first beam direction for the configured and/or scheduled UL transmission.

[00165] The WTRU may determine to use the second candidate beam direction based on one or more conditions based on AoA and/or AoD. A first WTRU that is configured and/or scheduled for UL transmission may determine that the AoD applied and/or used for the configured UL transmission based on a configured first beam direction is within a configured range with the AoA of one or more configured DL receptions at one or more second WTRUs. In an example, the first WTRU may be configured and/or scheduled in an SBFD or dynamic TDD configuration. The first WTRU may determine that if the first WTRU transmits UL in the direction of the first beam, the UL transmission may cause CLI (e.g., WTRU-to-WTRU CLI) on the DL signal and/or channel configured or scheduled for the second WTRU.

[00166] A DL TCI-states indication may be received. The first WTRU may receive indication and/or information (e.g., via DCI, MAC-CE, RRC) on the beam direction and/or TCI-states used, scheduled, and/or configured for DL reception for one or more second WTRUs, where the second WTRUs may be located nearby the first WTRU. In another example, the first WTRU may receive an indication and/or information on DL beam directions that are scheduled and/or configured for DL reception in the same (e.g., SBFD) time instance that the first WTRU is configured to transmit the configured and/or scheduled UL transmission. For example, the first WTRLI may receive the information on DL beam directions based on a bitmap indication, where a (e.g., each) bit in the bitmap represents a TCI-state. The bits in the bitmap may have a first value (e.g., value one) indicating that the corresponding TCI-state is scheduled for DL for one or more second WTRUs (e.g., in the corresponding SBFD time instance); the bits in the bitmap may have a second value (e.g., value zero) indicating that the corresponding TCI-state is not scheduled for DL for one or more (e.g., any) of the second WTRUs (e.g., in the corresponding SBFD time instance). As such, the first WTRU may use the received and/or configured bitmap indication to determine the TCI-states that are scheduled and/or configured for DL reception for one or more second WTRUs.

[00167] AoA and/or AoD measurement may be performed. If the first WTRU receives the indication that at least a DL TCI-state for at least a DL reception is scheduled for at least a second WTRU in the same (e.g., SBFD) time instance that the first WTRU is scheduled for UL transmission, the first WTRU may calculate and/or measure the AoA for the scheduled DL TCI-state. The first WTRU may calculate and/or measure the AoD of the first beam direction configured for the transmission of the scheduled and/or configured UL transmission.

[00168] A first WTRU may determine that the measured AOA of the DL TCI-state configured for a second WTRU is within a (pre-)configured range of the measured AoD of the first UL beam direction. As such, the first WTRU may determine to select a second beam direction from the set of candidate second beam directions for the corresponding UL transmission. The first WTRU may select the second beam direction so that the measured AoA of the DL TCI-state configured for the second WTRU is not within a (pre-)configured range of the measured AoD of the second UL beam direction.

[00169] Therefore, the first WTRU may determine to use and/or switch to the selected second beam direction for the configured and/or scheduled UL transmission. The first WTRU may transmit the configured and/or scheduled UL transmission based on the selected second beam direction.

[00170] Alternatively, the first WTRU that is configured and/or scheduled for UL transmission (e.g., in an SBFD configuration) may determine that the measured AoA of the DL TCI-state configured for the second WTRU is not within a (pre-)configured range of the measured AOD of the first UL beam direction. As such, the first WTRU may determine to use the configured first beam direction for the configured and/or scheduled UL transmission.

[00171] The WTRU may determine to use the second candidate beam direction based on one or more conditions based on MPE. A WTRU that is configured and/or scheduled for UL transmission may determine that the measured Maximum Permissible Exposure (MPE) in the direction of the first UL beam direction is higher than a corresponding (pre-)configured threshold, where the WTRU may select a second beam direction from the set of candidate second beam directions for the corresponding UL transmission.

[00172] The WTRU may select the second beam direction so that the measured MPE is lower than the corresponding threshold. The WTRU may determine to use and/or switch to the selected second beam direction for the configured and/or scheduled UL transmission. The WTRU may transmit the configured and/or scheduled UL transmission based on the selected second beam direction.

[00173] Alternatively, the WTRU that is configured and/or scheduled for UL transmission may determine that the measured MPE in the direction of the first UL beam direction is lower than the corresponding (pre- )configured threshold. As such, the WTRU may determine to use the configured first beam direction for the configured and/or scheduled UL transmission.

[00174] The WTRU may determine to use the second candidate beam direction based on one or more conditions based on one or more gNB indications. A WTRU that is configured and/or scheduled for UL transmission may receive one or more indications, where the WTRU may select a second beam direction from the set of candidate second beam directions for the corresponding UL transmission. The WTRU may receive the indications via DCI, MAC-CE, RRC, etc. The WTRU may receive one or more threshold values (e.g., via DCI, MAC-CE, RRC).

[00175] For example, the WTRU may receive the indications from the gNB based on implicit and/or explicit indications.

[00176] For an implicit indication, the WTRU may determine to switch the UL beam direction to the second beam based on an event or an implicit indication. The WTRU may receive one or more limit values, thresholds, maximum values, etc. (e.g., via DCI, MAC-CE, RRC). The implicit indication may be a number of requests for retransmission. For example, the WTRU may determine that the number of requests from gNB for retransmission of a UL transmission based on a first beam direction has reached a (pre-)configured maximum value. As such, the WTRU may determine to switch to the second beam direction for the corresponding UL transmission.

[00177] For an explicit indication, the WTRU may determine to switch the UL beam direction to the second beam based on an explicit indication received from the gNB (e.g., via DCI, MAC-CE, RRC). As such, the WTRU may determine to switch to the second beam direction for the corresponding UL transmission. [00178] A signaling framework for multi-beam UL configuration may be disclosed herein. A WTRU may perform one or more of the following actions. [00179] The WTRU may receive a configuration for a configured or dynamic UL grant (e.g., via DCI) indicating one or more time and/or frequency resources from a network (e.g., a gNB).

[00180] The WTRU may determine to use a first beam direction or a second beam direction for an UL transmission associated with the configured and/or dynamic grant, based on CLI measurements, a TCI mapping, and/or a QCL type.

[00181] The WTRU may transmit the UL transmission using the determined first or second beam direction. One or more of the following options may apply: primary or secondary TCI-states; and/or evolved QCL type, which may be used alone or in combination.

[00182] For example, the WTRU may receive (e.g., via DCI) a configuration for a configured or dynamic uplink (UL) grant indicating one or more time and frequency resources from a network (e.g., a gNB). The WTRU may determine to use a first beam direction or a second beam direction for a UL transmission associated with the configured or dynamic grant based on one or more cross-link interference (CLI) measurements. For example, the WTRU may use the beam direction having the lower measured CLI. The WTRU may select the second beam direction based on one or more of a transmission configuration index (TCI) mapping and a quasi-colocation (QCL) type. The WTRU may transmit, to the network, the UL transmission using the determined beam direction.

[00183] For example, the WTRU may select the second beam direction based on a TCI mapping. In this example, the WTRU may receive an indication of the first beam direction as a primary beam direction based on a configured or activated TCI state, a set of beam directions comprising the second beam direction, and a mapping between TCI states and respective beam directions, and may select the second beam direction from the set of beam directions based on the mapping between TCI states and respective beam directions and the CLI measurements. Additionally and/or alternatively, the WTRU may select the second beam direction based on a QCL type. In this example, the WTRU may receive an indication of the first beam direction as a primary beam direction (e.g., where the first beam direction is associated with a first QCL type), a set of beam directions comprising the second beam direction, and a mapping between the set of beam directions and respective QCL types. The WTRU may select the second beam direction from the set of beam directions based on the second beam direction being associated with a second QCL type and the CLI measurements. The first QCL type may be QCL-Type D and the second QCL type may be QCL-Type E.

[00184] For primary or secondary TCI-states, the WTRU may receive a first UL beam direction as the primary (e.g., default) beam direction based on a configured or activated TCI state (e.g., based on last TCI indicated in unified TCI framework, e.g., which has been received most recently via a DL-DCI comprising a TCI field, where the indicated TCI is determined as a valid unified TCI based on a configured beam application time (BAT)).

[00185] The WTRU may receive a second set of secondary beam directions, including at least a second UL beam direction, for example based on configured or activated TCI states.

[00186] For example, as an implicit determination method, the WTRU may determine the second set of secondary beam directions as one or more activated TCI states (e.g., activated via a TCI -activation MAC- CE) mapped to one or more codepoints in the TCI field.

[00187] The WTRU may receive further information (e.g., via a MAC-CE or the same TCI-activation MAC- CE) on a linkage between an activated TCI-state(s) and other (e.g., activated) TCI-state(s) as secondary TCI-states, for example as shown in Table 1 below:

Table 1. Example of MAC-E configuration of TCI states for multibeam UL

[00188] The WTRU may select the second beam direction from the second set of beam directions based on CLI measurements (e.g., the WTRU may select the beam direction with the least measured CLI).

[00189] For evolved QCL type, the WTRU may receive a first UL beam direction based on a configured or activated TCI state with QCL-Type D (e.g., based on a last TCI indicated in unified TCI framework). [00190] The WTRU may receive a second set of UL beam directions including at least a second UL beam direction based on configured or activated TCI state with an evolved QCL-Type (e.g., QCL-Type E).

Evolved QCL-Type may indicate the selective WTRU behavior, where the WTRU selects and uses from the beams indicated by QCL-Type E, (e.g., only) if of an event is triggered (e.g., via WTRU or gNB), or an event is detected in the UL transmission in a first beam direction (e.g., with QCL-Type-D). Conditions to select the second beam may be as disclosed herein (e.g., indicated by QCL-Type E).

[00191] The WTRU may select the second beam direction from the second set of beam directions based on CLI measurements (e.g., the WTRU may select the beam direction with the least measured CLI).

[00192] In an example related to multiple configured grant (CG) PUSCH transmission, the WTRU may receive a configuration of multiple CG PUSCH transmission occasions (e.g., time and/or frequency resources) in a (e.g., each) period of the configured CG PUSCH.

[00193] The WTRU may select a CG PUSCH transmission occasion associated with or based on the selected TCI state or the selected beam with evolved QCL Type.

[00194] For example, a time/frequency pattern association of TCI-states may be used. The WTRU may receive configurations (e.g., via configured grant configurations) including a list of TCI states and one or more patterns of CG PUSCH transmission occasions. A (e.g., each) TCI state of the list of TCI states may have a one-to-one association to one or more patterns of CG PUSCH transmission occasions.

[00195] The WTRU may use the selected TCI state based on above-mentioned options and may determine the CG PUSCH transmission occasion based on the selected TCI state and the association between the TCI state and one or more patterns of CG PUSCH transmission occasions.

[00196] The WTRU may transmit the UL transmission using the selected TCI state/beam direction and the determined CG PUSCH transmission occasion.

[00197] The WTRU may report the determined TCI state and/or corresponding patterns via UCI to the gNB. Reporting may allow the gNB to release (e.g., or reuse for other purpose) patterns of the configured CG PUSCH transmission occasions which are not associated with the reported TCI-state (e.g., in the context of unused time occasions (UTO)).

[00198] The WTRU may transmit the UL based on the determined and reported TCI state (e.g., using the one or more patterns of configured time and frequency resources), for example on condition that the WTRU determines the pattern has an association with the TCI state.

[00199] A WTRU may receive configuration information indicating a plurality of candidate UL beams (e.g., represented by SRIs, TCI-states, UL-TCIs, joint UL/DL TCIs, DL RSs, and/or UL RSs, etc.). [00200] The WTRU may receive an UL grant (e.g., a configured grant (CG) via higher-layer signaling and/or dynamic grant (DG) via a DCI), indicating time and/or frequency resources for transmitting a UL signal or channel scheduled by the UL grant. The WTRU may determine a first beam direction of the plurality of candidate UL beams that is indicated by the UL grant for transmitting the UL signal or channel. [00201] The WTRU may determine, based on CLI measurements, whether or not the indicated first beam direction is appropriate for transmitting the UL signal or channel. In an example, the WTRU may determine that a first beam direction is appropriate if the measured CLI level for the first beam is lower (e.g., not greater than) than a threshold; the WTRU may determine that the first beam direction is appropriate if the measured MPE level for the first beam is lower (e.g., not greater) than a threshold, etc.

[00202] If the first beam direction is appropriate, the WTRU may transmit the UL signal or channel using the first beam direction. If the first beam direction is not appropriate (e.g., the CLI for the first beam is greater (e.g., not less) than the threshold), the WTRU may determine a second beam direction based on at least one of the mechanisms disclosed herein. In an example, the WTRU may determine that the first beam direction is not appropriate if the measured CLI level for the first beam is higher (e.g., not less) than a threshold; the WTRU may determine that the first beam direction is not appropriate if the measured MPE level for the first beam is higher (e.g., not less) than a threshold, etc.

[00203] For example, the WTRU may select and/or determine the second beam direction when the measured CLI based on the second beam direction is lower (e.g., not greater) than the corresponding threshold and/or the measured CLI based on the second beam direction is the lowest among candidate second beam directions. The WTRU may select and/or determine the second beam direction when the measured MPE based on the second beam direction is lower (e.g., not greater) than the corresponding threshold and/or the measured MPE based on the second beam direction is the lowest among the candidate second beam directions, etc.

[00204] The WTRU may transmit the configured, scheduled, and/or determined UL signal or channel using the determined and/or selected second beam direction. This may provide benefits in terms of avoiding (e.g., or mitigating) CLI to other (e.g., nearby) WTRUs’ reception performance where the second beam direction used from the WTRU may be favorable in terms of CLI (e.g., compared to the first beam direction) for the other WTRUs’ reception performance.

[00205] An example of a mechanism for selecting the second beam direction may be primary/secondary TCI states. The WTRU may receive an indication (e.g., via RRC, MAC-CE, and/or a separate DCI) that the first beam direction is associated with one or more secondary TCI-states, e.g., before receiving the UL grant. For example, as shown in Table 1 , the indication (e.g., a TCI-activation MAC-CE) may indicate one or more mappings, (e.g. each) between a TCI codepoint (e.g., of a DCI field of the dynamic UL grant) and a primary TCI-state(s) (e.g., the first beam direction) where the primary TCI-state may further be associated with one or more secondary TCI-state(s) shown in the table.

[00206] For example, the TCI codepoint ‘001’ may be mapped with TCI-state7 (as a primary TCI-state, e.g., the first beam direction) which has association with multiple secondary TCI-states as {TCI-state6, TCI- state8, TCI-state9), e.g., among which the WTRU may determine (e.g., or select) the second beam direction.

[00207] Similarly, the TCI codepoint ‘000’ may be mapped with both TCI-state17 and TCI-state32 (as primary TCI-states, e.g., TCI-state17 for TRP1 and TCI-state32 for TRP2 in a multi-TRP scenario) (e.g., each) having association with multiple secondary TCI-states. For example, the TCI-state 17 may have an association with multiple secondary TCI-states as {TCI-state 16, TCI-state18, TCI-state19}, and TCI-state32 may have association with multiple secondary TCI-states as {TCI-state30, TCI-state31 , TCI-state33).

[00208] The TCI codepoint ‘11 T may be mapped with TCI-state13 (as a primary TCI-state, e.g., the first beam direction) which may have an association with multiple secondary TCI-states as {TCI-state14, TCI- statel 5, TCI-state16), e.g., among which the WTRU may determine (or select) the second beam direction. [00209] In an example of configured UL grant (e.g., for CG-PUSCH transmission), the WTRU may receive similar association information, e.g., as a similar example case of TCI codepoint ‘00T, indicating TCI-state7 is a primary TCI-state (e.g., the first beam direction) for the CG-PUSCH transmission, where the primary TCI-state (TCI-state7) may have an association with multiple secondary TCI-states as {TCI-state6, TCI- state8, TCI-state9). Other examples (e.g., similar to different examples of different TCI codepoint) may apply also (e.g., for the CG-PUSCH case).

[00210] Implicit determination of the secondary TCI states may be performed. In an example related to for dynamic UL grant (e.g., for DG-PUSCH transmission), based on determining a primary TCI-state (e.g., TCI- state7) by a received TCI codepoint (e.g., ‘001’) of a DCI (e.g., indicating the UL grant), the WTRU may determine that the secondary TCI-states are other primary TCI-states in different TCI codepoints other than the received TCI codepoint of the (same) DCI, e.g., where the secondary TCI-states in this example Table 1 are at least one of {TCI-state17, TCI-state32, ..., and/or TCI-state13).

[00211] In another example, based on determining a primary TCI-state (e.g., TCI-state13) by a received TCI codepoint (e.g., ‘111’) of a DCI (e.g., indicating the UL grant), the WTRU may determine that the secondary TCI-states are other primary TCI-states in different TCI codepoints other than the received TCI codepoint of the (same) DCI, e.g., where the secondary TCI-states in this example in Fig. 4-3 are at least one of {TCI-state17, TCI-state32, and/or TCI-state7}.

[00212] One or more examples may use a unified TCI framework. The WTRU may receive configuration information enabling unified TCI (UTCI) framework, where the unified TCI framework may include at least one of: joint DL/UL UTCI mode and/or separate DL/UL UTCI mode. The unified TCI framework may enable low-complexity (e.g., with reduced signaling overhead) beam indication mechanism, where an indicated unified TCI (beam) may be applicable for not only one single channel or signal, but for multiple different channels and/or signals simultaneously (e.g., which may reduce the beam control and/or indication complexity). For example, a primary TCI-state (e.g., TCI-state7) associated with TCI codepoint ‘00T in Table 1 , once it is indicated, the primary TCI-state (e.g., TCI-state7) may be used for not only the scheduled DG-PUSCH, but also for PUCCH transmission (e.g., at least for the separate DL/UL UTCI mode), PDSCH reception, and/or PDCCH monitoring (e.g., for the joint DL/UL UTCI mode). If the indicated primary TCI-state (as UTCI) (e.g., TCI-state7) is different from a currently used one (e.g., TCI-state13), the WTRU may use a pre-configured beam application time (BAT) parameter for determining when to start to apply the indicated primary TCI-state (as UTCI).

[00213] The WTRU may be configured with a DCI field comprising one or more TCI codepoints (e.g., as shown in examples in Table 1) where at least one primary TCI-state in a TCI codepoint may be a UTCI and at least one behavior disclosed herein may be applicable similarly (or in the same way) in terms of the UL beam determination (e.g., on whether the indicated primary TCI-state is used as is or a second beam direction is used being selected from the associated secondary TCI-states) for PUSCH transmission. However, the WTRU may determine to use the indicated primary TCI-state as is for other UL transmission (e.g., PUCCH Tx, SRS Tx) based on determining the indicated primary TCI-state is a UTCI, e.g., after a valid time duration based on the BAT on when to start to apply the indicated primary TCI-state. In another example, the WTRU may start to apply the second beam direction (selected from the associated secondary TCI-states) not only for the PUSCH transmission but also for at least one other type of UL transmissions (e.g., PUCCH, SRS, PRACH, etc.).

[00214] An example of a mechanism for selecting the second beam direction may be evolved QCL type. The WTRU may receive a first UL beam direction based on a configured or activated TCI state with QCL- Type D (e.g., based on a primary TCI-state as shown in examples in Table 1 , or based on last TCI (valid based on the BAT) indicated in unified TCI framework as disclosed herein). The WTRU may receive a second set of UL beam directions including at least a second UL beam direction based on configured or activated TCI state with an evolved QCL-Type (e.g., QCL-Type E).

[00215] An evolved QCL-Type may indicate a selective WTRU behavior, where the WTRU selects and uses from the beams configured or indicated by QCL-Type E, (e.g, only) if an event is triggered (e.g, via WTRU or gNB), or an event is detected in the UL transmission in a first beam direction (e.g, with QCL- Type-D) (e.g, as disclosed herein on conditions to select the second beam, e.g, indicated by QCL-Type E). In an example, the configured plurality of candidate UL beams (e.g, an UL-TCI state pool, a configured plurality of unified UL-TCIs with the separate DL/UL UTCI mode, or at least a part of a configured plurality of unified TCIs with the joint DL/UL UTCI mode, etc.) may comprise (e.g, consist of, include) a 1^st set of UL beams associated with QCL-Type D (e.g, for ‘spatial parameter’) among which the first UL beam direction may be indicated, and a 2^nd set of UL beams associated with QCL-Type E (e.g, to be used as the secondary TCI-states). The 1^st set of UL beams and the 2^nd set of UL beams may have a partial overlap, or have disjoint UL beam RSs, which may be configured to the WTRU (e.g, as a part of operational mode of configuration).

[00216] If the first beam direction (e.g, indicated by a configured or dynamic UL grant) is appropriate, the WTRU may transmit an UL signal or channel scheduled by the grant using the first beam direction. If the first beam direction is not appropriate (e.g, CLI level is above the threshold), the WTRU may determine a second beam direction (e.g, with having the least CLI among candidate secondary beam directions, and/or among the 2^nd set of UL beams (associated with QCL-Type E)) and transmit the UL signal or channel using the second beam direction.

[00217] Multiple CG-PUSCH transmission may be performed. The WTRU may receive configuration of multiple CG-PUSCH transmission occasions (e.g, time and/or frequency resources) in each period of the configured CG-PUSCH. The WTRU may receive configuration (e.g, via configured grant configuration or via a separate configuration) including a list of TCI states and one or more patterns of CG-PUSCH transmission occasions, where a (e.g, each) TCI state of the list of TCI states may have a one-to-one association to one or more patterns of CG-PUSCH transmission occasions. The WTRU may select a CG- PUSCH transmission occasion associated with or based on a selected TCI state or a selected beam with evolved QCL Type (e.g, QCL-Type E), based on at least one of the mechanisms disclosed herein for determining the selected TCI state. The WTRU may use the selected TCI state and determine the CG- PUSCH transmission occasion based on the selected TCI state and the association between the TCI state and one or more patterns of CG-PUSCH transmission occasions. The WTRU may transmit the UL transmission using the selected TCI state/beam direction and the determined CG-PUSCH transmission occasion.

[00218] The WTRU may (be configured to) report (e.g., via UCI) the determi ned/selected TCI state and/or corresponding pattern of CG-PUSCH transmission occasion to the gNB. This may allow the gNB to release (e.g., or reuse for other purpose) patterns of the configured CG PUSCH transmission occasions which are not associated with the reported TCI-state (e.g., unused time occasions (UTO)). The WTRU may transmit a scheduled UL channel or signal based on the determined and reported TCI state, e.g., using the one or more patterns of configured time and freq, resources, if the WTRU determines the pattern has an association with the TCI state.

[00219] The processes and instrumentalities described herein may apply in any combination, may apply to other wireless technologies, and for other services.

[00220] A WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc. WTRU may refer to application-based identities, e.g., user names that may be used per application.

[00221] The processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, and/or any host computer.

Claims

CLAIMS:

1 . A wireless transmit/receive unit (WTRU) comprising: a processor configured to: receive, from a network, a configuration for a configured or dynamic uplink (UL) grant indicating one or more time and frequency resources; determine to use a first beam direction or a second beam direction for a UL transmission associated with the configured or dynamic grant based on one or more cross-link interference (CLI) measurements; select the second beam direction based on a quasi-colocation (QCL) type, wherein the processor being configured to select the second beam direction based on the quasi-colocation (QCL) type comprises the processor being configured to: receive, from the network, an indication of the first beam direction as a primary beam direction, wherein the first beam direction is associated with a first QCL type, wherein the first QCL type is QCL-Type D; receive, from the network, a set of beam directions comprising the second beam direction, and a mapping between the set of beam directions and respective QCL types; and select the second beam direction from the set of beam directions based on the second beam direction being associated with a second QCL type and the CLI measurements; and transmit, to the network, the UL transmission using the determined beam direction.

2. The WTRU of claim 1 , wherein the processor is configured to select the second beam direction further based on a transmission configuration index (TCI) mapping.

3. The WTRU of claim 2, wherein the processor being configured to select the second beam direction based on the TCI mapping comprises the processor being configured to: receive, from the network, an indication of the first beam direction as a primary beam direction based on a configured or activated TCI state; receive, from the network, a set of beam directions comprising the second beam direction, and a mapping between TCI states and respective beam directions; and select the second beam direction from the set of beam directions based on the mapping between TCI states and respective beam directions and the CLI measurements.

4. The WTRU of claim 1 , wherein the second QCL type is QCL-Type E.

5. The WTRU of claim 1 , wherein the UL grant is received via downlink control information (DCI).

6. The WTRU of claim 1 , wherein the processor is configured to determine to use the first beam direction or the second beam direction for the UL transmission associated with the configured or dynamic grant based on one or more CLI measurements comprises the processor being configured to: measure a CLI associated with the first beam direction and a CLI associated with the second beam direction; on a condition that the CLI associated with the first beam direction is lower than the CLI associated with the second beam direction, determine to use the first beam direction; and on a condition that the CLI associated with the second beam direction is lower than the CLI associated with the first beam direction, determine to use the second beam direction.

7. A method implemented in a wireless transmit/receive unit (WTRU), the method comprising: receiving, from a network, a configuration for a configured or dynamic uplink (UL) grant indicating one or more time and frequency resources; determining to use a first beam direction or a second beam direction for a UL transmission associated with the configured or dynamic grant based on one or more cross-link interference (CLI) measurements; selecting the second beam direction based on and a quasi-colocation (QCL) type, wherein selecting the second beam direction based on the quasi-colocation (QCL) type comprises: receiving, from the network, an indication of the first beam direction as a primary beam direction, wherein the first beam direction is associated with a first QCL type, wherein the first QCL type is QCL-Type D; receiving, from the network, a set of beam directions comprising the second beam direction, and a mapping between the set of beam directions and respective QCL types; and selecting the second beam direction from the set of beam directions based on the second beam direction being associated with a second QCL type and the CLI measurements; and transmitting, to the network, the UL transmission using the determined beam direction.

8. The method of claim 7, the second beam direction is further selected based on a transmission configuration index (TCI) mapping.

9. The method of claim 8, wherein selecting the second beam direction based on a TCI mapping comprises: receiving, from the network, an indication of the first beam direction as a primary beam direction based on a configured or activated TCI state; receiving, from the network, a set of beam directions comprising the second beam direction, and a mapping between TCI states and respective beam directions; and selecting the second beam direction from the set of beam directions based on the mapping between TCI states and respective beam directions and the CLI measurements.

10. The method of claim 7, wherein the second QCL type is QCL-Type E.

11 . The method of claim 7, wherein the UL grant is received via downlink control information (DCI).

12. The method of claim 7, wherein determining to use the first beam direction or the second beam direction for the UL transmission associated with the configured or dynamic grant based on one or more CLI measurements comprises: measuring a CLI associated with the first beam direction and a CLI associated with the second beam direction; on a condition that the CLI associated with the first beam direction is lower than the CLI associated with the second beam direction, determining to use the first beam direction; and on a condition that the CLI associated with the second beam direction is lower than the CLI associated with the first beam direction, determining to use the second beam direction.