Disjoint resource indication for full-duplex operation

Abstract

Various aspects of the present disclosure relate generally to wireless communications. In some aspects, a wireless node may receive a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups in a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; identify the allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and communicate using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups. Many other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 003,062, filed on March 31, 2020, entitled “DISJOINT RESOURCE INDICATION FOR FULL-DUPLEX OPERATION,” and U.S. Non-Provisional Patent Application No. 17 / 214,640, filed on March 26, 2021, entitled “DISJOINT RESOURCE INDICATION FOR FULL-DUPLEX OPERATION,” both of which are expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communications and techniques and apparatus for disjoint resource indication for full-duplex operation. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that are capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs) that can support communications for multiple user equipment (UEs). A UE may communicate with a BS via a downlink and an uplink. A "downlink" (or "forward link") refers to a communication link from a BS to a UE, and an "uplink" (or "reverse link") refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different user devices to communicate at a city, country, region, and even global level. NR, which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL) and / or using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0007] In some aspects, a wireless communication method performed by a wireless node may include: receiving a frequency domain resource allocation indicator that identifies an allocation of a set of resource block groups among multiple resource block groups in a bandwidth portion, wherein the bandwidth portion includes multiple non-intersecting portions of the bandwidth portion, and the multiple non-intersecting portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; identifying the allocation of the set of resource block groups based at least in part on the frequency domain resource allocation indicator; and communicating using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0008] In some aspects, a wireless node for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups in a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; identify the allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and communicate using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0009] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless node, may cause the one or more processors to: receive a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups in a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; identify the allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and communicate using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0010] In some aspects, an apparatus for wireless communication may include: components for receiving a frequency domain resource allocation indicator that identifies an allocation of a set of resource block groups among a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of non-intersecting portions of the bandwidth portion, and the plurality of non-intersecting portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; components for identifying the allocation of the set of resource block groups based at least in part on the frequency domain resource allocation indicator; and components for communicating using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0011] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as described herein with reference to and illustrated by the accompanying figures and description.

[0012] The foregoing fairly broadly summarizes the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures to achieve the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein, their organization and methods of operation, and associated advantages will be better understood from the following description. Each figure is provided for the purpose of illustration and description, and not as a limitation of the scope of the claims.

[0013] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that these aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical devices, or devices supported by artificial intelligence). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. The device in combination with the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, (multiple) processors, interleavers, adders, or summers). The aspects described herein can be practiced in a variety of devices, components, systems, distributed arrangements, or end-user devices with different sizes, shapes, and structures. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to be able to understand the above features of the present disclosure in detail, a more specific description briefly summarized above may be made by reference to various aspects, some of which are shown in the accompanying drawings. However, it should be noted that the attached drawings only show some typical aspects of the present disclosure and should not be considered as limiting its scope, as the description may allow for other equivalent aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0015] Figure 1 is a schematic diagram illustrating an example of a wireless network according to the present disclosure.

[0016] Figure 2 is a schematic diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0017] Figure 3-Figure 5 is a schematic diagram illustrating an example of a full-duplex operation mode according to the present disclosure.

[0018] Figure 6 is a diagram showing an example of a full-duplex type according to the present disclosure.

[0019] Figure 7 is a diagram illustrating an example associated with disjoint resource indication for full-duplex operation according to the present disclosure.

[0020] Figure 8is a diagram illustrating an example process associated with disjoint resource indication for full-duplex operation according to the present disclosure.

[0021] Fig. 9 is a block diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0022] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings of this article, those skilled in the art will understand that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects described herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover devices and methods that are practiced using other structures, functions, or structures and functions other than the various aspects disclosed herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0023] Several aspects of telecommunication systems will now be described with reference to various devices and techniques. These devices and techniques will be described in the detailed description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, 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.

[0024] It should be noted that although various aspects may be described herein using terminology generally associated with 5G or NR radio access technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0025] Figure 1is a schematic diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0026] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. In this document, the terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NR", and "cell" may be used interchangeably.

[0027] In some aspects, the cells may not necessarily be fixed, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0028] The wireless network 100 may also include a relay station. A relay station is an entity that can receive a data transmission from an upstream station (e.g., a BS or a UE) and send the data transmission to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions of other UEs. Figure 1 In the example shown in FIG. 1 , a relay BS 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.

[0029] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a higher transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0030] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0031] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle-mounted component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0032] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may, for example, provide a connection for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as a processor component and / or a memory component). In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0033] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0034] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary for communicating with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0035] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) (which may span 410 MHz to 7.125 GHz), and / or may communicate using an operating band having a second frequency range (FR2) (which may span 24.25 GHz to 52.6 GHz). Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, although it is different from an extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" or the like (if used herein) may broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically noted, it should be understood that the term "millimeter wave" and the like (if used herein) can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0036] As mentioned above, providing Figure 1 As an example. Other examples can be related to Figure 1 The description is different.

[0037] Figure 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0038] At the base station 110, the transmit processor 220 may receive data from the data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). If applicable, a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and may provide T output symbol streams to T modulators (MOD) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0039] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, etc. In some aspects, one or more components of the UE 120 may be included in the housing 284 .

[0040] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0041] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included in, one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0042] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 (if applicable), further processed by the modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some aspects, the modulator and demodulator (e.g., modulator / demodulator 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 7-8 described).

[0043] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., the modulator / demodulator 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receive processors 238, transmit processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as described in reference to Figure 7-8 described).

[0044] A wireless node (which may include a controller / processor 240 of a base station 110, a controller / processor 280 of a UE 120, and / or Figure 2 Any other component(s) of the base station 110 may perform one or more techniques associated with disjoint resource indication for full-duplex operation as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) may perform or direct e.g. Figure 8 800 and / or operations of other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 8 The process 800 and / or operations of other processes as described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0045] In some aspects, the wireless node includes: means for receiving a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups in a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; means for identifying the allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; or means for communicating using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups. In some aspects, means for the wireless node to perform operations described herein may include, for example, one or more of a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for a wireless node to perform operations described herein may include, for example, one or more of an antenna 252, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a modulator 254, a controller / processor 280, or a memory 282.

