Frequency domain resource allocation for data channels in networks enabled with subband full duplexing at the base station

Abstract

A method of resource management for SBFD communication is described The method comprises receiving at least one configuration for at least one of SBFD communication and PDSCH. The at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 0. A size of an RBG is determined based on one of a number of PRBs present in a configured DL-BWP and a number of PRBs present in DL usable PRBs. At least one active RBG is determined for receiving the PDSCH, and the PDSCH is received in the at least one active RBG.

Description

FREQUENCY DOMAIN RESOURCE AEEOCATION FOR DATA CHANNEES IN NETWORKS ENABLED WITH SUBBAND FULL DUPLEXING AT THE BASESTATIONFIELD OF THE INVENTION

[0001] The present invention relates to Subband Full Duplexing (SBFD) communication in a cellular communication network, and more particularly to resource management for SBFD communication.BACKGROUND OF THE INVENTION

[0002] In Subband Full Duplexing (SBFD) communication, a node can simultaneously perform both downlink (DL) operation and uplink (UL) operation within the same carrier frequency. One or more DL subband (SB) and UL subband can be defined within a carrier frequency and the DL and UL operations can be performed in DL SB and UL SB, respectively. A SB is a set of contiguous frequency resources within the carrier. An UL SB and a DL SB can be active simultaneously over a certain time duration within the same carrier frequency. E.g., an SBFD capable base station (BS) can configure active UL and DL SBs to a user equipment (UE) simultaneously over a certain time duration with the same carrier frequency. When an UL SB is indicated as active by the BS to the UE, the UE is expected to transmit in the resources within the UL SB. Similarly, when a DL SB is indicated as active by the BS to the UE, the UE is expected to receive in the resources within the DL SB. The SBs for DL and UL operations can be non-overlapping (as shown in Fig. 1), partially overlapping (as shown in Fig. 2), or fully overlapping (as shown in Fig. 3). For example, in Fig. 1, the DL and UL SBs are nonoverlapping in frequency domain and separated by a guard band. In this illustration, the frequency domain configuration of the slots 2, 3, 4 and 5 are known as “DUD” since an UL SB is sandwiched between 2 DL SBs. D represents the DL SB and U represents the UL SB. Here, the UL SB and the DL SB in slots 2-5 are the active SBs. Instead of this, the configuration could be “DU” or “UD” as well. In the case of a DL SB sandwiched between 2 UL SBs, the configuration will be “UDU”. Further, such slots or symbols with active SBs configured are termed as SBFD slots / symbols. A slot / symbol which does not have both DL and UL active SBs like slot 1 in Fig. 1, is known as a non-SBFD symbol / slot.

[0003] In new radio (NR) technology, various types of frequency domain resource allocations are defined for physical downlink shared channel (PDSCH) and physical uplink shared channel(PUSCH). For example, in type 1 resource allocation for PDSCH, consecutive resource blocks (RBs) are allocated in the DL. As shown in Fig. 1, the DL bandwidth part (BWP) spans across the UL SB as well. Therefore, if the type 1 resource allocation is used in the DL, then the DL resource allocation can overlap with the UL SB as well as the guard band. In that scenario, the user equipment (UE) discards the RBs overlapping with the UL SB and the guard band for PDSCH reception. Hence, the existing resource allocation scheme needs to be enhanced to accommodate such cases where SBs are configured.OBJECTS OF THE INVENTION

[0004] A general objective of the present invention is to perform resource management for SBFD communication.

[0005] Another objective of the present invention is to devise resource allocation mechanism for accommodating scenarios where subbands are configured.

[0006] Another objective of the present invention is to address the impacts of SBFD on various frequency domain resource allocations for PDSCH and PUSCH.SUMMARY OF THE INVENTION

[0007] The summary is provided to introduce aspects related to methods of frequency domain resource allocation for data channels in networks enabled with subband full duplexing at the base station, and the aspects are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.

