WO2025237033A1

WO2025237033A1 - Methods for multi-slot pdsch/pusch fdra enhancements in sbfd

Info

Publication number: WO2025237033A1
Application number: PCT/CN2025/090842
Authority: WO
Inventors: Sumaila Anning MAHAMA; Mohammed S Aleabe AL-IMARI
Original assignee: MediaTek Inc
Current assignee: MediaTek Inc
Priority date: 2024-05-14
Filing date: 2025-04-24
Publication date: 2025-11-20
Anticipated expiration: 2026-11-14

Abstract

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE receives a frequency domain resource allocation (FDRA) configuration for a multi-slot transmission across a plurality of slots. The plurality of slots include at least one partitioned slot and at least one non-partitioned slot, the at least one partitioned slot including both downlink (DL) resources and uplink (UL) resources, and the at least one non-partitioned slot including only DL resources or only UL resources. The UE receives an FDRA configuration indicator indicating a usable slot set among the plurality of slots for applying the FDRA configuration. The UE applies the FDRA configuration to the usable slot set.

Description

METHODS FOR MULTI-SLOT PDSCH/PUSCH FDRA ENHANCEMENTS IN SBFD

CROSS-REFERENCE TO RELATED APPLICATION (S)

This application claims the benefits of U.S. Provisional Application Serial No. 63/647,127, entitled “Methods for Multi-slot PDSCH/PUSCH FDRA Enhancements in SBFD” and filed on May 14, 2024, which is expressly incorporated by reference herein in its entirety.

BACKGROUND Field

The present disclosure relates generally to wireless communications, and more particularly, to techniques for multi-slot PDSCH/PUSCH FDRA enhancements in SBFD.
Background

The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2 is a diagram illustrating a base station in communication with a UE in an access network.

FIG. 3 illustrates an example logical architecture of a distributed access network.

FIG. 4 illustrates an example physical architecture of a distributed access network.

FIG. 5 is a diagram showing an example of a DL-centric slot.

FIG. 6 is a diagram showing an example of an UL-centric slot.

FIG. 7 is a diagram illustrating configurations of time-frequency radio resources in SBFD.

FIG. 8 illustrates a flow chart of a process for multi-slot PDSCH/PUSCH FDRA enhancements in SBFD.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through backhaul links 132 (e.g., SI interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over backhaul links 134 (e.g., X2 interface) . The backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102’ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102’ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102’ , employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

A base station 102, whether a small cell 102’ or a large cell (e.g., macro base station) , may include an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band (e.g., 3 GHz -300 GHz) has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 108a. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the SMF 194 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Although the present disclosure may reference 5G New Radio (NR) , the present disclosure may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A) , Code Division Multiple Access (CDMA) , Global System for Mobile communications (GSM) , or other wireless/radio access technologies.

FIG. 2 is a block diagram of a base station 210 in communication with a UE 250 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 275. The controller/processor 275 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 275 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 216 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams destined for the UE 250. If multiple spatial streams are destined for the UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to the controller/processor 259, which implements layer 3 and layer 2 functionality.

The controller/processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. In the UL, the controller/processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 259 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 210, the controller/processor 259 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may be used by the TX processor 268 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antenna 252 via separate transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218RX receives a signal through its respective antenna 220. Each receiver 218RX recovers information modulated onto an RF carrier and provides the information to a RX processor 270.

The controller/processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer-readable medium. In the UL, the controller/processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller/processor 275 may be provided to the EPC 160. The controller/processor 275 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA) -based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP) ) . NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time division duplexing (TDD) . NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.

A single component carrier bandwidth of 100 MHz may be supported. In one example, NR resource blocks (RBs) may span 12 sub-carriers with a sub-carrier bandwidth of 60 kHz over a 0.25 ms duration or a bandwidth of 30 kHz over a 0.5 ms duration (similarly, 50MHz BW for 15kHz SCS over a 1 ms duration) . Each radio frame may consist of 10 subframes (10, 20, 40 or 80 NR slots) with a length of 10 ms. Each slot may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each slot may be dynamically switched. Each slot may include DL/UL data as well as DL/UL control data. UL and DL slots for NR may be as described in more detail below with respect to FIGs. 5 and 6.

The NR RAN may include a central unit (CU) and distributed units (DUs) . A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells) . For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals (SS) in some cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

FIG. 3 illustrates an example logical architecture of a distributed RAN 300, according to aspects of the present disclosure. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN. The backhaul interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term) . As described above, a TRP may be used interchangeably with “cell. ”

The TRPs 308 may be a distributed unit (DU) . The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated) . For example, for RAN sharing, radio as a service (RaaS) , and service specific ANC deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

The local architecture of the distributed RAN 300 may be used to illustrate fronthaul definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) . The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 302. According to aspects, no inter-TRP interface may be needed/present.

According to aspects, a dynamic configuration of split logical functions may be present within the architecture of the distributed RAN 300. The PDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.

FIG. 4 illustrates an example physical architecture of a distributed RAN 400, according to aspects of the present disclosure. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have distributed deployment. The C-RU may be closer to the network edge. A distributed unit (DU) 406 may host one or more TRPs. The DU may be located at edges of the network with radio frequency (RF) functionality.

FIG. 5 is a diagram 500 showing an example of a DL-centric slot. The DL-centric slot may include a control portion 502. The control portion 502 may exist in the initial or beginning portion of the DL-centric slot. The control portion 502 may include various scheduling information and/or control information corresponding to various portions of the DL-centric slot. In some configurations, the control portion 502 may be a physical DL control channel (PDCCH) , as indicated in FIG. 5. The DL-centric slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centric slot. The DL data portion 504 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE) . In some configurations, the DL data portion 504 may be a physical DL shared channel (PDSCH) .