[0046] In some aspects, the wireless node includes means for determining the common size based at least in part on the size of the first disjoint portion of the other of the uplink bandwidth or the downlink bandwidth or the size of the second disjoint portion of the other of the uplink bandwidth or the downlink bandwidth. In some aspects, the means for the wireless node to perform operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antenna 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246. In some aspects, the means for the wireless node to perform operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0047] In some aspects, the wireless node includes means for determining at least one of the first size or the second size based at least in part on the resource block group size table. In some aspects, the wireless node includes means for determining at least one of the first size or the second size based at least in part on at least one stored bandwidth portion configuration. In some aspects, the means for the wireless node to perform operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antenna 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246. In some aspects, the means for the wireless node to perform operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0048] In some aspects, the wireless node includes means for determining at least one of the first size or the second size based at least in part on a resource block group size table including a non-full-duplex operation or non-disjoint bandwidth portion operation configuration and a full-duplex operation or disjoint bandwidth portion operation configuration. In some aspects, means for the wireless node to perform operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antenna 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246. In some aspects, means for the wireless node to perform operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0049] In some aspects, the wireless node includes means for determining at least one of the first size or the second size based at least in part on a resource block group size table that includes a full-duplex operation or a disjoint bandwidth portion operation configuration instead of a non-full-duplex operation or a non-disjoint bandwidth portion operation configuration. In some aspects, means for the wireless node to perform operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antenna 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246. In some aspects, means for the wireless node to perform operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0050] although Figure 2 The blocks in the 200 and 210 are shown as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0051] As mentioned above, providing Figure 2 As an example. Other examples can be related to Figure 2 The description is different.

[0052] Figure 3-5is a schematic diagram illustrating one or more examples of a full-duplex operation mode according to the present disclosure. The UE and the BS may communicate with each other using beams. For example, the beam may be a downlink beam (e.g., over which information may be transmitted from the BS to the UE) or an uplink beam (e.g., over which information may be transmitted from the UE to the BS). In some aspects, the UE and the BS may be integrated access backhaul (IAB) wireless nodes.

[0053] The communication link between the UE and the BS may be referred to as half-duplex when the communication link includes only one of an uplink or a downlink, or may be referred to as full-duplex when the communication link includes both an uplink and a downlink. A full-duplex communication link may provide increased scalability of data rates on the link compared to a half-duplex communication link. In a full-duplex communication link, different antenna elements, subarrays, or antenna panels of a wireless communication device may perform uplink and downlink communications simultaneously or concurrently.

[0054] Compared to half-duplex communication, full-duplex communication may present certain challenges. For example, a wireless communication device (e.g., UE, BA and / or wireless node) may experience self-interference between the uplink beam and the downlink beam of a full-duplex link or between components of the wireless communication device. This self-interference may complicate monitoring of reference signals to detect beam failures. In addition, self-interference, cross-correlation, etc. may occur in a full-duplex communication link, but may not occur in a half-duplex communication link. Additionally, a wireless communication device may experience interfering transmissions from other wireless communication devices in the wireless network (e.g., based at least in part on the angular spread of beams sent by other wireless communication devices), which may cause beam failures (e.g., uplink beam failures, downlink beam failures, etc.).

[0055] like Figure 3 As shown in FIG. 1 , the example wireless network 300 includes a BS 310-1 operating in a full-duplex operation mode. The BS 310-1 may receive an uplink from a UE 320-2 and send a downlink to the UE 320-1. The UE-320-1 and the UE-320-2 may operate in a half-duplex operation mode. The BS 310-1 may experience downlink self-interference to the uplink based at least in part on the downlink sent to the UE 320-1 and the uplink received from the UE 320-2. Additionally, the BS 310-1 may experience interfering transmissions (e.g., from the BS 310-2) from other wireless communication devices transmitting in the wireless network 300. In addition, the UE 320-1 interferes with transmissions (e.g., from the UE 320-2, from the BS 310-2, etc.) from other wireless communication devices transmitting in the wireless network 300.

[0056] like Figure 4, the example wireless network 400 includes a UE 420-1 operating in a full-duplex operation mode. The UE 420-1 may send an uplink to the BS 410-1 and may receive a downlink from the BS 410-1. In some aspects, the BS 410-1 may operate in a full-duplex operation mode. The UE 420-1 may experience self-interference of the uplink to the downlink based at least in part on the uplink sent to the BS 410-1 and the downlink received from the BS 410-1. The wireless network 400 may include other wireless communication devices (such as BS 410-2 and UE 420-2). The BS 410-2 may send a downlink to the UE 410-2. The UE 420-1 may experience interfering transmissions based at least in part on the transmissions of the BS 410-2 and / or the UE 420-1. For example, a downlink transmitted by BS 410-2 may have an angular spread that may cause interfering transmissions to be received by UE 420-1. Similarly, an uplink transmitted by UE 420-2 may have an angular spread that may cause interfering transmissions to be received by UE 420-1.

[0057] Figure 5 As shown in , the example wireless network 500 includes a UE 520-1 operating in a full-duplex operation mode. The UE 520-1 may send an uplink to the BS 510-1 and may receive a downlink from the BS 510-2. The UE 520-1 may include a multi-transmit and receive (multi-TRP) architecture. The UE 520-1 may experience self-interference of the uplink to the downlink based at least in part on the uplink sent to the BS 510-1 and the downlink received from the BS 510-2. The BS 510-1 and the BS 510-2 may operate in a half-duplex operation mode. The BS 510-2 may send a downlink to the UE 520-2. In some aspects, the UE 520-1 may experience one or more interfering transmissions based at least in part on the transmissions of the BS 510-1, the BS 510-2, and / or the UE 520-2.

[0058] As mentioned above, providing Figure 3-5 As an example. Other examples can be related to Figure 3-5 The description is different.

[0059] Figure 6 600 is a schematic diagram illustrating one or more examples of full-duplex types according to the present disclosure. As described above, full-duplex operation may involve communication with both an uplink (UL) and a downlink (DL) at the same time (e.g., transmitting and receiving at the same time). The uplink and downlink may share resources associated with the communication (e.g., time resources and / or frequency resources).

[0060] like Figure 6 As shown in , full-duplex communication can be an in-band full-duplex (IBFD) mode (e.g., a mode including an uplink and a downlink that share the same time resources and / or frequency resources). In some aspects, the IBFD mode can be a fully overlapping IBFD mode, so that the downlink resources can completely overlap with the uplink resources (e.g., all uplink resources are shared with the downlink resources). In some aspects, the fully overlapping IBFD mode can have uplink resources that completely overlap with the downlink resources. In some aspects, the IBFD communication can be a partially overlapping IBFD mode, so that the downlink resources do not completely overlap with the uplink resources (e.g., only some uplink resources are shared with the downlink resources).

