Method and device for determining transport block size in sub-band full duplex

Abstract

The embodiment of the invention relates to a method and equipment for determining the size of a transmission block in full duplex of a sub-band. In an embodiment of the present application, a user equipment comprises: a wireless transceiver; and a processor coupled to the wireless transceiver. The processor is configured to: determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block; determining the size of a transmission block transmitted by the PUSCH based on one or more of the at least two frequency resources; and performing, via the wireless transceiver, the transport block on the uplink data channel (PUSCH) transmission using the at least two frequency resources. The at least two frequency resources have at least two different sizes.

Description

Technical Field

[0001] Embodiments of the present application relate generally to wireless communication techniques, and more particularly to methods and apparatus for determining transport block size in sub-band full-duplex. Background Art

[0002] In the new radio (NR), the available transport block size (TBS) may be determined for transmissions on the physical uplink shared channel (PUSCH). In this way, the user equipment (UE) may transmit data based on the determined TBS, and the base station (BS) may receive data based on the same TBS. Summary of the invention

[0003] Embodiments of the present application provide methods and apparatus for determining a transport block size in sub-band full-duplex.

[0004] Embodiments of the present application provide a user equipment (UE), comprising: a wireless transceiver; and a processor, which is coupled to the wireless transceiver. The processor is configured to: determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block; determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and perform the PUSCH transmission via the wireless transceiver. The at least two frequency resources have at least two different sizes.

[0005] Another embodiment of the present application provides a base station (BS), comprising: a wireless transceiver; and a processor, which is coupled to the wireless transceiver. The processor is configured to: determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block; determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and perform the PUSCH transmission via the wireless transceiver. The at least two frequency resources have at least two different sizes.

[0006] Another embodiment of the present application provides a method performed by a first user equipment (UE). The method includes: determining at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block; determining a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and performing the PUSCH transmission. The at least two frequency resources have at least two different sizes.

[0007] Another embodiment of the present application provides a method performed by a first base station (BS). The method includes: determining at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block; determining a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and receiving the PUSCH transmission. The at least two frequency resources have at least two different sizes. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented with reference to specific embodiments thereof illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and are therefore not to be considered limiting of its scope.

[0009] Figure 1 is a wireless communication system according to some embodiments of the present application;

[0010] Figure 2 is a diagram of PUSCH transmission based on PUSCH repetition type A according to some embodiments of the present application;

[0011] Figure 3 is a diagram of PUSCH transmission based on PUSCH repetition type B according to some embodiments of the present application;

[0012] Figure 4 is a diagram of PUSCH transmission based on enhanced PUSCH repetition type A according to some embodiments of the present application;

[0013] Figure 5 is a diagram of a PUSCH transmission based on transport block processing over multiple time slots according to some embodiments of the present application;

[0014] Figure 6 is a diagram of a sub-band full-duplex scheme according to some embodiments of the present application;

[0015] Figure 7 is a diagram of indicated frequency domain resources across a plurality of subbands configured with different transmission directions according to some embodiments of the present application;

[0016] Figure 8 is a diagram of resource allocation for PUSCH with PUSCH repetition type A or enhanced PUSCH repetition type A according to some embodiments of the present application;

[0017] Fig. 9 is a diagram of resource allocation for a PUSCH with PUSCH repetition type B according to some embodiments of the present application;

[0018] Fig.10is a diagram of resource allocation for a PUSCH with PUSCH repetition type B according to some embodiments of the present application;

[0019] Fig.11 is a diagram of resource allocation for PUSCH with TBOMS according to some embodiments of the present application;

[0020] Fig.12 is a flowchart of a method for determining a transport block size (TBS) according to some embodiments of the present application;

[0021] Fig.13 is a flowchart of another method for determining TBS according to an embodiment of the present application; and

[0022] Fig.14 is a block diagram of an apparatus according to some embodiments of the present application. DETAILED DESCRIPTION

[0023] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be accomplished by different embodiments that are intended to be included in the spirit and scope of the present application.

[0024] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings.

[0025] Figure 1 A wireless communication system 100 according to some embodiments of the present application is illustrated. Figure 1 Included is a base station (BS) 101 and a user equipment (UE) 103. Uplink 105 and downlink 107 are used to transmit data and signals between BS 101 and US 103. In uplink 105, a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) may be implemented to transmit data and signals from UE 103 to BS 101. In downlink 107, a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) may be implemented to transmit data and signals from the BS to the UE.

[0026] I. Determination of NR TB size for PDSCH

[0027] The TB size determination for PDSCH is performed as follows.

[0028] 1) The UE first determines the number of REs in the time slot (N RE ),

[0029] -UE first passes Determine the number of REs (N') allocated for PDSCH within a PRB (physical resource block)RE ),in is the number of subcarriers in a physical resource block, is the number of symbols allocated by PDSCH in a time slot, is the number of DM-RS REs per PRB in the scheduling duration containing the overhead of the DM-RS CDM group without data, as indicated by DCI (Downlink Control Information) format 1_1 or format 1_2 or as described for format 1_0 in clause 5.1.6.2, and is the overhead configured by the higher layer parameter xOverhead in PDSCH-ServingCellConfig. If xOverhead in PDSCH-ServingCellConfig is not configured (from a value of 6, 12 or 18), then Set to 0. If PDSCH is scheduled by PDCCH with CRC scrambled by SI-RNTI, RA-RNTI, MSGB-RNTI or P-RNTI, then Assumed to be 0. If PDSCH is scheduled by PDCCH with CRC scrambled by G-RNTI or G-CS-RNTI or PDSCH without PDCCH is activated by PDCCH with CRC scrambled by G-CS-RNTI, then It is the overhead configured by the higher layer parameter xOverhead-Multicast in PDSCH-Config-Multicast. If xOverhead-Multicast in PDSCH-Config-Multicast is not configured, then Set to 0.

[0030] -UE through N RE =min(156,N' RE )·n PRB Determine the total number of REs allocated for PDSCH (N RE ), where n PRB is the total number of PRBs allocated to the UE.

[0031] 2) Through N info =N RE ·R·Q m ·υ obtains unquantified intermediate variables (N info ).

[0032] If N info ≤3824

[0033] Use step 3 as the next step for TBS (Transport Block Size) determination

[0034] otherwise

[0035] Use step 4 as the next step in TBS determination

[0036] End of judgment

[0037] 3) When N info When ≤3824, TBS is determined as follows

[0038] -Quantized intermediate number of information bits in

[0039] - Use Table 1 to find no less than N' info The closest to TBS.

[0040] 4) When N info When >3824, TBS is determined as follows.

[0041] -Quantized intermediate number of information bits in And ties in the round function are broken towards the next largest integer.

[0042] - If R ≤ 1 / 4

[0043] in

[0044] otherwise

[0045] If N′ info >8424

[0046] in

[0047] otherwise

[0048]

[0049] End of judgment

[0050] End of judgment

[0051] Otherwise if Table 2 is used and 28 ≤ I MCS ≤31,

[0052] -TBS is assumed to be from using 0≤I MCS ≤27. If there is no PDCCH for using 0≤I MCS ≤ 27 of the same transport block and if the initial PDSCH of the same transport block is semi-persistently scheduled, then the TBS shall be determined from the most recent semi-persistently scheduled assignment PDCCH.

