Method for allocating physical downlink shared channel in sub-band full duplex

Abstract

Techniques related to physical downlink shared channel (PDSCH) allocation in a sub-band full duplex (SBFD) network are described herein. The techniques involve PDSCH frequency domain resource allocation (FDRA) type 0 and / or FDRA type 1, and include canceling one or more repetitions or SPS transmissions in an SBFD slot or a non-SBFD slot using fragmented resource block groups (RBGs), virtual resource block (VRB)-interleaving. The techniques further include a mapping of the VRB to a physical resource block (PRB) that excludes one or more PRBs in a sequence of physical resource blocks belonging to one or more UL subbands or one or more guard bands, and applying one or more rules to provide a selected broadband setting for a precoding resource block (RB) group (PRG) size, reference signaling (DMRS) is demodulated by using a physical downlink shared channel (PDSCH).

Description

[0001] [Cross-reference to related applications]

[0002] This disclosure is a part of a non-provisional application that claims priority to U.S. Provisional Application No. 63 / 371,239, filed on August 12, 2022, the contents of which are incorporated herein by reference in their entirety. [Technical field]

[0003] The present disclosure relates generally to mobile communications, and more particularly to configuration and scheduling of user equipment (UE) in a sub-band full-duplex (SBFD) network. [Background technology]

[0004] Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims listed below and are not admitted to be prior art by inclusion in this section.

[0005] In sub-band full-duplex (SBFD), all user equipments (UEs) operate in a half-duplex manner by sending or receiving data transmissions at a specific time, while the base station node, such as gNodeB (gNB), can transmit and receive data simultaneously on non-overlapping subbands of the carrier. For example, the gNB may receive data from UE#1 and UE#2 through an uplink (UL) subband while transmitting data to UE#3 through one or more downlink (DL) subbands. A DL subband refers to a resource block (RB) or a group of consecutive RBs in a frequency-domain resource allocation that can be used for downlink. Similarly, a UL subband refers to an RB or a group of consecutive RBs in a frequency-domain resource allocation that can be used for uplink. In addition, the subband partition format is a configuration that specifies all subbands in the DL or UL bandwidth part (BWP) bandwidth or in the UE channel bandwidth.

[0006] The partitioning of a slot or symbol into downlink and uplink subbands may be referred to as an SBFD partition format, while the periodic pattern of time division duplex (TDD) and SBFD configuration for each slot / symbol may be referred to as an SBFD layout configuration. Since legacy UEs only support TDD configuration functionality, their transmission and reception are completely controlled by the scheduling and applied TDD configuration. On the other hand, the gNB may share knowledge about the SBFD layout configuration with enhanced UEs. However, it cannot be ruled out that some UEs are unaware of the SBFD partitioning in certain circumstances. Therefore, how to enhance configuration and signaling with minimal UE complexity cost to allow flexible allocation of the physical downlink shared channel (PDSCH) in SBFD remains a technical challenge. Therefore, a technical solution for PDSCH allocation in SBFD networks is needed. [Summary of the invention]

[0007] The following summary is provided for informational purposes only and is not intended to be limiting in any way. That is, the following summary is intended to introduce the concepts, highlights, advantages, and benefits of the novel and non-obvious technologies described herein. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify essential features of the subject matter, nor is it a basis for determining the scope of the subject matter.

[0008] The purpose of the present disclosure is to propose solutions or solutions to the problems described herein. More specifically, the various schemes proposed in the present disclosure are believed to provide technical solutions involving UE configuration and scheduling in SBFD networks.

[0009] In one aspect, a method may include identifying a specific resource block group (RBG) located at a DL subband edge that partially overlaps a UL subband or a guard band (GB) of a physical resource block (PRBs) of a carrier in a PDSCH frequency domain resource allocation (FDRA) type 0 allocation bitmap. The method may also include providing information about the specific RBG that partially overlaps the UL subband or GB to a UE to guide the UE to use a non-overlapping portion of the specific RBG that does not overlap the UL subband or GB for PDSCH FDRA type 0 data transmission.

[0010] In another aspect, a method may include selecting a PRBs sequence for a carrier for PDSCH FDRA Type 1. The method may also include performing a virtual resource block (VRB) to physical resource block (PRB) mapping, the mapping mapping a plurality of PRBs in a physical resource block (PRB) sequence to a virtual resource block (VRB) sequence, wherein the mapping excludes one or more PRBs in the PRBs sequence belonging to one or more UL subbands or one or more guard bands.

[0011] In another aspect, an apparatus that may be implemented in a network may include a transceiver and a processor connected to the transceiver. The transceiver may be configured to wirelessly communicate. The processor may be configured to determine whether one or more of a set of conditions for using PDSCH DMRS exist. The set of conditions includes a broadband setting as a precoding resource block group (PRG) size can only be selected in a continuous FDRA, and a rule-based dynamic selection of a broadband setting as the PRG size in the Bundle Size Set 1 setting is conditional on the allocation size of the PRG reaching or exceeding half of the bandwidth of the bandwidth part (BWP). The PRG size is part of the PRB-BundlingType setting of the radio resource control (RRC) information element (IE) of the PDSCH DMRS, and the Bundle Size Set 1 setting is a downlink control information (DCI) configuration setting of the PDSCH. Subsequently, in response to determining that one or more of the set of conditions exist, the processor may apply one or more rules to provide a selection of a broadband setting for the PRG size.

[0012] It is worth noting that although the description provided herein may be in the context of certain wireless access technologies, networks and network topologies such as 5G / NR mobile communications, the proposed concepts, solutions and any variants / derivatives thereof may be implemented in, used for and implemented by other types of wireless access technologies, networks and network topologies, such as but not limited to Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-everything (V2X) and Non-terrestrial Network (NTN) communications. Therefore, the scope of the present disclosure is not limited to the examples described herein.

Brief Description of the Drawings

[0013] The accompanying drawings contain content provided for a further understanding of the present disclosure and are incorporated into and constitute a part of the present disclosure. These drawings show embodiments of the present disclosure and, together with the description, are used to explain the principles of the present disclosure. It is worth noting that the drawings are not necessarily drawn to scale, because in order to clearly illustrate the concepts of the present disclosure, some components may be shown as being not proportional to the size in actual implementation.

[0014] Figure 1 is a diagram of an example network environment in which various aspects of the present disclosure may be implemented.

[0015] Figure 2 It is a diagram of an example scenario under the first solution proposed in the present disclosure.

[0016] Figure 3 is a diagram of an example scenario under the second solution proposed in the present disclosure.

[0017] Figure 4 It is a diagram of an example scenario under the third solution proposed in the present disclosure.

[0018] Figure 5 It is a diagram of an example scenario under the fourth scheme proposed in the present disclosure.

[0019] Figure 6 is a block diagram of an example communication system according to an embodiment of the present disclosure.

[0020] Figure 7 is a flowchart of a first example process according to one embodiment of the present disclosure.

[0021] Figure 8 is a flowchart of a second example process according to one embodiment of the present disclosure.

[0022] Fig. 9 is a flowchart of a third example process according to one embodiment of the present disclosure. [Specific implementation method]