[0008] In one embodiment, a method of resource management for Sub-band Full Duplexing (SBFD) communication is described. The method comprises receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH). The at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 0. The method further comprises determining, by the at least one first node, a size of a Resource Block Group (RBG)based on one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP), and a number of Physical Resource Blocks (PRBs) present in downlink (DL) usable PRBs. The method further comprises determining, by the at least one first node, at least one active RBG for receiving the PDSCH. The method further comprises receiving, by the at least one first node, the PDSCH in the at least one active RBG.

[0009] In one aspect, the DL usable PRBs comprise at least one PRB in the configured DL- BWP overlapping with a DL subband for SBFD operation in SBFD time resource.

[0010] In one aspect, the at least one configuration is received in the at least one PRB overlapping with DL usable PRBs.

[0011] In one aspect, the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

[0012] In one aspect, the at least one active RBG is determined using a bitmap received by the at least one first node.

[0013] In one aspect, the at least one active RBG is determined from at least one RBG in one of the configured DL-BWP and active DL-BWP.

[0014] In one aspect, the at least one active RBG comprises at least one PRB of the RBG from the at least one active RBG overlapping with at least one of the DL subband for SBFD operation and the DL usable PRBs.

[0015] In one aspect, one of the configured DL-BWP and the DL usable PRBs is divided into a plurality of RBGs.

[0016] In one aspect, the bitmap is received in downlink control information (DCI).

[0017] In one embodiment, a method of resource management for SBFD communication is described. The method comprises receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH). The at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 1 and a resource indicator value (RIV). The method further comprisesdetermining, by the at least one first node, at least one Physical Resource Blocks (PRB) for receiving the PDSCH from the RIV value and one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP), and a number of Physical Resource Blocks (PRBs) present in a downlink (DL) usable PRBs. The method further comprises receiving, by the at least one first node, the PDSCH in the at least one PRB.

[0018] In one aspect, the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

[0019] In one aspect, the DL usable PRBs comprises at least one PRB in the configured DL- BWP overlapping with DL subband in SBFD time resource.

[0020] In one aspect, determining the at least one PRB for receiving the PDSCH comprises determining a starting PRB and number of PRBs.

[0021] In one aspect, the at least one PRB for receiving the PDSCH overlaps with DL usable PRBs.

[0022] In one embodiment, a method of resource management for SBFD communication is described. The method comprises receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Uplink Shared Channel (PUSCH). Tthe at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 0. The method further comprises determining, by the at least one first node, a size of a Resource Block Group (RBG) based on one of a number of Physical Resource Blocks (PRBs) present in a configured Uplink Bandwidth Part (UL-BWP), and a number of Physical Resource Blocks (PRBs) present in uplink (UL) usable PRBs. The method further comprises determining, by the at least one first node, at least one active RBG for transmitting the PUSCH. The method further comprises transmitting, by the at least one first node, the PUSCH in the at least one active RBG.

[0023] In one aspect, the UL usable PRBs comprise at least one PRB in the configured UL- BWP overlapping with UL subband.

[0024] In one aspect, the at least one active RBG is determined using a bitmap received by the at least one first node.

[0025] In one aspect, the at least one active RBG is determined from at least one RBG in one of the configured UL-BWP and active UL-BWP.

[0026] In one aspect, the at least one active RBG comprises at least one PRB of the RBG from the at least one active RBG overlapping with at least one of the UL subband for SBFD operation and the UL usable PRBs.

[0027] In one aspect, one of the configured UL-BWP and the UL usable PRBs is divided into a plurality of RBGs.

[0028] In one aspect, the bitmap is received in downlink control information (DCI).

[0029] In one aspect, the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

[0030] In one embodiment, a method of resource management for SBFD communication is described. The method comprises receiving, by at least one first node, at least one configuration for at least one of SBFD communication and PUSCH. The at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 1 and a resource indicator value (RIV). The method further comprises determining, by the at least one first node, at least one Physical Resource Blocks (PRB) for transmitting the PUSCH from the RIV value and one of a number of Physical Resource Blocks (PRBs) present in a configured Uplink Bandwidth Part (UL-BWP), and a number of Physical Resource Blocks (PRBs) present in an UL usable PRBs. The method further comprises transmitting, by the at least one first node, the PUSCH in the at least one PRB.