The DL-centric slot may also include a common UL portion 506. The common UL portion 506 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion 506 may include feedback information corresponding to various other portions of the DL-centric slot. For example, the common UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion 506 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs) , and various other suitable types of information.

As illustrated in FIG. 5, the end of the DL data portion 504 may be separated in time from the beginning of the common UL portion 506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE) ) to UL communication (e.g., transmission by the subordinate entity (e.g., UE) ) . One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

FIG. 6 is a diagram 600 showing an example of an UL-centric slot. The UL-centric slot may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the UL-centric slot. The control portion 602 in FIG. 6 may be similar to the control portion 502 described above with reference to FIG. 5. The UL-centric slot may also include an UL data portion 604. The UL data portion 604 may sometimes be referred to as the pay load of the UL-centric slot. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS) . In some configurations, the control portion 602 may be a physical DL control channel (PDCCH) .

As illustrated in FIG. 6, the end of the control portion 602 may be separated in time from the beginning of the UL data portion 604. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity) . The UL-centric slot may also include a common UL portion 606. The common UL portion 606 in FIG. 6 may be similar to the common UL portion 506 described above with reference to FIG. 5. The common UL portion 606 may additionally or alternatively include information pertaining to channel quality indicator (CQI) , sounding reference signals (SRSs) , and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS) , even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .

FIG. 7 is a diagram 700 illustrating configurations of time-frequency radio resources in Subband Full Duplex (SBFD) . To illustrate the SBFD mode, FIG. 7 depicts an exemplary layout of time-frequency radio resource allocation in SBFD for a user equipment (e.g., UE 104 shown in FIG. 1) served by a network through a base station (e.g., base station 102 shown in FIG. 1) . For example, the UE 104 may receive an SBFD-related configuration indicating the exemplary layout. The SBFD-related configuration may be configured by the base station 102 via higher layer signaling.

The layout may be based on a time division duplex (TDD) mechanism. In legacy TDD operation, time slots are strictly divided into downlink (DL) slots and uplink (UL) slots. For example, a sequence of DL slots is followed by a UL slot, and this pattern repeats over time. In such legacy systems, a UE performs DL reception during DL slots and UL transmission during UL slots.

In full duplex implementations, certain DL slots are converted into subband full duplex (SBFD) slots, also referred to as partitioned slots. In these slots, a portion of the DL resources is reallocated for UL transmission. This enables the UE to perform UL transmission on a portion of the resources that were previously dedicated to DL. The primary objective of this configuration is to increase UL transmission opportunities for UEs within a TDD carrier. The TDD may utilize the single carrier with a flexible UL and DL ratio to accommodate asymmetric UL and DL requirements. The exemplary layout shown in FIG. 7 depicts a TDD uplink (UL) /downlink (DL) configuration with a 5-slot time-domain pattern [D D D D U] per TDD period, where D represents a DL slot and U represents a UL slot.

Such a TDD pattern can be periodically repeated. FIG. 7 depicts two TDD periods. As illustrated in FIG. 7, a first TDD period includes slots 701-705 and a second TDD period includes slots 711-715. In the first TDD period, slots 701-704 are configured as DL slots, and slot 705 is configured as a UL slot. Similarly, in the second TDD period, slots 711-714 are configured as DL slots, and slot 715 is configured as a UL slot.

A set of subbands (SBs) may be introduced within the DL slots and a SB may include one or more contiguous resource blocks (RBs) . For example, according to the configuration, for each of the middle three DL slots in the first and second periods, the frequency resources may be partitioned into two DL SBs and one UL SB. As shown in FIG. 7, frequency resources in slot 702 are partitioned into two DL SBs 702a-b (i.e., the upper and lower parts) and one UL SB 702c (i.e., the middle part) . Similarly, frequency resources in slot 712 are partitioned into two DL SBs 712a-b (i.e., the upper and lower parts) and one UL SB 712c (i.e., the middle part) . Note that although the resource allocation layout for SBFD operation shown in FIG. 7 has a subband partitioning pattern of [D U D] , other subband partitioning patterns are possible in various embodiments. For example, the subband partitioning pattern may be [D U] or [U D] .

By introducing UL subbands into original DL slots, the base station 102 may operate in the SBFD mode during these partitioned slots: DL transmission and UL reception may be performed separately and simultaneously in DL SBs and UL SBs, respectively. The partitioned slots may be referred to as SBFD slots. The first full (or non-partitioned) DL slot and the last full UL slot shown in FIG. 7 may be referred to as non-SBFD slots. In other words, a partitioned (SBFD) slot/symbol includes both UL and DL resources, whereas a non-partitioned (non-SBFD) slot/symbol only include either UL or DL resources. Notably, in the present disclosure, the terms 'slot' and 'symbol' are not strictly distinguished. Any behavior or operation described with respect to a slot may, where appropriate, be equally applicable to a symbol at a finer granularity, and vice versa.

In operation, the UE 104 may perform uplink or downlink transmission based on resource configuration received from the base station 102. For example, an uplink transmission may include transmission of a physical uplink control channel (PUCCH) , a sounding reference signal (SRS) , and other physical channels or signals. The uplink transmission may be periodic, semi-persistent, or aperiodic. Some of the uplink transmissions 104 may be repeated across multiple consecutive slots.

During SBFD slots, the UE 104 may operate in either full-duplex or half-duplex mode, for example, depending on the capability of the UE 104. In 3GPP Release 19, an SBFD-aware UE may be full-duplex capable, meaning that such a UE is capable of simultaneously transmitting and receiving data on time-overlapping resources. Prior to 3GPP Release 19, UEs were typically half-duplex, meaning that while a gNodeB could simultaneously transmit and receive data at any given time, a UE could only either transmit or receive data at any given time. As a result, full-duplex capable SBFD-aware UEs can provide higher maximum user throughput with bidirectional data and lower latency. Additionally, such SBFD-aware UEs can also use downlink packets to provide additional hybrid automatic repeat-request (HARQ) DL retransmission opportunities. These advantages may be particularly beneficial in latency-critical applications, such as video streaming in virtual reality (VR) or extended reality (XR) environments.

