Sub-band full duplex (SBFD) allocation with disjoint sub-bands

Abstract

A method of wireless communication at a user equipment (UE) and a related apparatus are provided. In the method, the UE receives a resource allocation for a first set of resources in a first frequency band, the first frequency band being non-intersecting with a second frequency band in a sub-band full duplex (SBFD) slot, and communicates with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. According to the method, the resource allocation efficiency of scheduling resources on a plurality of disjoint sub-bands is improved.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 815,931, filed on July 28, 2022, entitled “SUB-BAND FULL DUPLEX (SBFD) ALLOCATION WITH DISJOINT SUB-BANDS,” and the entire contents of that application are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications with sub-band full-duplex resource allocation. Background Art

[0004] Wireless communication systems have been widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies that can support 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.

[0005] Such multiple access technologies have been adopted in a variety of telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a city-wide, national-wide, regional-wide, and even global scale. An exemplary telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] In order to have a basic understanding of one or more aspects of the present invention, a brief summary of these aspects is given below. This summary is not an exhaustive overview of all expected aspects. This summary is not intended to identify the key or important elements of all aspects, nor is it intended to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simple form as a prelude to the detailed description below.

[0007] In one aspect of the present disclosure, a method of wireless communication at a user equipment (UE), a related computer-readable medium, and an apparatus are provided. The apparatus receives a resource allocation for a first set of resources in a first frequency band that is disjoint with a second frequency band in a sub-band full-duplex (SBFD) time slot; and communicates with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

[0008] In one aspect of the present disclosure, a method of wireless communication at a network node, a related computer-readable medium, and a related apparatus are provided. The apparatus sends a resource allocation for a first set of resources in a first frequency band that is disjoint with a second frequency band in a sub-band full-duplex (SBFD) time slot; and communicates with a user equipment (UE) using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

[0009] To achieve the foregoing and related ends, one or more aspects include the features described in detail below and particularly pointed out in the claims. The following description and the accompanying drawings describe in detail certain exemplary features of one or more aspects. However, these features are merely illustrative of some of the various ways in which the basic principles of these various aspects can be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram showing an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram showing an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4A , 4B , 4C and Figure 4D Various modes of full-duplex communication are shown.

[0017] Figure 5 Examples of in-band full-duplex (IBFD) and sub-band frequency division duplex resources are shown.

[0018] Figure 6 An example device for simultaneously transmitting and receiving in full-duplex operation is shown.

[0019] Figure 7 is a diagram of a sub-band full-duplex (SBFD) slot format with frequency domain resource allocation (FDRA) in accordance with various aspects of the present disclosure.

[0020] Fig. 8A and Figure 8B is a diagram illustrating a first SBFD slot format with FDRA for downlink (DL) and uplink (UL), respectively, according to various aspects of the present disclosure.

[0021] Fig.9A and Fig. 9B is a diagram illustrating a second SBFD slot format with FDRA for DL ​​and UL, respectively, according to various aspects of the present disclosure.

[0022] Fig. 10A and Fig. 10B is a diagram illustrating a third SBFD slot format with FDRA for DL ​​and UL, respectively, according to various aspects of the present disclosure.

[0023] Fig.11 is a call flow diagram illustrating SBFD allocation with disjoint subbands, according to various aspects of the present disclosure.

[0024] Fig.12 is a flow chart illustrating a method of wireless communication according to various aspects of the present disclosure.

[0025] Fig.13 is a flow chart illustrating a method of wireless communication according to various aspects of the present disclosure.

[0026] Fig.14 is a flow chart illustrating a method of wireless communication according to various aspects of the present disclosure.

[0027] Fig.15is a flow chart illustrating a method of wireless communication according to various aspects of the present disclosure.

[0028] Fig.16 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0029] Fig.17 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0030] The specific embodiments described below in conjunction with the accompanying drawings describe various configurations, rather than representing that the concepts described herein can be implemented only in these configurations. In order to have a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be implemented without using these specific details. In some instances, in order to avoid obscuring these concepts, known structures and components are shown in block diagram form.

[0031] Some aspects of telecommunication systems are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and depicted in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). Such elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] For example, an element or any part of an element or any combination of elements can be implemented as a "processing system" including 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 chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, separate hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0033] Therefore, in one or more example aspects, embodiments and / or use cases, the functions described herein may be implemented with hardware, software, or any combination thereof. When implemented using software, these functions may be stored or encoded into one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that a computer can access. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these 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 and can be accessed by a computer.

[0034] Although various aspects, embodiments and / or use cases are described in this application by describing some examples, additional or different aspects, embodiments and / or use cases can be implemented in many different arrangements and scenarios. The various aspects, embodiments and / or use cases described herein can be implemented across multiple different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, embodiments and / or use cases can be implemented by integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, devices supporting artificial intelligence (AI), etc.) or combinations thereof. Although some examples may be specifically targeted at use cases or applications, they may not be specifically targeted at use cases or applications, but various applicability of the described examples may occur. The scope of various aspects, embodiments and / or use cases can be from chip-level or modular components to non-modular, non-chip-level implementations, and can also be aggregated, distributed or original equipment manufacturer (OEM) devices or systems containing one or more technologies herein. In some actual settings, the equipment containing the described aspects and features may also be necessary to include other components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., having different sizes, shapes, and configurations.

[0035] The deployment of a communication system such as a 5G NR system may be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network device (e.g., a base station (BS) or one or more units (or one or more components) performing base station functions) may be implemented in an aggregated or decomposed architecture. For example, a BS (e.g., a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or a monolithic BS) or a decomposed base station.

[0036] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (e.g., one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0037] Base station operations or network design may take into account the aggregated nature of base station functionality. For example, a decomposed network may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (e.g., a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality between two or more units at different physical locations, as well as distributing functionality for at least one unit virtually, which may enable flexibility in network design. Individual units of a decomposed base station or decomposed RAN architecture may be configured to communicate wired or wirelessly with at least one other unit.

[0038] Figure 1100 is a diagram illustrating an example of a wireless communication system and access network. The wireless communication system shown includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more decomposed base station units (e.g., a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both). The CU 110 may communicate with one or more DUs 130 via corresponding mid-haul links such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via respective fronthaul links. The RU 140 may communicate with each UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0039] Each unit (i.e., CU 110, DU 130, RU 140, near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces, and the one or more interfaces are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals from or send signals to one or more other units via a wired transmission medium. In addition, these units may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) that is configured to receive signals from or send signals to, or both, one or more other units via a wireless transmission medium.

[0040] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to process user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 110 may be implemented to communicate with DU130 as needed for network control and signaling.

[0041] DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 140. In some aspects, DU 130 may host one or more of the following based at least in part on functional splitting: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.), such as those defined by 3GPP. In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130, or with control functions hosted by CU 110.

[0042] Lower layer functions may be implemented by one or more RUs 140. In some deployments, based at least in part on a functional split such as a partitioning of lower layer functions, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (e.g., a vRAN architecture).

[0043] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and RAN coverage requirements may be managed through an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) 190) to perform network element lifecycle management (e.g., instantiating virtualized network elements) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (e.g., an open eNB (O-eNB) 111) via an O1 interface. In addition, in some implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via an O1 interface. The SMO framework 105 may also include a non-RT RIC 115 that is configured to support the functionality of the SMO framework 105 .

[0044] The non-RT RIC 115 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows (including model training and updating), or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that implement control and optimization of RAN elements and resources in near real time through data collection and actions on interfaces connecting one or more CUs 110, one or more DUs 130, or both, and O-eNBs to the near-RT RIC 125 (e.g., via an E2 interface).

[0045] In some implementations, in order to generate the AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be used by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (e.g., via reconfiguration of O1) or via the creation of a RAN management policy (e.g., an A1 policy).

[0046] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is represented by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station 102). The base station 102 provides an access point for the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also known as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also known as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation, with a total of Yx MHz (x component carriers) in each direction for transmission. These carriers may be adjacent to each other or may not be adjacent to each other. The 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). These component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0047] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be performed through various wireless D2D communication systems such as Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0048] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154 (e.g., in a 5 GHz unlicensed spectrum, etc.). When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0049] The electromagnetic spectrum is usually subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. FR2 sometimes presents a similar naming issue, although it is different from the extremely high frequency (EHF) band (30GHz-300 GHz), which is defined as the "millimeter wave" band by the International Telecommunication Union (ITU), but it is often (interchangeably) referred to as the "millimeter wave" band in various documents and articles.

[0050] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating frequency bands for these mid-band frequencies as the frequency range FR3 (7.125 GHz–24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations above 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR2-2 (52.6 GHz–71 GHz), FR4 (71 GHz–114.25 GHz), and FR5 (114.25 MHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0051] In view of the above, unless otherwise explicitly stated, the term "sub-6 GHz" and the like (if used herein) may broadly refer to frequencies less than 6 GHz, which may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, the term "millimeter wave" and the like (if used herein) may broadly refer to frequencies including mid-band frequencies, which may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0052] The base station 102 and the UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base stations 102 / UE 104. The transmit and receive directions of the base station 102 may be the same or different. The transmit and receive directions of the UE 104 may be the same or different.