[0023] Detailed embodiments and implementations of the subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely exemplary implementations of the subject matter, which may be embodied in various forms. However, the present disclosure may be embodied in many different forms and should not be considered to be limited to the exemplary embodiments and implementations set forth herein. On the contrary, these exemplary embodiments and implementations are provided to make the description of the present disclosure comprehensive and complete and to fully convey the scope of the present disclosure to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0024] Implementations according to the present disclosure relate to various techniques, methods, schemes and / or solutions for PDSCH allocation in a sub-band full-duplex (SBFD) network. According to the present disclosure, a variety of possible solutions may be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one combination or another combination.

[0025] Figure 1 An example network environment 100 is shown in which various solutions and schemes according to the present disclosure may be implemented. Figure 2-Figure 9 An example of implementing various proposed solutions in the network environment 100 according to the present disclosure is shown. The following description of various proposed solutions refers to Figure 1-Figure 9. For the proposed schemes described in scenarios 200, 300 and 500, the working assumption is that if the SBFD partition for any allocated symbol is known to the UE, then the SBFD partition is the same for all symbols of the allocation, at least within the same time slot. Therefore, for a group of one or more symbols belonging to a DL or UL allocation, if a single SBFD partition is indicated (i.e., the same for all symbols in the group), while for the remaining symbols belonging to the DL or UL allocation, the SBFD partition is unknown to the UE, then the UE may assign the same SBFD partition to these latter symbols. In one embodiment, for allocations with repetitions, the UE processes each repetition instance separately. However, in another embodiment, where there are allocations with repetitions, the UE may process all repetition instances together and allow a single SBFD partition. On the other hand, if no SBFD partition is indicated for any symbol belonging to a DL or UL allocation, then the UE may assume that no symbol is divided into subbands.

[0026] refer to Figure 1 , the network environment 100 may include a UE 110 in wireless communication with a RAN 120 (e.g., a 5G NR mobile network or other types of networks such as NTN). The UE 110 may be in wireless communication with the RAN 120 via a base station or network node 125 (e.g., an eNB, gNB, or a transmission reception point (TRP)). The RAN 120 may be part of a network 130. In the network environment 100, the UE 110 and the network 130 (via the network node 125 of the RAN 120) may implement various schemes involving techniques for UE configuration and scheduling in an SBFD network, as described below. It is worth noting that although various proposed schemes, options, and methods may be described separately, in actual applications, these proposed schemes, options, and methods may be implemented separately or in combination. That is, in some cases, one or more proposed schemes, options, and methods may be implemented separately or separately. In other cases, some or all of the proposed schemes, options, and methods may be implemented in combination.

[0027] Figure 2An example scenario 200 under a first proposed scheme according to the present disclosure is shown. Scenario 200 may involve physical downlink shared channel (PDSCH) allocations that may be dynamically indicated via downlink control information (DCI) using type 0 frequency domain resource allocation (FDRA). FDRA type 0 is based on an allocation bitmap where each bit represents a resource block (RB) group, the RB size depends on the bandwidth part (BWP) size, and a binary configuration option that allows the bitmap size to be halved (e.g., maximum 18 bits vs. maximum 9 bits) at the expense of increasing the resource block group (RBG) size (e.g., a power of 2 between 2 and 16 RBs). Therefore, type 0 FDRA easily allows flexible and non-contiguous RB allocations, which helps allocate RBs in multiple non-contiguous DL subbands to support SBFD operation. However, one problem with using type 0 FDRA is that resource fragmentation may occur in UL subbands near the edges of DL subbands.

[0028] In one embodiment, the UE may be configured to mitigate this problem by supporting type 0FDRA containing fragmented RGB at the boundary between DL and UL subbands based on the knowledge of the partitioned symbols. Figure 2 As shown in part (A) of the example shown in , the UE can be configured to support the use of fragmented RBGs, for example, fragments 2 and 4 of RBGs of physical resource blocks (PRBs) of UL subbands and / or guard bands (GBs) near the edge of a DL subband (UL-SB). This means that RBGs that partially overlap with UL-SBs or GBs, i.e., RBGs of PRBs that are required to separate DL subbands and UL subbands, can also be used for data transmission. However, only fragments of such RBGs, i.e., non-overlapping fragments of RBGs that do not overlap with UL-SBs or GBs, are used for transmission.

[0029] Figure 3 An example scenario 300 according to the second proposed solution of the present disclosure is shown. The scenario 300 may involve PDSCH FDRA Type 0, in which the trade-off between allocation granularity and signaling overhead may be balanced when multi-subband allocation uses or does not use full subbands. Figure 3 In the example shown, for type 0 allocations of SBFD slots / symbols (i.e., partitioned between DL and UL), a portion of the allocation bitmap (portion A) may be used for allocations via subband signaling, while another portion of the allocation bitmap (portion B) may be used for allocations via RBG signaling. Such an allocation map may include one or more features. For example, a first feature may be that the FDRA allocation bitmap size defined by the high-level definition of PDSCH FDRA type 0 may be retained. A second feature may be that the allocation map excludes RBGs that completely overlap with UL subbands or guard bands.

[0030] A third feature may be that there may be reserved flags in the bitmap for indicating which DL subbands are used for full or at least partial allocation. Thus, the remaining bits in the allocation bitmap may indicate the allocation of corresponding RBGs in the set of DL subslot RBGs that belong to at least a partial allocation. A fourth feature may be that the size of each RBG may be divided by two if the available bitmap length allows, unless the size of the RBG is already two. A fifth feature may be that the allocation bitmap is filled with zeros, ones and / or undefined bits.

[0031] A sixth feature may be that, in the case of M DL subbands (where M is an integer), the first M bits in the bitmap may indicate whether the corresponding bit is fully allocated (when the bit is set to 1) or at most partially allocated. For example, if the BWP BW and rbg_size configurations produce a 9-bit bitmap according to Release 17 (R17) of the 3GPP specification, and the first of the two subbands is fully allocated, then in the configuration '10|1111000', '10' indicates that the entire first subband is allocated, and '1111000' indicates that the first four RBGs of the second DL subband are allocated. A seventh feature may be that, in the case of M DL subbands (where M is an integer), the first M-1 bits in the bitmap may indicate whether the corresponding bit is fully allocated (when the bit is set to 1) or at most partially allocated.

[0032] An eighth feature may be that, in an implementation with two DL subbands, two bits p are reserved to indicate one of the following allocation options: (1) Val_11 - Both subbands are at least partially allocated, and bitmap<p|q> The remaining bits q in the bitmap cover the RBGs belonging to both subbands; (2) Val_01 - none of the RBGs of the first subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the second subband; and (3) Val_10 - none of the RBGs of the second subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the first subband.

[0033] A ninth feature may be that, in an implementation with two DL subbands, two bits p are reserved to indicate one of the following allocation options: (1) Val_00 - Both subbands are at least partially allocated, and bitmap<p|q> (2) Val_10 - all RBGs of the first subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the second subband; and (3) Val_01 - all RBGs of the second subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the first subband.

