Latency and coverage extension for sub-band non-overlapping full duplex

Abstract

A wireless transmit / receive unit (WTRU) may receive subband non-overlapping full duplex (SBFD) configuration information. The SBFD configuration information may be associated with subbands for uplink transmission and subbands for downlink reception. The WTRU may receive scheduling information associated with a physical uplink shared channel (PUSCH) transmission. The scheduling information may include a first frequency domain resource allocation (FDRA). The WTRU may send a first PUSCH transmission using a first frequency resource. The WTRU may determine that at least a second PUSCH transmission should be sent using at least one OFDM symbol. The WTRU may determine that the first frequency resource overlaps. The WTRU may receive one or more of a second FDRA or a frequency offset for the second PUSCH transmission. The WTRU may determine a second frequency resource for sending the second PUSCH transmission. The WTRU may send the second PUSCH transmission using the second frequency resource.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 410,947, filed September 28, 2022, the contents of which are incorporated herein by reference in their entirety. [Background technology]

[0002] The present disclosure relates to devices, methods, and systems for latency and coverage extension for subband non-overlapping full duplex (SBFD). Summary of the Invention

[0003] A wireless transmit / receive unit (WTRU) may receive subband non-overlapping full duplex (SBFD) configuration information. The SBFD configuration information may indicate one or more orthogonal frequency division multiplexing (OFDM) symbols associated with one or more subbands for uplink transmission and one or more subbands for downlink reception. The WTRU may receive scheduling information associated with multiple physical uplink shared channel (PUSCH) transmissions. The scheduling information may include a first frequency domain resource allocation (FDRA). The WTRU may send a first PUSCH transmission of the multiple PUSCH transmissions using a first frequency resource determined based on the first FDRA. The WTRU may determine that a second PUSCH transmission of the at least multiple PUSCH transmissions should be sent using at least one OFDM symbol of the one or more OFDM symbols. The WTRU may determine, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in one or more subbands for downlink reception of the at least one OFDM symbol. The WTRU may receive one or more of the second FDRA or frequency offset for the second PUSCH transmission. The WTRU may determine a second frequency resource for sending the second PUSCH transmission based on the one or more of the second FDRA or frequency offset. The second frequency resource may be included in one or more subbands for uplink transmission of the at least one OFDM symbol. The WTRU may send the second PUSCH transmission using the second frequency resource.

[0004] The WTRU may determine that the first frequency resource is at least partially included in one or more subbands for uplink transmission. The WTRU may receive a second FDRA or frequency offset in scheduling information. The scheduling information may include downlink control information. The WTRU may receive the second FDRA or frequency offset in a medium access control (MAC) control element (CE), a radio resource control (RRC) configuration, or the downlink control information. The WTRU may send the first PUSCH transmission using a time division duplex (TDD) configuration.

[0005] The WTRU may determine the start of the second PUSCH transmission based on the starting resource block (RB) of the SBFD or the starting RB of the second FDRA. The WTRU may determine the second FDRA from the indication or SBFD configuration information. The WTRU may determine the second FDRA from the first FDRA by applying a frequency offset. The frequency offset may be a resource block (RB) offset.

[0006] The frequency offset may be configured or indicated using a medium access control (MAC) control element (CE) or downlink control information (DCI). The frequency offset may be included in the indication or configuration. The SBFD configuration information may indicate PUSCH repetition or a transport block (TB) over multiple slots (TBoMS). The WTRU may determine the type of slot for the PUSCH transmission. The slot type may be SBFD or non-SBFD. The WTRU may determine the number of available slots. Determining the number of available slots may include one or more of determining that non-SBFD uplink transmission slots are available and determining that SBFD slots are available only if the second FDRA is within one or more subbands for the uplink transmission.

[0007] The WTRU may determine a first FDRA and a second FDRA for non-SBFD and SBFD slots. The first FDRA and the second FDRA may use frequency resources or physical resource block (PRB) resources. The WTRU may use the first FDRA for non-SBFD slots and the second FDRA for SBFD slots. The WTRU may use the first FDRA and a frequency offset to determine a second frequency resource for sending a second PUSCH transmission. The WTRU may use separate frequency resources for the SBFD and non-SBFD slots based on the first FDRA.

[0008] A WTRU may receive physical uplink control channel (PUCCH) configuration information. The WTRU may receive SBFD configuration information. The SBFD configuration information may indicate one or more orthogonal frequency division multiplexing (OFDM) symbols associated with one or more subbands for uplink transmission and one or more subbands for downlink reception. The WTRU may receive DCI including a first PRI. The WTRU may determine that the PUCCH transmission indicated by the DCI should be sent using at least one or more OFDM symbols associated with the set of one or more subbands for uplink transmission and the set of one or more subbands for downlink reception indicated by the SBFD configuration information. The WTRU may determine, based on a first rule interpreting the first PRI and the PUCCH configuration information, that the first PUCCH resource indicated by the first PRI is included in at least one frequency resource that is at least partially included in one subband of the set of one or more subbands for uplink transmission and / or at least one subband of the set of one or more subbands for downlink reception indicated by the SBFD configuration information. The WTRU may determine a second PUCCH resource in response to determining that the first PUCCH resource indicated by the first PRI is included in at least one frequency resource that is at least partially included in one subband of the set of one or more subbands for uplink transmission and / or at least one subband of the set of one or more subbands for downlink reception indicated by the SBFD configuration information. The second PUCCH resource may be determined based on a second rule for interpreting the first PRI and the PUCCH configuration information. The second PUCCH resource may be within the set of one or more subbands for uplink transmission indicated by the SBFD configuration information. The WTRU may send the PUCCH transmission using the second frequency resource.

[0009] The second rule may include applying a frequency offset to the first PUCCH resource. The second rule may include applying a different mapping for the first PRI to PUCCH resources for transmissions associated with the SFBD configuration information and the first PRI. The second rule may map the first PRI to a second PRI. The second PRI may be used to determine a second PUCCH resource. The second PRI may be used for SBFD uplink transmissions based on its association with a non-SBFD PRI.

[0010] The second PUCCH resource may be within a slot symbol. The PUCCH configuration information may include a transmission repetition count. The PUCCH may be transmitted using Frequency Domain Resource Allocation (FDRA). The DCI may indicate that the first PRI is for a HARQ-ACK transmission. Determining the second PUCCH resource may include re-indexing the PUCCH resource. The transmission of the PUCCH transmission may be in a time unit configured for SBFD.

[0011] Discussed herein are devices, methods, and systems for latency and coverage extension for subband non-overlapping full duplex. In one or more implementations, a WTRU may receive an indication and / or configuration instructing it to transmit on multiple PUSCH resources (e.g., repetition of a transport block among multiple transport blocks and / or repetition of multiple PUSCH transmissions). In one or more implementations, the WTRU may determine a type (e.g., UL, flexible, and / or SBFD) of each PUSCH resource of the multiple PUSCH resources and may transmit the PUSCH resource in each PUSCH using a first FDRA and / or a second FDRA based on the respective type of each PUSCH resource. In one or more implementations, based on the instruction and / or configuration, the WTRU may determine a second PUSCH resource for the second PUSCH transmission, where the second PUSCH resource is within a time unit and / or time unit (e.g., slot, symbol) of a second type (e.g., SBFD), and may transmit the second PUSCH in the second PUSCH resource using a second FDRA, for example, because the second PUSCH resource is of the second type. [Brief explanation of the drawings]

[0012] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements and in which: [Figure 1A] 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 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. [Figure 1C] 1B 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. [Figure 1D]FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system shown in FIG. 1A. [Figure 2] This is an example of subband non-overlapping full duplex (SBFD). [Figure 3] 10 is an example of different K1 values ​​for an exemplary slot configuration DDDDU time division duplex (TDD). [Figure 4] An example of PUCCH formats 3 and 4 will be illustrated. [Figure 5] 1 is an example PUCCH configured at an example downlink (DL) time instance with an example configured SBFD. [Figure 6] 1 is an exemplary PUSCH repetition in the presence of exemplary SBFD. [Figure 7] This is another example of SBFD. DETAILED DESCRIPTION OF THE INVENTION

[0013] 1A is a 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, messaging, broadcasts, etc., to multiple wireless users. Communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the 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 DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), etc.

[0014] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RANs 104 / 113, CNs 106 / 115, public switched telephone network (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 WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and / or "STA," may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., for remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in an industrial and / or automated processing chain context), a consumer electronics device, a device operating on a commercial wireless network and / or an industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a WTRU.

[0015] The communications system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communications networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNodeB, a Home Node B, a Home eNodeB, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each depicted as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0018] More specifically, as noted above, the communications system 100 may be a multiple-access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communications protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

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

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

[0021] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access, e.g., using the principle of dual connectivity (DC). 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).

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

[0023] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one 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 establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 through the CN 106 / 115.

[0024] The RAN 104 / 113 may communicate with the CN 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, 102d. The data may have various quality of service (QoS) requirements, such as different throughput, latency, error tolerance, reliability, data throughput, and mobility requirements. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A , it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, the CN 106 / 115, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0025] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, which use common communication protocols such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The 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 RAN 104 / 113 or a different RAT.

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

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

[0028] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0031] The transceiver 120 may be configured to modulate signals 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. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

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

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

[0034] 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 instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) 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 will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0035] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a direction sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0036] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both the UL (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and or substantially eliminating self-interference either through hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for transmission and reception of either some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or downlink (e.g., for reception)).

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

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

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

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

[0041] The MME 162 may be connected to each of the eNodeBs 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 users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies such as GSM and / or WCDMA.

[0042] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions such as anchoring the user plane during inter-eNodeB handovers, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

[0044] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices. For example, the CN 106 may include or 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. Additionally, 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.

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

[0046] In a representative embodiment, the other network 112 may be a WLAN.

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

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

[0049] High Throughput (HT) STAs may use 40 MHz wide channels for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0050] A Very High Throughput (VHT) STA may support channels of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz width. A 40 MHz and / or 80 MHz channel may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may separate the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the 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 the Medium Access Control (MAC).

[0051] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communications, such as MTC devices, within a macro coverage area. MTC devices may have limited capabilities, including, for example, support for (e.g., only support for) certain specific and / or limited bandwidths. MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0052] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be configured and / or limited by the STAs among all STAs operating in the BSS that support the minimum bandwidth operating mode. In an 802.11ah embodiment, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) configuration can depend on the status of the primary channel. For example, if the primary channel is busy due to a STA (that only supports 1 MHz operating mode) transmitting to the AP, the entire available frequency band may be considered busy, even though most of the frequency band may remain idle and be available for use.

[0053] In the United States, the available frequency band that can be used by 802.11ah is 902MHz to 928MHz. In South 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 country regulations.

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

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

[0056] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0057] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed spectrum. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with a gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as an eNodeB 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement a DC principle 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 eNodeBs 160a, 160b, 160c may act 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, 102c.

[0058] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D , the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0059] 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 is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an organization other than the operator of the CN.

[0060] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

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

[0062] The 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 packet-switched networks such as the Internet 110 to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policy, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0063] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. Additionally, 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 be connected to 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.

[0064] 1A-1D and the corresponding descriptions thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-ab, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0065] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may use terrestrial wireless communication to perform the tests.

[0066] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0067] The following abbreviations and acronyms, among others, are used herein: Subcarrier Spacing (Δf), NR Node B (gNB), Aperiodic (AP), Beam Failure Recovery (BFR), Beam Failure Detection-Reference Signal (BFD-RS), Block Error Rate (BLER), Bandwidth Part (BWP), Carrier Aggregation (CA), Contention-Based (CB) (e.g., access, channel, resource), Clear Channel Assessment (CCA), Code Division Multiplexing (CDM), Cell Group (CG), Cross Layer Interference (CLI), Coordinated Multi-Point transmission / reception (CoMP), Channel Occupancy Time (COT), Cyclic Prefix (CP). Prefix (CP), Common Phase Error (CPE), Conventional OFDM (relying on cyclic prefix) (CP-OFDM), Channel Quality Indicator (CQI), Core Network (e.g., LTE Packet Core or NR Core) (CN), Cyclic Redundancy Check (CRC), Channel State Information (CSI), Channel State Information-Reference Signal (CSI-RS), Central Unit (CU), Device to Device TransmissionD2D (e.g., LTE sidelink), Dual Connectivity (DC), Downlink Control Information (DCI), Downlink (DL), Demodulation Reference Signal (DM-RS), Data Radio Bearer (DRB), Distributed Unit (DU), E-UTRA-NR Dual Connectivity (EN-DC), Evolved Packet Core (EPC), Frequency Domain-Code Division Multiplexing (FD-CDM), Frequency Division Duplexing (FDD), Frequency Division Multiplexing (FDM), Inter-Cell Interference (ICI), Inter-Cell Interference Cancellation (ICIC), Internet Protocol (IP) Protocol (IP), Listen-Before-Talk (LBT), Logical Channel (LCH), Logical Channel Identity (LCID), Logical Channel Prioritization (LCP), Low Latency Communication (LLC), e.g., Long Term Evolution (LTE) from 3GPP LTE R8 onwards, Medium Access Control (MAC), Medium Access Control Element (MAC CE), Negative ACK (NACK), Multimedia Broadcast Multicast SystemSystem (MBMS), Master Cell Group (MCG), Modulation and Coding Scheme (MCS), Multiple Input Multiple Output (MIMO), Machine-Type Communication (MTC), Multi-RAT Dual Connectivity (MR-DC), Non-Access Stratum (NAS), New candidate beam-Reference Signal (NCB-RS), NR-RAN-E-UTRA Dual Connectivity (NE-DC), Dual Connectivity with New Radio (NR), Orthogonal Cover Code (OCC), Orthogonal Frequency-Division Multiplexing (ORD) Multiplexing, OFDM), Out-Of-Band (OOB) (radiated), total available WTRU power in a given transmission interval (P cmax), Primary cell of a Master Cell Group (Pcell), Primary Cell Group (PCG), Protocol Data Unit (PDU), Packet Error Rate (PER), Physical Layer (PHY), Public Land Mobile Network (PLMN), Packet Loss Rate (PLR), Physical Random-Access Channel (PRACH), Physical Resource Block (PRB), PUCCH Resource Indicator (PRI), Positioning Reference Signal (PRS), Primary cell of a Secondary cell group (PScell), Primary Synchronization Signal (PSS), Phase Tracking Reference Signal (PT-RS), Quality of Service (QoS) (from a physical layer perspective), Radio Access Bearer (RAB) Bearer (RAB), Radio Access Network Paging Area (RAN PA), Random Access Channel (or Procedure) (RACH), Random Access Response (RAR), Radio Access Technology (RAT), Resource Block (RB), Radio access network Central Unit (RCU), Radio Front end (RF), Resource Element (RE), Radio Link Failure (RCF)Failure (RLF), Radio Link Monitoring (RLM), Radio Network Identifier (RNTI), Random Access Occasion (RO), Read-Only Mode (ROM) (for MBMS), Radio Resource Control (RRC), Radio Resource Management (RRM), Reference Signal (RS), Round-Trip Time (RTT), Sub-Band Non-Overlapping Full Duplex (SBFD), Secondary Cell Group (SCG), Single Carrier Multiple Access (SCMA), Sub-Carrier Spacing (SCS), Service Data Unit (SDU), Spectrum Operation Mode (SOM), Semi-persistent (SP), Primary cell of a master and / or secondary cell group group, SpCell), Signaling Radio Bearer (SRB), Synchronization Signal (SS), Sounding Reference Signal (SRS), Secondary Synchronization Signal (SSS), Supplementary UpLink (SUL), Switching Gap (SWG) (in self-contained subframes), Transport Block (TB), Transport Block Size (TBS), Transmission Configuration Index (TCI), Time-Division DuplexingTransmission Reference Signal (TRS), Time Division Multiplexing (TDD), Time-Division Multiplexing (TDM), Time Interval (TI) (an integer multiple of one or more symbols), Transmission Time Interval (TTI) (at an integer multiple of one or more symbols), Transmission / Reception Point (TRP), Transmission / Reception Point Group (TRPG), Tracking Reference Signal (TRS), Transceiver (TRx), Uplink (UL), Ultra-Reliable Communication (URC), Ultra-Reliable and Low Latency Communications (URLLC), Vehicle Communications (V2X), Wireless Local Area Network (WLAN) and related technologies (IEEE 802.xx domain), and Cross Division Duplex (XDD).

[0068] In RAN#94-e, the RAN study items include New Radio (NR) duplex operation. This technology can be a major basis for improving traditional TDD operation by enhancing UL coverage, improving capacity, reducing latency, etc. Traditional TDD operation is based on splitting the time domain between uplink and downlink. NR Rel.18 will explore the feasibility of enabling full duplex, and / or more specifically sub-band non-overlapping full duplex (SBFD) at gNBs within traditional TDD bands.