[0061] In some aspects, the full-duplex mode may be a sub-band frequency division duplex (FDD) mode (e.g., a mode including an uplink and a downlink that share the same time resources and use different frequency resources). In some aspects, resources associated with the downlink and resources associated with the uplink may be separated in the frequency domain by a guard band (GB) (e.g., a frequency range not allocated to an uplink or a downlink).

[0062] As mentioned above, providing Figure 6 As an example. Other examples can be related to Figure 6 The description is different.

[0063] A wireless communication standard or administration may specify how the wireless spectrum is used. For example, 3GPP may specify how the wireless spectrum is used for 5G / NR radio access technology and interfaces. For example, a specification may indicate whether a frequency band is used as a paired spectrum or a non-paired spectrum. The frequency band in the paired spectrum may use a first frequency region for uplink communication and a second frequency region for downlink communication, wherein the second frequency region does not overlap with the second frequency region. For example, a paired frequency band may have an uplink operating frequency band and a downlink operating frequency band that are configured to use non-overlapping frequency regions. Some deployments may use FDD in paired frequency bands. As specified in 3GPP Technical Specification (TS) 38.101-1, examples of paired frequency bands in NR include NR operating frequency bands n1, n2, n3, n5, n7, n8, n12, n20, n25, and n28.

[0064] Unpaired bands may allow downlink and uplink operations within the same frequency region (e.g., the same operating band). For example, unpaired bands may configure the uplink operating band and the downlink operating band within the same frequency range. Some deployments may use time division duplexing (TDD) in unpaired bands, where some time intervals (e.g., time slots, sub-time slots, etc.) are used for uplink communications and other time intervals are used for downlink communications. In this case, substantially the entire bandwidth of the component carrier may be used for downlink communications or uplink communications, depending on whether the communication is performed in a downlink time slot, an uplink time slot, or a special time slot (where downlink or uplink communications may be scheduled). Examples of unpaired bands include NR operating bands n40, n41, and n50 specified by 3GPP TS 38.101-1.

[0065] In some cases, the use of TDD in an unpaired spectrum may be inefficient. For example, the uplink transmit power may be limited, which means that the UE may not be able to transmit with enough power to effectively utilize the full bandwidth of the uplink timeslot. This may be particularly problematic in large cells at the cell edge. In addition, the use of TDD may introduce delays relative to schemes in which uplink communications and downlink communications can be performed in the same time interval, because a given time interval may be used only for uplink communications or only for downlink communications using TDD. However, frequency domain resource allocation (FDRA) for a bandwidth portion (BWP) in the case of FDD in an unpaired spectrum may be problematic due to the gap between the first frequency region of the FDRA and the second frequency region of the FDRA (e.g., because the BWPs do not intersect).

[0066] Some techniques and devices described herein provide disjoint resource indications for full-duplex operation. For example, a wireless node may receive an FDRA indicator that identifies the allocation of a set of RBGs for a plurality of resource block groups (RBGs) in a BWP arranged between disjoint portions of the BWP. The wireless node may identify the allocation of a set of RBGs based at least in part on the FDRA indicator, and may communicate using the allocation of the set of RBGs. In this way, the wireless node may communicate using disjoint BWPs in full-duplex in an unpaired spectrum. Therefore, spectral efficiency in unpaired bands may be improved, particularly in large cells and at the cell edge. In addition, delays may be reduced on unpaired bands relative to TDD configurations.

[0067] Figure 7 is a schematic diagram illustrating an example 700 of disjoint resource indication for full-duplex operation. Figure 7As shown in FIG. 7 , example 700 may include a first wireless node 702 and a second wireless node 704. The first wireless node 702 and the second wireless node 704 may be IAB wireless nodes, UEs, BSs, and the like.

[0068] As shown by reference numeral 710, the first wireless node 702 may receive a FDRA from the second wireless node 704. For example, the FDRA may be identified in a downlink control information (DCI) field. The DCI may be formatted according to a technical standard such as 3GPP TS 38.212 V15 (e.g., format 0_1 ​​for scheduling a physical uplink shared channel (PUSCH), format 1_0 for scheduling a physical downlink shared channel (PDSCH), etc.).

[0069] In some aspects, the FDRA received by the first wireless node 702 may include an FDRA indicator identifying an allocation of a set of RBGs in a plurality of RBGs in a BWP. Figure 7 As shown in FIG. 1 , the BWP may include a UL bandwidth and a DL bandwidth. In some aspects, the BWP may be a disjoint BWP such that the UL bandwidth and / or the DL bandwidth may be disjoint in the frequency domain. For example, Figure 7 As shown in , the DL bandwidths may be disjoint, such that the time interval of the BWP includes a first disjoint DL segment in a first frequency region between the first and second disjoint DL segments and a second disjoint DL segment in a second frequency region (e.g., such that the first frequency region and the second frequency region are separated by a frequency region associated with the UL segment). In some aspects, the disjoint DL bandwidths may include more than two disjoint DL segments. In some aspects, the UL bandwidths may be disjoint in a similar manner as described above. In some aspects, the disjoint BWPs may include disjoint DL bandwidths and disjoint UL bandwidths (e.g., having disjoint DL BWPs and disjoint UL BWPs). In some aspects, another type of resource allocation may be arranged in a frequency region of disjoint bandwidths separating the BWPs. For example, a BWP may include a pair of downlink bandwidths separated by a guard band or another type of resource allocation.

[0070] In some aspects, the FDRA indicator may include a bitmap that identifies the allocation of RBG sets in the BWP. Each bit of the bitmap may correspond to an RBG in a plurality of RBGs in the BWP. Each bit of the bitmap may identify whether the RBG associated with the bit is allocated in the FDRA. For example, if the bit is assigned a value of '0', the bit may identify that the RBG associated with the bit is not allocated. If the bit is assigned a value of '1', the bit may identify that the RBG associated with the bit is allocated.

[0071] For example, a BWP may include multiple RBGs (e.g., Figure 7, from 'a' to 'd'). The frequency range from 'a' to 'd' may be an activated BWP. The first wireless node 702 may identify the activated BWP (e.g., based on an indication received by the first wireless node 702, a configuration associated with the first wireless node 702, etc.). In some aspects, the first wireless node 702 may identify an activated bandwidth associated with a DL bandwidth and / or a UL bandwidth (e.g., the first wireless node 702 may identify the activated DL bandwidth as between 'a' and 'b' and between 'c' and 'd', but not between 'b' and 'c').