According to the specifications of existing 3GPP standards, the same Frequency Domain Resource Allocation (FDRA) is uniformly applied across all transmission occasions of Semi-Persistent Scheduling Physical Downlink Shared Channel (SPS PDSCH) , regardless of whether repetitions are configured or not. That is, the same resource allocation is used across multiple slots, which may be a combination of full slots and SBFD partitioned slots, such as the slots 701-704.

Similarly, according to the current specifications, the same FDRA is uniformly applied across all transmission occasions of Configured Grant Physical Uplink Shared Channel (CG PUSCH) , regardless of whether repetitions are configured or not.

The network may be configured to allocate a portion of the available frequency domain resources to a UE on specific slots or symbols. Frequency-domain resources for PDSCH and PUSCH may be allocated dynamically through downlink control information (DCI) , using either Type-0 or Type-1 FDRA. Type-0 FDRA is based on a bitmap where each bit of the bitmap represents an RB group (RBG) in a resource allocation (e.g., a SBFD partitioned slot) , in which the RB size of the RBG is dependent on a bandwidth part (BWP) size. Accordingly, Type-0 FDRA can be readily used to provide flexible and non-contiguous RB allocations, which may be required in SBFD operation to allocate RBs from multiple non-contiguous DL SBs. In contrast, Type-1 FDRA is defined based on a starting RB and an RB length, which span a contiguous set of Physical Resource Blocks (PRBs) .

However, the utilization of a single FDRA indication for SPS PDSCH in SBFD operation may result in allocated resources that fall outside the DL resources within SBFD slots/symbols. Specifically, the DL allocation may overlap with UL resources and/or guardband resources. For example, as illustrated in FIG. 7, a DL multi-slot transmission starts at the non-SBFD slot 701, where the FDRA is defined based on the starting RB 706 at a middle frequency location in slot 701. Subsequently, in SBFD slots 702-704, according to the indication of the starting RB 706, the SPS PDSCHs are allocated from the middle frequency locations in slots 702-704 (i.e., the UL SB) , falling outside the DL SBs. As a result, taking slot 702 as an example, the SPS PDSCH 707 overlaps with the UL SB 702c, thereby resulting in a resource allocation conflict. In this scenario, the UE is not supposed to perform downlink reception on resources allocated for uplink transmission, leading to inefficient or invalid resource utilization.

Similarly, the utilization of a single FDRA indication for CG PUSCH in SBFD operation may result in allocated resources that fall outside the UL resources within SBFD slots/symbols. Specifically, the UL allocation may overlap with DL resources and/or guardband resources. For example, as illustrated in FIG. 7, a UL multi-slot transmission starts at the non-SBFD slot 705, where the FDRA is defined based on the starting RB 716 at an upper frequency location in slot 705. Subsequently, in SBFD slots 702-704, according to the indication of the starting RB 716, the CG PUSCHs are allocated from the upper frequency locations in slots 702-704 (i.e., the upper DL SBs) , falling outside the UL SB. As a result, taking slot 702 as an example, the CG PUSCH 717 overlaps with the upper DL SB 702a, thereby resulting in a resource allocation conflict. In this scenario, the UE is not supposed to perform uplink transmission on resources allocated for downlink reception, leading to inefficient or invalid resource utilization.

Consequently, there arises a need to configure FDRA for SPS PDSCH and/or CG PUSCH, both with and without repetitions, to address such resource allocation conflicts.

To address this issue, the present disclosure proposes enhancements to FDRA. Specifically, the FDRA mechanism is reinterpreted or modified such that the UE does not encounter scenarios where resource allocations are rendered unusable due to overlaps with resources allocated for the opposite transmission direction (e.g., DL allocation overlapping with UL resources, or vice versa) . Specifically, for a transmission (e.g., PDSCH or PUSCH) over a plurality of slots, together with a configured FDRA, the network may also instruct the UE on how to apply the configured FDRA. That is, among the plurality of slots, the network may indicate which slots can be applied by the configured FDRA. In this disclosure, these slots are referred to as a "usable slot set. "By indicating the usable slot set, the network can establish that the UE does not encounter resource allocation conflicts.

The usable slot set may be cell-specific and/or UE-specific. For example, the network may use cell-specific higher layer signaling to indicate a cell-specific usable slot set, and use UE-specific higher layer signaling to indicate a UE-specific usable slot set. When receiving an FDRA configuration indicator indicating a cell-specific usable slot set, the UE may apply the configured FDRA associated with the indicator to the usable slot set based on its capabilities. Specifically, if the UE does not support simultaneous transmission and reception on time-overlapping resources, it may only use one type of slots, even if the FDRA configuration indicator allows both partitioned and non-partitioned slots. In the case of a UE-specific usable slot set, the network may configure the usable slot set for a specific UE based on the UE’s capabilities. According to 3GPP agreements, Configuration 1 (restricting transmissions/receptions to SBFD symbols only or non-SBFD symbols only) will be the default UE behavior, while Configuration 2 (allowing transmissions/receptions in both SBFD and non-SBFD symbols) may be supported based on UE capability.

In an SPS PDSCH scenario, a UE (e.g., the UE 104) may be configured to apply FDRA for SPS PDSCH, with or without repetitions, to a specific set of slots or symbols (e.g., the usable slot set) . For example, the UE 104 may receive a resource allocation and periodicity configuration, which it applies whenever the scheduled period occurs and data is available for reception.

