METHOD AND APPARATUS FOR ALLOCATING FREQUENCY DOMAIN RESOURCES IN NON-CONTIGUOUS SUB-BANDS IN FULL SUB-BAND DUPLEX IN MOBILE COMMUNICATIONS

Description

1 / 27 METHOD AND APPARATUS FOR ALLOCATING FREQUENCY DOMAIN RESOURCES IN NON-CONTIGUOUS SUB-BANDS IN FULL SUB-BAND DUPLEX IN MOBILE COMMUNICATIONS CROSS-REFERENCE TO RELATED PATENT APPLICATION(S)

[0001] The present disclosure is part of a non-provisional application claiming the benefit of priority of U.S. Patent Application No. 63 / 500,929, filed May 9, 2023, the contents of which are incorporated herein by reference in their entirety. FIELD OF TECHNIQUE

[0002] The present disclosure generally relates to mobile communications and, more particularly, to frequency domain resource allocation (FDRA) in non-contiguous sub-bands in full-duplex sub-band (SBFD) in relation to mobile communications handsets. BACKGROUND

[0003] Unless otherwise indicated in this document, approaches described in this section are not prior art for the claims listed below and are not admitted as prior art by inclusion in this section.

[0004] In fifth-generation (5G) New Radio (NR) mobile communications, full-duplex sub-band (SBFD) technology is introduced. Generally, non-contiguous sub-bands can be configured in one slot. For example, two non-contiguous downlink sub-bands and one uplink sub-band between the non-contiguous downlink sub-bands are configured in one slot, or two non-contiguous uplink sub-bands and one downlink sub-band between the non-contiguous uplink sub-bands are configured in one slot.

[0005] However, considering both physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH), legacy frequency domain resource allocation (FDRA), especially the allocation type of Petition 870250101161, dated 05 / 11 / 2025, page 9 / 46 2 / 27 Resource 1 using a Resource Indication Value (RIV) to configure a set of virtual resource blocks (VRBs) may not be suitable for resource allocation in non-contiguous sub-bands in SBFD. More specifically, there is no solution for allocating VRBs and physical resource blocks (PRBs) configured in legacy FDRA in non-contiguous sub-bands in SBFD.

[0006] Therefore, how to apply FDRA in non-contiguous sub-bands in SBFD and allocate VRBs and PRBs correctly in non-contiguous sub-bands in SBFD have become important issues in the newly developed wireless communication network. Therefore, there is a need to provide appropriate schemes for applying FDRA in non-contiguous sub-bands in SBFD. SUMMARY

[0007] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described in this document. Selection implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0008] One objective of the present disclosure is to propose solutions or schemes that address the aforementioned issues relating to frequency domain resource allocation (FDRA) in non-contiguous sub-bands in full-duplex sub-band (SBFD) with respect to mobile communications devices.

[0009] In one aspect, a method may involve an appliance receiving an SBFD configuration and an FDRA configuration from a network node. The SBFD configuration includes sub-bands that are non-contiguous within a slot, and the FDRA configuration includes a plurality of resource blocks (RBs). The method may also involve the appliance receiving information from the network node. The information indicates to the Petition 870250101161, dated 05 / 11 / 2025, page 10 / 46 3 / 27 device that a subset of RBs outside of non-contiguous sub-bands is excluded.

[0010] In one aspect, a method may include an apparatus transmitting an SBFD configuration and an FDRA configuration to a user equipment (UE). The SBFD configuration includes sub-bands that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. The method may also include the apparatus transmitting information to the UE. The information indicates to the UE that a subset of the RBs outside the non-contiguous sub-bands is excluded.

[0011] In one aspect, an apparatus may comprise a transceiver that, during operation, communicates wirelessly with at least one network node of a wireless network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising receiving, through the transceiver, an SBFD configuration and an FDRA configuration from the network node. The SBFD configuration includes sub-bands that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. The processor may also perform operations comprising receiving, through the transceiver, information from the network node. The information indicates to the apparatus that a subset of the RBs outside the non-contiguous sub-bands is excluded.

[0012] In one aspect, an apparatus may comprise a transceiver that, during operation, communicates wirelessly with at least one UE of a wireless network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising transmitting, through the transceiver, an SBFD configuration and an FDRA configuration to the UE. The SBFD configuration includes sub-bands that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. The processor may also perform operations comprising Petition 870250101161, dated 05 / 11 / 2025, page 11 / 46 4 / 27 transmit, via the transceiver, information to the UE. The information indicates to the UE that a subset of the RBs outside the non-contiguous sub-bands is excluded.

[0013] It is worth noting that, although the description provided in this document may be in the context of certain radio access technologies, networks and network topologies such as Long Term Evolution (LTE), Advanced LTE, Advanced LTE Pro, Fifth Generation (5G), New Radio (NR), Internet of Things (IoT) and Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT) and sixth generation (6G), the concepts, schemes and any variations / derivatives thereof proposed may be implemented in, for and by other types of radio access technologies, networks and network topologies. Thus, the scope of this disclosure is not limited to the examples described in this document. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are included to provide further understanding of the disclosure and are incorporated into this document and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciated that the drawings are not necessarily to scale as some components may be shown as being out of proportion to the actual implementation size in order to clearly illustrate the concept of the present disclosure.

[0015] FIGURE 1 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0016] FIGURE 2 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0017] FIGURE 3 is a diagram representing an example scenario in schematics according to implementations of the present disclosure. Petition 870250101161, dated 05 / 11 / 2025, page 12 / 46 5 / 27