[0072] In some aspects, the size of the bitmap may correspond to the number of RBGs in an activated BWP (e.g., from 'a' to 'd'). For example, the bitmap may include one bit for each RBG in an activated BWP. For all bits that are not in an activated bandwidth associated with a DL bandwidth and / or a UL bandwidth, the bitmap may indicate a value of '0' (e.g., each bit between 'b' and 'c' may be assigned a value of '0', indicating that the RBG associated with the bits between 'b' and 'c' is not allocated in the BWP). For each bit in an activated bandwidth associated with a DL bandwidth and / or a UL bandwidth (e.g., each bit between 'a' and 'b' and each bit between 'c' and 'd' for a DL bandwidth), the bitmap indicates a value of '1' or '0' based at least in part on whether the RBG associated with the bit is allocated in the BWP.

[0073] In some aspects, the FDRA indicator may include a bitmap and a breakpoint identifier that divides the bitmap into a first bit subset of the bitmap and a second bit subset of the bitmap. The breakpoint identifier may be associated with an activation bandwidth associated with a DL bandwidth and / or a disjoint UL bandwidth. For example, the breakpoint identifier may indicate that each bit in the first bit subset of the bitmap corresponds to an RBG between 'a' and 'b', and the second bit subset of the bitmap corresponds to an RBG between 'c' and 'd'.