[0034] A tenth feature may be that, in an implementation with two DL subbands, two bits p are reserved to indicate one of the following allocation options: (1) Val_00 - Both subbands are at least partially allocated and the bitmap<p|q> The remaining bits q of the bitmap cover the RBGs belonging to both subbands; (2) Val_01 - none of the RBGs of the first subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the second subband; (3) Val_10 - none of the RBGs of the second subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the first subband; and (4) Val_11 - all RBGs of the first subband are used, and the remaining bits in the bitmap cover the RBGs belonging to the second subband.

[0035] Figure 4 An example scenario 400 according to a third proposed solution of the present disclosure is shown. The scenario 400 may involve a PDSCH allocation based on a code block group (CBG) in which virtual resource block (VRB) interleaving is used with a frequency domain resource allocation (FDRA) type 0. Currently, FDRA type 0 does not support VRB interleaving, and type 1 VRB interleaving is generally not compatible with sub-band full duplex (SBFD). However, Figure 4 The example shown in illustrates that VRB interleaving for FDRA Type 0 can be achieved using one or more features. The first feature is that the existing VRB interleaving field in the downlink control information (DCI) of the PDSCH can be used to signal VRB interleaving for FDRA Type 0. The second feature is that enabling and disabling VRB interleaving does not change the set of allocated physical resource blocks (PRBs). The third feature is that when VRB interleaving is enabled, the even VRB indices are first mapped to the allocated PRB sequence starting with the allocated PRB with the lowest index, and then the odd VRB indices are mapped to the remaining allocated PRBs. Therefore, in Figure 4 In the example shown in , part (A) shows the PRBs allocated in the original sequence of PRBs for the carrier used, and these allocated PRBs are called allocated PRBs (ARBs). Part (B) shows the sequence of VRBs interleaved with ARBs using one or more characteristics through ARB to VRB reverse mapping. As shown, the sequence of VRBs with even VRB indices (part B) are initially mapped sequentially to the ARB starting from the ARB with the lowest index in the sequence of ARBs (part A) until all VRBs with even VRB indices are mapped. Subsequently, the sequence of VRBs with odd VRB indices (part B) are sequentially mapped to the remaining ARBs in the sequence of ARBs (part A).

[0036] Figure 5An example scenario 500 according to a fourth proposed scheme of the present disclosure is shown. The scenario 500 may involve enhancements to PDSCH FDRA Type 1 on non-contiguous PRBs. In general, FDRA Type 1 provides fully flexible starting RB and RB length on a set of contiguous PRBs. In addition, FDRA Type 1 allows interleaved allocation on two contiguous sets of PRBs that are half a bandwidth part (BWP) bandwidth away. Therefore, since FDRA Type 1 is based on the starting RB and RB length, FDRA Type 1 supports RB granularity allocation, but is limited to contiguous segments of VRBs. Unlike FDRA Type 0, in which each VRB is always mapped to a PRB with the same index, in FDRA Type 1, VRB interleaving can be dynamically signaled, where the allocated VRB segments are mapped to two PRB segments starting from half the active BWP bandwidth distance, such that even PRBs are mapped to the lower segment and odd PRBs are mapped to the upper segment. In addition, only FDRA Type 1 can be used with DCI 1_0 and is used during initial access. Therefore, FDRA Type 1 is generally not suitable for simultaneous allocation on two (or more) downlink subbands.

[0037] However, there are several solutions to this problem. One solution is a VRB to PRB mapping that excludes PRBs that belong to uplink subbands or guard bands for FDRA Type 1. This mapping can be implemented using one or more techniques. In one technique, the first roundup(Log2M) bits can be used to select the subband, and the remaining roundup(log2(N*(N+1) / 2)) bits, where N is the width of the maximum downlink subband, are encoded as a start and length indicator (SLIV).

[0038] In another technique, a single contiguous VRB range is indicated by the existing SLIV rule, and the PRBs can be re-indexed by excluding PRBs that are not available for downlink transmission based on the SBFD configuration indicated to the UE. Figure 5 As shown in the first example in FIG. 1 , where part (A) shows VRBs and part (B) shows PRBs, VRB interleaving may be enabled for this technique. However, in an alternative implementation, VRBs may be interleaved. Furthermore, in another alternative implementation, VRB interleaving may always be disabled.

[0039] Another solution to overcome the problem is that when VRB interleaving is enabled for FDRA type 1, VRB interleaving can be performed on each consecutive PRB segment separately to exclude PRBs belonging to uplink subbands or guard bands. This form of interleaving is determined by Figure 5As shown in the interleaving of VBRs to PRBS from part (C) to part (D) in the second example in FIG, where the first VRB interleaving is performed on PRBs with indices 0-5 and the second VRB interleaving is performed on PRBs with indices 6-10. This interleaving can be implemented using one or more techniques. In one technique, for each consecutive PRB segment, first, the interleaving of indices 0…K can be applied. i -1 to calculate the value of the ith th ) The RB size of the subband is K i VRBs and PRBs are allocated. Then, i Instead of bandwidth size, VRB interleaving is applied to each consecutive PRB segment. In another technique, the higher layer configuration of PDSCH FDRA type 1 can be used to determine the RB range 0…K for each subband. i -1 to define the start and end positions of VRB interleaving.

[0040] For FDRA Type 0 and FDRA Type 1, when PDSCH is scheduled in a repetitive manner, the same FDRA allocation information may need to be interpreted in a mix of SBFD and non-SBFD time slots. Therefore, in accordance with the present disclosure, several techniques may be implemented under the fifth proposed scheme to define when to cancel repetitions in a time slot, such as a SBFD time slot or a non-SBFD time slot. In the first technique, when PDSCH is scheduled in a repetitive manner, repetitions are canceled in time slots that do not match the first time slot in a sequence of SBFD and non-SBFD time slots in each SBFD partition.

[0041] In the second technique, when PDSCH is scheduled in a repeated manner, the UE's FDRA behavior is adapted to the SBFD partition format of the first repetition instance. In addition, if all resource elements (REs) are available for downlink, all subsequent repetitions may use the same physical resource blocks (PRBs), otherwise, the repetition instance is cancelled for that time slot.

[0042] In a third technique, when PDSCH is scheduled in a repeated manner, the UE's FDRA behavior can be adapted to the SBFD partition format applicable to each repetition instance. In one example, for FDRA type 0 allocations on SBFD slots / symbols, RBG(s) may be allocated that partially overlap with the UL-SB and / or any guard bands required to separate the DL and UL subbands so that the transmission uses only non-overlapping RBs. This corresponds to Figure 2 Described is the usage of fragmented RBGs.

[0043] In another example, for FDRA type 0 allocations on SBFD slots / symbols, the adaptation may include using a portion of the allocation bitmap for signaling allocations of subbands and another portion of the bitmap for signaling allocations of RBGs, such as Figure 3 In an additional example, for FDRA type 0 allocations on SBFD slots / symbols, the Figure 4 In a further example, for FDRA type 1 allocations on SBFD slots / symbols, a VRB to PRB mapping may be used that excludes PRBs belonging to UL subbands or guard bands, such as Figure 5 Alternatively, when interleaving is enabled for FDRA type 1, interleaving may be performed separately for consecutive PRB segments, such as Figure 5 Further description to handle duplication.