[0018] FIGURE 4 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0019] FIGURE 5 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0020] FIGURE 6 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0021] FIGURE 7 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0022] FIGURE 8 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0023] FIGURE 9 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0024] FIGURE 10 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0025] FIGURE 11 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0026] FIGURE 12 is a diagram representing an example scenario in schematics according to implementations of the present disclosure.

[0027] FIGURE 13 is a block diagram of an example communication system according to an implementation of the present disclosure.

[0028] FIGURE 14 is a flowchart of an example process according to an implementation of the present disclosure.

[0029] FIGURE 15 is a flowchart of an example process. Petition 870250101161, dated 05 / 11 / 2025, page 13 / 46 6 / 27 in accordance with an implementation of this disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

[0030] Detailed embodiments and implementations of the claimed materials are disclosed in this document. However, it should be understood that the embodiments and implementations disclosed are only illustrative of the claimed materials, which may be embodied in various forms. The present disclosure, however, may be embodied in many different forms and should not be interpreted as limited to the exemplary embodiments and implementations set forth in this document. In particular, these exemplary embodiments and implementations are provided so that the description of the present disclosure may be thorough and complete and fully convey the scope of the present disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the embodiments and implementations presented. Overview

[0031] Implementations according to the present disclosure relate to various techniques, methods, schemes and / or solutions relating to frequency domain resource allocation (FDRA) in non-contiguous sub-bands in full-duplex sub-band (SBFD) with respect to devices in mobile communications. According to the present disclosure, various possible solutions can be implemented separately or jointly. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one or another combination.

[0032] With respect to the present disclosure, allocation of resource blocks (RBs) across non-contiguous sub-bands (SBs) in SBFD may be permitted for FDRA, especially for FDRA type 1. In particular, allocation of RBs across non-contiguous sub-bands in SBFD may be achieved by excluding RBs that fall outside the non-contiguous sub-bands in SBFD. Petition 870250101161, dated 05 / 11 / 2025, page 14 / 46 7 / 27

[0033] FIGURE 1 illustrates an example scenario 100 in schematics according to implementations of the present disclosure. Scenario 100 includes at least one network node and one UE, which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Scenario 100 illustrates the actual network structure. The UE may connect to the network side. The network side may comprise one or more network nodes.

[0034] In some embodiments, the network node can transmit an SBFD configuration and an FDRA configuration to the UE. The SBFD configuration can include SBs that are non-contiguous within a slot, and the FDRA configuration can include a plurality of RBs. In other words, the SBFD configuration can include parameters indicating the non-contiguous SBs within a slot, and the FDRA configuration can include parameters indicating the RBs. The network node can transmit information to the UE, and the information can indicate to the UE that a subset of the RBs outside the non-contiguous SBs should be excluded. After receiving the SBFD configuration, the FDRA configuration, and the information, the UE can apply the SBFD configuration and the FDRA configuration, and can determine that the subset of RBs outside the non-contiguous SBs should be excluded.

[0035] FIGURE 2 illustrates an example scenario 200 in schemes according to implementations of the present disclosure. In some embodiments, the SBFD configuration may include parameters indicating two non-contiguous downlink (DL) SBs and one uplink (UL) SB within a slot, and the UL SB is between the DL SBs. The FDRA configuration may include parameters indicating the RBs. The information may indicate to the UE that the subset of RBs outside the non-contiguous DL SBs is excluded. In other words, in these embodiments, the subset of RBs falling within the UL SB is excluded.

[0036] In some implementations, exclusion of the subset of RBs can be achieved by reindexing (i.e., renumbering) blocks of Petition 870250101161, dated 05 / 11 / 2025, p. 15 / 46 8 / 27 virtual resource blocks (VRBs) and physical resource blocks (PRBs) corresponding to the RBs. FIGURE 3 illustrates an example scenario in schematics according to implementations of the present disclosure. For example, RBs include VRBs and / or PRBs from a bandwidth portion (BWP) of DL, and the VRBs and / or PRBs are reindexed to exclude VRBs and / or PRBs outside the non-contiguous DL SBs. In other words, VRBs and / or PRBs from the DL BWP are reindexed to exclude VRBs and / or PRBs that fall within the UL SB (and guard band(s) – if guard band is configured) that is between the non-contiguous DL SBs.