[0053] The base station 102 may include or be referred to as a gNB, a Node B, an 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 transmission reception point (TRP), a network node, a network entity, a network device, or some other appropriate term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations including decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0054] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification processing, access authorization, and subscription management. One or more location servers 168 are shown as including a gateway mobile positioning center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE positioning services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN can determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may include signal measurements, position estimation, and optional speed calculation based on measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signal can be based on one or more of the following: a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., a pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (Multi-RTT), DL departure angle (DL-AoD), DL arrival time difference (DL-TDOA), UL arrival time difference (UL-TDOA), and UL arrival angle (UL-AoA) positioning) and / or other systems / signals / sensors.

[0055] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals, mobile terminals, wireless terminals, remote terminals, handheld devices, user agents, mobile clients, clients, or some other appropriate terminology. In some scenarios, the term UE may also be applied to one or more companion devices (e.g., in a device constellation arrangement). One or more of these devices may access the network collectively and / or individually.

[0056] Reference again Figure 1 In some aspects, the UE 104 may be configured to include a SBFD receiving component 198 configured to receive a resource allocation for a first set of resources in a first frequency band that is disjoint with the second frequency band in a SBFD time slot, and to communicate with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. In some aspects, the base station 102 may be configured to include a SBFD transmitting component 199 configured to transmit a resource allocation for a first set of resources in a first frequency band that is disjoint with the second frequency band in a SBFD time slot, and to communicate with a user equipment (UE) using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. Although the following description focuses on 5G NR, the concepts described herein may be applied to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0057] Figure 2A FIG200 is a diagram showing an example of a first subframe in a 5G NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels in a 5G NR subframe. Figure 2C FIG250 is a diagram showing an example of a second subframe in a 5G NR frame structure. Figure 2DFIG280 is a diagram showing an example of UL channels in a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD) or time division duplex (TDD), where in the case of FDD, for a specific set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to DL or UL, and in the case of TDD, for a specific set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is used flexibly between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI), or semi-statically / statically configured through radio resource control (RRC) signaling). It should be noted that the following description also applies to the 5G NR frame structure of TDD.

[0058] Figures 2A-2D The frame structure is shown, and various aspects of the present disclosure can be applied to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 subframes (1ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a micro time slot, which may include 7, 4 or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each time slot may include 14 or 12 symbols. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set specifies the subcarrier spacing (SCS) and effectively defines the symbol length / duration (which is equal to 1 / SCS).

[0059]

[0060] Table 1

[0061] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Thus, the subcarrier spacing is 15kHz for parameter set μ=0 and 240kHz for parameter set μ=4. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) for frequency division multiplexing (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0062] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0063] like Figure 2A As shown in , some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement (BRRS), and a phase tracking RS (PT-RS).

[0064] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The UE 104 uses the PSS to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be located within symbol 4 of a specific subframe of a frame. The UE uses the SSS to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically combined with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (e.g., system information block (SIB)), and paging messages.

[0065] like Figure 2C As shown in , some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are also possible) for channel estimation at the base station. The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short or long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of these comb structures. The base station can use the SRS for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0066] Figure 2D Examples of various UL channels in a subframe of a frame are shown. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK / negative ACK (NACK)). The PUSCH carries data and may also be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0067] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets are provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission 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; MAC layer functions 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.

[0068] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping for the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). Subsequently, the coded and modulated symbols may be split into parallel streams. Subsequently, each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the coding and modulation schemes and to implement spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier using each spatial stream for transmission.

[0069] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. Subsequently, the RX processor 356 uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDMA 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 point sent by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. These data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0070] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0071] Similar to the functions described in conjunction with the DL transmission of the base station 310, the controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission 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; MAC layer functions 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 processing, and logical channel prioritization.

[0072] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via respective transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0073] The base station 310 processes the UL transmission in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives the signal through its respective antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0074] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0075] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Related aspects of the SBFD receiving component 198 .

[0076] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Aspects related to the SBFD sending component 199 are described below.

[0077] Wireless communication systems can be configured to share available system resources and provide various telecommunication services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users. Full-duplex operation of wireless devices exchanging uplink and downlink communications that overlap in time can enable more efficient use of the wireless spectrum. Full-duplex operation can include sending and receiving simultaneously within the same frequency range. In some examples, the frequency range can be a mmW frequency range, such as frequency range 2 (FR2). In some examples, the frequency range can be a frequency range below 6 GHz, such as frequency range 1 (FR1). Full-duplex communication can reduce delays. For example, full-duplex operation can enable a UE to receive a downlink signal in an uplink-only time slot, which can reduce delays in downlink communications. Full-duplex communication can improve spectral efficiency, for example, the spectral efficiency of each cell or each UE. Full-duplex communication can enable more efficient use of wireless resources.

[0078] Figures 4A-4D Various modes of full-duplex communication are shown. Full-duplex communication supports sending and receiving information in a time-overlapping manner on the same frequency band. In this way, spectral efficiency can be improved relative to the spectral efficiency of half-duplex communication, which supports sending or receiving information in one direction at a time without overlapping uplink and downlink communications. Due to the simultaneous Tx / Rx nature of full-duplex communication, a UE or base station may experience self-interference caused by signal leakage from its local transmitter to its local receiver. In addition, a UE or base station may also experience interference from other devices, such as transmission from a second UE or a second base station. This interference (e.g., self-interference or interference caused by other devices) may affect the quality of communication and even cause the loss of information.

[0079] Figure 4A A first example of full-duplex communication 400 is shown, where a first base station 402a is in full-duplex communication with a first UE 404a and a second UE 406a. The first UE 404a and the second UE 406a may be configured for half-duplex communication or full-duplex communication. Figure 4AA first UE 404a performing downlink reception and a second UE 406a performing uplink transmission are shown. The second UE 406a may send a first uplink signal to the first base station 402a and other base stations (e.g., a second base station 408a near the second UE 406a). The first base station 402a sends a downlink signal to the first UE 404a while receiving an uplink signal from the second UE 406a (e.g., overlapping at least partially in time). The base station 402a may experience self-interference at the receiving antenna where it is receiving the uplink signal from the UE 406a, which is caused by receiving at least a portion of the downlink signal sent to the UE 404a. The base station 402a may experience additional interference due to the signal from the second base station 408a. Interference may also occur at the first UE 404a based on the signal from the second base station 408a and the uplink signal from the second UE 406a.

[0080] Figure 4B A second example of full-duplex communication 410 is shown, in which a first base station 402b performs full-duplex communication with a first UE 404b. In this example, UE 404b also operates in full-duplex mode. The first base station 402b and UE 404b receive and transmit communications that overlap in time and are in the same frequency band. Each of the base station and the UE may experience self-interference, which is due to leakage of a signal transmitted from a device to a receiver at the same device (e.g., received by the same device). Based on one or more signals transmitted from a second UE 406b and / or a second base station 408b close to the first UE 404b, the first UE 404a may experience additional interference.

[0081] Figure 4C A third example of full-duplex communication 420 is shown, where a first UE 404c sends and receives full-duplex communications with a first base station 402c and a second base station 408c. The first base station 402c and the second base station 408c can be used as multiple transmission reception points (multiple TRPs) for UL and DL communications with the UE 404c. The second base station 408c can also exchange communications with a second UE 406c. Figure 4C In the embodiment of the present invention, the first UE 404c may send an uplink signal to the first base station 402c, which may overlap in time with a downlink signal received from the second base station 408c. The first UE 404c may experience self-interference due to receiving at least a portion of the first signal while receiving the second signal, for example, when the UE attempts to receive a signal from another base station 408c, the uplink signal from the UE to the base station 402c may leak to (e.g., be received by) the receiver of the UE. The first UE 404c may experience additional interference from the second UE 406c.

[0082] Figure 4D A fourth example of full-duplex communication 430 is shown, wherein a first base station 402d adopts full-duplex communication with a first UE 404d, and sends downlink communication to a second UE 406d. In this example, the first UE 404d operates in full-duplex mode, and the second UE 406d operates in half-duplex mode. The first base station 402d and the first UE 404d receive and transmit communications that overlap in time and are in the same frequency band. Each of the base station 402d and the first UE 404d may experience self-interference, which is due to the leakage of the signal sent from the corresponding device to the receiver at the same device (e.g., received by the same device). Due to the signal sent by the base station 408d, the base station 402d may further experience cross-link interference. When receiving downlink communication from the base station 402d, the second UE 406d may experience cross-link interference from the uplink transmission of the first UE 404b.

[0083] Full-duplex communications may be in the same frequency band. Uplink communications and downlink communications may be in different frequency sub-bands, in the same frequency sub-band, or in partially overlapping frequency sub-bands. Figure 5 A first example 500 and a second example 510 of an in-band full-duplex (IBFD) resource and a third example 520 of a sub-band full-duplex resource are shown. In IBFD, signals can be sent and received in overlapping times and overlapping frequencies. As shown in the first example 500, the time and frequency allocation of the transmission resources 502 can completely overlap with the time and frequency allocation of the reception resources 504. In the second example 510, the time and frequency allocation of the transmission resources 512 can partially overlap with the time and frequency allocation of the reception resources 514.