[0069] The NR may support dynamic / flexible time division duplexing (TDD) based on a slot format indicator (SFI) that can be indicated to a group of WTRUs by a group-common (GC) DCI (format 2_0). In addition, semi-static configuration via tdd-UL-DL-config-common / dedicated may be configured such that the transmission pattern of each slot, symbol, and / or time instance can be configured as either "D" for downlink, "U" for uplink, or "F" for flexible (or "S" for a special time instance). In operation with SBFD configured in a time instance having a first TDD direction (e.g., DL), one or more sets of subbands, PRBs, and / or BWPs may be configured with a second TDD direction (e.g., UL). Thus, subbands with a second TDD direction may enable higher coverage, increased capacity, higher performance efficiency, and lower latency for transmissions in the second TDD direction (e.g., UL).

[0070] As shown in FIG. 2, an example of a TDD configuration (e.g., DXXSU) is provided in which UL subbands 202, 204 may be configured by RRC, MAC-CE, and / or DCI via SBFD configuration information in DL slot number 2 208 and DL slot number 3 210, respectively, as part of the SBFD configuration. FIG. 2 illustrates five slots: slot 1 206 (DL slot), slot 2 208 (SBFD slot), slot 3 210 (SBFD slot), slot 4 212 (flexible slot), and slot 5 214 (UL slot). "DXXSU" may refer to the DL slot, SBFD slot, SBFD slot, flexible slot, and UL slot configuration. UL SBs 202, 204 may be configured to be located at any location / subband (e.g., top, bottom, middle, etc.) within the SBFD slot. Flexible slots may be slots used in TDD in which some symbols are configured as DL and some symbols are configured as UL, based on the configuration. Slot 2 208 and slot 3 210 may be SBFD slots. The SBFD configuration information may indicate PUSCH repetition or transport block over multiple slots (TBoMS). The WTRU may determine the type of slot (e.g., SBFD, non-SBFD, flexible) for the PUSCH transmission. The WTRU may determine the number of available slots. Determining the number of available slots may include one or more of determining that non-SBFD uplink transmission slots are available and determining that SBFD slots are available only if the second FDRA is within one or more subbands for the uplink transmission.

[0071] In TDD NR, HARQ-ACK transmission may be possible on symbols that do not overlap with DL symbols indicated by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, if provided, and / or symbols of SS / PBCH blocks with indices provided by ssb-PositionsInBurst. HARQ-ACK timing may be configured via K1, indicated by parameter dl-DataToUL-ACK as part of PUCCH-Config, where K1 refers to the slot for PUCCH transmission and may range from 0 to 15 slots. As shown in FIG. 3, the slot configuration DDDDU may include different K1 values ​​(e.g., 2, 3, 4, 6). The size of the K1 value may be related to the distance between the DL slot and the next UL (e.g., PUCCH) transmission. For example, when K1 = 2, the next UL transmission is two slots away, and when K1 = 4, the next UL transmission is four slots away.

[0072] Reducing latency and improving coverage may be important objectives when applying SBFD as described herein. The present disclosure provides resource allocation for uplink transmissions in SBFD UL subbands. In particular, because the frequency band for SBFD subbands is different (e.g., restricted) compared to UL-only slots, the present disclosure considers interpreting PUCCH and PUSCH frequency resource allocation, HARQ-ACK transmission, UL repetition, and frequency hopping. As defined herein, the present disclosure discusses applying different FDRAs, different frequency hopping offsets, and / or disabling / skipping some operations in SBFD and / or non-SBFD (e.g., UL-only, DL-only) symbols. While such restriction schemes may result in lower coverage, lower capacity, and / or increased latency, which may contradict the objective of applying SBFD. Therefore, the present disclosure contemplates WTRU behavior when receiving a grant for PUCCH / PUSCH transmission in DL slots and / or DL ​​symbols. The WTRU may receive PUCCH configuration information. The WTRU may determine a first FDRA and a second FDRA for non-SBFD slots and SBFD slots. The first FDRA and the second FDRA may use frequency resources or physical resource block (PRB) resources. The WTRU may use the first FDRA for non-SBFD slots and the second FDRA for SBFD slots. The WTRU may use separate frequency resources for the SBFD slots and non-SBFD slots based on the first FDRA.

[0073] Furthermore, this disclosure contemplates whether / how to indicate frequency / PRB resources for DL ​​transmission when overlapping with SBFD UL subbands. Furthermore, this disclosure contemplates whether / how to perform (multi-slot) UL / DL repetition, where the repetition instance may span both SBFD time instances and UL-only / DL-only time instances. Furthermore, this disclosure contemplates how the WTRU may use SBFD UL subbands to enhance coverage in repetitive transmission / reception for PUCCH / PUSCH / PDCCH / PDSCH for MIMO / multi-TRP.

[0074] It should be noted that words such as "a" and "an" and similar words should be interpreted as "one or more" and "at least one." Similarly, any term ending in the suffix "(s)" should be interpreted as "one or more" and "at least one." The term "may" should be interpreted as "for example, may." It should also be noted that the phrases "serving cell" and "component carrier" may be used interchangeably herein. It should also be noted that the terms occasion, time instance, and time unit may be used interchangeably herein.

[0075] The WTRU may transmit and / or receive physical channels and / or reference signals according to at least one spatial domain filter. Note that the term "beam" may be used to refer to a spatial domain filter.

[0076] The WTRU may transmit physical channels and / or signals using the same spatial domain filter as that used to receive RSs (e.g., CSI-RSs) and / or SS blocks. In some cases, the WTRU transmission may be referred to as the "target," and the received RSs and / or SS blocks may be referred to as the "reference" and / or "source." In such cases, the WTRU may be said to transmit the target physical channels and / or signals according to a spatial relationship with reference to such RSs and / or SS blocks.

[0077] The WTRU may transmit a first physical channel and / or signal according to the same spatial-domain filter as used to transmit a second physical channel and / or signal. The first and second transmissions may be referred to as the “target” and “reference” (or “source”), respectively. In such a case, the WTRU may transmit the first (target) physical channel and / or signal according to a spatial relationship with reference to the second (reference) physical channel and / or signal.

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

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

[0080] The WTRU may receive and / or configure and / or provide one or more PUCCH resource sets (e.g., PUCCH-ResourceSet in PUCCH-Config). The WTRU may receive PUCCH configuration information. The WTRU may receive subband non-overlapping full duplex (SBFD) configuration information. The SBFD configuration information may indicate one or more orthogonal frequency division multiplexing (OFDM) symbols associated with one or more subbands for uplink transmission and one or more subbands for downlink reception. The WTRU may receive scheduling information associated with multiple physical uplink shared channel (PUSCH) transmissions. The scheduling information may include a first frequency domain resource allocation (FDRA). The WTRU may send a first PUSCH transmission of the multiple PUSCH transmissions using a first frequency resource determined based on the first FDRA. The WTRU may determine that a second PUSCH transmission of the at least multiple PUSCH transmissions should be sent using at least one OFDM symbol of the one or more OFDM symbols. The WTRU may determine, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in one or more subbands for uplink transmission and / or one or more subbands for downlink reception of the at least one OFDM symbol. The WTRU may receive one or more of the second FDRA or frequency offset for the second PUSCH transmission. The WTRU may determine a second frequency resource for sending the second PUSCH transmission based on the one or more of the second FDRA or frequency offset. The second frequency resource may be included in one or more subbands for uplink transmission of the at least one OFDM symbol. The WTRU may send the second PUSCH transmission using the second frequency resource.

[0081] A PUCCH resource set may include one or more PUCCH resources. In one or more cases, the PUCCH resource may include one or more of the following parameters: For example, the PUCCH resource may include a PUCCH resource index (e.g., pucch-ResourceId). In another example, the PUCCH resource may include an index indication for the first PRB before frequency hopping and / or without frequency hopping (e.g., startingPRB). In another example, the PUCCH resource may include an index indication for the first PRB after frequency hopping (e.g., secondHopPRB). In another example, the PUCCH resource may include an indication for intra-slot frequency hopping (e.g., intraSlotFrequencyHopping). In another example, the PUCCH resource may include an index indication for the first interlace and / or the second interlace (e.g., interlace0 and / or interlace1, respectively) and / or an index indication for the respective RB set (e.g., rb-SetIndex). In another example, the PUCCH resource may include a configuration (e.g., format) for a PUCCH format, which may be selected from one or more (pre-)configured formats.

[0082] The first PUCCH resource and / or the second PUCCH resource may be within a slot symbol. The PUCCH configuration information may include a transmission repetition number. The PUCCH may be transmitted using Frequency Domain Resource Allocation (FDRA). The DCI may indicate that the first PRI is for a HARQ-ACK transmission. Determining the second PUCCH resource may include re-indexing the PUCCH resource. The transmission of the PUCCH transmission may be in a time unit configured for SBFD.

[0083] An example of PUCCH formats 3 and 4 and parameters that may be included for each format is shown in Figure 4. Note that the exemplary parameters are non-limiting examples of parameters that may be included in PUCCH formats and PUCCH resource configurations. One or more of the parameters may be included. The number of bits and options for each parameter are examples. Other numbers of bits and / or options may also be included.

[0084] The PUCCH format may include one or more parameters indicated for each PUCCH transmission. The parameters may include, but are not limited to, a starting symbol index (e.g., startingSymbolIndex), a number of symbols (e.g., nrofSymbols), a number of PRBs (e.g., nrofPRBs), an initial cyclic shift value (e.g., initialCyclicShift), parameters for configuring an orthogonal cover code (OCC) (e.g., timeDomainOCC, occ-Length, occ-Index), etc. The PUCCH configuration may include one or more parameters (e.g., PUCCH-SpatialRelationInfo, pucch-SpatialRelationInfoId, TCI-State_r17) for indicating a spatial relationship and / or configuration for each PUCCH transmission. The spatial configuration and / or spatial relationship may be based on one or more reference signals and / or beam resources (e.g., ssb-Index, csi-RS-Index, srs, etc.).

[0085] The WTRU may report HARQ-ACK information for reception of PDSCH, reception of SPS PDSCH release, and / or reception of TCI state update in a slot indicated by a corresponding (e.g., activating) DCI (e.g., indicated by a PDSCH-to-HARQ_feedback timing indicator field) and / or provided by a PUCCH-Config (e.g., dl-DataToUL-ACK, dl-DataToUL-ACK-r16, and / or dl-DataToUL-ACK-ForDCI-Format1-2). In one example, the timing indicator value in the corresponding DCI may be mapped to a fixed slot location, for example, based on the SCS configuration of the PUCCH transmission (e.g., DCI format 1_0). In another example, the timing indicator value in the corresponding DCI may be mapped to select a slot location from a set of RRC-configured slot numbers (e.g., dl-DataToUL-ACK, dl-DataToUL-ACK-r16, dl-DataToUL-ACKForDCIFormat1_2 and / or dl-DataToUL-ACK-r17, etc.).

[0086] TRP (e.g., transmitting and receiving point) may be used interchangeably with one or more of TP (transmission point), RP (receiving point), RRH (radio remote head), DA (distributed antenna), BS (base station), sector (sector of a BS), and cell (e.g., geographic cell area served by a BS) while still being consistent with the disclosure provided herein. Multi-TRP may be used interchangeably with one or more of MTRP, M-TRP, and multi-TRP while still being consistent with the disclosure provided herein.

[0087] The terms "subband" and / or "sub-band" may be used to refer to frequency-domain resources. Furthermore, the terms "subband" and / or "sub-band" may be characterized by at least one of the following: a set of resource blocks (RBs), a set of resource block sets (RB sets) (e.g., when a carrier has an intra-cell guard band), a set of interlaced resource blocks, a bandwidth portion and / or a portion thereof, and / or a carrier and / or a portion thereof. For example, a subband may be characterized by a starting RB and a number of RBs for a set of contiguous RBs within a bandwidth portion. A subband may also be defined by values ​​of a frequency-domain resource allocation field and a bandwidth portion index. The WTRU may determine the start of the second PUSCH transmission based on the starting resource block (RB) of the SBFD or the starting RB of the second FDRA. The WTRU may determine the second FDRA from an indication or SBFD configuration information.

[0088] The term "XDD" may be used to refer to duplexing per subband (e.g., either UL and / or DL ​​are used per subband). Furthermore, the term "XDD" may be characterized by at least one of the following: cross-division duplex (e.g., FDD per subband within the TDD band), subband non-overlapping full duplex (SBFD), subband-based full duplex (e.g., full duplex where both UL and DL are used / mixed on a symbol / slot, but either UL and / or DL ​​are used per subband on a symbol / slot), frequency-domain multiplexing (FDM) of DL / UL transmissions within the TDD spectrum, subband non-overlapping full duplex (e.g., non-overlapping subband full duplex), full duplex other than co-frequency (e.g., spectrum sharing, non-overlapping per subband) full duplex, and / or advanced duplex methods other than (pure) TDD and / or FDD.

[0089] The terms "dynamic TDD" and / or "dynamic / flexible TDD" may refer to a TDD system and / or cell that can dynamically (and / or flexibly) change / adjust / switch communication directions (e.g., downlink, uplink, and / or sidelink) at a time instance (e.g., slot, symbol, subframe, etc.). In one example, in a system using dynamic / flexible TDD, a component carrier (CC) and / or a bandwidth part (BWP) may have a single type among "D," "U," and "F" on a symbol / slot based on an indication by a DCI, such as a group-common (GC)-DCI (e.g., format 2_0) with a slot format indicator (SFI), and / or based on the tdd-UL-DL-config-common and / or dedicated configuration. The term component carrier may refer to a set of frequencies, one or more BWPs, a serving cell, etc. At a given time instance (e.g., slot and / or symbol), a first gNB (e.g., cell, TRP) employing dynamic / flexible TDD may transmit a downlink signal to a first WTRU communicating with and / or associated with the first gNB, e.g., based on a first SFI and / or tdd-UL-DL-config configured and / or indicated by the first gNB. A second gNB (e.g., cell, TRP) employing dynamic / flexible TDD may receive an uplink signal transmitted from a second WTRU communicating with and / or associated with the second gNB, e.g., based on a second SFI and / or tdd-UL-DL-config configured / indicated by the second gNB. In one example, the first WTRU may determine that its reception of the downlink signal is being interfered with by an uplink signal, where the interference caused by the uplink signal may refer to WTRU-to-WTRU cross-layer interference (CLI).

[0090] The WTRU may report a subset of channel state information (CSI) components, which may correspond to at least a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of the panel used for reception at the WTRU (e.g., panel identification information and / or group identification information), measurements such as L1-RSRP, L1-SINR obtained from the SSB and / or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and / or other channel state information such as at least a rank indicator (RI), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a layer index (LI), etc.

[0091] A WTRU may receive synchronization signal / physical broadcast channel (SS / PBCH) blocks. The SS / PBCH blocks (SSBs) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and 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 switching, etc.

[0092] The WTRU may measure and report channel state information (CSI), and the CSI for each connection mode may include and / or be configured with one or more of the following parameters: CSI reporting configuration, CSI-RS resource set, and / or NZP-CSI-RS resource. In some cases, the CSI reporting configuration may include one or more of the following: CSI reporting quantity (e.g., Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), etc.; CSI reporting type (e.g., aperiodic, semi-persistent, and / or periodic); CSI reporting codebook configuration (e.g., Type I, Type II, Type II port selection, etc.); and / or CSI reporting frequency. In one or more cases, the CSI-RS resource set may include one or more of the following CSI resource configurations: NZP-CSI-RS resources for channel measurement, NZP-CSI-RS resources for interference measurement, and / or CSI-IM resources for interference measurement. In one or more cases, the NZP CSI-RS resources may include one or more of the following: NZP CSI-RS resource ID, periodicity and offset, QCL information or TCI state, and / or resource mapping (e.g., number of ports, density, CDM type, etc.).

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

[0094] The WTRU may be configured with the SS reference signal received power (SS-RSRP). The SS-RSRP may be measured based on synchronization signals (e.g., demodulation reference signals (DMRS) in the PBCH and / or SSS). The SS-RSRP may be defined as a linear average over the power contributions of resource elements (REs) carrying each synchronization signal. Power scaling of the reference signal may be determined to measure the RSRP. In the case where SS-RSRP is used for L1-RSRP, the measurement may be achieved based on the CSI reference signal in addition to the synchronization signal.

[0095] The WTRU may be configured with CSI-RSRP, which may be measured based on a linear average over the power contribution of resource elements (REs) carrying each CSI-RS. CSI-RSRP measurements may be configured within measurement resources for the configured CSI-RS occasions.