[0037] In these implementations, to exclude VRBs falling within the UL SB (i.e., the original VRBs #4 and #5), the original VRBs #0 to #3 and #6 to #9 are reindexed to VRBs #0 to #7 such that the reindexed VRBs become contiguous across the non-contiguous DL SBs. To exclude PRBs falling within the UL SB (i.e., the original PRBs #4 and #5), the original PRBs #0 to #3 and #6 to #9 are reindexed to PRBs #0 to #7 such that the reindexed PRBs become contiguous across the non-contiguous DL SBs. Therefore, the VRB-to-PRB merging procedure can avoid referencing PRBs outside the DL SBs.

[0038] When reindexing of VRBs and / or PRBs is applied in a slot with non-contiguous DL SBs, a subset of bits in the frequency domain allocation field provides (i.e., is used for) resource allocation. Different resource allocation types (e.g., type '0', type '1', and type 'dynamicswitch' configured by the resourceAllocation top-layer parameter specified in the 3GPP specification) may correspond to different frequency domain allocation field formats.

[0039] In some implementations, considering resource allocation type '1', the information may be downlink control information (DCI) including a frequency domain assignment field, and: (1) a first subset of bits of the frequency domain assignment field may be Petition 870250101161, dated 05 / 11 / 2025, page 16 / 46 9 / 27 is used to indicate a resource allocation; and (2) a second subset of bits from the frequency domain allocation field is not used for resource allocation. In some cases, (1) a first number of bits from the first subset of bits corresponds to a number of RBs that are across the SBs; and (2) a second number of bits from the second subset of bits corresponds to a difference between the first number of bits from the first subset of bits and a third number of bits corresponding to a number of all RBs in a BWP.

[0040] FIGURE 4 illustrates an example scenario 400 in schemes according to implementations of the present disclosure. For example, considering the frequency domain assignment field of resource allocation type '1', X1 represents the bit field length corresponding to all RBs in DL BWP (i.e., X1 represents the third bit number corresponding to the number of all RBs in DL BWP), and Y1 represents the number of most significant bits (MSBs) (among the X1 bits) of the frequency domain assignment field that provide (i.e., are used for) the resource allocation (i.e., Y1 represents the first bit number of the first subset of bits that corresponds to the number of RBs that are across DL SBs).Therefore, the remaining least significant bits (LSBs) (X1 - Y1) of the frequency domain allocation field are not used for resource allocation (i.e., (X1 - Y1) represents the second bit number of the second bit subset that corresponds to the difference between the first bit number of the first bit subset and the third bit number corresponding to the number of all RBs in DL BWP).

[0041] In some cases, U = \log2(N^'WP'W^ + 1) / 2)] ...(1) Y1 = Σ?-™^,^·™·!^·™' + 1) / 2)] ...(2) ΛΤ DL,BWP ss I 1-)1-) DT ΒΓ1Γ) Μ^Μ zz where NRB is the number of RBs in the DL BWP, NRB is the number of RBs in the ith DL SB, and NDL_SB is the number of DL SB.

[0042] In some implementations, considering the type of Petition 870250101161, dated 05 / 11 / 2025, p. 17 / 46 10 / 27 resource allocation '0', the information may be a DCI including a frequency domain assignment field, and: (1) a first subset of bits of the frequency domain assignment field may be used to indicate a resource allocation; and (2) a second subset of bits of the frequency domain assignment field is not used for resource allocation. In some cases, (1) a first number of bits of the first subset of bits corresponds to a number of resource block groups (RBGs) that are across the SBs; and (2) a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RGBs in a BWP.

[0043] FIGURE 5 illustrates an example scenario 500 in schemes according to implementations of the present disclosure. For example, considering the frequency domain assignment field of resource allocation type '0', X0 represents the bit field length corresponding to all RBGs in DL BWP (i.e., X0 represents the third bit number corresponding to the number of all RBs in DL BWP), and Y0 represents the number of MSBs (among the X0 bits) of the frequency domain assignment field that provide (i.e., are used for) the resource allocation (i.e., Y0 represents the first bit number of the first bit subset that corresponds to the number of RBGs that are across DL SBs).Therefore, the remaining (X0 - Y0) LSBs of the frequency domain allocation field are not used for resource allocation (i.e., (X0 - Y0) represents the second bit number of the second bit subset that corresponds to the difference between the first bit number of the first bit subset and the third bit number corresponding to the number of all RGBs in DL BWP).