[0053] Otherwise if Table 3 is used and 27 ≤ I MCS ≤31,

[0054] -TBS is assumed to be from using 0≤I MCS ≤26. If there is no PDCCH for using 0≤I MCS ≤ 26 of the same transport block and if the initial PDSCH of the same transport block is semi-persistently scheduled, then the TBS shall be determined from the most recent semi-persistently scheduled assignment PDCCH.

[0055] otherwise

[0056] -TBS is assumed to be from using 0≤I MCS ≤28. If there is no PDCCH for using 0≤I MCS ≤ 28 of the same transport block and if the initial PDSCH of the same transport block is semi-persistently scheduled, then the TBS shall be determined from the most recent semi-persistently scheduled assignment PDCCH.

[0057]

[0058]

[0059] Table 1: For N info TBS ≤ 3824

[0060]

[0061]

[0062] Table 2: MCS index table of PDSCH

[0063]

[0064]

[0065] Table 3: MCS index table of PDSCH

[0066] II. Determination of NR TB size for PUSCH

[0067] For a PUSCH scheduled by a RAR UL grant, or

[0068] For PUSCH scheduled by fallbackRAR UL grant, or

[0069] For PUSCH scheduled by DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or

[0070] For PUSCH scheduled by DCI format 0_1 ​​or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or

[0071] For a PUSCH transmission with a configured grant, or

[0072] For MsgA PUSCH transmission, if

[0073] -0≤I MCS ≤27 ​​and transform precoding is disabled and Table 5.1.3.1-2 is used, or

[0074] -0≤I MCS ≤28 and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or

[0075] -0≤I MCS ≤27 ​​and transform precoding is disabled, the UE shall first determine the TBS as specified below:

[0076] The UE should first determine the number of REs in the time slot (N RE ):