[0084] IBFD is in contrast to sub-band FDD, in which transmission resources and reception resources can overlap in time using different frequencies, as shown in the third example 520. In the third example 520, the UL, transmission resources 522 and reception resources 524 are separated by a guard band 526. The guard band can be a frequency resource provided between the transmission resource 522 and the reception resource 524, or a gap in the frequency resource. Separating the transmission frequency resource and the reception frequency resource with a guard band can help reduce self-interference. It can be considered that the transmission resources and reception resources that are directly adjacent to each other have a guard band width of 0. Since the output signal from the wireless device may extend beyond the transmission resource, the guard band can reduce the interference experienced by the wireless device. Sub-band FDD can also be called "flexible duplexing".

[0085] If full-duplex operation is for a UE or a device implementing UE functionality, transmission resources 502, 512, and 522 may correspond to uplink resources, and reception resources 504, 514, and 524 may correspond to downlink resources. Alternatively, if full-duplex operation is for a base station or a device implementing base station functionality, transmission resources 502, 512, and 522 may correspond to downlink resources, and reception resources 504, 514, and 524 may correspond to uplink resources.

[0086] Figure 6 An example device 602 is shown that includes a separate panel (e.g., antenna panel) for simultaneously transmitting and receiving in full-duplex operation. For example, device 602 is shown as including panel #1 and panel #2. In some examples, panel #1 can be used for downlink transmission. Downlink transmission can be at both edges of the frequency band, such as shown in 600 and 610. Panel #2 can be used for uplink reception, such as using frequency resources within the frequency band, such as in the middle of the frequency band. Such as in combination Figure 5 The described sub-band full-duplex operation can be associated with an isolation of greater than 40 dB. Figure 5 As shown in , the downlink and uplink resources may be in different parts of the frequency band with a guard band between the uplink and downlink parts of the frequency band. Figure 6 An example set of time and frequency resources 600 including both half-duplex periods and full-duplex periods is shown. For example, time period 620 includes half-duplex resources for downlink data, e.g., both panel #1 and panel #2 can receive downlink data during time period 620. Time period 630 includes sub-band full-duplex resources for uplink transmission (e.g., PUSCH) and downlink reception (e.g., downlink data), e.g., during time period 630, panel #1 can receive downlink data and panel #2 can send PUSCH. Time period 640 includes half-duplex resources for uplink data, e.g., both panel #1 and panel #2 can send PUSCH during time period 640. Figure 6 Also included is a graph 610 showing signal power over frequency, illustrating that uplink and downlink signals leak outside of the frequency range provided in the sub-band full-duplex resources of time period 630 .

[0087] When a time slot has frequency bands for uplink and downlink transmissions, the time slot format may be referred to as a "D+U" time slot. Downlink and uplink transmissions may occur in overlapping frequency resources (e.g., in-band full-duplex resources), or may occur in adjacent or slightly separated frequency resources (e.g., sub-band full-duplex resources), such as Figure 5In a particular D+U symbol, a half-duplex device can transmit in the uplink band and receive in the downlink band. In a particular D+U symbol, a full-duplex device can transmit in the uplink band and receive in the downlink band (e.g., in the same symbol or in the same time slot). A D+U time slot can include downlink-only symbols, uplink-only symbols, and full-duplex symbols. For example, in Figure 6 In the embodiment, time period 620 may extend one or more symbols (e.g., downlink symbols only), time period 640 may extend one or more symbols (e.g., uplink symbols only), and time period 630 may extend one or more symbols (e.g., full-duplex symbols or D+U symbols).

[0088] The UE may receive resource allocations from a base station for the UE to use for uplink transmissions and / or downlink receptions. For example, the base station may allocate resources to the UE for uplink transmissions (e.g., PUSCH transmissions). As an example, the base station may send downlink control information (DCI) that schedules uplink resources for the UE to use for PUSCH transmissions. In some aspects, the DCI may be referred to as scheduling DCI. In other aspects, the base station may send a DCI to the UE to indicate the resources that the UE is to use for receiving downlink transmissions (e.g., such as PDSCH). As an example, the scheduling information (e.g., in the DCI) may indicate a frequency domain resource allocation (FDRA).

[0089] Frequency domain resource allocation may indicate disjoint RBs (which may be referred to as allocation type 0) or contiguous RBs (which may be referred to as allocation type 1). Disjoint RB allocations (e.g., allocation type 0) may be indicated via a bitmap-based resource allocation scheme, where the bitmap in the DCI indicates the allocated resource block groups (RBGs). As an example, the bitmap size may be 18 bits or 9 bits (or may have different sizes in other examples), and the allocation may be multiple RBGs, and disjoint allocations allow the allocated RBGs to be contiguous or discontinuous. The RBG size may depend on the BWP size and / or configuration type. As an example, the RBG size may be configured by the parameter rbg-size via the configuration command ENUMERATED{config1,config2} in the RRC message. Table 1 shows an example set of RBG sizes under various rbg-size configurations and BWP sizes.

[0090] Table 1. Example RBG sizes for various configuration types and BWP sizes

[0091]

[0092] In a contiguous RB allocation (e.g., allocation type 1), the DCI may schedule a contiguous set of RBs for the UE. For example, the size of the allocated resources may be based on a parameter RB indicating the starting RB of the allocation. start , and indicates the number of consecutive RBs allocated The two parameters can be combined into a resource indication value (RIV) parameter. For example, the starting RB parameter and the number of consecutive RBs parameter can be combined in the following formula:

[0093] if but

[0094]

[0095] otherwise

[0096]

[0097] in, is the length of the consecutively allocated RBs, It is the BWP size.

[0098] An SBFD timeslot may have two disjoint DL or UL allocations (ie, disjoint DL or UL subbands), e.g. Figure 5 520 and / or Figure 6 As shown in the example of 630 in FIG. Two disjoint DL subbands may be separated by a UL frequency band in addition to any guard bands, and similarly, two disjoint subbands may be separated by a DL frequency band in addition to any guard bands.