The UE 104 may be provided with the time and frequency location of the SB through cell-specific and/or UE-specific higher layer signaling. Additionally, the UE 104 may be provided with the FDRA configuration for SPS PDSCH via higher layer signaling.

In certain configurations, the network, such as through the base station 102, may instruct the UE 104 to apply a configured FDRA for SPS PDSCH to a specific set of slots or symbols. Specifically, the configuration may include:
(1) the network instructs the UE 104 to apply a configured FDRA for SPS PDSCH exclusively
to partitioned slots or symbols.
(2) the network instructs the UE 104 to apply a configured FDRA for SPS PDSCH exclusively
to non-partitioned slots or symbols. In the context of SPS PDSCH, a non-partitioned slot or symbol refers to a slot or symbol containing only DL resources.
(3) the network instructs the UE 104 to apply the configured FDRA for SPS PDSCH to both
partitioned and non-partitioned slots or symbols. This option is based on the UE's capability to handle such allocations.

If the UE 104 is instructed to apply the FDRA for SPS PDSCH to both partitioned and non-partitioned slots or symbols, the UE 104 does not expect the FDRA to overlap with UL and/or guardband resources on partitioned symbols. That is, if the network configures the UE 104 to apply the allocation to both slot or symbol types, it may be the network's responsibility to configure the FDRA in such a way that no overlap occurs. For example, the network may configure the FDRA to fall within the upper or lower DL SBs, such that the allocation does not conflict with UL or guard band resources.

The determination of the slot or symbol type depends on the channel type and configuration conditions. For example, when sufficient frequency resource can be allocated such that a PDSCH transmission does not overlap an uplink subband in a SBFD slot, both non-SBFD and SBFD slots are usable.

For Radio Resource Control (RRC) or SPS, the configuration is provided via RRC signaling. Specifically, the configuration parameter for SPS is referred to as SPS-Config.

In certain configurations, the network may provide the UE 104 with a symbol type parameter (e.g., symbolType) which is added to the configuration to indicate the set of slots or symbols on which the configured FDRA for SPS PDSCH is to be applied. Through the new parameter (i.e., FDRA configuration indicator) , the network may provide the UE 104 with the following information:
(1) the time and frequency location of the SB; and/or
(2) the partitioning configuration, including which slots are partitioned and the size of the DL
and UL SBs.

The instructions on which slots or symbols to apply the resource allocation establish that the allocation does not overlap with resources allocated for the opposite transmission direction.

The new parameter may be provided in various ways. For example:
(1) The new parameter may be provided to the UE 104 via higher layer signaling. For example,
the new parameter may be provided within the SPS-Config information element.
(2) The new parameter may be provided to the UE 104 via Layer 1 signaling. For example,
the new parameter may be provided within the scheduling DCI. In scenarios involving repetitions, if the UE 104 receives the configuration via DCI, the symbol type parameter may be included within the DCI.

In certain configurations, the new parameter may have some possible values, indicating to the UE 104 whether to apply the configured FDRA for SPS PDSCH to: (1) Partitioned slots/symbols, (2) Non-partitioned slots/symbols, or (3) Both partitioned and non-partitioned slots/symbols.

Specifically, the interpretation of the parameter values includes:
Value (1) : Partitioned Slots/Symbols (e.g., symbolType = partitionedSymbols)
When the UE 104 receives Value (1) , the UE 104 considers the FDRA for SPS PDSCH to be
valid only for partitioned slots or symbols. That is, the UE 104 applies the FDRA for SPS PDSCH exclusively to partitioned slots or symbols. In contrast, the UE 104 considers the FDRA for SPS PDSCH to be invalid for non-partitioned slots or symbols. Correspondingly, the UE 104 may ignore the FDRA for SPS PDSCH.
Value (2) : Non-Partitioned Slots/Symbols (e.g., symbolType = nonPartitionedSymbols)
When the UE 104 receives (2) , the UE 104 considers the FDRA for SPS PDSCH to be valid only for non-partitioned slots or symbols. That is, the UE 104 applies the FDRA for SPS PDSCH exclusively to non-partitioned slots or symbols. In contrast, the UE 104 considers the FDRA for SPS PDSCH to be invalid for partitioned slots or symbols. Correspondingly, the UE 104 may ignore the FDRA for SPS PDSCH in these slots.
Value (3) : Both Partitioned and Non-Partitioned Slots/Symbols (e.g., symbolType = both)
When the UE 104 receives Value (3) , the UE 104 considers the FDRA for SPS PDSCH to be valid for both partitioned and non-partitioned slots or symbols. That is, the UE 104 applies the FDRA for SPS PDSCH to both partitioned and non-partitioned slots or symbols.

In the case of Value (3) , the UE 104 does not expect the FDRA to overlap with UL and/or guardband resources on partitioned symbols. If such an overlap occurs, the UE 104 considers any portion of the FDRA overlapping with UL or guardband resources as invalid and does not use that portion for PDSCH resource mapping. It is the network’s responsibility to establish that such overlaps do not occur when configuring FDRA for both partitioned and non-partitioned slots or symbols.

In a CG PUSCH scenario, the UE 104 may be configured to apply FDRA for CG PUSCH, with or without repetitions, to a specific set of slots or symbols. The UE 104 may be provided with the time and frequency location of the SB through cell-specific and/or UE-specific higher layer signaling. Additionally, the UE 104 is provided with the FDRA configuration for CG PUSCH via higher layer signaling.

In certain configurations, the network, such as through the base station 102, may instruct the UE 104 to apply a configured FDRA for CG PUSCH to a specific set of slots or symbols (e.g., the usable slot set) . Specifically, the configuration may include:
(1) the network instructs the UE 104 to apply a configured FDRA for CG PUSCH exclusively
to partitioned slots or symbols.
(2) the network instructs the UE 104 to apply a configured FDRA for CG PUSCH exclusively
to non-partitioned slots or symbols. In the context of CG PUSCH, a non-partitioned slot or symbol refers to a slot or symbol containing only UL resources.
(3) the network instructs the UE 104 to apply the configured FDRA for CG PUSCH to both
partitioned and non-partitioned slots or symbols. This option is based on the UE's capability to handle such allocations.