[0096] The WTRU may be configured with a SS signal-to-noise and interference ratio (SS-SINR). The SS-SINR may be measured based on synchronization signals (e.g., DMRS in the PBCH and / or SSS). The SS-RSRP may be defined as the linear average over the power contributions of resource elements (REs) carrying each synchronization signal divided by the linear average of the noise and interference power contributions. In the case where SS-SINR is used for L1-SINR, the noise and interference power measurement may be achieved based on resources configured by higher layers.

[0097] The WTRU may be configured with CSI-SINR, which may be measured based on a linear average over the power contribution of the resource elements (REs) carrying each CSI-RS divided by the linear average of the noise and interference power contributions. If CSI-SINR is used for L1-SINR, the noise and interference power measurement may be achieved based on resources configured by higher layers. Otherwise, the noise and interference power may be measured based on the resources carrying each CSI-RS.

[0098] The WTRU may be configured with a received signal strength indicator (RSSI), which may be measured based on an average of the total power contributions over the configured OFDM symbols and bandwidth. The power contributions may be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0099] The WTRU may be configured with a cross-layer interference received signal strength indicator (CLI-RSSI). The CLI-RSSI may be measured based on an average of the total power contributions in the configured OFDM symbols of the configured time and frequency resources. The power contributions may be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0100] The WTRU may be configured with a sounding reference signal RSRP (SRS-RSRP), which may be measured based on a linear average over the power contributions of resource elements (REs) carrying each SRS.

[0101] In one or more cases, the properties of the grant and / or allocation may consist of at least one of the following: frequency allocation, time allocation aspects such as duration, priority, modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks, TCI state, CRI and / or SRI, repetition count, whether the repetition scheme is Type A and / or Type B, whether the grant is a configured grant Type 1, Type 2 and / or dynamic grant, whether the allocation is a dynamic allocation and / or semi-persistent scheduling (configured) allocation, configured grant index and / or semi-persistent allocation index, periodicity of the configured grant and / or allocation, channel access priority class (CAPC), and / or any parameters provided in the DCI by the MAC and / or by the RRC for scheduling the grant and / or allocation.

[0102] The indication by the DCI may include at least one of the following: an explicit indication by the DCI field and / or RNTI used to mask the CRC of the PDCCH, and / or an implicit indication such as the DCI format, DCI size, Coreset and / or search space, aggregation level, first resource element of the received DCI (e.g., index of the first control channel element), etc., where the mapping between properties and values ​​may be signaled by RRC and / or MAC.

[0103] The signal may be used interchangeably with one or more of the following: sounding reference signal (SRS), channel state information reference signal (CSI-RS), semodulation reference signal (DM-RS), phase tracking reference signal (PT-RS), and / or synchronization signal block (SSB).

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

[0105] Downlink reception may be used interchangeably with Rx occasions, PDCCH, PDSCH, and / or SSB reception. Uplink transmission may be used interchangeably with Tx occasions, PUCCH, PUSCH, PRACH, and SRS transmission. RS may be used interchangeably with one or more of RS resource, RS resource set, and / or RS port and RS port group. RS may be used interchangeably with one or more of SSB, CSI-RS, SRS, and DM-RS. Time instances, slots, symbols, and subframes may be used interchangeably. UL-only Tx / Rx occasions and DL-only Tx / Rx occasions may be used interchangeably with legacy TDD UL and / or legacy TDD DL, respectively. In one example, legacy TDD UL / DL Tx / Rx occasions may be when SBFD is not configured and / or SBFD is disabled. The forward slash " / " sign, symbol, and / or mark may be construed as "and / or" unless otherwise stated, for example, "A / B" may mean "A and / or B."

[0106] The solutions provided in this disclosure may be applicable to uplink transmissions (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) and / or sets of uplink transmissions (e.g., repetitions) for PUCCH occasions transmitted according to a PUCCH configuration and / or PUSCH occasion transmitted according to a grant, such as a configured grant. A WTRU may be configured with uplink transmissions and / or repetitions in an UL-only time instance, and UL resources may be used for UL transmissions and / or repetitions on UL subbands in an SBFD time instance. The number / length of subbands configured for an UL-only time instance may span larger subbands than the uplink subbands in the SBFD time instance. For example, all RBs within a BWP may be used for the uplink in an uplink-only slot / symbol, but a subset of the RBs within the BWP may be used for the uplink in an SBFD slot / symbol.

[0107] The solutions described in this disclosure may be applicable to downlink reception (e.g., SPS PDSCH, PDCCH, CSI-RS, etc.) and / or a set of downlink receptions (e.g., repetitions) configured in a DL-only time instance, and the configured PDSCH resources may be used for DL ​​reception and / or repetitions on DL subbands in the SBFD-configured time instance. In one example, SBFD may be configured for one or more uplink subbands in a legacy DL time instance, with the remaining subbands used for DL. Alternatively, SBFD may be configured for one or more downlink subbands in a legacy uplink time instance, with the remaining subbands used for UL. In this case, the number / length of subbands configured for the DL-only time instance may span more subbands than the downlink subbands in the SBFD time instance. For example, all RBs within a BWP may be used for DL ​​in a DL-only slot / symbol, but a subset of RBs within the BWP may be used for DL ​​in an SBFD slot / symbol.

[0108] In one or more cases, the WTRU may be configured for resource allocation when using SBFD. The WTRU may receive and / or be configured with one or more resource allocation configurations for uplink transmissions (e.g., channels) in one or more Tx occasions. For example, in the case of a controlled uplink transmission (e.g., PUCCH), the resource configuration (e.g., for each resource allocation configuration) may include one or more parameters such as a starting PRB, a second-hop starting PRB, a number of PRBs, a number of slots, a starting symbol index, a PUCCH format, a cyclic shift, an OCC setting, etc., which may be indicated based on a PUCCH resource index / indicator (e.g., PUCCH-ResourceId). In one example, in the case of a downlink (shared) channel transmission (e.g., PDSCH) that may be configured by a semi-static instruction (e.g., an SPS PDSCH configured by SPS-Config), the WTRU may determine, receive, and / or be configured with an associated PUCCH resource index / indicator to be used for transmitting corresponding control information (e.g., HARQ-ACK, CSI report, etc.). For example, the time resources (e.g., slots) for the transmission of HARQ-ACK in each PUCCH may be defined based on one or more RRC configured parameters (e.g., K1 defined via dl-DataToUL-ACK in PUCCH-Config within BWP-UplinkDedicated) and / or activated by DCI (e.g., formatting 1_1 and / or 1_2 with the value of the Timing Indicator field to PDSCH-to-HARQ_feedback).

[0109] In another example, for an uplink shared channel transmission (e.g., PUSCH), the resource allocation / configuration may be indicated based on one or more settings / parameters such as time resources (e.g., timeDomainAllocation), frequency resources (e.g., frequencyDomainAllocation), periodicity, repetition, etc. For example, for a PUSCH transmission corresponding to a first configured grant (e.g., Type 1) and / or a PUSCH transmission corresponding to a second configured grant (e.g., Type 2) and activated (e.g., DCI), the resource allocation is provided by one or more parameters (e.g., via ConfiguredGrantConfig in BWP-UplinkDedicated and / or activation of an UL grant received on the DCI). Furthermore, for a PUSCH transmission corresponding to an UL grant (e.g., a dynamic grant), the TDRA value (e.g., in the DCI) may indicate a slot offset (e.g., K2 via an indexed row), a start and length indicator (e.g., SLIV), and / or directly the starting symbol and allocation length, the respective PUSCH mapping type, the number of slots used for TBS determination, and / or the number of repetitions of the PUSCH transmission. The WTRU may send the first PUSCH transmission using a time division duplex (TDD) configuration.

[0110] In one or more cases, the WTRU may be configured with a PUCCH resource set and a PUCCH resource indicator (PRI). The WTRU may receive PUCCH configuration information. The WTRU may receive one or more PUCCH resource sets including one or more PUCCH resources and / or may be configured with one or more PUCCH resource sets. In one example, the PUCCH resource may comprise parameters including a PUCCH resource index, an index of the first PRB, an index of the first PRB for frequency hopping, a PUCCH format, a starting symbol index, a number of symbols, a number of PRBs, etc. The WTRU may receive and / or be configured with a PUCCH resource indicator (PRI) (e.g., via a DCI such as a DL grant DCI). In one example, the PRI may be indicated by a number of bits (e.g., up to 3 bits, etc.). The PRI may indicate a PUCCH resource. The PRI may indicate a PUCCH resource from among a set of (configured) PUCCH resources that may be provided by the PUCCH resource set. The PUCCH resource and / or PUCCH resource set may be received from and / or configured by the gNB. The WTRU may use the PRI to determine the resource allocation (e.g., time and / or frequency resources) to be used for PUCCH transmission (e.g., for HARQ-ACK feedback of PDSCH indicated by DL grant DCI).

[0111] A WTRU may receive a DCI including a first PRI. The WTRU may determine that a PUCCH transmission indicated by the DCI should be sent using at least one or more OFDM symbols associated with a set of one or more subbands for uplink transmission and a set of one or more subbands for downlink reception indicated by the SBFD configuration information. The WTRU may determine, based on a first rule for interpreting the first PRI and the PUCCH configuration information, that the first PUCCH resource indicated by the first PRI is included in at least one frequency resource that is at least partially included in one subband of the set of one or more subbands for uplink transmission and / or at least one subband of the set of one or more subbands for downlink reception indicated by the SBFD configuration information. The WTRU may determine a second PUCCH resource in response to determining that the first PUCCH resource indicated by the first PRI is included in at least one frequency resource that is at least partially included in one subband of the set of one or more subbands for uplink transmission and / or at least one subband of the set of one or more subbands for downlink reception indicated by the SBFD configuration information. The second PUCCH resource may be determined based on a second rule for interpreting the first PRI and the PUCCH configuration information. The second PUCCH resource may be within the set of one or more subbands for uplink transmission indicated by the SBFD configuration information. The WTRU may send the PUCCH transmission using the second frequency resource.

[0112] The second rule may include applying a frequency offset to the first PUCCH resource. The second rule may include applying a different mapping for the first PRI to PUCCH resources for transmissions associated with the SFBD configuration information and the first PRI. The second rule may map the first PRI to a second PRI. The second PRI may be used to determine a second PUCCH resource. The second PRI may be used for SBFD uplink transmissions based on its association with a non-SBFD PRI.

[0113] In one or more cases, the resource configuration configured and / or received in frequency (e.g., PRB assignment, PRB index) may be based on the BWP. In one example, the BWP may be an active BWP linked to a respective Tx occasion. In other words, the resource configuration (e.g., PRB assignment, PRB index) may be based on the active linked BWP. Thus, the index used for PRB indication for resource allocation may be based on the entire (active) (linked) BWP (e.g., like a Tx occasion with a UL-only configuration in TDD). In one example, for an active uplink BWP (e.g., indicated by bwp-id), if the total number of available PRBs is N, the PRB index used in the resource configuration may be indexed from 0 to N. Thus, the WTRU may be configured to determine whether / how to indicate frequency / PRB resources for transmission in the SBFD UL subband.

[0114] In one or more cases, a WTRU (e.g., an SBFD-capable WTRU) may receive and / or be configured with one or more SBFD UL and / or DL ​​subbands within one or more symbols that may be (e.g., previously) configured as DL, UL, and / or flexible symbols. The configuration as DL, UL, and / or flexible may be based on one or more TDD UL / DL configurations that the WTRU may receive, such as a common TDD UL / DL configuration, a dedicated TDD UL / DL configuration, and / or an SFI (e.g., a dynamically indicated SFI). The WTRU may be configured with one or more time and frequency resource allocations for the SBFD subbands.

[0115] In one or more cases, the SBFD configuration may include a flag signal (e.g., enable / disable), where, for example, one value (e.g., a value of 0) may indicate no SBFD configuration (e.g., SBFD is not enabled) and another value (e.g., a value of 1) may indicate the enablement of the SBFD configuration. The SBFD configuration may be indicated via a SIB, semi-statically (e.g., via RRC), dynamically (e.g., via MAC-CE, DCI), etc. The WTRU may receive an indication of time resources (e.g., one or more symbols, slots, etc.) for which SBFD is applicable to a serving cell, carrier, and / or BWP. The WTRU may receive frequency resources (e.g., subbands, BWP, and / or one or more PRBs) for which SBFD may be configured. The SBFD configuration may be configured (e.g., linked to) a BWP and / or may apply to a BWP, such as an active BWP. The time instances (e.g., slots, symbols) configured for SBFD may be indicated based on a periodic configuration, a semi-persistent configuration, and / or an aperiodic configuration. In one example, the time instance may be indicated via a bitmap configuration.

[0116] In one example, a WTRU may be configured with a DL TDD configuration for a component carrier (CC) and / or a BWP for one or more Rx occasions (e.g., via a tdd-UL-DL-config-common / dedicated configuration, a slot format indicator (SFI), etc.). The WTRU may receive and / or be configured with SBFD operation as part of the TDD DL configuration at the respective time instance. Thus, if SBFD is configured, the configured frequency resources (e.g., subbands / PRBs / BWPs) may be configured for the UL channel / Tx occasion. In another example, the WTRU may be configured with a UL TDD configuration for a component carrier (CC) and / or a BWP for one or more Tx occasions (e.g., via a tdd-UL-DL-config-common / dedicated configuration, a slot format indicator (SFI), etc.). The WTRU may further receive and / or be configured with an SBFD configuration as part of the TDD UL configuration at the respective time instance. Thus, when SBFD is configured, the configured frequency resources (e.g., subbands / PRBs / BWPs) may be configured for DL ​​channels / Rx occasions. In another example, a WTRU may be configured with DL / UL / flexible TDD configurations for a component carrier (CC) and / or BWPs for one or more Rx / Tx occasions (e.g., via a tdd-UL-DL-config-common / dedicated configuration, a slot format indicator (SFI), etc.). The WTRU may receive and / or be configured for SBFD operation as part of the TDD DL / UL / flexible configuration at each time instance. Thus, when SBFD is configured, the configured frequency resources (e.g., subbands / PRBs / BWPs) may be configured for either UL transmission and / or DL ​​reception based on the configuration. The duplexing mode for the SBFD configuration (UL / DL) may be indicated by a flag, where, for example, a first value (e.g., 0) may indicate UL duplexing mode and a second value (e.g., 1) may indicate a DL duplexing mode.The SBFD duplex mode configuration / flag may be configured as part of the SBFD configuration, which may be semi-static (e.g., via RRC) and / or dynamic (e.g., via DCI, MAC-CE). The SBFD duplex mode configuration / flag may be configured as part of the resource allocation configuration for a Tx / Rx occasion.

[0117] In one or more cases, the WTRU may be configured for PUCCH resource determination in SBFD. The WTRU may receive PUCCH configuration information. In one or more cases, the WTRU may receive and / or be configured with one or more PUCCH transmission configurations within and / or for SBFD symbols and / or slots (symbols / slots), where the PUCCH configurations may include a PUCCH resource indicator (PRI). In one example, a DCI format with a DL dynamic grant and / or a DCI format activating and / or releasing an SPS PDSCH may include an indication of a PRI to a corresponding PUCCH resource. The WTRU may use the indicated PRI to determine resources for transmission of each PUCCH (e.g., including HARQ-ACK, CSI-RS, etc.).

[0118] The WTRU may determine time-domain resources for PUCCH transmission, which may be mapped to a TDD DL time instance (e.g., one or more symbols and / or slots). In one example, the WTRU may be configured with HARQ-ACK transmission, and the configured K1 may refer to a DL symbol and / or slot. Thus, the WTRU may determine whether the configured TDD DL time instance is configured with SBFD and whether SBFD operation is enabled (e.g., based on a respective enable / disable flag). If SBFD is not enabled for the TDD DL time instance, the WTRU may skip transmitting the PUCCH at the respective time instance and may monitor, detect, and / or discover the next UL Tx occasion.

[0119] In one or more cases, the WTRU may determine that the configured and / or received PRI maps to time resources corresponding to SBFD-configured symbols and / or slots and / or Tx occasions (e.g., the SBFD configuration flag is enabled). Accordingly, the WTRU may determine whether the frequency resources corresponding to the received / configured PRI are mapped to PRBs, subbands, and / or BWPs corresponding to frequency resources that may be configured for SBFD. The WTRU may use the received PRI to determine frequency resources that may be configured for transmission of the respective PUCCH. The WTRU may determine whether the frequency resources configured for transmission of the respective PUCCH overlap with frequency resources that may be configured for SBFD operation.

[0120] In one example, the WTRU may be configured with SBFD at a time instance (e.g., symbol / slot / tx occasion), the starting PRB corresponding to the subband and / or PRB and / or BWP of the SBFD may be indicated by PRB index N1, and the last PRB corresponding to the subband and / or PRB and / or BWP of the SBFD may be indicated by PRB index N2. Thus, the WTRU may determine whether the PRB corresponding to the PUCCH transmission (e.g., configured by the PRI via the starting PRB and PRB number) is mapped to a PRB between index N1 and index N2.