[0099] Since the subbands are disjoint, a scheduling scheme with a start and length indication indicates a contiguous resource allocation (e.g., allocation type 1), while due to the presence of the separation band, the two subbands are disjoint and non-contiguous. A bitmap scheduling scheme (e.g., allocation type 0) may be inefficient because the bitmap will include bits for indicating RBs in the separation band that cannot be allocated. The bitmap may be complex, and the added bits indicating the separation band do not represent the useful bandwidth. Therefore, the various aspects presented herein provide efficient resource allocation that can use bits that can be interpreted as being used for non-disjoint resources (e.g., such as Figure 6 620 and 640) and for disjoint resources (e.g., Figure 6 The signaling (shown at 630 in FIG. 6 ) schedules resources on multiple disjoint subbands. Therefore, control information (e.g., scheduling DCI) can be used to allocate resources, for example, on one frequency band or multiple frequency bands, and can be interpreted differently by the UE receiving the control information.

[0100] Figure 7is a diagram of a SBFD slot format 700 with frequency domain resource allocation (FDRA) in accordance with various aspects of the present disclosure. Figure 7 A time period 720 with half-duplex downlink resources, a time period 740 with half-duplex uplink resources, and a time period 730 with SBFD resources are shown, wherein the SBFD resources include disjoint frequency resources for the downlink. Figure 7 The time slot format shown in is similar to Figure 6 The time slot format shown in , except that, at 730, two frequency domain resource allocations (FDRA1 and FDRA2) are respectively allocated in two non-intersecting subbands for downlink reception. As proposed herein, FDRA1 and FDRA2 may be indicated to the UE in scheduling information indicating the FDRA for one of the two non-intersecting subbands. In one configuration, in a full-duplex time slot with two non-intersecting subbands, the UE may interpret a frequency domain resource allocation indicated for one subband (i.e., FDRA1) as also allocating a corresponding frequency domain resource allocation (i.e., FDRA2) on the other subband. Figure 7 In the example shown in , the frequency domain allocation is shown as resources for downlink transmission, but the concepts proposed herein can be similarly applied to resources allocated for uplink transmission in non-intersecting subbands. In this example, the base station can send scheduling information (e.g., a scheduling DCI indicating an FDRA in one of multiple non-intersecting subbands), and the UE can interpret the scheduling DCI as allocating an FDRA in each of the non-intersecting subbands. Although examples for resource allocation in DCI are given, the concepts given herein can be similarly applied to other resource allocation methods. For example, the base station can allocate resources via a configured grant or other semi-persistent scheduling indicating an FDRA in one of multiple non-intersecting subbands, and the UE can interpret the resource allocation as allocating an FDRA in each of the non-intersecting subbands. For example, the UE can receive a resource configuration indicated in RRC signaling and / or via MAC-CE, which indicates resources in one subband, and the UE can interpret the resource allocation as an allocation in multiple non-intersecting frequency subbands.

[0101] Frequency domain resource allocation on two disjoint subbands may be interpreted or applied in various ways. Fig. 8A 8 is a diagram showing a first SBFD slot format 800, in which the FDRA for downlink resources is interpreted as being allocated in a plurality of disjoint subbands. Fig. 8AAs shown in , the downlink resources include two subbands (a first subband and a second subband) separated by a protection resource (i.e., a guard band) and an uplink resource. The UE may receive scheduling information indicating a first FDRA 802 in the first subband and may interpret the scheduling information as allocating a corresponding second FDRA 804 in the second subband. Fig. 8A As shown in , a UE may receive a PDSCH (e.g., a transport block (TB) including data) in a first FDRA 802 in a first subband and may receive a repetition of the PDSCH (e.g., a repetition of a TB) in a second FDRA 804 in a second subband. The same concept may apply to disjoint uplink resources. Figure 8B 8 is a diagram showing a first SBFD time slot format 850 with disjoint uplink resources. Figure 8B As shown in , the uplink resources include two subbands (a first subband and a second subband) separated by a protection resource (i.e., a guard band) and a downlink resource. The UE may receive scheduling information (e.g., a first FDRA 852) indicating the uplink resources and may interpret the scheduling information as allocating a corresponding second FDRA 854 in the second subband. Fig. 8A As described in Figure 8B In the embodiment, the UE may send a PUSCH (eg, including a TB of data) in a first FDRA 852 in a first subband and may send a repetition of the PUSCH (eg, including a repetition of the TB) in a second FDRA 854 in a second subband.

[0102] Fig.9A Shows something like Fig. 8A The time slot format of the time slot format is 900. Fig.9A As shown in , the downlink resources include two subbands (a first subband and a second subband) separated by a protection resource (i.e., a guard band) and an uplink resource. The UE may receive scheduling information indicating resources in one subband (e.g., a first FDRA 902) and may interpret the scheduling information as allocating a corresponding set of resources (e.g., a second FDRA 904) in another subband, for example, where the first FDRA 902 and the second FDRA 904 are allocated in the first subband and the second subband, respectively. Fig. 8A Compared to the example in which the UE receives a repetition of the PDSCH in the second FDRA, Fig.9A In the embodiment of the present invention, the same TB may be mapped on downlink resources in the first subband and the second subband. That is, the first FDRA 902 on the first subband may include the first part of the TB, and the second FDRA 904 on the second subband may include the second part of the TB. The same scheme applies to uplink resources. Fig. 9B is shown similar to Figure 8B FIG. 950 is a diagram of a time slot format of a time slot format. Fig. 9B As shown in , the uplink resources include two subbands (a first subband and a second subband) separated by a guard resource (i.e., a guard band) and a downlink resource. A first FDRA 952 and a second FDRA 954 are allocated in the first subband and the second subband, respectively, for example, by an indication of the first FDRA 952 in the scheduling information. The same TB is mapped on the uplink resources in the first subband and the second subband (e.g., for PUSCH transmission). As shown in Fig. 9B As shown in FIG. 9 , a first FDRA 952 on a first sub-band may include a first portion of a TB, and a second FDRA 954 on a second sub-band may include a second portion of the TB.

[0103] Fig. 10A An example is shown where different PDSCH transmissions may be sent in resources allocated in disjoint subbands. Fig. 10A The time slot format 1000 shown in FIG. 1 is similar to Fig. 8A and Fig.9A The time slot format in . Fig. 10A As shown in , the downlink resources include two subbands (a first subband and a second subband) separated by a protection resource (i.e., a guard band) and an uplink resource. The UE may receive scheduling information indicating resources in one subband (e.g., a first FDRA 1002), and the UE may interpret the scheduling information as allocating a corresponding set of resources in another subband (e.g., a second FDRA 1004), for example, where the first FDRA 1002 and the second FDRA 1004 are allocated in the first subband and the second subband, respectively. Fig. 10A As shown, two PDSCHs may be sent in two FDRAs, respectively. For example, the UE may receive a first PDSCH (PDSCH1) in a first FDRA 1002 and may receive a second PDSCH (PDSCH2) in a second FDRA 1004. The same concept applies to uplink resources. Fig. 10B Shows something like Figure 8B and Fig. 9B The time slot format of the time slot format is 1050. Fig. 10BAs shown in , the uplink resources include two subbands (first subband and second subband) separated by protection resources (i.e., protection band) and downlink resources. The UE may receive control signaling with scheduling information that allocates an FDRA in one of the subbands, and the UE may interpret the scheduling information as allocating a first FDRA 1052 and a second FDRA 1054 in the first subband and the second subband, respectively. Two PUSCHs may be sent in the two FDRAs, respectively. That is, the UE may send a first PUSCH (PUSCH1) in the first FDRA 1052, and may send a second PUSCH (PUSCH2) in the second FDRA 1054.

[0104] The duplication of resources in the frequency domain (e.g., interpreting a FDRA for one subband as allocating a corresponding FDRA in a disjoint subband) may be achieved in various ways. In some aspects, the UE may be configured by RRC to interpret a FDRA in a scheduling DCI as two FDRAs spanning two subbands. For example, a base station may send RRC signaling to the UE indicating that the UE interprets a FDRA scheduled for one subband as allocating a corresponding FDRA in a disjoint subband. The UE may then interpret the scheduling information (e.g., including the FDRA) according to the RRC configuration. If the UE receives RRC signaling indicating that the UE interprets the FDRA as a single allocation, or does not receive RRC signaling for interpreting a FDRA for resource duplication, the UE may instead interpret the scheduling information with a FDRA in one subband as allocating resources in the indicated subband without a corresponding FDRA in a disjoint subband. In some aspects, an indication (e.g., one or more bits) in the scheduling DCI may be used to indicate to the UE whether the FDRA is allocated on one subband or on two disjoint subbands. For example, when sending scheduling information in a DCI, the base station may indicate to the UE the type of resource allocation interpretation that applies disjoint subbands. In some aspects, more than one bit may be used to indicate the type of resource allocation interpretation that the UE is to apply, and the indication may provide additional information. As an example, the DCI may further indicate the subband that will carry the resources (e.g., the subband to which the FDRA included in the DCI corresponds) and the transmission properties on the resources allocated in the disjoint subbands (e.g., whether one TB, more than one TB, or a repetition scheme is used). For example, the DCI may indicate whether the UE is to Fig. 8A In the same manner as in the above, PDSCH is received in a repeated manner, such as Figure 8B PUSCH is sent in a repeated manner as in Fig.9A Receive the PDSCH mapped on resources allocated in both subbands as in Fig. 9B The PUSCH mapped on resources allocated in both subbands is sent as in Fig. 10ADifferent PDSCHs are received in different subband resources as in Fig. 10B In some aspects, the UE may interpret the FDRA indicated in the scheduling information to allocate resources on one subband or multiple subbands based on the slot type. In one example, the UE may interpret that if the slot type is an SBFD slot (e.g., Figure 7 730 in the scheduling information), the UE may interpret one FDRA received in the scheduling information as allocating the corresponding FDRA in another disjoint subband. For example, the FDRA may be interpreted as being repeated in the SBFD time slot. In another example, the UE may interpret the FDRA according to certain time slots configured via an RRC message. For example, the UE may receive an RRC configuration that instructs the UE to interpret the FDRA with duplication in the SBFD time slot and to interpret the FDRA without duplication in the half-duplex time slot.

[0105] The duplication of FDRA in two subbands can be implemented in various ways. In some aspects, when duplication of FDRA in two subbands is implemented, the first RB in the second subband can be considered to be the first RB in the first subband. For example, if the first allocated RB in the first subband is RB5, then the allocation of the second subband can similarly start from the fifth RB at the beginning of the second subband. For example, Figure 7 The following example is shown, where FDRA1 can start on the i-th RB of the first subband and FDRA2 can start on the i-th RB of the second subband, i being an integer. In some aspects, the duplication of the FDRA for the first subband in the second subband can start from the first RB of the second subband.

[0106] Since the RBG size in each subband may be different, duplicating the FDRA in the second subband may result in the FDRA in the second subband having a different size (i.e., a larger or smaller bandwidth) than the FDRA in the first subband. To address this issue, in some aspects, if the RBG size in the two subbands is different, the UE may use the same bitmap in each subband regardless of the FDRA size. In other aspects, the UE may interpret the bitmap with an increased bitmap or a decreased bitmap size in the second subband to match the allocated bandwidth (BW) of the FDRA in the two subbands.

[0107] Fig.11 1 is a call flow diagram 1100 illustrating SBFD resource allocation with disjoint subbands according to various aspects of the present disclosure. Fig.11As shown in , in a SBFD resource allocation scheme with disjoint subbands, BS 1104 may send DCI 1108 to the UE, or another resource allocation such as a configured grant or semi-persistent scheduling, which includes scheduling information indicating an FDRA in a first subband that is disjoint with a second subband. For example, DCI 1108 may indicate Figure 7 At 1110, UE 1102 may interpret the FDRA received in the DCI. The interpretation may be based on, for example, Figure 7 , 8A , 8B, 9A, 9B, 10A and Fig. 10B In some aspects, the base station may send an RRC configuration 1106 to the UE that instructs the UE to interpret resources allocated in one subband as providing corresponding resource allocations in disjoint subbands. The RRC signaling may indicate one or more slot types for which the UE will use this interpretation. The RRC signaling may indicate the manner in which the duplicated resources will be used (e.g., Fig. 8A or Figure 8B Repetitions in Fig.9A or Fig. 9B Map TB on the combined resource, or as Fig. 10A or Fig. 10B In some aspects, such an indication may be carried in the DCI 1108 rather than in the RRC configuration. In some aspects, the RRC configuration 1106 may indicate that the UE does not interpret the allocated resources with duplication, and at 1110, the UE may interpret these resources as being allocated within a single subband. The DCI may include a scheme for scheduling FDRA in disjoint subbands for DL / UL transmissions between the UE 1102 and the BS 1104, e.g. Fig. 8A , 8B , 9A, 9B, 10A and Fig. 10B . DL / UL transmissions may then be exchanged between UE 1102 and BS 1104 based on the resources allocated in the DCI and the interpretation of the resource allocation at 1110. For example, the UE may send one or more PUSCH transmissions in FDRA in disjoint subbands, and the base station may receive these PUSCHs, e.g., as combined with Figure 8B , 9B or Fig. 10B As another example, the base station may send one or more PDSCH transmissions in FDRA in disjoint subbands, and the UE may receive these PDSCHs, for example, as combined with Fig. 8A , 9A or Fig. 10A Any of the ones described.

[0108] Fig.12 1200 is a flowchart illustrating wireless communication methods according to various aspects of the present disclosure. These methods may be performed by a UE. The UE may be UE 104, 350, 1102, or Fig.16 The method provides a SBFD resource allocation with disjoint subbands, which improves the resource allocation efficiency of scheduling resources on multiple disjoint subbands.

[0109] like Fig.12 As shown in , at 1202, the UE may receive a resource allocation for a first set of resources in a first frequency band from a network node, the first frequency band being disjoint from a second frequency band in a SBFD time slot. The network node may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; Fig.16 In one example, the receiving operation may be performed by the SBFD receiving component 198. Fig.11 As shown in , in one configuration, UE 1102 may receive DCI 1108, or other types of resource allocations such as configured grants or semi-persistent resource allocations, from BS 1104, and DCI 1108 may include resource allocations for a first set of resources in a first frequency band, wherein the first frequency band does not intersect with a second frequency band in a SBFD time slot.

[0110] At 1204, the UE may communicate with the network node using a first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. The communication may be performed, for example, by the SBFD receiving component 198. Fig.11 As shown in , in one configuration, a UE 1102 may communicate with a BS 1104 via a DL / UL transmission 1112. The communication may use a first set of resources in a first frequency band and a corresponding second set of resources in a second frequency band.

[0111] In some aspects, the first frequency band may be a first uplink frequency band and the second frequency band may be a second uplink frequency band. The first resource set may be uplink resources in the first uplink frequency band separated from the second uplink frequency band in an SBFD time slot. The first uplink frequency band and the second uplink frequency band may be separated by at least one of a downlink frequency band and a guard frequency band. The communication with the network node may include sending an uplink communication to the network node in a first resource set in the first uplink frequency band and a corresponding second resource set in the second uplink frequency band.

[0112] In one example, if Figure 8B As shown in , the SBFD time slot may include uplink resources. The uplink resources in the SBFD time slot may include a first subband and a second subband separated by a downlink frequency band and a guard frequency band. The first resource set may be a first FDRA 852 in the first subband, and the second resource set may be a second FDRA 854 in the second subband. Therefore, when communicating with the network node, the UE may use the first FDRA 852 and the second FDRA 854 as communication resources.

[0113] Fig.13 1300 is a flowchart illustrating methods of wireless communication according to various aspects of the present disclosure. These methods may be performed by a UE. The UE may be UE 104, 350, 1102, or Fig.16 The method provides a SBFD resource allocation with disjoint subbands, which improves the resource allocation efficiency of scheduling resources on multiple disjoint subbands.

[0114] like Fig.13 As shown in , at 1302, the UE may receive a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in an SBFD time slot. The UE may communicate with a network node using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band. The network node may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; Fig.16 Network entity 1602 in a hardware implementation of FIG. 1604 ). Fig. 8A , 8B , 9A, 9B, 10A and Fig. 10B Various examples of a first set of resources in a first frequency band and a second set of resources in a second frequency band are shown.

[0115] In some aspects, the communication between the UE and the network node may be an uplink communication. Thus, the first frequency band is a first uplink frequency band and the second frequency band is a second uplink frequency band. The first uplink frequency band and the second uplink frequency band may be separated by at least one of a downlink frequency band and a guard frequency band.

[0116] In some aspects, such as Fig.13 As shown in , at 1304, the UE may send a PUSCH transmission in a first set of resources in a first uplink frequency band. At 1306, the UE may send a repetition of the PUSCH transmission in a corresponding second set of resources in a second uplink frequency band. For example, as Figure 8BAs shown in , the uplink resources in the SBFD time slot may include a first subband and a second subband separated by a downlink frequency band and a guard frequency band. The first resource set may be a first FDRA 852 in the first subband, and the second resource set may be a second FDRA 854 in the second subband. When communicating with a network node, the UE may send a PUSCH transmission in the first FDRA 852 and send a repetition of the PUSCH transmission in the second FDRA 854.

[0117] In some aspects, such as Fig.13 As shown in , at 1308, the UE may map the same TB for the PUSCH on the first resource set and the corresponding second resource set. Fig. 9B As shown in , the uplink resources in the SBFD time slot may include a first subband and a second subband separated by a downlink frequency band and a guard frequency band. The first resource set may be a first FDRA 952 in the first subband, and the second resource set may be a second FDRA 954 in the second subband. When communicating with a network node, the UE may map the same TB for PUSCH on the first FDRA 952 and the second FDRA 954. That is, the first FDRA 952 on the first subband may include a first portion of the TB, and the second FDRA 954 on the second subband may include a second portion of the TB.

[0118] In some aspects, such as Fig.13 As shown in , at 1310, the UE may send a first PUSCH transmission in a first set of resources in a first uplink frequency band. At 1312, the UE may send a second PUSCH transmission in a corresponding second set of resources in a second uplink frequency band. For example, as Fig. 10B As shown in , the uplink resources in the SBFD time slot may include a first subband and a second subband separated by a downlink frequency band and a guard frequency band. The first resource set may be a first FDRA 1052 in the first subband, and the second resource set may be a second FDRA 1054 in the second subband. When communicating with a network node, the UE may send a first PUSCH (PUSCH 1) transmission in the first FDRA 1052 and a second PUSCH (PUSCH 2) transmission in the second FDRA 1054.

[0119] In some aspects, the communication between the UE and the network node may be a downlink communication. Thus, the first frequency band is a first downlink frequency band and the second frequency band is a second downlink frequency band. The first downlink frequency band and the second downlink frequency band may be separated by at least one of an uplink frequency band and a guard frequency band.

[0120] In some aspects, such as Fig.13As shown in , at 1314, the UE may receive a physical downlink shared channel (PDSCH) transmission in a first set of resources in a first downlink frequency band. At 1316, the UE may receive a repetition of the PDSCH transmission in a corresponding second set of resources in a second downlink frequency band. For example, Fig. 8A As shown in , the downlink resources in the SBFD time slot may include a first subband and a second subband separated by an uplink frequency band and a guard frequency band. The first resource set may be a first FDRA 802 in the first subband, and the second resource set may be a second FDRA 804 in the second subband. When communicating with a network node, the UE may receive a PDSCH transmission in the first FDRA 802 and receive a repetition of the PDSH transmission in the second FDRA 804.

[0121] In some aspects, such as Fig.13 As shown in , at 1318, the UE may map the same TB for the PDSCH on the first resource set and the corresponding second resource set. Fig.9A As shown in , the downlink resources in the SBFD time slot may include a first subband and a second subband separated by an uplink frequency band and a guard frequency band. The first resource set may be a first FDRA 902 in the first subband, and the second resource set may be a second FDRA 904 in the second subband. When communicating with a network node, the UE may map the same TB for the PDSCH on the first FDRA 902 and the second FDRA 904. That is, the first FDRA 902 on the first subband may include a first portion of the TB, and the second FDRA 904 on the second subband may include a second portion of the TB.

[0122] In some aspects, such as Fig.13 As shown in , at 1320, the UE may receive a first PDSCH transmission in a first set of resources in a first downlink frequency band. At 1322, the UE may receive a second PDSCH transmission in a corresponding second set of resources in a second downlink frequency band. For example, as Fig. 10A As shown in , the downlink resources in the SBFD time slot may include a first subband and a second subband separated by an uplink frequency band and a guard frequency band. The first resource set may be a first FDRA 1002 in the first subband, and the second resource set may be a second FDRA 1004 in the second subband. When communicating with a network node, the UE may receive a first PDSCH (PDSCH 1) transmission in the first FDRA 1002 and a second PDSCH (PDSCH 2) transmission in the second FDRA 1004.

[0123] In some respects, Fig.12 and Fig.13In the illustrated method, the UE may further receive an indication to interpret the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band.

[0124] In one example, the indication may be included in the RRC configuration prior to resource allocation. Fig.11 As shown in , UE 1102 may receive an RRC from BS 1104, and the RRC may include the indication.

[0125] In one example, the indication may be included in a DCI, and the DCI may include resource allocation. Fig.11 As shown in , UE 1102 may receive DCI from BS 1104, and the DCI may include the indication. The DCI may further include a resource allocation (eg, FDRA).

[0126] In some aspects, the indication may include additional information for resource allocation. For example, in one example, the indication may be a one-bit indication indicating whether the FDRA is on one subband or on two subbands. In another example, the indication may include a multi-bit indication. The multi-bit indication may indicate information related to the characteristics of the communication, including but not limited to the subband carrying the resource (i.e., the main band in the first band and the second band), whether the communication includes one TB or more than one TB, whether there is duplication of TBs in the first band and the second band, whether the same TB is mapped to the allocated resources in the first band and the second band, or whether the communication is sent or received in the first band and the second band.

[0127] In some aspects, the UE may communicate with the network node using a first set of resources in a first frequency band and a corresponding second set of resources in a second frequency band based on the slot type. In one example, when the slot type is an SBFD slot or an RRC-configured slot type, the UE may communicate with the network node using non-overlapping frequency bands (i.e., using Fig. 8A or the FDRA shown in 8B), and a single FDRA is repeated identically.

[0128] In some aspects, the resource allocation may indicate that a first set of resources starts at the nth resource block in a first frequency band (n is an integer), and a corresponding second set of resources starts at the nth resource block in a second frequency band. Figure 7 In the FDRA shown in , FDRA1 may start on the i-th RB of the first subband, and FDRA2 may start on the i-th RB of the second subband (i is an integer).

[0129] In some aspects, the resource allocation may indicate that a first set of resources begins at the nth resource block in a first frequency band (n is an integer), and a corresponding second set of resources begins at the first resource block in a second frequency band.

[0130] In some aspects, the first frequency band and the second frequency band have different RBG sizes. In one example, the UE can use the same bitmap in the first frequency band and the second frequency band. In another example, the UE can use the first bitmap for the first frequency band and the modified bitmap for the second frequency band to match the bandwidth allocated in the first frequency.

[0131] In some aspects, the resource allocation may include a disjoint resource block allocation or a contiguous resource block allocation within the first frequency band.

[0132] Fig.14 1400 is a flowchart illustrating a method of wireless communication according to various aspects of the present disclosure. The method may be performed by a network node. The network node may be Figure 1 A base station or a component of a base station in an access network, or a network component (e.g., base station 102, 310; BS1104; or Fig.17 The method provides a SBFD resource allocation with disjoint sub-bands, which improves the resource allocation efficiency of scheduling resources on multiple disjoint sub-bands.

[0133] like Fig.14 As shown in FIG. 14, at 1402, a network node may send a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band is disjoint from a second frequency band in a SBFD time slot. The resource allocation may be sent to a UE. The UE may be UE 104, 350, 1102, or Fig.16 In one example, the resource allocation can be sent by the SBFD sending component 199. Fig. 8A , 8B , 9A, 9B, 10A and Fig. 10B Various examples of a first set of resources in a first frequency band and a second set of resources in a second frequency band are shown.

[0134] At 1404, the network node may communicate with a user equipment (UE) using a first set of resources in a first frequency band and a corresponding second set of resources in a second frequency band. The communication may be performed, for example, by the SBFD transmitting component 199. Fig.11 As shown in FIG, BS 1104 may communicate with UE 1102 via DL / UL transmission 1112. The communication may use a first set of resources in a first frequency band and a corresponding second set of resources in a second frequency band.

[0135] Fig.15 1500 is a flowchart illustrating a method of wireless communication according to various aspects of the present disclosure. The method may be performed by a network node. The network node may be Figure 1 A base station or a component of a base station in an access network, or a network component (e.g., base station 102, 310; BS1104; or Fig.17 The method provides a SBFD resource allocation with disjoint sub-bands, which improves the resource allocation efficiency of scheduling resources on multiple disjoint sub-bands.

[0136] like Fig.15 As shown in FIG. 1 , steps 1504 and 1506 are similar to Fig.14 That is, at 1504, the network node may send a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a SBFD time slot. At 1506, the network node may communicate with the UE using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band. The details of these processes are similar to Fig.14 Those shown in are therefore omitted here for the sake of brevity.

[0137] In some aspects, prior to 1504, at 1502, the network node may send an indication for interpreting the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band. In some aspects, the indication may be included in an RRC configuration prior to the resource allocation, or in downlink control information including the resource allocation. For example, Fig.11 As shown in , in one configuration, BS 1104 may send (1106) an RRC configuration to UE 1102, and the RRC configuration may include the indication. In one configuration, BS 1104 may send (1108) a DCI or other type of resource allocation, such as a configured grant or a semi-persistent resource allocation, to UE 1102, which includes a resource allocation (e.g., FDRA), and the DCI may include the indication.

[0138] In some aspects, the indication may be a one-bit indication indicating whether the FDRA is on one subband or on two subbands. In another example, the indication may include a multi-bit indication. The multi-bit indication may indicate information related to the characteristics of the communication, including but not limited to the subband carrying the resource (i.e., the main band in the first band and the second band), whether the communication includes one TB or more than one TB, whether there is duplication of TBs in the first band and the second band, whether the same TB is mapped to the allocated resources in the first band and the second band, or whether the communication is a transmission or reception in the first band and the second band.

[0139] In some aspects, communication utilizing a first set of resources in a first frequency band and a corresponding second set of resources in a second frequency band may be based on a slot type. In one example, when the slot type is a SBFD slot or a slot type configured via RRC, a single FDRA may be repeated identically on non-overlapping frequency bands in a SBFD slot (i.e., using Fig. 8A or FDRA shown in 8B).

[0140] In some aspects, the resource allocation may indicate that a first set of resources starts at the nth resource block in a first frequency band (n is an integer), and a corresponding second set of resources starts at the nth resource block in a second frequency band. Figure 7 In the FDRA shown in , FDRA1 may start on the i-th RB of the first subband, and FDRA2 may start on the i-th RB of the second subband (i is an integer).

[0141] In some aspects, the resource allocation may indicate that a first set of resources begins at the nth resource block in a first frequency band (n is an integer), and a corresponding second set of resources begins at the first resource block in a second frequency band.

[0142] In some aspects, the first frequency band and the second frequency band have different resource block group (RBG) sizes. In one example, the UE can use the same bitmap in the first frequency band and the second frequency band. In another example, the UE can use the first bitmap for the first frequency band and the modified bitmap for the second frequency band to match the bandwidth allocated in the first frequency.

[0143] Fig.161600 is a diagram illustrating an example of a hardware implementation for an apparatus 1604. The apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., a cellular RF transceiver). The cellular baseband processor 1624 may include on-chip memory 1624'. In some aspects, the apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606'. In some aspects, the device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, an SPS module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), other memory modules 1626, a power source 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include their own dedicated antennas, and / or communicate using an antenna 1680. The cellular baseband processor 1624 communicates with the UE 104 and / or RUs associated with the network entity 1602 via one or more antennas 1680 through the transceiver 1622. The cellular baseband processor 1624 and the application processor 1606 may each include a computer-readable medium / memory 1624', 1626', respectively. Other memory modules 1626 may also be considered as computer-readable medium / memory. Each computer-readable medium / memory 1624', 1606', 1626 may be non-temporary. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, which includes executing software stored on a computer-readable medium / memory. When the software is executed by the cellular baseband processor 1624 / application processor 1606, the cellular baseband processor 1624 / application processor 1606 performs the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software.The cellular baseband processor 1624 / application processor 1606 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1604 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1624 and / or the application processor 1606, and in another configuration, the device 1604 may be the entire UE (e.g., see. Figure 3 350) and includes other modules of device 1604.

[0144] As described above, component 198 (i.e., SBFD receiving component 198) can be configured to receive a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a SBFD time slot, and communicate with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. SBFD receiving component 198 can also be configured to perform a combined Fig.12 or the flowchart described in 13 and / or by Fig.11 1604. Component 198 may be in the cellular baseband processor 1624, the application processor 1606, or in both the cellular baseband processor 1624 and the application processor 1606. Component 198 may be one or more hardware components specifically configured to perform the stated processing / algorithms, implemented by one or more processors configured to perform the stated processing / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1604 may include various components configured to implement various functions. In one configuration, the device 1604 (specifically, the cellular baseband processor 1624 and / or the application processor 1606) includes: a unit for receiving a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band is non-intersecting with a second frequency band in a SBFD time slot; a unit for communicating with a network node using a first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. The device may also include a unit for performing a combined Fig.12 or the flowchart described in 13 and / or by Fig.11 The means may be components 198 of the apparatus 1604 configured to perform the functions recited by these means. As described above, the apparatus 1604 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, these means may be the TX processor 368, the RX processor 356, and / or the controller / controller 359 configured to perform the functions recited by these means.

[0145] Fig.17 1700 is a diagram illustrating an example of a hardware implementation for a network entity 1702. The network entity 1702 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. For example, depending on the layer functionality handled by the component 199, the network entity 1702 may include a CU 1710; both a CU 1710 and a DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both a DU 1730 and a RU 1740; or a RU 1740. The CU 1710 may include a CU processor 1712. The CU processor 1712 may include an on-chip memory 1712'. In some aspects, the CU 1710 may also include an additional memory module 1714 and a communication interface 1718. CU 1710 communicates with DU 1730 via a mid-range link such as an F1 interface. DU 1730 may include a DU processor 1732. DU processor 1732 may include on-chip memory 1732'. In some aspects, DU 1730 may also include other memory modules 1734 and a communication interface 1738. DU 1730 communicates with RU 1740 via a front-range link. RU 1740 may include a RU processor 1742. RU processor 1742 may include on-chip memory 1742'. In some aspects, RU 1740 may also include other memory modules 1744, one or more transceivers 1746, antenna 1780, and communication interface 1748. RU 1740 communicates with UE 104. On-chip memory 1712', 1732', 1742' and other memory modules 1714, 1734, 1744 may each be considered as a computer-readable medium / memory. Each computer readable medium / memory may be non-temporary. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer readable medium / memory. When the software is executed by the corresponding processor, the processor performs the various functions described above. The computer readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0146] As described above, component 199 (i.e., SBFD transmitting component 199) can be configured to transmit a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band is disjoint from a second frequency band in a SBFD time slot, and communicate with the UE using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band. SBFD transmitting component 199 can also be configured to perform a combined Fig.14 or the flowchart described in 15 and / or by Fig.111702. Component 199 may be within one or more processors of one or more of CU 1710, DU 1730, and RU 1740. Component 199 may be one or more hardware components specifically configured to perform the stated processing / algorithms, implemented by one or more processors configured to perform the stated processing / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1702 may include various components configured to implement various functions. In one configuration, network entity 1702 includes: a unit for sending a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band is non-intersecting with a second frequency band in a SBFD time slot; a unit for communicating with a UE using a first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. The network entity may also include a unit for performing a combined Fig.14 or the flowchart described in 15 and / or by Fig.11 The means may be components 199 of the network entity 1702 configured to perform the functions recited by these means. As described above, the network entity 1702 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, these means may be the TX processor 316, the RX processor 370, and / or the controller / controller 375 configured to perform the functions recited by these means.