If the UE 104 is instructed to apply the FDRA for CG PUSCH to both partitioned and non-partitioned slots or symbols, the UE 104 does not expect the FDRA to overlap with DL and/or guardband resources on partitioned symbols. That is, if the network configures the UE 104 to apply the allocation to both slot or symbol types, it may be the network's responsibility to establish that the FDRA is configured in such a way that no overlap occurs. For example, the network may configure the FDRA to fall within the middle UL SB, such that the allocation does not conflict with DL or guard band resources.

The determination of the slot or symbol type depends on the channel type and configuration conditions. For example, when sufficient frequency resource can be allocated such that a PUSCH transmission does not overlap a downlink subband in a SBFD slot, both non-SBFD and SBFD slots are usable.

In certain configurations, the network may provide the UE 104 with a symbol type parameter (e.g., symbolType) to indicate the set of slots or symbols on which the configured FDRA for CG PUSCH is to be applied. Through the new parameter (e.g., the FDRA configuration indicator) , the network may provide the UE 104 with the following information:
(1) the time and frequency location of the SB; and/or
(2) the partitioning configuration, including which slots are partitioned and the size of the DL
and UL SBs.

The new parameter may be provided in various ways. For example:
(1) The new parameter may be provided to the UE 104 via higher layer signaling. For example,
the new parameter may be provided within the rrc-ConfiguredUplinkGrant inside configuredGrantConfig parameter structure.
(2) The new parameter may be provided to the UE via Layer 1 signaling. For example, the
new parameter may be provided within the scheduling DCI. In scenarios involving repetitions, if the UE 104 receives the configuration via DCI, the symbol type parameter may be included within the DCI.

In certain configurations, the new parameter may have some possible values, indicating to the UE 104 whether to apply the configured FDRA for CG PUSCH to: (1) Partitioned slots/symbols, (2) Non-partitioned slots/symbols, or (3) Both partitioned and non-partitioned slots/symbols.

Specifically, the interpretation of the parameter values includes:
Value (1) : Partitioned Slots/Symbols (e.g., symbolType = partitionedSymbols)
When the UE 104 receives Value (1) , the UE 104 considers the FDRA for CG PUSCH to be
valid only for partitioned slots or symbols. That is, the UE 104 applies the FDRA for CG PUSCH exclusively to partitioned slots or symbols. In contrast, the UE 104 considers the FDRA for CG PUSCH to be invalid for non-partitioned slots or symbols. Correspondingly, the UE 104 may ignore the FDRA for CG PUSCH.
Value (2) : Non-Partitioned Slots/Symbols (e.g., symbolType = nonPartitionedSymbols)
When the UE 104 receives Value (2) , the UE 104 considers the FDRA for CG PUSCH to be
valid only for non-partitioned slots or symbols. That is, the UE applies the FDRA for CG PUSCH exclusively to non-partitioned slots or symbols. In contrast, the UE 104 considers the FDRA for CG PUSCH to be invalid for partitioned slots or symbols. Correspondingly, the UE 104 may ignore the FDRA for CG PUSCH.
Value (3) : Both Partitioned and Non-Partitioned Slots/Symbols (e.g., symbolType = both)
When the UE 104 receives Value (3) , the UE 104 considers the FDRA for CG PUSCH to be
valid for both partitioned and non-partitioned slots or symbols. That is, the UE applies the FDRA for CG PUSCH to both partitioned and non-partitioned slots or symbols.

In the case of Value (3) , the UE 104 does not expect the FDRA to overlap with DL and/or guardband resources on partitioned symbols. If such an overlap occurs, the UE 104 considers any portion of the FDRA overlapping with DL or guardband resources as invalid and does not use that portion for PUSCH resource mapping. It is the network’s responsibility to establish that such overlaps do not occur when configuring FDRA for both partitioned and non-partitioned slots or symbols.

For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission/reception within a slot has either all SBFD or all non-SBFD symbols) for an SBFD-aware UE, the SBFD-aware UE is provided with one of the following configurations:
Configuration 1: The transmissions/receptions are restricted to SBFD symbols only or non-
SBFD symbols only.
Configuration 2: The transmissions/receptions may occur in both SBFD symbols and non-
SBFD symbols.

For Configuration 1, the valid symbol type is determined as follows:
For semi-statically configured transmissions/receptions without activation DCI, the valid
symbol type is explicitly configured by RRC.
For dynamically scheduled transmissions/receptions, the valid symbol type is determined
based on the symbol type of the first transmission/reception.

For Type 2 CG PUSCH and SPS PDSCH:
The valid symbol type for Type 2 CG PUSCH is determined based on the symbol type of the
first CG PUSCH associated with activation DCI.
The valid symbol type for SPS PDSCH is determined based on the symbol type of the first
SPS PDSCH associated with activation DCI.

For an SPS PDSCH configuration without repetitions, if the reception occasions are across SBFD symbols and non-SBFD symbols where each reception occasion has either all SBFD or all non-SBFD symbols (i.e. Configuration 2) , PDSCH repetitions across SBFD symbols and non-SBFD symbols in different slots where each repetition has either all SBFD or all non-SBFD symbols (i.e. Configuration 2) , and for multi-PDSCH scheduled by a single DCI across SBFD symbols and non-SBFD symbols, where each PDSCH within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2) , only the assigned PRBs within DL usable PRBs in SBFD symbols are considered valid.

