WO2025212596A1

WO2025212596A1 - Methods for scheduling enhancements for a physical channel across sbfd and non-sbfd symbols

Info

Publication number: WO2025212596A1
Application number: PCT/US2025/022471
Authority: WO
Inventors: Aata EL HAMSS; Jonghyun Park; Moon Il Lee; Paul Marinier; Janet Stern-Berkowitz; Nazli KHAN BEIGI; Virgile Garcia
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2024-04-01
Filing date: 2025-04-01
Publication date: 2025-10-09
Anticipated expiration: 2026-10-01

Abstract

A wireless transmit receive unit (WTRU) determines whether to use one or both of subband full duplex (SBFD) and non-SBFD symbols for an UL transmission based on the number of SBFD symbols and the DMRS configuration for the transmission. When the WTRU determines to use both SBFD and non-SBFD symbols for the transmission, the WTRU determines the RB allocation for each of the SBFD and non-SBFD symbols based on one or more of the UL subband configuration for the SBFD symbols, the configured or indicated frequency allocation, and the number of SBFD symbols and/or the number of non-SBFD symbols for the transmission. Additional embodiments are disclosed.

Description

METHODS FOR SCHEDULING ENHANCEMENTS FOR A PHYSICAL CHANNEL ACROSS SBFD AND NON-SBFD SYMBOLS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/572,726, filed April 1 , 2024, the contents of which are incorporated herein by reference.

BACKGROUND

[0002] There are two primary modes of operation in current communication systems: Frequency Division Duplex (FDD) and Time Division Duplex (TDD). In FDD mode, downlink (DL) and uplink (UL) transmissions can be configured at the same time but using different carrier frequencies. In TDD mode, the DL and UL transmissions are separated in the time domain. To improve resource availability in one direction (DL or UL), full duplex (FD) was studied for new radio (NR) systems. Full duplex includes a base station, e.g., a gNB, and/or a mobile device, e.g., a user equipment (UE), transmitting and receiving in the same carrier bandwidth at the same time. A concept referred to as subband full duplex (SBFD) was introduced where a carrier bandwidth is divided in multiple subbands and each subband will have transmissions in only one direction.

[0003] In current NR systems, a transmission in UL or DL direction has a same number of allocated resource blocks (RBs), e.g., each RB including 12 subcarriers. The design of the system only allows to indicate a single Frequency Domain Resource Allocation (FDRA) for a transmission. For a dynamic grant, the downlink control information (DCI) explicitly indicates the FDRA for an UL transmission whereas for a configured grant, the FDRA of the transmission is indicated using radio resource control (RRC) signaling or is indicated in the DCI activating the configured grant. Allowing a transmission with a different number of RBs can cause, in some cases, phase continuity issues at the receiver side. The transmitter may not be able to maintain the phase continuity if the number of RBs changes during the transmission. Consequently, the channel estimation at the receiver can be degraded. The current resource allocation scheme in NR is limited to indicate one frequency domain resource allocation for the entire transmission. When the phase continuity issue can be resolved, it may be beneficial to configure a transmission with a different number of RBs in SBFD and non-SBFD slots. Solutions for how and when to enable UL/DL transmission within a slot including both SBFD and non-SBFD symbols are desired.

SUMMARY

[0004] According to one aspect of the disclosed embodiments, the UE, also referred to herein as a wireless transmit receive unit (WTRU), determines whether to use one or both of subband full duplex (SBFD) and non-SBFD symbols for an UL transmission based on the number of SBFD symbols and the demodulation reference signal (DM RS) configuration for the transmission. When the WTRU determines to use both SBFD and non-SBFD symbols for the transmission, the WTRU determines the RB allocation for each of the SBFD and non-SBFD symbols based on one or more of the UL subband configuration for the SBFD symbols, the configured or indicated frequency allocation, and the number of SBFD symbols and/or the number of non-SBFD symbols for the transmission. [0005] According to one aspect, the WTRU receives configuration of at least one of a first set of slots that have only SBFD symbols, a second set of slots that have only non-SBFD symbols and a third set of slots that have both SBFD and non-SBFD symbols. In one example, the WTRU receives a configuration or indication (e.g., in a scheduling or activating DCI) indicating to transmit an uplink transmission in a slot in the third set of slots. The indication includes a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA) for the transmission. [0006] In some aspects, the TDRA may indicate a row or entry in a configured list or table of resource allocations. As an example, the TDRA may indicate an allocation that spans or includes both SBFD and non-SBFD symbols. The FDRA may indicate one or more RBs for the UL transmission.

[0007] According to various aspects of the disclosed embodiments, the WTRU may determine to use both SBFD and non-SBFD symbols for the uplink transmission based on one or more of the following:

[0008] (i) A number of demodulation reference signal (DMRS) resource elements (REs) or a location of a DMRS

(e.g., comprising one or more DM-RS REs) in the SBFD symbols and/or non-SBFD symbols. For example, if the WTRU determines that the number of DMRS-REs in the non-SBFD symbol(s) of the slot or the TDRA is above a configured threshold, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission.

[0009] (ii) A time gap between the SBFD and non-SBFD symbols. For example, if the WTRU determines that the time gap between the SBFD and non-SBFD symbols (e.g., of the slot or TDRA) is below a configured threshold, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission.

[0010] (iii) The number of SBFD and non-SBFD symbols. For example, if the WTRU determines that the ratio of the number of SBFD to the number of non-SBFD symbols (e.g., in the slot or TDRA) is below a configured threshold, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission.

[0011] (iv) The indicated TDRA (e.g., TDRA row or entry). For example, if the indicated TDRA indicates a time domain allocation in both SBFD and non-SBFD symbols, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission.

[0012] When the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines the RB allocation for the uplink transmission and transmits the UL transmission in the SBFD and non-SBFD symbols (e.g., of the TDRA). In one example, the WTRU determines the RB allocation using the indicated FDRA where the reference point for the resource allocation is the first RB of the UL subband in the SBFD symbols. The WTRU uses the same RB allocation in the SBFD and non-SBFD symbols.

[0013] In another example when the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines the RB allocation for the SBFD and non-SBFD symbols based on the UL subband configuration, the number of SBFD symbols and the indicated FDRA (where the reference point for the resource allocation is the first RB of the UL bandwidth part (BWP)). For example, if some of the RBs indicated by the FDRA are located outside the UL subband and the number of SBFD symbols (e.g., in the slot or TDRA) is above a threshold, the WTRU uses only the RBs within the UL subband for both SBFD and non-SBFD symbols for the transmission. Otherwise, for example, the WTRU uses all the indicated RBs in the non-SBFD symbols and uses only the RBs located within the UL subband in SBFD symbols. [0014] According to other aspects when the WTRU determines not to use both SBFD and non-SBFD symbols, the WTRU transmits either on SBFD or non-SBFD symbols (e.g., of the TDRA) based on the number of SBFD and/or non- SBFD symbols (e.g., of the slot or TDRA). In one example, the WTRU transmits using only the non-SBFD symbols when the number of non-SBFD symbols is greater than the number of SBFD symbols. In another example, the WTRU transmits using only the SBFD symbols when the number of SBFD symbols is greater than the number of non-SBFD symbols. Additional aspects, features and/or advantages are disclosed in the embodiments which follow.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0020] FIG. 2 is a block diagram illustrating an example of a slot with both subband full duplex (SBFD) symbols and non-SBFD symbols;

[0021] FIG. 3 is block diagram illustrating an example SBFD configuration in multiple slots;

[0022] FIG. 4 is a block diagram illustrating an example of using a same resource block (RB) allocation for both SBFD symbols and non-SBFD symbols according to an embodiment;