[0044] For FDRA with semi-persistent scheduling (SPS), it can be determined based on enabling DCI in FDRA Type 0 and FDRA Type 1. This means that when scheduling SPS allocations, the same FDRA allocation information may need to be interpreted in a mix of SBFD and non-SBFD time slots. Therefore, in accordance with the present disclosure, several techniques can be implemented under the sixth proposed scheme to define when to cancel SPS transmissions in a time slot. In the first technique, when SPS PDSCH is scheduled, SPS transmissions can be canceled in time slots that do not match the first transmission in the sequence in each SBFD partition.

[0045] In the second technique, when SPS PDSCH is scheduled, the UE's FDRA behavior is adapted to the SBFD partition format for the first SPS transmission based on the enabling DCI. In addition, if all REs are available for downlink, all subsequent SPS transmissions may use the same PRBs, otherwise the SPS transmission is cancelled for that time slot.

[0046] In a third technique, when SPS PDSCH is scheduled, the UE's FDRA behavior can be adapted to the SBFD partition format applicable to each SPS transmission. In one example, for FDRA type 0 allocations on SBFD slots / symbols, RBG(s) may be allocated that partially overlap with the UL-SB and / or any guard bands required to separate the DL and UL subbands so that the transmission uses only non-overlapping RBs. This corresponds to Figure 2 Described is the usage of fragmented RBGs.

[0047] In another example, for FDRA type 0 allocations on SBFD slots / symbols, the adaptation may include using a portion of the allocation bitmap for signaling allocations of subbands and another portion of the bitmap for signaling allocations of RBGs, such as Figure 3 In an additional example, for FDRA type 0 allocations on SBFD slots / symbols, the Figure 4In a further example, for FDRA type 1 allocations on SBFD slots / symbols, a VRB to PRB mapping may be used that excludes PRBs belonging to UL subbands or guard bands, such as Figure 5 Alternatively, when interleaving is enabled for FDRA type 1, interleaving may be performed separately for consecutive PRB segments, such as Figure 5 Further description is given to handle SPS allocation.

[0048] The physical downlink shared channel (PDSCH) demodulation reference signaling (DMRS) is a special type of physical layer signaling used as reference signaling for decoding the PDSCH. In various aspects, DMRS mapping is based on common resource block (CRB) indexing, and then the CRBs are selected by the PDSCH transmission bandwidth (BW). In the PRB-BundlingType setting of the DMRS in the radio resource control (RRC) information element (IE), the precoding resource block group (PRG) size may be in the range of {2PRBs, 4PRBs, 'wideband'}, where 'wideband' is only used in certain cases, such as when the base station (BS) optimizes the precoder using reciprocity-based channel estimation. In addition, the 'wideband' PRG can only be selected with contiguous FDRA. This may be a problem because the 'wideband' PRG may have practicality when allocated on non-contiguous DL subbands in a SBFD slot. In addition, the rule-based dynamic selection of 'wideband' in BundleSize Set 1 (DCI configuration setting for PDSCH attributes) depends on the allocation size of the PRG reaching or exceeding half of the BWP bandwidth. However, in the allocation scenario of SBFD timeslots, this ratio may be too high. For example, in some cases, the total available bandwidth in the DL subband may be less than half of the BWP bandwidth.

[0049] However, these problems can be overcome by one or more techniques under the seventh scheme proposed according to the present disclosure. The first technique is that a 'wideband' PRG can be semi-statically configured when the allocation of the PRG is continuous on a continuous sequence of DL subband RBs. However, in this case, the UE may only be able to interpolate within the DL subband. The second technique is that conditional PRG sizes such as 'n2-wideband' can be addressed so that 'wideband' is selected when (1) the allocation is continuous on a continuous sequence of DL subband RBs; or (2) the size of the allocation reaches or exceeds a predetermined threshold. For example, the predetermined threshold may be half of the BWPBW, the sum of all RBs in the DL BWP, half of the DL subband bandwidth (assuming that the allocation is limited to a single subband), or the bandwidth of the full DL subband (not excluding transmissions spanning multiple subbands).

[0050] A third technique is to configure the rule-based dynamic selection of 'wideband' in Bundle Size Set 1 to be dependent on the allocation size reaching or exceeding one of the following options, which may be fixed or selected by a predefined rule or configuration: (1) half of the BWP BW; (2) the sum of all RBs in the DL BWP; (3) half of the DL subband bandwidth (assuming the allocation is limited to a single subband); or (4) the bandwidth of the full DL subband (not excluding transmissions spanning multiple subbands). In a fourth technique, if the PDSCH is scheduled with repetitions or SPS, the slot that yields the lowest threshold may be used to determine the precoder selection, and the same precoder may be used in the repetition.

[0051] Example Implementation

[0052] Figure 6 An example communication system 600 is shown, including at least an example device 610 and an example device 620, according to an embodiment of the present disclosure. Each of the device 610 and the device 620 can perform various functions to implement the techniques, schemes, processes and methods described herein, involving techniques for UE configuration and scheduling in SBFD networks, including various schemes of various proposed designs, concepts, schemes, systems and methods described above, including the network environment 100, and the processes described below.

[0053] Each of the devices 610 and 620 may be part of an electronic device, which may be a network device or a UE (e.g., UE 110), such as a portable or mobile device, a wearable device, a vehicle device or a vehicle, a wireless communication device, or a computing device. For example, each of the devices 610 and 620 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing device (e.g., a tablet, a laptop, or a notebook computer). Each of the devices 610 and 620 may also be part of a machine-type device, which may be an Internet of Things (IoT) device, such as a fixed or static device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of the devices 610 and 620 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, device 610 and / or device 620 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G network, NR network, or IoT network.

[0054] In some embodiments, each of the apparatus 610 and the apparatus 620 may be implemented in the form of one or more integrated circuit (IC) chips, such as but not limited to one or more single-core processors, one or more multi-core processors, one or more complex instruction set computing (CISC) processors, or one or more reduced instruction set computing (RISC) processors. In the above various schemes, each of the apparatus 610 and the apparatus 620 may be implemented in or as a network device or UE. Each of the apparatus 610 and the apparatus 620 may include Figure 6 , such as processor 612 and processor 622, respectively. Device 610 and device 620 may also include one or more other components not related to the solution proposed in the present disclosure (e.g., internal power supply, display device and / or user interface device), so for the sake of brevity, these components of device 610 and device 620 are not shown in FIG. Figure 6 It is not shown in the figure and is not described below.

[0055] In one aspect, processor 612 and processor 622 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more complex instruction set computers (CISC) or reduced instruction set computers (RISC) processors. That is, although the singular term "a processor" is used here to refer to processor 612 and processor 622, in some implementations, each processor 612 and processor 622 may include multiple processors, and in other implementations, may include a single processor, consistent with the content disclosed herein. In another aspect, processor 612 and processor 622 may be implemented in the form of hardware (optionally, firmware), including electronic components, such as but not limited to one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more variable capacitors, which are configured and arranged to achieve the specific purposes disclosed herein. In other words, in at least some implementations, processor 612 and processor 622 are special-purpose machines specially designed, arranged and configured to perform specific tasks, including technologies related to UE configuration and scheduling in SBFD networks according to various implementations disclosed herein.