For Configuration 1 and frequency resource allocation Type 0, if the valid symbol type for SPS PDSCH, CG PUSCH, PDSCH/PUSCH repetition, multi-PDSCH/PUSCH scheduled by a single DCI and TBoMS (Transport Block over Multiple Slots) is SBFD symbols:
(1) When an assigned RBG overlaps with the subband boundary, only the PRBs within DL
usable PRBs are considered to be valid for PDSCH reception and only the PRBs within UL usable PRBs are considered to be valid for PUSCH transmission.
(2) The number of PRBs for TBS (Transport Block Size) determination is based on the
assigned PRBs within DL usable PRBs only and assigned PRBs within UL usable PRBs only for PDSCH and PUSCH respectively.
(3) SBFD aware UE does not expect to be assigned with a RBG for PDSCH which is fully
outside DL usable PRBs or a RBG for PUSCH which is fully outside UL usable PRBs.

For Configuration 1 and frequency resource allocation Type 1, if the valid symbol type for SPS PDSCH, PDSCH repetition and multi-PDSCH scheduled by a single DCI is SBFD symbols, then:
(1) Only the assigned PRBs within DL usable PRBs are considered to be valid for PDSCH.
(2) Assigned PRBs that fall outside DL usable PRBs are considered to be invalid and should
not be used for PDSCH resource mapping.
(3) Existing RB indexing and VRB (virtual RB) -to-PRB mapping are reused.
(4) The number of PRBs for TBS determination is based on the assigned PRBs within DL
usable PRBs only.

The disclosure proposes a mechanism for dynamically configuring FDRA in both downlink and/or uplink directions to avoid resource conflicts in SBFD systems. The disclosure introduces an FDRA configuration indicator to explicitly indicate the applicable slot types (partitioned, non-partitioned, or both) and establishes that resource allocations do not overlap with resources allocated for the opposite transmission direction. This approach aligns with the development of 3GPP RAN1 agreements and can be adapted to various channel types and configurations.

As described supra, in certain implementations, when the UE is instructed to apply the configured FDRA to both partitioned and non-partitioned slots or symbols, the network explicitly establishes that the FDRA does not overlap with resources allocated for the opposite transmission direction. Specifically, for SPS PDSCH, the FDRA configuration provided to the UE is within the DL subbands in SBFD slots, avoiding any overlap with UL subbands or guardband resources. Similarly, for CG PUSCH, the FDRA configuration provided to the UE is within the UL subbands in SBFD slots, avoiding any overlap with DL subbands or guardband resources. If, despite these precautions, an overlap occurs, the UE treats the overlapping portions as invalid and refrains from using them for transmission or reception.

In certain implementations, the UE capability to handle simultaneous transmission and reception on partitioned slots or symbols is explicitly indicated to the network. Based on this capability indication, the network determines whether to configure the UE with FDRA for both partitioned and non-partitioned slots or symbols, or to restrict the UE to only one type of slot or symbol. By default, UEs are configured to apply FDRA exclusively to either partitioned or non-partitioned slots or symbols (Configuration 1) . However, UEs capable of simultaneous transmission and reception may be explicitly configured by the network to apply FDRA to both types of slots or symbols (Configuration 2) .

In certain implementations, the FDRA configuration indicator (e.g., the symbolType parameter) provided to the UE may be dynamically updated by the network based on changes in the UE's operating conditions or capabilities. For example, if the UE initially supports only Configuration 1 (restricted to one type of slot or symbol) , but later acquires the capability to support simultaneous transmission and reception, the network may dynamically update the FDRA configuration indicator via higher layer signaling or layer 1 signaling (e.g., DCI) to enable Configuration 2. Conversely, if the UE's capability or operating conditions change such that simultaneous transmission and reception is no longer feasible, the network may dynamically update the FDRA configuration indicator to revert to Configuration 1.

In certain implementations, the FDRA configured for multi-slot transmissions (e.g., SPS PDSCH or CG PUSCH) is compatible with the slot or symbol type configuration indicated by the FDRA configuration indicator. For example, if the FDRA configuration indicator specifies that the UE should apply the FDRA exclusively to partitioned slots or symbols, the network configures the FDRA such that it is fully contained within the appropriate subbands (DL subbands for SPS PDSCH or UL subbands for CG PUSCH) of the partitioned slots or symbols. Similarly, if the FDRA configuration indicator specifies that the UE should apply the FDRA exclusively to non-partitioned slots or symbols, the network configures the FDRA accordingly to avoid resource allocation conflicts.

In certain implementations, when the FDRA configuration indicator is provided via scheduling DCI, the UE interprets the indicator on a per-scheduling basis. Specifically, each scheduling DCI may independently indicate the applicable slot or symbol type for the associated FDRA. Thus, the UE may receive different FDRA configuration indicators in successive scheduling DCIs, enabling flexible and dynamic adaptation of resource allocation strategies based on instantaneous network conditions, UE capabilities, or traffic requirements.

In certain implementations, when determining the valid symbol type for dynamically scheduled transmissions or receptions, the UE uses the symbol type of the first transmission or reception occasion associated with the activation DCI as a reference. Subsequent repetitions or multi-slot transmissions associated with the same activation DCI inherit the symbol type determined by the first transmission or reception occasion.

FIG. 8 illustrates a flow chart 800 of a process for multi-slot PDSCH/PUSCH FDRA enhancements in SBFD. This process involves interactions between a network (NW) and a UE (e.g., the UE 104) through a base station (e.g., the base station 102) .

At block 802, the UE receives a frequency domain resource allocation (FDRA) configuration for a multi-slot transmission across a plurality of slots. The plurality of slots may include at least one partitioned slot and at least one non-partitioned slot, the at least one partitioned slot including both downlink (DL) resources and uplink (UL) resources, and the at least one non-partitioned slot including only DL resources or only UL resources.