[0074] In some aspects, the size of the bitmap may correspond to the number of RGBs from 'a' to 'b' and the number of RGBs from 'c' to 'd'. In some aspects, the number of bits associated with the first disjoint segment of the BWP (e.g., from a' to 'b') may be different from the number of bits associated with the second disjoint segment of the BWP (e.g., from 'c' to 'd'). For example, the number of bits corresponding to the first disjoint segment of the BWP may be 10 bits. The number of bits corresponding to the second disjoint segment of the BWP may be 5 bits. Thus, in this case, the total size of the bitmap may be 15 bits. The breakpoint identifier may indicate to the first wireless node 702 that the first 10 bits of the bitmap correspond to the first disjoint segment of the BWP, while the remaining bits of the bitmap (e.g., the next 5 bits) correspond to the second disjoint segment of the BWP. In this way, the bitmap may not need to include bits corresponding to each RBG of the activated BWP (e.g., from 'a' to 'b').

[0075] In some aspects, the FDRA indicator may include a first bitmap identifying a first portion of an allocation of RBG sets corresponding to a first disjoint segment of the BWP (e.g., from 'a' to 'b'). The FDRA indicator may include a second bitmap identifying a second portion of an allocation of RBG sets corresponding to a second disjoint segment of the BWP (e.g., from 'c' to 'd'). In this case, the size of the first bitmap may correspond to the number of RBGs in the first disjoint segment, and the size of the second bitmap may correspond to the number of RBGs in the second disjoint segment. The size of the first bitmap and / or the second bitmap may depend on the size of the RBGs in each segment of the BWP (e.g., the first disjoint segment and the second disjoint segment), as described below.

[0076] In some aspects, the first wireless node 702 may determine a size associated with a plurality of RBGs in the BWP based at least in part on a size of the BWP and / or based at least in part on a stored BWP configuration. For example, the RBG size may be determined using a RBG size table (such as Table 5.1.2.2.1-1 of 3GPP TS 38.214 Version 15.3.0 Release 15). For example, the RBG size table may indicate a first BWP configuration and a second BWP configuration. The RBG size table may indicate that for a BWP size between 1 and 36 resource blocks (RBs), the RBG size is 2 RBs for the first BWP configuration and 4 RBs for the second BWP configuration. The number of RBGs in the BWP may be determined by dividing the size of the BWP by the number of RBs in each RBG. For example, for a BWP size of 1-36, the number of RBGs in the first BWP configuration is 18 RBGs (e.g., 36 divided by 2), and the number of RBGs in the second BWP configuration is 9 RBGs (e.g., 36 divided by 4). In this manner, the first wireless node 702 can determine the number of RBGs per BWP based at least in part on the size of the BWP and / or based at least in part on the BWP configuration. As described above, the size of the bitmap included in the FDRA indicator can correspond to the number of RBGs in the BWP (e.g., if the BWP includes 9 RBGs, the bitmap can include 9 bits).

[0077] In some aspects, the size of each of the multiple RBGs included in the BWP may be associated with a common size. For example, each RBG from 'a' to 'd' in the BWP may be the same size. In this case, the first wireless node 702 may determine the size of each RBG based at least in part on the size of one of the non-intersecting segments of the BWP. For example, the first wireless node 702 may determine the size of each RBG based at least in part on the size of the first non-intersecting segment of the BWP or the size of the second non-intersecting segment of the BWP in a similar manner as described above. Since each of the multiple RBGs included in the BWP may be associated with a common size, the size of the RBG in the first non-intersecting segment may be the same as the size of the RBG in the second non-intersecting segment. Therefore, the first wireless node 702 may determine the size of each RBG in the non-intersecting BWP based at least in part on the size of the first non-intersecting segment of the BWP or the size of the second non-intersecting segment of the BWP and / or at least in part on the BWP configuration using the RBG size table.

[0078] In some aspects, a first one or more resource block groups in the plurality of resource block groups are associated with a first size, and a second one or more resource block groups in the plurality of resource block groups are associated with a second size different from the first size. For example, RBGs included in a first disjoint segment of a BWP may be associated with the first size, while RBGs included in a second disjoint segment of the BWP may be associated with the second size.

[0079] In some aspects, the first wireless node 702 may determine the first size and the second size, respectively, in a manner similar to that described above. For example, the first wireless node 702 may determine the first size based at least in part on the size of the first non-intersecting segment of the BWP and / or based at least in part on the BWP configuration using an RBG size table. The first wireless node 702 may determine the second size based at least in part on the size of the second non-intersecting segment of the BWP and / or based at least in part on the BWP configuration using an RBG size table as described above.

[0080] In some aspects, the first wireless node 702 may determine the first size and the second size based at least in part on the modified RBG size table. The modified RBG size table may include configurations of non-full-duplex operation or non-disjoint BWP operation configurations (e.g., first BWP configurations and second BWP configurations) and one or more full-duplex operation or disjoint bandwidth portion operation configurations (e.g., new BWP configurations). The first wireless node 702 may determine the first size and the second size based at least in part on the modified RBG size table in a similar manner as described above.

[0081] In some aspects, the first wireless node 702 may determine the first size and the second size based at least in part on a new RBG size table. The new RBG size table may include one or more full-duplex operation or disjoint bandwidth portion operation configurations (e.g., new BWP configurations). The new RBG size table may not include BWP configurations that are not full-duplex operation or non-disjoint BWP operation configurations (e.g., first BWP configurations and second BWP configurations). The first wireless node 702 may determine the first size and the second size based at least in part on the new RBG size table in a similar manner as described above.

[0082] In this way, the first wireless node 702 can identify the size of the bitmap associated with the disjoint BWP because the number of RBGs in each segment of the disjoint BWP can correspond to the number of bits in the bitmap. For example, if the first wireless node 702 determines that there are 18 RBGs in a first disjoint segment of the BWP, the first wireless node 702 can identify that 18 bits of the bitmap can be associated with the first disjoint segment of the BWP. Similarly, if the first wireless node 702 determines that there are 9 RBGs in a second disjoint segment of the BWP, the first wireless node 702 can identify that 9 bits of the bitmap can be associated with the second disjoint segment of the BWP.

[0083] In some aspects, the FDRA indicator may include at least one of a start indicator or a length indicator identifying an allocation of a set of resource block groups. The start indicator may indicate a first RBG included in the allocation, and the length indicator may indicate the number of RBGs included in the allocation. In some aspects, the length indicator may indicate the number of consecutive RBGs (e.g., indicated by the start indicator) included in the allocation after the first RBG. In some aspects, the start indicator and the length indicator may be combined into a resource indicator value. The FDRA indicator may include one or more resource indicator values.

[0084] In some aspects, the FDRA indicator may include a first resource indicator value and a second resource indicator value. The first resource indicator value may identify a first start indicator and a first length indicator associated with a first disjoint segment of the BWP. The second resource indicator value may indicate a second start indicator and a second length indicator associated with a second disjoint segment of the BWP. Thus, the first resource indicator value may indicate one or more allocated RBGs in the first disjoint segment of the BWP, and the second resource indicator value may indicate one or more allocated RBGs in the second disjoint segment of the BWP.

[0085] In some aspects, the FDRA indicator may include a resource indicator value (e.g., indicating a start indicator and a length indicator). In some aspects, the start of the allocated RBG set (e.g., indicated by the start indicator) and the end of the allocated RBG set (e.g., indicated by the length indicator) may be in the same non-intersecting segment of the BWP (e.g., the start and end of the allocated RBG set may both be in a first non-intersecting segment of the BWP, or the start and end of the allocated RBG set may both be in a second non-intersecting segment of the BWP). In this case, the allocated RBG set may be contiguous from the start indicated by the start indicator to the end indicated by the length indicator.

[0086] In some aspects, the start of the allocated RBG set (e.g., indicated by the start indicator) and the end of the allocated RBG set (e.g., indicated by the length indicator) may be in different non-intersecting segments of the BWP (e.g., the start of the allocated RBG set may be in a first non-intersecting segment of the BWP, and the end of the allocated RBG set may be in a second non-intersecting segment of the BWP). In this case, the allocated RBG set may include a first subset of the allocated RBG set from the start indicated by the start indicator to the end of the first non-intersecting segment of the BWP (e.g., from the start to 'b'). The allocated RBG set may include a second subset of the allocated RBG set from the start of the second non-intersecting segment of the BWP to the end indicated by the length indicator (e.g., from 'c' to the end).

[0087] In some aspects, the FDRA indicator may include a start indicator (e.g., indicating the start of the allocated RBG set) and an end indicator (e.g., indicating the end of the allocated RBG set). The start indicator and the end indicator may indicate that all RBGs between the start and the end are allocated RBGs. In some aspects, the allocated RBG sets (e.g., indicated by the start indicator and the end indicator) may be in different disjoint segments of the BWP in a similar manner as described above.

[0088] In some aspects, the FDRA indicator may include an end indicator (e.g., indicating the end of the allocated RBG set) and a length indicator (e.g., indicating the number of consecutive RBGs included in the allocation before the last RBG (e.g., indicated by the end indicator)). In some aspects, the allocated RBG sets (e.g., indicated by the end indicator and the length indicator) may be in different disjoint segments of the BWP in a similar manner as described above.

[0089] like Figure 7 As indicated by reference numeral 720, the first wireless node 702 may identify the allocated RBG set based at least in part on the FDRA indicator. For example, the first wireless node 702 may identify the allocated RBG set based at least in part on one or more bitmaps. In some aspects, the first wireless node 702 may identify the allocated RBG set based at least in part on a start indicator and a length indicator of the allocated RBG set.

[0090] As shown by reference numeral 730, the first wireless node 702 can receive on the downlink using the allocated RGB set. In some aspects, disjoint BWPs can be associated with uplinks. In this case, the first wireless node 702 can transmit on the uplink using the allocated RGB set.

[0091] In this way, the first wireless node 720 can communicate in the unpaired spectrum using disjoint BWPs in full duplex. Therefore, the spectrum efficiency in the unpaired band can be improved, especially in large cells and at the cell edge. In addition, relative to the TDD configuration, delay can be reduced on the unpaired band.

[0092] As mentioned above, providing Figure 7 As an example. Other examples can be related to Figure 7 The description is different.

[0093] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a wireless node in accordance with the present disclosure. The example process 800 is an example of a wireless node (eg, the first wireless node 702, the second wireless node 704, etc.) performing operations associated with disjoint resource indication for full-duplex operation.

[0094] like Figure 8 As shown, in some aspects, process 800 may include receiving a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups of a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion (block 810). For example, as described above, a wireless node (e.g., using antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups of a plurality of resource block groups in a bandwidth portion. In some aspects, the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion.

[0095] like Figure 8 As also shown in FIG. 8 , in some aspects, process 800 may include identifying an allocation of a set of resource block groups based at least in part on the frequency-domain resource assignment indicator (block 820). For example, as described above, the wireless node (e.g., using controller / processor 240, controller / processor 280, etc.) may identify an allocation of a set of resource block groups based at least in part on the frequency-domain resource assignment indicator.

[0096] like Figure 8As also shown in FIG. 8 , in some aspects, process 800 may include communicating using an allocation of a set of resource block groups based at least in part on identifying an allocation of a set of resource block groups (block 830). For example, as described above, a wireless node (e.g., using antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, transmit processor 264, TX MIMO processor 266, modulator 254, etc.) may communicate using an allocation of resource block groups based at least in part on identifying an allocation of resource block groups.

[0097] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0098] In a first aspect, the bandwidth portion includes an uplink bandwidth and a downlink bandwidth.

[0099] In a second aspect, alone or in combination with the first aspect, the frequency domain resource allocation indicator comprises a bitmap identifying an allocation of a set of resource block groups.

[0100] In a third aspect, alone or in combination with one or more of the first and second aspects, each bit of the bitmap corresponds to a resource block group of the plurality of resource block groups.

[0101] In a fourth aspect, alone or in combination with one or more aspects of the first to third aspects, the frequency domain resource allocation indicator includes a breakpoint identifier that divides the bitmap into a first bit subset of the bitmap and a second bit subset of the bitmap, and the first bit subset corresponds to a first subset of multiple resource block groups in a first non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and the second bit subset of the bitmap corresponds to a second subset of multiple resource block groups in a second non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth.

[0102] In a fifth aspect, either alone or in combination with one or more aspects of the first to fourth aspects, the frequency domain resource allocation indicator comprises a first bitmap identifying a first portion of an allocation of a set of resource block groups in a first non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth, and a second bitmap identifying a second portion of an allocation of a set of resource block groups in a second non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth.

[0103] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, each resource block group in the plurality of resource block groups is associated with a common size.

[0104] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 800 includes determining a common size based at least in part on a size of a first non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth or a size of a second non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth.

[0105] In an eighth aspect, either alone or in combination with one or more aspects of the first to seventh aspects, a first one or more resource block groups among the plurality of resource block groups are associated with a first size, and a second one or more resource block groups among the plurality of resource block groups are associated with a second size different from the first size.

[0106] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 800 includes determining at least one of the first size or the second size based at least in part on a resource block group size table.

[0107] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 800 includes determining at least one of the first size or the second size based at least in part on at least one stored bandwidth portion configuration.

[0108] In an eleventh aspect, alone or in combination with one or more aspects of the first to tenth aspects, process 800 includes: determining at least one of the first size or the second size based at least in part on a resource block group size table including non-full-duplex operation or non-disjoint bandwidth portion operation configurations and full-duplex operation or disjoint bandwidth portion operation configurations.

[0109] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, process 800 includes determining at least one of the first size or the second size based at least in part on a resource block group size table that includes full-duplex operation or non-disjoint bandwidth portion operation configurations rather than non-full-duplex operation or non-disjoint bandwidth portion operation configurations.

[0110] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the frequency domain resource allocation indicator comprises at least one of a start indicator or a length indicator identifying an allocation of a set of resource block groups.

[0111] In a fourteenth aspect, alone or in combination with one or more aspects of the first to thirteenth aspects, wherein the start indicator indicates that the start of the resource block group set is in a first non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and the length indicator indicates that the end of the resource block group set is in a second non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and the resource block group set includes a first subset of the resource block group set from the start indicated by the start indicator to the end of the first non-intersecting part, and a second subset of the resource block group set from the start of the second non-intersecting part to the end indicated by the length indicator.

[0112] In the fifteenth aspect, alone or in combination with one or more aspects of the first to fourteenth aspects, the start of the set of resource block groups indicated by the start indicator and the end of the set of resource block groups indicated by the length indicator are both in one of a first non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth or a second non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and the set of resource block groups is continuous from the start indicated by the start indicator to the end indicated by the length indicator.

[0113] Although Figure 8 Example blocks of process 800 are shown, but in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or different Figure 8 Those blocks shown are arranged differently. Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.

[0114] Fig. 9 900 is a block diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a wireless node, or a wireless node may include apparatus 900. In some aspects, apparatus 900 may include a receiving component 902 and a transmitting component 904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As also shown, apparatus 900 may include one or more of identifying component 908 or determining component 910, etc.

[0115] In some aspects, the apparatus 900 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 900 and / or Fig. 9 One or more components shown may include the above combined Figure 2One or more components of the UE or BS described. Additionally or alternatively, Fig. 9 One or more of the components shown above may be combined Figure 2 In some embodiments, the present invention may be implemented in one or more components described in the present invention. Additionally or alternatively, one or more components of the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0116] The receiving component 902 may receive communications such as reference signals, control information, data communications, or combinations thereof from the apparatus 906. The receiving component 902 may provide the received communications to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 906. In some aspects, the receiving component 902 may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a UE or BS are described.