[0044] In some cases, Ύ0 = |(wXí') + (^(^ / 001)) / 1]... (3) =Σ*><-» [(n“-sw+ (N^BΛ / οά 1)) / l] ...(4) where Npaypan)° is the size of DL BWP, N^p0 is the starting RB of Petition 870250101161, dated 05 / 11 / 2025, p. 18 / 46 11 / 27 DL BWP, ^^BSB, is the number of RBs in the i-th DL SB, Nfí^o^ is the starting RB of the i-th DL SB, and P is the number of RBs in each RBG.

[0045] FIGURE 6 illustrates an example scenario 600 in schemes according to implementations of the present disclosure. In some implementations, considering the frequency domain assignment field corresponding to the resource allocation type 'dynamicswitch' (i.e., both resource allocation type '0' and type '1' are configured), the frequency domain assignment field can be interpreted as: (1) the MSB of the frequency domain assignment field is used to indicate the resource allocation type (i.e., '0' for type '0' and '1' for type '1'); (2) when resource allocation type '0' is indicated (i.e., the MSB has bit value '0'), the next Y0 bits of the frequency domain allocation field provide (i.e., are used for) resource allocation and the remaining ([max(X0,X1) + 1] — V0) LSBs of the frequency domain allocation field are not used for resource allocation;(3) When resource allocation type '1' is specified (i.e., the MSB has bit value '1'), the next Y1 bits of the frequency domain assignment field provide (i.e., are used for) resource allocation and the remaining ([max(X0, X1) + 1] — V1) LSBs of the frequency domain assignment field are not used for resource allocation. In these implementations, the calculations of X0, Y0, X1 and Y1 may refer to formulas (1) to (4) shown above. It should be noted that max(X0,X1) is defined as the maximum of X0 and X1.

[0046] FIGURE 7 illustrates an example scenario 700 in schemes according to implementations of the present disclosure. In some embodiments, the SBFD configuration may include parameters indicating two non-contiguous UL SBs and a DL SB between the UL SBs within a slot. The FDRA configuration may include parameters indicating the RBs. The information may indicate to the UE that the subset of RBs outside the non-contiguous UL SBs is excluded. In these embodiments, the subset of RBs that falls within the DL SB is excluded. Petition 870250101161, dated 05 / 11 / 2025, p. 19 / 46 12 / 27 (and guard band(s) - if guard band is configured) is excluded.

[0047] In some implementations, exclusion of the subset of RBs can be achieved by reindexing (i.e., renumbering) VRBs and PRBs corresponding to the RBs. FIGURE 8 illustrates an example 800 scenario in schemas according to implementations of the present disclosure. For example, RBs include VRBs and / or PRBs from a UL BWP, and VRBs and / or PRBs are reindexed to exclude VRBs and / or PRBs outside the non-contiguous UL SBs. In other words, VRBs and / or PRBs from the UL BWP are reindexed to exclude VRBs and PRBs that fall within the DL SB that is between the non-contiguous UL SBs.

[0048] In these implementations, to exclude VRBs falling outside the DL SB (i.e., the original VRBs #4 and #5), the original VRBs #0 to #3 and #6 to #9 are reindexed to VRBs #0 to #7 in such a way that the reindexed VRBs become contiguous across the non-contiguous UL SBs. To exclude PRBs falling outside the DL SB (i.e., the original PRBs #4 and #5), the original PRBs #0 to #3 and #6 to #9 are reindexed to PRBs #0 to #7 in such a way that the reindexed PRBs become contiguous across the non-contiguous UL SBs. Therefore, the VRB-to-PRB merging procedure can avoid referencing PRBs outside the UL SBs.

[0049] When reindexing of VRBs and / or PRBs is applied in a slot with non-contiguous UL SBs, a subset of bits in the frequency domain allocation field provides (i.e., is used for) resource allocation. Different resource allocation types (e.g., type '0', type '1', and type 'dynamicswitch' configured by the resourceAllocation top-layer parameter specified in the 3GPP specification) may correspond to different frequency domain allocation field formats.

[0050] In some implementations, considering resource allocation type '1' and frequency hopping function being disabled, the information may be a DCI including a frequency domain assignment field, and: (1) a first subset Petition 870250101161, dated 05 / 11 / 2025, page 20 / 46 (1) 13 / 27 bits of the frequency domain assignment field can be used to indicate a resource allocation; and (2) a second subset of bits of the frequency domain assignment field is not used for resource allocation. In some cases, (1) a first number of bits of the first subset of bits corresponds to a number of RBs that are across the SBs; and (2) a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RBs in a BWP.

[0051] FIGURE 9 illustrates an example scenario 900 in schemes according to implementations of the present disclosure. For example, considering the frequency domain assignment field of resource allocation type '1' and the frequency hopping function being disabled, X1 represents the bit field length corresponding to all RBs in UL BWP (i.e., X1 represents the third bit number corresponding to the number of all RBs in UL BWP), and Y1 represents the number of MSBs (among the X1 bits) of the frequency domain assignment field that provide (i.e., are used for) resource allocation (i.e., Y1 represents the first bit number of the first subset of bits that corresponds to the number of RBs that are across UL SBs).Therefore, the remaining (X1 - Y1) LSBs of the frequency domain allocation field are not used for resource allocation (i.e., (X1 - Y1) represents the second bit number of the second bit subset that corresponds to the difference between the first bit number of the first bit subset and the third bit number corresponding to the number of all RBs in UL BWP).

[0052] In some cases, X1 = \log^'BW\N^ + 1) / 2)1 ---(5) Y1 = Σ^!^^™'^^^ + 1) / 2)1 ---(6) λτ UL,BWP ✓ z -. 1-)1-) ttt nrm :U!j—SB,Í sz where NRb is the number of RBs in the UL BWP, NRb is the number of RBs in the i—th UL SB, and NUl-Sb is the number of UL SBPetition 870250101161, dated 11 / 05 / 2025, p. 21 / 46 14 / 27

[0053] In some implementations, considering the frequency domain assignment field corresponding to resource allocation type '1' and frequency hopping function being enabled, the information may be a DCI including a frequency domain assignment field, and: (1) a first subset of bits of the frequency domain assignment field may be used to indicate a resource allocation; and (2) a second subset of bits of the frequency domain assignment field is not used for resource allocation. In some cases, (1) a first number of bits of the first subset of bits corresponds to a number of RBs that are across the SBs; and (2) a third number of bits corresponds to a number of all RBs in a BWP.

[0054] FIGURE 10 illustrates an example scenario 1000 in schemes according to implementations of the present disclosure. For example, considering the frequency domain assignment field of resource allocation type '1' and frequency hopping function being enabled, X1 represents the bit field length corresponding to all RBs in UL BWP (i.e., X1 represents the third bit number corresponding to the number of all RBs in UL BWP), Y1 represents the number of MSBs (among the X1 bits) of the frequency domain assignment field that provide (i.e., are used for) the resource allocation (i.e., Y1 represents the first bit number of the first subset of bits that corresponds to the number of RBs that are across UL SBs), and NUL_ho= MSBs of the frequency domain assignment field are used to indicate a frequency offset of the frequency hopping function.Therefore, (X1 — Y1 — NUL_ho=) remaining LSBs of the frequency domain assignment field are not used for resource allocation (that is, (X1 — Y1 — NUL_ho=) represents a second bit number of the second bit subset). In these implementations, the calculations of X1 and Y1 can refer to formulas (5) and (6) shown above.

[0055] In some modalities, considering the field of Petition 870250101161, dated 05 / 11 / 2025, page 22 / 46 15 / 27 Frequency domain assignment corresponding to resource allocation type 0, the information may be a DCI including a frequency domain assignment field, and: (1) a first subset of bits of the frequency domain assignment field may be used to indicate a resource allocation; and (2) a second subset of bits of the frequency domain assignment field is not used for resource allocation. In some cases, (1) a first number of bits of the first subset of bits corresponds to a number of RGBs that are across the SBs; and (2) a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RGBs in a BWP. [005 6] FIGURE 11 illustrates an example scenario 1100 in schemes according to implementations of the present disclosure. For example, considering the frequency domain assignment field of resource allocation type '0', X0 represents the bit field length corresponding to all RGBs in UL BWP (i.e., X0 represents the third bit number corresponding to the number of all RBs in UL BWP), and Y0 represents the number of MSBs (among the X0 bits) of the frequency domain assignment field that provide (i.e., are used for) the resource allocation (i.e., Y0 represents the first bit number of the first bit subset that corresponds to the number of RGBs that are across UL SBs).Therefore, the remaining (X0 - Y0) LSBs of the frequency domain allocation field are not used for resource allocation (i.e., (X0 - Y0) represents the second bit number of the second bit subset that corresponds to the difference between the first bit number of the first bit subset and the third bit number corresponding to the number of all RGBs in UL BWP).