[0023] FIG. 5 is a block diagram illustrating an example of using a different resource block (RB) allocation for SBFD symbols and non-SBFD symbols according to an alternative embodiment;

[0024] FIG. 6 is a block diagram illustrating an example of using a different RB allocation for SBFD symbols and non-SBFD symbols according to third embodiment; and

[0025] FIG. 7 is a flow diagram illustrating an example WTRU method according to various embodiments.

DETAILED DESCRIPTION

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

[0027] As shown in FIG. 1 A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fl device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

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

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

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

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

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

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

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

[0036] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellularbased RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106. [0037] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

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

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

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

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

[0044] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example. [0045] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

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

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

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

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

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

[0053] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0054] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

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

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

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

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

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

[0060] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication. [0061] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0062] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

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

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

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

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

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

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

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

[0070] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

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

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

[0073] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types ofservices being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

[0074] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IPbased, non-IP based, Ethernet-based, and the like.

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

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

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

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

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

[0080] As mentioned previously, there are two modes of operation in current communication systems: Frequency Division Duplex (FDD) and Time Division Duplex (TDD). In FDD mode, DL and UL transmissions can be configured at the same time but using different carrier frequencies. In TDD mode, the DL and UL transmissions are separated in time domain for a TDD frame. This time restriction can impact the coverage of the transmission especially for uplink transmissions. To solve this limitation of the resource availability in one direction (DL or UL), full duplex (FD) was studied to be supported in new radio (NR) systems.

[0081] Full duplex consist on having a base station, e.g., a gNB and/or mobile station, e.g., a WTRU transmits and receives in the same carrier bandwidth at the same time. In the 3GPP full duplex study, subband full duplex (SBFD) concept was introduced where a carrier is divided in multiple subbands and each subband will have transmissions only one direction. For example, one SBFD configuration could be to divide a carrier into three subbands, with a first subband configured for downlink transmission, a second subband configured for uplink transmission and a third subband configured for downlink transmission. The three subbands can be separated by a gap in frequency domain to protect the transmissions from cross link interference (CLI). [0082] Referring to FIG. 2 an example slot 200 in a radio frame is shown. Slot 200 may have one or more symbols configured with subband full duplex (SBFD) (i.e., SBFD symbol 202), e.g., including one or more DL subbands 204, 208 and one or more UL subband(s) 206 in a same symbol. Slot 200 may also include one or more symbols configured with non-SBFD, meaning with the full bandwidth in one direction (i.e., non-SBFD symbol 220) with uplink band 212. When a slot is configured with both SBFD and non-SBFD symbols, the available bandwidth for transmission in one direction will change during the slot. For example, a slot configured with 7 symbols for SBFD (DL-UL-DL) and with 7 symbols for non-SBFD (UL only). In such case, the available bandwidth for uplink transmission increases in the second half of the slot. There are certain benefits for scheduling a transmission that spans both SBFD and non-SBFD symbols. For example, in a coverage limited scenario, the scheduler can maximize the usage of the available bandwidth and schedule a WTRU with a higher number of resource blocks (RBs) in non-SBFD symbols compared to SBFD symbols. [0083] In current NR systems, a transmission in an uplink or downlink direction has the same number of allocated RBs. The design of the system only allows a scheduler to indicate a single Frequency Domain Resource Allocation (FDRA) for a transmission. For a dynamic grant, the downlink control information (DCI) explicitly indicates the FDRA for the transmission, whereas for a configured grant, the FDRA of the transmission is indicated using RRC signaling or is indicated in the DCI activating the configured grant.

[0084] One potential issue with SBFD symbol and non-SBFD symbol use in current NR systems is that channel estimation is impacted with a variable number of RBs per slot. Allowing a transmission with different number of RBs can cause, in some cases, phase continuity issue at the receiver side. The transmitter may not be able to maintain the phase continuity if the number of RBs changes during the transmission. Consequently, the channel estimation at the receiver can be degraded.

[0085] Another potential issue with using SBFD and non-SBFD symbols in a slot in current NR systems is the frequency domain resource allocation (FDRA) scheme in NR. The current resource allocation scheme in NR is limited to indicate one frequency domain resource allocation for the entire transmission. When the phase continuity issue can be resolved, it may be beneficial to configure a transmission with a different number of RBs in SBFD and non-SBFD slots.

[0086] Based on the foregoing, embodiments are disclosed herein that may address how and when to enable UL/DL transmission within a slot having both SBFD and non-SBFD symbols. The following embodiments may provide example solutions for SBFD and non-SBFD use in NR or future systems.

[0087] In one example embodiment, the WTRU determines whether to use one or both of SBFD and non-SBFD symbols for an UL transmission based on the number of SBFD symbols and the demodulation reference signal (DMRS) configuration for the transmission. When the WTRU determines to use both SBFD and non-SBFD symbols for the transmission, the WTRU determines the RB allocation for each of the SBFD and non-SBFD symbols based on one or more of the UL subband configuration(s) for the SBFD symbols, the configured or indicated frequency allocation, and the number of SBFD symbols and/or the number of non-SBFD symbols for the transmission.

[0088] In various embodiments, the WTRU receives a configuration for using at least one of a first set of slots that have only SBFD symbols, a second set of slots that have only non-SBFD symbols and a third set of slots that have both SBFD symbols and non-SBFD symbols. The WTRU receives a configuration or indication (e.g., in a scheduling or activating DCI) indicating to transmit an uplink transmission in a slot in the third set of slots.

[0089] The indication includes a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA) for the transmission. For example, the TDRA may indicate a row or entry in a configured list or table of resource allocations. The TDRA may indicate an allocation that spans or includes both SBFD and non-SBFD symbols. The FDRA may indicate one or more RBs for the UL transmission.

[0090] With this configuration, the WTRU may determine either to use both SBFD and non-SBFD symbols for the uplink transmission or not use both SBFD and non-SBFD symbols in the uplink transmission. In various example embodiments, the WTRU may determine to use both SBFD and non-SBFD symbols in the uplink transmission based on one or more of the considerations (1)-(4) below.

[0091] (1) A number of demodulation reference signal (DMRS) resource elements (REs) or a location of a DMRS

(e.g., having one or more DMRS REs) in the SBFD symbols and/or non-SBFD symbols. For example, if the WTRU determines that the number of DMRS REs in the non-SBFD symbol(s) of the slot or the TDRA is above a configured threshold, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission.

[0092] (2) A time gap between the SBFD and non-SBFD symbols. For example, if the WTRU determines that the time gap between the SBFD symbol and non-SBFD symbol (e.g., of the slot or TDRA) is below a configured threshold, the WTRU may determine to use both SBFD and non-SBFD symbols for the uplink transmission.

[0093] (3) The number of SBFD and non-SBFD symbols. For example, if the WTRU determines that a ratio of the number of SBFD symbols to the number of non-SBFD symbols (e.g., in the slot or TDRA) is below a configured threshold, the WTRU may determine to use both SBFD and non-SBFD symbols for the uplink transmission.

[0094] (4) The indicated TDRA (e.g., TDRA row or entry). For example, if the indicated TDRA indicates a time domain allocation in both SBFD and non-SBFD symbols, the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission. It is noted that the foregoing are non-limiting examples and determination to use both SBFD symbols and non-SBFD symbols in a slot of an uplink transmission may be based on other factors.

[0095] When the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission, the WTRU may determine the RB allocation for the uplink transmission and send the UL transmission in the SBFD and non-SBFD symbols (e.g., of the TDRA). In one example referred to herein as Alternative 1 (e.g., FIG. 4), when the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines the RB allocation using the indicated FDRA where the reference point for the resource allocation is the first RB of the UL subband in the SBFD symbols. In this example, the WTRU uses the same RB allocation in the SBFD and non-SBFD symbols.

