CN118104326A - Power control and link adaptation associated with cross-division duplexing (XDD) - Google Patents

Abstract

Systems, methods, and instrumentalities are described herein related to power control and link adaptation for cross-division duplexing (XDD). A wireless transmit/receive unit (WTRU) may receive an grant associated with transmission of an Uplink (UL) signal. The grant may indicate a first set of Resource Blocks (RBs). The WTRU may determine a Frequency Gap (FG) between the first set of RBs and the reference RB. The WTRU may adjust one or more transmission (Tx) parameters based on the determined FG. When the determined FG is less than a predefined threshold, the WTRU may reduce one or more of a transmit power or a Modulation Coding Scheme (MCS) level associated with transmission of UL signals scheduled by the grant. The WTRU may transmit the UL signal using the adjusted one or more Tx parameters.

Description

Power control and link adaptation associated with cross-division duplexing (XDD)

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional patent application 63/244,452, filed on 9, 15, 2021, and U.S. provisional patent application 63/395,901, filed on 8, 2022, which are hereby incorporated by reference in their entireties.

Background

Mobile communications using wireless communications continue to evolve. The fifth generation may be referred to as 5G. The former generation (legacy) mobile communication may be, for example, fourth generation (4G) Long Term Evolution (LTE).

Disclosure of Invention

Systems, methods, and instrumentalities are described herein related to power control and link adaptation for cross-division duplexing (XDD). Systems, methods, and instrumentalities are described herein in relation to subband non-overlapping full duplex (SBFD) operation based on transmit parameter adjustment. A wireless transmit/receive unit (WTRU) may apply dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD), for example. For example, the WTRU may apply dynamic UL PC and/or dynamic MCS adjustment for XDD, or Tx behavior change (e.g., tx discard, skip, stop, cancel and/or defer or Tx with modified parameters) if one or more of the following conditions are met: if the frequency gap between the RBs of the first configuration and/or indication (e.g., for UL Tx) and the RBs of the second configuration and/or indication (e.g., for DL Rx) on the (e.g., same) symbol/slot is below a first threshold; if the spatial domain separation between the first configuration and/or indicated beam/RS/TCI for UL Tx and the second configuration and/or indicated beam/RS/TCI (e.g., for DL Rx) on the (e.g., same) symbol/slot is below a second threshold; if a priority indication of the RB for the first configuration and/or indication of UL Tx is given; etc. Priority rules (e.g., in the conditions and/or criteria described herein) may be predefined, configured, or indicated, for example, on which conditions may be applied as higher priority (e.g., as compared to others).

In an example, the WTRU may determine a first transmission power for UL transmission if a Frequency Gap (FG) value for UL transmission is equal to or less than a threshold. The WTRU may determine a second transmission power for the UL transmission if the FG value for the UL transmission is greater than a threshold. For example, if the WTRU is instructed to do so, the WTRU may determine one or more power control parameters (e.g., based on FG values). The WTRU may determine one or more power control parameters based on the FG value and the presence of DL transmissions in DL resources (e.g., which may be used for FG value determination). The WTRU may determine UL transmission power (e.g., first) without regard to FG values. The WTRU may scale (e.g., use a scaling factor) (e.g., each) the transmit power of the frequency resources, e.g., based on its associated FG value.

In an example, the WTRU may apply a second MCS (e.g., instead of applying the first MCS for UL or DL resource scheduling, configuration, and/or indication), where the second MCS may have a J-level MCS difference compared to the first MCS, e.g., if one or more of the above conditions and/or criteria are met (e.g., as described herein). The WTRU may be configured with more than one J value/parameter. The WTRU may be configured with J ₁、J₂, etc. (e.g., as multiple candidate MCS adjustment values/parameters, e.g., to apply multi-level dynamic MCS adjustment). The WTRU may apply (e.g., be configured and/or instructed/switched to) joint UL PC and MCS adjustment behavior. For example, if dynamic UL PC reduction (e.g., of more than X dB) is applied, the WTRU may apply WTRU-initiated MCS adjustment.

The WTRU may be configured to receive grants (e.g., in one or more mixed UL/DL symbols) for transmission of UL signals. In response to receiving the grant, the WTRU may determine ase:Sub>A Frequency Gap (FG) as ase:Sub>A value between the UL grant (e.g., first or last) RB and the closest reference RB (e.g., ref RB-ase:Sub>A, ref RB-B, ref RB-C, or Ref RB-D). The WTRU may adjust Tx parameters (e.g., MCS, link Adaptation (LA), and/or Power Control (PC) parameters) based on the determined FG value, for example. In an example, if the FG value is less than a predefined or preconfigured threshold, the WTRU may decrease the transmit power and/or decrease the MCS value/level for the transmission of UL signals scheduled by the grant. The WTRU may apply multi-level MCS/PC/LA adjustment based on using multiple thresholds (e.g., if configured). The WTRU may transmit UL signals using the determined or adjusted Tx parameters (e.g., MCS, LA, and/or PC parameters).

Drawings

Fig. 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

Fig. 1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communication system shown in fig. 1A, in accordance with an embodiment.

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 communication system shown in fig. 1A, according to an embodiment.

Fig. 1D is a system diagram illustrating another example RAN and another example CN that may be used within the communication system shown in fig. 1A, according to an embodiment.

Fig. 2 shows an example FD-gNB and HD-WTRU in a cell.

Fig. 3 illustrates example frequency gaps for allocated resources for UL transmissions (e.g., UL Tx) within UL resources.

Fig. 4A shows an example sub-band non-overlapping full duplex (SBFD).

Fig. 4B illustrates example SBFD operations based on transmit parameter adjustment.

Fig. 4C illustrates an example frequency gap value determination.

Detailed Description

Fig. 1A is a schematic diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messages, broadcasts, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 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 Discrete Fourier Transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter Bank Multicarrier (FBMC), and the like.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, rans 104/113, cns 106/115, public Switched Telephone Networks (PSTN) 108, the internet 110, and other networks 112, although it will be understood 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. As an 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 User Equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular telephones, personal Digital Assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hot spot or Mi-Fi devices, internet of things (IoT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronic devices, devices operating on a commercial and/or industrial wireless network, and the like. Any one of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

Communication system 100 may also include base station 114a and/or 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 internet 110, and/or the other network 112. As an example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node bs, evolved node bs (enbs), home node bs, home evolved node bs, next generation node bs (gnbs), NR node bs, site controllers, access Points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

Base station 114a may be part of RAN 104/113 that may also include other base stations and/or network elements (not shown), such as Base Station Controllers (BSCs), radio Network Controllers (RNCs), relay nodes, and the like. Base station 114a and/or 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 cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a particular geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of a 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 a cell. For example, beamforming may be used to transmit and/or receive signals in a desired spatial direction.

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, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).

More specifically, as noted above, communication 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, or the like. For example, a 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 use Wideband CDMA (WCDMA) to establish the air interfaces 115/116/117.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).

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and/or LTE-advanced (LTE-a) and/or LTEPro (LTE-a Pro) to establish the air interface 116.

In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may use a New Radio (NR) to establish the air interface 116.

In embodiments, 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, e.g., using a Dual Connectivity (DC) principle. Thus, the air interface utilized by the 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., enbs and gnbs).

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 1X, CDMA EV-DO, tentative standard 2000 (IS-2000), tentative standard 95 (IS-95), tentative standard 856 (IS-856), global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN), and the like.

The base station 114B in fig. 1A may be, for example, a wireless router, home node B, home evolved node B, or access point, and may utilize any suitable RAT to facilitate wireless connections in local areas such as business, home, vehicle, campus, industrial facility, air corridor (e.g., for use by drones), road, etc. In an 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 pico cell or femto cell. As shown in fig. 1A, the base station 114b may have a direct connection with the internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106/115.

The RANs 104/113 may communicate with the CNs 106/115, which may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. The data may have different quality of service (QoS) requirements, such as different 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, prepaid calls, internet connections, video distribution, etc., and/or perform advanced security functions such as user authentication. Although not shown in fig. 1A, it should be appreciated that the RANs 104/113 and/or CNs 106/115 may communicate directly or indirectly with other RANs that employ the same RAT as the RANs 104/113 or a different RAT. For example, in addition to being connected to a RAN 104/113 that may utilize NR radio technology, the CN 106/115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA 2000, wiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.PSTN 108 may include circuit-switched telephone networks that provide Plain Old Telephone Services (POTS). The internet 110 may include a global system for interconnecting computer networks and devices using common communication protocols, such as Transmission Control Protocol (TCP), user Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP internet protocol suite. Network 112 may include wired and/or wireless communication networks owned and/or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RANs 104/113 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 WTRU102c shown in fig. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based radio technology, and with a base station 114b, which may employ an IEEE 802 radio technology.

Fig. 1B is a system diagram illustrating an example WTRU 102. As shown in fig. 1B, 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 peripheral devices 138, etc. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

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, or the like. The processor 118 may perform signal decoding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit/receive element 122. Although fig. 1B depicts the processor 118 and the transceiver 120 as separate components, it should be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

The transmit/receive element 122 may be configured to transmit signals to and receive signals from a base station (e.g., base station 114 a) 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 one embodiment, the transmit/receive element 122 may be an emitter/detector configured to emit and/or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive RF and optical signals. It should be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

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

The transceiver 120 may be configured to modulate signals to be transmitted by the transmit/receive element 122 and demodulate signals received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (such as NR and IEEE 802.11).

The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128, such as a Liquid Crystal Display (LCD) display unit or an 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. Further, 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. 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 never physically locate memory access information on the WTRU 102, such as on a server or home computer (not shown), and store the data in that memory.

The processor 118 may receive power from the power source 134 and may be configured to distribute and/or control power to 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 battery packs (e.g., nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.

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

The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software modules and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, the number of the cells to be processed, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photographs and/or video), universal Serial Bus (USB) ports, vibrating devices, television transceivers, hands-free headsets, wireless communications devices, and the like,Modules, frequency Modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and/or augmented reality (VR/AR) devices, activity trackers, and the like. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; a geographic position sensor; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and/or humidity sensors.

WTRU 102 may include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and/or simultaneous. The full duplex radio station may include an interference management unit for reducing and/or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WRTU 102 may comprise a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and/or simultaneous.

Fig. 1C is a system diagram illustrating a RAN 104 and a CN 106 according to one embodiment. As noted above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using an E-UTRA radio technology. RAN 104 may also communicate with CN 106.

RAN 104 may include enode bs 160a, 160B, 160c, but it should be understood that 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 to communicate with the WTRUs 102a, 102B, 102c over the air interface 116. In an embodiment, the evolved node bs 160a, 160B, 160c may implement MIMO technology. Thus, the enode B160 a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example.

Each of the evolved node 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 UL and/or DL, and the like. As shown in fig. 1C, the enode bs 160a, 160B, 160C may communicate with each other over an X2 interface.

The CN 106 shown in fig. 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the evolved node bs 162a, 162B, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating the user of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, and the like. MME 162 may provide control plane functionality for switching between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and/or WCDMA.

SGW 164 may be connected to each of the evolved node bs 160a, 160B, 160c in RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102 c. The SGW 164 may perform other functions such as anchoring user planes during inter-enode B handover, triggering paging when DL data is available to the WTRUs 102a, 102B, 102c, managing and storing the contexts of the WTRUs 102a, 102B, 102c, etc.