[0057] In some cases, Ύ0 = [(Ν^“η)* + ( N^mod P)) / p] ...(7) rc = Σ / (V / + ( N^.t / od P)) / P] ...(8) Petition 870250101161, dated 05 / 11 / 2025, p. 23 / 46 16 / 27 where N^'anho is the size of UL BWP, N^p0 is the starting RB of UL BWP, Nm~SB'1 is the number of RBs in the i-th UL SB, N^-Som is the starting RB of the i-th UL SB, and P is the number of RBs in each RBG.

[0058] FIGURE 12 illustrates an example scenario 1200 in schemes according to implementations of the present disclosure. In some implementations, considering the frequency domain assignment field corresponding to the resource allocation type 'dynamicswitch' (i.e., both resource allocation type '0' and type '1' are configured), the frequency domain assignment field can be interpreted as: (1) the MSB of the frequency domain assignment field is used to indicate the resource allocation type (i.e., '0' for type '0' and '1' for type '1'); (2) when resource allocation type '0' is indicated (i.e., the MSB has bit value '0'), the next Y0 bits of the frequency domain allocation field provide (i.e., are used for) resource allocation and the remaining ([max(X0,X1) + 1] — V0) LSBs of the frequency domain allocation field are not used for resource allocation;(3) when the resource allocation type '1' is indicated (i.e., the MSB has bit value '1'), the next Y1 bits of the frequency domain assignment field provide (i.e., are used for) the resource allocation and the remaining ([max(X0, X1) + 1] — V1) LSBs of the frequency domain assignment field are not used for resource allocation. In these implementations, the calculations of X0, Y0, X1 of Y1 may refer to formulas (5) to (8) shown above. It should be noted that max(X0,X1) is defined as the maximum of X0 and X1.

[0059] In some embodiments, the encoding rule for a resource allocation type '1' RIV may be adjusted due to PRB reindexing. In some implementations, the encoding rule for RIV is adjusted as follows: I Ndl-sb I If (LRb — 1) < p!—J, then RIV = N^-SBx (LRb — 1) + RB^ / o Petition 870250101161, dated 05 / 11 / 2025, page 24 / 46 17 / 27 Otherwise R1V = Nbb-sbX (NbBTsb- Lrb + 1) + ΙH^ - 1 - RBlnici*) where 1 < Lrb< N^B-SB— RBinício, NrB-sbé is the number of RBs in the DL SBs, Lrb is the number of contiguous RB allocations, and RBiníCi0 is the RB at the start of the allocation.

[0060] In some implementations, the encoding rule for RIV is adjusted as follows: IN VLS! I If (Lrb - 1) < [-B!^], then R1V = N:tSBX (Lrb -1)+ RBMcio Otherwise R1V = NRB-sbX (Nrb-sb- Lrb + 1) + (Pί-'“ - 1 - RBMcio) where 1 < Lrb< M:-58- RBiníCi0, N:B-SB is the number of RBs in the UL SBs, Lrb is the number of contiguous RB allocations, and RBiníCi0 is the RB at the start of the allocation. Illustrative Implementations

[0061] FIGURE 13 illustrates an example communication system 1300 having an example communication device 1310 and an example network device 1320 according to an implementation of the present disclosure. Each of the communication device 1310 and the network device 1320 can perform various functions to implement schemes, techniques, processes and methods described in this document relating to FDRA in non-contiguous SBs in SBFD with respect to user equipment and network device in mobile communications, including the scenarios / schemes described above as well as processes 1400 and 1500 described below.

[0062] The communication device 1310 may be a part of an electronic device, which may be a UE such as a portable or mobile device, a wearable device, a wireless communication device or a computing device. For example, the communication device 1310 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing device such as a tablet computer, a Petition 870250101161, dated 05 / 11 / 2025, page 25 / 46 18 / 27 laptop computer or notebook. The 1310 communication device may also be part of a machine-type device, which may be an IoT, NB-IoT or IIoT device such as a stationary or fixed device, a household appliance, a wired communication device or a computing device. For example, the 1310 communication device may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker or a home control center. Alternatively, the 1310 communication device may be implemented in the form of one or more integrated circuit (IC) chips such as, for example, and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors.The communication apparatus 1310 may include at least some of the components shown in FIGURE 13, such as a processor 1312, for example. The communication apparatus 1310 may additionally include one or more other components not relevant to the proposed scheme of the present disclosure (for example, internal power supply, display device and / or user interface device), and thus such components of the communication apparatus 1310 are not shown in FIGURE 13 nor described below in the interest of simplicity and brevity.

[0063] The 1320 network appliance may be part of a network appliance, which may be a network node such as a satellite, a base station, a small cell, a router, or a gateway. For example, the 1320 network appliance may be implemented in an eNodeB in an LTE network, in a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or in a satellite or base station in a 6G network. Alternatively, the 1320 network appliance may be implemented in the form of one or more IC chips such as, for example, and without limitation, one or more single-core processors, one or more Petition 870250101161, dated 05 / 11 / 2025, page 26 / 46 19 / 27 multi-core processors, or one or more RISC or CISC processors. The 1320 network device may include at least some of the components shown in FIGURE 13, such as a 1322 processor, for example. The 1320 network device may additionally include one or more other components not relevant to the proposed scheme of the present disclosure (for example, internal power supply, display device and / or user interface device), and thus such components of the 1320 network device are not shown in FIGURE 13 nor described below in the interest of simplicity and brevity.

[0064] In one aspect, each of the 1312 processor and the 1322 processor may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “a processor” is used in this document to refer to the 1312 processor and the 1322 processor, each of the 1312 processor and the 1322 processor may include multiple processors in some implementations and a single processor in other implementations according to the present disclosure.In another aspect, each of the 1312 processor and the 1322 processor can be implemented in hardware (and optionally firmware) form with electronic components including, for example, and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more resistors with memory, and / or one or more varactors that are configured and arranged to achieve specific purposes according to the present disclosure. In other words, in at least some implementations, each of the 1312 processor and the 1322 processor is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks, including autonomous reliability enhancements in a device (for example, as represented by the 1310 communication apparatus) and a network (for example, as represented by the apparatus). Petition 870250101161, dated 05 / 11 / 2025, page 27 / 46 20 / 27 network 1320) according to various implementations of the present disclosure.