[0077] - The UE first determines the number of REs (N') allocated for the PUSCH within a PRB by: RE )

[0078] - in is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L allocated for PUSCH according to clause 6.1.2.1 for scheduled PUSCH or clause 6.1.2.3 for configured PUSCH, is the number of REs per PRB of DM-RS within the allocated duration containing the overhead of the DM-RS CDM group with no data, as described in clause 6.1.2.3 for PUSCH with a configured grant or as indicated by DCI format 0_1 ​​or DCI format 0_2 or as described in clause 6.2.2 for DCI format 0_0, and It is the overhead configured by the higher layer parameter xOverhead in PUSCH-ServingCellConfig. Not configured (a value from 6, 12, or 18), then Assumed to be 0.

[0079] For Msg3 or MsgA PUSCH transmission, Always set to 0. In case of PUSCH repetition type B, the nominal repetition is determined assuming a duration of L symbols and no segmentation

[0080] - The UE determines the total number of REs allocated for PUSCH (N RE )as follows

[0081] - For TB processing over multiple time slots, N RE =N*min(156,N′ RE )·n PRB , where n PRB is the total number of PRBs allocated for the UE and N is the number of time slots used for TBS determination, which is indicated by numberOfSlotsTBoMS.

[0082] - Otherwise, N RE =min(156,N′ RE )·n PRB .

[0083] - Next, proceed with steps 2 to 4 as defined in TBS determination for PDSCH

[0084] - For PUSCH scheduled by fallbackRAR UL grant, the UE assumes that the TB size determined by the UL grant in the fallbackRAR should be the same as the TB size used in the corresponding MsgA PUSCH transmission.

[0085] Otherwise if

[0086] -28≤I MCS ≤31 and transform precoding is disabled and Table 5.1.3.1-2 is used, or

[0087] -28≤I MCS ≤31, and transform precoding is disabled,

[0088] -TBS is assumed to be from using 0≤I MCS ≤27. If there is no PDCCH for using 0≤I MCS ≤ 27 of the same transport block and if the initial PUSCH of the same transport block is transmitted using a configured grant,

[0089] -TBS shall be determined from configuredGrantConfig which configures grant type 1 PUSCH.

[0090] - The TBS shall be determined from the nearest PDCCH scheduling configuration grant type 2 PUSCH.

[0091] otherwise

[0092] -TBS is assumed to be from using 0≤I MCS ≤28. If there is no PDCCH for using 0≤I MCS ≤ 28 of the same transport block and if the initial PUSCH of the same transport block is transmitted using a configured grant,

[0093] -TBS shall be determined from configuredGrantConfig which configures grant type 1 PUSCH.

[0094] - The TBS shall be determined from the nearest PDCCH scheduling configuration grant type 2 PUSCH.

[0095] III. NR Resource Allocation

[0096] Before the NR UE transmits PUSCH (including dynamically scheduled PUSCH and CG (configuration grant) PUSCH), it receives frequency domain resource allocation assignment and time domain resource assignment from the NR gNB (generalized NodeB) to determine the frequency domain and time domain resources of the PUSCH.

[0097] III.1. Resource allocation in the frequency domain

[0098] For dynamically scheduled PUSCH and CG type 2 PUSCH, the UE shall use the resource allocation field in the detected PDCCH DCI to determine the resource assignment. However, for CG type 1 PUSCH, the resource assignment applied for transmission is provided by the higher layer parameter frequencyDomainAllocation in configuredGrantConfig. The frequency domain resource assignment indicates to the scheduling UE a set of resource blocks (RBs) within the active bandwidth part. The RB index of the resource allocation is determined within the active bandwidth part of the UE.

[0099] III.2. Resource allocation in the time domain

[0100] III.2.i. Dynamic scheduling of PUSCH

[0101] For dynamically scheduled PUSCH, the 'Time domain resource assignment' field value m of the DCI provides a row index m+1 to the allocation table, and the resource allocation table used may be predefined by the 3GPP specification or may be configured by higher layer parameters. The index row defines the time slot offset K to be applied to the PUSCH transmission 2 , start and length indicator SLIV, or directly start symbol S and allocation length L, and number of repetitions (if numberOfRepetitions exists in the resource allocation table). Among them, the time slot offset K2 Used to indicate the number of time slots between the DCI reception time slot and the PUSCH transmission time slot.

[0102] There are four main schemes for resource allocation in the time domain for dynamically scheduled PUSCH, including PUSCH repetition type A introduced in Rel-15 and PUSCH repetition type B introduced in Rel-16. Enhanced PUSCH repetition type A is beneficial for PUSCH coverage enhancement for TDD. It is recommended to be supported in Rel-17. TB processing PUSCH on multiple time slots (TBOMS) is beneficial for PUSCH coverage enhancement. It is recommended to support TBOMS in Rel-17. For a specific PUSCH transmission, the scheme used can be configured by higher layer parameters. The time domain resource allocation of these four schemes can be found as follows.

[0103] For PUSCH repetition type A, the start symbol S associated with the start of the slot and the number L of consecutive symbols allocated for PUSCH counting from symbol S are determined from the start of the index line and the length indicator SLIV.

[0104] If (L-1)≤7, then

[0105] SLIV=14·(L-1)+S

[0106] otherwise

[0107] SLIV=14·(14-L+1)+(14-1-S)

[0108] Where 0<L≤14-S.

[0109] When transmitting a PUSCH scheduled by DCI format 0_1 ​​or 0_2 in a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI and NDI=1, the number of repetitions K is determined as

[0110] -If numberOfRepetitions exists in the resource allocation table, then the number of repetitions K is equal to numberOfRepetitions;

[0111] - Otherwise if the UE is configured by pusch-AggregationFactor, then the number of repetitions K is equal to pusch-AggregationFactor;

[0112] -Otherwise K=1.

[0113] For PUSCH repetition type A, the same symbol allocation applies across K consecutive slots provided K>1. The UE shall repeat the TB across K consecutive slots, applying the same symbol allocation in each slot.

[0114] For example, assuming K 2 =1, S=2 (indicating that the PUSCH transmission starts at symbol #2, i.e., the third symbol), L=8 (indicating that the length of the PUSCH transmission is 8), K=4, then the time domain resources of the PUSCH with PUSCH repetition type A can be seen at Figure 2 In. Figure 2 In , each slot contains 14 symbols, and one rectangle in a slot indicates 2 symbols. Figure 2 In the example, the data transmitted in PUSCH#0 to PUSCH#3 are the same. Therefore, the data transmitted in PUSCH#0 is transmitted 4 times in total.

[0115] For enhanced PUSCH repetition type A, if any symbol of PUSCH overlaps with the symbol set of a slot indicated to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as downlink, then PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted.

[0116] For PUSCH repetition type B, the number of nominal repetitions is given by numberOfRepetitions. For the nth nominal repetition, n = 0, ..., numberOfRepetitions – 1,

[0117] - where the nominal repetition starts in the time slot indicated by is given by , and the start symbol associated with the start of the time slot is given by

[0118] Given.

[0119] - The time slot where the nominal repetition ends is represented by is given by , and the end symbol associated with the start of the time slot is given by Given.

[0120] Here, K s is the time slot in which PUSCH transmission starts, and is the number of symbols per time slot. The start symbol S associated with the start of the time slot and the number of consecutive symbols L allocated for PUSCH counting from symbol S are provided by the startSymbol and length of the index row of the resource allocation table, respectively.

[0121] For PUSCH repetition type B, symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols for PUSCH repetition type B transmission. After determining the invalid symbols for PUSCH repetition type B transmission for each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH repetition type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than 0 for the nominal repetition, then the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a contiguous set of all potentially valid symbols for PUSCH repetition type B transmission that can be used for the slot. Actual repetitions with a single symbol are omitted except for the case where L=1.

[0122] If any symbol of the PUSCH overlaps with the set of symbols of a timeslot indicated to the UE as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the actual repetition is omitted.

[0123] For example, assuming K 2 =0, S=2, L=8, K=4, then the time domain resources of PUSCH with PUSCH repetition type B can be seen in Figure 3 In. Figure 3 In , each time slot includes 14 symbols, and one rectangle in a time slot indicates 2 symbols. Figure 3 (A) shows four nominal repetitions (nominal repetition #0 to nominal repetition #3). After considering the downlink transmission indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, Figure 3 (B) shows 5 actual repetitions (actual repetition #0 to actual repetition #4), where each of the five actual repetitions may occupy a different symbol in the time slot. Figure 3 As shown in (B), the symbols indicated as downlink are considered invalid symbols for PUSCH repetition type B transmission, and thus Figure 3 The actual repeats in (B) are not continuous.

[0124] For enhanced PUSCH repetition type A, resource allocation in the time domain is almost the same as PUSCH repetition type A, except that the number of repetitions is counted based on the available time slot. If at least one of the symbols indicated by TDRA (time domain resource allocation) of PUSCH in the time slot overlaps with a symbol not desired for UL transmission, the time slot is determined to be unavailable, and the semi-static flexible symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered available.

[0125] For example, assuming K 2 =1, S=2, L=8, K=4, then the time domain resources of PUSCH with enhanced PUSCH repetition type A can be seen in Figure 4 In. Figure 4 In , each slot contains 14 symbols, and one rectangle in a slot indicates 2 symbols. Figure 4 In slot #2, the data transmitted in PUSCH #0 to PUSCH #3 are the same. Therefore, the data transmitted in PUSCH #0 is transmitted 4 times in total. In slot #2, the first symbol to the fourth symbol are occupied by downlink transmission (e.g., configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), and the transmission of PUSCH #1 to PUSCH #3 is in slot #3 to slot #5.

[0126] For TBOMS, time domain resource determination may be performed via PUSCH repetition type A (e.g., TDRA). The number of slots K allocated for TBOMS is determined by using the row index of the TDRA list, counted via RRC configuration and based on the available slots for UL transmission. The transmission in each slot may be referred to as a transmission part of a TB in the present invention. The determination of available slots is as defined in enhanced PUSCH repetition type A.

[0127] For example, assuming K 2 =1, S=2, L=8, K=4, then the time domain resources of PUSCH with TBOMS can be seen in Figure 5 In. Figure 5 In , each slot contains 14 symbols, and one rectangle in a slot indicates 2 symbols. Figure 5In slot #2, the data transmitted in PUSCH #0 to PUSCH #3 may be different. The transport block may be divided into four parts, and the four parts are transmitted in PUSCH #0 to PUSCH #3 respectively. In slot #2, the first symbol to the fourth symbol are occupied by downlink transmission (e.g., configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), and the transmission of PUSCH #1 to PUSCH #3 is in slot #3 to slot #5.

[0128] III.2.ii.CG PUSCH

[0129] For CG type 1 PUSCH transmissions, the higher layer parameter timeDomainAllocation value m provides a row index m+1 pointing to the determined time domain resource allocation table, where the starting symbol and length are determined following the procedures defined herein for dynamically scheduled PUSCH. For CG type 2 PUSCH transmissions, resource allocation follows the UL grant received on the DCI.

[0130] There are also four main schemes for time domain resource allocation involving CG PUSCH of type 1 or type 2. They are somewhat different from the schemes for dynamically scheduled PUSCH (e.g. PUSCH repetition type A, PUSCH repetition type B, enhanced PUSCH repetition type A, and TBOMS). If numberOfRepetitions is present in the time domain resource allocation table, then the (nominal) number of repetitions K to be applied to the transmitted transport block is provided by the index row in the table; otherwise, K is provided by the higher layer configuration parameter repK. In addition, other procedures defined in the terms of dynamic scheduling may be reused.

[0131] For PUSCH repetition type B, for PUSCH transmissions with type 1 or type 2 configuration grants, the nominal and actual repetitions are determined according to the procedure for PUSCH repetition type B defined in the clause for dynamically scheduling PUSCH.

[0132] IV. Sub-band full-duplex

[0133] To achieve excellent data rates and latency, 5G spectrum on higher frequency bands is inevitable. Overcoming the reduced coverage on such carriers can be a challenge. 3GPP Rel.18 will likely introduce a new duplexing scheme that enables simultaneous use of downlink and uplink within a TDD carrier using non-overlapping frequency resources, which may be referred to as sub-band full-duplexing. The intent of this scheme is to extend the duration over which uplink transmissions can occur to improve uplink coverage and capacity. And the simultaneous use of DL and UL is only at the gNB and not at the UE side. An example of a duplexing scheme can be seen in Figure 6 In. Figure 6 In the different sub-bands of time slot #0, DL (downlink) #0 and DL #1 are duplexed with UL (uplink) #0. Figure 6 In the example, DL#2 and DL#3 are duplexed with UL#1 in different subbands of time slot #1.

[0134] Based on the background NR resource allocation, it is observed that the gNB can indicate only one frequency domain resource in the BWP (bandwidth part). For PUSCH repetition type A, PUSCH repetition type B and enhanced PUSCH repetition type A, the frequency resource is the same for each repetition. For TBOMS, the frequency resource is the same for each part of the transmission.

[0135] Therefore, in a sub-band full-duplex scenario, the indicated frequency domain resources may span multiple sub-bands configured with different transmission directions in some time slots, e.g. Figure 7 1. This scenario can be avoided by indicating small frequency domain resources by the gNB, which means that the indicated frequency domain resources will span multiple subbands configured with different transmission directions in any time slot. For dynamically scheduled PUSCH without repetition, this method will not have any restrictions. However, for CG PUSCH transmission without repetition or PUSCH with repetition or TBOMS, it is not reasonable to always indicate small frequency domain resources considering scheduling flexibility and resource utilization.

[0136] Therefore, some methods of the present application can be used to solve the problem of how to transmit PUSCH if the indicated frequency domain resources of PUSCH will span multiple subbands configured with different transmission directions in a subband full-duplex scenario. The embodiments of the present application are described as follows.

[0137] IV.1. Solution 1: At least two frequency domain resources are indicated, and they are used separately for different time slots.

[0138] IV.1.i. Solution 1-1

[0139] For PUSCH transmission with PUSCH repetition type A, the two resource assignments may be different and are used to indicate two frequency domain resources used in a time slot configured with a subband full-duplex scheme and a normal time slot, respectively. Figure 8 In the example, time slot #0 and time slot #1 are configured with a sub-band full-duplex scheme, one frequency domain resource is used for PUSCH repetition 1 and PUSCH repetition 2, and the other frequency domain resource is used for PUSCH repetition 3 and PUSCH repetition 4 in normal time slot #2 and time slot #3.

[0140] IV.1.ii. Solution 1-2

[0141] For PUSCH transmission with PUSCH repetition type B, the two resource assignments may be different and used to indicate two frequency domain resources used in a time slot configured with a sub-band full-duplex scheme and a normal time slot, respectively.

[0142] IV.1.ii.1.Solution 1-2-1

[0143] For each nominal PUSCH repetition, the frequency domain resource used is selected based on whether the occupied time slot of the nominal repetition (determined by the starting symbol) is configured with a subband full-duplex scheme. Fig. 9 In (A), the starting symbols of nominal repetition 1, nominal repetition 2, and nominal repetition 3 are in time slot #0 and time slot #1 configured with the sub-band full-duplex scheme, so one lower frequency domain resource of the time slot configured for sub-band full-duplex is used for nominal repetition 1, nominal repetition 2, and nominal repetition 3, and another frequency domain resource is used for nominal repetition 4. Thereafter, the resources used for actual repetition can be determined according to the current technology in Section 1, for example, in Fig. 9 In (A), the actual repetitions determined can be Fig. 9 It is found in (B) that seven (7) actual repetitions are determined for PUSCH transmission.

[0144] IV.1.ii.2. Solution 1-2-2

[0145] For each actual PUSCH repetition, the frequency domain resources used are selected according to whether the occupied time slot of the actual repetition is configured with a sub-band full-duplex scheme. Fig.10 In time slot #0 and time slot #1 configured with the subband full-duplex scheme, one frequency domain resource is used for actual PUSCH repetition 1 to actual PUSCH repetition 4, and in normal time slot #2 and time slot #3, another frequency domain resource is used for actual PUSCH repetition 5, actual PUSCH repetition 6 and actual PUSCH repetition 7.

[0146] IV.1.ii. Solutions 1-3

[0147] For PUSCH transmission with TBOMS, two resource assignments may be different and used to indicate two frequency domain resources used in a time slot configured with a sub-band full-duplex scheme and a normal time slot, respectively.

[0148] For each transmission part, the frequency domain resources used are selected according to whether the occupied time slots of the transmission part are configured with a sub-band full-duplex scheme. Fig.11 In time slot #0 and time slot #1 configured with the sub-band full-duplex scheme, one frequency domain resource is used for transmission part 1 and transmission part 2, and in normal time slot #2 and time slot #3, another frequency domain resource is used for transmission part 3 and transmission part 4.

[0149] IV.2. Solution 2: Indicate a frequency domain resource, then the UE adjusts this resource to adapt according to predefined rules Subband configuration.

[0150] For example, for a time slot without sub-band full duplex, the indicated frequency resources are applied; and for a time slot with sub-band full duplex, the applied frequency resources will be reduced to match the size of the sub-band. In this way, at least two frequency domain resources can be determined to be used separately for different time slots. The use of these two resources can be the same as in Embodiment 1.

[0151] For all embodiments in the disclosure of this application, the term “time slot” may be replaced by “time unit.” A time unit may be one or more frames, one or more subframes, one or more time slots, one or more subslots, or one or more symbols.

[0152] According to the solution, we can find that in a full-duplex scenario, for PUSCH repetition type A, TB processing on multiple time slots, or PUSCH repetition type B, there may be at least two frequency domain resources determined for PUSCH transmission and the sizes of these frequency domain resources may be different. However, the TBS may be determined based on only one size of these frequency domain resources. It should be determined how to use one or more of the at least two frequency domain resources to determine the TBS.

[0153] The disclosure of this application proposes an embodiment of determining the TBS when there are at least two frequency domain resources determined for PUSCH transmission in a sub-band full-duplex scenario. We assume that the UE knows the used frequency domain resources in each time slot or each repetition.

[0154] When at least two frequency domain resources are determined to be used for PUSCH transmission in a full-duplex scenario, determining the TBS may include step 1 and step 2. In addition, step 2 may be step 2-1 or step 2-2.

[0155] V. Step 1 : Determine at least two frequency domain resources for PUSCH transmission with PUSCH repetition type A or PUSCH repetition type B or for PUSCH transmission in multiple time slots with TBOMS.

[0156] The at least two frequency domain resources include at least two RB numbers.

[0157] The exemplary operation of step 1 may be (but is not limited to) any one of Embodiments 1 or 2 disclosed herein.

[0158] VI. Step 2-1 : Determine the TBS of PUSCH transmission based on one RB number among at least two RB numbers.

[0159] VI.1. Example 1

[0160] One RB number is the number of RBs of the first frequency domain resource used by the first PUSCH transmission. That is, only the size of the frequency domain resource used by the first PUSCH transmission is used to determine the TBS. The mentioned frequency resource is used for the first repetition of the PUSCH transmission in the time domain or for the PUSCH transmission in the first time slot. In this embodiment, the TBS can be determined earlier and simply because the frequency domain resource used by the first PUSCH transmission is used to determine the TBS.

[0161] The following are some examples of Example 1.

[0162] ■ For PUSCH repetition type A, the first PUSCH transmission is the first repetition.

[0163] ■ For PUSCH repetition type B, the first PUSCH transmission is the first actual or nominal repetition.

[0164] ■ For TBOMS, the first PUSCH transmission is the PUSCH transmission in the first time slot.

[0165] ■ The first PUSCH transmission may be further omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling.

[0166] ■ The first PUSCH transmission is the first PUSCH transmission among all remaining PUSCH transmissions after semi-static DL symbol omission configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0167] In some embodiments, the operation of step 2-1 of embodiment 1 may be as follows.

[0168]

[0169] VI.1.i. Example 1-1

[0170] The first PUSCH transmission is the first PUSCH repetition in the time domain for PUSCH with PUSCH repetition type A. The first PUSCH transmission may be further omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling.

[0171] like Figure 8As shown in FIG. 1 , the first PUSCH transmission is a repetition in slot #0. Therefore, the TBS determination is based on the number of RBs of repetition 1.

[0172] In some embodiments, repetition 1 may be further omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling.

[0173] VI.1.ii. Examples 1-2

[0174] For PUSCH with PUSCH repetition type A, the first PUSCH transmission is the first PUSCH repetition among all remaining PUSCH repetitions after semi-static DL symbol omission configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0175] like Figure 8 As shown in FIG. 1 , assuming that repetition 1 is omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling, the first PUSCH transmission is repetition 2 in slot #1. Therefore, TBS determination is based on the number of RBs of repetition 2.

[0176] VI.1.iii. Examples 1-3

[0177] For PUSCH with PUSCH repetition type B, the first PUSCH transmission is the first nominal PUSCH repetition in the time domain.

[0178] The first PUSCH transmission may be further omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling.

[0179] like Fig. 9 As shown in (A), the first PUSCH transmission is nominal repetition 1 in slot #0. Therefore, the TBS determination is based on the number of RBs of nominal repetition 1.

[0180] VI.1.iv. Examples 1-4

[0181] For PUSCH with PUSCH repetition type B, the first PUSCH transmission is the first nominal PUSCH repetition among all remaining PUSCH repetitions after semi-static DL symbol omission configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0182] like Fig. 9 As shown in (A), assuming that nominal repetition 1 is omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling, the first PUSCH transmission is nominal repetition 2 in slot #1. Therefore, TBS determination is based on the number of RBs of nominal repetition 2.

