Patent Description:
<CIT> provides a system and method for transmitting control information. A method for communications controller operations includes combining control data for each relay node of at least one relay node into a control channel data stream, mapping a plurality of transmission resources for the control channel data stream into a plurality of physical resource blocks using a distributed virtual resource mapping rule, and transmitting the plurality of physical resource blocks to the set of at least one relay node. The plurality of transmission resources are mapped to physical resource blocks that are non-contiguous in a frequency domain.

<CIT> relates to methods and apparatus mapping virtual resource blocks (VRBs) to physical resource blocks (PRBs) and using the mapping in wireless communications, for example, in new radio (NR) technologies. An exemplary method includes determining a first interleaved mapping that maps a first interleaving unit of N consecutive first virtual resource blocks (VRBs) to N consecutive first physical resource blocks (PRBs), wherein each first PRB comprises a set of frequency resources during a period, transmitting a first grant allocating the first interleaving unit of first VRBs to a first user equipment (UE), and communicating with the first UE via the first PRBs mapped to the first VRBs of the first interleaving unit.

<NPL>", provides several proposals regarding DVRB issues.

<NPL>, discusses frequency-domain resource allocation, time-domain resource allocation, and TBS determination.

The scope of protection of the present invention is defined by the independent claims.

A problem associated with frequency division duplex (FDD) or full duplex communication is self-interference, particularly with respect to sub-band full duplex (SBFD) communications. Resource allocations for SBFD communications may be implemented via a frequency domain resource allocation (FDRA), which may be identified in a downlink control information (DCI) field. The FDRA may identify frequency resource explicitly via a bitmap (Type o) or via reference to a range of RBs (Type <NUM>).

For Type o allocation, in some aspects, each bit of the bit map may correspond to an RB group (RGB) of a plurality of RBGs in the BWP. However, if there is a relatively large gap between the first and second disjoint BWP DL segments (e.g., sub-BWP segments), the bitmap indication may become unpractical due to inefficiency.

For Type <NUM> allocation, consecutive (or contiguous) RBs are identified in association with a resource indicator value (RIV) via designation of a startpoint (RBstart) and a size (or length) indicator. Because Type <NUM> allocation identifies a BWP segment via start and length indicators in terms of RIV, it is difficult to use Type <NUM> allocation to reference disjoint BWP segments for SBFD. In particular, attempting to use Type <NUM> allocation to span across both disjoint BWP segments (e.g., DL BWP segments) will cause the indicated BWP to include the intervening BWP segment (e.g., UL BWP segment). Alternatively, each disjoint BWP segment can be identified via its own RIV and its own separate start and length indicators, which may increase overhead and complexity.

Further, at the gNB scheduler, a first virtual RB (VRB) group may be associated with a first disjoint BWP segment, while a virtual VRB group may be associated with a second disjoint BWP segment. VRB groups are typically mapped to physical RBs (PRBs) in accordance with a VRB-to-PRB mapping rule for one particular set of contiguous PRBs, and not multiple disjointed sets of PRBs (or BWP segments) which occur with respect to SBFD slots as noted above.

Aspects of the present disclosure are directed to an allocation of VRB groups to PRB across disjoint BWP segments based upon one or more VRB-to-PRB mapping rules for an SBFD slot. The aspects describe below provide various technical advantages, such as leveraging SBFD so as to provide Rx-WOLA to reduce ACLR leakage to the UL signal, analog LPF to improve ADC dynamic range, Rx-AGC states to improve the NF, and so on.

In an aspect of the disclosure, a method, a computer-readable medium, a computer program and an apparatus are provided. The apparatus may be a wireless node, such as a UE or a BS. The wireless node may perform the method as defined in claim <NUM>.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, cIoT user equipment, base station, wireless communication device, and/or processing system as substantially described with reference to and as illustrated by the drawings, and specification.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with disjoint resource indication for full-duplex operation, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, interpreting, and/or the like) by one or more processors of the base station <NUM> and/or the UE <NUM>, may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, interpreting the instructions, and/or the like.