[0031] In one aspect, the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

[0032] In one aspect, the UL usable PRBs comprises at least one PRB in the configured UL- BWP overlapping with UL subband in SBFD time resource.

[0033] In one aspect, determining the at least one PRB for transmitting the PUSCH comprises determining a starting PRB and number of PRBs.

[0034] In one aspect, the at least one PRB for transmitting the PUSCH overlaps with UL usable PRBs.

[0035] In one embodiment, a method of resource management for Sub-band Full Duplexing (SBFD) communication is described. The method comprises configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH). The at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 0. The method further comprises signaling, by the at least one second node, at least one active resource block group (RBG) for receiving the PDSCH .The at least one physical resource block (PRB) of an RBG from the at least one active RBG overlaps with at least one of downlink (DL) subband for SBFD operation and DL usable PRBs. The method further comprises transmitting, by the at least one second node, the PDSCH in the at least one active RBG.

[0036] In one aspect, the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

[0037] In one aspect, the DL usable PRBs comprise at least one PRB in configured DL-BWP overlapping with the DL subband for SBFD operation in SBFD time resource.

[0038] In one aspect, configuring the at least one configuration comprises configuring at least one bandwidth part (BWP). The at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

[0039] In one aspect, signalling the at least one active RBG is using a downlink control information (DCI).

[0040] In one aspect, the RBG is from one of configured DL-BWP and DL usable PRB.

[0041] In one aspect, signalling the at least one active RBG is using a bitmap.

[0042] In one aspect, size of the RBG is based on one of a number of PRBs present in a configured Downlink Bandwidth Part (DL-BWP), and a number of PRBs present in the DL usable PRBs.

[0043] In one embodiment, a method of resource management for SBFD communication is described. The method comprises configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH). The at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 1 and a resource indicator value (RIV). The RIV is determined based on one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP) of at least one first node, and a number of Physical Resource Blocks (PRBs) present in a downlink (DL) usable PRBs of the at least one first node. The method further comprises transmitting, by the at least one second node, the PDSCH in at least one PRB overlapping with DL usable PRBs.

[0044] In one aspect, the RIV is determined based on starting PRB for transmission of the PDSCH and number of PRBs for transmitting the PDSCH.

[0045] In one aspect, the number of PRBs for transmitting the PDSCH comprises at least one PRB within at least one of DL subband and DL usable PRBs.

[0046] In one aspect, the starting PRB is within at least one of DL subband and DL usable PRBs.

[0047] In one aspect, the RIV indicates the at least one PRB.

[0048] In one aspect, the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

[0049] In one aspect, the DL usable PRBs comprises at least one PRB in the configured DL- BWP overlapping with DL subband in SBFD time resource.

[0050] In one aspect, configuring the at least one configuration comprises configuring at least one bandwidth part (BWP). The at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

[0051] In one embodiment, a method of resource management for Sub-band Full Duplexing (SBFD) communication is described. The method comprises configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Uplink Shared Channel (PUSCH). The at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 0. The method further comprises signaling, by the at least one second node, at least one active resource block group (RBG) for transmitting the PUSCH. The at least one physical resource block (PRB) of an RBG from the at least one active RBG overlaps with at least one of uplink (UL) subband for SBFD operation and UL usable PRBs. The method further comprises receiving, by the at least one second node, the PUSCH in the at least one active RBG.

[0052] In one aspect, the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

[0053] In one aspect, the UL usable PRBs comprise at least one PRB in configured UL-BWP overlapping with the UL subband in SBFD time resource.

[0054] In one aspect, configuring the at least one configuration comprises configuring at least one bandwidth part (BWP). The at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

[0055] In one aspect, signalling the at least one active RBG is using a downlink control information (DCI).

[0056] In one aspect, the RBG is from one of configured UL-BWP and UL usable PRB.

[0057] In one aspect, signalling the at least one active RBG is using a bitmap.

[0058] In one aspect, size of the RBG is based on one of a number of PRBs present in a configured Uplink Bandwidth Part (UL-BWP), and a number of PRBs present in the UL usable PRBs.