The SGW 164 may be connected to a PGW 166 that may provide the WTRUs 102a, 102b, 102c with access to a packet switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network (such as the PSTN 108) to facilitate communications between the WTRUs 102a, 102b, 102c and legacy landline communication 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 other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers.

Although the WTRU is depicted in fig. 1A-1D as a wireless terminal, it is contemplated that in some representative embodiments such a terminal may use a wired communication interface with a communication network (e.g., temporarily or permanently).

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

A WLAN in an infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic to and/or from the BSS. Traffic originating outside the BSS and directed to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the respective destination. 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 pass the traffic to the destination STA. Traffic between STAs within a BSS may be considered and/or referred to as point-to-point traffic. Point-to-point traffic may be sent between (e.g., directly between) the source and destination STAs using Direct Link Setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunnel DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure mode of operation or similar modes of operation, the AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access/collision avoidance (CSMA/CA) may be implemented, for example, in an 802.11 system. For CSMA/CA, STAs (e.g., each STA), including the AP, may listen to the primary channel. If the primary channel is listened to/detected by a particular STA and/or determined to be busy, the particular STA may backoff. One STA (e.g., only one station) may transmit at any given time in a given BSS.

High Throughput (HT) STAs may communicate using 40MHz wide channels, for example, via a combination of a primary 20MHz channel with an adjacent or non-adjacent 20MHz channel to form a 40MHz wide channel.

Very High Throughput (VHT) STAs may support channels that are 20MHz, 40MHz, 80MHz and/or 160MHz wide. 40MHz and/or 80MHz channels may be formed by combining consecutive 20MHz channels. The 160MHz channel may be formed by combining 8 consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels (this may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data may pass through a segment parser that may split the data into two streams. An Inverse Fast Fourier Transform (IFFT) process and a time domain process may be performed on each stream separately. These streams may be mapped to two 80MHz channels and data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be sent to a Medium Access Control (MAC).

802.11Af and 802.11ah support modes of operation below 1 GHz. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11 ac. The 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the television white space (TVWS) spectrum, and the 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter type control/machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., supporting only) certain bandwidths and/or limited bandwidths. MTC devices may include batteries with battery lives above a threshold (e.g., to maintain very long battery lives).

WLAN systems that can support multiple channels, and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by STAs from all STAs operating in the BSS (which support a minimum bandwidth mode of operation). In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only) 1MHz mode, the primary channel may be 1MHz wide, even though the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and/or other channel bandwidth modes of operation. The carrier sense and/or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because the STA (supporting only 1MHz mode of operation) is transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band remains idle and possibly available.

The available frequency band for 802.11ah in the united states is 902MHz to 928MHz. In korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

Fig. 1D is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As noted above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, 102c over an air interface 116. RAN 113 may also communicate with CN 115.

RAN 113 may include gnbs 180a, 180b, 180c, but it should be understood that RAN 113 may include any number of gnbs while remaining consistent with an embodiment. Each of the gnbs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In an implementation, 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 gnbs 180a, 180b, 180 c. Thus, the gNB 180a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example. In an embodiment, the gnbs 180a, 180b, 180c may implement carrier aggregation techniques. 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 the unlicensed spectrum while the remaining component carriers may be on the licensed spectrum. In embodiments, the gnbs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180 c).

The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using transmissions associated with the scalable parameter sets. For example, the OFDM symbol interval and/or OFDM subcarrier interval may vary from one transmission to another, from one cell to another, and/or from one portion of the wireless transmission spectrum to another. The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using various or scalable length subframes or Transmission Time Intervals (TTIs) (e.g., including different numbers of OFDM symbols and/or continuously varying absolute time lengths).

The gnbs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in an independent configuration and/or in a non-independent configuration. In a standalone configuration, the WTRUs 102a, 102B, 102c may communicate with the gnbs 180a, 180B, 180c while also not accessing other RANs (e.g., such as the enode bs 160a, 160B, 160 c). In an independent configuration, the WTRUs 102a, 102b, 102c may use one or more of the gnbs 180a, 180b, 180c as mobility anchor points. In an independent configuration, the WTRUs 102a, 102b, 102c may use signals in unlicensed frequency bands to communicate with the gnbs 180a, 180b, 180 c. In a non-standalone configuration, the WTRUs 102a, 102B, 102c may communicate or connect with the gnbs 180a, 180B, 180c, while also communicating or connecting with other RANs (such as the enode bs 160a, 160B, 160 c). For example, the WTRUs 102a, 102B, 102c may implement DC principles to communicate with one or more gnbs 180a, 180B, 180c and one or more enodebs 160a, 160B, 160c substantially simultaneously. In a non-standalone configuration, the enode bs 160a, 160B, 160c may serve as mobility anchors for the WTRUs 102a, 102B, 102c, and the gnbs 180a, 180B, 180c may provide additional coverage and/or throughput for serving the WTRUs 102a, 102B, 102 c.

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 UL and/or DL, support of network slices, interworking between dual connectivity, NR and E-UTRA, routing of user plane data towards User Plane Functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and so on. As shown in fig. 1D, gnbs 180a, 180b, 180c may communicate with each other through an Xn interface.

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

AMFs 182a, 182b may be connected to one or more of gNB 180a, 180b, 180c in RAN 113 via an N2 interface and may function as a control node. For example, the AMFs 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slices (e.g., handling of different PDU sessions with different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMFs 182a, 182b may use network slices to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102 c. For example, different network slices may be established for different use cases, such as services relying on ultra-high reliability low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for Machine Type Communication (MTC) access, and so on. AMF 162 may provide control plane functionality for switching between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-a Pro, and/or non-3 GPP access technologies such as WiFi.

The SMFs 183a, 183b may be connected to AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to UPFs 184a, 184b in the CN 115 via an N4 interface. SMFs 183a, 183b may select and control UPFs 184a, 184b and configure traffic routing through UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, ethernet-based, etc.

UPFs 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 a packet-switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-host PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

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 other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may connect to the local Data Networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

In view of fig. 1A-1D and the corresponding descriptions of fig. 1A-1D, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more emulation devices (not shown): the WTRUs 102a-d, base stations 114a-B, evolved node bs 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMFs 182a-B, UPFs 184a-B, SMFs 183a-B, DN 185a-B, and/or any other devices described herein. The emulated device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation device may be used to test other devices and/or analog network and/or WTRU functions.

The simulation device may be designed to enable one or more tests of other devices in a laboratory environment and/or an operator network environment. For example, the one or more emulation devices can perform one or more or all of the 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 can perform one or more functions 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 testing purposes and/or may perform testing using over-the-air wireless communications.

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

Systems, methods, and instrumentalities are described herein related to power control and link adaptation for cross-division duplexing (XDD). A wireless transmit/receive unit (WTRU) may apply dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD), for example. For example, the WTRU may apply dynamic UL PC and/or dynamic MCS adjustment for XDD, or Tx behavior change (e.g., tx discard, skip, stop, cancel and/or defer or Tx with modified parameters) if at least one of the following conditions is met: if the frequency gap between the RBs of the first configuration and/or indication (e.g., for UL Tx) and the RBs of the second configuration and/or indication (e.g., for DL Rx) on the (e.g., same) symbol/slot is below a first threshold; if the spatial domain separation between the first configuration and/or indicated beam/RS/TCI for UL Tx and the second configuration and/or indicated beam/RS/TCI (e.g., for DL Rx) on the (e.g., same) symbol/slot is below a second threshold; if a priority indication of the RB for the first configuration and/or indication of UL Tx is given; etc. Priority rules (e.g., in the conditions and/or criteria described herein) may be predefined, configured, or indicated, for example, on which conditions may be applied as higher priority (e.g., as compared to others).

In an example, the WTRU may determine a first transmission power for UL transmission if a Frequency Gap (FG) value for UL transmission is equal to or less than a threshold. The WTRU may determine a second transmission power for the UL transmission if the FG value for the UL transmission is greater than a threshold. For example, if the WTRU is instructed to do so, the WTRU may determine one or more power control parameters (e.g., based on FG values). The WTRU may determine one or more power control parameters based on the FG value and the presence of DL transmissions in DL resources (e.g., which may be used for FG value determination). The WTRU may determine UL transmission power (e.g., first) without regard to FG values. The WTRU may scale (e.g., use a scaling factor) (e.g., each) the transmit power of the frequency resources, e.g., based on its associated FG value.

In an example, the WTRU may apply a second MCS (e.g., instead of applying the first MCS for UL or DL resource scheduling, configuration, and/or indication), where the second MCS may have a J-level MCS difference compared to the first MCS, e.g., if at least one of the above conditions and/or criteria is met (e.g., as described herein). The WTRU may be configured with more than one J value/parameter. The WTRU may be configured with J ₁、J₂, etc. (e.g., as multiple candidate MCS adjustment values/parameters, e.g., to apply multi-level dynamic MCS adjustment). The WTRU may apply (e.g., be configured and/or instructed/switched to) joint UL PC and MCS adjustment behavior. For example, if dynamic UL PC reduction (e.g., of more than X dB) is applied, the WTRU may apply WTRU-initiated MCS adjustment.

Dynamic time division duplexing (e.g., TDD) may be supported (e.g., in NR), for example, by a set of common (e.g., GC) DCIs (e.g., format 2_0 as shown in table 1), which may indicate TDD-UL-DL-config-common/dedicated slot formats and/or semi-static configurations (e.g., where each slot/symbol may be one of DL, UL, or flexible).

Table 1: time slot format for conventional cyclic prefix

…

Duplexing may be assumed to use half-duplex (HD), for example, for both the network (e.g., gNB) and the WTRU. Full Duplex (FD) may be supported. Full duplex may be supported (e.g., by enhancements) at least for the network/gNB (e.g., and also for the WTRU, which may include Integrated Access and Backhaul (IAB) devices). Fig. 2 shows an example FD-gNB and HD-WTRU in a cell. Cross-division duplexing (XDD) (e.g., sub-band level FD, as shown in fig. 2) may provide reduced FD implementation complexity, e.g., at the transmitter (e.g., at the gNB), e.g., in terms of cancelling self-interference (SI) and mitigating cross-link interference (CLI).

In an example (e.g., where the granularity of the subbands used for XDD may be a configurable set of RBs), the network (e.g., the gNB) may flexibly configure/schedule/indicate (e.g., to the first WTRU) transmission of UL resources (e.g., PUSCH, PUCCH, SRS) over a first set of RBs, e.g., which may be adjacent to a second set of RBs for DL reception by the second WTRU (e.g., in terms of XDD). If the first WTRU and the second WTRU are close to each other, UL resource transmission by the first WTRU may cause WTRU-to-WTRU CLI (e.g., CLI leakage), e.g., on a neighboring second set of RBs for DL reception by the second WTRU. Dynamic CLI leakage problems may exist on adjacent DL and UL subbands.

Hereinafter, the phrases a, an and the like may be construed to be one or more or at least one. Any term ending with the suffix(s) can be construed as one or more or at least one. For example, a term may be able to be interpreted as a phrase.

The term subband may refer to frequency domain resources and may be characterized by one or more of the following: a set of Resource Blocks (RBs); a set of resource block sets (RB sets) (e.g., if the carrier has an intra-cell guard band); interleaving a set of resource blocks; a bandwidth portion (e.g., or a portion of a bandwidth portion); or a carrier wave (e.g., or a portion of a carrier wave).

For example, a subband may be characterized by a starting RB and number of RBs of a set of consecutive RBs (e.g., within a bandwidth portion). The subbands may be defined by values of a frequency domain resource allocation field and a bandwidth part index.