<FIG> are diagrams illustrating one or more examples of full-duplex operation modes, in accordance with various aspects of the present disclosure. A user equipment (UE) and a base station (BS) may communicate with each other using beams. For example, a beam may be a downlink beam (e.g., on which information may be conveyed from the BS to the UE) or an uplink beam (e. g, on which information may be conveyed from the UE to the BS). In some aspects, the UE and the BS may be integrated access backhaul (IAB) wireless nodes.

A communication link between a UE and a BS may be referred to as half-duplex when the communication link includes only one of an uplink or a downlink or full-duplex when the communication link includes an uplink and a downlink. A full-duplex communication link may provide increased scalability of data rates on the link in comparison to a half-duplex communication link. In a full-duplex communication link, different antenna elements, sub-arrays, or antenna panels of a wireless communication device may simultaneously or contemporaneously perform uplink and downlink communication.

Full-duplex communication may present certain challenges in comparison to half-duplex communication. For example, a wireless communication device (e.g., a UE, a BA, and/or a wireless node) may experience self-interference between an uplink beam and a downlink beam of a full-duplex link or between components of the wireless communication device. This self-interference may complicate the monitoring of reference signals to detect beam failure. Furthermore, self-interference, cross-correlation, and/or the like, may occur in a full-duplex communication link that may not occur in a half-duplex communication link. Additionally, a wireless communication device may experience interfering transmissions from other wireless communication devices (e.g., based at least in part on an angular spread of a beam transmitted by the other wireless communication devices) in the wireless network that may cause a beam failure (e.g., an uplink beam failure, a downlink beam failure, and/or the like).

As shown in <FIG>, an example wireless network <NUM> includes a BS <NUM>-<NUM> operating in a full-duplex operation mode. The BS <NUM>-<NUM> may receive an uplink from a UE <NUM>-<NUM> and transmit a downlink to a UE <NUM>-<NUM>. The UE-<NUM>-<NUM> and the UE <NUM>-<NUM> may be operating in a half-duplex operation mode. The BS <NUM>-<NUM> may experience downlink to uplink self-interference based at least in part on the downlink transmitted to UE <NUM>-<NUM> and the uplink received from UE <NUM>-<NUM>. Additionally, BS <NUM>-<NUM> may experience interfering transmissions from other wireless communication devices transmitting in the wireless network <NUM> (e.g., from a BS <NUM>-<NUM>). Moreover, UE <NUM>-<NUM> interfering transmissions from other wireless communication devices transmitting in the wireless network <NUM> (e.g., from the UE <NUM>-<NUM>, from the BS <NUM>-<NUM>, and/or the like).

As shown in <FIG>, an example wireless network <NUM> includes a UE <NUM>-<NUM> operating in a full-duplex operation mode. The UE <NUM>-<NUM> may transmit an uplink to a BS <NUM>-<NUM> and may receive a downlink from the BS <NUM>-<NUM>. In some aspects, the BS <NUM>-<NUM> may be operating in a full-duplex operation mode. The UE <NUM>-<NUM> may experience uplink to downlink self-interreference based at least in part on the uplink transmitted to the BS <NUM>-<NUM> and the downlink received from the BS <NUM>-<NUM>. The wireless network <NUM> may include other wireless communication devices, such as a BS <NUM>-<NUM> and a UE <NUM>-<NUM>. The BS <NUM>-<NUM> may transmit a downlink to the UE-<NUM>-<NUM>. The UE <NUM>-<NUM> may experience an interfering transmission based at least in part on the transmission of the BS <NUM>-<NUM> and/or the UE <NUM>-<NUM>. For example, the downlink transmitted by the BS <NUM>-<NUM> may have an angular spread that may cause an interfering transmission to be received by the UE <NUM>-<NUM>. Similarly, an uplink transmitted by the UE <NUM>-<NUM> may have an angular spread that may cause an interfering transmission to be received by the UE <NUM>-<NUM>.