[0183] VI.1.v. Examples 1-5

[0184] For PUSCH with PUSCH repetition type B, the first PUSCH transmission is the first actual PUSCH repetition in the time domain.

[0185] The first PUSCH transmission may be further omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling.

[0186] like Fig. 9 As shown in (B), the first PUSCH transmission is the actual repetition 1 in slot #0. That is, the TBS determination is based on the number of RBs of the actual repetition 1.

[0187] VI.1.vi. Examples 1-6

[0188] For PUSCH with PUSCH repetition type B, the first PUSCH transmission is the first actual PUSCH repetition among all remaining actual PUSCH repetitions after semi-static DL symbol omission configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0189] like Fig. 9As shown in (B), assuming that actual repetition 1 is omitted by semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or dynamic signaling, the first PUSCH transmission is actual repetition 2 in slot #1. That is, TBS determination is based on the number of RBs of actual repetition 2.

[0190] VI.1.vii. Examples 1-7

[0191] For PUSCH transmission with TBOMS, the first PUSCH transmission is the PUSCH transmission in the first time slot. The first PUSCH transmission may be further omitted by dynamic signaling.

[0192] like Fig.11 As shown in FIG. 1 , the first PUSCH transmission is part 1 in slot #0. Therefore, the TBS determination is based on the number of RBs in part 1.