[0056] In some implementations, the device 610 may also include a transceiver 616 connected to the processor 612. The transceiver 616 may be capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 616 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs). In some implementations, the transceiver 616 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 616 may be equipped with multiple transmit antennas and multiple receive antennas for multiple input multiple output (MIMO) wireless communication. In some implementations, the device 620 may also include a transceiver 626 connected to the processor 622. The transceiver 626 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 626 may be capable of wirelessly communicating with different types of UE / wireless networks of different RATs. In some implementations, the transceiver 626 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 626 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0057] In some implementations, the device 610 may further include a memory 614 connected to the processor 612 and accessible by the processor 612 and storing data therein. In some implementations, the device 620 may further include a memory 624 connected to the processor 622 and accessible by the processor 622 and storing data therein. Each of the memory 614 and the memory 624 may include a random access memory (RAM) type, such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and / or zero capacitance RAM (Z-RAM). Alternatively, each of the memory 614 and the memory 624 may also include a read-only memory (ROM) type, such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of the memory 614 and the memory 624 may also include a non-volatile random access memory (NVRAM) type, such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and / or phase change memory.

[0058] Each of the apparatus 610 and the apparatus 620 may be a communication entity capable of communicating with each other using various proposed schemes disclosed herein. For illustrative purposes and without limitation, the following provides a description of the capabilities of the apparatus 610 as a UE (e.g., UE 110) and the apparatus 620 as a network node (e.g., network node 126 or another network node implementing one or more of the above network-side functions), as an application server-side network (e.g., network 130 as a 5G / NR mobile network).

[0059] In some proposed schemes according to the techniques disclosed herein involving PDSCH allocation in a SBFD network, a processor 622 of an apparatus 620, implemented as or as a network node (e.g., UE 125) may identify a specific RBG located at an edge of a DL subband that partially overlaps PRBs of a UL subband or GB of a carrier in a PDSCH FDRA type 0 allocation bitmap. Subsequently, the processor 622 may provide information about the specific RBG that partially overlaps with the UL subband or GB to the UE via a transceiver 626 to guide the UE to use a non-overlapping portion of the specific RBG that does not overlap with the UL subband or GB for data transmission of PDSCH FDRA type 0. For example, the information may be received by the UE via a transceiver 616 and processed by the processor 612.

[0060] In some implementations, the processor 622 may further allocate multiple PRBs from the PRBs sequence of the carrier to generate an ARBs sequence used by PDSCH FDRA type 0, and then map the ARBs sequence to VRBs through VRB interleaving, which VRB interleaving includes sequentially mapping a first group of VRBs in a VRBs sequence with an even VRB index to an ARB sequence starting from an ARB with a lowest index, and then sequentially mapping a second group of VRBs in a VRBs sequence with an odd VRB index to the remaining ARBs in the ARBs sequence.

[0061] In some implementations, when the PDSCH is scheduled in a repetitive manner, the processor 622 may cancel one or more repetitions in a sub-band full duplex (SBFD) time slot or a non-SBFD time slot, and the canceling of one or more repetitions may include: (1) canceling one or more repetitions in the time slot when the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's frequency domain resource allocation (FDRA) behavior to the SBFD partition format of the first repetition in the time slot and canceling the repetition of the time slot when all resource elements (REs) are available for downlink but subsequent repetitions do not use the same physical resource blocks (PRBs); or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each repetition in the time slot.

[0062] In some implementations, when a semi-persistent scheduling (SPS) assignment is scheduled for the PDSCH, the processor 622 may cancel an SPS transmission in an SBFD time slot or a non-SBFD time slot, where the canceling of the SPS transmission may include: (1) canceling the SPS transmission in the time slot when the SBFD partition does not match the first transmission in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's FDRA behavior to the SBFD partition format for the first SPS transmission after enabling downlink control information (DCI) and canceling the repetition of the time slot when all REs are available for downlink but subsequent SPS transmissions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each SPS transmission in the time slot.

[0063] In other embodiments according to the present disclosure, a processor 622 of the apparatus 620, implemented in or as a network node (e.g., a user equipment 125), may select a PRBs sequence of a carrier for a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 1. Subsequently, the processor 622 may perform a virtual resource block to physical resource block (VRB-PRB) mapping, which maps a plurality of PRBs in the PRBs sequence to the VRBs sequence, wherein the mapping excludes one or more PRBs in the PRBs sequence belonging to one or more uplink (UL) subbands or one or more guard bands.

[0064] In some implementations, performing VRB-PRB mapping includes using the first roundup(Log2 M) bits to select a subband, and the remaining roundup(log2(N*(N+1) / 2)) bits, where N is the width of the maximum downlink (DL) subband, are encoded as a start and length indicator (SLIV).

[0065] In certain implementations, when a single contiguous VRB range is indicated by an existing SLIV rule, performing VRB-PRB mapping includes re-indexing a sequence of PRBs for VRB-PRB mapping by excluding PRBs that are unavailable for downlink transmission based on a SBFD configuration indicated to the UE.

[0066] In some implementations, when virtual resource block interleaving (VBR-interleaving) is enabled for VRB-PRB mapping and VRB interleaving is performed separately for each consecutive PRB segment in a sequence of PRBs, VRB interleaving is performed for each consecutive PRB segment and at least first applies indexes 0…K i -1According to the i th The resource block (RB) size Ki of the subband is allocated to VRBs and PRBs, and then K iAlternatively, VRB interleaving is performed on each consecutive PRB segment by using at least a higher layer configuration of PDSCH FDRA type 1 to determine the RB range 0…K for each subband. i -1 to define the start and end positions of VRB interleaving.

[0067] In some implementations, when the PDSCH is scheduled in a repeated manner, the processor 622 may cancel one or more repetitions in an SBFD time slot or a non-SBFD time slot, and canceling one or more repetitions may include: (1) canceling one or more repetitions in the time slot when the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's FDRA behavior to the SBFD partition format of the first repetition in the time slot and canceling the repetition of the time slot when all REs are available for downlink but subsequent repetitions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each repetition in the time slot.

[0068] In some implementations, when an SPS allocation is scheduled for the PDSCH, the processor 622 may cancel an SPS transmission in an SBFD time slot or a non-SBFD time slot, where the canceling of the SPS transmission may include: (1) canceling the SPS transmission in the time slot when the SBFD partition does not match the first transmission in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's FDRA behavior to the SBFD partition format for the first SPS transmission after DCI is enabled and canceling the repetition of the time slot when all REs are available for downlink but subsequent SPS transmissions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each SPS transmission in the time slot.

[0069] In an additional aspect presented in the present disclosure, relating to a PDSCH allocation technique, a processor 622 of an apparatus 620, implemented in or as a network node (e.g., a user equipment 125), may determine whether one or more of a set of conditions exist regarding the use of a PDSCH demodulation reference signaling (DMRS). The set of conditions includes a wideband setting as a precoding resource block (PRG) size can only be selected in a continuous frequency domain resource allocation (FDRA), and a rule-based dynamic selection of a wideband setting as a PRG size in a BundleSize Set 1 setting is conditional on the allocation size of the PRG reaching or exceeding half of a bandwidth part (BWP) bandwidth. The PRG size is part of a PRB-BundlingType setting of a radio resource control (RRC) information element (IE) of a PDSCH DMRS, and the Bundle Size Set 1 setting is a downlink control information (DCI) configuration setting of the PDSCH. Subsequently, in response to determining that one or more of the set of conditions exist, the processor 622 may apply one or more rules to provide for selecting a wideband setting for the PRG size.