[0096] In another example, referred to as Alternative 2 (e.g., FIG. 5), when the WTRU uses both SBFD and non- SBFD symbols for the uplink transmission, the WTRU determines the RB allocation for the SBFD and non-SBFD symbols based on the UL subband configuration, the number of SBFD symbols and the indicated FDRA (where the reference point for the resource allocation is the first RB of the UL BWP). For example, if some of the RBs indicated by the FDRA are located outside the UL subband and the number of SBFD symbols (e.g., in the slot or TDRA) is above a threshold, the WTRU uses only the RBs within the UL subband for both SBFD and non-SBFD symbols for the uplink transmission. Otherwise, for example, the WTRU uses all the indicated RBs in the non-SBFD symbols and uses only the RBs located within the UL subband in the SBFD symbols.

[0097] In the event the WTRU determines not to use both SBFD and non-SBFD symbols in the uplink transmission, the WTRU may transmit on either the SBFD symbol or non-SBFD symbol (e.g., of the TDRA), based on the number of SBFD and/or non-SBFD symbols (e.g., of the slot or TDRA). In one example, the WTRU transmits using only the non-SBFD symbols when the number of non-SBFD symbols is greater than the number of SBFD symbols. In another example, the WTRU transmits using only the SBFD symbols when the number of SBFD symbols is greater than the number of non-SBFD symbols.

[0098] In this manner, the WTRU can use a longer duration for the uplink transmission when the previously- mentioned phase continuity issue can be mitigated.

[0099] As used herein, the terms ‘a’ and ‘an’ and similar phrases are meant to be interpreted as ‘one or more’ and ‘at least one’. Similarly, any term which ends with the suffix ‘(s)’ is meant to be interpreted as ‘one or more’ and ‘at least one’. The term ‘may’ is to be interpreted as ‘may, for example’. Furthermore, a symbol ‘I’ (e.g., forward slash) may be used herein to represent ‘and/or’, where for example, ‘A/B’ may imply ‘A and/or B’.

[0100] Additionally, as used herein, the term 'subband” is used to refer to a frequency-domain resource and may be characterized by at least one of the following:

[0101] -A set of resource blocks (RBs);

[0102] -A set of resource block sets (RB sets), e.g. when a carrier has intra-cell guard bands;

[0103] -A set of interlaced resource blocks;

[0104] -A bandwidth part, or portion thereof; and/or

[0105] -A carrier, or portion thereof.

[0106] For example, a subband may be characterized by a starting RB and number of RBs for a set of contiguous RBs within a bandwidth part (BWP). A subband may also be defined by the value of a frequency-domain resource allocation (FDRA) field and BWP index.

[0107] Detailed embodiments for subband-based full duplex (SBFD) will now be described. Hereinafter, the term ‘‘SBFD” is used to refer to a subband-wise duplex (e.g., either UL or DL being used per subband) and may be characterized by at least one of the following:

[0108] -Cross Division Duplex (e.g., XDD, subband-wise FDD within a TDD band);

[0109] -Subband-based full duplex (e.g., full duplex as both UL and DL are used/mixed on a symbol/slot, but either UL or DL being used per subband on the symbol/slot);

[0110] -Frequency-domain multiplexing (FDM) of DL/UL transmissions within a TDD spectrum;

[0111] -A subband non-overlapping full duplex (SBFD) (e.g., non-overlapped subband full-duplex);

[0112] -A full duplex other than a same-frequency (e.g., spectrum sharing, subband-wise-overlapped) full duplex; and/or

[0113] -An advanced duplex method, e.g., other than (pure) TDD or FDD, e.g., partial in-band full duplex, subband overlapping full duplex, in-band full duplex (IBFD). [0114] In the following disclosure, a property of a grant or assignment may include of at least one of: a frequency allocation; an aspect of time allocation, such as a duration; a priority; a modulation and coding scheme; a transport block size; a number of spatial layers; a number of transport blocks; a transmission configuration indication (TCI) state, channel state reference signal indicator (CRI) or sounding reference signal resource indicator (SRI); a number of repetitions; whether the repetition scheme is Type A or Type B; whether the grant is a configured grant type 1 , type 2 or a dynamic grant; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; a configured grant index or a semi-persistent assignment index; a periodicity of a configured grant or assignment; a channel access priority class (CAPC); and/or any parameter provided in downlink control information (DCI), by medium access control (MAC) or by radio resource control (RRC) for scheduling the grant or assignment.

[0115] In the example embodiments, an indication by DCI may include of at least one of: an explicit indication by a DCI field or by radio network temporary identifier (RNTI) used to mask the cyclic redundancy check (CRC) of the physical downlink control channel (PDCCH); and/or an implicit indication by a property such as DCI format, DCI size, core resource set (CORESET) or search space (SS), Aggregation Level (AL), first resource element of the received DCI (e.g., index of first Control Channel Element (CCE)), where the mapping between the property and the value may be signaled by RRC or MAC.

[0116] As used herein, a “signal” may be interchangeably used with one or more of: sounding reference signal (SRS); channel state information (CSI) reference signal (CSI-RS); demodulation reference signal (DM-RS); phase tracking reference signal (PT-RS); and/or synchronization signal block (SSB), but still be consistent with the disclosed embodiments.

[0117] Hereafter, a “channel” may be interchangeably used with one or more of: physical downlink control channel (PDCCH); physical downlink shared channel (PDSCH); physical uplink control channel (PUCCH); physical uplink shared channel (PUSCH); physical random access channel (PRACH); and/or other types of channels, but still consistent with the disclosed embodiments. Additionally, downlink reception may be used interchangeably with a receive (Rx) occasion, PDCCH, PDSCH, SSB reception, and uplink transmission may be used interchangeably with a transmit (Tx) occasion, PUCCH, PUSCH, PRACH, SRS transmission.

[0118] Hereinafter, reference signal (RS) may be interchangeably used with one or more of RS resource, RS resource set, RS port and RS port group, one or more of SSB, CSI-RS, SRS and DMRS, and still be consistent with the disclosed embodiments. Time instance may be interchangeably used with slot, symbol, subframe. UL-only and DL-only Tx/Rx occasions may interchangeably be used with legacy TDD UL or legacy TDD DL, respectively. In an example, the legacy TDD UL/DL transmit (Tx)Zreceive (Rx) occasions may be the cases where SBFD is not configured and/or where SBFD is disabled. An UL signal (e.g., at least one of SRS, DMRS, PUSCH, PUCCH, PRACH, PTRS, etc.) may be used interchangeably with a UL signal or channel, or a UL channel or signal. A DL signal (e.g., at least one of CSI-RS, SSB, PDSCH, PDCCH, PBCH, PTRS, etc.) may be used interchangeably with a DL signal or channel, or a DL channel or signal.

[0119] Example embodiments with subband full duplex (SBFD) frequency domain configuration are disclosed. In one example, a WTRU may be configured with SBFD in a frequency domain configuration which may be associated with a carrier frequency. In another example, the SBFD configuration may alternatively associated with a bandwidth part (BWP) of a carrier frequency. The SBFD frequency domain configuration may allocate some resource blocks (RBs) of the BWP/carrierfor uplink transmission and other RBs of the BWP/carrier for downlink transmission. In various examples, the WTRU may be configured with a SBFD frequency domain configuration using dedicated RRC signaling or common broadcasted signaling e.g., system information block (SIB) signaling. Hereafter, the RB(s) or RE(s) may be interchangeably used with RE(s), RB(s), REG(s), RBG(s), frequency-unit(s), subband(s), band(s), BWP(s), component carrier(s), etc., but still consistent with the disclosed embodiments, e.g., any frequency-domain granularity as frequency-unit may be applicable in terms of whether full duplex (e.g., SBFD) operation may be performed on one or more frequency-units.