[0147] Various aspects of the present disclosure provide a method of wireless communication at a UE and a related apparatus. In the method, the UE receives a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band is disjoint with a second frequency band in an SBFD time slot, and communicates with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band. The method allows allocating FDRAs in multiple disjoint subbands according to various schemes, thereby improving the resource allocation efficiency of scheduling resources on multiple disjoint subbands.

[0148] It should be understood that the specific order or block hierarchy in the process / flow chart disclosed herein is only an example of an exemplary method. It should be understood that the specific order or block hierarchy in these processes / flow charts can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in an exemplary order, but are not limited to the specific order or hierarchy provided.

[0149] To enable any person of ordinary skill in the art to implement the various aspects described herein, the above description is made around various aspects. It is obvious to a person of ordinary skill in the art that various modifications to these aspects are possible, and the general principles defined herein may also be applicable to other aspects. Therefore, the present invention is not limited to the aspects described herein, but is consistent with the full scope of the present invention. Modifying a certain component with a singular form does not mean "one and only one", but may be "one or more". Terms such as "if", "when..." and "when..." do not imply a direct time relationship or reaction. That is, these phrases (e.g., "when...") do not mean to take action immediately in response to an action or to take action during the occurrence of an action, but simply mean that if the conditions are met, an action will occur, but there is no need to have a specific or immediate time constraint on the occurrence of the action. The word "exemplary" used herein means "used as an example, illustration or description". Any aspect described as "exemplary" herein should not be interpreted as being more preferred or more advantageous than other aspects. Unless otherwise specifically stated, 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, which may include multiple A, multiple B, or multiple 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members or some members of A, B, or C. A set should be interpreted as a group of elements, where the elements are numbered one or more. Thus, for a group X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a group of devices. All structural and functional equivalents of the components of the various aspects described throughout the present disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, which are known or will be known to those of ordinary skill in the art. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is clearly recorded in the claims. Words such as "module", "device", "element", "equipment", etc. are not substitutes for the word "unit".Therefore, a constituent element of a claim should not be construed as a functional module unless the constituent element is explicitly described using the wording of “functional module”.