[0070] In some implementations, applying the one or more rules includes the processor 622 performing at least one of the following: (A) providing configuration for the wideband setting so that the PRG size is semi-statically configured when the allocation of the wideband PRG is contiguous over a contiguous sequence of downlink (DL) subband resource blocks (RBs); (B) configuring the wideband setting to select the PRG size when the allocation of the wideband PRG is contiguous over a contiguous sequence of DL subband RBs or when the allocation size of the wideband PRG meets or exceeds one of the following: (1) half of the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half of the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; (C) providing for dynamic selection of the wideband setting in Bundle Size set 1 based on the allocation size of the wideband PRG meeting or exceeding one of the following: (1) half of the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half of the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband. The sum of all RBs in the BWP; (3) half the width of the DL subband when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; and (D) for PDSCH using repeated or semi-persistent scheduling (SPS), the time slot that produces the lowest threshold is used to determine the precoder selection and the precoder is reused. It is worth noting that when the wideband setting is semi-statically configured for the PRG size, the user equipment is configured to interpolate only within the subband.

[0071] Example process

[0072] Figure 7-9An exemplary process 700-900 is shown, which is consistent with an implementation of the present disclosure. Each process 700-900 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods, whether in part or in whole, including those described above. More specifically, process 600 may represent an aspect of the proposed concepts and schemes, involving the technology of user equipment configuration and scheduling in SBFD networks. Each process 700-900 may include one or more operations, actions or functions, as shown in one or more blocks. Although shown as discrete blocks, the various blocks of each process can be divided into additional blocks, merged into fewer blocks or eliminated according to the desired implementation. In addition, the blocks / sub-blocks of each process can be executed in the order shown in each figure, or can be executed in a different order. In addition, one or more blocks / sub-blocks of each process may be iteratively executed. Each process 700-900 can be implemented by device 610 and device 620 and their variants. For illustrative purposes only and without limitation of scope, process 600 is described in the context of an application server-side network (e.g., network 130) with device 610 as a user equipment (e.g., user equipment 110) and device 620 as a communication entity, such as a network node or base station (e.g., network node 125 or other network node implementing one or more of the above-described network-side functions).

[0073] Figure 7 700, consistent with one implementation of the present disclosure. At 710, the process 700 may include a processor 622 of an apparatus 620, implemented in or as a network node (e.g., user equipment 125), identifying a particular resource block group (RBG) located at a DL subband edge, the RBG partially overlapping a guard band (GB) of a carrier's uplink (UL) subband or a carrier's physical resource blocks (PRBs) in a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 0 allocation bitmap.

[0074] At 720, process 700 may include processor 622 providing information about the specific RBG to a user equipment (UE), the resource block group partially overlapping with the uplink subband or the guard band, and the information indicating that the UE uses a non-overlapping portion of the specific RBG that does not overlap with the UL subband or the GB for PDSCH FDRA type 0 data transmission.

[0075] In some implementations, process 700 may include the processor 622 allocating multiple physical resource blocks from a physical resource block sequence of the carrier to generate an allocated resource block (ARBs) sequence for use by the PDSCH FDRA type 0; and then mapping the allocated resource block sequence to virtual resource blocks through virtual resource block (VRB) interleaving, the virtual resource block interleaving including sequentially mapping a first group of virtual resource blocks with even virtual resource block indices in the virtual resource block sequence to the allocated resource block sequence starting from the allocated resource block with the lowest index, and then sequentially mapping a second group of virtual resource blocks with odd indices in the virtual resource block sequence to the remaining allocated resource blocks in the allocated resource block sequence.

[0076] In some implementations, when the PDSCH is scheduled in a repetitive manner, the process 700 may include the processor 622 canceling one or more repetitions in a sub-band full duplex (SBFD) time slot or a non-SBFD time slot, wherein the canceling of the one or more repetitions includes: (1) canceling one or more repetitions in the time slot when the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's frequency domain resource allocation (FDRA) behavior to the SBFD partition format of the first repetition in the time slot and canceling the repetition of the time slot when all resource elements (REs) are available for downlink but subsequent repetitions do not use the same physical resource blocks (PRBs); or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each repetition in the time slot.

[0077] In some implementations, when a semi-persistent scheduling (SPS) allocation is scheduled for the PDSCH, the process 700 may include the processor 622 canceling the SPS transmission in a SBFD time slot or a non-SBFD time slot, wherein the canceling of the SPS transmission includes: (1) canceling the SPS transmission in the time slot when the SBFD partition does not match the first transmission in the SBFD and non-SBFD time slot sequence; (2) adapting the UE's FDRA behavior to the SBFD partition format of the first SPS transmission after enabling downlink control information (DCI) and canceling the repetition of the time slot when all REs are available for downlink but subsequent SPS transmissions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each SPS transmission in the time slot.

[0078] Figure 8 is a flow chart of an example process 800 according to one implementation of the present disclosure. At 810, process 800 may include processor 622 of apparatus 620, implemented in or as a network node (eg, user equipment 125), selecting a sequence of physical resource blocks (PRBs) for a carrier of PDSCH FDRA Type 1.

[0079] At 820, process 800 may include processor 622 performing a virtual resource block (VRB) to physical resource block (PRB) mapping that maps a plurality of physical resource blocks in a physical resource block sequence to a virtual resource block sequence, wherein the mapping excludes one or more physical resource blocks in the physical resource block sequence that belong to one or more uplink (UL) subbands or one or more guard bands.

[0080] In some implementations, the performance of VRB-PRB mapping of process 800 includes using the first roundup(Log2 M) bits to select a subband, and the remaining roundup(log2(N*(N+1) / 2)) bits, where N is the width of the maximum downlink (DL) subband, are encoded as a start and length indicator (SLIV).

[0081] In some implementations, when a single contiguous range of virtual resource blocks is indicated by an existing SLIV rule, the performance of VRB-PRB mapping of process 800 includes re-indexing a sequence of physical resource blocks for VRB-PRB mapping by excluding physical resource blocks that are indicated to a user equipment (UE) as unavailable for downlink transmission based on a sub-band full-duplex (SBFD) configuration.

[0082] In some implementations, when virtual resource block interleaving is enabled for VRB-PRB mapping and virtual resource block interleaving is performed on each consecutive physical resource block segment in a physical resource block sequence, virtual resource block interleaving is performed on each consecutive physical resource block segment, at least first applying indexes 0...K i -1 according to the resource block (RB) size Ki i th The subband is allocated with virtual resource blocks and physical resource blocks, and then K i Instead of bandwidth size, virtual resource block interleaving is applied to each consecutive physical resource block segment. Alternatively, virtual resource block interleaving is performed on each consecutive physical resource block segment, at least by using the higher layer configuration of PDSCH FDRA type 1 to determine the RB range 0...K for each subband i -1 to define the starting and ending positions of the virtual resource blocks.