[0059] In one embodiment, a method of resource management for SBFD communication is described. The method comprises configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Uplink Shared Channel(PUSCH). The at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type as type 1 and a resource indicator value (RIV). The RIV is determined based on one of a number of Physical Resource Blocks (PRBs) present in a configured Uplink Bandwidth Part (UL-BWP) of at least one first node, and a number of Physical Resource Blocks (PRBs) present in a Uplink (UL) usable PRBs of the at least one first node. The method further comprises receiving, by the at least one second node, the PUSCH in at least one PRB overlapping with UL usable PRBs.

[0060] In one aspect, the RIV is determined based on starting PRB and number of PRBs for receiving the PUSCH.

[0061] In one aspect, the number of PRBs for receiving the PUSCH comprises at least one PRB within at least one of UL subband and UL usable PRBs.

[0062] In one aspect, the starting PRB is within at least one of UL subband and UL usable PRBs.

[0063] In one aspect, the RIV indicates the at least one PRB.

[0064] In one aspect, the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

[0065] In one aspect, the UL usable PRBs comprises at least one PRB in the configured UL- BWP overlapping with UL subband in SBFD time resource.

[0066] In one aspect, configuring the at least one configuration comprises configuring at least one bandwidth part (BWP). The at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Fig. 1 illustrates non-overlapping subbands for use in Subband Full Duplexing (SBFD) operation.

[0068] Fig. 2 illustrates partially overlapping subbands for use in SBFD operation.

[0069] Fig. 3 illustrates fully overlapping subbands for use in SBFD operation.DETAILED DESCRIPTION OF THE INVENTION

[0070] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.

[0071] Exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. This disclosure may however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of the disclosure to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments of the disclosure, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).

[0072] In NR technology, Physical Downlink Shared Channel (PDSCH) resource allocation is of 2 types: Type 0 and Type 1. In type 0, Downlink Bandwidth Part (DL BWP) is divided into a number of Resource Block Groups (RBGs) where the RBG size is based on the DL BWP size. A bitmap is provided in Downlink Control Information (DCI) to indicate the RBGs in which the UE will receive PDSCH. In type 1, consecutive RBs are allocated in the DL.Impact on type 0

[0073] For a DUD / UD / DU configuration, if the configured DL BWP overlaps with the active UL SB and / guard band, then the actual size of the DL BWP can be obtained after removing the PRBs of the DL BWP overlapping with active UL SB and guard band (if any). This can have an impact on the RBG size since determination of RBG size is dependent on the BWP size. Further, an RBG indicated as active for PDSCH reception can partly fall in the active UL SB. In that scenario, the UE may drop the whole RBG or the part of the RBG that overlaps with theactive UL SB. Therefore, it is evident that some methods / rules need to be defined that can be used to allocate DL resources for type 0. It can be done using different methods.

[0074] A first method requires that the UE uses the number of PRBs in the configured BWP to determine RBG size. A second method requires that the UE updates the BWP size based on the active UL SB configured and determines RBG size based on the size of updated BWP size. The updated BWP size will be the RBs of the DL BWP overlapping with the active DL SB. A third method requires that the UE determines the RBG size for each non-contiguous section of the BWP overlapping with active DL SB, based on the size of the corresponding noncontiguous section.

[0075] The UE divides the BWP (configured or actual) into RBGs and receives indication from the base station (BS) regarding which are the active RBGs. It can be done using the following methods. i) The BS indicates the bitmap for active RBGs using the legacy method. Thus, RBGs indicated as active can overlap with the active UL SB. If an active RBG fully overlaps with active UL SB then, the UE ignores active RBG. If an active RBG overlaps partially with active UL SB, then the UE receives PDSCH for the portion of the RBG not overlapping with active UL SB. ii) If an RBG overlaps, fully or partially with active UL SB then, the BS skips indication for those RBGs Therefore, the bitmap size can be reduced. The bitmap can be indicated separately for non-contiguous SBs. iii) If an RBG overlaps, fully or partially, with active UL SB then the BS indicates that RBG as inactive. iv) If an RBG fully overlaps with active UL SB, then the BS indicates that RBG as inactive. In case of partial overlap between RBG and active UL SB, the BS can indicate the RBG as active.