[0193] VI.2. Example 2 : One RB number is the number of RBs of the frequency domain resources used by a specific PUSCH transmission, where the specific PUSCH transmission may be indicated by RRC signaling or DCI signaling from the gNB or may be predefined in the 3GPP specification. The transport block size may be determined based on the frequency resource size of one repetition of the PUSCH transmission. One repetition may be indicated by the BS or predetermined in the protocol. The PUSCH transmission may use PUSCH repetition type B.

[0194] The transport block size may be determined based on the frequency resource size of the PUSCH transmission on one time slot. One time slot may be indicated by the BS or predetermined in the protocol. The PUSCH transmission may use PUSCH repetition type A or TB OMS.

[0195] Embodiment 2 may be similar to step 2-1 of embodiment 1. With respect to embodiment 1, embodiment 2 uses the frequency resource size used by a specific PUSCH transmission instead of the frequency resource size used by the first PUSCH transmission. For example, the specific PUSCH transmission may be the second PUSCH transmission or the last PUSCH transmission.

[0196] VI.3. Example 3 : One RB number is the minimum RB number of at least two RB numbers. The transport block size may be determined based on the minimum size of at least two frequency resources. In this case, the determined TBS may be lower, resulting in a lower code rate and better communication robustness.

[0197] VI.3.i. Example 3-1

[0198] For PUSCH with PUSCH repetition type A, such as Figure 8As shown in FIG. 1 , there are two RB numbers. Therefore, TBS determination is based on the smaller RB number, such as the RB number of repetition 1 or repetition 2.

[0199] VI.4. Example 4 : One RB number is the maximum (or highest) RB number of at least two RB numbers. The transport block size may be determined based on the maximum (or highest) size of at least two frequency resources. In this case, the determined TBS may be larger (higher), which may result in higher code rate and higher capacity.

[0200] VI.4.i. Example 4-1

[0201] For PUSCH with PUSCH repetition type B, such as Fig. 9 As shown in (B), there are two RB numbers. Therefore, TBS determination is based on the larger (higher) RB number, such as the RB number of actual repetition 6 or repetition 7.

[0202] VI.5. Example 5 : One RB number is the number of RBs used by PUSCH transmission in a normal time slot, where the normal time slot is a time slot not used for subband full-duplex. The transport block size may be determined based on the size of one frequency resource of at least two frequency resources, and one frequency resource is used for PUSCH transmission in a time unit without subband full-duplex transmission.

[0203] VI.5.i. Example 5-1