The term XDD may refer to sub-band aspect duplexing (e.g., using UL or DL per sub-band), and may be characterized by one or more of the following: cross-division duplexing (e.g., subband-wise FDD within the TDD band); full duplex on a subband basis (e.g., full duplex, as both UL and DL may be used/mixed on symbols/slots, and UL or DL may be used per subband on symbols/slots); frequency Domain Multiplexing (FDM) of DL/UL transmissions (e.g., within the TDD spectrum); sub-band non-overlapping full duplex (e.g., non-overlapping sub-band full duplex); full duplex except for common frequency (e.g., spectrum sharing, overlapping sub-band aspects) full duplex; or advanced duplexing methods (e.g., methods other than TDD or FDD, such as pure TDD or pure FDD).

The term MCS adjustment may refer to a MCS change/adjustment (e.g., WTRU initiated/directed) from an MCS level for scheduling, configuration and/or indication of UL (or DL) resources. MCS adjustment may be used as a representative name for MCS change/adjustment (e.g., WTRU initiated/directed), such as, but not limited to, a specific example only.

For example, the term MCS adjustment may imply an MCS change between a first MCS (e.g., scheduling, configuring, and/or indicating an association with UL (or DL) resources) and a second (e.g., alternative) MCS. The WTRU may determine the second MCS, for example, based on an MCS adjustment (e.g., but not necessarily, based on an MCS adjustment). In an example, the first MCS may be an MCS configured or activated for the configured grant type 1 or 2 (e.g., for UL), an MCS in an SPS activation command (e.g., for DL), or an MCS indicated in DCI (e.g., for dynamic grant or dynamic assignment, etc.).

The term dynamic/flexible TDD may refer to a TDD system/cell that may dynamically and/or flexibly change, adjust, and/or switch communication directions (e.g., downlink, uplink, or side link, etc.) over a time instance (e.g., slot, symbol, subframe, etc.). In one example, in a system employing dynamic/flexible TDD, a Component Carrier (CC) or a bandwidth part (BWP) may have one single type among 'D', 'U' and 'F' on a symbol/slot based on an indication of a Group Common (GC) -DCI (e.g., format 2_0) including a Slot Format Indicator (SFI) and/or based on a TDD-UL-DL-config-common/dedicated configuration. At a given time instance/slot/symbol, a first gNB (e.g., cell, TRP) employing dynamic/flexible TDD may transmit downlink signals to a first WTRU in communication with/associated with the first gNB based on a first SFI and/or TDD-UL-DL-config configured and/or indicated by the first gNB, and a second gNB (e.g., cell, TRP) employing dynamic/flexible TDD may receive uplink signals transmitted from a second WTRU in communication with/associated with the second gNB based on a second SFI and/or TDD-UL-DL-config configured and/or indicated by the second gNB. In one example, a first WTRU may determine that reception of a downlink signal is being interfered with by an uplink signal, where interference caused by the uplink signal may refer to WTRU-to-WTRU cross-layer interference (CLI).

The WTRU may transmit or receive physical channels or reference signals according to one or more spatial domain filters. The term beam may refer to a spatial domain filter.

The WTRU may transmit a physical channel or signal using the same spatial domain filter as that used to receive an RS (such as CSI-RS) or SS block. The WTRU transmissions may be referred to as targets and the received RS or SS blocks may be referred to as references or sources. In such cases, the WTRU may purportedly transmit the target physical channel or signal according to a spatial relationship referencing such RS or SS blocks.

The WTRU may transmit the first physical channel or signal according to the same spatial domain filter as that used to transmit the second physical channel or signal. The first transmission and the second transmission may be referred to as a target, a reference, and/or a source, respectively. In such cases, the WTRU may purportedly transmit a first (e.g., target) physical channel or signal according to a spatial relationship referencing a second (e.g., reference) physical channel or signal.

The spatial relationship may be implicit, configured by RRC, and/or signaled by a MAC CE or DCI. For example, the WTRU may implicitly transmit PUSCH and PUSCH DM-RS according to the same spatial domain filter as the SRS indicated by the SRI indicated in the DCI or configured by the RRC. In another example, the spatial relationship may be configured by RRC for SRS Resource Indicator (SRI) or signaled by MAC CE for PUCCH. Such spatial relationships may also be referred to as beam pointing.

The WTRU may receive the first (e.g., target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as the second (e.g., reference) downlink channel or signal. For example, such an association may exist between a physical channel such as a PDCCH or PDSCH and its corresponding DM-RS. Such an association may exist when the WTRU is configured with a quasi-parity (QCL) hypothesis type D between corresponding antenna ports, at least when the first signal and the second signal are reference signals. Such association may be configured to transmit a configuration indicator (TCI) state. The WTRU may indicate the association between CSI-RS or SS blocks and DM-RS by an index to the TCI state set (configured by RRC and/or signaled by MAC CE). Such an indication may also be referred to as a beam indication.

TRP (e.g., transmission and reception points) may be used interchangeably herein with one or more of Transmission Point (TP), reception Point (RP), radio Remote Head (RRH), distributed Antenna (DA), base Station (BS), sector (e.g., of BS), and cell (e.g., geographic cell area served by BS). Multiple TRP may be used interchangeably herein with one or more of MTRP, M-TRP, and/or multiple TRP.

The WTRU may report a subset of Channel State Information (CSI) components, where the CSI components may correspond to at least one of a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of a faceplate for reception at the WTRU (e.g., such as a faceplate identification or a group identification), measurements such as L1-RSRP, L1-SINR (e.g., CRI-RSRP, CRI-SINR, SSB-Index-RSRP, SSB-Index-SINR) taken from SSB or CSI-RS, and/or other channel state information such as one or more of a Rank Indicator (RI), a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Layer Index (LI), and so on.

The WTRU may receive a synchronization signal/physical broadcast channel (SS/PBCH) block (SSB). SSBs may include a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and/or a Physical Broadcast Channel (PBCH). The WTRU may monitor, receive, and/or attempt to decode SSBs during initial access, initial synchronization, radio Link Monitoring (RLM), cell search, cell handover, etc.

The WTRU may measure and report Channel State Information (CSI). The CSI for each connection mode may include or be configured with one or more of a CSI reporting configuration, a CSI-RS resource set, and/or one or more NZP CSI-RS resources. The CSI reporting configuration may include a CSI reporting amount (e.g., channel Quality Indicator (CQI), rank Indicator (RI), precoding Matrix Indicator (PMI), CSI-RS resource indicator (CRI), layer Indicator (LI), etc.), a CSI reporting type (e.g., aperiodic, semi-persistent, periodic), a CSI reporting codebook configuration (e.g., type I, type II port selection, etc.), and/or a CSI reporting frequency.

The CSI-RS resource set may include one or more of the following CSI resource settings: NZP-CSI-RS resources for channel measurements, NZP-CSI-RS resources for interference measurements, and/or CSI-IM resources for interference measurements.

The NZP CSI-RS resources may include NZP CSI-RS resource IDs, periodicity and offset, QCL information, and TCI status and/or resource mapping (e.g., port number, density, CDM type, etc.).

The 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. For example, one or more of the following may be applied. The following parameters are non-limiting examples of parameters that may be included in the reference signal measurements. One or more of these parameters may be included. Other parameters may be included.

The SS reference signal received power (SS-RSRP) may be measured based on a synchronization signal (e.g., demodulation reference signal (DMRS) or SSs in PBCH). SS-RSRP may be defined as a linear average of the power contributions to the Resource Elements (REs) carrying the respective synchronization signals. In measuring RSRP, power scaling for the reference signal may be performed. In case SS-RSRP is used for L1-RSRP, the measurement may be done based on CSI reference signals in addition to synchronization signals.

The CSI-RSRP may be measured based on a linear average of power contributions to Resource Elements (REs) carrying the respective CSI-RS. CSI-RSRP measurements may be configured within measurement resources of the configured CSI-RS occasion.

SS signal-to-noise-and-interference ratio (SS-SINR) may be measured based on a synchronization signal (e.g., DMRS or SSS in PBCH). SS-SINR may be defined as the linear average of the power contributions to the Resource Elements (REs) carrying the respective synchronization signals divided by the linear average of the noise and interference power contributions. In the case that SS-SINR is used for L1-SINR, noise and interference power measurements may be done based on resources configured by higher layers.

The CSI-SINR may be measured based on a linear average of power contributions to Resource Elements (REs) carrying the respective CSI-RS divided by a linear average of noise and interference power contributions. When CSI-SINR is used for L1-SINR, noise and interference power measurements may be done based on resources configured by higher layers. Otherwise, noise and interference power may be measured based on the resources carrying the respective CSI-RS.

A Received Signal Strength Indicator (RSSI) may be measured based on an average of the configured OFDM symbols and the total power contribution in the 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.).

A cross-layer interference received signal strength indicator (CLI-RSSI) may be measured based on an average of total power contributions 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.).

The sounding reference signal RSRP (SRS-RSRP) may be measured based on a linear average of power contributions to Resource Elements (REs) carrying the respective SRS.

The characteristics of the authorization or assignment may include one or more of the following: frequency allocation; aspects of time allocation (such as duration, for example); a priority; modulation and coding schemes; transmission block size; the number of spatial layers; the number of transport blocks; TCI status, CRI or SRI; repeating the times; whether the repetition scheme is type a or type B; whether the authorization is a configured authorization type 1, type 2 or dynamic authorization; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configuration) assignment; configured authorization indexes or semi-persistent assignment indexes; periodicity of configured grants or assignments; a Channel Access Priority Class (CAPC); and/or any other parameter provided in the DCI by the MAC or by the RRC for scheduling grants or assignments.

The indication by DCI may include an explicit indication by DCI field or by RNTI for masking CRC of PDCCH. The indication by DCI may include an implicit indication by a characteristic such as a 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 a mapping between the characteristic and the value may be signaled by RRC or MAC.

RS may be used interchangeably herein with one or more of RS resources, sets of RS resources, RS ports, and/or groups of RS ports.

RS may be used interchangeably herein with one or more of SSB, CSI-RS, SRS, and/or DM-RS.

The WTRU may be configured to adjust one or more Tx parameters for the UL signal based on the frequency gap, spatial domain separation, and/or priority indication. For example, the WTRU may adjust a transmit power or a Modulation Coding Scheme (MCS) level based on the frequency gap, the spatial domain separation, and/or the priority indication. The UL signal may be associated with one or more RBs in the vicinity (e.g., adjacent) of one or more DL RB sets. Cross-link interference (CLI) may result when one or more RBs for UL signals are close in frequency to one or more DL RB sets. The WTRU may adjust one or more Tx parameters for the UL signal to reduce CLI.

The frequency gap may be a value between (e.g., first or last) RBs of the UL signal and a reference symbol (e.g., a closest reference symbol). The spatial domain separation may be a separation value between a beam/TCI associated with the UL signal and a DL reference beam/TCI. The WTRU may adjust one or more Tx parameters when the spatial domain separation is less than a predetermined threshold. The priority indication may be associated with the UL signal. The WTRU may adjust one or more Tx parameters when the priority indicated by the priority indication is above a predetermined threshold and/or level. The adjustment of one or more Tx parameters may be dynamic. For example, the WTRU may adjust one or more Tx parameters for each.

Dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) may be applied. In an example, for example, a WTRU may apply dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) or Tx behavior change (e.g., tx discard, skip, stop, cancel, and/or defer or Tx with modified parameters) if one or more of the following conditions are met: the frequency gap between the RBs of the first configuration, schedule, and/or indication (e.g., for UL Tx) and the RBs of the second configuration, schedule, and/or indication (e.g., for DL Rx) on the (e.g., same) symbol/slot is below a first threshold; the spatial domain separation between the first configured, activated and/or indicated beam/RS/TCI (e.g., for UL Tx) and the second configured, activated and/or indicated beam/RS/TCI (e.g., for DL Rx) on (e.g., the same) symbol/slot is below a second threshold (e.g., in terms of beam index, or based on pre-configuration rules across multiple beam configuration candidates); or provide a priority indication of the RB (e.g., for UL Tx) of the first configuration, schedule, and/or indication. The beam configuration may represent a beam/RS/TCI (e.g., one or more beams for transmission or reception, one or more RSs for transmission or reception, and/or TCI for Tx or Rx). The TCI may include beam information, timing information, and/or doppler related information. Beam configuration may be used interchangeably herein with beam/RS/TCI.

For example, if the frequency gap between a first configured, scheduled, and/or indicated RB (e.g., for UL Tx) and a second configured, scheduled, and/or indicated RB (e.g., for DL Rx) over (e.g., the same) symbol/slot is below a first threshold, the WTRU may apply (e.g., be configured to) dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) or Tx behavior change (e.g., tx discard, skip, stop, cancel, defer, and/or Tx with modified parameters). A WTRU that is to transmit UL resources over a first RB may identify the frequency location of a second RB, e.g., to make a comparison to evaluate conditions and/or criteria (e.g., to determine whether the frequency gap is below a first threshold).

The frequency location of the second RB may be known, identified, and/or determined, e.g., based on a hybrid (UL/DL) slot/symbol type configuration and/or indication, e.g., by including enhanced tdd-UL-DL-config of the hybrid slot/symbol type. In an example, a hybrid (e.g., UL/DL) slot/symbol type may indicate slots/symbols that may be used for both DL and UL, each allocated (e.g., non-overlapping) independent RBs over a slot/symbol, e.g., for XDD (e.g., on the gNB side).

In an example, independent RBs on slots/symbols for DL and UL (e.g., each of DL and UL) may partially or fully overlap, e.g., based on configuration and/or indication of a network (e.g., of a gNB) of the WTRU.

In an example, if a slot/symbol for transmission of UL resources corresponds to a hybrid slot/symbol type (e.g., is configured and/or indicated to the WTRU), the WTRU may determine a frequency gap between a first RB for UL Tx and any (e.g., nearest) RBs belonging to the RBs of the DL corresponding to the hybrid slot/symbol type.

In an example, the WTRU may receive a subband-specific slot format indication and determine the frequency gap from a configured subband and slot format combination.

The frequency location of the second RB may be (e.g., explicitly) signaled, configured, and/or indicated (e.g., by the network, such as from the gNB) to the WTRU (e.g., as a muted (e.g., DL) RB, muted (e.g., DL) frequency region, an indication (e.g., DL) RB for muting, puncturing, skipping, interrupting, and/or flipping, or an indication (e.g., DL) RB for a specific purpose (including a purpose indicating frequency gaps, etc.), e.g., via MAC-CE signaling and/or DCI signaling. In an example, the explicit signaling may include information related to DL RBs (e.g., allocated to a second WTRU), e.g., where the information related to the second WTRU may be signaled and/or indicated to the WTRU (e.g., to support/assist in performing WTRU-to-WTRU CLI mitigation actions at the WTRU, etc.).

In an example, the information related to the second WTRU may include information related to a WTRU ID (e.g., corresponding to the second WTRU), e.g., where the WTRU ID may be a parameter configured for the second WTRU. The information related to the WTRU ID may include and/or indicate an RNTI (e.g., C-RNTI, etc.) and/or sequence initialization or scrambling parameters (e.g., configured for the second WTRU).

The WTRU may receive (e.g., overhear) DCI transmitted for the second WTRU. Based on receiving the DCI (e.g., directly), the WTRU may determine and/or identify a frequency location of a second RB (e.g., which may include a scheduled RB for the second WTRU).

In an example, the information related to the second WTRU may include information related to beam/RS/TCI (e.g., associated with DL RBs) and/or parameters for signal strength/quality metrics associated with beam/RS/TCI, for example (e.g., RSRP, L1-RSRP, cri-RSRP, ssb-Index-RSRP, L1-SINR, and/or SRS-RSRP, etc.).

In an example, the RS of the beam/RS/TCI may be SRS and the parameter for the signal strength/quality metric may be SRS-RSRP, e.g., where the SRS-RSRP may be determined (e.g., by the second WTRU) based on the measured SRS.

The frequency location of the second RB may be implicitly identified and/or determined by the WTRU, e.g., based on predefined and/or preconfigured rules. In an example, the predefined rule may be that the second RB used for comparison to evaluate the condition and/or criteria (e.g., to determine whether the frequency gap is below a first threshold) is one or more sets of DL RBs previously received, monitored, and/or measured at the WTRU. The one or more sets may be DL RBs that were recently received, monitored, and/or measured. The one or more sets may be the union of the most recently received, monitored and/or measured DL RBs of X (1) and/or within predefined and/or preconfigured time window parameters and/or values.

The first threshold may be predefined, preconfigured, identified, and/or indicated to the WTRU, e.g., as Y (1) RB. In an example, if y=2, then the conditions and/or criteria for applying dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) may be satisfied if the frequency gap between the first RB for UL and the second RB for DL is less than or equal to y=2 RB.

In an example, the multi-level threshold and accordingly the multi-level dynamic UL PC applied for XDD may be configured and/or adapted for the WTRU. In an example, two values of the threshold may be configured for the WTRU, y1=2 and y2=5. The WTRU may apply level 1 dynamic UL PC operation, e.g., P1 dB UL power reduction, if the frequency gap between the first RB for UL and the second RB for DL is less than or equal to y1=2 RBs. If the frequency gap between the first RB for UL and the second RB for DL is between y1=2 RB and y2=5 RB, the WTRU may apply level 2 dynamic UL PC operation, e.g., P2 (e.g., where P2< P1) dB UL power reduction. The WTRU may prohibit the application (e.g., not apply) of dynamic UL PC operation (e.g., for XDD) if the frequency gap between the first RB for UL and the second RB for DL is greater than y2=5 RB.

The multi-level threshold and correspondingly applying multi-level dynamic (UL) MCS adjustment (e.g., for XDD) may be configured and/or applicable to the WTRU. In an example, two values of the threshold may be configured for the WTRU, y1=2 and y2=5. If the frequency gap between the first RB for UL and the second RB for DL is less than or equal to y1=2 RBs, the WTRU may apply level 1 dynamic MCS adjustment, e.g., a Q1 level MCS reduced from the MCS level for scheduling, configuration, and/or indication of UL resources. If the frequency gap between the first RB for UL and the second RB for DL is between y1=2 RB and y2=5 RB, the WTRU may apply level 2 dynamic MCS adjustment, e.g., a Q2 level MCS reduced from the MCS level for scheduling, configuration, and/or indication of UL resources. The WTRU may prohibit the application (e.g., not apply) of dynamic MCS adjustment (for XDD) if the frequency gap between the first RB for UL and the second RB for DL is greater than y2=5 RBs.

Fig. 3 illustrates an example frequency gap 300 of allocated resources for UL transmissions 310 (e.g., UL Tx) within UL resources 304. The frequency gap may be a frequency distance between the allocated UL resources and adjacent resources (e.g., DL resources) determined, scheduled, configured, and/or allocated in the time slot. The frequency gap may define a frequency interval between allocated resources and adjacent (e.g., downlink) resources in a time slot.

For example, UL Tx 310 may be allocated one or more resources within UL resource 304. UL resources 304 may be adjacent to one or more DL resources 302, 306. For example, UL resource 304 may be between first DL resource 302 and second DL resource 306. The WTRU may determine one or more (e.g., two) frequency gap values 305, 315 for the allocated resources of UL transmission 310 based on one or more DL resources 302, 306. For example, the first frequency gap value 305 (e.g., FG (1)) may be a frequency interval between the first DL resource 302 and a first frequency resource (e.g., first RB) allocated for UL Tx 310. The second frequency gap value 315 (e.g., FG (2)) may be a frequency interval between the second DL resource 306 and the last frequency resource (e.g., last RB) allocated for UL Tx 310.

The frequency gap of UL Tx 310 may be the minimum between first frequency gap value 305 (e.g., FG (1)) and second frequency gap value 315 (e.g., FG (2)). The frequency gap of UL frequency resources (e.g., UL RBs) may be referred to as the frequency distance between the closest DL resource and the UL frequency resource. The closest DL resource may be closest to the first RB associated with UL Tx 310 or closest to the last RB associated with UL Tx 310. The frequency gap may be indicated as a unit of RBs, subcarriers, or subbands.