[0076] All methods stated above are applicable to UDU configuration as well.Impact on type 1

[0077] In the case of type 1, the Resource Indication Value (RIV) in NR is calculated based on the BWP size, length of the DL allocation and start RB. For a DUD / UD / DU configuration, if the configured DL BWP extends beyond the active DL SB, then the actual size of the DL BWP can be obtained by the number of RBs overlapping with the active DL SB. In one method, the DL BWP size is the configured BWP size. In another method, the DL BWP size is the actual BWP size calculated based on the RBs overlapping with the active DL SB. The length of DL allocation can be such that it excludes any PRB which does not overlap with the active DL SB. In another method, the length of the DL allocation can include any PRB that does not overlap with the active DL SB but the UE does not receive DL in those PRBs. E.g., in case of a DUD configuration, the length of the DL resource allocation can span the active UL SB as well, but the UE does not receive any DL within the active UL SB. The start RB can be restricted within the actual DL BWP or go beyond the actual DL BWP. All methods stated above are applicable to UDU configuration as well.

[0078] Impact of SBFD on PUSCH frequency domain resource allocation is described successively.Impact on type 0

[0079] For a DUD / UD / DU configuration, if the configured UL BWP extends beyond the active UL SB, then the actual size of the UL BWP can be obtained as the number of RBs of the configured BWP overlapping with the active UL SB. This can have an impact on the determination of RBG size since it is dependent on the BWP size. Further, an RBG indicated as active for PUSCH transmission can partly fall in the active UL SB. In that scenario, the UE may drop the whole RBG or the part of the RBG that goes beyond the active UL SB. Therefore, it is evident that some methods / rules need to be defined that can be used to allocate UL resources for type 0. It can be done using different methods. A first method requires that the UE uses the number of PRBs in the configured BWP to determine RBG size. A second method requires that the UE updates the BWP size based on the active UL SB configured and determines RBG size based on the size of updated BWP size. The updated BWP size will be the RBs of the UL BWP overlapping with the active UL SB.

[0080] The UE divides the BWP (actual / configured) into RBGs and receives indication from the BS regarding which are the active RBGs. It can be done using the following methods.i) The BS indicates the bitmap for active RBGs using the legacy method. Thus, RBGs indicated as active can overlap with the active DL SBs. If an active RBG fully overlaps with active DL SB then, the UE ignores active RBG. If an active RBG overlaps partially with active DL SB, then the UE transmits PUSCH for the portion of the RBG overlapping with active UL SB. ii) If an RBG overlaps, fully or partially with active DL SB then, the BS skips indication for those RBGs Therefore, the bitmap size can be reduced. iii) If an RBG overlaps, fully or partially, with active DL SB then the BS indicates that RBG as inactive. iv) If an RBG fully overlaps with active DL SB, then the BS indicates that RBG as inactive. In case of partial overlap between RBG and active DL SB, the BS can indicate the RBG as active.

[0081] All methods stated above are applicable to UDU configuration as well.Impact on type 1

[0082] In the case of type 1, the RIV is calculated based on the BWP size, length of the UL allocation and start RB. For a DUD / UD / DU configuration, if the configured UL BWP extends beyond the active UL SB, then the actual size of the UL BWP can be obtained by the number of RBs overlapping with the active UL SB. In one method, the UL BWP size is the configured BWP size. In another method, the UL BWP size is the actual BWP size calculated based on the RBs overlapping with the active UL SB. The length of UL allocation can be such that it is well restricted within the active UL SB. In another method, if the length provided is more than the actual UL BWP, then the UE discards the RBs that fall outside the actual UL BWP. The start RB can be restricted within the actual UL BWP or go beyond the actual UL BWP. All methods stated above are applicable to UDU configuration as well.Impact on type 2