[0121] If the frequency domain resources corresponding to the PUCCH transmission overlap with the subbands, PRBs, and / or BWPs corresponding to the SBFD configuration (eg, located within the SBFD boundaries), the WTRU may decide to transmit the respective PUCCH.

[0122] In one or more cases, the WTRU may determine that a frequency domain resource corresponding to a PUCCH transmission is partially / wholly outside a subband, PRB, and / or BWP boundary (e.g., PRB index between N1 and N2) corresponding to an SBFD configuration. Accordingly, the WTRU may determine one or more operation modes based on one or more parameters explicitly and / or implicitly determined (e.g., by the gNB). When the WTRU transmits an uplink (e.g., PUCCH / PUSCH) in an SBFD time instance, the WTRU may determine whether one or more values ​​are provided to the WTRU to implicitly and / or explicitly determine a resource location for each UL transmission within the SBFD resource.

[0123] In one or more cases, when a WTRU is configured for uplink transmission in a downlink time instance, the WTRU may determine resources for transmission based on one or more of the following: The WTRU may determine to resolve overlaps with symbols in slots indicated as downlink (e.g., by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated). The WTRU may determine whether the DL time instance is configured with an SBFD configuration (e.g., SBFD is enabled and the respective time and frequency resources are configured). If SBFD is not enabled, the WTRU may skip UL transmission in the respective DL time instance. The WTRU may determine whether the resource allocation for each uplink transmission is within the resources configured for the SBFD uplink subband in the respective time instance. In one or more cases where the resources configured for UL transmission are outside the SBFD boundaries (e.g., frequency domain resources), the WTRU may determine whether one or more values ​​are provided to the WTRU to implicitly and / or explicitly determine the resource location for each UL transmission within the SBFD resources. The WTRU may determine new and / or reinterpreted and / or reindexed resources for each UL transmission in the SBFD time instance.

[0124] In one or more cases, the WTRU may be configured for downlink resource allocation in SBFD symbols. The WTRU may receive and / or be configured with one or more Semi-Persistent Scheduling (SPS) configurations in the BWP (e.g., via sps-Config and / or sps-ConfigToAddModList), where the SPS configuration may include a transmission periodicity, a PDSCH aggregation factor, etc. The WTRU may receive DCI (e.g., format 1_1 and / or 1_2) that may activate one or more SPS transmissions (e.g., CRC scrambled with CS-RNTI), where the DCI may include a time and frequency configuration for each PDSCH transmission. The WTRU may receive scheduling information associated with multiple Physical Uplink Shared Channel (PUSCH) transmissions. The scheduling information may include a first Frequency Domain Resource Allocation (FDRA). One or more PDSCH transmissions may be coincidentally scheduled at DL time instances that may be configured in the SBFD configuration. Therefore, some subbands / PRBs in each DL time instance may be assigned / configured as UL subbands and for UL transmission (e.g., in the case of dynamic SBFD configuration at each time instance). In that case, the frequency domain assignment for one or more of the (SPS) PDSCH transmissions may overlap with the SBFD UL subbands configured at each time instance. Therefore, the WTRU may be configured to determine whether / how to indicate frequency / PRB resources for DL ​​transmissions when overlapping with SBFD UL subbands.

[0125] In one or more cases, a WTRU may be configured for downlink transmission at downlink time instances where one or more UL SBFD subbands, BWPs, and / or PRBs may be enabled / disabled. Alternatively, a WTRU may be configured for DL ​​transmission at UL time instances where one or more DL SBFD subbands, BWPs, and / or PRBs may be enabled / disabled.

[0126] In one or more cases, when a WTRU is configured for downlink transmission in a downlink time instance with an SBFD configuration, the WTRU may determine resources for transmission based on one or more of the following: The WTRU may determine to resolve overlap with symbols in slots indicated as downlink (e.g., by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated). The WTRU may determine whether the DL time instance is configured with an SBFD configuration (e.g., SBFD is enabled and the respective time and frequency resources are configured). If SBFD is enabled, the WTRU may determine whether the resource allocation for the respective downlink transmission overlaps with the resources configured for the SBFD uplink subband at the respective time instance. If the resources have partial / full overlap (e.g., frequency domain resources), the WTRU may determine whether one or more values ​​are provided to the WTRU to implicitly and / or explicitly determine the resource location for the respective DL transmission within the SBFD resources. The WTRU may determine new, reinterpreted, and / or reindexed resources for each DL transmission in the SBFD time instance. The WTRU may determine, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in one or more subbands for uplink transmission and one or more subbands for downlink reception of at least one OFDM symbol. The WTRU may receive (e.g., via a network-provided configuration) one or more of the second FDRA or a frequency offset for the second PUSCH transmission based on the first frequency resource being at least partially included in one or more subbands for uplink transmission and one or more subbands for downlink reception of at least one OFDM symbol. The WTRU may determine a second frequency resource for sending the second PUSCH transmission based on one or more of the second FDRA or the frequency offset.The second frequency resource may be included in one or more subbands for uplink transmission of at least one OFDM symbol. The WTRU may send a second PUSCH transmission using the second frequency resource.

[0127] The second PUCCH resource may be within a slot symbol. The PUCCH configuration information may include a transmission repetition count. The PUCCH may be transmitted using Frequency Domain Resource Allocation (FDRA). The DCI may indicate that the first PRI is for a HARQ-ACK transmission. Determining the second PUCCH resource may include re-indexing the PUCCH resource. The transmission of the PUCCH transmission may be in a time unit configured for SBFD.

[0128] In one or more cases, the WTRU may be configured to determine explicit indications of resource allocation in SBFD symbols. The WTRU may be configured with one or more types of slots within a bandwidth, where a first type of time instance (e.g., slot / symbol) may be used and / or determined for a first direction (e.g., downlink), a second type of time instance may be used and / or determined for a second direction (e.g., uplink), and a third type of time instance may have a first group of frequency resources within the bandwidth for the first direction and a second group of frequency resources within the bandwidth for the second direction. Bandwidth may be used interchangeably with bandwidth portion (BWP), carrier, subband, PRB, and system bandwidth. The first type of time instance (e.g., slot for the first direction) may be referred to as a downlink time instance. The second type of time instance (e.g., slot for the second direction) may be referred to as an uplink time instance. The third type of time instance may be referred to as a subband non-overlapping full duplex (SBFD) time instance. A group of frequency resources in the first direction may be referred to as a downlink subband, a downlink frequency resource, and / or a downlink RB, and a group of frequency resources in the second direction may be referred to as an uplink subband, an uplink frequency resource, and / or an uplink RB.

[0129] The WTRU may be configured with one or more PUCCH resource sets (e.g., up to four PUCCH resource sets), and each PUCCH resource set may include one or more PUCCH resources (e.g., up to 32 PUCCH resources). The WTRU may receive PUCCH configuration information. Each PUCCH resource may be configured with a PUCCH resource ID, starting PRB, intra-slot hopping ON / OFF, and PUCCH format. Based on the PUCCH format, the WTRU may be configured to determine the number of symbols and the maximum number of RBs.

[0130] In one or more cases, a WTRU may be configured with one or more PUCCH resource sets for an uplink-only time instance (e.g., TDD legacy UL-only symbols and / or slots). The WTRU may be configured to use the PUCCH resources configured for an SBFD time instance (e.g., symbols and / or slots), and the number of uplink RBs in SBFD may be less than the number of uplink RBs in an uplink-only time instance. For example, the WTRU may be configured to use all RBs in a BWP for the uplink in an uplink slot, while a subset of the RBs in the BWP may be used for the uplink in an SBFD slot.

[0131] As illustrated in FIG. 5, the WTRU may determine whether an SBFD subband is configured and / or applied to at least one DL time unit, and whether the PUCCH resource is within an SFBD subband.

[0132] In one or more cases, the WTRU may modify the location of resources and / or receive an indication (e.g., via DCI, MAC-CE, and / or RRC signaling) that may instruct the WTRU to modify the location of resources (e.g., PUCCH and / or PUSCH resources), which may include changing and / or shifting (e.g., by an offset) the starting PRB and / or changing the number of PRBs. The modification applies to one or more SBFD-enabled time instances.

[0133] In one or more cases, the WTRU may be configured to reinterpret and / or reindex. The WTRU may reinterpret and / or reindex configured resources based on a PRB shift offset received as part of an SBFD configuration (e.g., group common configuration, RRC / MAC-CE / DCI configuration). The WTRU may receive one or more frequency offset values ​​in addition to one or more flag indications that enable such reinterpretation (e.g., enable / disable). The WTRU may determine the second FDRA from the first FDRA by applying a frequency offset. The frequency offset may be a resource block (RB) offset. The frequency offset may be configured or indicated using a medium access control (MAC) control element (CE) or downlink control information (DCI). The frequency offset may be included in the indication or configuration. The WTRU may use the first FDRA and the frequency offset to determine a second frequency resource for sending a second PUSCH transmission.

[0134] The PRB index provided for downlink and / or uplink resources in the frequency domain may be partially and / or entirely mapped to a PRB outside the boundaries of the downlink subband and / or uplink subband and / or PRB and / or BWP in the SBFD configuration, respectively. Accordingly, the WTRU may determine to use a configured offset value to be added to and / or subtracted from the configured UL and / or DL ​​PRB index such that the new PRB index maps within the SBFD UL and / or DL ​​boundary, PRB, BWP, and / or subband, respectively. In one example, the WTRU may be provided with and / or configured with a flag indication to add and / or subtract the configured offset value based on the preceding and / or succeeding location, respectively, of the configured UL and / or DL ​​PRB index with respect to the corresponding PRB, BWP, and / or subband within the SBFD time instance. In another example, the WTRU may be provided and / or configured with positive and / or negative offset values ​​at preceding and / or succeeding locations of the configured UL and / or DL ​​PRB index, respectively, for the corresponding PRB, BWP, subband within the SBFD time instance.

[0135] In one or more cases, the WTRU may be configured to determine a starting RB association. The starting RB index of a PUCCH resource in an uplink slot may be associated with a starting RB index in an uplink subband in an SBFD slot and / or symbol. Alternatively, the starting RB index of a configured PUSCH resource may be associated with a configured RB index in an uplink subband at an SBFD time instance. Furthermore, the starting RB index of an SPS PDSCH 508 resource may be associated with a configured RB index in a downlink subband at an SBFD time instance. The WTRU may receive an indication for the associated starting RB index as part of an SBFD configuration (e.g., group common configuration and / or RRC / MAC-CE / DCI configuration). Alternatively, the WTRU may receive an indication of the associated starting RB index as part of a PUCCH resource indication (e.g., via DCI activation). Thus, the WTRU may determine the RB index to be used for UL transmission and / or DL ​​reception in the SBFD UL subband 512 and / or DL ​​subband based on the associated starting RB index, and the starting RB index (e.g., for a PUCCH resource) in each SBFD subband may be determined as a function of the number of RBs in the uplink subband in the SBFD slot (N b,SFBD ), a function of the number of RBs in an uplink slot (N b,UL ) and a function of the starting RB index within the uplink slot. The WTRU may determine the start of the second PUSCH transmission based on the starting resource block (RB) of the SBFD or the starting RB of the second FDRA. The WTRU may determine the second FDRA from the indication or SBFD configuration information.

[0136] The second PUCCH resource may be within a slot symbol. The PUCCH configuration information may include a transmission repetition count. The PUCCH may be transmitted using Frequency Domain Resource Allocation (FDRA). The DCI may indicate that the first PRI is for a HARQ-ACK transmission. Determining the second PUCCH resource may include re-indexing the PUCCH resource. The transmission of the PUCCH transmission may be in a time unit configured for SBFD.

[0137] In one or more cases, the WTRU may be configured to determine alternative resources. One or more PUCCH resources located within the uplink subband in the SFBD slot (e.g., valid PUCCH resources) may be used, and other PUCCH resources (e.g., invalid PUCCH resources) that may be located outside the uplink subband in the SBFD slot may be considered unavailable PUCCH resources. If the WTRU is instructed to use an invalid PUCCH resource in the SFBD slot, the WTRU may drop and / or be permitted to drop the PUCCH transmission. If the WTRU is instructed to use an invalid PUCCH resource in the SFBD slot, the WTRU may use PUCCH resources in the nearest and / or latest uplink-only time instance in a future time instance. If the WTRU is instructed to use an invalid PUCCH resource in the SFBD slot, the WTRU may transmit the PUCCH on a default PUCCH resource, which may be a pre-configured (or determined) PUCCH resource in the SFBD slot. The PUCCH resource indices may be reordered, re-indexed, and / or re-indicated to valid PUCCH resources within an SBFD slot. The WTRU may be configured with an "SBFD-specific" PUCCH resource indicator to be used when SBFD is enabled and the original PUCCH resources are invalid. For example, the WTRU may determine that one or more PUCCH resources within an SBFD time instance are invalid. Thus, the WTRU may decide to use the "SBFD-specific" configured PUCCH resources.

[0138] In one or more cases, the WTRU may be configured to determine a PRI association. The WTRU may be configured with a first set (e.g., up to 8) of PUCCH resources. The WTRU may configure and / or receive a PUCCH resource indicator (PRI) as part of scheduling and / or activating DCI, which may indicate the PUCCH resources to be used for PUCCH transmission. The WTRU may receive scheduling information associated with multiple physical uplink shared channel (PUSCH) transmissions. The scheduling information may include a first frequency domain resource allocation (FDRA). In one or more cases, the first set of PUCCH resources may be configured for the case where the WTRU is scheduled in an UL-only time instance, and there may be a second set of PUCCH resources associated with the PUCCH resources in the first set. Thus, when the WTRU is scheduled for PUCCH transmission in an UL-only time instance, the WTRU may use a PRI to map the PUCCH transmission based on the first set of PUCCH resources. However, if the WTRU is scheduled for a PUCCH transmission in the UL subband 512 of the SBFD time instance, the WTRU may use the PRI to map the PUCCH transmission based on a second set of associated PUCCH resources. In one example, the set of PUCCH resources may include a maximum of (e.g., 8) PUCCH resources, but in this mode of operation, for (e.g., a 3-bit PRI), a maximum of (e.g., 16) PUCCH resources (e.g., two PUCCH resource sets) may be configured, with the first set of PUCCH resources associated with the second set of PUCCH resources.

[0139] In one or more cases, a WTRU may be configured with a first group of PUCCH resource sets that may be associated with a first type of time resource (e.g., uplink slots) and a second group of PUCCH resource sets that may be associated with a second type of time resource (e.g., SBFD slots). The starting RB of the PUCCH resources in the first group of PUCCH resource sets may be based on an RB index of the BWP, and the starting RB of the PUCCH resources in the second group of PUCCH resource sets may be based on an RB index in the UL subband. The WTRU may be indicated (e.g., in a DCI) whether use of a PUCCH resource in the second group of PUCCH resource sets is permitted and / or not permitted. If indicated that use of one or more PUCCH resources in the second group of PUCCH resource sets is not permitted, the WTRU may consider the one or more PUCCH resources as available resources for other transmissions (e.g., PUSCH).

[0140] In one or more cases, the WTRU may be configured for independent / separate PUCCH configurations for SBFD and / or non-SBFD Tx / Rx occasions. The WTRU may determine a first FDRA and a second FDRA for non-SBFD slots and SBFD slots. The first FDRA and the second FDRA may use frequency resources or physical resource block (PRB) resources. The WTRU may use the first FDRA for non-SBFD slots and the second FDRA for SBFD slots. The WTRU may use separate frequency resources for SBFD slots and non-SBFD slots based on the first FDRA. In one or more cases, the WTRU may be configured to determine a PUCCH configuration applicable to SBFD. In some solutions, the WTRU may receive a first PUCCH configuration and a second PUCCH configuration, such as PUCCH-Config and / or system information provided by dedicated RRC signaling and / or PUCCH-ConfigCommon provided by dedicated RRC signaling. The WTRU may first determine whether to transmit PUCCH resources from the first PUCCH configuration and / or the second PUCCH configuration based on one of the following: The WTRU may determine the applicable PUCCH configuration based on the type of slot, as described above. For example, the WTRU may transmit PUCCH resources from the first PUCCH configuration if the slot type is "uplink" and from the second PUCCH configuration if the slot type is "SBFD." The WTRU may determine the applicable PUCCH configuration based on the timing of the slot, with respect to slot index and / or system frame number. For example, the WTRU may receive an RRC configuration for a first (or second) set of slots applicable to the first (or second) PUCCH configuration. The first (or second) set of slots may be identified by a periodicity 506 and an offset and / or by a bitmap in which each bit position represents a slot. The SBFD configuration information may indicate PUSCH repetition or transport block (TB) over multiple slots (TBoMS). The WTRU may determine the type of slot for PUSCH transmission.The type of slot may be SBFD or non-SBFD (e.g., DL only, UL only). The WTRU may determine the number of available slots. Determining the number of available slots may include one or more of determining that non-SBFD uplink transmission slots are available and determining that SBFD slots are available only if the second FDRA is within one or more subbands for uplink transmission.