The frequency gap may be a frequency interval between uplink resources and a reference frequency, e.g., where the uplink resources are resources allocated (e.g., scheduled and/or configured) for UL transmissions. The reference frequency may be one or more of the following: first, last, or center frequency resources (e.g., RBs, subcarriers) of adjacent downlink resources or downlink resource regions; a first, last, or center frequency resource of the associated bandwidth portion; first, last, or center frequency resources of a default bandwidth portion (e.g., bwp#0); first, last, or center frequency resources of an associated SS/PBCH block; or frequency resources configured within BWP.

Frequency gap may be used interchangeably herein with frequency location, FG, frequency Gap Distance (FGD), frequency distance, frequency spacing, minimum frequency gap, minimum frequency distance, minimum FG, cross-link frequency gap, and cross-link frequency distance.

The WTRU may determine one or more power control parameters for UL Tx based on spatial domain separation between UL beam configuration (e.g., for UL Tx) and DL beam configuration. For example, the WTRU may receive an indication to adjust one or more power control parameters according to a spatial domain separation between UL beam configuration (e.g., for UL Tx) and DL beam configuration. The WTRU may determine UL transmission power (e.g., without regard to spatial domain separation). The WTRU may determine the scaling factor based on spatial domain separation. The WTRU may scale (e.g., use a scaling factor) the transmission power of UL Tx based on the scaling factor determined based on the spatial domain separation.

The WTRU may apply dynamic UL PC, dynamic MCS adjustment (e.g., for XDD), and/or Tx behavior change (e.g., tx discard, skip, stop, cancel, defer, or Tx with modified parameters) based on spatial domain separation (e.g., configured). For example, if the spatial domain separation between the first configuration, activated and/or indicated beam/RS/TCI for UL Tx and the second configuration, activated and/or indicated beam/RS/TCI for DL Rx on the same symbol/slot is below a second threshold (e.g., in terms of beam index, or based on a pre-configuration rule across multiple beam configuration candidates). The WTRU may be configured to transmit UL resources over the first RB using the first beam configuration, and may identify and/or determine a second beam configuration to compare to evaluate a condition or criterion (e.g., determine whether spatial domain separation is below a second threshold).

The second beam configuration may be identified and/or determined based on a mixed (UL/DL) slot/symbol type configuration and/or indication, e.g., by enhanced tdd-UL-DL-config (which may include mixed slot/symbol types). In an example, the WTRU may be notified of a second beam configuration associated with RBs allocated for DL in a hybrid (UL/DL) slot/symbol type. Such associations may be one or more of the following: the second beam configuration is for an expected receive beam configuration of the WTRU through RBs of the DL in the hybrid slot/symbol type; the second beam configuration is different from (e.g., has) information content (e.g., is configured and/or indicated for evaluation of conditions and/or criteria (e.g., determining whether spatial domain separation is below a second threshold)) of a third beam configuration (e.g., has) configured and/or indicated as a desired beam configuration for DL reception by the WTRU on the RBs.

The second beam configuration may be (e.g., explicitly) signaled, configured, and/or indicated (e.g., by the network, such as from the gNB) to the WTRU (e.g., based on differences in beam configuration index, and/or based on configured and/or indicated spatial domain windows/ranges used to determine spatial domain separation, etc.), e.g., by MAC-CE signaling and/or DCI signaling. In an example, the explicit signaling may include (e.g., desired) DL receive beam configuration related information of the second WTRU and/or beam quality metrics associated with the beam configuration of the second WTRU (e.g., RSRP, L1-RSRP, cri-RSRP, ssb-Index-RSRP, L1-SINR, and/or SRS-RSRP, etc.). In an example, the RS of the beam configuration of the second WTRU may be SRS and the beam quality metric may be SRS-RSRP, e.g., where the SRS-RSRP may be determined and/or derived (e.g., by the second WTRU) based on measuring the SRS.

The second beam configuration may be identified and/or determined (e.g., implicitly) by the WTRU (e.g., based on predefined/preconfigured rules), e.g., based on differences in beam configuration index, and/or based on configured and/or indicated spatial domain windows/ranges (e.g., for determining spatial domain separation, etc.). In an example, the predefined rule may be one or more of a second beam configuration for comparison to evaluate conditions and/or criteria (e.g., to determine whether the spatial domain separation is below a second threshold) and a beam configuration for (e.g., previous) use and/or application of DL RBs (e.g., over hybrid slot/symbol type symbols/slots) received, monitored, and/or measured at the WTRU. In an example, one or more of the previously used and/or applied beam configurations may be a most recently used and/or applied beam configuration of DL RBs (e.g., on symbols indicating/associated with a hybrid slot/symbol type) for reception, monitoring, and/or measurement at the WTRU. In an example, one or more of the previously used and/or applied beam configurations may be a union of the most recently used and/or applied beams/RS/TCI (and/or within predefined/preconfigured time window parameters and/or values) of a (≡1).

The second threshold may be predefined, preconfigured, identified, and/or indicated to the WTRU. The second threshold may be predefined, preconfigured, identified, and/or indicated to the WTRU, for example, as a difference in B (> 1) beam (/ RS/TCI) index (e.g., the beam index may continuously increase in a monotonic manner according to actual spatial domain beam direction changes, or the gNB may configure and/or indicate pattern related information across the beam configuration index for the WTRU to calculate and/or evaluate the difference in beam configuration index). In an example, if b=2, then conditions and/or criteria for applying dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) or Tx behavior change (e.g., tx discard, skip, stop, cancel, defer, and/or Tx with modified parameters) may be met, e.g., if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration for DL is less than or equal to the difference in beam configuration index of b=2.

The second threshold may be predefined, preconfigured, identified and/or indicated to the WTRU, for example, based on configured and/or indicated spatial domain windows and/or angular domain range/extension related parameters, etc. (e.g., for determining spatial domain separation, etc.).

In an example, the multi-level threshold and accordingly the multi-level dynamic UL PC applied for XDD may be configured for and/or adapted for use by the WTRU. For example, the first threshold may be associated with applying a first dynamic UL PC operation. The second threshold may be associated with applying a second dynamic UL PC operation. The second threshold may be greater than the first threshold. In an example, two values of the threshold (e.g., a first threshold and a second threshold) may be configured to b1=3 and b2=7. The WTRU may apply a first (e.g., level 1) dynamic UL PC operation, e.g., P1 dB UL power reduction, if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is less than or equal to a first threshold (e.g., a difference in b1=3 beam configuration index). The WTRU may apply level 2 dynamic UL PC operation, e.g., P2 (< P1) dB UL power reduction, if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is between a first threshold (e.g., b1=3) and a second threshold (e.g., b2=7). For example, when the difference in beam configuration index is greater than a first threshold and less than a second threshold, the difference in beam configuration index may be between the first threshold and the second threshold. The WTRU may prohibit (e.g., may not apply) dynamic UL PC operation (e.g., for XDD) if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is greater than the difference in second b2=7 beam/RS/TC index.

In an example, the multi-level threshold and correspondingly applying multi-level dynamic (UL) MCS adjustment (for XDD) may be configured and/or applicable to the WTRU. For example, the first threshold may be associated with applying a first dynamic MCS adjustment. The second threshold may be associated with applying a second dynamic MCS adjustment. The second threshold may be greater than the first threshold. In an example, two values of the threshold may be configured for WTRUs b1=3 and b2=7. The WTRU may apply a first (e.g., level 1) dynamic MCS adjustment, e.g., a Q1 level MCS reduced from the MCS level for scheduling, configuration, and/or indication of UL resources, if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is less than or equal to a first threshold (e.g., b1=3) beam configuration index. If the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is between b1=3 and b2=7, the WTRU may apply a level 2 dynamic MCS adjustment, e.g., a Q2 level MCS reduced from the MCS level for scheduling, configuration, and/or indication of UL resources. The WTRU may prohibit (e.g., not apply) dynamic MCS adjustment (e.g., for XDD) if the difference in beam configuration index between the first beam configuration for UL and the second beam configuration (for DL) is greater than the difference in b2=7 beam/RS/TC index.

The WTRU may apply dynamic UL PC and/or dynamic MCS adjustment (e.g., for XDD) or Tx behavior change (e.g., tx discard, skip, stop, cancel and/or defer or Tx with modified parameters), e.g., if a priority indication of RBs for the first configuration, schedule and/or indication of UL Tx is given. The priority indication may imply giving priority (e.g., of a particular level) to UL Tx (e.g., as compared to other actions on the second UL and/or DL resource on the (e.g., same) symbol/slot).

In an example, a priority indication may be sent (e.g., given) to UL Tx. For example, if a priority indication is given to UL Tx, the WTRU may prohibit application (e.g., may not apply) of dynamic UL PC operation and/or dynamic MCS adjustment (e.g., for XDD), or Tx behavior change (e.g., tx discard, skip, stop, cancel and/or defer or Tx with modified parameters). If a priority indication is given to UL Tx, the WTRU may prohibit application (e.g., may not apply) of dynamic UL PC operation and/or dynamic MCS adjustment (e.g., for XDD), or Tx behavior change (e.g., tx discard, skip, stop, cancel, and/or defer or Tx with modified parameters), e.g., regardless of whether other conditions and/or criteria are met. The WTRU may apply dynamic UL PC operation with different levels of power reduction and/or different levels of MCS adjustment and/or dynamic MCS adjustment (e.g., for XDD), e.g., if a priority indication is given (e.g., to UL Tx).

In an example, if no priority indication is given, the WTRU may apply X (dB) UL power reduction, e.g., based on applying dynamic UL PC operation (e.g., for XDD). If a priority indication is given, the WTRU may apply f (X) (dB) UL power reduction, e.g., based on applying dynamic UL PC operation (e.g., for XDD), where f (X) may be a calculated value (e.g., a function f ()) based on a pre-definition, pre-configuration, and/or indication of value X). In an example, f (X) may be a value reduced from X. For example, instead of applying X-dB UL power reduction, a reduced power reduction value of f (X) (e.g., as compared to X) may be applied (e.g., based on a given priority indication). In an example, f (X) may be a value that increases from X. For example, instead of applying X-dB UL power reduction, power boosting of f (X) may be applied based on a given priority indication (e.g., if a (e.g., polar) high priority is indicated for UL TX, e.g., URLLC packets of the (e.g., special polar) type, etc.).

In an example, if no priority indication is given, the WTRU may apply the Y-level MCS adjustment, e.g., based on applying dynamic MCS adjustment (e.g., for XDD). If a priority indication is given, the WTRU may apply g (Y) level MCS adjustment, e.g., based on applying dynamic MCS adjustment (e.g., for XDD), where g (Y) may be a value calculated based on a predefined, preconfigured and/or indicated function g (). In an example, g (Y) may be a value reduced from Y. The reduced MCS reduction value of g (Y) (e.g., as compared to Y) may be applied based on, for example, the given priority indication, rather than applying the Y-level MCS reduction/reduction. In an example, g (Y) may be a value increased from Y. For example, rather than applying a Y-level MCS reduction/decrease, a higher MCS for g (Y) may be applied based on the given priority indication (e.g., if a (e.g., very) high priority is indicated for UL TX, e.g., packets requiring a high data rate (e.g., URLLC) are successfully delivered with lower latency, so that a higher MCS may be desired based on efficient network implementations with interference management around UL TX).

Priority rules (e.g., as described herein in the conditions and/or criteria above) may be predefined, configured, or indicated, for example, on which conditions may be applied as higher priority than others. In an example, the condition of whether to give a priority indication for the first configured, scheduled and/or indicated RB for UL Tx may have the highest priority. If the condition of whether the priority indication for the first configured, scheduled and/or indicated RB for UL Tx is met or not is met, UL power reduction and/or MCS adjustment may not be applied, e.g. regardless of whether other conditions are met or not.

In an example, a condition whether a frequency gap between a first configured, scheduled, and/or indicated RB for UL Tx and a second configured, scheduled, and/or indicated RB (e.g., for DL Rx) on the same symbol/slot is below a first threshold may have a second highest priority. For example, if the condition of whether the priority indication for the first configured, scheduled and/or indicated RB for UL Tx is not satisfied, then it may be checked next whether the frequency gap is below a first threshold. For example, if the frequency gap between the first RB for UL and the second RB for DL is greater than Y2 RB, the WTRU may prohibit application (e.g., not application) of dynamic UL PC operation for XDD (e.g., regardless of a condition that checks whether the spatial domain separation between the first configured, activated, and/or indicated beam/RS/TCI for UL Tx and the second configured, activated, and/or indicated beam/RS/TCI (e.g., for DL Rx) on the same symbol/slot is below a second threshold), and so on.

Sub-band non-overlapping full duplex (SBFD) operations may be performed based on one or more Tx parameter adjustments. In an example, new Radio (NR) duplexing operations (e.g., NR-duplexing, XDD, etc.) may improve conventional TDD operations by enhancing UL coverage, increasing capacity, reducing latency, etc. Conventional TDD operation may be based on splitting the time domain between the uplink and downlink. Investigation (e.g., as shown in fig. 4A) may be conducted considering the feasibility of allowing full duplex, or more specifically SBFD (e.g., at the gNB), within a conventional TDD band, wherein the SBFD slots shown (including frequency resource allocation based on a combination of DL SB and UL SB) may be based on a hybrid (UL/DL) slot/symbol type configuration/indication, e.g., examples of known, identified and/or determined by enhanced TDD-UL-DL-config including hybrid slot/symbol types and the like described in this disclosure. In an example, a hybrid (UL/DL) slot/symbol type may indicate slots/symbols that may be used for both DL and UL, each allocated a (non-overlapping) independent RB on the slot/symbol, e.g., for XDD/SBFD (e.g., on the gNB side). The gNB may schedule UL and DL resources to the WTRUs within the UL and DL non-overlapping subbands, respectively.