[0083] In the case of type 2, multiple interlaces of resource blocks are defined where each interlace consists of a number of common resource blocks. The number of interlaces is known to the UE. The resource allocation is provided in terms of an RIV which is calculated based onthe starting interlace index, the number of interlaces and the number of contiguous interlace indices.

[0084] For a DUD / UD / DU configuration, if the configured UL BWP extends beyond the active UL SB, then the actual size of the UL BWP can be obtained by the number of RBs overlapping with the active UL SB . In one method, the UL BWP size is the configured BWP size. In another method, the UL BWP size is the actual BWP size calculated based on the RBs overlapping with the UL SB. In NR, the UE expects that the number of common resource blocks in an interlace contained within bandwidth part is no less than “10”. However, in this case, the size of the actual BWP can be such that the number of common resource blocks in an interlace contained within bandwidth part is less than 10. In that case, the value of “10” defined in the specification can be reduced. In another method, the UE does not expect type 2 allocation if active UL SBs are configured to it. All methods stated above are applicable to UDU configuration as well.

[0085] In the above detailed description, reference is made to the accompanying drawings that form a part thereof, and illustrate the best mode presently contemplated for carrying out the invention. However, such description should not be considered as any limitation of scope of the present invention. The structure thus conceived in the present description is susceptible of numerous modifications and variations, all the details may furthermore be replaced with elements having technical equivalence.

Claims

WE CLAIM:

1. A method of resource management for Sub-band Full Duplexing (SBFD) communication, the method comprising: receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH), wherein the at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 0; determining, by the at least one first node, a size of a Resource Block Group (RBG) based on one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP), and a number of PRBs present in downlink (DL) usable PRBs; determining, by the at least one first node, at least one active RBG for receiving the PDSCH; and receiving, by the at least one first node, the PDSCH in the at least one active RBG.

2. The method as claimed in claim 1, wherein the DL usable PRBs comprise at least one PRB in the configured DL-BWP overlapping with a DL subband for SBFD operation in SBFD time resource.

3. The method as claimed in claim 1, wherein the at least one configuration is received in the at least one PRB overlapping with DL usable PRBs.

4. The method as claimed in claim 1, wherein the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

5. The method as claimed in claim 1, wherein the at least one active RBG is determined using a bitmap received by the at least one first node.

6. The method as claimed in claim 1, wherein the at least one active RBG is determined from at least one RBG in one of the configured DL-BWP and active DL-BWP.

7. The method as claimed in claim 1, wherein the at least one active RBG comprises at least one PRB of the RBG from the at least one active RBG overlapping with at least one of the DL subband for SBFD operation and the DL usable PRBs.

8. The method as claimed in claim 1, wherein one of the configured DL-BWP and the DL usable PRBs is divided into a plurality of RBGs.

9. The method as claimed in claim 5, wherein the bitmap is received in downlink control information (DCI).

10. A method of resource management for SBFD communication, the method comprising: receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH), wherein the at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 1 and a resource indicator value (RIV); determining, by the at least one first node, at least one Physical Resource Blocks (PRB) for receiving the PDSCH from the RIV value and one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP), and a number of PRBs present in a downlink (DL) usable PRBs, and receiving, by the at least one first node, the PDSCH in the at least one PRB.

11. The method as claimed in claim 10, wherein the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

12. The method as claimed in claim 10, wherein the DL usable PRBs comprises at least one PRB in the configured DL-BWP overlapping with DL subband in SBFD time resource.

13. The method as claimed in claim 10, wherein determining the at least one PRB for receiving the PDSCH comprises determining a starting PRB and number of PRBs.

14. The method as claimed in claim 10, wherein the at least one PRB for receiving the PDSCH overlaps with DL usable PRBs.

15. A method of resource management for SBFD communication, the method comprising: receiving, by at least one first node, at least one configuration for at least one of SBFD communication and Physical Uplink Shared Channel (PUSCH), wherein the at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 0; determining, by the at least one first node, a size of a Resource Block Group (RBG) based on one of a number of Physical Resource Blocks (PRBs) present in a configured Uplink Bandwidth Part (UL-BWP), and a number of PRBs present in uplink (UL) usable PRBs; determining, by the at least one first node, at least one active RBG for transmitting the PUSCH; and transmitting, by the at least one first node, the PUSCH in the at least one active RBG.