As shown in <FIG>, an example wireless network <NUM> includes a UE <NUM>-<NUM> operating in a full-duplex operation mode. The UE <NUM>-<NUM> may transmit an uplink to a BS <NUM>-<NUM> and may receive a downlink from a BS <NUM>-<NUM>. The UE <NUM>-<NUM> may include a multi transmission and reception (multi-TRP) architecture. The UE <NUM>-<NUM> may experience uplink to downlink self-interreference based at least in part on the uplink transmitted to the BS <NUM>-<NUM> and the downlink received from the BS <NUM>-<NUM>. The BS <NUM>-<NUM> and the BS <NUM>-<NUM> may be operating in a half-duplex mode of operation. The BS <NUM>-<NUM> may transmit a downlink to a UE <NUM>-<NUM>. In some aspects, the UE <NUM>-<NUM> may experience one or more interfering transmissions based at least in part on the transmissions of BS <NUM>-<NUM>, BS <NUM>-<NUM>, and/or UE <NUM>-<NUM>.

<FIG> is a diagram illustrating one or more examples <NUM> of full-duplex types, in accordance with various aspects of the present disclosure. As described above, full-duplex operation may involve communications having both an uplink (UL) and a downlink (DL) at the same time (e.g., transmit and receive at the same time). The uplink and downlink may share resources (e.g., time resources and/or frequency resources) associated with the communications.

As shown in <FIG>, a full-duplex communication may be an in-band full duplex (IBFD) mode (e.g., a mode that includes an uplink and a downlink that share the same time resources and/or frequency resources). In some aspects, an IBFD mode may be a full overlap IBFD mode, such that the downlink resources may completely overlap the uplink resources (e.g., all of the uplink resources are shared with the downlink resources). In some aspects, a full overlap IBFD mode may have uplink resources that completely overlap the downlink resources. In some aspects, an IBFD communication may be a partial overlap IBFD mode, such that the downlink resources do not completely overlap the uplink resources (e.g., only some of the uplink resources are shared with the downlink resources).

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

A wireless communication standard or governing body may specify how a wireless spectrum is to be used. For example, 3GPP may specify how wireless spectrum is to be used for the <NUM>/NR radio access technology and interface. As an example, a specification may indicate whether a band is to be used as paired spectrum or unpaired spectrum. A band in a paired spectrum may use a first frequency region for uplink communication and a second frequency region for downlink communication, where the first frequency region does not overlap the second frequency region. For example, a paired band may have an uplink operating band and a downlink operating band that are configured to use non-overlapped frequency regions. Some deployments may use frequency division duplexing (FDD) in the paired bands. Examples of paired bands in NR include NR operating bands n1, n2, n3, n5, n7, n8, n12, n20, n25, and n28, as specified by 3GPP Technical Specification (TS) <NUM>-<NUM>.

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

In some cases, it may be inefficient to use TDD in an unpaired spectrum. For example, uplink transmit power may be limited, meaning that UEs may not be capable of transmitting with enough power to efficiently utilize the full bandwidth of an uplink slot. This may be particularly problematic in large cells at the cell edge. Furthermore, the usage of TDD may introduce latency relative to a scheme in which uplink communications and downlink communications can be performed in the same time interval, since a given time interval may be used for only uplink communication or for only downlink communication using TDD. However, frequency domain resource assignment (FDRA) for a bandwidth part (BWP) in the case of FDD in an unpaired spectrum may be problematic due to a gap between a first frequency region of the FDRA and a second frequency region of the FDRA (e.g., due to the BWP being disjointed).

<FIG> illustrates a top-perspective 700A and a side-perspective 700B of a panel architecture for a full duplex gNB in accordance with an aspect of the disclosure. The panel architecture depicted in <FIG> which comprises Panels #<NUM> and #<NUM> that may support simultaneous Tx and Rx operations, and may help to improve isolation to reduce self-interference (e.g., >50dB). In an example, Panel #<NUM> may be used for DL transmission at both edges of a respective BWP, while Panel #<NUM> is used for UL reception at a middle of the respective BWP.