[0120] Example embodiments with SBFD time domain configuration are disclosed. The WTRU may be configured with a time domain configuration that indicates slot configurations for SBFD (i.e., SBFD time domain configuration). For example, the WTRU may be configured with a first set of slots that have only SBFD symbols, a second set of slots that have only non-SBFD symbols (i.e., symbols where the entire BWP or the carrier is for configured for either UL or DL) and a third set of slots that have both SBFD and non-SBFD symbols. The WTRU may be configured with SBFD time domain configuration(s) using dedicated RRC signaling or common broadcasted signaling e.g., SIB signaling. As used herein, the slot(s) or symbol(s) may be interchangeably used with symbol(s), slot(s), sub-frame(s), frame(s), timeunits), etc., but still be consistent with the disclosed embodiments, e.g., any time-domain granularity as time-unit may be applicable in terms of whether full duplex (e.g., SBFD) operation may be performed on one or more time-units.

[0121] Referring to FIG. 3, an example of a full duplex (e.g., SBFD) configuration in shown by frame 300. In one example embodiment, a WTRU may receive one or more configurations for SBFD operation. The one or more configurations may include the information on time resources (e.g., symbols, slots, etc.) where the SBFD (e.g., full duplex operation configuration is performed at gNB) is applied. The configurations may include the information on frequency resources in the configured SBFD time resources, e.g., a first UL subband, a first DL subband, a first guard band, a first sidelink SB, a first Flexible SB, and so forth. In example frame 300, configured time resources include slots n, n+1 , n+2, n+3 and n+4. Slot n is a non-SBFD downlink slot 305, slots n+1 through n+3 are configured SBFD slots 310 and slot n+4 is a non-SBFD uplink slot 320.

[0122] In terms of frequency resources, frame 300 is configured with a bandwidth part (BWP) 330 of a component carrier (CC). As shown, DL slot 305 is configured with the entire BWP 330, the configured SBFD slots 310 include a first DL subband 312, an UL subband 314 and a second DL subband 316 and UL slot 320 is configured with the entire BWP 330. In an example, the WTRU may receive the SBFD configurations via a DCI, MAC-control element (CE), RRC, a system information block (SIB), a broadcast message, a multicast message toward a group of WTRUs, and so forth.

[0123] In an example, the WTRU may operate in half-duplex (HD) operation based on the configurations, where the WTRU may either transmit an UL (or sidelink) signal or receive a DL (or sidelink) signal in a configured (or indicated) SBFD time instance. In another example (e.g., if configured by the gNB), the WTRU may operate in full-duplex (FD) operation (e.g., subband non-overlapping FD (SBFD), subband partially/fully-overlapping FD) using the first set of SBFD configurations, where the WTRU may both transmit an UL (or sidelink) signal and receive a DL (or sidelink) signal in a configured (or indicated) SBFD time instance. [0124] Example embodiments with TDRA table configuration(s) are disclosed. The WTRU may be configured semi- statically (e.g., RRC signaling) with a time domain resource allocation (TDRA) table that includes multiple rows. Each row represents a time domain resource allocation with a different starting symbol and/or number of allocated symbols for a transmission. With dynamic signaling (e.g., scheduling DCI or DCI activating a configured grant), the WTRU may be indicated with a TDRA row from the semi-statically configured TDRA table. In some example embodiments, at least one TDRA row may indicate both SBFD and non-SBFD symbols. In an example, the TDRA row can have a Start and Length Indication Value (SLIV) element to indicate to the WTRU a starting symbol and number of consecutively allocated symbols for the transmission. Using the indicated SLIV, the WTRU may determine that the starting symbol and number of consecutively allocated symbols are within both SBFD and non-SBFD symbols.

[0125] Example embodiments with FDRA configuration(s) are disclosed. The WTRU may be configured with multiple resource allocation types to indicate the frequency domain resource allocation (FDRA). Each resource allocation type may indicate a FDRA bitfield in the scheduling DCI or in the activating DCI in the configured grant. In one resource allocation type, the FDRA bitfield may be a bitmap where each bit indicates to the WTRU whether a resource block group (RBG) is allocated for the transmission or not. Another resource allocation type may be the FDRA bitfield indicating the starting resource block (RB) and the number of contiguously allocated RBs. The FDRA bitfield size may depend on the bandwidth of the scheduled carrier/subband. When the WTRU can be dynamically scheduled with either SBFD or non-SBFD, the possible scheduled frequency resources may change. For example, scheduling either in an UL subband (with fewer RBs compared to the UL BWP) or in the UL BWP may result in different possible FDRA bitfield sizes.

[0126] In one example embodiment, the WTRU may be configured to receive the FDRA with fixed bitfield size regardless of whether the scheduling is intended for SBFD or non-SBFD symbols. In one example, the FDRA bitfield size may correspond to the UL BWP. When the WTRU is scheduled with SBFD symbols, the WTRU may assume zero padding of the FDRA bitfield portion that exceeds the FDRA bitfield size corresponding to the UL subband size. In another embodiment, the FDRA bitfield size may change dynamically depending on whether the scheduling is on SBFD or non-SBFD symbols. The WTRU may firstly determine the scheduled symbols and then WTRU may determine the FDRA bitfield size. When the WTRU determines that both SBFD and non-SBFD symbols are scheduled for the transmission, the WTRU may assume the larger FDRA bitfield size.

[0127] In some embodiments, the WTRU may determine whether the FDRA bitfield corresponds to an UL subband or an UL BWP based on the existence of zero-bit padding in the FDRA bitfield. For example, if the WTRU determines that the FDRA bitfield has N zeros in the most significant bits (MSB) or least significant bits (LSB), the WTRU may assume that the FDRA bitfield corresponds to the UL subband.

[0128] Examples for scheduling/configuring a WTRU for transmission using SBFD and non-SBFD symbols are described. For example, the WTRU may be configured or indicated to send an uplink transmission or receive a downlink transmission in a slot that has both SBFD and non-SBFD symbols (in the following a SBFD slot is referred to as a slot that has both SBFD and non-SBFD symbols). For a dynamic grant, the WTRU may be indicated with a TDRA row and FDRA value in the scheduling DCI. For a configured grant with DCI activation, the WTRU may be indicated with a TDRA row and a FDRA value in the activation DCI. For a configured grant without DCI activation, the time domain resource allocation and the frequency domain resource allocation may be signaled to the WTRU using the RRC configuration.

[0129] In various embodiments, the following conditions and/or examples are described: (i) conditions for the WTRU to determine whether to use both SBFD and non-SBFD symbols; (ii) examples for the WTRU to determine the RB allocation and transmit power to use in SBFD and non-SBFD symbols; and (iii) examples for the WTRU to determine what symbols to use for the transmission in a condition that both SBFD and non-SBFD symbols cannot be used. The following example embodiments may be applied for both uplink and downlink transmissions.

[0130] Various embodiments for determining transmission using SBFD and non-SBFD symbols are disclosed in the following examples (1)-(6).

[0131] (1) DMRS configuration. The WTRU may be configured with one or multiple demodulation reference signal

(DMRS) configurations. The DMRS configuration may be a combination of semi-static configuration and dynamic configuration. For example, the WTRU may receive multiple DMRS configurations using RRC signaling, and a DCI may indicate one DMRS configuration from the RRC DMRS configurations. A DMRS configuration may indicate the number of REs within a RB that will be used as a demodulation reference signal. A DMRS configuration may further indicate the time domain location of the REs that will be used for the DMRS. The time domain configuration of DMRS may be relative to a transmission (e.g., the first symbol of the transmission) or may be indicated relative to the slot (e.g., third symbol of the slot). When the WTRU is configured/indicated to transmit an uplink transmission in a SBFD slot, the WTRU may determine whether to use both SBFD and non-SBFD symbols for the uplink transmission based on the DMRS configuration of the uplink transmission. The WTRU may determine to use both SBFD and non-SBFD symbols when the DMRS configuration of the uplink transmission have one or more of the following:

[0132] -The number of DMRS REs in the SBFD symbols is above a configured or indicated threshold;

[0133] -The number of DMRS REs in the non-SBFD symbols is above a configured or indicated threshold;

[0134] -The total number of DMRS REs in both SBFD symbols and non-SBFD symbols is above a configured or indicated threshold; and/or

[0135] -The location of the DMRS REs in the SBFD symbols and/or non-SBFD symbols is within a preconfigured time position. For example, when the WTRU is configured with DMRS for the uplink transmission with DMRS RE(s) in the last SBFD symbol (or within last L SBFD symbol(s), where L may be configured or indicated). In another example, when the WTRU is configured with DMRS for the uplink transmission with DMRS RE(s) in the first non-SBFD symbol (or within first M non-SBFD symbol(s), where M may be configured or indicated). The WTRU may determine the time domain configuration of DMRS using the indicated time domain resource allocation (TDRA) and the SBFD time domain configuration.

[0136] (2) Time gap between SBFD and non-SBFD symbols. In various embodiments, the WTRU may be configured or indicated with a time gap (e.g., G symbol(s)) between the SBFD and non-SBFD symbols. Such a gap may allow the WTRU to transit from SBFD transmission to non-SBFD transmission. For example, during the gap, the WTRU may adjust its frequency filter to be able to transmit in the entire carrier bandwidth instead of just the UL subband. The WTRU may be configured or indicated with a time gap threshold. When the WTRU is configured/indicated to transmit an uplink transmission in a SBFD slot, the WTRU may determine whether to use both SBFD and non-SBFD for the uplink transmission based on the time gap between SBFD and non-SBFD symbols. For example, when the time gap between SBFD and non-SBFD symbols is below the time gap threshold, the WTRU may use both SBFD and non-SBFD symbols for the uplink transmission.

[0137] (3) Number of SBFD and non-SBFD symbols. The WTRU may be configured with a number of SBFD symbols in a slot and a number of non-SBFD symbols in the slot. When the WTRU is indicated/configured to transmit an uplink transmission in a slot, the WTRU may determine the number of SBFD symbols and non-SBFD symbols in the uplink transmission using the TDRA indication and the SBFD configuration in the slot. The WTRU may determine whether to use both SBFD and non-SBFD for the uplink transmission based on the number of SBFD and non-SBFD symbols of the transmission. For example, in one embodiment, the WTRU may calculate the ratio of the number of SBFD symbols to the number of non-SBFD symbols of the transmission. If the WTRU determines that the ratio of the number of SBFD symbols to the number of non-SBFD symbols is below a configured or indicated threshold, the WTRU may use both SBFD and non-SBFD symbols for the uplink transmission. In another example embodiment, the WTRU may calculate the number of SBFD symbols of the scheduled/configured uplink transmission. If the WTRU determines that the number of SBFD symbols is below a configured or indicated threshold, the WTRU may use both SBFD and non-SBFD symbols for the uplink transmission. In another example embodiment, the WTRU may calculate the number of non-SBFD symbols of the scheduled/configured uplink transmission. If the WTRU determines that the number of non-SBFD symbols is above a configured, the WTRU may use both SBFD and non-SBFD symbols for the uplink transmission.

[0138] (4) TDRA row indication. In various embodiments, the WTRU may be configured to determine whether to use both SBFD and non-SBFD symbols for the uplink transmission based on the TDRA indication/configuration of the uplink transmission. In one example solution, a value (or codepoint) of the TDRA field of the TDRA indication/configuration may indicate a flag parameter indicating at least one of the following:

[0139] -Case-A: a time domain allocation in SBFD symbols (only). For example, the SLIV element of the indicated TDRA row have a starting symbol and number of consecutively allocated symbols within SBFD symbols only;

[0140] -Case-B: a time domain allocation in non-SBFD symbols (only). For example, the SLIV element of the indicated TDRA row have a starting symbol and number of consecutively allocated symbols within non-SBFD symbols only; and/or

[0141] -Case-C: a time domain allocation in both SBFD and non-SBFD symbols. For example, the SLIV element of the indicated TDRA row have a starting symbol and number of consecutively allocated symbols within both SBFD and non-SBFD symbols.

[0142] For example, if the indicated/configured TDRA row indicates a time domain allocation in both SBFD and non-SBFD symbols (e.g., Case-C, e.g., indicated by the flag parameter), the WTRU may use both SBFD and non- SBFD symbols for the uplink transmission. In another example, if the indicated/configured TDRA row indicates a time domain allocation in SBFD symbols (only), e.g., Case-A (e.g., indicated by the flag parameter), the WTRU may use SBFD symbols (only) for the uplink transmission, e.g., even though the scheduled symbol index(es) for the uplink transmission span across both SBFD and non-SBFD symbols. In a further example, if the indicated/configured TDRA row indicates a time domain allocation in non-SBFD symbols (only), e.g., Case-B (e.g., indicated by the flag parameter), the WTRU may use non-SBFD symbols (only) for the uplink transmission, e.g., even though the scheduled symbol index(es) for the uplink transmission span across both SBFD and non-SBFD symbols.

[0143] (5) Occurrence of a transmission in the slot after a SBFD slot. In some embodiments, the WTRU may be configured to determine whether to use both SBFD and non-SBFD symbols for the uplink transmission based on the scheduling/configuration of transmission in the slot after the SBFD slot, where the slot may be (n+1 )-th slot if the SBFD slot is n-th slot. For example, if the WTRU is configured/scheduled with a transmission in the next slot after the SBFD slot (e.g., where the next slot may be (n+ 1 )-th slot if the SBFD slot is n-th slot), the WTRU may use both SBFD and non-SBFD symbols for the transmission. The next slot may be configured with (e.g., only) non-SBFD symbols. In an example, the WTRU may determine to use both SBFD and non-SBFD symbols for the uplink transmission on condition that at least the S starting symbols of the next slot are configured with non-SBFD symbols and/or at least D DMRS RE(s) are allocated in the S starting symbols for where D may be pre-configured or indicated. This may provide benefits in terms of avoiding the phase continuity issue by using DMRS REs (e.g., front-loaded DMRS REs) in the next slot (e.g., (n+ 1 )-th slot) for channel estimation in non-SBFD symbols in the SBFD slot (e.g., n-th slot).

[0144] (6) WTRU capability. In certain embodiments, the WTRU may be configured to determine whether to use both SBFD and non-SBFD for the uplink transmission based the WTRU capability of maintaining the phase continuity across SBFD and non-SBFD symbols. For example, the WTRU may be capable of maintaining the phase when using SBFD and non-SBFD symbols for uplink transmission. The WTRU may report such capability to the network and the gNB may configure/schedule transmission using SBFD and non-SBFD symbols, e.g., on condition that the WTRU receives from the gNB a confirmation or configuration signal that enables a type of transmission using both SBFD and non-SBFD symbols (e.g., within a slot or within a time unit).

[0145] Example transmission parameters for a physical channel transmission with SBFD and non-SBFD symbols will now be described. In various embodiments, a WTRU may determine: (i) the RB allocation; and/or (ii) transmit power parameters when a transmission includes both SBFD and non-SBFD symbols.

[0146] Alternative embodiments for determining RB allocation for transmitting SBFD and non-SBFD symbols follow.