16. The method as claimed in claim 15, wherein the UL usable PRBs comprise at least one PRB in the configured UL-BWP overlapping with UL subband.

17. The method as claimed in claim 15, wherein the at least one active RBG is determined using a bitmap received by the at least one first node.

18. The method as claimed in claim 15, wherein the at least one active RBG is determined from at least one RBG in one of the configured UL-BWP and active UL-BWP.

19. The method as claimed in claim 15, wherein the at least one active RBG comprises at least one PRB of the RBG from the at least one active RBG overlapping with at least one of the UL subband for SBFD operation and the UL usable PRBs.

20. The method as claimed in claim 15, wherein one of the configured UL-BWP and the UL usable PRBs is divided into a plurality of RBGs.

21. The method as claimed in claim 17, wherein the bitmap is received in downlink control information (DCI).

22. The method as claimed in claim 15, wherein the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

23. A method of resource management for SBFD communication, the method comprising: receiving, by at least one first node, at least one configuration for at least one of SBFD communication and PUSCH, wherein the at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 1 and a resource indicator value (RIV); determining, by the at least one first node, at least one Physical Resource Blocks (PRB) for transmitting the PUSCH from the RIV value and one ofa number of Physical Resource Blocks (PRBs) present in a configured Uplink Bandwidth Part (UL-BWP), and a number of PRBs present in an UL usable PRBs; and transmitting, by the at least one first node, the PUSCH in the at least one PRB.

24. The method as claimed in claim 23, wherein the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

25. The method as claimed in claim 23, wherein the UL usable PRBs comprises at least one PRB in the configured UL-BWP overlapping with UL subband in SBFD time resource.

26. The method as claimed in claim 23, wherein determining the at least one PRB for transmitting the PUSCH comprises determining a starting PRB and number of PRBs.

27. The method as claimed in claim 23, wherein the at least one PRB for transmitting the PUSCH overlaps with UL usable PRBs.

28. A method of resource management for Sub-band Full Duplexing (SBFD) communication, the method comprising: configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH), wherein the at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 0; signaling, by the at least one second node, at least one active resource block group (RBG) for receiving the PDSCH,wherein the at least one physical resource block (PRB) of an RBG from the at least one active RBG overlaps with at least one of downlink (DL) subband for SBFD operation and DL usable PRBs; and transmitting, by the at least one second node, the PDSCH in the at least one active RBG.

29. The method as claimed in claim 28, wherein the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

30. The method as claimed in claim 28, wherein the DL usable PRBs comprise at least one PRB in configured DL-BWP overlapping with the DL subband for SBFD operation in SBFD time resource.

31. The method as claimed in claim 28, wherein configuring the at least one configuration comprises configuring at least one bandwidth part (BWP), wherein the at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

32. The method as claimed in claim 28, wherein signalling the at least one active RBG is using a downlink control information (DCI).

33. The method as claimed in claim 28, wherein the RBG is from one of configured DL- BWP and DL usable PRB.

34. The method as claimed in claim 28, wherein signalling the at least one active RBG is using a bitmap.

35. The method as claimed in claim 28, wherein size of the RBG is based on one of a number of PRBs present in a configured Downlink Bandwidth Part (DL-BWP), and a number of PRBs present in the DL usable PRBs.

36. A method of resource management for SBFD communication, the method comprising:configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Downlink Shared Channel (PDSCH), wherein the at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PDSCH comprises a resource allocation type of the PDSCH as type 1 and a resource indicator value (RIV), wherein the RIV is determined based on one of a number of Physical Resource Blocks (PRBs) present in a configured Downlink Bandwidth Part (DL-BWP) of at least one first node, and a number of PRBs present in a downlink (DL) usable PRBs of the at least one first node, and transmitting, by the at least one second node, the PDSCH in at least one PRB overlapping with DL usable PRBs.

37. The method as claimed in claim 36, wherein the RIV is determined based on starting PRB for transmission of the PDSCH and number of PRBs for transmitting the PDSCH.