[0141] The WTRU may determine the applicable PUCCH configuration based on implicit and / or explicit instructions and / or configurations. The WTRU may receive PUCCH configuration information. For example, the WTRU may receive an indication of whether to use the first PUCCH configuration and / or the second PUCCH configuration from a field in the DCI. In another example, the WTRU may determine the PUCCH configuration based on the Coreset, search space, and / or RNTI used to decode the corresponding PDCCH 504.

[0142] In one or more cases, the WTRU may then determine PUCCH resources from the first PUCCH configuration and / or the second PUCCH configuration based on at least one of the following solutions. For example, the WTRU may be configured to determine resources for HARQ-ACK 510. In one or more cases, the WTRU may receive a configuration and / or indication of PUCCH resources according to a legacy solution that applies to the PUCCH configuration determined in the first step. For example, the WTRU may receive a PRI from a field of the DCI and determine applicable PUCCH resources from a set of PUCCH resources configured as part of the determined PUCCH configuration. Such a solution may also be applicable in the case of PUCCH repetition. In such a case, the WTRU may determine the PUCCH resources applicable to the PUCCH repetition from the indicated PRI and the PUCCH configuration applicable to the slot in which the PUCCH repetition occurs. This allows for the determination of different PUCCH resources for different PUCCH repetitions. In another example, for a PUCCH carrying HARQ-ACK 510 of only an SPS PDSCH 508, the WTRU may select a PUCCH resource from a set (sps-PUCCH-AN-List) consisting of the determined PUCCH configuration.

[0143] In another example, the WTRU may be configured to determine resources for the periodic CSI, SR, and / or SPS HARQ-ACK 510. In one or more cases, the WTRU may receive a configuration and / or indication of first and second PUCCH resources applicable to the first and second PUCCH configurations, respectively. For example, the WTRU may receive a configuration of first and second PUCCH resource identifiers in a periodic CSI reporting configuration for transmitting periodic CSI, a scheduling request (SR) resource configuration for transmitting SR, and / or an SPS configuration for transmitting HARQ-ACK 510 for SPS. If the WTRU determines that the PUCCH should be transmitted from the first (or second) PUCCH configuration, it may transmit the periodic CSI report, SR, and / or HARQ-ACK 510 on the first (or second) configured PUCCH resource of the first (or second) PUCCH configuration. In another example, the WTRU may be configured to determine other channels. The WTRU may be configured with one or more configured PUSCH resources for an uplink-only time instance (e.g., TDD legacy UL only), and the configured PUSCH resources may be used for an SBFD-configured time instance. In this case, the number and / or length of PRBs, subbands, and / or BWPs configured for the UL-only time instance may span larger subbands, PRBs, and / or BWPs than the uplink subbands, PRBs, and / or BWPs in the SBFD time instance. For example, all RBs within a BWP may be used for the uplink in an uplink-only slot and / or symbol, but a subset of the RBs within the BWP may be used for the uplink in an SBFD slot and / or symbol.

[0144] In one or more cases, a WTRU may be configured for downlink transmission at downlink time instances where one or more UL SBFD subbands, BWPs, and / or PRBs may be enabled and / or disabled. Alternatively, a WTRU may be configured for DL ​​transmission at UL time instances (e.g., time units) where one or more DL SBFD subbands and / or BWP PRBs may be enabled and / or disabled.

[0145] Furthermore, the WTRU may be configured with one or more SPS PDSCH 508 resources for one or more DL-only time instances (e.g., TDD legacy DL only), and the configured PDSCH resources may be used for the SBFD-configured time instances. In one example, SBFD may be configured for one or more uplink PRBs, BWPs, and / or subbands for the legacy DL time instance, and the remaining PRBs, BWPs, and / or subbands may be used for the DL. Alternatively, SBFD may be configured for one or more downlink PRBs, BWPs, and / or subbands in the (e.g., legacy) uplink-only time instance, and the remaining PRBs, BWPs, and / or subbands are used for the UL. In this case, the number and / or length of the PRBs, subbands, and / or BWPs configured for the DL-only time instance may span larger subbands, PRBs, and / or BWPs than the downlink subbands, PRBs, and / or BWPs in the SBFD time instance. For example, all RBs in a BWP may be used for DL ​​in a DL-only slot / symbol, but a subset of the RBs in a BWP may be used for DL ​​in an SBFD slot and / or symbol.

[0146] In one or more cases, the WTRU may be configured to determine PUCCH resources to support repetitions. In one or more cases, the WTRU may be configured to determine an indication of associated PUCCH resources to support PUCCH repetitions. A WTRU configured to transmit PUCCH repetitions may determine the PUCCH resources applicable to each repetition using the following solution: The WTRU may receive for each PUCCH resource in the first (second) PUCCH configuration. In one or more cases, the configuration may include: the number of repetitions applicable if the PUCCH resource is indicated (e.g., by the PRI), and an indication of associated PUCCH resources in another PUCCH configuration (e.g., from the second (or first) PUCCH configuration) applicable to the PUCCH repetition in a slot where the other PUCCH configuration is applicable.

[0147] The WTRU may then determine a reference PUCCH resource from the first PUCCH configuration and / or the second PUCCH configuration based on the indicated PRI. The WTRU may select a PUCCH configuration based on either a fixed rule (e.g., always the first configuration) and / or a PUCCH configuration applicable to the slot in which the initial PUCCH repetition occurs. The WTRU may then determine the number of PUCCH repetitions and the associated PUCCH resource from the configuration provided for the reference PUCCH resource. For each PUCCH repetition, the WTRU selects either the reference PUCCH resource and / or the associated PUCCH resource according to the PUCCH configuration applicable to the slot in which the PUCCH repetition occurs.

[0148] The second rule may include applying a frequency offset to the first PUCCH resource. The second rule may include applying a different mapping for the first PRI to PUCCH resources for transmissions associated with the SFBD configuration information and the first PRI. The second rule may map the first PRI to a second PRI. The second PRI may be used to determine a second PUCCH resource. The second PRI may be used for SBFD uplink transmissions based on its association with a non-SBFD PRI.

[0149] In one or more cases, the WTRU may indicate a PUCCH resource index (PRI) with its associated reporting timing within an associated DCI (e.g., scheduling of DCI for a PDSCH), where the PRI may be interpreted differently based on the associated slot type. For example, if the PRI is associated with a first type of slot (e.g., an uplink slot), the PRI may indicate one of the PUCCH resources within the PUCCH resource set, while when the PRI is associated with a second type of slot (e.g., an SBFD slot), the PRI may indicate which RB within the SBFD slot is determined as an uplink subband, and a given PUCCH resource within the uplink subband may be used for PUCCH transmission.

[0150] In one or more cases, the WTRU may be configured to determine an implicit indication of resource allocation in the SBFD symbol. If the WTRU is not configured with a (dedicated) PUCCH resource configuration, the WTRU may use a default PUCCH configuration (e.g., received in system information such as pucch-ResourceCommon). In one example, the default PUCCH configuration may include parameters for transmission of one or more control information (e.g., HARQ-ACK 510) in the (e.g., initial) uplink BWP. For example, the default PUCCH configuration may indicate parameters such as the PUCCH format, the first symbol, the number of symbols, the PRB offset, the set of initial cyclic shift indexes, etc. Thus, the WTRU may be configured to determine whether / how to implicitly indicate frequency / PRB resources for transmission in the SBFD UL subband 512.

[0151] The WTRU may be configured with the respective uplink transmissions at time instances when an SBFD configuration is enabled (e.g., via a flag indication). The SBFD configuration may include time-domain and frequency-domain configurations for the TDD downlink and / or UL subbands / frequencies / PRBs that may be located within / as part of a flexible time instance (e.g., configured via tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, etc.).

[0152] In one or more cases, the WTRU may determine that the frequency domain resource for the UL transmission at the SBFD time instance is outside the boundaries of the SBFD uplink frequency / subband / PRB. In one example, the WTRU may determine that the PRI configured for the PUCCH transmission does not lie within the boundaries of the respective SBFD uplink frequency / BWP / subband / PRB. The WTRU may determine whether one or more values ​​are provided to the WTRU to explicitly determine the resource location for each UL transmission within the SBFD resource (e.g., frequency shift, re-indexing of PRB ID, indication for PRI within the boundaries of the SBFD UL subband 512, etc.).

[0153] In one or more cases, the WTRU may decide to implicitly define frequency domain resources (e.g., PRBs) for each uplink transmission that are within the boundaries of the SBFD UL subband 512. In one example, the WTRU may decide to use one or more default settings for frequency domain resources for each uplink transmission. The WTRU may be configured with a flag indication to enable / disable the implicit determination of PRBs / frequency domain resources.

[0154] In one example, the WTRU may determine that, for a PUCCH transmission, the configured PRI is mapped to a PRB / subband that is outside the SBFD UL subband 512 / PRB boundary. Thus, the WTRU may decide to use the (default) PUCCH setting / configuration that was configured before the dedicated PUCCH resources were configured (e.g., pucch-ResourceCommon), for example, for PUCCH resource allocation. In that case, the WTRU may decide to reinterpret / reindex the (default) PUCCH setting / configuration to correspond to the frequency / subband / PRB allocation within the SBFD UL subband 512 / PRB boundary. For example, the WTRU may consider the PRB offset / starting PRB configured in the (default) PUCCH setting / configuration with respect to the SBFD UL subband 512 / PRB boundary.

[0155] In one example, a WTRU may be configured with SBFD at a time instance, where the starting PRB corresponding to the subband / PRB / BWP of SBFD may be indicated by PRB index N1, and the last PRB corresponding to the subband / PRB / BWP of SBFD may be indicated by PRB index N2. Thus, the WTRU may consider the PRB offset / starting PRB configured in the (default) PUCCH setting / configuration with respect to the SBFD UL starting PRB index N1. For example, if the PRB offset / starting PRB indicates 0 and / or 4, the WTRU may consider the respective PRB index as N1 and / or N1+4, respectively.

[0156] In one or more cases, the WTRU may determine that no explicit or implicit indication is provided (e.g., no implicit indication is allowed based on an enable / disable flag) to determine the PRB / frequency domain resource within the SBFD UL subband 512 / PRB / BWP. Thus, the WTRU may decide to skip uplink transmissions in the respective SBFD UL subbands / PRBs. The WTRU may determine to use the earliest UL SB / slot for the respective uplink transmission (e.g., for a PUCCH transmission corresponding to an SPS PDSCH 508 configuration).

[0157] In one or more cases, the WTRU may be configured to determine the reliability of resource allocation in the SBFD symbol. The WTRU may receive and / or be configured with one or more Semi-Persistent Scheduling (SPS) configurations in the BWP (e.g., via sps-Config and / or sps-ConfigToAddModList), where the SPS configurations may include transmission periodicity, PDSCH aggregation factor, etc. The WTRU may receive DCI (e.g., format 1_1 and / or 1_2) that may activate one or more SPS transmissions (e.g., CRC scrambled with CS-RNTI), where the DCI may include time and frequency configurations for each PDSCH transmission. In one example, the WTRU may receive a HARQ-ACK 510 transmission (e.g., K1 514) and the time and resources for each PUCCH transmission, including a process ID.

[0158] Upon receiving the first DL (e.g., PDSCH), the WTRU may perform a first uplink (e.g., PUCCH, PUSCH) transmission on the SBFD UL subband 512. The WTRU may further monitor, detect, and / or receive a second DL reception (e.g., SPS PDSCH 508 corresponding to the first configured DL and / or PDCCH 504 scheduling a new grant). Based on the second received DL, the WTRU may determine whether to indicate / confirm that the first transmitted UL was received (e.g., at the gNB). If no confirmation is received, the WTRU may decide to retransmit the UL (e.g., PUCCH / HARQ-ACK 510) (e.g., for reliability purposes). In one example, the WTRU may decide to retransmit the PUCCH / HARQ-ACK 510 at the latest uplink-only time instance after the respective time instance (e.g., as indicated by K1 514). This behavior may be configurable (e.g., by the gNB) through different configurations.

[0159] In one or more cases, the WTRU may receive at least one configuration (e.g., mode, operation, behavior, operating mode, etc.) for UL transmission behavior in the following SBFD slot (or symbol). For example, the WTRU may be configured for a one-time transmission. In another example, the WTRU may be configured for a conditional fallback transmission. In another example, the WTRU may be configured for a conditional repeated base transmission.

[0160] For a one-time transmission configuration, for a scheduled / instructed UL (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) transmission, the WTRU may perform a single UL transmission in a valid / instructed slot (or symbol), which may be an SBFD slot / symbol, a "flexible" slot / symbol, and / or an "uplink" slot / symbol, based on the indicated parameter of the valid slot (e.g., the K1 514 value indicated by the DCI). In one example, the UL transmission may include a PUCCH transmission. The PUCCH transmission may be performed in response to receiving a DL grant for scheduling a DL reception (e.g., a PDSCH). The DL grant may indicate a value (e.g., K1 514) that may indicate (e.g., suggest) an SBFD slot (or symbol), for example, within a separately configured / indicated legacy "downlink" slot and / or within a legacy "downlink" slot (e.g., by a tdd-UL-DL-config parameter that configures a slot / symbol-level time-domain pattern based on "D", "F", "U", and / or by a slot format indicator (SFI) that indicates a symbol-level time-domain pattern based on "D", "F", "U" via a DCI). In response to determining a K1 514 value that indicates (e.g., suggests) one of an SBFD slot (or symbol), an "F" slot (or symbol), and a "U" slot (or symbol), the WTRU may perform a PUCCH transmission (one time, e.g., one time only) on the time instance indicated by the K1 514 value.

[0161] In one example, the WTRU may determine that the slot (or symbol) indicated by the K1 514 value is an SBFD slot (or symbol). In response to the determination, the WTRU may perform a PUCCH transmission (one time, e.g., one-time only) on the SBFD slot (or symbol) indicated by the K1 514 value, and the WTRU may identify / determine that the SBFD slot (or symbol) indicated by the K1 514 value is a valid UL transmission timing, but the SBFD slot is included in a separately configured / indicated legacy "D" slot. This may provide an advantage in terms of latency reduction for UL transmissions that may be performed earlier than legacy UL-only time instances, which may further improve the overall system latency performance of the communications system (e.g., for latency-sensitive use cases such as URLLC), including both DL and UL.

[0162] In one example, the WTRU may determine that the slot (or symbol) indicated by the K1 514 value is a "flexible (F)" slot (or symbol). In response to the determination, the WTRU may perform a PUCCH transmission (one time, e.g., one time only) in the "F" slot (or symbol) indicated by the K1 514 value.

[0163] In one example, the WTRU may determine that the slot (or symbol) indicated by the K1 514 value is an "uplink (U)" slot (or symbol). In response to the determination, the WTRU may perform a PUCCH transmission (one time, e.g., one and only time) in the "U" slot (or symbol) indicated by the K1 514 value.

[0164] With respect to a conditional fallback transmission configuration, for a scheduled / instructed UL (e.g., PUCCH, PUSCH, SRS, and / or PRACH) transmission to be performed at a first time instance, the WTRU may determine, based on one or more predefined and / or preconfigured conditions being met, that the UL transmission should not be performed but rather fallback to be performed at a second time instance.

[0165] In one example, the UL transmission may include a PUCCH transmission. The PUCCH transmission may be performed in response to receiving a DL grant for scheduling DL reception (e.g., a PDSCH). The DL grant may indicate a K1 514 value that may indicate (e.g., suggest) an SBFD slot (or symbol), for example, within a separately configured / indicated legacy “downlink” slot and / or within a downlink-only time instance (e.g., by a tdd-UL-DL-config parameter that configures a slot / symbol-level time-domain pattern based on “D”, “F”, “U”, and / or by a slot format indicator (SFI) that indicates a symbol-level time-domain pattern based on “D”, “F”, “U” via a DCI). The WTRU may determine that the first time instance indicated by the K1 514 value is the SBFD slot (or symbol). The WTRU may further determine that one or more conditions are met at the first time instance, and based thereon, the WTRU may determine that UL transmission is a fallback to be performed at the second time instance. In one example, the second time instance may be a (legacy) UL-only and / or flexible time instance.

[0166] In one example, the second time instance may be the latest (legacy) UL-only time instance after the first time instance (e.g., slot / symbol indicated by K1 514). In one example, the second time instance may be the latest (legacy) flexible time instance after the first time instance (e.g., slot / symbol indicated by K1 514).