<FIG> illustrates an example resource allocation <NUM> for a FDD BS and one or more UEs in accordance with an aspect of the disclosure. In particular, slots <NUM> and <NUM> are configured as SBFD slots, with a first disjoint BWP DL segment and a second disjoint BWP DL segment. In some designs, the first and second BWP DL segments may be associated with DL transmissions to different UEs. The first and second disjoint BWP DL segments are separated by a BWP UL segment (e.g., PUSCH) and guard bands (GBs). In some designs, the BWP UL segment may be associated with UL transmissions from one or more of the different UEs. In some systems such as <NUM>, the first and second disjoint BWP DL segments may correspond to sub-BWP segments.

In <FIG>, the resource allocation <NUM> is based on the underlying panel architecture depicted in <FIG>. For the SBFD slots <NUM>-<NUM>, in some designs, greater than <NUM> dB isolation may be arranged between the UL and DL BWP segments. In some designs, Weighted Overlap Add (WOLA) processing at Receiver (Rx-WOLA) may be implemented to reduce adjacent channel leakage power ratio (ACLR) to the UL BWP segment. In some designs, analog low pass filtering (LPF) may be used to improve analog to digital conversion (ADC) dynamic range. In some designs, Rx automatic gain control (AGC) states may be configured to improve the noise figure (NF). In some designs, a digital integrated circuit (IC) of the ACLR leakage may exceed <NUM> dB, and a non-linear model may be configured per each Tx-Rx pair.

In some designs, the allocation of frequency resources in slots <NUM> and <NUM> may be indicated via a frequency domain resource allocation (FDRA) from the base station. 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 <NUM> V15 (e.g., format 0_1 for scheduling a physical uplink shared channel (PUSCH), formation 1_0 for scheduling a physical downlink shared channel (PDSCH), and/or the like).

The FDRA may identify frequency resource explicitly via a bitmap (Type <NUM>) or via reference to a range of RBs (Type <NUM>). For Type <NUM> allocation, in some aspects, each bit of the bit map may correspond to an RB group (RGB) of a plurality of RBGs in the BWP. Each bit of the bit map may identify if an RBG associated with the bit is allocated in the FDRA. For example, if the bit is assigned a value of '<NUM>', the bit may identify that the RBG associated with the bit is not allocated. If the bit is assigned a value of '<NUM>', the bit may identify that the RBG associated with the bit is allocated. In some designs, the size of the bitmap may be either <NUM> bits or <NUM> bits. However, if there is a relatively large gap between the first and second disjoint BWP DL segments, the bitmap indication may become unpractical due to inefficiency.

For Type <NUM> allocation, consecutive (or contiguous) RBs are identified in association with a resource indicator value (RIV) via designation of a startpoint (RBstart) and a size (or length) indicator, as follows:
<IMG>.

Because Type <NUM> allocation identifies a BWP segment via start and length indicators in terms of RIV, it is difficult to use Type <NUM> allocation to reference disjoint BWP segments for SBFD. In particular, attempting to use Type <NUM> allocation to span across both disjoint BWP segments (e.g., DL BWP segments) will cause the indicated BWP to include the intervening BWP segment (e.g., UL BWP segment). Alternatively, each disjoint BWP segment can be identified via its own RIV and its own separate start and length indicators, which may increase overhead and complexity.

<FIG> illustrates an exemplary process <NUM> of wireless communications according to an aspect of the disclosure. The process <NUM> of <FIG> is performed by a wireless node, which may correspond to either a UE such as UE <NUM> or a BS such as BS <NUM>.

At <NUM>, the wireless node (e.g., controller/processor <NUM>, controller/processor <NUM>, scheduler <NUM>, etc.) determines within a SBFD slot, an allocation of first and second VRB groups to PRBs across first and second BWP segments based upon one or more VRB-to-PRB mapping rules. As will be discussed in more detail below, the VRB-to-PRB mapping rule(s) may comprise a manner in which the VRB groups are interleaved (or not interleaved) across the first and second BWP segments, and possibly a separate intervening BWP segment. In an example, if the wireless node corresponds to a UE, then the determination at <NUM> may occur at the controller/processor <NUM> where the FDRA is processed. In another example, if the wireless node corresponds to a UE, then the determination at <NUM> may occur at the controller/processor <NUM> and/or the scheduler <NUM> where the VRB-to-PRB mapping is implemented. In some systems such as <NUM>, the first and second disjoint BWP DL segments may correspond to sub-BWP segments.