Fig. 4A depicts an example SBFD slot format 400. The example SFBD slot format 400 may include multiple slots. For example, the example SFBD slot format 400 may include a DL slot 410, one or more hybrid slots 420, 430, a flexible slot 440, and a UL slot 442.DL slots 410 may be reserved for downlink transmissions. The hybrid slots 420, 430 may be divided into subbands to accommodate both UL and DL transmissions in the same slot. Each of the hybrid slots 420, 430 may be divided into multiple segments of consecutive symbols. Each section of consecutive symbols may be used for a DL subband, UL subband, or flexible subband. DL subbands may be reserved for DL transmission. UL subbands may be reserved for UL subbands. The flexible subbands may be used for DL transmission or UL transmission.

Hybrid slot 420 may include one or more DL subbands (e.g., such as DL subband 422 and DL subband 426) and one or more UL subbands (e.g., such as UL subband 424). The hybrid slot 430 may include one or more DL subbands (e.g., such as DL subband 432 and DL subband 436) and one or more UL subbands (e.g., such as UL subband 434). Operations based on SBFD slots may reduce implementation complexity in FD at least at the gNB. The WTRU may be configured and/or scheduled to transmit UL signals (e.g., PUSCH, PUCCH, SRS) over a first set of RBs (e.g., UL SBs) that may be adjacent to a second set of RBs (e.g., DL SBs) for DL reception by a second WTRU (e.g., may be in the vicinity of the WTRU). UL signals transmitted by the WTRU may cause WTRU-to-WTRU cross link (e.g., leakage) interference (e.g., such as CLI or CLLI) on a neighboring second set of RBs for DL reception by a second WTRU. When the gNB uses FD operation, one or more of the solutions discussed herein may be used to reduce dynamic CLI leakage in adjacent DL/UL subbands.

Fig. 4B depicts an example SBFD operation 450 based on Tx parameter adjustment. As shown in fig. 4B, in one example, at 452, the WTRU may receive an indication of one or more RBs (e.g., one or more reference RBs) that are used as references to determine FG. The one or more reference RBs may be the highest and/or lowest RBs of the first portion of DL RBs and the second portion of DL RBs. For example, ase:Sub>A first portion of the DL RBs may range from Ref RB-A to Ref RB-B, and ase:Sub>A second portion of the DL RBs may range from Ref RB-C to Ref RB-D. In an example, the second portion of the DL RB may be an example of a second RB to be compared to evaluate the conditions and/or criteria discussed herein, where the example may also be based on fig. 3. The indication may be received via RRC, MAC-CE, and/or DCI. In one example, the RRC may configure a set (e.g., for one or more RBs), and the MAC-CE and/or DCI may indicate one of the set.

At 456, the WTRU may receive an grant associated with transmission of the UL signal. For example, the grant may indicate one or more RBs (e.g., a set of RBs) for transmission of UL signals (e.g., in at least one mixed UL/DL symbol). At 458, the WTRU may determine FG as ase:Sub>A value between the UL grant (e.g., first or last) RB and the closest reference RB (e.g., ref RB-ase:Sub>A, ref RB-B, ref RB-C, or Ref RB-D), e.g., in response to receiving the grant. At 460, the WTRU may determine and/or adjust Tx parameters (e.g., MCS, link Adaptation (LA), and/or Power Control (PC) parameters) based on the determined FG value. The WTRU may reduce the transmit power and/or reduce the MCS value/level for transmission of UL signals scheduled by the grant if the FG value is less than a predefined or preconfigured threshold. The WTRU may apply multi-level MCS/PC/LA adjustment based on multiple thresholds (e.g., if multiple thresholds are configured). For example, the WTRU may apply a first adjustment when the FG value is less than a first threshold and the WTRU may apply a second adjustment when the FG value is less than the first and second thresholds. At 462, the WTRU may transmit an UL signal using the determined or adjusted Tx parameters (e.g., MCS, LA, and/or PC parameters).

The WTRU may be configured to determine a frequency gap associated with the UL signal based on one or more portions of the DL RB. For example, the UL signal may be between two parts of the DL RB. The WTRU may determine which portion of the DL RB the UL signal is closer to. The WTRU may identify one or more reference RBs in each portion of the DL RBs. The one or more reference RBs may be first and/or last RBs in the respective portion of the DL RBs.

Fig. 4C depicts example FG value determinations 470, 480. In a first example FG value determination 470, the UL signal 472 may be scheduled on a set of scheduled RBs under a first portion of DL RBs. For example, the set of RBs scheduled for UL signal 472 may be indicated via grants received by the WTRU. The first portion of the DL RBs may include ase:Sub>A first reference RB (e.g., ref RB-A) and ase:Sub>A second reference RB (e.g., ref RB-B). The first and second reference RBs may be first and last RBs in the first portion of the DL RB, respectively. The WTRU may determine that FG (e.g., between UL signal 472 and the first portion of DL RBs) is three RBs, which is the RB rank distance between the highest UL RB of the set of scheduled RBs allocated to UL signal 472 and Ref RB-ase:Sub>A.

In a second example FG value determination 480, UL signal 482 may be scheduled on a set of scheduling RBs between a first portion of DL RBs and a second portion of DL RBs. For example, the set of RBs scheduled for UL signal 482 may be indicated via grants received by the WTRU. The second portion of the DL RBs may include a first reference RB (e.g., ref RB-C) and a second reference RB (e.g., ref RB-D). The first and second reference RBs may be first and last RBs in the second portion of the DL RB, respectively. UL signal 482 may be closer to a second portion of DL RBs than to the first portion of DL RBs. The WTRU may determine that the FG is two RBs, which is the RB level distance between the highest UL RB of the scheduled RB set and Ref RB-C. UL signal 482 may be three or more RBs from the first portion of the DL RB.

As described herein, a WTRU may (be configured to) receive an uplink grant indicating a set of Resource Blocks (RBs) for UL transmissions sent over one or more symbols (e.g., at least one of the one or more symbols is a hybrid UL/DL symbol in BWP).

The WTRU may determine a value of FG between a first RB from the set of RBs for UL transmission and a second RB from the one or more reference RBs (e.g., in response to receiving an uplink grant). The WTRU may determine one or more transmission parameters (e.g., MCS, transmit power, and/or link adaptation parameters) based on the determined FG values. The WTRU may transmit UL transmissions using the determined transmission parameters.

In an example, the first RB may be a lowest or highest RB of the set of RBs for UL transmission, and the second RB may be a nearest RB to the first RB of the one or more reference RBs (and the FG value may be determined as an increment (e.g., difference, RB rank distance/difference, etc.) between them).

In an example, the second RB from the one or more reference RBs may be an RB for (or configured for) DL transmission in one or more of the symbols. The WTRU may also (be configured to) receive an explicit identification of one or more reference RBs (e.g., via RRC, MAC CE, and/or DCI).

Dynamic UL PC (e.g., for XDD) may be implemented. The WTRU may determine a transmission power (P) for the UL transmission based on one or more power control parameters, including one or more of the following, but not limited to: maximum transmission power (P _CMAX); nominal transmission power (P _O); path Loss (PL), e.g., measured from path loss RS; scaling factor (α) of PL; or closed loop power control parameters for time slots or symbols i (f (i)). The WTRU may determine the transmit power for PUSCH, PUCCH, and SRS transmissions in equations (1), (2), and (3), respectively.

/>

In an example, the transmission power for UL transmissions may be determined, for example, based on a Frequency Gap (FG) value. For example, if the FG value for the UL transmission is equal to or less than a threshold, the WTRU may determine a first transmission power for the UL transmission. For example, if the FG value for the UL transmission is greater than a threshold, the WTRU may determine a second transmission power for the UL transmission. One or more of the following may be applied: the WTRU may determine one or more power control parameters based on the FG values; the WTRU may determine one or more power control parameters based on the FG value and the presence of DL transmissions in DL resources (e.g., which may be used for FG value determination); or, for example, if the WTRU is instructed to do so, the WTRU may determine one or more power control parameters based on the FG value.

The WTRU may determine one or more power control parameters based on the FG values. In an example, the first P _CMAX value and/or the f (i) value may be used, for example, if the FG value for the UL transmission is equal to or less than a threshold. For example, if the FG value for UL transmission is greater than a threshold value, the second P _CMAX value and/or the f (i) value may be used, e.g., where the threshold value may be configured via (e.g., higher layer) signaling (e.g., RRC signaling and/or MAC-CE signaling) and/or indicated by dynamic signaling (e.g., MAC-CE signaling and/or DCI signaling). The first P _CMAX value may be determined based on the power level supported by the WTRU and the second P _CMAX value may be configured via signaling (e.g., higher layer signaling and/or dynamic signaling), or vice versa. The first f (i) value may be a (e.g., absolute) value configured via signaling (e.g., higher layer signaling and/or dynamic signaling), and the second f (i) value may be accumulated via TPC commands, or vice versa.

In an example, the WTRU may determine the set of power control parameters based on the FG value. For example, if the FG value is greater than a threshold, a subset of power control parameters may be used (e.g., configured and/or indicated), and if the FG value is equal to or less than the threshold, a second subset of power control parameters (e.g., a full set) may be used (e.g., configured and/or indicated), or vice versa. For example, if the FG value is equal to or less than a threshold value, a power offset parameter (e.g., poffset) may be part of the power control parameter, e.g., where the power offset value may be determined based on the FG value.

In an example, the WTRU may determine the set of power control parameters based on the FG value. For example, if the FG value is greater than a threshold value, the Tx power may be determined using a first set of power control parameters. For example, if the FG value is equal to or less than the threshold value, the Tx power may be determined using a second set of power control parameters.

The WTRU may determine one or more power control parameters based on the FG value and the presence of DL transmissions in DL resources (e.g., which may be used for FG value determination). For example, if no DL signal transmission is detected in DL resources that may be used for FG value determination, the WTRU may determine a transmission power without an FG value. Otherwise, the WTRU may determine the transmission power based on the FG value. The presence of DL signaling in the DL resource region may be indicated or signaled to the WTRU. For example, if the WTRU is scheduled for UL transmission, the WTRU may be indicated as being related to the presence of DL signaling in the DL resource region.

For example, if the WTRU is instructed to do so, the WTRU may determine one or more power control parameters based on the FG value. For example, the scheduled DCI for a UL transmission (e.g., PUSCH transmission, SRS transmission) may include an indication to determine whether to adjust the transmission power (e.g., based on FG values).

In an example, UL transmission power of UL frequency resources may be determined (e.g., based on FG values). For example, the UL transmission may include one or more frequency resources within a time slot, and each frequency resource (e.g., RB) may have its associated (e.g., respective) FG value. The WTRU may determine UL transmission power (e.g., first) without regard to FG values and the WTRU may scale (e.g., using a scaling factor) the transmission power of each frequency resource based on its associated FG value. For example, a scaling factor for the frequency resource may be determined from its associated FG value. For example, the scaling factor may be '1' for frequency resources that may have their associated FG value greater than a threshold. For example, the scaling factor may be less than '1' for frequency resources that may have their associated FG value less than a threshold.

In an example, if one or more of the above conditions and/or criteria as described herein are met (e.g., based on frequency gaps, spatial domain separation, and/or priority indication, etc.), the WTRU may (e.g., configured and/or indicated as) apply one or more of the following dynamic UL PC operations (e.g., for XDD operations): dynamic UL PC adjustment; multiple UL PC loops for XDD; or enhanced Power Headroom Report (PHR).