[0117] The transmitting component 904 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 906. In some aspects, one or more other components of the device 906 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include the above in combination with Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE or BS. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0118] The receiving component 902 can receive a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups of a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion. The identifying component 908 can identify the allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator. The receiving component 902 or the transmitting component 904 can communicate using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0119] Determining component 910 can determine the common size based at least in part on a size of a first disjoint portion of the other of the uplink bandwidth or the downlink bandwidth or a size of a second disjoint portion of the other of the uplink bandwidth or the downlink bandwidth.

[0120] Determining component 910 can determine at least one of the first size or the second size based at least in part on a resource block group size table.

[0121] Determining component 910 can determine at least one of the first size or the second size based at least in part on at least one stored bandwidth portion configuration.

[0122] Determining component 910 can determine at least one of the first size or the second size based at least in part on a resource block group size table including non-full duplex operation or non-disjoint bandwidth portion operation configurations and full duplex operation or disjoint bandwidth portion operation configurations.

[0123] Determining component 910 can determine at least one of the first size or the second size based at least in part on a resource block group size table including full duplex operation or disjoint bandwidth portion operation configurations but not non-full duplex operation or non-disjoint bandwidth portion operation configurations.

[0124] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be additional components, fewer components, different components, or different components. Fig. 9 The components shown are arranged differently. Fig. 9 Two or more of the components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The component collection (one or more) shown may perform the operations described as being performed by Fig. 9 One or more functions performed by another component collection shown in .

[0125] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0126] The following provides an overview of some aspects of the disclosure:

[0127] Aspect 1: A wireless communication method performed by a wireless node, comprising: receiving a frequency domain resource allocation indicator that identifies an allocation of a set of resource block groups among multiple resource block groups in a bandwidth portion, wherein the bandwidth portion includes multiple non-intersecting portions of the bandwidth portion, and the multiple non-intersecting portions include uplink bandwidth or downlink bandwidth separated by another portion of the bandwidth portion; identifying the allocation of the set of resource block groups based at least in part on the frequency domain resource allocation indicator; and communicating using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

[0128] Aspect 2: The method according to aspect 1, wherein the bandwidth part includes an uplink bandwidth and a downlink bandwidth.

[0129] Aspect 3: The method according to any one of aspects 1 to 2, wherein the frequency domain resource allocation indicator comprises a bitmap identifying allocation of resource block group sets.

[0130] Aspect 4: The method according to aspect 3, wherein each bit of the bitmap corresponds to a resource block group in the plurality of resource block groups.