[0065] In some implementations, the communication device 1310 may also include a transceiver 1316 coupled to the processor 1312 and capable of transmitting and receiving data wirelessly. In some implementations, the communication device 1310 may additionally include a memory 1314 coupled to the processor 1312 and capable of being accessed by the processor 1312 and storing data therein. In some implementations, the network device 1320 may also include a transceiver 1326 coupled to the processor 1322 and capable of transmitting and receiving data wirelessly. In some implementations, the network device 1320 may additionally include a memory 1324 coupled to the processor 1322 and capable of being accessed by the processor 1322 and storing data therein. Therefore, communication device 1310 and network device 1320 can communicate wirelessly with each other by means of transceiver 1316 and transceiver 1326, respectively.To aid in better understanding, the following description of the operations, functionalities, and capabilities of each of the communication device 1310 and the network device 1320 is provided in the context of a mobile communication environment in which the communication device 1310 is implemented in or as a communication device or a UE and the network device 1320 is implemented in or as a network node of a communication network.

[0066] In some implementations, processor 1312 may receive, via transceiver 1316, an SBFD configuration and an FDRA configuration from network device 1320. The SBFD configuration includes SBs that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. Processor 1312 may receive, via transceiver 1316, information from network device 1320. This information indicates to communication device 1310 that a subset of RBs outside the non-contiguous SBs is excluded. Petition 870250101161, dated 05 / 11 / 2025, page 28 / 46 21 / 27

[0067] In some implementations, non-contiguous SBs are DL SBs or UL SBs.

[0068] In some implementations, VRBs and PRBs corresponding to RBs are reindexed to exclude the subset of RBs outside of non-contiguous SBs.

[0069] In some implementations, reindexed VRB numbers and reindexed PRB numbers are respectively contiguous across non-contiguous SBs.

[0070] In some implementations, the information includes a frequency domain assignment field, and a first subset of bits from the frequency domain assignment field is used to indicate a resource allocation.

[0071] In some implementations, a second subset of bits from the frequency domain assignment field is not used for resource allocation.

[0072] In some implementations, a first number of bits of the first bit subset corresponds to a number of RBs that are across the SBs.

[0073] In some implementations, a second bit number from the second bit subset corresponds to a difference between the first bit number from the first bit subset and a third bit number corresponding to a number of all RBs in a BWP.

[0074] In some implementations, a first number of bits of the first bit subset corresponds to a number of RGBs that are across the SBs.

[0075] In some implementations, a second bit number from the second bit subset corresponds to a difference between the first bit number from the first bit subset and a third bit number corresponding to a number of all RGBs in a BWP.

[0076] In some implementations, a RIV is adjusted based on the reindexed PRBs. Petition 870250101161, dated 05 / 11 / 2025, p. 29 / 46 22 / 27

[0077] In some implementations, processor 1322 can transmit, via transceiver 1326, an SBFD configuration and an FDRA configuration to communication device 1310. The SBFD configuration includes SBs that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. Processor 1322 can transmit, via transceiver 1326, information to communication device 1310. This information indicates to communication device 1310 that a subset of the RBs outside the non-contiguous SBs is excluded.

[0078] In some implementations, non-contiguous SBs are DL SBs or UL SBs.

[0079] In some implementations, RBs include VRBs and VRBs are reindexed to exclude the subset of RBs outside of non-contiguous sub-bands.

[0080] In some implementations, RBs include PRBs and PRBs are reindexed to exclude the subset of RBs outside of non-contiguous sub-bands.

[0081] In some implementations, reindexed VRB numbers and reindexed PRB numbers are respectively contiguous across non-contiguous SBs.

[0082] In some implementations, the information includes a frequency domain assignment field, and a first subset of bits from the frequency domain assignment field is used to indicate a resource allocation.

[0083] In some implementations, a second subset of bits from the frequency domain assignment field is not used for resource allocation.

[0084] In some implementations, a first number of bits of the first bit subset corresponds to a number of RBs that are across the SBs.

[0085] In some implementations, a second bit number from the second bit subset corresponds to a difference between the first bit number from the first bit subset and a third bit number. Petition 870250101161, dated 05 / 11 / 2025, p. 30 / 46 23 / 27 is the number of bits corresponding to a number of all RBs in a BWP.