The WTRU may apply dynamic UL PC adjustment. The dynamic UL PC adjustment may be a direct UL PC adjustment to the UL PC equation/formula, e.g., the power reduction coefficient/parameter may be added to existing PC terms (e.g., open loop PC parameters) of one or more of P0 (e.g., as nominal power), path loss terms (e.g., based on PL RS), α (e.g., as ratio parameters for PL), etc. Dynamic UL PC adjustment may involve applying additional offsets on the current UL PC calculation. Applying the additional offset on the current UL PC calculation may include, for example, introducing an additional power reduction term in the UL PC equation, directly reducing P _MAX (e.g., associated with applying P-MPR), where P _MAX (e.g., P _CMAX) is the maximum (e.g., allowable) transmission power for the WTRU, and/or an explicit power reduction offset parameter may be applied after UL PC calculation is complete.

The WTRU may apply multiple UL PC loops for XDD. One or more of the following UL PC loops may be configured for WTRU maintenance/application/update: UL PC loops (e.g., l=0) for non-XDD slots/symbols (e.g., the loops may be the same as legacy (e.g., may share legacy CLPCs)); UL PC loops (e.g., l=1) for XDD slots/symbols with a first set/combination (e.g., satisfied) of conditions, UL PC loops (e.g., l=2) for XDD slots/symbols with a second set/combination (e.g., satisfied) of conditions, UL PC loops (e.g., l=3) for XDD slots/symbols with a third set/combination (e.g., satisfied) of conditions, and so forth.

In an example, the UL PC loop may correspond to (e.g., be associated with) a separate closed loop PC parameter (e.g., a different value of l in the UL PC equation/formula).

In an example, the first set of conditions may involve determining that a distance between the UL and DL subbands is short (< RB), e.g., as in the above-described conditions and/or criteria when the frequency gap is below a first threshold (e.g., as described herein). In an example, the second set of conditions may involve determining that a distance between UL and DL subbands is large (r) RB and that a spatial domain separation between a first beam configuration for UL subbands and a second beam configuration for DL subbands is below a threshold, as in the above conditions (e.g., as described herein).

The WTRU may determine an enhanced Power Headroom Report (PHR). The Power Headroom (PH) may be calculated, derived, estimated or determined by (e.g., XDD) slot/symbol type and/or one or more conditions and/or criteria (e.g., as described herein), e.g., for PH type 0, PH type 1, PH type 2, etc. The PH type 0 may be the same as a conventional PH, e.g., calculated based on P _MAX–P_PUSCH, without taking any possible XDD operation. In examples, the WTRU may (e.g., be configured and/or indicated as) report (e.g., based on a value of P _offsetXDD1) a different information content/value than PH _type0 only, for example, based on P _MAX–P_PUSCH2 (e.g., where P _PUSCH2 may include one or more power reduction parameters/items) or based on P _MAX–P_PUSCH–P_offsetXDD2, PH type 2 for the XDD slot and when a second set/combination of conditions is met.

For example, one or more PHR types may be used, where each PHR type may be associated with a PH type. For example, the first PHR type may correspond to a first PH type report; the second PHR type may correspond to a second PH type report; and so on. The WTRU may trigger the PHR, for example, based on one or more PHR conditions. The one or more PHR conditions may be determined, for example, based on the PHR type. The first set of PHR conditions may be configured, used, or determined for a first PHR type and the second set of PHR conditions may be configured, used, or determined for a second PHR type. The set of PHR conditions may include one or more of the following: periodicity (e.g., expiration of a timer), a threshold of PL gaps (e.g., PL value change since last PHR transmission), a threshold of power backoff, or a threshold of P-MPR. (e.g., each) PHR condition/parameter may be configured (e.g., independently) or determined for a set of PHR conditions. For example, a set of PHR conditions may be used (e.g., collectively) regardless of PHR type. One or more PHR conditions/parameters may be configured (e.g., independently) for the PHR type.

The WTRU may be instructed to report a set of PHR types, e.g., if a trigger condition is met for one or more PHR types within the set of PHR types. For example, if the set of PHR types includes a first PHR type and a second PHR type and a trigger condition for the first PHR type is satisfied, the WTRU may trigger PHR for the first PHR type and the second PHR type (e.g., even if the second PHR type does not satisfy the trigger condition). The set may be configured via (e.g., higher layer) signaling (e.g., via RRC signaling). The set may be determined based on XDD-related configuration information (e.g., tdd-UL-DL-config-Common/Dedicated for XDD, non-XDD slot/symbol types, XDD slot/symbol types (e.g., including mixed UL/DL slot/symbol types), the above conditions as described herein, such as for frequency gaps and/or for spatial domain separation, etc.). For example, if a trigger condition for a second PHR type or a third PHR type is satisfied, the set of PHR types may include the first PHR type by default (e.g., automatically) (e.g., for a legacy PH type 0). The WTRU may trigger the set of PHR types, e.g., based on a dynamic indication. For example, the network (e.g., the gNB) may indicate (e.g., via DCI) to report one or more PHR types, where the indication may include which PHR types to report and uplink resource information associated with the triggered PHR.

Dynamic MCS adjustment (e.g., for XDD) may be performed. Table 2 shows an example MCS index table for DL, e.g., that may be shared/reused for UL cases (e.g., and in some cases may be restricted for UL, e.g., PUSCH with transform precoding).

Table 2: example MCS index table for DL

In an example, if one or more of the above conditions and/or criteria are met (e.g., related to frequency gaps, spatial domain separation, priority indication, etc., as described herein), the WTRU may apply (e.g., be configured and/or indicated as) one or more of the following dynamic MCS adjustment methods (e.g., for XDD operation). Such MCS adjustment may be applicable to PDSCH transmissions that are at least dynamically or semi-permanently scheduled, or PUSCH transmissions that are dynamically or scheduled with configured grants, or repetitions thereof.

General actions for dynamic MCS adjustment may be performed. If one or more of the above conditions and/or criteria are met, the WTRU may apply a second MCS (e.g., instead of applying the first MCS for UL (or DL) resource scheduling, configuration, and/or indication), e.g., where the second MCS may have a J-level MCS difference compared to the first MCS. The information related to J may be preconfigured, predetermined, and/or indicated (e.g., from the network/gNB) to the WTRU. In an example, the first MCS may be an MCS Index (IMCS) of 7 (e.g., a modulation order qm=2 with a spectral efficiency of 1.0273). The WTRU may be configured and/or indicated with j=2. For example, in response to determining that one or more of the above conditions and/or criteria are met (e.g., as described herein), the WTRU may apply the second MCS as an MCS Index (IMCS) of 5 (=7-J) for transmitting UL resources or for receiving DL resources. The WTRU may apply a second MCS set to the lowest possible MCS index of the MCS index table, e.g., if the second MCS becomes out of range (e.g., below the lowest index of the MCS index table).

Multiple levels of dynamic MCS adjustment may be performed. The WTRU may be configured with multiple values and/or parameters of J. In an example, the WTRU may be configured with J1, J2, etc. (e.g., as a plurality of candidate MCS adjustment values/parameters), e.g., to apply multi-level dynamic MCS adjustment. In an example, J1 may be 2, and J2 may be 4, and so on. If one or more of the above conditions and/or criteria are met (e.g., as described herein), the WTRU may apply a second MCS or a third MCS, etc. (e.g., instead of applying the first MCS for UL or DL resource scheduling, configuration, and/or indication), e.g., where the second MCS may have a J1 level MCS difference compared to the first MCS and the third MCS may have a J2 level MCS difference compared to the first MCS, and so on.

In an example, the first MCS may be an MCS Index (IMCS) of 7 (e.g., a modulation order qm=2 with a spectral efficiency of 1.0273). For example, in response to determining that one or more of the above conditions and/or criteria are met to meet a first set of conditions and/or criteria based on a first threshold, the WTRU may apply the second MCS as an MCS Index (IMCS) of 5 (=7-J1, such as j1=2) (e.g., for transmitting UL resources or for receiving DL resources).

In an example, the first MCS may be an MCS Index (IMCS) of 7 (e.g., a modulation order qm=2 with a spectral efficiency of 1.0273). For example, in response to determining that one or more of the above conditions and/or criteria are met to meet a second set of conditions and/or criteria based on a second threshold, the WTRU may apply a third MCS as an MCS Index (IMCS) of 3 (=7-J2, such as j2=4) for transmitting UL resources or for receiving DL resources.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on one or more of the following: indicated MCS, indicated/determined SRS Resource Indicator (SRI) or TCI status, priority indicator, UL/SUL indicator, BWP/carrier indicator, resource allocation type, open loop power control parameter set, PDSCH/PUSCH mapping type, etc.

The first set of conditions and/or criteria may be based on the indicated MCS. For example, if the indicated MCS is below (or equal to) the threshold, the WTRU may apply a second MCS. The WTRU may apply a third MCS if the indicated MCS is above a threshold.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on an indicated/determined SRS Resource Indicator (SRI) or TCI status. The WTRU may receive an association (e.g., association information) between the SRI/TCI state and the MCS adjustment value (e.g., J1, J2, etc.), e.g., via one or more of MAC CE signaling or RRC signaling. For example, a first SRI/TCI state may be associated with a first MCS adjustment value (e.g., J1) and a second SRI/TCI state may be associated with a second MCS adjustment value (e.g., J2). The WTRU may determine the second MCS or the third MCS based on the association, for example. For example, if the WTRU receives an indication of the first SRI/TCI state or determines the first SRI/TCI state for PDSCH/PUSCH, the WTRU may determine to use the second MCS based on J1. If the WTRU receives an indication of the second SRI/TCI state, for example, or determines the second SRI/TCI state for PDSCH/PUSCH, the WTRU may determine to use a third MCS based on J2,

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on a priority indicator. The WTRU may receive an association (e.g., association information) between the priority and MCS adjustment values (e.g., J1, J2, etc.), e.g., via one or more of MAC CE signaling or RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a lower priority and a second MCS adjustment value (e.g., J2) for a higher priority.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on UL/SUL indicators. The WTRU may receive the association between the UL/SUL and the MCS adjustment value (e.g., J1, J2, etc.), e.g., via one or more of MAC CE signaling or RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a (e.g., non-supplemental) UL and a second MCS adjustment value (e.g., J2) for a Supplemental UL (SUL).

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on BWP/carrier indicators. The WTRU may receive an association (e.g., association information) between the BWP/cell and the MCS adjustment value (e.g., J1, J2, etc.), e.g., via one or more of MAC CE signaling or RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a first BWP/cell and a second MCS adjustment value (e.g., J2) for a second BWP/cell.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on a resource allocation type (e.g., resource allocation types 0 and 1). The WTRU may receive an association between the resource allocation type and the MCS adjustment value (e.g., J1, J2, etc.), for example, via one or more of MAC CE signaling and RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a first resource allocation type and a second MCS adjustment value (e.g., J2) for a second resource allocation type.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on an open loop power control parameter set. The WTRU may receive an association between the open loop power control parameter set and MCS adjustment values (e.g., J1, J2, etc.), for example, via one or more of MAC CE signaling or RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a first open loop power control parameter set and a second MCS adjustment value (e.g., J2) for a second open loop power control parameter set.

The first set of conditions and/or criteria and the second set of conditions and/or criteria may be based on PDSCH/PUSCH mapping types. The WTRU may receive an association (e.g., association information) between the PDSCH/PUSCH mapping type and the MCS adjustment value (e.g., J1, J2, etc.), e.g., via one or more of MAC CE signaling or RRC signaling. For example, the WTRU may receive a first MCS adjustment value (e.g., J1) for a first PDSCH/PUSCH mapping type (e.g., PDSCH/PUSCH mapping type a) and a second MCS adjustment value (e.g., J2) for a second PDSCH/PUSCH mapping type (e.g., PDSCH/PUSCH mapping type B).