[0147] Referring to FIG. 4, a first embodiment, referred to as Alternative 1 , diagram 400 shows an example for a slot 405, where a same RB allocation 410 is used for both SBFD symbols 415 and non-SBFD symbols 420. Upon determining to use both SBFD and non-SBFD symbols for the uplink transmission, the WTRU may determine the RB allocation for the uplink transmission in the SBFD symbols 415 and non-SBFD symbols 420. In one example, the WTRU may determine the RB allocation using the indicated/configured FDRA where the reference point for the resource allocation 410 may be the first RB of the UL subband in the SBFD symbol(s) 415 (or a pre-configured RB located in the UL subband in SBFD symbol(s) 415, e.g. not located outside of the UL subband 417). For example, the WTRU may assume that the indicated FDRA bitfield size corresponds to the uplink subband 417, e.g., where the indicated FDRA field is interpreted based on the uplink subband 417 (instead of an UL (active) BWP size). The WTRU may assume zero-bit padding if the FDRA bitfield size indicated in the DCI is larger than FDRA bitfield size of the UL subband 417. In this embodiment, the WTRU may use the same RB allocation for transmission in both SBFD and non- SBFD symbols of the slot. [0148] Referring to FIG. 5, a second embodiment, referred to as Alternative 2, diagram 500 shows an example for a slot 505 where a different RB allocation 517 is used for SBFD symbols 515 and non-SBFD symbols 520. Upon determining to use both SBFD and non-SBFD symbols for the uplink transmission, the WTRU may determine the RB allocation for the uplink transmission in the SBFD symbol(s) 515 and non-SBFD symbol(s) 520. In one example, the WTRU may determine the RB allocation for SBFD symbol(s) and non-SBFD symbol(s) based on the UL subband configuration, the number of SBFD symbols and the indicated/configured FDRA, where the reference point for the FDRA is the first RB (or a pre-configured RB) of the UL BWP (e.g., not of the UL subband). For example, if some of the RBs indicated/configured by the FDRA are located outside the UL subband and the number of SBFD symbols of the scheduled/configured transmission is above a threshold, the WTRU may use only the RBs within the UL subband for both SBFD and non-SBFD symbols for the transmission (e.g., as shown in FIG. 4). If some of the RBs indicated/configured by the FDRA are located outside the UL subband and/or the number of SBFD symbols of the scheduled/configured transmission is below the threshold, the WTRU may use all the indicated RBs in the non-SBFD symbols and use only the RBs located within the UL subband (e.g., by applying a rate-matching behavior, puncturing, or truncation, etc.) in SBFD symbols for the uplink transmission. Such a threshold may be configured to the WTRU or defined (e.g., fixed in the specification).

[0149] In another example, if some of the RBs indicated/configured by the FDRA are located outside the UL subband and the number of non-SBFD symbols of the scheduled/configured transmission is below a threshold, the WTRU may use (only) the RBs within the UL subband for both SBFD and non-SBFD symbols for the transmission (e.g., Alternative 1 in FIG. 4). If some of the RBs indicated/configured by the FDRA are located outside the UL subband and the number of non-SBFD symbols of the scheduled/configured transmission is above the threshold, the WTRU may use all the indicated RBs in the non-SBFD symbols and use only the RBs located within the UL subband in SBFD symbols for the uplink transmission (e.g., Alternative 2 in FIG. 5). Such threshold may be configured to the WTRU or fixed by a specification.

[0150] In another example, if some of the RBs indicated/configured by the FDRA are located outside the UL subband and the ratio of SBFD symbols over non-SBFD symbols of the scheduled/configured transmission is above a threshold, the WTRU may use (only) the RBs within the UL subband for both SBFD and non-SBFD symbols for the transmission. If some of the RBs indicated/configured by the FDRA are located outside the UL subband and the ratio of SBFD symbols over non-SBFD symbols of the scheduled/configured transmission is below the threshold, the WTRU may use all the indicated RBs in the non-SBFD symbols and use only the RBs located within the UL subband in SBFD symbols for the uplink transmission. Such threshold may be configured to the WTRU or fixed in the specification.

[0151] Referring to FIG. 6, a third embodiment, referred to as Alternative 3, diagram 600 is shown where a first RB allocation 617 is used in a slot 605 for SBFD symbol(s) 615 and a second, different RB allocation 610 is used in non- SBFD symbols 620. In some examples, the WTRU may be configured to determine a different RB allocation for SBFD symbols and non-SBFD symbols. In one example, the WTRU may determine the RB allocation for non-SBFD symbols using the indicated/configured FDRA and determine the RB allocation for SBFD symbols using a factor. The factor may be RRC and/or dynamically indicated or configured from the gNB or alternatively determined by the WTRU. For example, in diagram 600, using the number S1 of SBFD symbols 615 and the number S2 of non-SBFD symbols 620, the WTRU may calculate the factor as S1/S2. The WTRU may calculate the number N1 of allocated RBs 617 in SBFD symbols 615 as: N1=N2x S1/S2 where N2 is the number of allocated RBs 610 in the non-SBFD symbols 620 indicated by the FDRA. In another example, the WTRU may calculate the factor as NT 1/NT2, where NT 1 and NT2 are the total number of RBs of the uplink subband 619 and uplink bandwidth part 630, respectively. The WTRU may calculate the number N1 of allocated RBs 617 in SBFD symbols 615 as: N1=N2x NT1/ NT2 where N2 is the number of allocated RBs 610 in the non-SBFD symbols 620, which may indicated by the FDRA.

[0152] In another example solution, the WTRU may determine the RB allocation for SBFD symbols using the indicated/configured FDRA and determine the RB allocation for non-SBFD symbols using a multiplying factor. The multiplying factor may be RRC and/or dynamically indicated or configured from the gNB or alternatively determined by the WTRU. For example, using the number of SBFD symbols and the number of non-SBFD symbols, the WTRU may calculate the multiplying factor as S2/S1 , where S1 and S2 are the number of SBFD symbols non-SBFD symbols respectively. The WTRU may calculate the number of allocated RBs N2 in non-SBFD symbols as: N2=N1x S2/S1 where N1 is the number of allocated RBs in the SBFD symbols indicated by FDRA. In another example, the WTRU may calculate the multiplying factor as NT2/NT 1 , where NT 1 and NT2 are the total number of RBs of the uplink subband and uplink bandwidth part respectively. The WTRU may calculate the number of allocated RBs N2 in non-SBFD symbols as: N2=N1x NT2/ NT1 where N1 is the number of allocated RBs in the SBFD symbols indicated by FDRA.

[0153] Embodiments for transmit power determination for the uplink transmission with SBFD and non-SBFD symbols are now described. In certain embodiments, a WTRU configuration includes two set of power control parameters. In an example, the WTRU may be configured with two power control parameter sets when the WTRU is configured with SBFD. A first power control parameter set for uplink transmission on SBFD symbols and a second power control parameter set for transmission on non-SBFD symbols. The first power control parameter set may include a first Pcmax P_cmaXil, a first P0_nominal_PUSCH P_{o n}ominai,puscH? , ^a first P0_UE_PUSCH P_{o UE},PUSCH,I a first a_{l t} a first reference signal (RS) for pathloss estimation, and/or a first closed-loop adjustment index. To determine the transmit power P_PUSCH f°^r the PUSCH transmission when using the first power control parameter set, the WTRU may use the following equation:

PPUSCH min{P_C7nax i, PQ nominal,! + 10 log]o(2^M g^{, f}'^H) + a PL + _pp + } Eq. 1

[0154] Where P_o nominal, i = P_o nominal, PUSCH, i + Po UE, PUSCH, 1 , A is the subcarrier spacing, M ^SCH is the total number of allocated RBs for PUSCH, PL is the downlink estimated pathloss, A_FF is the bits per resource element and f is the transmit power control (TPC) adjustment command.

[0155] The second power control parameter set may include a second Pcmax, P_cmax? < ^a second P0_nominal_PUSCH, P_o nominal, PUSCH, 2 < ^a second P0_UE_PUSCH P_{o UE}, PUSCH, ^a second a₂, a second RS for pathloss estimation, and/or a second closed-loop adjustment index. To determine the transmit power P_PUSCH f°^r the PUSCH transmission when using the second power control parameter set, the WTRU may use the following formula:

[0156] Where P_o nominal? = P nominal, PUSCH? + Po UE, PUSCH? , A is the subcarrier spacing, M ^SCH is the total number of allocated RBs for PUSCH, PL is the downlink estimated pathloss, A_FF is the bits per resource element and f is the TPC adjustment command. In these examples, the first power control parameter set may be associated with uplink transmission using non-SBFD symbols only and the second power control parameter set can be associated with uplink transmission using SBFD symbols only.

[0157] In other examples, the WTRU may determine the same power control parameters for SBFD and non-SBFD symbols. When the WTRU is configured/scheduled to send an uplink transmission occupying both SBFD and non- SBFD symbols, the WTRU may determine one of the two power control parameter sets for the uplink transmission occupying SBFD symbols and non-SBFD symbols. In some examples, the WTRU may apply the same power control parameter set for SBFD symbols and non-SBFD symbols when one or more of the following is satisfied:

[0158] (i) the same number of RBs are used for the uplink transmission in SBFD and non-SBFD symbols;

[0159] (ii) the ratio of the number of SBFD symbols over the number of non-SBFD symbols is below a configured or indicated threshold;

[0160] (iii) the number of SBFD symbols is above a configured or indicated threshold;

[0161] (iv) the number of non-SBFD symbols is above a configured or indicated threshold; and/or

[0162] (v) the WTRU is configured with a transmission in the slot after the SBFD slot, where the slot may be (n+1)- th slot if the SBFD slot is n-th slot, e.g., for a transmission block over multiple slots (TBoMS) scheme or multi-slot repetition scheme, etc.

[0163] When the WTRU applies the same power control parameter set, the WTRU may be configured to apply either the first power control parameter set or the second power control parameter set. For example, the WTRU may be configured to apply the second power control parameter set for both SBFD symbols and non-SBFD symbols. In another example, the WTRU may be configured to apply the first power control parameter set for both SBFD symbols and non-SBFD symbols.

[0164] In another example, the WTRU may apply separate power control parameter sets for SBFD symbols and non-SBFD symbols when a different number of RBs are used in SBFD and non-SBFD symbols for the uplink transmission. For example, the WTRU may select the first power control parameter set for non-SBFD symbols and the second power control parameter set for SBFD symbols, e.g., on condition that the WTRU determines a different number of RBs are used in SBFD and non-SBFD symbols for the uplink transmission.

[0165] Transmission parameters for a physical channel with either SBFD symbols or non-SBFD symbols are also disclosed.

[0166] In one example, the WTRU may select only SBFD symbols for the transmission. In various embodiments, the WTRU may be configured to transmit part of the uplink transmission when the uplink transmission is configured/indicated to have both SBFD and non-SBFD symbols and/or when the WTRU determines that transmission with both SBFD and non-SBFD symbols is not allowed, e.g., the WTRU transmits in a sub-set of scheduled resources and does not transmit in the remaining part. In one example, the WTRU may transmit using only the SBFD symbols, e.g., when the number of SBFD symbols of the configured/scheduled transmission is greater than the number of non- SBFD symbols. In another example, the WTRU may transmit using only the SBFD symbols, e.g., when the ratio of SBFD symbols over the number of non-SBFD symbols is greater than a threshold. [0167] In some embodiments, the WTRU may transmit using only the SBFD symbols if the WTRU measures low cross link interference from the downlink subband. For example, the WTRU may be configured to measure downlink reference signal (e.g., non-zero power RS or zero-power RS) in the downlink subband adjacent(s) to the uplink subband. The WTRU may determine a quality metric (e.g., RSRP, power measurement on a resource, RSSI, etc.) of the DL reference signal and if the measured quality metric is below a threshold, the WTRU may assume that cross link interference is low and consequently may use the SBFD symbols. In another example, the WTRU may be configured to measure power received in a set of resource elements in the uplink subband (e.g., configured/indicated for the transmission). If the measured power in the configured set of resource elements within uplink subband is below threshold, the WTRU may assume that cross link interference is low and consequently may use the SBFD symbols.

[0168] In other example embodiments, the WTRU may transmit using only the SBFD symbols if the WTRU has data transmission with a certain quality of service. The quality of service may include priority, latency and/or the reliability. For example, when the WTRU is configured/scheduled with low latency data transmission, the WTRU may select to transmit on SBFD symbols when the SBFD symbols are before non-SBFD symbols. The WTRU may be configured with QoS flow, Data Radio Bearer, logical channel ID or logical channel group for which transmission on only SBFD symbols is allowed.

[0169] In other examples, the WTRU selects only non-SBFD symbols for the uplink transmission. The WTRU may be configured to transmit part of the uplink transmission when the uplink transmission is configured/indicated to have both SBFD and non-SBFD symbols and/or when the WTRU determines that transmission with both SBFD and non- SBFD symbols is not allowed. In one example, the WTRU may transmit using only the non-SBFD symbols when the number of non-SBFD symbols of the configured/scheduled transmission is greater than the number of SBFD symbols. In another example, the WTRU may transmit using only the non-SBFD symbols when the ratio of SBFD symbols over the number of non-SBFD symbols is below a threshold.

[0170] In some examples, the WTRU may transmit using only the non-SBFD symbols if the WTRU measures high cross link interference from the downlink subband. For example, the WTRU may be configured to measure downlink reference signal (e.g., non-zero power RS or zero-power RS) in the downlink subband adjacent(s) to the uplink subband. The WTRU may determine a quality metric (e.g., RSRP, power measurement on a resource, RSSI, etc.) of the DL reference signal and if the measured RSRP is above a threshold, the WTRU assumes that cross link interference is high and consequently may use only the non-SBFD symbols. In another example, the WTRU may be configured to measure power received in a set of resource elements in the uplink subband (e.g., configured/indicated for the transmission). If the measured power in the configured set of resource elements within uplink subband is above a threshold, the WTRU may assume that cross link interference is high and consequently may use only the non-SBFD symbols.

[0171] In another example, the WTRU may transmit using only the non-SBFD symbols if the WTRU has data transmission with a certain quality of service (QoS). The quality of service may include priority, latency and/or the reliability. For example, when the WTRU is configured/scheduled with high reliability data transmission, the WTRU may select to transmit on only non-SBFD symbols to better protect the transmission from the interference. The WTRU may be configured with QoS flow, Data Radio Bearer, logical channel ID or logical channel group for which transmission on only non-SBFD symbols is allowed. [0172] Referring to FIG. 7, an example method 700 is shown for a WTRU determining to use one or both SBFD and non-SBFD symbols for uplink transmission. The WTRU determines whether to use one or both of SBFD and non- SBFD symbols for an UL transmission based on the number of SBFD symbols and the DMRS configuration for the transmission. When the WTRU determines to use both SBFD and non-SBFD symbols for the transmission, the WTRU determines the RB allocation for each of the SBFD and non-SBFD symbols based on one or more of the UL subband configuration for the SBFD symbols, the configured or indicated frequency allocation, and the number of SBFD symbols and/or the number of non-SBFD symbols for the transmission.

[0173] As shown by the example method 700 in FIG. 7, the WTRU receives configuration 705 of at least one of a first set of slots that have only SBFD symbols, a second set of slots that have only non-SBFD symbols and a third set of slots that have both SBFD and non-SBFD symbols.

[0174] The WTRU receives a configuration or indication (e.g., in a scheduling or activating DCI) indicating to transmit an uplink transmission in a slot in the third set of slots. The indication includes a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA) for the transmission. In an example, the TDRA may indicate a row or entry in a configured list or table of resource allocations. The TDRA may indicate an allocation that spans or includes both SBFD symbol(s) and non-SBFD symbol(s) of the slot. The FDRA may indicate one or more RBs for the UL transmission.