[0150] As used herein, the phrase "based on" shall not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) shall be interpreted as "based at least on A" unless specifically stated otherwise.

[0151] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limited thereto.

[0152] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving a resource allocation for a first set of resources in a first frequency band, wherein the first frequency band does not intersect with a second frequency band in a sub-band full-duplex (SBFD) time slot; and communicating with a network node using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band.

[0153] Aspect 2 is a method according to Aspect 1, wherein the first resource set is an uplink resource in a first uplink frequency band, the first uplink frequency band is separated from the second uplink frequency band in the SBFD time slot by at least one of a downlink frequency band or a protection frequency band, and communicating with the network node includes: using the first resource set in the first uplink frequency band and the corresponding second resource set in the second uplink frequency band to send uplink communication to the network node.

[0154] Aspect 3 is a method according to Aspect 2, wherein sending the uplink communication includes: sending PUSCH transmission in the first resource set in the first uplink frequency band; and sending a repetition of the PUSCH transmission in the corresponding second resource set in the second uplink frequency band.

[0155] Aspect 4 is a method according to any one of aspects 1 or 2, wherein the method further comprises: mapping the same transport block for PUSCH on the first resource set and the corresponding second resource set.

[0156] Aspect 5 is a method according to Aspect 2, wherein sending the uplink communication includes: sending a first PUSCH transmission in the first resource set in the first uplink frequency band; and sending a second PUSCH transmission in the corresponding second resource set in the second uplink frequency band.