[0086] In some implementations, a first number of bits of the first bit subset corresponds to a number of RGBs that are across the SBs.

[0087] In some implementations, a second bit number from the second bit subset corresponds to a difference between the first bit number from the first bit subset and a third bit number corresponding to a number of all RGBs in a BWP.

[0088] In some implementations, a RIV is adjusted based on the reindexed PRBs. Illustrative Processes

[0089] FIGURE 14 illustrates an example process 1400 according to an implementation of the present disclosure. Process 1400 may be an example implementation of scenarios / schemes mentioned above, either partially or completely, with respect to FDRA in non-contiguous SBs in SBFD of the present disclosure. Process 1400 may represent an implementation aspect of communication device features 1310. Process 1400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 1410 and 1420. Although illustrated as distinct blocks, several blocks of process 1400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks of process 1400 may be executed in the order shown in FIGURE 14 or, alternatively, in a different order.Process 1400 can be implemented by communication device 1310 or by any suitable UE or machine-type devices. For illustrative purposes only and without limitation, process 1400 is described below in the context of communication device 1310. Process 1400 can start in block 1410.

[0090] In block 1410, process 1400 may include processor Petition 870250101161, dated 05 / 11 / 2025, page 31 / 46 24 / 27 1312 of communication device 1310 receives an SBFD configuration and an FDRA configuration from a network node. The SBFD configuration includes SBs that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. Process 1400 can proceed from block 1410 to block 1420.

[0091] In block 1420, process 1400 may include processor 1312 receiving information from the network node. The information indicates to communication device 1310 that a subset of RBs outside non-contiguous SBs is excluded. [00 92] FIGURE 15 illustrates an example process 1500 according to an implementation of the present disclosure. Process 1500 may be an example implementation of scenarios / schemes mentioned above, either partially or completely, with respect to FDRA in non-contiguous sub-bands in SBFD of the present disclosure. Process 1500 may represent an implementation aspect of network appliance features 1320. Process 1500 may include one or more operations, actions, or functions as illustrated by one or more of blocks 1510 and 1520. Although illustrated as distinct blocks, several blocks of process 1500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks of process 1500 may be executed in the order shown in FIGURE 15 or, alternatively, in a different order.Process 1500 can be implemented by network appliance 1320 or by any suitable network device or machine-type devices. For illustrative purposes only and without limitation, process 1500 is described below in the context of network appliance 1320. Process 1500 can start in block 1510.

[0093] In block 1510, process 1500 may include processor 1322 of network appliance 1320 transmitting an SBFD configuration and an FDRA configuration to a UE. The SBFD configuration includes SBs that are non-contiguous within a slot, and the FDRA configuration includes a plurality of RBs. Process 1500 may proceed Petition 870250101161, dated 05 / 11 / 2025, page 32 / 46 25 / 27 of block 1510 to block 1520.

[0094] In block 1520, process 1500 may include processor 1322 transmitting information from network device 1320 to the UE. The information indicates to the UE that a subset of RBs outside non-contiguous SBs is excluded. Additional Notes

[0095] The subject matter described in this document sometimes illustrates different components contained within, or connected to, other different components. It is to be understood that such represented architectures are only examples, and that in fact many other architectures can be implemented that achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively associated in such a way that the desired functionality is achieved. Consequently, any two components in this document combined to achieve a particular functionality can be seen as associated with each other in such a way that the desired functionality is achieved, independent of architectures or intermediate components.Similarly, any two components thus associated can also be seen as being operationally connected, or operationally coupled, to each other to achieve the desired functionality, and any two components capable of being thus associated can also be seen as being operationally coupleable to each other to achieve the desired functionality. Specific examples of operationally coupleable components include, but are not limited to, physically coupleable and / or physically interacting components and / or wirelessly interacting and / or logically interacting components.

[0096] Furthermore, with regard to the substantial use of any plural and / or singular terms in this document, those skilled in the art may translate from plural to singular and / or Petition 870250101161, dated 05 / 11 / 2025, pp. 33 / 46 26 / 27 singular to plural such as is appropriate for context and / or application. The various singular / plural permutations may be explicitly shown in this document for the sake of clarity.

[0097] Furthermore, it will be understood by those skilled in the art that, in general, terms used in this document, and especially in the appended claims, for example, bodies of the appended claims, are generally intended as open terms, for example, the term including should be interpreted as including, but not limited to, the term having should be interpreted as having at least, the term includes should be interpreted as includes, but is not limited to, etc. It will be further understood by those skilled in the art that if a specific number of an introduced claim recitation is intended, such intention will be explicitly stated in the claim, and in the absence of such recitation, such intention is not present. For example, as an aid to understanding, the following appended claims may make use of the introductory expressions at least one and one or more to introduce recitations of claims.However, the use of such expressions should not be interpreted as indicating that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only such recitation, even when the same claim includes the introductory expressions "a or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a and / or an" should be interpreted as meaning "at least one" or "one or more"; the same remains true for the use of definite articles used to introduce claim recitations. Furthermore, even if a specific number of an introduced claim recitation is explicitly reported, those skilled in the art will recognize that such recitation should be interpreted as meaning "at least the reported number," for example, the simple recitation of two recitations, without others. Petition 870250101161, dated 05 / 11 / 2025, pp. 34 / 46 27 / 27 modifiers means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense that a person technically knowledgeable in the subject would understand the convention, for example, “a system having at least one of A, B, and C” would include, but is not limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In instances where a convention analogous to "at least one of A, B, or C, etc." is used, such a construction is generally intended in the sense that a person technically knowledgeable in the subject matter would understand the convention, for example, "a system having at least one of A, B, or C" would include, but is not limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.It will be further understood by those skilled in the art that virtually any disjunctive word and / or expression presenting two or more alternative terms, whether in the description, claims or drawings, should be understood as considering the possibilities of including one of the terms, one or the other of the terms, or both terms. For example, the expression “A or B” will be understood as including the possibilities of “A or “B” or “A and B.”