38. The method as claimed in claim 37, wherein the number of PRBs for transmitting the PDSCH comprises at least one PRB within at least one of DL subband and DL usable PRBs.

39. The method as claimed in claim 37, wherein the starting PRB is within at least one of DL subband and DL usable PRBs.

40. The method as claimed in claim 36, wherein the RIV indicates the at least one PRB.

41. The method as claimed in claim 36, wherein the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

42. The method as claimed in claim 36, wherein the DL usable PRBs comprises at least one PRB in the configured DL-BWP overlapping with DL subband in SBFD time resource.

43. The method as claimed in claim 36, wherein configuring the at least one configuration comprises configuring at least one bandwidth part (BWP), wherein the at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

44. A method of resource management for Sub-band Full Duplexing (SBFD) communication, the method comprising: configuring, by at least one second node, at least one configuration for at least one of SBFD communication and Physical Uplink Shared Channel (PUSCH), wherein the at least one configuration for the SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type of the PUSCH as type 0; signaling, by the at least one second node, at least one active resource block group (RBG) for transmitting the PUSCH, wherein the at least one physical resource block (PRB) of an RBG from the at least one active RBG overlaps with at least one of uplink (UL) subband for SBFD operation and UL usable PRBs; and receiving, by the at least one second node, the PUSCH in the at least one active RBG.

45. The method as claimed in claim 44, wherein the type of the at least one subband comprises one of DL subband, UL subband, and guard band.

46. The method as claimed in claim 44, wherein the UL usable PRBs comprise at least one PRB in configured UL-BWP overlapping with the UL subband in SBFD time resource.

47. The method as claimed in claim 44, wherein configuring the at least one configuration comprises configuring at least one bandwidth part (BWP),wherein the at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

48. The method as claimed in claim 44, wherein signalling the at least one active RBG is using a downlink control information (DCI).

49. The method as claimed in claim 44, wherein the RBG is from one of configured UL- BWP and UL usable PRB.

50. The method as claimed in claim 44, wherein signalling the at least one active RBG is using a bitmap.

51. The method as claimed in claim 44, wherein size of the RBG is based on one of a number of PRBs present in a configured Uplink Bandwidth Part (UL-BWP), and a number of PRBs present in the UL usable PRBs.

52. A method of resource management for SBFD communication, the method comprising: configuring, by at least one second node, at least one configuration for at least one ofSBFD communication and Physical Uplink Shared Channel (PUSCH), wherein the at least one configuration for SBFD communication comprises indication of at least one frequency location of at least one subband for SBFD operation and type of the at least one subband, and the at least one configuration for PUSCH comprises a resource allocation type as type 1 and a resource indicator value (RIV), wherein the RIV is determined based on one of a number of Physical Resource Blocks (PRBs) present in a configuredUplink Bandwidth Part (UL-BWP) of at least one first node, and a number of PRBs present in a Uplink (UL) usable PRBs of the at least one first node; andreceiving, by the at least one second node, the PUSCH in at least one PRB overlapping with UL usable PRBs.

53. The method as claimed in claim 52, wherein the RIV is determined based on starting PRB and number of PRBs for receiving the PUSCH.

54. The method as claimed in claim 53, wherein the number of PRBs for receiving the PUSCH comprises at least one PRB within at least one of UL subband and UL usable PRBs.

55. The method as claimed in claim 53, wherein the starting PRB is within at least one of UL subband and UL usable PRBs.

56. The method as claimed in claim 52, wherein the RIV indicates the at least one PRB.

57. The method as claimed in claim 52, wherein the type of the at least one subband comprises downlink (DL) subband, uplink (UL) subband, and guard band.

58. The method as claimed in claim 52, wherein the UL usable PRBs comprises at least one PRB in the configured UL-BWP overlapping with UL subband in SBFD time resource.

59. The method as claimed in claim 52, wherein configuring the at least one configuration comprises configuring at least one bandwidth part (BWP), wherein the at least one BWP is one of downlink BWP (DL-BWP) and uplink BWP (UL-BWP).

Images