[0157] Aspect 6 is a method according to Aspect 1, wherein the first resource set is downlink resources in a first downlink frequency band, the first downlink frequency band is separated from the second downlink frequency band in the SBFD time slot by at least one of an uplink frequency band or a protection frequency band, and communicating with the network node includes: receiving downlink communication from the network node in the first resource set in the first downlink frequency band and the corresponding second resource set in the second downlink frequency band.

[0158] Aspect 7 is a method according to Aspect 6, wherein receiving the downlink communication includes: receiving PDSCH transmission in the first resource set in the first downlink frequency band; and receiving a repetition of the PDSCH transmission in the corresponding second resource set in the second downlink frequency band.

[0159] Aspect 8 is a method according to any one of aspects 1 and 6, wherein the method further comprises: mapping the same transport block for PDSCH on the first resource set and the corresponding second resource set.

[0160] Aspect 9 is a method according to Aspect 6, wherein receiving the downlink communication includes: receiving a first PDSCH transmission in the first resource set in the first downlink frequency band; and receiving a second PDSCH transmission in the corresponding second resource set in the second downlink frequency band.

[0161] Aspect 10 is a method according to any one of aspects 1-9, wherein the method further comprises: receiving an indication to interpret the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band.

[0162] Aspect 11 is a method according to aspect 10, wherein the indication is included in an RRC configuration prior to the resource allocation.

[0163] Aspect 12 is a method according to aspect 10, wherein the indication is included in downlink control information including the resource allocation.

[0164] Aspect 13 is a method according to Aspect 10, wherein the indication further indicates one of the following: a main frequency band in the first frequency band and the second frequency band, repetition of transmission on the first frequency band and the second frequency band, mapping the same transmission block on the allocated resources in the first frequency band and the second frequency band, or sending or receiving different transmissions in the first frequency band and the second frequency band.

[0165] Aspect 14 is a method according to any one of aspects 1-13, wherein the UE communicates with the network node using the first resource set in the first frequency band and the corresponding second resource set in the second frequency band based on a time slot type.

[0166] Aspect 15 is a method according to aspect 14, wherein the time slot type is a SBFD time slot or an RRC-configured time slot type associated with interpreting a single FDRA on disjoint frequency bands.

[0167] Aspect 16 is a method according to any one of Aspects 1-15, wherein the resource allocation indicates that the first resource set starts at the nth resource block in the first frequency band, n is an integer, and the corresponding second resource set starts at the nth resource block in the second frequency band.

[0168] Aspect 17 is a method according to any one of Aspects 1-15, wherein the resource allocation indicates that the first resource set starts at the nth resource block in the first frequency band, n is an integer, and the corresponding second resource set starts at the first resource block in the second frequency band.

[0169] Aspect 18 is a method according to any one of aspects 1-17, wherein the first frequency band and the second frequency band have different RBG sizes.

[0170] Aspect 19 is a method according to aspect 18, wherein the UE uses the same bitmap in the first frequency band and the second frequency band.