[0131] Aspect 5: A method according to any one of Aspects 3 to 4, wherein the frequency domain resource allocation indicator includes a breakpoint identifier that divides the bitmap into a first bit subset of the bitmap and a second bit subset of the bitmap, and wherein the first bit subset corresponds to a first subset of multiple resource block groups in a first non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and the second bit subset of the bitmap corresponds to a second subset of multiple resource block groups in a second non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth.

[0132] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the frequency domain resource allocation indicator includes a first bitmap identifying a first part of the allocation of a set of resource block groups in a first non-intersecting part of the other in the uplink bandwidth or the downlink bandwidth, and a second bitmap identifying a second part of the allocation of a set of resource block groups in a second non-intersecting part of the other in the uplink bandwidth or the downlink bandwidth.

[0133] Aspect 7: The method according to any one of aspects 1 to 6, wherein each resource block group in the plurality of resource block groups is associated with a common size.

[0134] Aspect 8: The method according to Aspect 7 also includes: determining the common size based at least in part on the size of a first non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth or the size of a second non-intersecting portion of the other of the uplink bandwidth or the downlink bandwidth.

[0135] Aspect 9: A method according to any one of Aspects 1 to 8, wherein a first one or more resource block groups among the plurality of resource block groups are associated with a first size, and a second one or more resource block groups among the plurality of resource block groups are associated with a second size different from the first size.

[0136] Aspect 10: The method according to aspect 9, further comprising: determining at least one of the first size or the second size based at least in part on a resource block group size table.

[0137] Aspect 11: The method according to any one of aspects 9 to 10 further comprises: determining at least one of the first size or the second size based at least in part on at least one stored bandwidth portion configuration.

[0138] Aspect 12: The method according to any one of Aspects 9 to 11 further includes: determining at least one of the first size or the second size based at least in part on a resource block group size table including non-full-duplex operation or non-non-intersecting bandwidth portion operation configurations and full-duplex operation or non-non-intersecting bandwidth portion operation configurations.

[0139] Aspect 13: The method according to any one of Aspects 9 to 12 further includes: determining at least one of the first size or the second size based at least in part on a resource block group size table including full-duplex operation or non-disjoint bandwidth portion operation configuration rather than non-full-duplex operation or non-disjoint bandwidth portion operation configuration.

[0140] Aspect 14: The method according to any one of aspects 1 to 13, wherein the frequency domain resource allocation indicator comprises at least one of a start indicator or a length indicator identifying an allocation of a set of resource block groups.

[0141] Aspect 15: A method according to Aspect 14, wherein a start indicator indicates that the start of a resource block group set is in a first non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and a length indicator indicates that the end of a resource block group set is in a second non-intersecting part of the other of the uplink bandwidth or the downlink bandwidth, and wherein the resource block group set includes a first subset of the resource block group set from the start indicated by the start indicator to the end of the first non-intersecting part, and a second subset of the resource block group set from the start of the second non-intersecting part to the end indicated by the length indicator.

[0142] Aspect 16: A method according to any one of Aspects 14 to 15, wherein the start of a set of resource block groups indicated by a start indicator and the end of a set of resource block groups indicated by a length indicator are both located in one of a first non-intersecting part of the other of an uplink bandwidth or a downlink bandwidth or a second non-intersecting part of the other of an uplink bandwidth or a downlink bandwidth; and wherein the set of resource block groups is continuous from the start indicated by the start indicator to the end indicated by the length indicator.

[0143] Aspect 17: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, so that the apparatus performs one or more methods of aspects 1 to 16.

[0144] Aspect 18: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to execute the method of one or more aspects of Aspect 1 to Aspect 16.

[0145] Aspect 19: An apparatus for wireless communication, comprising at least one component for performing the method of one or more aspects of Aspect 1 to Aspect 16.

[0146] Aspect 20: A non-transitory computer-readable medium storing a code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 1 to 16.

[0147] Aspect 21: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of Aspect 1-Aspect 16.

[0148] As used herein, the term "component" is intended to be interpreted broadly as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other, "software" should be interpreted broadly as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes and / or functions, etc. As used herein, the processor is implemented in hardware and / or a combination of hardware and software. Obviously, the system and / or method described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware and / or software code used to implement these systems or methods does not limit these aspects. Therefore, the operation and behavior of the system and / or method are described herein without reference to specific software codes-it can be understood that software and hardware can be designed to implement a system and / or method based at least in part on the description of this article.

[0149] As used herein, satisfying a threshold may mean greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0150] Although specific combinations of features are listed in the claims and / or specific combinations of features are disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can directly rely on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one" referring to the list of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, ccc or any other order of a, b and c).

[0151] Unless explicitly described in this way, any element, behavior or instruction used in this article is not interpreted as key or necessary. Moreover, as used herein, the articles "a" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more quoted items associated with the article "the", and can be used interchangeably with "one or more (the one or more)". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects (for example, related items, unrelated items or a combination of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only intended to a project, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "has", "have", "having" etc. are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to represent "based at least in part". Furthermore, as used herein, the term "or" when used in series is intended to be inclusive and can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in combination with "either" or "only one of").

Claims

1. A method of wireless communication performed by a wireless node, comprising: receiving a frequency domain resource allocation indicator identifying an allocation of a set of resource block groups among a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion is a full-duplex bandwidth portion including an uplink bandwidth and a downlink bandwidth, the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include an uplink bandwidth or a downlink bandwidth separated by another portion of the bandwidth portion; identifying an activated bandwidth associated with the spaced uplink bandwidth or the spaced downlink bandwidth; identifying an allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and Based at least in part on identifying the allocation for the set of resource block groups, communicating using the allocation for the set of resource block groups.

2. The method according to claim 1, wherein: The frequency domain resource assignment indicator comprises a bitmap identifying the allocation of the set of resource block groups.

3. The method according to claim 2, wherein: Each bit of the bitmap corresponds to a resource block group among the plurality of resource block groups.

4. The method according to claim 2, wherein: The frequency domain resource allocation indicator includes a breakpoint identifier that divides the bitmap into a first bit subset of the bitmap and a second bit subset of the bitmap, and wherein the first bit subset corresponds to a first subset of the plurality of resource block groups in a first non-intersecting portion of the activation bandwidth, and the second bit subset of the bitmap corresponds to a second subset of the plurality of resource block groups in a second non-intersecting portion of the activation bandwidth.