Joint UL PC and MCS adjustment actions may be performed. The WTRU may apply (e.g., be configured and/or instruct/switch to) one or more of the following (e.g., joint UL PC and MCS adjustment) actions, e.g., each defined/configured as a separate mode of operation: mode 1, mode 2 or mode 3. In an example, mode 1 may include UL Tx power adjustment (e.g., based on one or more of the dynamic UL PC methods described above) without any MCS adjustment (e.g., only).

In an example, mode 2 may include (e.g., a level one) WTRU-initiated MCS adjustment, e.g., based on certain conditions (e.g., depending on which dynamic UL PC reduction is applied). The threshold M (e.g., in dB) for WTRU-initiated MCS adjustment may be predefined, configured, or indicated to the WTRU. The WTRU may apply predefined, preconfigured, and/or indicated dynamic MCS adjustment/reduction (e.g., a Y-level MCS reduced from the scheduling, configuration, and/or indicated MCS level for UL resources) and transmit UL resources with the applied MCS reduction, e.g., if an XdB dynamic UL PC reduction (e.g., where x+.m) is applied to the transmission of UL resources (e.g., based on one or more of the dynamic UL PC methods described above). In an example, if y=1, the MCS index for scheduling, configuring and/or indicating UL resources may be adjusted to be the MCS index-Y (=1) for scheduling, configuring and/or indicating. For example, if the scheduled, configured, and/or indicated MCS index-Y (=1) becomes out of range (e.g., below the lowest index), the WTRU may apply the adjusted MCS index as the lowest MCS index.

In an example, mode 3 may include multi-level WTRU-initiated MCS adjustment, e.g., based on a particular set of conditions (e.g., depending on which dynamic UL PC reduction is applied). One or more thresholds (e.g., M1, M2, …, in dB) for multi-level WTRU-initiated MCS adjustment may be predefined, configured, or indicated to the WTRU. The WTRU may determine whether the calculated XdB belongs to which interval of the multi-level MCS adjustment, e.g., if an X dB dynamic UL PC reduction is applied to transmission of UL resources (e.g., based on one or more of the dynamic UL PC methods described above). In an example, if X > M1, X may belong to a first interval for multi-level MCS adjustment. The WTRU (e.g., if X > M1) may apply a Y1 level MCS that is reduced from the scheduling, configuration, and/or indicated MCS level for the UL resources, e.g., the adjusted MCS index may be the scheduling, configuration, and/or indicated MCS index-Y1. In an example, if M2< X+.m1, then X may belong to the second interval for multi-level MCS adjustment. The WTRU (e.g., if M2< x+.m1) may apply a Y2 level MCS that is reduced from the scheduling, configuration and/or indicated MCS level for UL resources, e.g., the adjusted MCS index may be the scheduling, configuration and/or indicated MCS index-Y2. In an example, if X+.m2, then X may belong to a third interval for multi-level MCS adjustment. The WTRU (e.g., if x+.m2) may apply a Y3 level MCS that is reduced from the scheduling, configuration and/or indicated MCS level for the UL resources, e.g., the adjusted MCS index may be the scheduling, configuration and/or indicated MCS index-Y3.

In an example, each value of Y1, Y2, Y3, etc. may be predefined, preconfigured, and/or indicated for each interval (e.g., first interval, second interval, or third interval, etc.), e.g., for a multi-level dynamic MCS reduction. If the scheduled, configured, and/or indicated MCS index-Yk becomes out of range (e.g., below the lowest index), the WTRU may apply the adjusted MCS index as the lowest MCS index.

The WTRU may provide feedback and/or reports, for example, regarding MCS adjustments. Based on (e.g., after) or after receiving the configured, scheduled, and/or indicated UL resources, the WTRU may provide feedback and/or reports regarding the applied WTRU-initiated MCS adjustment to the network (e.g., the gNB), for example, by applying the WTRU-initiated MCS adjustment (e.g., by following general behavior for dynamic MCS adjustment, by applying multi-level dynamic MCS adjustment, by mode 2 as one-level joint adjustment, and/or mode 3 as multi-level joint adjustment, etc.). Feedback/reporting regarding the applied WTRU-initiated MCS adjustment may be transmitted, for example, based on applying one or more of the following: transmitting on non-XDD slots/symbols (e.g., only) (e.g., which may benefit robustness of WTRU feedback) or regardless of XDD/non-XDD slot/symbol type; periodic reports, semi-persistent reports, or non-periodic reports; etc.

Feedback/reports regarding applied WTRU-initiated MCS adjustments may be transmitted on non-XDD slots/symbols (e.g., only), or regardless of XDD/non-XDD slot/symbol type. In an example, the transmission instance may be indicated (e.g., explicitly) by the network (e.g., the gNB). The transmission instance may be (e.g., implicitly) determined to be, for example, the earliest possible non-XDD slot/symbol (e.g., at least after a time offset value). For example, the time offset value may be configured, indicated, and/or determined based on the reported WTRU capability value associated with the time offset.

In an example, the WTRU feedback/reporting may be configured as periodic (e.g., UCI-like) reporting, semi-persistent (e.g., UCI-like) reporting, or aperiodic (e.g., UCI-like) reporting, e.g., based on configured and/or indicated periodicity and/or offset parameters for WTRU feedback/reporting transmissions and/or information about RBs.

In an example, based on WTRU feedback and/or reporting (e.g., later) regarding the applied WTRU-initiated MCS adjustment, the network (e.g., the gNB) may indicate and/or update to the WTRU one or more parameters and/or values (e.g., adjustment step sizes (e.g., Y, Y, Y2, Y3, etc.)) and/or thresholds (e.g., M, M1, M2, M3, etc.), e.g., to determine which interval to apply which step size to the WTRU-initiated MCS adjustment, etc.

Although the above features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements.

While the implementations described herein may consider 3GPP specific protocols, it should be appreciated that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein consider LTE, LTE-a, new Radio (NR), or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario, and are applicable to other wireless systems as well.

The processes described above may be implemented in computer programs, 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 a wired or wireless connection) and/or computer readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, internal hard disks and removable disks), magneto-optical media, and optical media (such as Compact Disks (CD) -ROM disks, and/or Digital Versatile Disks (DVD)). A processor associated with the software may be used to implement a radio frequency transceiver for the WTRU, the terminal, the base station, the RNC, and/or any host computer.

Claims (20)

1. A wireless transmit/receive unit (WTRU), the WTRU comprising:

a processor configured to:

Receiving an grant associated with transmission of an Uplink (UL) signal, wherein the grant indicates a first set of Resource Blocks (RBs);

Determining a Frequency Gap (FG) between the first set of RBs and a reference RB;

adjusting one or more transmission (Tx) parameters based on the determined FG, wherein when the determined FG is less than a predefined threshold, configured to adjust the one or more Tx parameters includes one or more of a Modulation Coding Scheme (MCS) level configured to reduce a transmit power or associated with transmission of the UL signal scheduled by the grant; and

The UL signal is transmitted using the adjusted one or more Tx parameters.

2. The WTRU of claim 1, wherein the UL signal transmission is sent over one or more symbols, and wherein at least one of the one or more symbols is a hybrid UL/Downlink (DL) symbol in a portion of bandwidth.

3. The WTRU of claim 1 wherein the reference RB used to determine the FG is a reference RB closest to the first set of RBs.

4. The WTRU of claim 4, wherein the first set of RBs is between a second set of RBs and a third set of RBs, and wherein the second set of RBs includes the reference RBs when the first set of RBs is closer to the second set of RBs than to the third set of RBs, and wherein the third set of RBs includes the reference RBs when the first set of RBs is closer to the third set of RBs than to the second set of RBs.

5. The WTRU of claim 1 wherein the frequency gap is a frequency difference between the first set of RBs and the reference RB.

6. The WTRU of claim 1 wherein the reference RB is configured for Downlink (DL) transmission.

7. The WTRU of claim 1, further comprising receiving an indication of one or more reference RBs to be used in determining the FG, wherein the one or more reference RBs comprise the reference RB.

8. The WTRU of claim 1, wherein the predetermined threshold is a first predetermined threshold, and wherein the processor is configured to:

When the FG is less than the first predetermined threshold and greater than a second predetermined threshold, adjust a first Tx parameter of the one or more Tx parameters, an

When the FG is less than the first predetermined threshold and less than the second predetermined threshold, a second Tx parameter of the one or more Tx parameters is adjusted.

9. The WTRU of claim 8, wherein the first predetermined threshold is 2 resource blocks and the second predetermined threshold is 5 resource blocks.

10. The WTRU of claim 8, wherein the processor is further configured to:

Determining a spatial domain separation between a first beam associated with the transmission of the UL signal and a second beam associated with a downlink transmission;

determining a priority level associated with the transmission of the UL signal; and

One or more Tx parameters are adjusted based on one or more of the spatial domain separation or the priority level associated with the transmission of the UL signal.

11. A method performed by a wireless transmit/receive unit (WTRU), the method comprising:

Receiving an grant associated with transmission of an Uplink (UL) signal, wherein the grant indicates a first set of Resource Blocks (RBs);

Determining a Frequency Gap (FG) between the first set of RBs and a reference RB;

Adjusting one or more transmission (Tx) parameters based on the determined FG, wherein adjusting the one or more Tx parameters includes one or more of reducing a transmit power or a Modulation Coding Scheme (MCS) level associated with transmission of the UL signal scheduled by the grant when the determined FG is less than a predefined threshold; and

The UL signal is transmitted using the adjusted one or more Tx parameters.

12. The method of claim 11, wherein the UL signal transmission is transmitted over one or more symbols, and wherein at least one of the one or more symbols is a hybrid UL/Downlink (DL) symbol in a bandwidth portion.

13. The method of claim 11, wherein the reference RB used to determine the FG is a reference RB closest to the first set of RBs.

14. The method of claim 13, wherein the first set of RBs is between a second set of RBs and a third set of RBs, and wherein the second set of RBs comprises the reference RBs when the first set of RBs is closer to the second set of RBs than to the third set of RBs, and wherein the third set of RBs comprises the reference RBs when the first set of RBs is closer to the third set of RBs than to the second set of RBs.

15. The method of claim 1, wherein the frequency gap is a frequency difference between the first set of RBs and the reference RB.

16. The method of claim 11, wherein the reference RB is configured for Downlink (DL) transmission.

17. The method of claim 11, further comprising receiving an indication of one or more reference RBs to be used in determining the FG, wherein the one or more reference RBs comprise the reference RB.

18. The method of claim 11, wherein the predetermined threshold is a first predetermined threshold, and wherein the method further comprises:

When the FG is less than the first predetermined threshold and greater than a second predetermined threshold, adjust a first Tx parameter of the one or more Tx parameters, an

When the FG is less than the first predetermined threshold and less than the second predetermined threshold, a second Tx parameter of the one or more Tx parameters is adjusted.

19. The method of claim 18, wherein the first predetermined threshold is 2 resource blocks and the second predetermined threshold is 5 resource blocks.

20. The method of claim 18, further comprising:

Determining a spatial domain separation between a first beam associated with the transmission of the UL signal and a second beam associated with a downlink transmission;

determining a priority level associated with the transmission of the UL signal; and

One or more Tx parameters are adjusted based on one or more of the spatial domain separation or the priority level associated with the transmission of the UL signal.