At <NUM>, the wireless node (e.g., antennas 252a. 252r, modulator/demodulator 254a. 254r, MIMO detector <NUM>, receive processor <NUM>, Tx MIMO processor <NUM>, transmit processor <NUM>, antennas 234a. 234r, modulator/demodulator 232a. 232r, MIMO detector <NUM>, receive processor <NUM>, Tx MIMO processor <NUM>, transmit processor <NUM>, etc.) communicates data over the first and second sets of PRBs in accordance with the allocation. In an example, if the wireless node corresponds to a UE, then the communicating at <NUM> may comprise transmitting uplink data, receiving downlink data, or a combination thereof. In another example, if the wireless node corresponds to a BS, then the communicating at <NUM> may comprise transmitting downlink data, receiving uplink data, or a combination thereof.

Referring to <FIG>, in an example, the one or more VRB-to-PRB mapping rules may comprise mapping the first VRB to a first disjoint BWP segment without interleaving, or mapping the second VRB to a second disjoint BWP segment without interleaving, or a combination thereof. <FIG> illustrates a VRB-to-PRB mapping scheme 1000A in accordance with this approach, whereby a first VRB group (i.e., VRB #<NUM>) and a second VRB group (i.e., VRB #<NUM>) map directly to respective PRBs in a first disjoint BWP segment 1005A and a second disjoint BWP segment 1010A, respectively, without interleaving.

Referring to <FIG>, in another example, the one or more VRB-to-PRB mapping rules may comprise mapping the first VRB to a first disjoint BWP segment with interleaving, and mapping the second VRB to a second disjoint BWP segment with interleaving that is independent relative to the interleaving associated with the first disjoint BWP segment. <FIG> illustrates a VRB-to-PRB mapping scheme 1000B in accordance with this approach, whereby a first VRB group (i.e., VRB #<NUM>) and a second VRB group (i.e., VRB #<NUM>) map directly to PRBs in a first disjoint BWP segment 1005B and a second disjoint BWP segment 1010B, respectively, with independent interleaving. In other words, the individual RBs of VRB #<NUM> are interleaved with respect to each other, but not with respect to the individual RBs of VRB #<NUM>.

Referring to <FIG>, in another example, the one or more VRB-to-PRB mapping rules may comprise mapping a respective VRB to a respective disjoint BWP segment with interleaving if the respective disjoint BWP segment is above a size threshold and without interleaving if the respective disjoint BWP segment is not above the size threshold. In an example, this particular VRB-to-PRB mapping rule may function to override one or more other VRB-to-PRB mapping rules that would otherwise dictate that interleaving be used.

Referring to <FIG>, in another example, the one or more VRB-to-PRB mapping rules may comprise merging the first and second VRB groups, and then mapping the merged VRB group to the first and second disjoint BWP parts with interleaving. <FIG> illustrates a VRB-to-PRB mapping scheme <NUM> in accordance with this approach, whereby a first VRB group (i.e., VRB #<NUM>) and a second VRB group (i.e., VRB #<NUM>) are merged into a combined VRB <NUM> while being interleaved together, after which the combined and interleaved VRB <NUM> is mapped to a first disjoint BWP segment <NUM> and a second disjoint BWP segment <NUM>, respectively.

Referring to <FIG>, in another example, the one or more VRB-to-PRB mapping rules may comprise jointly interleaving the first and second VRBs across the first and second disjoint BWP segments. <FIG> illustrates a VRB-to-PRB mapping scheme <NUM> in accordance with this approach, whereby a first VRB group (i.e., VRB #<NUM>) and a second VRB group (i.e., VRB #<NUM>) are jointly interleaved across a first disjoint BWP segment <NUM> and a second disjoint BWP segment <NUM>, respectively. In the aspect of <FIG>, the allocation of the first and second VRBs is across PRBs that overlap with an intervening BWP segment <NUM> between the first and second disjoint BWP segments. In particular, one particular PRB <NUM> to which VRB #<NUM> is mapped overlaps with the intervening BWP segment <NUM>. In an example, the first and second disjoint BWP segments comprise DL data, and the intervening BWP segment comprises a GB, UL data, or a combination thereof. So, VRB #<NUM>'s allocation of PRB <NUM> may overlap with the GB and/or with one or UL data transmission. In other designs (e.g., where Type <NUM> or bitmap-based VRB-to-PRB mapping rule is used), the overlap can be avoided.

There are various ways in which the wireless node (which may correspond to UE or BS) may handle such an overlap, including but not limited to:.

<FIG> illustrates a VRB-to-PRB mapping scheme <NUM> in accordance with an approach whereby the UE interprets an overlap as a cycling repetition at the UE. In <FIG>, a first VRB group (i.e., VRB #<NUM>) and a second VRB group (i.e., VRB #<NUM>) are jointly interleaved across a first disjoint BWP segment <NUM> and a second disjoint BWP segment <NUM>, respectively. In the aspect of <FIG>, the allocation of the first and second VRBs is across PRBs that overlap with an intervening BWP segment <NUM> between the first and second disjoint BWP segments. In particular, one particular PRB <NUM> to which VRB #<NUM> is mapped overlaps with the intervening BWP segment <NUM>. In this case, the UE interprets PRB <NUM> as a cycling repetition of another PRB that is not inside of the intervening BWP segment <NUM>, in this case, PRB <NUM> which is part of the first disjoint BWP segment <NUM>.

Referring to <FIG>, in another example, the one or more VRB-to-PRB mapping rules may comprise scheduling the DL data in the first and second disjoint BWP segments via a single resource indicator value (RIV) with a startpoint and length indicator that encompasses the intervening BWP segment. In other words, a Type <NUM> allocation may be used whereby VRB #<NUM> and VRB #<NUM> are treated as a single PDSCH transmission that spans the first and second VRBs across the first and second disjoint BWP segments as well as an intervening BWP segment. <FIG> illustrates a VRB-to-PRB mapping scheme <NUM> in accordance with this approach, whereby a consolidated VRB associated with a single RIV is interleaved across a first disjoint BWP segment <NUM> and a second disjoint BWP segment <NUM>, respectively. In the aspect of <FIG>, the allocation of the VRB is across PRBs that overlap with an intervening BWP segment <NUM> between the first and second disjoint BWP segments. In particular, one particular PRB <NUM> to which VRB #<NUM> is mapped overlaps with the intervening BWP segment <NUM>. In an example, the first and second disjoint BWP segments comprise DL data, and the intervening BWP segment comprises a GB, UL data, or a combination thereof. So, VRB #<NUM>'s allocation of PRB <NUM> may overlap with the GB and/or with one or UL data transmission. In a further example, the overlap reflected in <FIG> with respect to PRB <NUM> may be handled via any of the mechanisms described above with respect to the overlap of PRB <NUM> in <FIG> (e.g., UE performing rate-matching only whereby PDSCH PRBs in the overlapping part are unavailable for PDSCH transmission, DL data omitted from this PRB, interpreted as error condition or cycling repetition, etc.). In other designs (e.g., where Type <NUM> or bitmap-based VRB-to-PRB mapping rule is used), the overlap can be avoided.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different means/components in exemplary apparatuses <NUM> and <NUM> in accordance with an aspect of the disclosure. The apparatus <NUM> may be a UE (e.g., UE <NUM>) in communication with an apparatus <NUM>, which may be a base station (e.g., base station <NUM>).

The apparatus <NUM> includes a transmission component <NUM>, which may correspond to transmitter circuitry in UE <NUM> as depicted in <FIG>, including controller/processor <NUM>, antenna(s) 252a. 252r, modulators(s) 254a. 254r, TX MIMO processor <NUM>, TX processor <NUM>. The apparatus <NUM> further includes SBFD component <NUM>, which may correspond to processor circuitry in UE <NUM> as depicted in <FIG>, including controller/processor <NUM>, etc. The apparatus <NUM> further includes a reception component <NUM>, which may correspond to receiver circuitry in UE <NUM> as depicted in <FIG>, including controller/processor <NUM>, antenna(s) 252a. 252r, demodulators(s) 254a. 254r, MIMO detector <NUM>, RX processor <NUM>.

The apparatus <NUM> includes a reception component <NUM>, which may correspond to receiver circuitry in BS <NUM> as depicted in <FIG>, including controller/processor <NUM>, antenna(s) 234a. 234r, demodulators(s) 232a. 232r, MIMO detector <NUM>, RX processor <NUM>, communication unit <NUM>. The apparatus <NUM> further includes a SBFD component <NUM>, which may correspond to processor circuitry in BS <NUM> as depicted in <FIG>, including controller/processor <NUM>. The apparatus <NUM> further includes a transmission component <NUM>, which may correspond to transmission circuitry in BS <NUM> as depicted in <FIG>, including e.g., controller/processor <NUM>, antenna(s) 234a. 234r, modulators(s) 232a. 232r, Tx MIMO processor <NUM>, TX processor <NUM>, communication unit <NUM>.

Referring to <FIG>, the transmission component <NUM> transmits uplink traffic data (e.g., PUSCH, etc.) and uplink control data (e.g., PUCCH, UCI, etc.) to the to the reception component <NUM>. In some designs, the SBFD component <NUM> determines VRB-to-PRB allocations for an SBFD slot, which may be based in part on the uplink communications from the apparatus <NUM>. The SBFD <NUM> forwards the VRB-to-PRB allocations for the SBFD slot to the transmission component <NUM>, which transmits downlink traffic data (e.g., PDSCH) and downlink control data (e.g., PDCCH, DCI, RRC signaling, MAC-CEs, FDRA, etc.) to the reception component <NUM> based on the VRB-to-PRB allocations for the SBFD slot. The SBFD component <NUM> determines the VRB-to-PRB allocations for the SBFD slot processes the downlink data and/or schedules uplink data for transmission based on the determination.

One or more components of the apparatus <NUM> and apparatus <NUM> may perform each of the blocks of the algorithm in the aforementioned flowchart of <FIG>. As such, each block in the aforementioned flowchart of <FIG> may be performed by a component and the apparatus <NUM> and apparatus <NUM> may include one or more of those components.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus <NUM> employing a processing system <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors and/or hardware components, represented by the processor <NUM>, the components <NUM>, <NUM> and <NUM>, and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM> and <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the UE <NUM> of <FIG> and may include the memory <NUM>, and/or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

In one configuration, the apparatus <NUM> (e.g., a UE) for wireless communication includes means for determining, within a sub-band full duplex (SBFD) slot, an allocation of first and second virtual resource block (VRB) groups to physical resource blocks (PRBs) across first and second disjoint bandwidth part (BWP) segments based upon one or more VRB-to-PRB mapping rules, and means for communicating data over the first and second sets of PRBs in accordance with the allocation.

The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> and/or the processing system <NUM> of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the processing system <NUM> may include the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM> and <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the BS <NUM> of <FIG> and may include the memory <NUM>, and/or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

In one configuration, the apparatus <NUM> (e.g., a BS) for wireless communication includes means for determining, within a sub-band full duplex (SBFD) slot, an allocation of first and second virtual resource block (VRB) groups to physical resource blocks (PRBs) across first and second disjoint bandwidth part (BWP) segments based upon one or more VRB-to-PRB mapping rules, and means for communicating data over the first and second sets of PRBs in accordance with the allocation.

In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

Claim 1:
A method performed by a wireless node (<NUM>, <NUM>), comprising:
determining (<NUM>), within a sub-band full duplex, SBFD, slot for transmitting and receiving at the same time within said SBFD slot, an allocation of first and second virtual resource block, VRB, groups to physical resource blocks, PRBs, across first and second disjoint bandwidth part, BWP, segments within the SBFD slot based upon one or more VRB-to-PRB mapping rules; and
communicating (<NUM>) data over the first and second sets of PRBs in accordance with the allocation.