[0098] From the foregoing, it will be understood that various implementations of the present disclosure are described in this document for illustrative purposes, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Therefore, the various implementations disclosed in this document are not intended to be limitations, with the true scope and spirit being indicated by the following claims. Petition 870250101161, dated 05 / 11 / 2025, pp. 35 / 46

Claims

1 / 4 CLAIMS 1. A method, characterized in that it comprises: receiving, by a processor of an apparatus, a full duplex sub-band configuration (SBFD) and a frequency domain resource allocation configuration (FDRA) of a network node, wherein the SBFD configuration includes sub-bands that are non-contiguous within a slot, and the FDRA configuration includes a plurality of resource blocks (RBs); and receiving, by the processor, information from the network node, wherein the information indicates to the apparatus that a subset of the RBs outside the non-contiguous sub-bands is excluded.

2. Method according to claim 1, characterized in that the non-contiguous sub-bands are either downlink sub-bands or uplink sub-bands.

3. A method according to claim 2, characterized in that the RBs include a plurality of virtual resource blocks (VRBs) and the VRBs are reindexed to exclude the subset of RBs outside the non-contiguous sub-bands, and the reindexed numbers of VRBs are contiguous across the non-contiguous sub-bands; or the RBs include a plurality of physical resource blocks (PRBs) and the PRBs are reindexed to exclude the subset of RBs outside the non-contiguous sub-bands, and the reindexed numbers of PRBs are respectively contiguous across the non-contiguous sub-bands.

4. A method according to claim 3, characterized in that the information includes a frequency domain assignment field, and wherein a first subset of bits of the frequency domain assignment field is used to indicate a resource allocation.

5. Method according to claim 4, characterized in that a second subset of bits of the frequency domain assignment field is not used for resource allocation. Petition 870250090774, dated 06 / 10 / 2025, p. 17 / 21 2 / 4 6. Method, according to claim 5, characterized in that a first number of bits of the first subset of bits corresponds to a number of RBs that are across the sub-bands.

7. A method according to claim 6, characterized in that a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RBs in a bandwidth part (BWP).

8. Method, according to claim 5, characterized in that a first number of bits of the first subset of bits corresponds to a number of groups of feature blocks (RGBs) that are across the sub-bands.

9. A method according to claim 8, characterized in that a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RGBs in a bandwidth part (BWP).

10. Method, according to claim 3, characterized in that a feature indicator value (RIV) is adjusted based on the reindexed PRBs.

11. A method characterized in that it comprises: transmitting, by a processor of an apparatus, a full-duplex sub-band configuration (SBFD) and a frequency-domain resource allocation configuration (FDRA) to a user equipment (UE), wherein the SBFD configuration includes sub-bands that are non-contiguous within a slot, and wherein the FDRA configuration includes a plurality of resource blocks (RBs); and transmitting, by the processor, information to the UE, wherein the information indicates to the UE that a subset of the RBs outside the non-contiguous sub-bands is excluded.

12. Method, according to claim 11, characterized by the fact that the non-contiguous sub-bands are downlink sub-bands or uplink sub-bands.

13. A method according to claim 12, characterized in that the RBs include a plurality of virtual resource blocks (VRBs) and the VRBs are reindexed to exclude the subset of RBs outside the non-contiguous sub-bands, and the reindexed numbers of VRBs are contiguous across the non-contiguous sub-bands; or the RBs include a plurality of physical resource blocks (PRBs) and the PRBs are reindexed to exclude the subset of RBs outside the non-contiguous sub-bands, and the reindexed numbers of PRBs are respectively contiguous across the non-contiguous sub-bands.

14. A method according to claim 13, characterized in that the information includes a frequency domain assignment field, and wherein a first subset of bits of the frequency domain assignment field is used to indicate a resource allocation.

15. Method according to claim 14, characterized in that a second subset of bits of the frequency domain assignment field is not used for resource allocation.

16. Method, according to claim 15, characterized in that a first number of bits of the first subset of bits corresponds to a number of RBs that are across the sub-bands.

17. Method, according to claim 16, characterized in that a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RBs in a bandwidth part (BWP).

18. Method, according to claim 15, characterized in that a first number of bits of the first subset of bits corresponds to a number of groups of feature blocks (RGBs) Petition 870250090774, dated 06 / 10 / 2025, p. 19 / 21 4 / 4 that are across the sub-bands.

19. A method according to claim 18, characterized in that a second number of bits of the second subset of bits corresponds to a difference between the first number of bits of the first subset of bits and a third number of bits corresponding to a number of all RGBs in a bandwidth part (BWP).

20. Apparatus, characterized in that it comprises: a transceiver that, during operation, communicates wirelessly with a network node; and a processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising: receiving, through the transceiver, a full-duplex sub-band configuration (SBFD) and a frequency-domain resource allocation configuration (FDRA) from the network node, wherein the SBFD configuration includes sub-bands that are non-contiguous within a slot, and wherein the FDRA configuration includes a plurality of resource blocks (RBs); and receiving, through the transceiver, information from the network node, wherein the information indicates to the apparatus that a subset of the RBs outside the non-contiguous sub-bands is excluded. Petition 870250090774, dated 06 / 10 / 2025, pp. 20 / 21

Images