[0204] For PUSCH with PUSCH repetition type A, such as Figure 8 As shown in FIG. 1 , there are two RB numbers. Therefore, TBS determination is based on the RB number of PUSCH transmission in normal time slots (eg, time slot #2 and time slot #3).

[0205] VI.6. Example 6 : One RB number is the number of RBs used by PUSCH transmission in a sub-band full-duplex time slot. The transport block size may be determined based on the size of one frequency resource among at least two frequency resources, and one frequency resource is used for PUSCH transmission in a time unit with sub-band full-duplex transmission.

[0206] VI.6.i. Example 6-1

[0207] For PUSCH with PUSCH repetition type B, such as Fig. 9 As shown in (B), there are two RB numbers. Therefore, TBS determination is based on the RB number of the actual repeated PUSCH transmission in the dim duplex time slot (eg, time slot #0 or time slot #1).

[0208] VI.7. Example 7: One RB number is indicated by the gNB from at least two PRB numbers. The transport block size may be determined based on one size indicated by the BS from among at least two different sizes.

[0209] The gNB may indicate TBS determination using a maximum size or a minimum size, using a size in a full-duplex slot or a normal slot, or using one of at least two numbers of RBs indicated by RRC signaling or DCI.

[0210] VI.8. Example 8 : One RB number is the number of RBs used by more PUSCH transmissions. The transport block size may be determined based on the size of one frequency resource among at least two frequency resources, and one frequency resource is most frequently used for PUSCH transmissions.

[0211] In Embodiment 8, one RB number may be used by more PUSCH transmissions among all remaining PUSCH transmissions after semi-static DL symbol omission configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0212] VI.8.i. Example 8-1

[0213] like Fig. 9 As shown in (B), five (5) actual repetitions use a smaller (lower) RB number and only one (1) uses a larger (higher) RB number. Because there are more repetitions using a smaller RB number than a larger RB number, the smaller RB number is used for TBS determination.

[0214] For embodiment 1-8 of step 2-1, the UE does not expect the coding rate to exceed the maximum coding rate.

[0215] VI.9. Example 9 : TBS determination is also based on a scaling factor and one of the at least two numbers of RBs. One of the at least two numbers of RBs may be determined based on the operations disclosed in any one of embodiments 1-8 of step 2-1. The transport block size may be determined based on a scaling factor and one or more of the at least two frequency resources, and the scaling factor is assigned by the BS or predetermined in a protocol.

[0216] The UE determines the total number of REs allocated for PUSCH (N RE )as follows.

[0217] - For TB processing over multiple time slots, N RE =N*min(156,N′ RE )·n PRB *f, where n PRBis the total number of PRBs allocated to the UE, and N is the number of time slots used for TBS determination indicated by numberOfSlotsTBoMS. Where f is the scaling factor.

[0218] - Otherwise, N RE =min(156,N′ RE )·n PRB *f.

[0219] VII. Step 2-2 : Determine the TBS of PUSCH transmission based on at least two RB numbers.

[0220] The UE determines the total number of REs allocated for PUSCH (N RE )as follows.

[0221] - For TB processing over multiple time slots, where n PRB (i) is the total number of PRBs allocated to the UE in the i-th slot among N slots, and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS.

[0222] - or for TB processing over multiple time slots, where n PRB N(i) is one of the total number of PRBs allocated to the UE among the M number of RBs, and N(i) is the number of timeslots used for TBS determination using n PRB (i) The number of time slots, and N is indicated by numberOfSlotsTBoMS.

[0223] For PUSCH transmission with TBOMS, such as Fig.11 As shown in FIG. 1 , the total number of PRBs allocated to the UE in the first and second time slots is R1, and the total number of PRBs allocated to the UE in the third and fourth time slots is R2. RE =min(156,N′ RE )*R1*2+min(156,N′ RE )*R2*2.

[0224] Fig.12 is a flow chart of a method 1200 performed by a UE according to some embodiments of the present application. Fig.12 The method described in Figure 1 UE 103 executes in.

[0225] Method 1200 includes operations 1201, 1203, and 1205. In operation 1201, the UE may determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block, wherein the at least two frequency resources have at least two different sizes. In operation 1203, the UE may determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources. In operation 1205, the UE performs the PUSCH transmission. The at least two different sizes may be the number of resource blocks (RBs) or the number of resource elements (REs).

[0226] In some embodiments, PUSCH transmission may be used for repeated transmission of transport blocks on one or more time slots or may be used for transmitting transport blocks on multiple time slots. In a PUSCH repetition type B scheme, PUSCH transmission may be used for repeated transmission of transport blocks on one time slot.

[0227] In some embodiments, PUSCH transmission for transmitting transport blocks may use one of the following schemes: physical uplink shared channel (PUSCH) repetition type A, PUSCH repetition type B, or transport block processing over multiple slots (TBOMS).

[0228] In some embodiments, the transport block size of the PUSCH transmission may be determined based on one of at least two frequency resources.

[0229] In some embodiments, the transport block size may be determined based on the size of one frequency resource of the at least two frequency resources.One frequency resource may be used for the first repetition of PUSCH transmission in the time domain or may be used for PUSCH transmission in the first time slot.

[0230] In some embodiments, the first repetition may be a first actual repetition or a first nominal repetition in the time domain.

[0231] In some embodiments, the PUSCH transmission may be the remaining PUSCH transmission after handling collisions between PUSCH transmissions and semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0232] In some embodiments, the transport block size may be determined based on a first frequency resource size of one repetition of a PUSCH transmission indicated by a base station (BS) or predetermined in a protocol. One repetition of a PUSCH transmission may be an actual repetition or a nominal repetition. A PUSCH transmission may use PUSCH repetition type B.

[0233] In some embodiments, the transport block size may be determined based on the second frequency resource size of the PUSCH transmission on one time slot. One time slot may be indicated by a base station (BS) or predetermined in a protocol. The PUSCH transmission may use PUSCH repetition type A or TBOMS.

[0234] In some embodiments, the PUSCH transmission may be the remaining PUSCH transmission after handling collisions between PUSCH transmissions and semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0235] In some embodiments, the transport block size may be determined based on a minimum size of at least two frequency resources.

[0236] In some embodiments, the transport block size may be determined based on a maximum size of at least two frequency resources.

[0237] In some embodiments, the transport block size may be determined based on the size of one of the at least two frequency resources, and one frequency resource is used for PUSCH transmission in a time unit without sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a subslot.

[0238] In some embodiments, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource may be used for PUSCH transmission in a time unit with sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0239] In some embodiments, the transport block size may be determined based on one size among at least two different sizes indicated by a base station (BS).

[0240] In some embodiments, the transport block size may be determined based on the size of one frequency resource of the at least two frequency resources.One frequency resource may be most frequently used for PUSCH transmission.

[0241] In some embodiments, the transport block size may be determined based on a scaling factor and one or more of the at least two frequency resources. The scaling factor may be assigned by the BS or predetermined in a protocol.

[0242] In some embodiments, at least two frequency resources may be used to transmit a transport block over a plurality of time slots.The transport block size may be determined based on all sizes of the at least two different sizes.

[0243] Fig.13 is a flow chart of a method 1300 performed by a BS according to some embodiments of the present application. Fig.13 The method described in Figure 1 BS101 is implemented in

[0244] The method 1300 includes operations 1301, 1303, and 1305. In operation 1301, the BS may determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block. The at least two frequency resources have at least two different sizes. In operation 1303, the BS may determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources. In operation 1305, the BS may receive the PUSCH transmission. The at least two different sizes may be the number of resource blocks (RBs) or the number of resource elements (REs).

[0245] In some embodiments, PUSCH transmission may be used for repeated transmission of transport blocks on one or more time slots or may be used for transmitting transport blocks on multiple time slots. In a PUSCH repetition type B scheme, PUSCH transmission may be used for repeated transmission of transport blocks on one time slot.

[0246] In some embodiments, PUSCH transmission for transmitting transport blocks may use one of the following schemes: physical uplink shared channel (PUSCH) repetition type A, PUSCH repetition type B, or transport block processing over multiple slots (TBOMS).

[0247] In some embodiments, the transport block size of the PUSCH transmission may be determined based on one of at least two frequency resources.