[0083] In some implementations, when the PDSCH is scheduled in a repeated manner, process 800 may include processor 622 canceling one or more repetitions in a SBFD time slot or a non-SBFD time slot, wherein canceling one or more repetitions includes: (1) canceling one or more repetitions in the time slot when the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots; (2) adapting the UE's FDRA behavior to the SBFD partition format of the first repetition in the time slot and canceling the repetition of the time slot when all REs are available for downlink but subsequent repetitions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each repetition in the time slot.

[0084] In some implementations, when an SPS allocation is scheduled for the PDSCH, process 800 may include processor 622 canceling an SPS transmission in a SBFD time slot or a non-SBFD time slot, wherein canceling the SPS transmission includes: (1) canceling the SPS transmission in the time slot when the SBFD partition does not match the first transmission in the SBFD and non-SBFD time slot sequence; (2) adapting the UE's FDRA behavior to the SBFD partition format for the first SPS transmission after enabling DCI, and canceling the duplication of the time slot when all REs are available for downlink but subsequent SPS transmissions do not use the same PRBs; or (3) adapting the UE's FDRA behavior to the SBFD partition format applicable to each SPS transmission in the time slot.

[0085] Fig. 9 is a flow chart of an example process 900 according to an embodiment of the present disclosure. At 910, the process 900 may include a processor 622 in an apparatus 620, implemented in or as a network node (e.g., user equipment 125), determining whether one or more of a set of conditions for using PDSCH DMRS exist. The set of conditions includes a wideband setting as a PRG size can only be selected in a continuous FDRA, and a rule-based dynamic selection of a wideband setting as a PRG size in a Bundle Size Set 1 setting is conditional on the allocated size of the PRG reaching or exceeding half of the BWP bandwidth. The PRG size is part of the PRB-BundlingType setting of the RRC IE of the PDSCH DMRS, and the Bundle Size Set 1 setting is a DCI configuration setting for the PDSCH.

[0086] At 920, in response to determining that one or more of the set of conditions exist, process 900 may include processor 622 applying one or more rules to provide for selecting a bandwidth setting for the PRG size.

[0087] In some embodiments, applying the one or more rules includes the processor 622 performing at least one of the following: (A) providing configuration for the wideband setting so that the PRG size is semi-statically configured when the allocation of the wideband PRG is contiguous over a contiguous sequence of downlink (DL) subband RBs; (B) configuring the wideband setting to select the PRG size when the allocation of the wideband PRG is contiguous over a contiguous sequence of DL subband RBs or when the allocated size of the wideband PRG meets or exceeds one of the following: (1) half of the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half of the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; (C) providing for dynamic selection of the wideband setting in Bundle Size set 1 based on the condition that the allocated size of the wideband PRG meets or exceeds one of the following: (1) half of the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half of the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband. The sum of all RBs in the BWP; (3) half the width of the DL subband when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; and (D) for PDSCH using repetition or SPS, the time slot that produces the lowest threshold is used to determine the precoder selection and the precoder is used by repetition. It is appreciated that when the wideband setting is semi-statically configured for the PRG size, the user equipment is configured to interpolate only within the subband.

[0088] Additional Notes

[0089] The subject matter described herein sometimes shows different components contained in or connected to different other components. It should be understood that the architectures depicted in this way are only examples, and many other architectures can actually be implemented to achieve the same function. Conceptually, the arrangement of any components to achieve the same function is actually "associated" in order to achieve the desired function. Therefore, any two components combined here to achieve a specific function can be regarded as "associated" with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be regarded as "operably connected" to each other, or "operably coupled" to achieve the desired function, and any two components that can be so associated can also be regarded as "operably coupled" to each other to achieve the desired function. Specific examples of operable coupling include, but are not limited to, components that can be physically matched and / or physically interacted and / or components that can be wirelessly interacted and / or wirelessly interacted and / or components that can interact logically and / or logically interact.

[0090] Furthermore, with respect to nearly any plural and / or singular terms used herein, one having technical skill can translate from the plural to the singular and / or from the singular to the plural as appropriate to the context and / or application. Various singular and plural permutations may be expressly listed herein for the sake of clarity.

[0091] Furthermore, those skilled in the art will understand that, in general, the terms used herein, especially in the appended claims, such as the bodies of the appended claims, are generally considered to be "open" terms, for example, the word "comprising" should be interpreted as "including but not limited to", the word "having" should be interpreted as "having at least", the word "including" should be interpreted as "including but not limited to", etc. In addition, those skilled in the art will further understand that if a specific number of claim recitations is intended to be introduced, such intent will be explicitly stated in the claim, and in the absence of such a statement, such intent is absent. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be interpreted to mean that any particular claim that introduces a claim recitation with the indefinite article "a" or "an" only includes one implementation of such a recitation, even if the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an", for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same is true for the use of definite articles used to introduce claim recitations. Furthermore, even if a particular number of an introduced claim recitation is explicitly stated, one skilled in the art will recognize that such recitation should be interpreted as at least the stated number, e.g., merely stating "two recitations," without other modifiers, means at least two recitations, or two or more recitations. Furthermore, where a convention similar to "at least one of A, B, and C, etc." is used, generally, such constructions are intended to be understood by those skilled in the art, e.g., "a system having at least A, B, and C" would include, but are not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Where a convention similar to "at least one of A, B, or C, etc." is used, generally, such constructions are intended to be understood by those skilled in the art, e.g., "a system having at least A, B, or C" would include, but are not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will further understand that almost any disjunctive word and / or phrase presenting two or more alternative terms in the description, claims, or drawings should be understood to contemplate the possibility of including one, either, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". From the foregoing, it can be seen that various implementations of the present disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of the present disclosure.Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

1. A method comprising: identifying, by a processor of the network, a particular resource block group (RBG) located at an edge of a downlink (DL) subband that overlaps a guard band (GB) portion of an uplink (UL) subband of a carrier or a physical resource block (PRB) of a carrier in a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 0 allocation bitmap; and Information about the specific RBG is provided to a user equipment (UE) by a processor of the network, the information indicating that the UE uses a non-overlapping portion of the specific RBG that does not overlap with the UL subband or the GB for data transmission of PDSCH FDRA type 0.

2. The method of claim 1, further comprising: allocating, by a processor of the network, a plurality of physical resource blocks from a sequence of physical resource blocks of a carrier to generate a sequence of allocated resource blocks (ARBs) for use by the PDSCH FDRA type 0; as well as The network's processor maps the sequence of allocated resource blocks to virtual resource blocks through virtual resource block (VRB) interleaving, which includes sequentially mapping a first group of virtual resource blocks with even virtual resource block indices in the virtual resource block sequence to the sequence of allocated resource blocks starting from the allocated resource block with the lowest index, and then sequentially mapping a second group of virtual resource blocks with odd indices in the virtual resource block sequence to the remaining allocated resource blocks in the sequence of allocated resource blocks. The method of claim 2 , wherein enabling or disabling the virtual resource block interleaving does not change the allocated resource block sequence.