[0171] Aspect 20 is a method according to aspect 18, wherein the UE uses a first bitmap for the first frequency band and uses a modified bitmap for the second frequency band to match the bandwidth allocated in the first frequency.

[0172] Aspect 21 is a method according to any one of aspects 1-20, wherein the resource allocation comprises non-overlapping resource block allocation or continuous resource block allocation within the first frequency band.

[0173] Aspect 22 is an apparatus comprising means for executing the method according to any one of aspects 1-21.

[0174] Aspect 23 is an apparatus comprising a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to perform the method according to any one of aspects 1-21.

[0175] In aspect 24, the apparatus according to aspect 22 or 23 further comprises at least one transceiver.

[0176] Aspect 25 is a non-transitory computer-readable medium storing computer executable code, wherein when the code is executed by a processor, the processor is caused to perform the method according to any one of aspects 1-21.

[0177] Aspect 26 is a method for wireless communication at a network node. The method includes: sending a resource allocation for a first set of resources in a first frequency band, the first frequency band being disjoint from a second frequency band in an SBFD time slot; and communicating with a UE using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

[0178] Aspect 27 is a method according to Aspect 26, wherein the method further includes: sending an indication to interpret the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band, wherein the indication is included in an RRC configuration prior to the resource configuration, or included in downlink control information including the resource allocation.

[0179] Aspect 28 is a method according to Aspect 27, wherein the indication further indicates one of the following: a main frequency band in the first frequency band and the second frequency band, repetition of transmission on the first frequency band and the second frequency band, mapping the same transmission block on the allocated resources in the first frequency band and the second frequency band, or sending or receiving different transmissions in the first frequency band and the second frequency band.

[0180] Aspect 29 is a method according to any one of aspects 26-28, wherein the communication using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band is based on a time slot type.

[0181] Aspect 30 is a method according to any one of Aspects 26-29, wherein the resource allocation indicates that the first resource set starts at the nth resource block in the first frequency band, n is an integer, and the corresponding second resource set starts at the nth resource block in the second frequency band.

[0182] Aspect 31 is a method according to any one of aspects 26-29, wherein the resource allocation indicates that the first resource set starts at the nth resource block in the first frequency band, n is an integer, and the corresponding second resource set starts at the first resource block in the second frequency band.

[0183] Aspect 32 is a method according to any one of aspects 26-31, wherein the first frequency band and the second frequency band have different RBG sizes.

[0184] Aspect 33 is an apparatus comprising means for performing the method according to any one of aspects 26-32.

[0185] Aspect 34 is an apparatus comprising a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to perform the method according to any one of aspects 26-32.

[0186] In aspect 35, the apparatus according to aspect 33 or 34 further comprises at least one transceiver.

[0187] Aspect 36 is a non-transitory computer-readable medium storing computer executable code, wherein when the code is executed by a processor, the processor is caused to perform the method according to any one of aspects 26-32.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: receiving a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a sub-band full duplex (SBFD) time slot; and Communicating with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

2. The device according to claim 1, wherein: The first set of resources are uplink resources in a first uplink frequency band, the first uplink frequency band being separated from a second uplink frequency band in the SBFD time slot by at least one of a downlink frequency band or a guard frequency band, and wherein, in order to communicate with the network node, the at least one processor is configured to: An uplink communication is sent to the network node using the first set of resources in the first uplink frequency band and the corresponding second set of resources in the second uplink frequency band.

3. The device according to claim 2, wherein: To send the uplink communication, the at least one processor is configured to: sending a physical uplink shared channel (PUSCH) transmission in the first set of resources in the first uplink frequency band; and A repetition of the PUSCH transmission is sent in the corresponding second set of resources in the second uplink frequency band.

4. The device according to claim 2, wherein: The at least one processor is further configured to: On the first resource set and the corresponding second resource set, the same transport block is mapped for a physical uplink shared channel (PUSCH).

5. The device according to claim 2, wherein: To transmit the uplink communication, the at least one processor is configured to include: sending a first physical uplink shared channel (PUSCH) transmission in the first set of resources in the first uplink frequency band; and A second PUSCH transmission is sent in the corresponding second set of resources in the second uplink frequency band.

6. The device according to claim 1, wherein: The first set of resources are downlink resources in a first downlink frequency band, the first downlink frequency band being separated from a second downlink frequency band in the SBFD time slot by at least one of an uplink frequency band or a guard frequency band, and wherein, in order to communicate with the network node, the at least one processor is configured to: Downlink communications are received from the network node in the first set of resources in the first downlink frequency band and the corresponding second set of resources in the second downlink frequency band.

7. The device according to claim 6, wherein: To receive the downlink communication, the at least one processor is configured to: receiving a physical downlink shared channel (PDSCH) transmission in the first set of resources in the first downlink frequency band; and A repetition of the PDSCH transmission is received in the corresponding second set of resources in the second downlink frequency band.

8. The device according to claim 6, wherein: The downlink communication maps the same transport block for a physical downlink shared channel (PDSCH) on the first resource set and the corresponding second resource set.

9. The device according to claim 6, wherein: To receive the downlink communication, the at least one processor is configured to: receiving a first physical downlink shared channel (PDSCH) transmission in the first set of resources in the first downlink frequency band; and A second PDSCH transmission is received in the corresponding second set of resources in the second downlink frequency band.

10. The device according to claim 1, wherein: The at least one processor is further configured to: An indication is received to interpret the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band.

11. The device according to claim 10, wherein: The indication is included in a radio resource control (RRC) configuration prior to the resource allocation.

12. The device according to claim 10, wherein: The indication is included in downlink control information including the resource allocation.

13. The device according to claim 10, wherein: The instructions further indicate one of the following: a main frequency band among the first frequency band and the second frequency band, repetition of transmissions on said first frequency band and said second frequency band, mapping the same transport block on the allocated resources in the first frequency band and the second frequency band, or Different transmissions are sent or received in the first frequency band and the second frequency band.

14. The device according to claim 1, wherein: The at least one processor is configured to communicate with the network node using the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band based on a timeslot type.

15. The device according to claim 14, wherein: The time slot type is a SBFD time slot or an RRC configured time slot type associated with interpreting a single frequency domain resource allocation (FDRA) on disjoint frequency bands.

16. The device according to claim 1, wherein The resource allocation indicates that the first set of resources starts at an nth resource block in the first frequency band, n being an integer, and the corresponding second set of resources starts at the nth resource block in the second frequency band.

17. The device according to claim 1, wherein: The resource allocation indicates that the first set of resources starts at an nth resource block in the first frequency band, n being an integer, and the corresponding second set of resources starts at a first resource block in the second frequency band.

18. The device according to claim 1, wherein: The first frequency band and the second frequency band have different resource block group (RBG) sizes.

19. The device according to claim 18, wherein: The same bitmap is used in the first frequency band and the second frequency band.

20. The device according to claim 18, wherein A first bitmap is used for the first frequency band and a modified bitmap is used for the second frequency band to match the bandwidth allocated in the first frequency band.

21. The device according to claim 1, wherein The resource allocation includes a disjoint resource block allocation or a contiguous resource block allocation within the first frequency band.

22. An apparatus for wireless communication at a network entity, comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: transmitting a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a sub-band full duplex (SBFD) time slot; and Communicate with a user equipment (UE) using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

23. The device according to claim 22, wherein: The at least one processor is further configured to: An indication is sent to interpret the resource allocation as two frequency domain resource allocations spanning the first frequency band and the second frequency band, wherein the indication is included in a radio resource control (RRC) configuration prior to the resource configuration or in downlink control information including the resource allocation.

24. The device according to claim 23, wherein: The instructions further indicate one of the following: a main frequency band among the first frequency band and the second frequency band, repetition of transmissions on said first frequency band and said second frequency band, mapping the same transport block on the allocated resources in the first frequency band and the second frequency band, or Different transmissions are sent or received in the first frequency band and the second frequency band.

25. The device according to claim 22, wherein: The communication utilizing the first set of resources in the first frequency band and the corresponding second set of resources in the second frequency band is based on a slot type.

26. The device according to claim 22, wherein: The resource allocation indicates that the first set of resources starts at an nth resource block in the first frequency band, n being an integer, and the corresponding second set of resources starts at the nth resource block in the second frequency band.

27. The device according to claim 22, wherein: The resource allocation indicates that the first set of resources starts at an nth resource block in the first frequency band, n being an integer, and the corresponding second set of resources starts at a first resource block in the second frequency band.

28. The device according to claim 22, wherein: The first frequency band and the second frequency band have different resource block group (RBG) sizes.

29. A method for wireless communication at a user equipment (UE), comprising: receiving a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a sub-band full duplex (SBFD) time slot; as well as Communicating with a network node using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

30. A method for wireless communication at a network node, comprising: transmitting a resource allocation for a first set of resources in a first frequency band that is disjoint from a second frequency band in a sub-band full duplex (SBFD) time slot; as well as Communicate with a user equipment (UE) using the first set of resources in the first frequency band and a corresponding second set of resources in the second frequency band.

Images