[0167] In one or more cases, a "conditional fallback transmission" (e.g., configuration 2) may be associated with and / or applied to a "one-time transmission" (e.g., configuration 1), and the WTRU may determine an operation mode based on one or more conditions (e.g., based on configuration 1 and / or configuration 2). If one or more of the following conditions apply, the WTRU may determine configuration 2 instead of configuration 1. For example, if the scheduled / configured / instructed frequency domain resources (e.g., a set of PRBs) of the UL (e.g., PUCCH) transmission are not (completely) comprised / contained within the uplink subband on the SBFD slot / symbol, the SBFD slot / symbol includes (or is determined based on) the first time instance. In another example, if the scheduled / configured / instructed frequency domain resources (e.g., a set of PRBs) of the UL (e.g., PUCCH) transmission are at least partially not comprised / contained within the uplink subband on the SBFD slot / symbol, the SBFD slot / symbol includes (or is determined based on) the first time instance. In another example, if neither the above explicit nor implicit instructions apply, a conditional fallback transmission may be applied.

[0168] For a conditional repetition-based transmission configuration, in the case of a scheduled / instructed UL (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) transmission, the WTRU may perform the UL transmission at least once at a first time instance, which may be a valid / instructed slot (or symbol), e.g., an SBFD slot / symbol, a "flexible" slot / symbol, and / or an "uplink" slot / symbol, based on the indicated parameters of the valid slot (e.g., the K1 514 value indicated by the DCI), and if applicable, the WTRU may perform the UL transmission again at a second time instance. This may provide advantages in terms of reliability and robustness in the considered communication system.

[0169] In one example, the UL transmission may include a PUCCH transmission. The PUCCH transmission may be performed in response to receiving a DL grant for scheduling DL reception (e.g., a PDSCH). The DL grant may indicate a K1 514 value that may indicate (e.g., suggest) an SBFD slot (or symbol) within a separately configured / indicated legacy "downlink" slot and / or within a "downlink-only" time instance (e.g., by a tdd-UL-DL-config parameter that configures a slot / symbol-level time-domain pattern based on "D", "F", "U", and / or by a slot format indicator (SFI) that indicates a symbol-level time-domain pattern based on "D", "F", "U" via a DCI).

[0170] In one or more cases, the WTRU may determine that the first time instance (e.g., indicated by the K1 514 value) is an SBFD slot (or symbol). Thus, the WTRU may determine to perform an UL retransmission on a second time instance (which may be later than the first time instance). The WTRU may be configured with a flag indication to enable / disable retransmission at the second time instance. The WTRU may be explicitly configured with the second time instance and / or the WTRU may implicitly determine the second time instance. In one example, the second time instance may be a (legacy) "uplink only" (or "F") slot (or symbol). In one example, the second time instance may be the latest (legacy) "uplink only" slot (or symbol) after the first time instance (e.g., the slot / symbol indicated by K1 514). In one example, the second time instance may be the latest (legacy) "F" slots (or symbols) after the first time instance (e.g., the slot / symbol indicated by K1 514). If the UL transmission is based on a configuration for Tx repetition (e.g., slot-level repetition, intra-slot repetition, etc.), the WTRU may perform the UL transmission repetitively after the second time instance based on the configuration for Tx repetition.

[0171] In one or more cases, the WTRU may monitor, detect, and / or receive a new grant in the PDCCH scheduling 504 during an UL transmission in the SBFD UL subband 512. The WTRU may receive scheduling information associated with multiple physical uplink shared channel (PUSCH) transmissions. The scheduling information may include a first frequency domain resource allocation (FDRA). When the WTRU (successfully) receives a PDCCH, for example, within a predefined and / or preconfigured time window, the WTRU may identify / determine that it (e.g., the PDCCH 504) is an acknowledgment of reception (at the gNB) of the UL transmission. Based on the identification / determination, the WTRU may decide not to apply conditional fallback Tx (e.g., based on a conditional fallback transmission configuration) and / or conditional repetition-based Tx (e.g., based on a conditional repetition-based transmission configuration).

[0172] In one or more cases, the WTRU may be configured to determine enhancements for multiple transmissions (e.g., repetitions) in an SBFD framework. The WTRU may be configured to perform Tx / Rx repetitions, for example, to enhance Tx / Rx coverage. For example, the WTRU may use multi-slot PUSCH / PUCCH transmissions and / or multi-slot PDSCH / PDCCH 504 receptions. In a TDD framework with SBFD configurations enabled, multi-slot UL transmissions and / or DL ​​receptions may span SBFD slots / symbols / time instances and legacy UL-only and DL-only time instances, respectively. Thus, the WTRU may be configured to determine whether / how to perform (multi-slot) UL / DL repetitions, and the repetition instances may span both SBFD time instances and UL-only / DL-only time instances.

[0173] In one or more cases, the WTRU may be configured for multiple UL transmissions (e.g., repetitions). The WTRU may be configured, instructed, and / or may receive configuration information instructing it to perform PUCCH and / or PUSCH repetitions. The number of PUCCH repetitions may be indicated as part of a configuration (e.g., a PUCCH format and / or PUCCH resource configuration) that the WTRU may receive (e.g., from a gNB). The number of PUSCH repetitions may be indicated by a time domain resource allocation (TDRA) field in the DCI and / or may be included as part of a configured grant configuration.

[0174] The WTRU may be configured, instructed, and / or may receive configuration information that suggests transmitting repetitions (e.g., PUSCH repetitions) using the "available slot count." In this case, the WTRU may skip PUSCH repetitions in slots in which PUSCH repetitions are dropped according to the first (e.g., semi-static) configuration. For example, PUSCH repetitions that overlap with downlink symbols according to the first (e.g., semi-static) configuration are not counted. For example, if the WTRU is configured and / or instructed to transmit N repetitions, the skipped repetitions are not counted and the actual transmitted repetitions are N. In another example, skipped and / or dropped repetitions are counted and the actual number of repetitions may be less than N.

[0175] If SBFD is applied (e.g., in one or more time units, such as one or more symbols and / or slots), the WTRU may perform UL repetition, such as PUSCH and / or PUCCH repetition, using at least one of the following solutions: PUSCH and / or PUCCH may be used as a non-limiting example of UL transmission. Another transmission may be used and still be consistent with this disclosure.

[0176] In one or more cases, the WTRU may determine that the set of PUSCH (or PUCCH) repetitions occur only in slots of the same type as the slot in which the first and / or initial transmission occurs. For example, if the first PUSCH transmission occurs in an SBFD slot, subsequent PUSCH repetitions may occur in (or only occur in) SBFD slots, not in UL-only time instances / slots. Conversely, if the first PUSCH transmission occurs in an UL-only time instance, subsequent PUSCH repetitions may occur in (or only occur in) UL-only time instances (or flexible time instances), not in SBFD time instances. The WTRU may send the first PUSCH transmission using a time division duplex (TDD) configuration. For PUSCH repetitions for which the "available slot count" is not configured, the WTRU may drop PUSCH repetitions that overlap an SBFD slot. Optionally, such a solution may be applicable only if the initial transmission occurs in an UL-only time instance. The SBFD configuration information may indicate PUSCH repetition or transport block (TB) over multiple slots (TBoMS). The WTRU may determine a slot type for PUSCH transmission. The slot type may be SBFD or non-SBFD. The WTRU may determine the number of available slots. Determining the number of available slots may include one or more of determining that non-SBFD uplink transmission slots are available and determining that SBFD slots are available only if the second FDRA is within one or more subbands for uplink transmission.

[0177] In one or more cases, the WTRU may determine that PUSCH (or PUCCH) transmission and / or repetition is to be performed in an SBFD time instance under the condition that the frequency allocation of the PUSCH (or PUCCH) completely overlaps or is contained within the subbands available for uplink transmission in the SBFD slot. The WTRU may make this determination under the condition that it has received an indication (e.g., DCI and / or MAC CE) and / or configuration that such transmission is permitted.

[0178] Turning now to Figure 6, an example 602 of PUSCH repetition in the presence of SBFD is illustrated. In one or more cases, a WTRU may be configured for uplink repetition with SBFD for the PUSCH, as shown in Figure 6. The WTRU may receive an indication (e.g., in a DCI) that instructs it to send multiple PUSCH transmissions. The multiple transmissions may be repetitions (e.g., transport blocks (TBs)), transmissions of different TBs, and / or a combination of TB repetitions and different TBs. The DCI may be an UL grant DCI.

[0179] In one or more cases, a WTRU may receive a first indication and / or configuration (e.g., in a DCI) of a first frequency domain resource allocation (FDRA) for PUSCH transmission in a first type of time unit (e.g., an UL and / or a flexible time unit). The WTRU may receive the first FDRA, the second FDRA, and / or a frequency offset in scheduling information. The scheduling information may include downlink control information. The WTRU may receive the second FDRA or frequency offset in a medium access control (MAC) control element (CE), a radio resource control (RRC) configuration, or downlink control information. In a non-SBFD slot (e.g., an UL-only slot 604, 610), the WTRU may use frequency resources indicated by the first FDRA (e.g., the first FDRA determined from a DCI indication index). The UL-only slot 604, 610 may comprise a portion that is a TDD UL subband and / or a portion that is a PUSCH repetition in the UL-only slot and the SBFD slot. The UL-only slots 604, 610 may be multiple TDD UL slots. If the PUSCH of the multiple PUSCH transmissions (e.g., repetitions) is transmitted in a second type of time unit (e.g., SBFD time unit), the WTRU may determine a second FDRA applicable to the PUSCH transmissions in the second type of time unit. The first FDRA and the second FDRA may be configured as part of a configured grant configuration and / or may be indicated in a field of a configured grant activation DCI. The WTRU may send a first PUSCH transmission of the multiple PUSCH transmissions using a first frequency resource determined based on the first FDRA. The WTRU may determine that at least a second PUSCH transmission of the multiple PUSCH transmissions should be sent using at least one OFDM symbol of the one or more OFDM symbols. The WTRU may determine, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in one or more subbands for uplink transmission and / or one or more subbands for downlink reception of at least one OFDM symbol.The WTRU may receive one or more of a second FDRA or a frequency offset for the second PUSCH transmission. The WTRU may determine a second frequency resource for sending the second PUSCH transmission based on the one or more of the second FDRA or the frequency offset. The second frequency resource may be included in one or more subbands for uplink transmission of at least one OFDM symbol. The WTRU may send the second PUSCH transmission using the second frequency resource.

[0180] In one or more cases, the WTRU may determine the second FDRA under the condition that the first frequency allocation of the PUSCH does not completely overlap and / or does not fall within the subbands available for uplink transmission in the SBFD time unit. The WTRU may determine the second FDRA according to one of the following solutions:

[0181] In one or more cases, the WTRU may be configured for an alternative FDRA configuration. In one or more cases, the second FDRA may be indicated in a DCI that indicates multiple PUSCH transmissions (e.g., repetitions). The second FDRA may be received via an RRC configuration, such as a configured grant configuration.