[0175] Next, the WTRU determines 710 whether to use both SBFD and non-SBFD symbols for the uplink transmission. In various embodiments, this determination may be based on one or more of the following considerations (1 )-(4) and/or any determination considerations previously described.

[0176] (1) A number of DMRS REs or a location of a DMRS (e.g., comprising one or more DM-RS REs) in the

SBFD symbols and/or non-SBFD symbols. For example, if the WTRU determines that the number of DMRS-REs in the non-SBFD symbol(s) of the slot or the TDRA is above a configured threshold, the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission.

[0177] (2) A time gap between the SBFD and non-SBFD symbols. For example, if the WTRU determines that the time gap between the SBFD and non-SBFD symbols (e.g., of the slot or TDRA) is below a configured threshold, the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission.

[0178] (3) The number of SBFD and non-SBFD symbols. For example, if the WTRU determines that the ratio of the number of SBFD to the number of non-SBFD symbols (e.g., in the slot or TDRA) is below a configured threshold, the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission.

[0179] (4) The indicated TDRA (e.g., TDRA row or entry). For example, if the indicated TDRA indicates a time domain allocation in both SBFD and non-SBFD symbols, the WTRU determines to use both SBFD and non-SBFD symbols for the uplink transmission.

[0180] When the WTRU determines at step 710 to use both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines 715 the RB allocation for the uplink transmission and transmits 720 the UL transmission in the SBFD and non-SBFD symbols (e.g., of the TDRA). As mentioned previously, in Alternative 1 , when the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines the RB allocation using the indicated FDRA where the reference point for the resource allocation is the first RB of the UL subband in the SBFD symbols and the WTRU uses the same RB allocation in the SBFD and non-SBFD symbols.

[0181] In Alternative 2, when the WTRU uses both SBFD and non-SBFD symbols for the uplink transmission, the WTRU determines 715 the RB allocation for the SBFD and non-SBFD symbols based on the UL subband configuration, the number of SBFD symbols and the indicated FDRA (where the reference point for the resource allocation is the first RB of the UL BWP). For example, if some of the RBs indicated by the FDRA are located outside the UL subband and the number of SBFD symbols (e.g., in the slot or TDRA) is above a threshold, the WTRU uses only the RBs within the UL subband for both SBFD and non-SBFD symbols for the transmission. Otherwise, for example, the WTRU uses all the indicated RBs in the non-SBFD symbols and uses only the RBs located within the UL subband in SBFD symbols. The WTRU then sends 720 the uplink transmission over both SBFD and non-SBFD symbols using the determined RB allocation.

[0182] In the event the WTRU determines at step 710 not to use both SBFD and non-SBFD symbols, the WTRU selects 725 and transmits on either the SBFD symbol(s) or the non-SBFD symbol(s) (e.g., of the TDRA), based on the number of SBFD and/or non-SBFD symbols (e.g., of the slot or TDRA). For example, the WTRU transmits using only the non-SBFD symbols when the number of non-SBFD symbols is greater than the number of SBFD symbols. Alternatively, for example, the WTRU transmits using only the SBFD symbols when the number of SBFD symbols is greater than the number of non-SBFD symbols.

[0183] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer- readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as 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, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMS What is Claimed:

1 . A method for a wireless transmit/receive unit (WTRU), the method comprising: determining to use one or more subband full duplex (SBFD) symbols and one or more non-SBFD symbols in a time instance allocated for an uplink (UL) transmission, wherein the determination is based on a configuration of at least one of a number of the SBFD symbols and a number of the non-SBFD symbols in the time instance or a time gap between the SBFD symbols and the non-SBFD symbols in the time instance and respective thresholds; determining a resource block (RB) allocation in the time instance for the SBFD symbols and the non- SBFD symbols; and sending, on a physical channel, the UL transmission using the determined RB allocation for the SBFD symbols and the non-SBFD symbols.

2. The method of claim 1 , wherein the time instance comprises one of a slot or a subframe.

3. The method of claim 1 , wherein determining the RB allocation is based on one or more of an UL subband configuration for the SBFD symbols, a configured or indicated frequency allocation of the UL transmission, the configured number of the SBFD symbols or the configured number of the non-SBFD symbols for the time instance.

4. The method of claim 1 , wherein the determined RB allocation is the same for the SBFD symbols and for the non-SBFD symbols.

5. The method of claim 1 , wherein the determined RB allocation is different for the SBFD symbols than the non- SBFD symbols.

6. The method of claim 1 , wherein determining to use the one or more SBFD symbols and the one or more non- SBFD symbols for the UL transmission is further based on one or more of: a configured number of demodulation reference signal DMRS resource elements (REs) or a location of a DMRS RE in the SBFD symbols or the non-SBFD symbols; or an indicated time domain resource allocation (TDRA) in both the SBFD symbols and the non-SBFD symbols.

7. The method of claim 1 , wherein the determined RB allocation for the SBFD symbols and the non-SBFD symbols is within a configured UL subband of the SBFD symbols.

8. The method of claim 1 , wherein prior to sending the UL transmission, the method further comprises: determining a transmit power for the SBFD symbols and the non-SBFD symbols based on a configured power control parameter set for each respective type of symbol.

9. The method of claim 1 , wherein the physical channel comprises one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH) or a physical random access channel (PRACH).

10. A wireless transmit/receive unit (WTRU) comprising: a processor; and a transceiver operatively coupled with the processor, wherein the processor and the transceiver are configured to: determine to use one or more subband full duplex (SBFD) symbols and one or more non-SBFD symbols in a time instance allocated for an uplink (UL) transmission, wherein the determination is based on a configuration of at least one of a number of the SBFD symbols and a number of the non-SBFD symbols in the time instance or a time gap between the SBFD symbols and the non-SBFD symbols in the time instance and respective thresholds; determine a resource block (RB) allocation in the time instance for the SBFD symbols and the non-SBFD symbols; and send, on a physical channel, the UL transmission using the determined RB allocation for the SBFD symbols and the non-SBFD symbols.

11. The WTRU of claim 10, wherein the time instance comprises one of a slot or a subframe.

12. The WTRU of claim 10, wherein determining the RB allocation is based on one or more of an UL subband configuration for the SBFD symbols, a configured or indicated frequency allocation of the UL transmission, the configured number of SBFD symbols or the configured number of non-SBFD symbols for the time instance.

13. The WTRU of claim 10, wherein the determined RB allocation is the same for the SBFD symbols and for the non-SBFD symbols.

14. The WTRU of claim 10, wherein the determined RB allocation is different for the SBFD symbols than the non- SBFD symbols.

15. The WTRU of claim 10, wherein determining to use the SBFD symbols and the non-SBFD symbols for the UL transmission is further based on one or more of: a configured number of demodulation reference signal DMRS resource elements (REs); a location of a DMRS RE in the SBFD symbols or the non-SBFD symbols; or an indicated time domain resource allocation (TDRA) in both the SBFD symbols and the non-SBFD symbols.

16. The WTRU of claim 10, wherein the determined RB allocation for the SBFD symbols and the non-SBFD symbols is within a configured UL subband of the SBFD symbols.

17. The WTRU of claim 10, wherein prior to sending the UL transmission, the processor and the transceiver are further configured to: determine a transmit power for the SBFD symbols and the non-SBFD symbols based on a configured power control parameter set for each respective type of symbol.

18. The WTRU of claim 10, wherein the physical channel comprises one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH) or a physical random access channel (PRACH).