4. The method of claim 2, wherein a virtual resource block interleaving field of downlink control information (DCI) for PDSCH is used to signal the VRB interleaving for the PDSCH FDRA type 0.

5. The method of claim 1, wherein the PDSCH is scheduled in a repetitive manner, further comprising canceling one or more repetitions in a sub-band full duplex (SBFD) time slot or a non-SBFD time slot, wherein the canceling one or more repetitions comprises: When the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots, canceling one or more repetitions in the time slot; Adapt the UE's frequency domain resource allocation behavior to the SBFD partition format in the first repetition of a slot and remove the repetition of the slot when all resource elements (REs) are available for downlink but subsequent repetitions do not use the same physical resource blocks; or The frequency domain resource allocation behavior of the UE is adapted to the SBFD partition format applicable to each repetition in the time slot.

6. The method of claim 1 , wherein a semi-persistent scheduling (SPS) allocation is scheduled for the PDSCH, further comprising canceling SPS transmission in a sub-band full duplex (SBFD) time slot or a non-SBFD time slot, wherein canceling SPS transmission comprises: When the SBFD partition does not match the first transmission in the SBFD and non-SBFD time slot sequence, the SPS transmission in the time slot is cancelled; Adapt the UE's frequency domain resource allocation behavior to the SBFD partition format for the first SPS transmission after DCI is enabled and remove the duplication of time slots when all resource elements (REs) are available for downlink but subsequent SPS transmissions do not use the same physical resource blocks; or The frequency domain resource allocation behavior of the UE is adapted to the SBFD partition format applicable to each SPS transmission in a timeslot.

7. A method comprising: A processor of the network selects a physical resource block sequence for a carrier of a physical downlink shared channel (PDSCH) frequency domain resource allocation (FDRA) type 1; as well as A virtual resource block to physical resource block (VRB-PRB) mapping is performed by a processor of the network, which maps multiple physical resource blocks in a physical resource block sequence to a virtual resource block sequence, wherein the mapping excludes one or more physical resource blocks in the physical resource block sequence belonging to one or more UL subbands or one or more guard bands.

8. The method of claim 7, wherein performing VRB-PRB mapping comprises using the first roundup(Log2 M) bits to select a subband, and the remaining roundup(log2(N*(N+1) / 2)) bits are encoded as a start and length indicator (SLIV), where N is the width of a maximum DL subband.

9. The method of claim 7, wherein a single contiguous virtual resource block range is indicated by an existing start and length indicator (SLIV) rule, and wherein performing VRB-PRB mapping includes re-indexing a physical resource block sequence for VRB-PRB mapping by excluding physical resource blocks that are indicated to a user equipment (UE) as unavailable for downlink transmission based on a sub-band full-duplex (SBFD) configuration.

10. The method of claim 7, wherein virtual resource block interleaving is enabled for VRB-PRB mapping.

11. The method of claim 10, wherein virtual resource block interleaving is performed for each consecutive physical resource block segment in the physical resource block sequence.

12. The method of claim 11, wherein for each consecutive PRB segment, at least first applying indexes 0 ... K i -1 According to i th The resource block (RB) size Ki of the subband is allocated to virtual resource blocks and physical resource blocks, and then K i Instead of bandwidth size, virtual resource block interleaving is applied to each consecutive physical resource block segment.

13. The method of claim 11, wherein the virtual resource block interleaving is performed for each continuous physical resource block segment, and the RB range 0 ... K of each subband is determined at least by using a high-level configuration of PDSCH FDRA Type-1. i -1 to define the starting and ending positions of the virtual resource blocks.

14. The method of claim 7, wherein virtual resource block interleaving is disabled for VRB-PRB mapping.

15. The method of claim 7, wherein the PDSCH is scheduled in a repetitive manner, further comprising canceling one or more repetitions in a sub-band full duplex (SBFD) time slot or a non-SBFD time slot, wherein the canceling one or more repetitions comprises: canceling one or more repetitions in a time slot when the SBFD partition does not match the first time slot in the sequence of SBFD and non-SBFD time slots; Adapt the UE's frequency domain resource allocation (FDRA) behavior to the first repeated SBFD partition format and remove the duplication of slots when all REs are available for downlink but not all subsequent repetitions use the same physical resource block; or Adapt the UE's FDRA behavior to the SBFD partition format applicable to each repetition in the timeslot.

16. The method of claim 7, wherein a semi-persistent scheduling (SPS) is arranged for the PDSCH, further comprising canceling SPS transmission in a SBFD time slot or a non-SBFD time slot, wherein canceling SPS transmission comprises: When the SBFD partition does not match the first transmission in the SBFD and non-SBFD time slot sequence, canceling the SPS transmission in the time slot; Adapt the UE's FDRA behavior to the SBFD partition format for the first SPS transmission after DCI is enabled and remove the duplication of slots when all REs are available for downlink but not all subsequent SPS transmissions use the same physical resource blocks; or Adapt the UE's FDRA behavior to the SBFD partition format applicable to each SPS transmission in the timeslot.

17. An apparatus implementable in a network, comprising: a transceiver configured to communicate with one or more network nodes of the network; and A processor coupled to the transceiver and configured to perform operations including: determining whether one or more of a set of conditions exist regarding use of a physical downlink shared channel (PDSCH) demodulation reference signaling (DMRS), the set of conditions comprising a wideband setting as a precoding resource block (RB) group (PRG) size can only be selected in a contiguous frequency domain resource allocation (FDRA), and a rule-based dynamic selection of a wideband setting as a PRG size in a Bundle Size Set 1 setting is conditional on an allocated size of the PRG reaching or exceeding half of a bandwidth of a bandwidth part (BWP); and In response to determining that one or more of the set of conditions exist, one or more rules are applied to provide for selecting a bandwidth setting for the PRG size.

18. The apparatus as claimed in claim 17, wherein applying one or more rules performs at least one of the following: Provides configuration for wideband settings so that when allocation of wideband PRGs is contiguous over a sequence of consecutive downlink (DL) sub-band RBs, the PRG size is semi-statically configured; Configure the wideband settings to select the PRG size when the allocation of the wideband PRG is contiguous over a sequence of consecutive DL subband RBs or when the allocation size of the wideband PRG meets or exceeds one of the following: (1) half the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; Provide for dynamic selection of a wideband setting in Bundle Size set 1 based on the allocation size of the wideband PRG meeting or exceeding one of the following conditions: (1) half the BWP bandwidth; (2) the sum of all RBs in the DL BWP; (3) half the DL subband width when the allocation of the wideband PRG is limited to a single subband; or (4) the bandwidth of the full DL subband; and For PDSCH using repetition or semi-persistent scheduling (SPS), the slot that yields the lowest threshold is used to determine the precoder selection, and the precoder is used through repetition.

19. The apparatus as claimed in claim 18, wherein the user equipment (UE) is configured to interpolate only within a subband when the wideband setting is semi-statically configured for the PRG size.

20. The apparatus of claim 17, wherein the PRG size is part of a PRB-BundlingType setting of a radio resource control (RRC) information element (IE), PDSCH DMRS, and wherein the Bundle Size Set 1 setting is a DCI configuration setting for the PDSCH.

Images