[0182] In one or more cases, the WTRU may be configured for reinterpretation and / or reindexing. In one or more cases, the second FDRA may be calculated from the first FDRA and at least one parameter. The at least one parameter may include, for example, a frequency offset 612, e.g., with respect to a resource block. The second FDRA may be determined by applying the frequency offset 612 to the first FDRA. In the SBFD slots 606, 608, the WTRU may calculate the frequency offset 612 associated with the first FDRA or the second (2 nd) FDRA (e.g., may use a frequency resource indicated by an offset 612 determined from a second FDRA or DCI indication index, an offset 612 included in the DCI, or a MAC-CE indication offset 612. The WTRU may determine the second FDRA from the first FDRA by applying a frequency offset. The frequency offset may be a resource block (RB) offset. The frequency offset may be configured or indicated using a medium access control (MAC) control element (CE) or downlink control information (DCI). The frequency offset may be included in the indication or configuration. The WTRU may use the first FDRA and the frequency offset to determine a second frequency resource for sending the second PUSCH transmission. The SBFD slots 606, 608 may be a portion that is a TDD DL subband, The PUSCH repetitions may include portions that are UL subbands and / or portions that are PUSCH repetitions in UL-only slots and SBFD slots. SBFD slots 606, 608 may be multiple DL slots. As shown in FIG. 6, the subbands occupied for transmission of PUSCH repetitions in UL-only slots and SBFD slots may vary depending on whether the PUSCH repetitions are in UL-only slots (e.g., 604) or SBFD slots (e.g., 606). To avoid collisions with downlink reception, PUSCH repetition transmissions may be scheduled and / or configured to be transmitted on UL subbands.

[0183] The second PUCCH resource may be within a slot symbol. The PUCCH configuration information may include a transmission repetition count. The PUCCH may be transmitted using Frequency Domain Resource Allocation (FDRA). The DCI may indicate that the first PRI is for a HARQ-ACK transmission. Determining the second PUCCH resource may include re-indexing the PUCCH resource. The transmission of the PUCCH transmission may be in a time unit configured for SBFD.

[0184] The at least one parameter may be explicitly configured by RRC and / or indicated by a field in the MAC CE and / or DCI. Alternatively, the at least one parameter may be implicitly determined from a configuration of SBFD, such as from the lowest RB that can be used for uplink transmission. Alternatively, the at least one parameter may be a positive and / or negative offset 612 value used to determine the second FDRA by re-indexing the start (RB) of the first FDRA so that the second FDRA completely overlaps or is contained in the subbands available for uplink transmission in the SBFD time unit. The WTRU may apply this solution under the condition that it has received an indication and / or configuration (e.g., a flag indicating "enabled") (e.g., by DCI and / or MAC CE) that such transmission via the second FDRA is allowed in the second type of time unit. Otherwise, the WTRU may transmit (e.g., only transmit) a PUSCH (e.g., repetition) via a first type of slot. The WTRU may transmit PUSCH repetitions on any of the UL subbands in the SBFD slots 606, 608.

[0185] In one or more cases, the WTRU may be configured for association of a starting RB. In one or more cases, the start (e.g., RB) of the first FDRA may be associated with a starting (e.g., RB) index within an uplink subband in an SBFD time unit. Thus, the WTRU may determine a second starting (RB) index and a respective FDRA based on an association between the starting (RB) index of the first FDRA and a UL subband within the SBFD time instance. The WTRU may determine the start of the second PUSCH transmission based on the starting resource block (RB) of the SBFD or the starting RB of the second FDRA. The WTRU may determine the second FDRA from an indication or SBFD configuration information. The WTRU may receive the association of the starting index of the first FDRA and the second FDRA as part of SBFD configuration and / or PUSCH configuration and / or PUSCH activation (e.g., via RRC, MAC-CE, DCI). The WTRU may receive the second FDRA and / or frequency offset in the scheduling information. The scheduling information may include downlink control information. The WTRU may receive the second FDRA or frequency offset in a Medium Access Control (MAC) Control Element (CE), a Radio Resource Control (RRC) configuration, or downlink control information. The WTRU may receive a flag indication (e.g., via a DCI and / or MAC CE) regarding activation / deactivation of using the association of the starting RB.

[0186] The described solution may be applicable to a set of PUCCH occasions and / or repetitions for a PUCCH transmitted according to a PUCCH configuration.

[0187] In one or more cases, the WTRU may be configured for PUCCH repetition. The WTRU may be configured to perform UL transmission based on PUCCH repetition, which may be time-domain-multiplexed (TDMed) repetition based on higher layer configuration parameters, such as "nrofSlots," which indicates the number of repetitions (of the same PUCCH content / message).

[0188] In one example, a WTRU may be configured with PUCCH resources, and one or more configuration parameters for the PUCCH resources may include a PUCCH-FormatConfig parameter, which may include a parameter for "nrofSlots." In another example, a WTRU may be configured with PUCCH resources, and one or more configuration parameters for the PUCCH resources may directly include a parameter indicating the number of repetitions, e.g., "pucch-RepetitionNrofSlots."

[0189] Upon receiving such a configuration (e.g., “nrofSlots”, “pucch-RepetitionNrofSlots”, etc.), the WTRU may identify / determine that a PUCCH resource carries uplink-control-information (UCI) and that the same PUCCH resource in another slot or slots carries a repetition of the UCI to be transmitted by the WTRU.

[0190] The WTRU may further be configured with a multi-TRP (mTRP)-based repetition scheme (or operating mode), in which case the WTRU may be configured with at least two spatial domain parameters (e.g., as "spatial relationship information" and / or an UL transmission configuration indicator, UL-TCI and / or a joint DL / UL TCI, respectively). Each of the spatial domain parameters may be associated / used for each Tx (occasion) of the repeated UL transmission. The spatial domain parameters (e.g., of the at least two configured spatial domain parameters) may include a source reference signal (RS) as the WTRU's spatial domain reference for generating / determining the spatial domain filter (or filter coefficients) used for the UL transmission.

[0191] A problem / challenge that may be solved is that some of the PUCCH repetition-based transmissions coincide with DL reception in SBFD slots / symbols if allowed in SBFD slots / symbols, at least when such PUCCH repetitions are configured in the WTRU.

[0192] In one or more cases, the WTRU may receive a configuration for PUCCH repetition, where at least one symbol for the PUCCH repetition occurs in one or more SBFD symbols (e.g., in a "D" symbol) and / or in an "F" and / or "U" symbol (e.g., in one or more UL subbands). The WTRU may receive a DL grant / configuration / instruction to receive a DL signal (or channel) in a repeated symbol of at least one or more SBFD symbols. One or more of the following may apply:

[0193] In a first example (e.g., operating mode 1), the WTRU may drop transmissions for all Tx occasions of the PUCCH repetition, and the WTRU may receive the DL signal (or channel) instead, which may provide advantages in terms of reduced WTRU complexity and simplified operating behavior in a communication system employing SBFD operation.

[0194] In a second example (e.g., operating mode 2), the WTRU may be configured for selective transmission. The WTRU may transmit one or more non-overlapping TX occasions (of a PUCCH repetition), for example, if no overlap is found / determined in the time domain and / or if up to X symbols overlap, where a value of X>0 may be predefined and / or preconfigured and / or instructed. The WTRU may drop the transmission of other TX occasions of the overlapped PUCCH repetition, and instead, the WTRU may receive a DL signal (or channel) on the overlapped symbols. This may allow both the DL and UL links to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be transmitted as part of the PUCCH repetition.

[0195] In some cases, the WTRU may be configured for per-PRI code point configuration. The WTRU may transmit a PUCCH Tx occasion (of a PUCCH repetition) using a PUCCH resource indicated by the codepoint of the PRI field in the DCI that scheduled DL signal (or channel) reception, where the WTRU may be configured with a PUCCH resource used for an SBFD slot / symbol that has a valid frequency resource allocation within the UL subband within the SBFD slot / symbol. The WTRU may be configured with a second PUCCH resource (e.g., mapped to a second codepoint within the same PRI field) used for a (legacy) "U" (or "F") slot / symbol that may have a second frequency resource allocation that is not fully covered within the UL subband.

[0196] In some cases, the WTRU may be configured for implicit interpretation of alternative resources. The WTRU may transmit a PUCCH Tx occasion (of a PUCCH repetition) using a first set of frequency resource allocation parameters (e.g., one or more PRBs) configured for the PUCCH resource indicated by the codepoint of the PRI field in the DCI that scheduled DL signal (or channel) reception. The WTRU may be configured with a PUCCH resource including two different frequency resource allocation parameter sets, e.g., a first set of frequency resource allocation parameters for SBFD slots / symbols (in the UL subband) and a second set of frequency resource allocation parameters for (legacy) "U" (or "F") slots / symbols (within the UL-BWP, but which may exceed the UL subband and / or may be at least partially outside the UL subband).

[0197] In some cases, the WTRU may be configured for PUCCH resource indicator association. The WTRU may transmit a PUCCH Tx occasion (of a PUCCH repetition) using a PUCCH resource indicated by a codepoint of the PRI field in the DCI that scheduled DL signal (or channel) reception, where the WTRU may be configured with a PUCCH resource used for an SBFD slot / symbol that has a valid frequency resource allocation in the UL subband within the SBFD slot / symbol. The WTRU may be configured with a second PUCCH resource that has association / linkage with the PUCCH resource by higher layer signaling, e.g., RRC and / or MAC-CE, and that is not mapped to another codepoint within the same PRI field. If the WTRU identifies / determines to transmit a second PUCCH Tx occasion in a (legacy) U" (or "F") slot / symbol in response to receiving the same code point in the PRI field, the WTRU may transmit the second PUCCH Tx occasion using the second PUCCH resource (associated / linked to the PUCCH resource) based on identifying and determining the association / linkage.

[0198] In some cases, the WTRU may be configured for selective transmission (based on the TCI state). For example, in Example 2A (e.g., operating mode 2A), the WTRU may transmit a TCI (e.g., beam and / or time / frequency domain channel large-scale characteristic / quasi-co-location (QCL) type) configured and / or instructed such that one or more TX occasions (of a PUCCH repetition) are overlapped with the DL, but the UL and DL are identical (or associated with the same set of TCIs), and the WTRU may report its capabilities for such simultaneous Tx (e.g., as part of a PUCCH repetition) and Rx (of the DL). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU.

[0199] In some cases, the WTRU may be configured for selective transmission (based on a repetition pattern). For example, in Example 2B (e.g., operating mode 2B), the WTRU may transmit one or more TX occasions (of PUCCH repetitions) that are indicated with the same (or predefined and / or preconfigured pattern) spatial relationship information (or UL-TCI and / or TCI) and that do not overlap with the DL based on a configured repetition pattern (e.g., “cyclic Mapping” and / or “sequential Mapping”), e.g., when no overlap is found / determined in the time domain and / or when up to X symbols overlap, where a value of X>0 may be predefined and / or preconfigured and / or indicated. A “cyclic Mapping” pattern may refer to a first Tx occasion using a first TCI and a second Tx occasion using a second TCI, and these two patterns of occasions are repeated until the last Tx occasion is reached. A "sequentialMapping" pattern may mean a first Tx occasion using a first TCI, a second Tx occasion using the first TCI, a third Tx occasion using the second TCI, and a fourth Tx occasion using the second TCI, with these four occasion patterns repeated until the last Tx occasion is reached. The WTRU may drop transmissions of other Tx occasions of the overlapped PUCCH repetition, and instead, the WTRU may receive a DL signal (or channel) on the overlapped symbols. This may allow both the DL and UL links to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be transmitted as part of the PUCCH repetition.

[0200] In some cases, the WTRU may be configured to determine that all Tx occasions of a PUCCH repetition overlap with the DL, and depending on the determination, the WTRU may conditionally implement Example 1 (Operation Mode 1) as a fallback behavior.

[0201] In a third example (e.g., operating mode 3), the WTRU may drop DL reception and (repeatedly) transmit UL unless the DL may at least partially include SSB, TRS, special monitoring occasions (e.g., looking for random access responses (RARs), beam failure recovery (BFR) responses, and / or specifically configured / instructed DL signals / channels, etc.), in which case the WTRU may instead drop transmissions of all UL Tx occasions and / or parts of UL Tx occasions that may overlap with itself.

[0202] In one or more cases, the WTRU may be configured for PUSCH repetition. The WTRU may be configured to perform UL transmission based on PUSCH repetition, which may be time-domain multiplexed (TDMed) repetition based on a higher layer configuration parameter, e.g., "numberOfRepetition," which indicates the number of repetitions (of the same PUSCH content / packet). In one example, the WTRU may be configured with a parameter (e.g., "numberOfRepetitions") in a codepoint (or field state) of a time-domain resource allocation (TDRA) field in the UL-DCI (e.g., DCI format 0_1 ​​and / or 0_2, etc.).

[0203] The problem / challenge that may be solved is that some of the PUSCH repetition-based transmissions collide with DL reception in SBFD slots / symbols if allowed in SBFD slots / symbols, at least when such PUSCH repetitions are configured in the WTRU.

[0204] In one or more cases, the WTRU may receive an UL grant / configuration / instruction for a PUSCH repetition, and at least one symbol for the PUSCH repetition may be included in one or more SBFD symbols (e.g., a "D" symbol) and / or an "F" and / or "U" symbol (in one or more UL subbands). If the WTRU receives a DL grant / configuration / instruction to receive a DL signal (or channel) on a duplicated symbol of at least one or more SBFD symbols, one or more of the following examples (e.g., Example 1, Example 2, and Example 3) apply. For Example 1 (e.g., operational mode 1), the WTRU may drop transmissions of all Tx occasions of the PUSCH repetition (e.g., of PUSCH repetition type A) and / or all actual repetitions (e.g., of PUSCH repetition type B), and instead, the WTRU may receive the DL signal (or channel). This may provide advantages in terms of reduced WTRU complexity and simplified operational behavior in communication systems employing SBFD operation.

[0205] For example, with respect to Example 2 (e.g., Operational Mode 2), the WTRU may be configured for selective transmission. For example, the WTRU may transmit one or more non-overlapping TX occasions (of a PUSCH repetition) if, for example, no overlap is found / determined in the time domain, or if up to Y symbols overlap, where a value of Y>0 may be predefined and / or preconfigured and / or instructed. The WTRU may drop the transmission of other TX occasions of the overlapped PUSCH repetition, and instead, the WTRU may receive a DL signal (or channel) on the overlapped symbols. This may improve system throughput and operational efficiency / flexibility, as both the DL and UL links may be used and at least non-overlapping symbols may be transmitted as part of the PUSCH repetition. The WTRU may be configured for selective transmission (based on the TCI state). For example, in Example 2A (e.g., operating mode 2A), the WTRU may transmit a TCI (e.g., beam and / or time / frequency domain channel large-scale characteristic / quasi-co-location (QCL) type) configured and / or instructed such that one or more TX occasions (of a PUSCH repetition) are overlapped with the DL, but the UL and DL are identical (or associated with the same set of TCIs), and the WTRU may report its capabilities for such simultaneous Tx (e.g., as part of a PUSCH repetition) and Rx (of the DL). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU. In one example, a WTRU may transmit with one or more TX occasions (of a PUSCH repetition) overlapping with the DL, with a first WTRU panel used for Tx and a second UL panel used for DL, and the WTRU may report its capabilities for such simultaneous Tx (e.g., as part of a PUSCH repetition) and Rx (of the DL) across at least two different WTRU panels (or antenna groups and / or different Tx / Rx (hardware) entities, etc.). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU.The WTRU may be configured for selective transmission (based on a repetition pattern). For example, in Example 2B (e.g., operating mode 2B), the WTRU may transmit one or more TX occasions (of PUSCH repetitions) indicated with the same (or predefined and / or preconfigured pattern) spatial relationship information (or UL-TCI and / or TCI) and that do not overlap with the DL based on a configured repetition pattern (e.g., “cyclic Mapping” and / or “sequential Mapping”), e.g., when no overlap is found / determined in the time domain and / or when up to Y symbols overlap, where a value of Y>0 may be predefined and / or preconfigured and / or indicated. A “cyclic Mapping” pattern may refer to a first Tx occasion using a first TCI and a second Tx occasion using a second TCI, and these two occasion patterns are repeated until the last Tx occasion is reached. A "sequentialMapping" pattern may mean a first Tx occasion using a first TCI, a second Tx occasion using the first TCI, a third Tx occasion using the second TCI, and a fourth Tx occasion using the second TCI, with these four occasion patterns repeated until the last Tx occasion is reached. The WTRU may drop transmissions on other Tx occasions of the overlapped PUSCH repetition, and instead, the WTRU may receive a DL signal (or channel) on the overlapped symbols. This may allow both the DL and UL links to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be transmitted as part of the PUCCH repetition.

[0206] In one or more cases for Example 2, the WTRU may be configured for alternative FDRA. If such overlap for DL ​​is detected, identified, and / or determined at the WTRU, instead of dropping the transmission, the WTRU may use (or be configured to use) a different frequency domain resource allocation to transmit one or more TX occasions (of PUSCH repetitions). To this end, the WTRU may receive a configuration / indication of a different frequency domain resource allocation (e.g., a set of PRBs) to be used for transmission.

[0207] The WTRU may determine that all Tx occasions of the PUSCH repetitions overlap in the DL, and depending on the determination, the WTRU may conditionally implement example 1 (operating mode 1) as fallback behavior.

[0208] In one or more cases related to Example 3 (e.g., Operational Mode 3), the WTRU may drop DL reception and (repeatedly) transmit UL unless the DL includes at least (partially) an SSB, TRS, special monitoring occasion (e.g., looking for a random access response (RAR), beam failure recovery (BFR) response, and / or a specifically configured / instructed DL signal / channel, etc.), in which case the WTRU may instead drop transmissions of all UL Tx occasions and / or parts of UL Tx occasions that may overlap with itself.

[0209] In one or more cases, the WTRU may be configured for PDCCH repetition. The WTRU may be configured to perform DL reception based on PDCCH repetition, which may be time-domain multiplexed (TDMed) repetition, based on higher layer configuration parameters, such as "searchSpaceLinking," which indicates two linked search spaces in which PDCCH candidates (e.g., identical PDCCH and / or DCI content) may be repeatedly transmitted (e.g., to be associated with a search space set).

[0210] The problem / challenge that can be solved is that, at least when such PDCCH repetition is configured in the WTRU, if allowed in the SBFD slot / symbol, at least one linked PDCCH candidate (one of at least two linked PDCCH candidates associated with a search space set based on a parameter, e.g., "searchSpaceLinking") collides (e.g., in the time domain) with the UL transmission of the SBFD slot / symbol.

[0211] In one or more cases, when a WTRU is configured with (and monitors) two linked PDCCH candidates (e.g., at least via TDM), if the WTRU determines that at least one of them overlaps (for at least one symbol) with a (scheduled / configured / instructed) UL Tx within an SBFD symbol, one or more of the following may apply:

[0212] For example, the condition for determining whether overlapped may be based either on when the actual UL TX is scheduled and / or when a UL sub-band (SBFD configuration) is given and at least partially overlaps with the DL. The WTRU may be configured (or instructed) to apply either a first behavior for the condition based on whether the actual UL TX is scheduled and / or a second behavior for the condition based on when a UL sub-band (SBFD configuration) is given and at least partially overlaps with the DL (e.g., regardless of whether the actual UL Tx is scheduled and / or unscheduled).

[0213] In example 1 (e.g., operating mode 1), the WTRU may drop reception of both of the at least two linked PDCCH candidates of a PDCCH repetition, and the WTRU may instead perform an UL transmission (if actually scheduled), which may provide advantages in terms of reduced WTRU complexity and simplified operating behavior in communication systems employing SBFD operation.

[0214] The WTRU may be configured for selective reception. In example 2 (e.g., operation mode 2), the WTRU may receive one or more non-overlapping PDCCH candidates (of the at least two linked PDCCH candidates), e.g., if no overlap is found in the time domain and / or if up to Z symbols overlap, where a value of Z>0 may be predefined and / or preconfigured and / or indicated. The WTRU may drop reception of other PDCCH candidates of the at least two linked PDCCH candidates that are overlapped, and instead, the WTRU may perform UL transmissions on the overlapped symbols. This may allow both DL and UL links to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be received as part of the PDCCH repetition.

[0215] The WTRU may be configured for selective reception based on the TCI status. In Example 2A (e.g., operating mode 2A), the WTRU may receive a TCI (e.g., beam and / or time / frequency domain channel large-scale characteristic / quasi-co-location (QCL) type) configured and / or indicated such that one or more PDCCH candidates (of the PDCCH repetition) are overlapped with the UL, but the UL and DL are identical (or associated with the same set of TCIs), and the WTRU may report its capabilities for such simultaneous Rx (e.g., as part of the PDCCH repetition) and Tx (of the UL). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU.

[0216] The WTRU may be configured for selective reception based on the UL panel. In one example, the WTRU may receive a first WTRU panel used for Tx and a second WTRU panel used for DL, where one or more PDCCH candidates (of a PDCCH repetition) overlap with the UL, and the WTRU may report its capabilities for such simultaneous Rx (e.g., as part of a PDCCH repetition) and Tx (of the UL) across at least two different WTRU panels (or antenna groups and / or different Tx / Rx (hardware) entities, etc.). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU.

[0217] In one or more cases, if the WTRU determines that all linked PDCCH candidates of a PDCCH repetition are overlapped in the UL, the WTRU may conditionally implement example 1 (operation mode 1) as a fallback behavior depending on the determination.

[0218] In example 3 (e.g., operating mode 3), the WTRU may drop the UL transmission and monitor all linked PDCCH candidates, which may provide the advantage that the DL control channel (via PDCCH repetition) may be protected with high priority.

[0219] In one or more cases, the WTRU may be configured for PDSCH repetition. The WTRU may be configured to perform DL reception based on PDSCH repetition, which may be time domain multiplexed (TDMed) repetition and / or frequency domain multiplexed (FDMed) repetition based on a higher layer configuration parameter, such as "repetitionNumber," that indicates the number of repetitions (e.g., of the same PDSCH content / packet and / or PDSCH transport block). In one example, the WTRU may be configured with a parameter (e.g., "repetitionNumber") that may be in the codepoint (or field state) of the time domain resource allocation (TDRA) field in the DL-DCI (e.g., DCI format 1_1 and / or 1_2, etc.). The WTRU may be configured with higher layer configuration parameters, e.g., "repetitionScheme" that indicates / selects one DL mTRP Tx scheme among "fdmSchemeA" (or "fdmSchemeB") for frequency domain-based repetition scheme and "tdmSchemeA" for time domain-based repetition scheme.

[0220] The problem / issue that can be resolved is that some of the PDSCH repetition-based occasions collide (e.g., in the time domain) with UL transmissions in SBFD slots / symbols, if allowed in the SBFD slots / symbols, at least when such PDSCH repetitions are configured in the WTRU.

[0221] In one or more cases, when a WTRU is configured with two or more PDSCH Tx occasions of the same TB (e.g., either multi-slot-level PDSCH and / or intra-slot-level PDSCH), the WTRU may determine (or be configured to determine) whether each PDSCH Tx occasion has at least one symbol-level overlap and / or whether there is no (scheduled / configured / instructed) UL Tx of SBFD symbols. One or more of the following may apply: The condition for determining overlap and / or non-overlapping may be based either on when the actual UL TX is scheduled and / or when a UL sub-band (SBFD configuration) is given and at least partially overlaps with the DL. The WTRU may be configured (or instructed) to apply either a first behavior for the condition based on whether the actual UL TX is scheduled and / or a second behavior for the condition based on when a UL sub-band (SBFD configuration) is given and at least partially overlaps with the DL (e.g., regardless of whether the actual UL Tx is scheduled and / or not).

[0222] In example 1 (e.g., operating mode 1), the WTRU may drop all reception of two or more scheduled / configured / instructed PDSCH Tx occasions, and the WTRU may instead perform UL transmissions (if actually scheduled), which may provide advantages in terms of reduced WTRU complexity and simplified operating behavior in communication systems employing SBFD operation.

[0223] In one or more cases, the WTRU may be configured for selective reception. In example 2 (e.g., operation mode 2), the WTRU may receive one or more non-overlapping PDSCH Tx occasions (out of two or more scheduled / configured / instructed PDSCH Tx occasions) (e.g., if no overlap is found / determined in the time domain and / or if up to A symbols are overlapped, where a value of A>0 may be predefined and / or preconfigured and / or instructed). The WTRU may drop reception of other overlapped PDSCH Tx occasions, and instead, the WTRU may perform UL transmissions on the overlapped symbols. This allows both the DL link and the UL link to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be received as part of the PDSCH repetition. One or more of the following may apply: The WTRU may be configured for selective reception based on the TCI state. Furthermore, the WTRU may be configured for selective reception based on the repetition pattern.

[0224] For example, with respect to selective reception based on TCI status, in Example 2A (e.g., operational mode 2A), a WTRU may receive a TCI (e.g., beam and / or time / frequency domain channel large scale characteristic / quasi-co-location (QCL) type) configured and / or instructed such that one or more PDSCH Tx occasions (of a PDSCH repetition) are overlapped with the UL, but the UL and DL are identical (or associated with the same set of TCIs), and the WTRU may report its capabilities for such simultaneous Rx (e.g., as part of a PDSCH repetition) and Tx (of the UL). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU. In one example, a WTRU may receive one or more PDSCH Tx occasions (of a PDSCH repetition) overlapping with the UL, with a first WTRU panel used for Tx and a second UL panel used for DL, and the WTRU may report its capabilities for such simultaneous Rx (e.g., as part of a PDSCH repetition) and Tx (of the UL) across at least two different WTRU panels (or antenna groups and / or different Tx / Rx (hardware) entities, etc.). The WTRU may report such capabilities based on its supported / implemented capabilities for full-duplex operation (for simultaneous Tx and Rx) at the WTRU.

[0225] For example, with regard to selective reception based on a repetition pattern, in Example 2B (e.g., operating mode 2B), the WTRU may receive one or more PDSCH Tx occasions (of PDSCH repetitions) indicated with the same (or predefined and / or preconfigured pattern) TCI (or DL-TCI) based on a configured repetition pattern (e.g., "cyclicMapping" and / or "sequentialMapping") that do not overlap in the UL, e.g., when no overlap is found / determined in the time domain and / or when up to A symbols overlap, where a value of A>0 may be predefined and / or preconfigured and / or indicated. A "cyclicMapping" pattern may mean that a first PDSCH Tx occasion is received with a first TCI and a second PDSCH Tx occasion is received with a second TCI, and these two PDSCH Tx occasion patterns are repeated until the last PDSCH Tx occasion is reached. A "sequentialMapping" pattern may refer to a first PDSCH Tx occasion received on a first TCI, a second PDSCH Tx occasion received on a first TCI, a third PDSCH Tx occasion received on a second TCI, and a fourth PDSCH Tx occasion received on a second TCI, where these four PDSCH Tx occasion patterns are repeated until the last PDSCH Tx occasion is reached. The WTRU may drop reception of other PDSCH Tx occasions of the overlapped PDSCH repetition, and instead, the WTRU may perform UL transmissions on the overlapped symbols. This may allow both the DL link and the UL link to be used, and may improve system throughput and operating efficiency / flexibility, since at least non-overlapping symbols may be received as part of the PDSCH repetition.

[0226] In one or more cases, the WTRU may be configured for an alternative FDRA configuration. For example, if such overlap with the UL is detected, identified, and / or determined at the WTRU, instead of dropping reception, the WTRU may use (or be configured to use) a different frequency-domain resource allocation to receive one or more PDSCH Tx occasions. To this end, the WTRU may receive a configuration / indication of a different frequency-domain resource allocation (e.g., a set of PRBs) to be used for reception.

[0227] In one or more cases, if the WTRU determines that all PDSCH Tx occasions of a PDSCH repetition (of two or more scheduled / configured / instructed PDSCH Tx occasions) overlap with the UL, the WTRU may conditionally implement Example 1 (Operation Mode 1) as a fallback behavior depending on the determination.

[0228] In example 3 (e.g., operating mode 3), the WTRU may drop the UL transmission and monitor all PDSCH Tx occasions (of two or more scheduled / configured / instructed PDSCH Tx occasions) of the PDSCH repetitions, which may provide the advantage that DL throughput performance may be improved based on setting the DL Rx with higher priority compared to the UL Tx.

[0229] In one or more cases, the disclosure provided herein may relate to devices, methods, and systems for uplink and downlink resource allocation in SBFD symbols, including explicit and implicit indication of resource allocation, as well as reliability issues. In one or more cases, the devices, methods, and systems for resource allocation may relate to the following: uplink resource allocation in SBFD symbols, downlink resource allocation in SBFD symbols, explicit indication of resource allocation in SBFD symbols, implicit indication of resource allocation in SBFD symbols, and reliability of resource allocation in SBFD symbols. Furthermore, the disclosure provided herein may relate to devices, methods, and systems for repetition enhancement in SBFD symbols, including symbol availability for UL Tx and UL / DL repetition transmission in multi-TRP and MIMO systems. In one or more cases, the devices, methods, and systems for repetition enhancement in SBFD symbols may relate to symbol availability for UL Tx and UL / DL repetition transmission in multi-TRP and MIMO. In one or more cases, UL / DL repetition transmission in multi-TRP and MIMO may include a solution for PUCCH repetition, a solution for PUSCH repetition, a solution for PDCCH repetition, and a solution for PDSCH repetition.

[0230] Turning to FIG. 7, another example of SBFD slots is illustrated. In FIG. 2, SBFD slots 208, 210 are surrounded by DL slot 206 on the left and flexible slot 212 and UL slot 214 on the right, whereas in FIG. 7, SBFD slots 208, 210 have UL slot 702 and UL slot 704 on the left and right, respectively. Any arrangement or pattern of UL, DL, flexible, SBFD, special time instance, or other slots is contemplated in this disclosure. The slot arrangement may affect the selected K1 value and periodicity. The slot arrangement may also affect the configuration (e.g., subband, frequency) of PUSCH repetitions.

[0231] Additional solutions are described herein that may be implemented in conjunction with any and / or all portions of the present disclosure. From the WTRU's perspective, WTRUs in a cell may be informed of a mixed D / U region (e.g., slot) across RBs per symbol / slot, with subband granularity at least at the group of RBs or BWP level. For BWP-level SBFD, the subband indication for SBFD operation may be based on reusing an existing BWP indicator in the DCI. Or, alternatively, the BWP indication may be interpreted as a muted RB / BWP region for DL ​​reception or UL transmission to be rate-matched around the muted RBs, as a simplified SBFD operation.

[0232] If the WTRU detects a timing mismatch (e.g., interference caused by timing offset in UL transmissions in the SBFD UL subband, part of the UL transmission intended for the SBFD UL subband being in the DL receive subband, etc.), the WTRU may request an adjustment and report the problem, or may decide which overlapping portions of either the DL or UL symbols may be dropped or punctured. For example, the WTRU may also decide to include the time required for timing alignment in each UL / DL SB in the SBFD slot, and the UL transmission scheduled on the SBFD slot may have a rate-matched or punctured symbol in the front symbol position of the UL transmission, or the DL symbol may be punctured; this should depend on the gNB's flexible configuration for such WTRU behavior.

[0233] In some cases, the WTRU may drop UL transmissions or DL ​​receptions that span the DL or UL subbands, respectively. DL / UL channels / signals that overlap RBs outside the DL / UL subbands in SBFD or non-SBFD slots, respectively, may be dropped or postponed.

[0234] While features and elements are described above in particular combinations, those skilled in the art will understand that each feature and / or element may be used alone and / or in any combination with the other features and elements. Additionally, the methods described herein may be implemented in a computer program, software, and / or firmware embodied in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include electronic signals (transmitted over wired and / or wireless connections) and 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 internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, a WTRU, a terminal, a base station, an RNC, and / or any host computer.

Claims

1. 1. A wireless transmit / receive unit (WTRU), comprising: a processor, the processor comprising: receiving subband non-overlapping full duplex (SBFD) configuration information, the SBFD configuration information indicating one or more orthogonal frequency division multiplexing (OFDM) symbols associated with one or more subbands for uplink transmission and one or more subbands for downlink reception; receiving scheduling information associated with a plurality of physical uplink shared channel (PUSCH) transmissions, the scheduling information including a first frequency domain resource allocation (FDRA); sending a first PUSCH transmission of the plurality of PUSCH transmissions using a first frequency resource determined based on the first FDRA; determining that a second PUSCH transmission of the at least a plurality of PUSCH transmissions is to be sent using at least one OFDM symbol of the one or more OFDM symbols; determining, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in the one or more subbands for downlink reception of the at least one OFDM symbol; receiving one or more of a second FDRA or a frequency offset for the second PUSCH transmission; determining a second frequency resource for sending the second PUSCH transmission based on one or more of the second FDRA or the frequency offset, the second frequency resource being included in the one or more subbands for uplink transmission of the at least one OFDM symbol; A wireless transmit / receive unit (WTRU) configured to send the second PUSCH transmission using the second frequency resource.

2. The WTRU of claim 1 , wherein the processor is further configured to determine that the first frequency resource is at least partially included in the one or more subbands for uplink transmission.

3. The WTRU of claim 1 , wherein the processor is further configured to receive the second FDRA or the frequency offset in the scheduling information.

4. The WTRU of claim 1 , wherein the scheduling information includes the downlink control information.

5. 10. The WTRU of claim 1, wherein the processor is further configured to receive the second FDRA or the frequency offset in a medium access control (MAC) control element (CE), a radio resource control (RRC) configuration, or downlink control information.

6. The WTRU of claim 1 , wherein the processor is further configured to send the first PUSCH transmission using a time division duplex (TDD) configuration.

7. The WTRU of claim 1 , wherein the processor is further configured to determine the start of the second PUSCH transmission based on a starting resource block (RB) of the SBFD or a starting RB of the second FDRA.

8. The WTRU of claim 1 , wherein the processor is further configured to determine the second FDRA from an indication or the SBFD configuration information.

9. The WTRU of claim 1 , wherein the processor is further configured to determine the second FDRA from the first FDRA by applying the frequency offset.

10. The WTRU of claim 1 , wherein the frequency offset is a resource block (RB) offset.

11. 2. The WTRU of claim 1, wherein the frequency offset is configured or indicated using a medium access control (MAC) control element (CE) or downlink control information (DCI), and the frequency offset is included in the indication or configuration.

12. The WTRU of claim 1 , wherein the SBFD configuration information indicates PUSCH repetition or transport block (TB) over multiple slots (TBoMS).

13. The WTRU of claim 1 , wherein the processor is further configured to determine a type of slot for a PUSCH transmission, the type of slot being SBFD or non-SBFD.

14. 10. The WTRU of claim 1, wherein the processor is further configured to determine a number of available slots, and determining the number of available slots includes one or more of: determining non-SBFD uplink transmission slots as available; and determining SBFD slots as available only if a second FDRA is within one or more subbands for uplink transmission.

15. 2. The WTRU of claim 1, wherein the processor is further configured to determine the first FDRA and the second FDRA for non-SBFD slots and SBFD slots, wherein the first FDRA and the second FDRA use frequency resources or physical resource block (PRB) resources.

16. The WTRU of claim 1 , wherein the processor is further configured to use the first FDRA for non-SBFD slots and the second FDRA for SBFD slots.

17. The WTRU of claim 1 , wherein the processor is further configured to determine the second frequency resource for sending the second PUSCH transmission using the first FDRA and the frequency offset.

18. The WTRU of claim 1 , wherein the processor is further configured to use separate frequency resources for SBFD slots and non-SBFD slots based on the first FDRA.

19. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving subband non-overlapping full duplex (SBFD) configuration information, the SBFD configuration information indicating one or more orthogonal frequency division multiplexing (OFDM) symbols associated with one or more subbands for uplink transmission and one or more subbands for downlink reception; receiving scheduling information associated with a plurality of physical uplink shared channel (PUSCH) transmissions, the scheduling information including a first frequency domain resource allocation (FDRA); sending a first PUSCH transmission of the plurality of PUSCH transmissions using a first frequency resource determined based on the first FDRA; determining that a second PUSCH transmission of the at least a plurality of PUSCH transmissions is to be sent using at least one OFDM symbol of the one or more OFDM symbols; determining, based on the SBFD configuration information and the first FDRA, that the first frequency resource is at least partially included in the one or more subbands for downlink reception of the at least one OFDM symbol; receiving one or more of a second FDRA or a frequency offset for the second PUSCH transmission; determining a second frequency resource for sending the second PUSCH transmission based on one or more of the second FDRA or the frequency offset, the second frequency resource being included in the one or more subbands for uplink transmission of the at least one OFDM symbol; and sending the second PUSCH transmission using the second frequency resource.

20. 20. The method of claim 19, further comprising: determining that the first frequency resource is at least partially included in the one or more subbands for uplink transmission.

21. 20. The method of claim 19, wherein the second FDRA or the frequency offset is received in the scheduling information.

22. 20. The method of claim 19, wherein the scheduling information includes the downlink control information.

23. 20. The method of claim 19, wherein the second FDRA or the frequency offset is received in a medium access control (MAC) control element (CE), a radio resource control (RRC) configuration, or downlink control information.

24. 20. The method of claim 19, wherein the first PUSCH transmission is sent using a time division duplex (TDD) configuration.

25. 20. The method of claim 19, wherein the start of the second PUSCH transmission is determined based on a starting resource block (RB) of the SBFD or a starting RB of the second FDRA.

26. The method of claim 19 , wherein the second FDRA is determined from an indication or the SBFD configuration information.

27. 20. The method of claim 19, wherein the second FDRA is determined from the first FDRA by applying the frequency offset.

28. 20. The method of claim 19, wherein the frequency offset is a resource block (RB) offset.

29. 20. The method of claim 19, wherein the frequency offset is configured or indicated using a Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI), and the frequency offset is included in the indication or configuration.

30. 20. The method of claim 19, wherein the SBFD configuration information indicates PUSCH repetition or transport block (TB) over multiple slots (TBoMS).

31. 20. The method of claim 19, further comprising determining a type of slot for PUSCH transmission, the type of slot being SBFD or non-SBFD.

32. 20. The method of claim 19, further comprising determining a number of available slots, wherein determining the number of available slots comprises one or more of: determining non-SBFD uplink transmission slots as available; and determining SBFD slots as available only if the second FDRA is within one or more subbands for uplink transmission.

33. 20. The method of claim 19, wherein the first FDRA and the second FDRA for non-SBFD slots and SBFD slots are determined, and the first FDRA and the second FDRA use frequency resources or physical resource block (PRB) resources.

34. 20. The method of claim 19, wherein the first FDRA is used for non-SBFD slots and the second FDRA is used for SBFD slots.

35. 20. The method of claim 19, wherein the second frequency resource for sending the second PUSCH transmission is determined using the first FDRA and the frequency offset.

36. 20. The method of claim 19, wherein separate frequency resources are used for SBFD slots and non-SBFD slots based on the first FDRA.

Images