[0248] In some embodiments, the transport block size may be determined based on the size of one frequency resource among at least two frequency resources, and the one frequency resource is used for the first repetition of PUSCH transmission in the time domain or for PUSCH transmission in the first time slot.

[0249] In some embodiments, the first repetition may be a first actual repetition or a first nominal repetition in the time domain.

[0250] In some embodiments, the PUSCH transmission may be the remaining PUSCH transmission after handling collisions between PUSCH transmissions and semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0251] In some embodiments, the transport block size may be determined based on a first frequency resource size of one repetition of a PUSCH transmission indicated by the BS or predetermined in the protocol. One repetition of a PUSCH transmission may be an actual repetition or a nominal repetition. A PUSCH transmission may use PUSCH repetition type B.

[0252] In some embodiments, the transport block size may be determined based on the second frequency resource size of the PUSCH transmission on one time slot. One time slot may be indicated by the BS or predetermined in the protocol. The PUSCH transmission may use PUSCH repetition type A or TBOMS.

[0253] In some embodiments, the PUSCH transmission may be the remaining PUSCH transmission after handling collisions between PUSCH transmissions and semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0254] In some embodiments, the transport block size may be determined based on a minimum size of at least two frequency resources.

[0255] In some embodiments, the transport block size may be determined based on a maximum size of at least two frequency resources.

[0256] In some embodiments, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource may be used for PUSCH transmission in a time unit without sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0257] In some embodiments, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource may be used for PUSCH transmission in a time unit with sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0258] In some embodiments, the transport block size may be determined based on one size among at least two different sizes indicated by the BS.

[0259] In some embodiments, the transport block size may be determined based on the size of one frequency resource of the at least two frequency resources.One frequency resource may be most frequently used for PUSCH transmission.

[0260] In some embodiments, the transport block size may be determined based on a scaling factor and one or more of the at least two frequency resources. The scaling factor may be assigned by the BS or predetermined in a protocol.

[0261] In some embodiments, at least two frequency resources may be used to transmit a transport block over a plurality of time slots.The transport block size may be determined based on all sizes of the at least two different sizes.

[0262] Fig.14 14 is a block diagram of an exemplary device 1400 according to some embodiments of the present application. Device 1400 may be a UE (eg, UE 103) or a BS (eg, BS 101).

[0263] refer to Fig.14 , the apparatus 1400 may include at least one transmitter 1402, at least one receiver 1404, and at least one processor 1406. The at least one transmitter 1402 is coupled to the at least one processor 1406, and the at least one receiver 1404 is coupled to the at least one processor 1406. The at least one transmitter 1402 may be coupled with the at least one receiver 1404.

[0264] Although in this figure, elements such as transmitter 1402, receiver 1404, and processor 1406 are illustrated as singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, transmitter 1402 and receiver 1404 may be combined into one device, such as a transceiver. In some embodiments of the present application, apparatus 1400 may further include an input device, a memory, and / or other components. Transmitter 1402, receiver 1404, and processor 1406 may be configured to perform any of the methods described herein (e.g., regarding Fig.12 and 13 ).

[0265] According to some embodiments of the present application, the device 1400 may be a UE. In some embodiments of the present application, the processor 1406 may be configured to: determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block, wherein the at least two frequency resources have at least two different sizes; determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and perform PUSCH transmission via a wireless transceiver (or transmitter 1402, receiver 1404). The at least two different sizes may be the number of resource blocks (RBs) or the number of resource elements (REs).

[0266] In some embodiments of the present application, PUSCH transmission may be used for repeated transmission of a transport block on one or more time slots or may be used to transmit a transport block on multiple time slots.

[0267] In some embodiments of the present application, PUSCH transmission for transmitting transport blocks may use one of the following schemes: physical uplink shared channel (PUSCH) repetition type A, PUSCH repetition type B, or transport block processing over multiple slots (TBOMS).

[0268] In some embodiments of the present application, the transport block size of the PUSCH transmission may be determined based on one of at least two frequency resources.

[0269] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources.One frequency resource may be used for the first repetition of PUSCH transmission in the time domain or for PUSCH transmission in the first time slot.

[0270] In some embodiments of the present application, the first repetition may be a first actual repetition or a first nominal repetition in the time domain.

[0271] In some embodiments of the present application, the PUSCH transmission may be the remaining PUSCH transmission after handling the collision between the PUSCH transmission and the semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0272] In some embodiments of the present application, the transport block size may be determined based on a first frequency resource size of one repetition of PUSCH transmission indicated by a base station (BS) or predetermined in a protocol. One repetition of PUSCH transmission may be an actual repetition or a nominal repetition. PUSCH transmission may use PUSCH repetition type B.

[0273] In some embodiments of the present application, the transport block size may be determined based on the second frequency resource size of the PUSCH transmission on one time slot. One time slot may be indicated by a base station (BS) or predetermined in a protocol. The PUSCH transmission may use PUSCH repetition type A or TBOMS.

[0274] In some embodiments of the present application, the PUSCH transmission may be the remaining PUSCH transmission after handling the collision between the PUSCH transmission and the semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0275] In some embodiments of the present application, the transport block size may be determined based on the minimum size of at least two frequency resources.

[0276] In some embodiments of the present application, the transport block size may be determined based on the maximum size of at least two frequency resources.

[0277] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource may be used for PUSCH transmission in a time unit without sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0278] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource is used for PUSCH transmission in a time unit with sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0279] In some embodiments of the present application, the transport block size may be determined based on one size indicated by a base station (BS) among at least two different sizes.

[0280] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource among the at least two frequency resources. One frequency resource may be most frequently used for PUSCH transmission.

[0281] In some embodiments of the present application, the transport block size may be determined based on a scaling factor and one or more of the at least two frequency resources. The scaling factor may be assigned by the BS or predetermined in a protocol.

[0282] In some embodiments of the present application, at least two frequency resources may be used to transmit a transport block over a plurality of time slots. The transport block size is determined based on all sizes of at least two different sizes.

[0283] According to some embodiments of the present application, the device 1400 may be a BS. In some embodiments of the present application, the processor 1406 may be configured to: determine at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block, wherein the at least two frequency resources have at least two different sizes; determine a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and receive the PUSCH transmission via a wireless transceiver (or transmitter 1402, receiver 1404). The at least two different sizes may be the number of resource blocks (RBs) or the number of resource elements (REs).

[0284] In some embodiments of the present application, PUSCH transmission may be used for repeated transmission of a transport block on one or more time slots or may be used to transmit a transport block on multiple time slots.

[0285] In some embodiments of the present application, PUSCH transmission for transmitting transport blocks may use one of the following schemes: physical uplink shared channel (PUSCH) repetition type A, PUSCH repetition type B, or transport block processing over multiple slots (TBOMS).

[0286] In some embodiments of the present application, the transport block size of the PUSCH transmission may be determined based on one of at least two frequency resources.

[0287] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources.One frequency resource may be used for the first repetition of PUSCH transmission in the time domain or for PUSCH transmission in the first time slot.

[0288] In some embodiments of the present application, the first repetition may be a first actual repetition or a first nominal repetition in the time domain.