At block 804, the UE receives an FDRA configuration indicator indicating a usable slot set among the plurality of slots for applying the FDRA configuration.

At block 806, the UE applies the FDRA configuration to the usable slot set.

In certain configuration, the UE identifies, based on higher-layer signaling or layer-1 signaling, a time-frequency partitioning that indicates one or more subbands in the at least one partitioned slot. The UE selectively uses the FDRA configuration within one or more downlink subbands or uplink subbands in the identified time-frequency partitioning.

In certain configuration, the UE determines, in response to the FDRA configuration indicator indicating both the at least one partitioned slot and the at least one non-partitioned slot, that the FDRA configuration does not overlap with UL resources in DL transmissions or with DL resources in UL transmissions. The UE ignores any portion of the FDRA configuration that overlaps with resources allocated for an opposite transmission direction or with guardband resources in the at least one partitioned slot.

In certain configuration, to apply the FDRA configuration to the usable slot set, the UE performs a physical downlink shared channel (PDSCH) reception or a physical uplink shared channel (PUSCH) transmission only in subband regions that correspond to the usable slot set. The UE refrains from using subband regions that lie outside a valid partitioning boundary or that overlap with resources allocated for an opposite transmission direction.

In certain configuration, the UE receives, via radio resource control (RRC) signaling, an indication of whether the UE is restricted to transmitting or receiving in the at least one partitioned slot, the at least one non-partitioned slot, or both. The indication is associated with a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration.

In certain configuration, the indication may be provided as a symbolType parameter, the symbolType parameter having one of: a first value indicating that the FDRA configuration is valid only for the at least one partitioned slot; a second value indicating that the FDRA configuration is valid only for the at least one non-partitioned slot; or a third value indicating that the FDRA configuration is valid for both the at least one partitioned slot and the at least one non-partitioned slot.

In certain configuration, to apply the FDRA configuration: for a downlink transmission, the UE uses only those physical resource blocks (PRBs) within a DL subband of each partitioned slot of the usable slot set. For an uplink transmission, the UE uses only those PRBs within a UL subband of each partitioned slot of the usable slot set.

In certain configuration, the UE determines, based on a type of FDRA utilized, that at least one assigned resource block group (RBG) or contiguous set of physical resource blocks (PRBs) partially overlaps a boundary between a DL subband and a UL subband in a partitioned slot of the usable slot set. The UE uses a portion of the at least one assigned RBG or contiguous set of PRBs that lies fully within a valid DL area for downlink or a valid UL area for uplink, as indicated by the FDRA configuration indicator.

In certain configuration, in response to the FDRA configuration indicator specifying the at least one partitioned slot exclusively, the UE applies the FDRA configuration to slots containing both DL and UL resources. The UE ignores the FDRA configuration in any non-partitioned slot containing solely DL resources or solely UL resources.

In certain configuration, in response to the FDRA configuration indicator specifying the at least one non-partitioned slot exclusively, the UE applies the FDRA configuration to slots containing solely DL or solely UL resources. The UE ignores the FDRA configuration in any partitioned slot containing both DL and UL resources.

In certain configuration, the UE receives, in a scheduling downlink control information (DCI) message, an activation for a semi-persistent scheduling physical downlink shared channel (SPS PDSCH) or a Type-2 configured grant physical uplink shared channel (CG PUSCH) . The UE determines a symbol type for a first transmission occasion associated with the activation. The UE applies the FDRA configuration to subsequent repetitions according to the determined symbol type.

In certain configuration, the UE determines, for each of multiple transmission occasions, that an assigned FDRA falls within a DL usable resource region or a UL usable resource region in a partitioned slot of the usable slot set. The UE completes a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) mapping for physical resource blocks (PRBs) within a valid subband region. The UE discards PRBs that fall outside the valid subband region or overlap with guardband resources.

In certain configuration, the UE determines that the UE supports applying the FDRA configuration to both the at least one partitioned slot and the at least one non-partitioned slot The UE expects that the FDRA configuration avoids conflict between DL and UL resources. The UE uses the FDRA configuration for multi-slot transmissions across the usable slot set.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

Claims

A method of wireless communication performed by a user equipment (UE) , comprising:

receiving a frequency domain resource allocation (FDRA) configuration for a multi-slot transmission across a plurality of slots, wherein the plurality of slots comprises at least one partitioned slot and at least one non-partitioned slot, the at least one partitioned slot including both downlink (DL) resources and uplink (UL) resources, and the at least one non-partitioned slot including only DL resources or only UL resources;

receiving an FDRA configuration indicator indicating a usable slot set among the plurality of slots for applying the FDRA configuration; and

applying the FDRA configuration to the usable slot set.
The method of claim 1, further comprising:

identifying, based on higher-layer signaling or layer-1 signaling, a time-frequency partitioning that indicates one or more subbands in the at least one partitioned slot; and

selectively using the FDRA configuration within one or more downlink subbands or uplink subbands in the identified time-frequency partitioning.
The method of claim 1, further comprising:

determining, in response to the FDRA configuration indicator indicating both the at least one partitioned slot and the at least one non-partitioned slot, that the FDRA configuration does not overlap with UL resources in DL transmissions or with DL resources in UL transmissions; and

ignoring any portion of the FDRA configuration that overlaps with resources allocated for an opposite transmission direction or with guardband resources in the at least one partitioned slot.
The method of claim 1, wherein applying the FDRA configuration to the usable slot set comprises:

performing a physical downlink shared channel (PDSCH) reception or a physical uplink shared channel (PUSCH) transmission only in subband regions that correspond to the usable slot set; and

refraining from using subband regions that lie outside a valid partitioning boundary or that overlap with resources allocated for an opposite transmission direction.
The method of claim 1, further comprising:

receiving, via radio resource control (RRC) signaling, an indication of whether the UE is restricted to transmitting or receiving in the at least one partitioned slot, the at least one non-partitioned slot, or both, wherein the indication is associated with a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration.
The method of claim 5, wherein the indication is provided as a symbolType parameter, the symbolType parameter having one of:

a first value indicating that the FDRA configuration is valid only for the at least one partitioned slot;

a second value indicating that the FDRA configuration is valid only for the at least one non-partitioned slot; or

a third value indicating that the FDRA configuration is valid for both the at least one partitioned slot and the at least one non-partitioned slot.
The method of claim 1, wherein applying the FDRA configuration includes:

for a downlink transmission, using only those physical resource blocks (PRBs) within a DL subband of each partitioned slot of the usable slot set; and

for an uplink transmission, using only those PRBs within a UL subband of each partitioned slot of the usable slot set.
The method of claim 1, further comprising:

determining, based on a type of FDRA utilized, that at least one assigned resource block group (RBG) or contiguous set of physical resource blocks (PRBs) partially overlaps a boundary between a DL subband and a UL subband in a partitioned slot of the usable slot set; and

using a portion of the at least one assigned RBG or contiguous set of PRBs that lies fully within a valid DL area for downlink or a valid UL area for uplink, as indicated by the FDRA configuration indicator.
The method of claim 1, further comprising:

in response to the FDRA configuration indicator specifying the at least one partitioned slot exclusively, applying the FDRA configuration to slots containing both DL and UL resources; and

ignoring the FDRA configuration in any non-partitioned slot containing solely DL resources or solely UL resources.
The method of claim 1, further comprising:

in response to the FDRA configuration indicator specifying the at least one non-partitioned slot exclusively, applying the FDRA configuration to slots containing solely DL or solely UL resources; and

ignoring the FDRA configuration in any partitioned slot containing both DL and UL resources.
The method of claim 1, further comprising:

receiving, in a scheduling downlink control information (DCI) message, an activation for a semi-persistent scheduling physical downlink shared channel (SPS PDSCH) or a Type-2 configured grant physical uplink shared channel (CG PUSCH) ;

determining a symbol type for a first transmission occasion associated with the activation; and

applying the FDRA configuration to subsequent repetitions according to the determined symbol type.
The method of claim 1, further comprising:

determining, for each of multiple transmission occasions, that an assigned FDRA falls within a DL usable resource region or a UL usable resource region in a partitioned slot of the usable slot set;

completing a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) mapping for physical resource blocks (PRBs) within a valid subband region; and

discarding PRBs that fall outside the valid subband region or overlap with guardband resources.
The method of claim 1, further comprising:

determining that the UE supports applying the FDRA configuration to both the at least one partitioned slot and the at least one non-partitioned slot;

expecting that the FDRA configuration avoids conflict between DL and UL resources; and

using the FDRA configuration for multi-slot transmissions across the usable slot set.
An apparatus for wireless communication, the apparatus being a user equipment (UE) , comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive a frequency domain resource allocation (FDRA) configuration for a multi-slot transmission across a plurality of slots, wherein the plurality of slots comprises at least one partitioned slot and at least one non-partitioned slot, the at least one partitioned slot including both downlink (DL) resources and uplink (UL) resources, and the at least one non-partitioned slot including only DL resources or only UL resources;

receive an FDRA configuration indicator indicating a usable slot set among the plurality of slots for applying the FDRA configuration; and

apply the FDRA configuration to the usable slot set.
The apparatus of claim 14, wherein the at least one processor is further configured to:

identify, based on higher-layer signaling or layer-1 signaling, a time-frequency partitioning that indicates one or more subbands in the at least one partitioned slot; and

selectively use the FDRA configuration within one or more downlink subbands or uplink subbands in the identified time-frequency partitioning.
The apparatus of claim 14, wherein the at least one processor is further configured to:

determine, in response to the FDRA configuration indicator indicating both the at least one partitioned slot and the at least one non-partitioned slot, that the FDRA configuration does not overlap with UL resources in DL transmissions or with DL resources in UL transmissions; and

ignore any portion of the FDRA configuration that overlaps with resources allocated for an opposite transmission direction or with guardband resources in the at least one partitioned slot.
The apparatus of claim 14, wherein the at least one processor is further configured to:

receive, via radio resource control (RRC) signaling, an indication of whether the UE is restricted to transmitting or receiving in the at least one partitioned slot, the at least one non-partitioned slot, or both, wherein the indication is associated with a semi-persistent scheduling (SPS) configuration or a configured grant (CG) configuration.
A computer-readable medium storing computer executable code for wireless communication of a user equipment (UE) , comprising code to:

receive a frequency domain resource allocation (FDRA) configuration for a multi-slot transmission across a plurality of slots, wherein the plurality of slots comprises at least one partitioned slot and at least one non-partitioned slot, the at least one partitioned slot including both downlink (DL) resources and uplink (UL) resources, and the at least one non-partitioned slot including only DL resources or only UL resources;

receive an FDRA configuration indicator indicating a usable slot set among the plurality of slots for applying the FDRA configuration; and

apply the FDRA configuration to the usable slot set.
The computer-readable medium of claim 18, further comprising code to:

identify, based on higher-layer signaling or layer-1 signaling, a time-frequency partitioning that indicates one or more subbands in the at least one partitioned slot; and

selectively use the FDRA configuration within one or more downlink subbands or uplink subbands in the identified time-frequency partitioning.
The computer-readable medium of claim 18, further comprising code to:

determine, in response to the FDRA configuration indicator indicating both the at least one partitioned slot and the at least one non-partitioned slot, that the FDRA configuration does not overlap with UL resources in DL transmissions or with DL resources in UL transmissions; and

ignore any portion of the FDRA configuration that overlaps with resources allocated for an opposite transmission direction or with guardband resources in the at least one partitioned slot.