5. The method according to claim 1, wherein: The frequency domain resource allocation indicator comprises a first bitmap identifying a first portion of the allocation of the set of resource block groups in a first non-intersecting portion of the activation bandwidth, and a second bitmap identifying a second portion of the allocation of the set of resource block groups in a second non-intersecting portion of the activation bandwidth.

6. The method according to claim 1, wherein: Each resource block group of the plurality of resource block groups is associated with a common size.

7. The method according to claim 6, further comprising: The common size is determined based at least in part on a size of a first non-intersecting portion of the activation bandwidth or a size of a second non-intersecting portion of the activation bandwidth.

8. The method according to claim 1, wherein: A first one or more resource block groups of the plurality of resource block groups are associated with a first size, and a second one or more resource block groups of the plurality of resource block groups are associated with a second size different than the first size.

9. The method according to claim 8, further comprising: At least one of the first size or the second size is determined based at least in part on a resource block group size table.

10. The method according to claim 8, further comprising: At least one of the first size or the second size is determined based at least in part on at least one stored bandwidth portion configuration.

11. The method according to claim 8, further comprising: At least one of the first size or the second size is determined based at least in part on a resource block group size table including non-full-duplex operation or non-disjoint bandwidth portion operation configurations and full-duplex operation or disjoint bandwidth portion operation configurations.

12. The method according to claim 8, further comprising: At least one of the first size or the second size is determined based at least in part on a resource block group size table including full-duplex operation or disjoint bandwidth portion operation configurations but not non-full-duplex operation or non-disjoint bandwidth portion operation configurations.

13. The method according to claim 1, wherein: The frequency domain resource assignment indicator comprises at least one of a start indicator or a length indicator identifying the allocation of the set of resource block groups.

14. The method according to claim 13, wherein: The start indicator indicates that the start of the set of resource block groups is in a first disjoint portion of the activation bandwidth, and the length indicator indicates that the end of the set of resource block groups is in a second disjoint portion of the activation bandwidth, and The resource block group set includes a first subset of the resource block group set from the start indicated by the start indicator to the end of the first non-intersecting part, and a second subset of the resource block group set from the start of the second non-intersecting part to the end indicated by the length indicator.

15. The method according to claim 13, wherein: a start of the set of resource block groups indicated by the start indicator and an end of the set of resource block groups indicated by the length indicator are both in one of a first disjoint portion of the activation bandwidth or a second disjoint portion of the activation bandwidth; as well as The resource block group set is continuous from the start indicated by the start indicator to the end indicated by the length indicator.

16. A wireless node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: receiving a frequency domain resource allocation indicator identifying an allocation of a set of resource block groups among a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion is a full-duplex bandwidth portion including an uplink bandwidth and a downlink bandwidth, the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include an uplink bandwidth or a downlink bandwidth separated by another portion of the bandwidth portion; identifying an activated bandwidth associated with the spaced uplink bandwidth or the spaced downlink bandwidth; identifying an allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and Based at least in part on identifying the allocation for the set of resource block groups, communicating using the allocation for the set of resource block groups.

17. The wireless node of claim 16, wherein: The frequency domain resource assignment indicator comprises a bitmap identifying the allocation of the set of resource block groups.

18. The wireless node of claim 17, wherein: Each bit of the bitmap corresponds to a resource block group among the plurality of resource block groups.

19. The wireless node of claim 17, wherein: The frequency domain resource allocation indicator includes a breakpoint identifier that divides the bitmap into a first bit subset of the bitmap and a second bit subset of the bitmap, and wherein the first bit subset corresponds to a first subset of the plurality of resource block groups in a first non-intersecting portion of the activation bandwidth, and the second bit subset of the bitmap corresponds to a second subset of the plurality of resource block groups in a second non-intersecting portion of the activation bandwidth.

20. The wireless node of claim 16, wherein: The frequency domain resource allocation indicator comprises a first bitmap identifying a first portion of the allocation of the set of resource block groups in a first non-intersecting portion of the activation bandwidth, and a second bitmap identifying a second portion of the allocation of the set of resource block groups in a second non-intersecting portion of the activation bandwidth.

21. The wireless node of claim 16, wherein: Each resource block group of the plurality of resource block groups is associated with a common size.

22. The wireless node of claim 21, wherein: The one or more processors are further configured to: The common size is determined based at least in part on a size of a first non-intersecting portion of the activation bandwidth or a size of a second non-intersecting portion of the activation bandwidth.

23. The wireless node of claim 16, wherein: A first one or more resource block groups of the plurality of resource block groups are associated with a first size, and a second one or more resource block groups of the plurality of resource block groups are associated with a second size different than the first size.

24. The wireless node of claim 23, wherein: The one or more processors are further configured to: At least one of the first size or the second size is determined based at least in part on a resource block group size table.

25. The wireless node of claim 23, wherein: The one or more processors are further configured to: At least one of the first size or the second size is determined based at least in part on at least one stored bandwidth portion configuration.

26. The wireless node of claim 23, wherein: The one or more processors are further configured to: At least one of the first size or the second size is determined based at least in part on a resource block group size table including non-full-duplex operation or non-disjoint bandwidth portion operation configurations and full-duplex operation or disjoint bandwidth portion operation configurations.

27. A non-transitory computer readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a wireless node, cause the wireless node to: receiving a frequency domain resource allocation indicator identifying an allocation of a set of resource block groups among a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion is a full-duplex bandwidth portion including an uplink bandwidth and a downlink bandwidth, the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include an uplink bandwidth or a downlink bandwidth separated by another portion of the bandwidth portion; identifying an activated bandwidth associated with the spaced uplink bandwidth or the spaced downlink bandwidth; identifying an allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and Based at least in part on identifying the allocation for the set of resource block groups, communicating using the allocation for the set of resource block groups.

28. An apparatus for wireless communication, comprising: means for receiving a frequency domain resource assignment indicator identifying an allocation of a set of resource block groups among a plurality of resource block groups in a bandwidth portion, wherein the bandwidth portion is a full-duplex bandwidth portion including an uplink bandwidth and a downlink bandwidth, the bandwidth portion includes a plurality of disjoint portions of the bandwidth portion, and the plurality of disjoint portions include an uplink bandwidth or a downlink bandwidth separated by another portion of the bandwidth portion; means for identifying an activated bandwidth associated with said spaced uplink bandwidth or said spaced downlink bandwidth; means for identifying an allocation of the set of resource block groups based at least in part on the frequency domain resource assignment indicator; and Means for communicating using the allocation of the set of resource block groups based at least in part on identifying the allocation of the set of resource block groups.

Images