[0289] In some embodiments of the present application, the PUSCH transmission may be the remaining PUSCH transmission after handling the collision between the PUSCH transmission and the semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0290] In some embodiments of the present application, the transport block size may be determined based on the first frequency resource size of one repetition of PUSCH transmission indicated by the BS or predetermined in the protocol. One repetition of PUSCH transmission may be an actual repetition or a nominal repetition. PUSCH transmission may use PUSCH repetition type B.

[0291] In some embodiments of the present application, the transport block size may be determined based on the second frequency resource size of the PUSCH transmission on one time slot. One time slot may be indicated by the BS or predetermined in the protocol. The PUSCH transmission may use PUSCH repetition type A or TBOMS.

[0292] In some embodiments of the present application, the PUSCH transmission may be the remaining PUSCH transmission after handling the collision between the PUSCH transmission and the semi-static DL symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0293] In some embodiments of the present application, the transport block size may be determined based on the minimum size of at least two frequency resources.

[0294] In some embodiments of the present application, the transport block size may be determined based on the maximum size of at least two frequency resources.

[0295] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources. One frequency resource may be used for PUSCH transmission in a time unit without sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a sub-time slot.

[0296] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource of at least two frequency resources, and one frequency resource is used for PUSCH transmission in a time unit with sub-band full-duplex transmission. The time unit may be a time slot, a symbol, a frame, a subframe, or a subslot.

[0297] In some embodiments of the present application, the transport block size may be determined based on one size indicated by the BS among at least two different sizes.

[0298] In some embodiments of the present application, the transport block size may be determined based on the size of one frequency resource among the at least two frequency resources. One frequency resource may be most frequently used for PUSCH transmission.

[0299] In some embodiments of the present application, the transport block size may be determined based on a scaling factor and one or more of the at least two frequency resources. The scaling factor may be assigned by the BS or predetermined in a protocol.

[0300] In some embodiments of the present application, at least two frequency resources may be used to transmit a transport block over multiple time slots.The transport block size may be determined based on all sizes of at least two different sizes.

[0301] In some embodiments of the present application, the device 1400 may further include at least one non-transitory computer-readable medium. In some embodiments of the present disclosure, the non-transitory computer-readable medium may store computer-executable instructions to enable the processor 1406 to implement any of the methods described above. For example, when the computer-executable instructions are executed, the processor 1406 may interact with the transmitter 1402 and / or the receiver 1404 to perform, for example, Fig.12 and 13 Operation of the method described.

[0302] The method according to the embodiment of the present application case can also be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special-purpose computer, a programmed microprocessor or microcontroller and a peripheral integrated circuit element, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device or the like. In general, any device on which a finite state machine capable of implementing the flow chart shown in the figure resides can be used to implement the processor function of the present application case. For example, an embodiment of the present application case provides a device for determining TBS including a processor and a memory. Computer programmable instructions for implementing the method for determining TBS are stored in a memory, and the processor is configured to execute computer programmable instructions to implement the method for determining TBS. The method for determining TBS can be any method described in the present application case.

[0303] It should be understood by those skilled in the art that as technology develops and advances, the terms described in the present application may change and should not affect or limit the principle and spirit of the present application.

[0304] Alternative embodiments preferably implement methods according to embodiments of the present application in a non-transitory computer-readable storage medium storing computer programmable instructions. The instructions are preferably executed by a computer-executable component that is preferably integrated with a network security system. The non-transitory computer-readable storage medium may be stored on any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, optical storage device (CD or DVD), hard drive, floppy disk drive, or any suitable device. The computer-executable component is preferably a processor, but the instructions may be executed alternatively or additionally by any suitable dedicated hardware device. For example, embodiments of the present application provide a non-transitory computer-readable storage medium having computer programmable instructions stored therein. The computer programmable instructions are configured to implement a method for determining a transport block size according to any embodiment of the present application.

[0305] Although the present application has been described using its specific embodiments, it is obvious that a person skilled in the art will understand many substitutions, modifications and changes. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, it will enable a person of ordinary skill in the art of the disclosed embodiments to make and use the teachings of the present application by simply adopting the elements of the independent claims. Therefore, the embodiments of the present application as described herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present application.

[0306] In this document, the terms "comprises," "comprising," or any other variations thereof, are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a series of elements includes not only the elements but may also include other elements not expressly listed or inherent to the process, method, article, or apparatus. In the absence of further constraints, an element preceded by "a," "an," or the like does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element. In addition, the term "another" is defined as at least a second or more. The terms "include," "have," and the like, as used herein, are defined as "including."

Claims

1. A user equipment UE, comprising: Wireless transceiver; and a processor coupled to the wireless transceiver and configured to: determining at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block, wherein the at least two frequency resources have at least two different sizes; determining a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and The PUSCH transmission is performed via the wireless transceiver. 2 . The UE according to claim 1 , wherein the PUSCH transmission is used for repeated transmission of the transport block over one or more time slots or for transmitting the transport block over the multiple time slots. 3 . The UE according to claim 1 , wherein the transport block size of the PUSCH transmission is determined based on one of the at least two frequency resources.

4. The UE according to claim 3, wherein the transport block size is determined based on the size of one frequency resource among the at least two frequency resources, and the one frequency resource is used for the first repetition of the PUSCH transmission in the time domain or for the PUSCH transmission in the first time slot. The UE according to claim 4 , wherein the first repetition is a first actual repetition or a first nominal repetition in the time domain. 6 . The UE according to claim 3 , wherein the transport block size is determined based on a first frequency resource size of one repetition of the PUSCH transmission indicated by a base station BS or predetermined in a protocol.

7. The UE according to claim 3, wherein the transport block size is determined based on a second frequency resource size of the PUSCH transmission on one time slot, the one time slot being indicated by a base station BS or predetermined in the protocol.

8. The UE according to claim 3, wherein the transport block size is determined based on a minimum size of the at least two frequency resources.

9. The UE according to claim 3, wherein the transport block size is determined based on a size of one frequency resource among the at least two frequency resources, and the one frequency resource is used for the PUSCH transmission in a time unit with sub-band full-duplex transmission.

10. The UE according to claim 3, wherein the transport block size is determined based on one size indicated by a base station BS among the at least two different sizes.

11. The UE according to claim 3, wherein the transport block size is determined based on a size of one frequency resource among the at least two frequency resources, and the one frequency resource is most frequently used for the PUSCH transmission.

12. The UE of claim 3, wherein the transport block size is determined based on a scaling factor and one or more of the at least two frequency resources, and the scaling factor is assigned by a BS or predetermined in a protocol.

13. The UE of claim 1, wherein the at least two frequency resources are used to transmit the transport block over a plurality of time slots, and the transport block size is determined based on all sizes of the at least two different sizes.

14. A base station BS, comprising: Wireless transceiver; and a processor coupled to the wireless transceiver and configured to: determining at least two frequency resources for a physical uplink shared channel (PUSCH) transmission for transmitting a transport block, wherein the at least two frequency resources have at least two different sizes; determining a transport block size for the PUSCH transmission based on one or more of the at least two frequency resources; and The PUSCH transmission is received via the wireless transceiver.

15. The BS of claim 14, wherein the at least two frequency resources are used to transmit the transport block over a plurality of time slots, and the transport block size is determined based on all sizes of the at least two different sizes.

Images