Method and system for coverage enhancement in wireless networks

Abstract

Methods and systems for coverage enhancement in wireless networks are disclosed. In one aspect, a method of wireless communication is disclosed. The method includes a network node configuring a multi-slot transmission by determining a number of repetitions of a transmission based on available slots according to a rule for performing repeated transmissions in consecutive slots, and transmitting a message according to the repetitions.

Description

Technical Field

[0001] This disclosure generally pertains to digital wireless communications. Background Technology

[0002] Mobile telecommunications technologies are driving the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide more complex and demanding access requirements and flexibility.

[0003] Long-Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE-Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system, known as 5G, advances the LTE and LTE-A wireless standards and aims to support higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging service requirements. Summary of the Invention

[0004] On one hand, a method for data communication is disclosed. The method includes: a network node configuring multi-slot transmission by determining the number of repeated transmissions based on available time slots according to rules for performing repeated transmissions in consecutive time slots, and transmitting messages according to the repeated transmissions.

[0005] On the other hand, a data communication method is disclosed. The method includes: a network node configuring multi-timeslot transmission by determining the transmission power of the transmission or repeated transmission according to rules for performing repeated transmissions in consecutive time slots, and performing the transmission or repeated transmission.

[0006] On the other hand, a data communication method is disclosed. The method includes: a user equipment determining the availability of a transmission or repeated transmission to perform a transmission in multiple time slots; the user equipment determining the availability of transport block processing on the multiple time slots; when it is determined that the transmission or repeated transmission and the transport block processing on the multiple time slots are available, performing a first determination of the number of transmissions or repeated transmissions and the number of the multiple time slots; and performing the transmission based on the first determination.

[0007] On the other hand, a data communication method is disclosed. The method includes: a user equipment determining the availability of a transmission or repeated transmission to perform a transmission in multiple time slots; the user equipment determining the availability of transport block processing on the multiple time slots; calculating a transport block size based on a single time slot or multiple time slots when it is determined that the transmission or repeated transmission and the transport block processing on the multiple time slots are available; and performing the transmission or repeated transmission based on the transport block size.

[0008] On the other hand, a data communication method is disclosed. The method includes: a user equipment determining the availability of a transmission or retransmission for transmitting a Physical Uplink Shared Channel (PUSCH) in multiple uplink time slots; the user equipment determining the availability of transport block processing on the multiple uplink time slots; when the transmission or retransmission and the transport block processing on the multiple uplink time slots are determined to be available, multiplexing uplink control information (UCI) on the multiple uplink time slots associated with the transport block processing; and transmitting the uplink control information (UCI) and the PUSCH to a network node.

[0009] On the other hand, a data communication method is disclosed. The method includes: a user equipment determining the availability of repeated transmissions for transmitting Msg3 to a network node; configuring a first TDRA table different from an existing Time Domain Resource Allocation (TDRA) table; determining that the first TDRA table includes a repetition factor; performing the repeated transmissions using the first TDRA table for time domain resource allocation; and, when it is determined that no TDRA table is configured, using a default table for time domain resource allocation.

[0010] On the other hand, a method for data communication is disclosed. The method includes: determining the availability of repetitive transmissions for Msg3 transmission; determining the availability of frequency hopping; and, when it is determined that the repetitive transmissions and frequency hopping for Msg3 transmission are available, executing an instruction to perform frequency hopping between time slots.

[0011] On the other hand, a method for data communication is disclosed. The method includes: determining the availability of Msg3 repetition transmission; and, when the availability of Msg3 repetition transmission is determined, instructing the enabling of Redundancy Version (RV) mode, cross-slot channel estimation, and enhanced PUSCH repetition type A.

[0012] On the other hand, a data communication method is disclosed. The method includes: determining an inter-slot FH mode and an inter-slot FH bundle based on a time division duplex (TDD) configuration and a frequency hopping (FH) bundle definition; and performing repeated transmissions using the inter-slot FH mode.

[0013] In another example aspect, a wireless communication device is disclosed, which includes a processor configured to implement the methods described above.

[0014] In another example, a computer storage medium is disclosed, on which code for implementing the above-described methods is stored.

[0015] These and other aspects are described in this document. Attached Figure Description

[0016] Figure 1 An example of a redundant version (RV) sequence for repeated transmission of the Physical Uplink Shared Channel (PUSCH) is shown.

[0017] Figure 2 Another example of an RV sequence used for repeated PUSCH transmission is shown.

[0018] Figure 3A An example of single-slot repetition for TB processing is shown. Figure 3B An example of multi-slot repetition for TB processing is shown.

[0019] Figure 4A An example of RV and repetition patterns for transport block (TB) processing with multiple consecutive time slots having repetition is shown. Figure 4B Another example of RV and repetition patterns for TB processing is shown.

[0020] Figure 5 An example of an RV mode for TB processing with multiple repeating time slots is shown.

[0021] Figure 6 Another example of RV mode for TB processing with multiple repeating time slots is shown.

[0022] Figure 7 An example of a conflict between the Physical Uplink Control Channel (PUCCH) and the PUSCH is shown.

[0023] Figure 8 Different inter-slot frequency hopping (FH) modes in the time domain are shown for a PUSCH with 8 repetitions in TDD and an inter-slot FH beam size of 2.

[0024] Figure 9 The diagram shows a comparison of setting a random access contention resolution timer (ra-ContentionResolutionTimer) for conventional Msg3 transport and for Msg3 repetition with a repetition factor of 2 when TDD is configured as "DDDSU".

[0025] Figure 10 The comparison of setting the random access contention resolution timer for conventional Msg3 transmission and Msg3 repetition with a repetition factor of 4 is shown with TDD configured as "DDDDDDDSUU".

[0026] Figure 11 An example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0027] Figure 12 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0028] Figure 13 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0029] Figure 14 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0030] Figure 15 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0031] Figure 16 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0032] Figure 17 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0033] Figure 18 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0034] Figure 19 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0035] Figure 20 An example of a wireless communication system is shown.

[0036] Figure 21 It is a block diagram representation of a portion of a radio station based on one or more embodiments of the disclosed technology. Detailed Implementation

[0037] The section headings used in this document are for ease of understanding only and do not limit the scope of the embodiments to the sections describing them. Furthermore, although embodiments are described with reference to 5G examples, the disclosed techniques can be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0038] Current standards provide new WIDs (Work Item Descriptions) for NR (New Radio) coverage enhancement, but some coverage bottlenecks still exist. For example, Msg3 and PUSCH (Physical Uplink Shared Channel) in a connected state are potential coverage bottleneck channels. In some embodiments, the disclosed techniques can be used to address the problem of coverage bottleneck channels. Specifically, some embodiments of the disclosed techniques provide enhancement mechanisms for both Msg3PUSCH and PUSCH in a connected state.

[0039] Coverage is one of the key factors that operators consider when commercializing cellular networks, as it directly impacts service quality as well as capital expenditure (CAPEX) and operating expenditure (OPEX). While coverage is crucial for the success of NR commercialization, to date, no comprehensive coverage assessment has been conducted, nor has a comparison with traditional RATs been made that considers all the details of the NR specifications.

[0040] In the physical channel, Msg3 PUSCH and PUSCH are potential coverage bottleneck channels and require corresponding enhancements. For PUSCH transmission, the number of PUSCH type A repetitions determined based on the available UL time slots and TB (transmission block) processing over multiple time slots is proposed as a coverage enhancement method. Then, methods for distinguishing whether the repetition count is based on available UL time slots, as well as methods for calculating transmission power, TBS, time slot number indication, and UCI (uplink control information) multiplexing on PUSCHs undergoing TB processing over multiple time slots, should be determined.

[0041] For Msg3 PUSCH, a simple approach is to apply repeated transmissions. This requires a solution to indicate the number of repetitions to the User Equipment (UE). Furthermore, in addition to Msg3 PUSCH repetition, other features can be supported, such as inter-slot frequency hopping (FH), RV (Redundancy Version) cycling between repetitions, cross-slot channel estimation, and a contention resolution timer for each repetition, along with corresponding signaling indications.

[0042] This patent document uses only examples from the 3GPP New Radio (NR) network architecture and 5G protocols to facilitate understanding, and the disclosed technologies and embodiments can be practiced in other wireless systems using communication protocols different from 3GPP protocols.

[0043] In this patent document, the terms “repeated transmission” and “transmission repetition” can be used to refer to the repeated transmission of information via at least one of the Physical Uplink Shared Channel (PUSCH), Physical Data Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), or any other channel.

[0044] In the context of this patent document, the indefinite article “a” or “an” has the meaning of “one or more”.

[0045] Exemplary Example 1

[0046] In Rel-17, PUSCH repetition type A needs to be enhanced. One mechanism for determining PUSCH repetition type A enhancement is based on the available UL slots, namely the number of repetitions, or performing a count of the number of repetitions. However, in Rel-15, when the number of repetitions K>1, the UE repeats TB in K consecutive slots (K consecutive slots apply the same symbol allocation in each slot), and the PUSCH transmission in the slot is omitted when any symbol in the repetition conflicts (or contradicts) the frame structure / another transmission. The disclosed techniques can be implemented in some embodiments to provide a way to distinguish between the two methods discussed below:

[0047] Option 1: Use RRC signaling to indicate whether the number of repetitions is determined based on available UL time slots.

[0048] If the signaling is configured, for example, to be "enable", it means that the number of repetitions is determined based on the available UL time slots. Otherwise, the mechanism in Rel-15 is used.

[0049] Option 2: Use 1 bit in the DCI (Downlink Control Information) to indicate whether the repetition count is determined based on the available UL slots.

[0050] For example, if an indication of "1" is present, the number of repetitions is determined based on the available UL time slots. In other words, the mechanism in Rel-17 can be used, for example, to determine (or count) the number of repetitions. Otherwise, the mechanism in Rel-15 is used.

[0051] Option 3: Use some implicit method to indicate whether the number of repetitions is determined based on the available UL time slots.

[0052] For example, the number of repetitions can be associated with initial access channel enhancement mechanisms. In some embodiments, if repetition is enabled for the initial Msg3 transmission, or if more than one repetition is indicated for the Msg3 transmission, the number of repetitions for the PUSCH transmission is determined based on the available UL time slots. In some embodiments, the number of repetitions for the PUSCH transmission is determined based on the available UL time slots determined by the PRACH (Physical Random Access Channel) format. In one example, all PRACH preambles are grouped into several sets, and when some dedicated preamble sets are used, the number of repetitions for the PUSCH transmission is determined based on the available UL time slots.

[0053] In some embodiments, when the number of repetitions for PUSCH type A is determined based on available UL time slots, the indicated number of repetitions is the actual number of repetitions. In other words, if a repetition is dropped or omitted due to a conflict, that repetition is not counted in the total number of repetitions.

[0054] In some embodiments, when the number of repetitions for PUSCH type A is not determined based on available UL slots, the indicated number of repetitions is the actual number of repetitions. This means that if a repetition is dropped or omitted due to a conflict, that repetition is not counted in the total number of repetitions.

[0055] When the number of repetitions for PUSCH type A is determined based on the available UL time slots, the RV for each actual repetition should be determined. The disclosed techniques can be used to implement the following methods.

[0056] Method 1: RV loop based on actual repetition

[0057] The corresponding RV index for the i-th repetition is equal to the (mod(i-1,M)+1)-th value in the RV sequence, where M equals the length of the RV sequence.

[0058] Method 2: RV loop based on nominal repetition

[0059] Figure 1 An example of a redundant version (RV) sequence for repeated transmission of the Physical Uplink Shared Channel (PUSCH) is shown. Figure 2 Another example of an RV sequence used for repeated PUSCH transmission is shown.

[0060] When a PUSCH repetition conflicts with an SFI (Slot Format Indicator) or other transmissions, the RV index is determined. The nominal repetition count K' equals the actual repetition count K plus the number of discarded repetitions. The RV corresponding to the i-th repetition is equal to the (mod(i-1,M)+1)-th value in the RV sequence, where M equals the length of the RV sequence. For example, as... Figure 1As shown, the number of repetitions K is equal to 4, and the RV sequence is {0,2,3,1}. When the second “nominal” repetition conflicts with or contradicts SFI, the actual repetition RV cycle is {0,3,1,0}.

[0061] Furthermore, discarded duplicate RVs in the sequence are deferred to the last duplicate transmission. For example, such as Figure 2 As shown, the number of repetitions K is equal to 4, and the RV sequence is {0,2,3,1}. When the second “nominal” repetition conflicts with SFI, the actual repetition of the RV cycle is {0,3,1,2}.

[0062] Exemplary Example 2

[0063] In Rel-15 / 16, channel estimation is based on a single transmission opportunity, and when the UE transmits a PUSCH on an active UL BWPb on carrier f of serving cell c, the UE determines the PUSCH transmission power P in PUSCH transmission opportunity i using the following formula: parameter set configuration with index j and PUSCH power control adjustment state with index l. PUSCH,b,f,c (i,j,q d ,l).

[0064]

[0065] in:

[0066] P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c in PUSCH transmission opportunity i.

[0067] P O_PUSCHb,,f,c (j) is composed of component P O_NOMINAL_PUSCH,f,c (j) and component P O_UE_PUSCH,b,f,c The parameters are composed of the sum of (j), where j∈{0,1,...,J-1}.

[0068] The bandwidth of the PUSCH resource allocation is represented by the number of resource blocks on the effective UL BWPb of the carrier f used for serving cell c, and μ is the SCS configuration defined in [4, TS 38.211].

[0069] K S =1.25, Furthermore, K S When Δ = 0, TF,b,f,c (i) = 0, where K SEach UL BWPb of each carrier f and serving cell c is provided by deltaMCS. If the PUSCH transmission is on more than one layer [6, TS 38.214], then Δ TF,b,f,c (i) = 0. For each carrier f and each serving cell c, the effective UL BWPb, BPRE, and... The calculation method is as follows:

[0070] -For PUSCH with UL-SCH data, Furthermore, for CSI transmission in PUSCH that does not contain UL-SCH data, in,

[0071] -C is the number of code blocks to be transferred, K r It is the size of the code block r, and N RE It is the quantity of resource elements, and is determined as in, It is the number of symbols used for PUSCH transmission opportunity i on the effective ULBWPb of carrier f in serving cell c. It is the number of subcarriers in PUSCH symbol j excluding DM-RS subcarriers and phase-tracking RS samples [4, TS 38.211], and it is assumed that no segmentation of nominal repetitions is performed in the case of PUSCH transmission with repetition type B. And C, K r Defined in [5, TS 38.212].

[0072] - When PUSCH includes UL-SCH data Furthermore, as described in Clause 9.3, when PUSCH includes CSI but excludes UL-SCH data,

[0073] -Q m It is the modulation order, and as described in [6, TS 38.214], R is the target bit rate provided by the DCI format of the scheduled PUSCH transmission, wherein the PUSCH transmission includes CSI but does not include UL-SCH data.

[0074] For PUSCH repetition, cross-slot channel estimation can be used to improve the channel estimation accuracy on the receiver side. However, it is necessary to keep the transmission power constant for each repetition. To achieve this, the following approach can be considered.

[0075] Option 1: Calculate transmission power based on a single transmission occasion (TO) or time slot. Furthermore, when employing DMRS location / granularity optimization in the time domain, a single TO or time slot is the one with the maximum / minimum available REs among multiple TOs or time slots used for joint channel estimation by the gNB. In one example, when the gNB performs channel estimation across N TOs or time slots, the transmission power is calculated based on the TO or time slot with the maximum available RE, RE = max{REto1, REto2, ..., REtoi}, where REtoi equals the number of available REs in the i-th TO or time slot. Furthermore, a single TO or time slot can be the first or any one of multiple TOs or time slots.

[0076] Option 2: When the gNB performs channel estimation across multiple TOs or time slots, calculate the transmission power based on all TOs or time slots. The number of available REs is equal to: REto1 + REto2 + ... + REtoi, where REtoi is equal to the number of available REs in the i-th TO or time slot.

[0077] Furthermore, when TB processing is enabled on multiple time slots, a similar method can be reused for transmission power calculation.

[0078] Method 1: When determining the Transport Block Size (TBS) based on a single timeslot, the transmission power is calculated based on that single timeslot. Furthermore, a single timeslot is the timeslot with the maximum / minimum available RE among multiple timeslots used for TB processing. Additionally, a single timeslot can be the first or any one of multiple timeslots.

[0079] Method 2: When the transport block size (TBS) is determined based on multiple time slots, the transmission power is calculated based on the entire time slot.

[0080] Exemplary Example 3

[0081] The Rel-17 coverage enhancement work item supports TB processing over multiple time slots. The number of time slots spanned by the TB needs to be determined. Furthermore, if repetition and TB processing are supported simultaneously over multiple time slots, the number of time slots and the number of repetitions for the TB processing need to be further determined. In some embodiments, the number of time slots can be consecutive. In some embodiments, the number of time slots can be discontinuous. In some embodiments, the number of time slots can be consecutive available time slots. In some embodiments, the number of time slots can be discontinuous available time slots.

[0082] Figure 3A An example of single-slot repetition for TB processing is shown.

[0083] In some embodiments, repetition is a single-slot PUSCH repetition. A single-slot repetition means that there is one slot in each PUSCH repetition transmission. For example, when the repetition count is configured to 4 and the number of slots for TB processing is 2, then each repetition transmission includes slots in the time domain and the total number of slots for PUSCH repetition transmissions is 4 (assuming no repetition transmissions are omitted), and TB processing occurs over two slots, such as... Figure 3A As shown in the image.

[0084] In some embodiments, repetition involves repeating the TB process over multiple time slots. For example, there are a total of four time slots, where the TB process is repeated in the first two time slots and in the last two time slots. The disclosed techniques can be used to implement the following methods.

[0085] Figure 3B An example of multi-slot repetition for TB processing is shown.

[0086] In some embodiments, repetition is a multi-slot repetition used for TB processing over multiple slots, meaning that there are multiple slots in each PUSCH repetition transmission, and the same symbols are assigned in each slot. For example, when the number of repetitions is configured to 4 and the number of slots for TB processing is 2, then each repetition transmission includes 2 slots in the time domain, and the total number of slots used for PUSCH transmission is: 4*2=8 (assuming no repetition transmissions are omitted). Figure 3B As shown in the image.

[0087] Option 1: Reuse the current mechanism to indicate the number of repetitions when repetition is enabled, and separately indicate the number of time slots used for TB processing.

[0088] Option 1-1: Use a set of values ​​in RRC signaling to indicate the number of time slots, and reuse some bit fields in DCI, such as the FDRA (Frequency Domain Resource Allocation) field, to indicate the number of time slots.

[0089] Option 1-2: Joint encoding with the TDRA table. Add a column to the TDRA table to indicate the number of time slots. Additionally, jointly encode the number of time slots used for TB processing and the repetition count K (if repetition is enabled), and configure a table where each code point represents the number of time slots used for TB processing and the repetition count (furthermore, the number of time slots is no greater than the repetition count). For example, when the code point value is represented as "0", the repetition count is equal to 4, and the number of time slots is equal to 2, as shown in Table 1.

[0090] Table 1: Joint coding of the number of time slots and the number of repetitions

[0091] 0 4 2 1 8 4 … … … N 16 4

[0092] In some embodiments, if TB processing is enabled on multiple time slots, and repetition is a repetition of TB processing on multiple time slots, the process needs to determine when a portion (several symbols or time slots) of the repetition transmission conflicts with SFI or other transmissions. Method 1: Omit only the portion of the time slots in the repetition that conflict with SFI or other transmissions, and transmit the remaining time slots of the repetition. Method 2: Omit the entire repetition transmission.

[0093] Similarly, when supporting both repetition and TB processing simultaneously across multiple time slots, the repetition and RV modes should be determined. The disclosed techniques can be used to implement the following methods.

[0094] Figure 4A An example of RV and repetition patterns for transport block (TB) processing with multiple consecutive time slots having repetition is shown. Figure 4B Another example of RV and repetition patterns for TB processing is shown.

[0095] Method 1: The RV index of the i-th repetition of K is equal to the (mod(K-1,M)+1)-th value of the RV sequence, where M is the length of the RV sequence. For example, when the repetition count K is 4 and the number of time slots is 2, the RV pattern is {0,2,3,1}, as shown below. Figure 4A As shown in the diagram. Each repetition consists of two consecutive time slots, and the RV cycle for each repetition is {0,2,3,1}.

[0096] Furthermore, each repetition includes two discontinuous time slots, and the RV cycle for each repetition is {0,2,3,1}. For example... Figure 4B As shown in the image.

[0097] Figure 5 An example of an RV mode for TB processing with multiple repeating time slots is shown. Figure 6 Another example of RV mode for TB processing with multiple repeating time slots is shown.

[0098] Method 2: RV is the same across multiple time slots processed by TB. The number of K's is determined by the repetition count K and the number of time slots N. The number of K's is equal to ceil(K / N). The RV index of the i-th repetition K' is equal to the (mod(K-1,M)+1)-th value in the RV sequence, where M is the length of the RV sequence. For example, when the repetition count K is 4 and the number of time slots is 2, the RV pattern is {0,2,3,1}, as shown below. Figure 5 As shown in the diagram. Each repetition consists of one time slot, and the RV cycle for each repetition is {0,0,2,2}.

[0099] For CG PUSCH transmissions, the RV indexes in multiple time slots used for TB processing should be identical to aid the receiver in performing timing and frequency tracking. Multiple time slots used for TB processing can be considered as a bundle, with RV cycles performed within these bundles. For example, when the repetition count K is 4 and the number of time slots used for TB processing is 2, the RV pattern is {0,2,3,1}, as shown below. Figure 5 As shown in the diagram, the first two time slots are considered the first bundle, and the last two time slots are considered the second bundle. The RV index of the first bundle is 0, and the RV index of the second bundle is 2. Therefore, the RV indices for each repetition are {0,0,2,2}.

[0100] Furthermore, the RV pattern can be the same or different across multiple time slots used for TB processing, and the RV can be cycled within these multiple time slots. For example, when the repetition count K is 4 and the number of time slots is 2, the RV pattern is {0,2,3,1}, as shown below. Figure 6 As shown in the diagram. Each repetition consists of one time slot, and the RV cycle for each repetition is {0,2,0,2}.

[0101] Exemplary Example 4

[0102] The current standard for TBS measurement procedures for PUSCH is as follows:

[0103] 1) The UE first determines the number of REs (NREs) in the time slot:

[0104] -UE first determines PRB(N') using the following formula. RE The number of REs (N') allocated to PUSCH in ) RE )

[0105] - in, It is the number of subcarriers in the frequency domain within the physical resource block. It is the number of symbols L assigned to the PUSCH according to Clause 6.1.2.1 (for scheduled PUSCH) or Clause 6.1.2.3 (for configured PUSCH). It is the number of REs used by each PRB for DM-RS during the allocated duration. This includes the overhead of DM-RS CDM groups without data, as described in Clause 6.1.2.3 for PUSCHs with configuration authorization, 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 This is the overhead configured through the high-level parameter xOverhead in PUSCH-ServingCellConfig. If If not configured (value is 6, 12, or 18), then It is assumed to be 0. For Msg3 or MsgA PUSCH transmissions, It is always set to 0. In the case of PUSCH repeating type B, It is determined by assuming a duration of L symbols without segmented nominal repetition.

[0106] -UE via N RE =min(156,N') RE )·n PRB Determine the allocation to PUSCH(N) RE The total number of REs, where n PRB This is the total number of PRBs allocated to the UE.

[0107] 2) The non-quantized intermediate variable (Ninfo) is transmitted through N... info =N RE ·R·Q m •υ is obtained.

[0108] If N info ≤3824

[0109] Use step 3 as the next step in the TBS determination in TS 38.214.

[0110] otherwise

[0111] Use step 4 as the next step in the TBS determination in TS 38.214.

[0112] End, if

[0113] NRE is a parameter used for TBS calculations.

[0114] When enabling TB processing across multiple time slots, it is necessary to determine the method for TBS calculation. The disclosed techniques can be used to implement the following methods.

[0115] Option 1: Calculate TBS based on a single time slot used for TB processing across multiple time slots. In some embodiments, the number of available REs is the total number of REs for the PUSCH excluding the reference signal in a time slot. In some embodiments, the single time slot is the first time slot among multiple time slots used for TB processing. In some embodiments, the single time slot is any one of the multiple time slots used for TB processing.

[0116] Option 2: Calculate TBS based on multiple time slots, where the number of available REs is the total number of REs for all PUSCHs across all time slots, excluding the reference signal used for TB processing. In some embodiments, the total number of available REs may not exceed a threshold H, where the value of H may be determined based on a single time slot among the multiple time slots used for TB processing or explicitly indicated by the gNB.

[0117] Furthermore, when TB processing is performed across multiple time slots, the number of resource blocks (RBs) allocated can be reduced accordingly. When the number of RBs allocated is limited, some bits of the FDRA field in the DCI can be saved.

[0118] Option 1: The size of the FDRA field in DCI is related to the number of time slots processed by TB, and the number of RBs is no greater than N_RB / N. Here, N_RB is the maximum number of Bandwidth Parts (BWP), and N is the number of time slots processed by TB. In the current standard, the length of RB is equal to N. If there are no restrictions on RB allocation, then Frequency Domain Resource Allocation (FDRA) requires ceil(log2(N(N+1) / 2)) bits. If RB allocation is performed when the number of RBs allocated is less than Y, then FDRA requires ceil(log2(N*Y*(Y-1) / 2)) bits. The number of bits for FDRA is as follows when Y is different.

[0119] In the current specification, the RIV (Resource Indicator Value) based on a binary tree (piecewise function) does not increase linearly with S+L, where S is the starting point of the RB and L is the length of the RB. A new formula for calculating the RIV is needed. The following formula can be used to implement some embodiments of the disclosed technology:

[0120] RIV=(N-L+2)*(N-L+1) / 2-S-1-(N-Y+1)*(NY) / 2

[0121] In some embodiments, the binary tree-based formula is reused and bits are saved by limiting the flexibility and length of resource allocation. The formula for calculating the FDRA size is as follows:

[0122] FDRA size = ceil(log2(N(N+1) / 2))

[0123] This method requires an additional set of BWP indicators. For example, the number of time slots used for TB processing is equal to 4, and the BWPs are divided into 4 groups, each group being round(BWP / 4) in size, denoted as BWP_set1, BWP_set2, BWP_set3, and BWP_set4. Which BWP group should the UE use? A straightforward approach is to reuse some bits in the FDRA field to indicate the BWP group. For example, 2 bits in the FDRA field are used to indicate the BWP group: "00" for BWP_set1, "01" for BWP_set2, "10" for BWP_set3, and "11" for BWP_set4. The starting RB of each BWP group is equal to: 0 + round(BWP_RB / N) * (Ni-1). BWP_RB is the number of RBs in the BWP, and Ni is the index of BWP_set1.

[0124] Exemplary Example 5

[0125] In the current standard, the data rate limit per CC is as follows:

[0126] For the j-th serving cell, if the higher-level parameter processingType2Enabled of PUSCH-ServingCellConfig is configured for the serving cell and set to enabled, or if for PUSCH, at least one IMCS > W, where W = 28 for MCS tables 5.1.3.1-1 and 5.1.3.1-3, and W = 27 for MCS tables 5.1.3.1-2, 6.1.4.1-1, and 6.1.4.1-2, or if for PUSCH repetition type B it is an actual repetition, then if the following conditions are not met, the UE is not required to process PUSCH transmissions:

[0127]

[0128] in

[0129] -L is the number of symbols assigned to PUSCH.

[0130] -M is the number of TBs in PUSCH.

[0131] - Where μ is the parameter set of PUSCH.

[0132] For the m-th TB,

[0133] -A is the number of bits in a transport block as defined in Clause 6.2.1 of [5, TS 38.212].

[0134] -C is the total number of coded blocks in a transport block as defined in Clause 5.2.2 of [5, TS 38.212].

[0135] -C′ is the number of coded blocks scheduled for the transport block as defined in Clause 5.4.2.1 of [5, TS 38.212].

[0136] - The data rate CC [Mbps] is calculated as the maximum data rate of the carrier in the frequency band of the serving cell for any signaling band combination and feature set consistent with the serving cell, wherein the data rate value is given by the formula in Clause 4.1.2 of [13, TS 38.306], including the scaling factor f(i).

[0137] - Each actual repetition of PUSCH repetition type B is considered as a PUSCH.

[0138] When TB processing is enabled on multiple time slots, the values ​​of L and A should be determined. The disclosed techniques can be used to implement the following methods.

[0139] Option 1: L is defined as the number of symbols in one of the multiple time slots used for TB processing, and TBS (i.e., A) is based on one of the multiple time slots used for TB processing.

[0140] Option 2: L is defined as the number of symbols in the multiple time slots used for TB processing, and TBS (i.e. A) is based on the multiple time slots used for TB processing.

[0141] Option 3: L is defined as the number of symbols in one of the multiple time slots used for TB processing, and TBS (i.e., A) is based on the multiple time slots used for TB processing.

[0142] Option 4: L is defined as the number of symbols in the multiple time slots used for TB processing, and TBS (i.e. A) is based on one of the multiple time slots used for TB processing.

[0143] Furthermore, if L is defined as the number of symbols in a time slot, and TBS (i.e., A) is based on an unlimited number of time slots, the data rate may exceed the maximum data rate. This should be avoided. On the other hand, TBS should not exceed the maximum size of the UE's buffer. The data rate should be considered as a limit to TBS.

[0144] Option 1: When L is defined as the number of symbols in multiple time slots used for TB processing, and TBS (i.e., A) is based on multiple time slots, the following formula should be satisfied:

[0145]

[0146] Where N is the number of time slots used for TB processing. TBS (i.e., A) will be limited by the data rate, and the maximum TBS should not exceed DataRateCC*L*T / N.

[0147] Option 2: When L is defined as the number of symbols in one of the multiple time slots used for TB processing, and TBS (i.e., A) is based on the multiple time slots used for TB processing, the following formula should be satisfied:

[0148]

[0149] Where N is the number of time slots used for TB processing. TBS (i.e., A) will be limited by the data rate, and the maximum TBS should not exceed DataRateCC*L*T. Furthermore, the above formula should also be satisfied when L is defined as the number of symbols in one of the multiple time slots used for TB processing, and TBS (i.e., A) is based on one of the multiple time slots used for TB processing.

[0150] If we want to use data rate to limit TBS, some embodiments define L as L' / N or N*floor(L' / N), where L' is the number of symbols allocated to the PUSCH in a time slot, and N is the number of time slots. In other words, data rate limiting is used to limit the actual TBS. Put another way, because L becomes smaller, the TBS must also become smaller so as not to increase the data rate that the UE can support.

[0151] For CA cases, the data rate limit is as follows. Within the cell group, the UE does not need to process PUSCH transmissions in time slot sj of serving cell j. For j = 0, 1, 2...J-1, if the following condition is not met at any given time point, then time slot sj overlaps with that time point:

[0152]

[0153] in

[0154] -J represents the number of configured serving cells within the frequency range.

[0155] -For the j-th serving cell

[0156] -M is the number of TBs transmitted in time slot sj.

[0157] -T slot μ(j) =10 -3 / 2 μ(j) , where μ(j) is the parameter set of PUSCH in the time slot sj of the j-th serving cell.

[0158] For the m-th TB,

[0159] -A is the number of bits in a transport block as defined in Clause 6.2.1 of [5, TS 38.212].

[0160] -C is the total number of code blocks in a transport block as defined in Clause 5.2.2 of [5, TS 38.212].

[0161] -C′ is the number of scheduling code blocks of the transport block as defined in Clause 5.4.2.1 of [5, TS 38.212]. The data rate [Mbps] is calculated as the sum of the maximum data rates of all carriers in the frequency range of any signaling band combination and feature set consistent with the configured serving cell, wherein the data rate value is given by the formula in Clause 4.1.2 of [13, TS 38.306], including the scaling factor f(i).

[0162] For the data rate limit per CC, the same approach is reused.

[0163] Option 1: T slot μ(j) It is defined as one of the multiple time slots used for TB processing, and TBS (i.e., A) is based on one of the multiple time slots used for TB processing. Wherein, μ(j) is the set of parameters of PUSCH in the time slot of the j-th serving cell.

[0164] Option 2: T slot μ(j) It is defined as the number of time slots used for TB processing, and TBS (i.e., A) is based on the number of time slots used for TB processing. Here, μ(j) is the set of parameters for PUSCH in the time slot of the j-th serving cell.

[0165] Option 3: T slot μ(j) It is defined as one of multiple time slots used for TB processing, and TBS (i.e., A) is based on multiple time slots used for TB processing. Wherein, μ(j) is the set of parameters of PUSCH in the time slot of the j-th serving cell.

[0166] Option 4: T slot μ(j) Defined as the number of symbols in multiple time slots used for TB processing, and TBS (i.e., A) is based on one time slot in the multiple time slots used for TB processing. Here, μ(j) is the set of parameters for PUSCH in the time slot of the j-th serving cell.

[0167] Data rate should be considered to limit TBS.

[0168] Method 1: When T slot μ(j When defined as multiple time slots, and TBS (i.e., A) is based on multiple time slots, the following formula should be satisfied:

[0169]

[0170] Where N is the number of time slots used for TB processing. TBS (i.e., A) will be limited by the data rate, and the maximum TBS should not exceed DataRateCC*L*T / N.

[0171] Method 2: When T slot μ(j) When defined as the number of symbols in one of the multiple time slots used for TB processing, TBS (i.e., A) is determined based on the multiple time slots used for TB processing.

[0172] In some embodiments, if A is based on a TBS across multiple time slots, A may exceed the maximum data rate. To avoid this, for TB processing across multiple time slots, T... slot μ(j) Changed to T slot μ(j) / N, where N is the number of time slots. In other words, the data rate limit is used to limit the actual TBS. Or, because T slot μ(j) As the size decreases, the TBS must also decrease to ensure that the data rate supported by the UE is not increased.

[0173] Exemplary Example 6

[0174] Figure 7 An example of a conflict between the Physical Uplink Control Channel (PUCCH) and the PUSCH is shown.

[0175] When TB processing is enabled on multiple time slots, the UE also transmits UCI information during one or more of the multiple time slots used for TB processing. The UCI information can be multiplexed on the PUSCH. The disclosed techniques can be used to implement the following methods.

[0176] Option 1: UCI is multiplexed on time slots overlapping with PUCCH, wherein the time slots used for UCI multiplexing include DMRS (Dedicated Demodulation Reference Signals) symbols.

[0177] Option 2: UCI is multiplexed on time slots that do not overlap with PUCCH. In some embodiments, the time slot is the time slot closest to the start or end symbol of the PUCCH in the time domain. For example, such as Figure 7 As shown, the TB processing of PUSCH occurs over four time slots, and PUCCH transmission conflicts with PUSCH transmission on time slot 4. UCI is multiplexed on time slot 3. Furthermore, the time slots include DMRS symbols. Additionally, the first symbol in the time slot used for UCI multiplexing must satisfy the timeline, which is defined in Section 9.2.5 of TS 38.213.

[0178] Option 3: UCI is multiplexed across multiple time slots for TB processing, which may or may not overlap with PUCCH. Furthermore, UCI is multiplexed from back to front across multiple time slots, wherein the last symbol in the multiple time slots used for UCI multiplexing must satisfy the timeline defined in Section 9.2.5 of TS 38.213. Additionally, the first time slot used for UCI multiplexing includes DMRS. (This last part is a repetition of the previous sentence and can be omitted.)

[0179] Furthermore, if PUCCH transmission is repeated, one or more of the multiple time slots used for TB processing overlap with PUCCH in the time domain, and the entire time slot used for TB processing is omitted. Additionally, the remaining time slots used for TB processing that do not overlap with PUCCH in the time domain can be transmitted.

[0180] For HARQ-ACK transmission on a PUSCH that does not use repeating type B with UL-SCH, the number of coded modulation symbols per layer used for HARQ-ACK transmission is denoted as Q′. ACK And determined in the following way:

[0181]

[0182] in:

[0183] -O ACK It is the number of HARQ-ACK bits;

[0184] -If O ACK ≥360, then L ACK =11; otherwise, L ACK It is the number of CRC bits used for HARQ-ACK as determined in Clause 6.3.1.2.1;

[0185] -

[0186] -C UL-SCH It is the number of UL-SCH code blocks transmitted by PUSCH;

[0187] - If the DCI format for scheduling PUSCH transmissions includes a CBGTI field indicating that the UE will not transmit the r-th code block, then K r =0; otherwise, K r It is the size of the r-th code block of the UL-SCH transmitted by PUSCH;

[0188] - It is the scheduling bandwidth for PUSCH transmission, expressed as the number of subcarriers;

[0189] - It is the number of subcarriers in OFDM symbol l carrying PTRS in PUSCH transmission;

[0190] - This refers to the number of resource elements available for UCI transmission in OFDM symbol 1 during PUSCH transmission, where... and It is the total number of OFDM symbols for PUSCH (including all OFDM symbols used for DMRS);

[0191] -For any OFDM symbol carrying PUSCH in DMRS

[0192] - For any OFDM symbol that does not carry PUSCH in DMRS

[0193] -α is configured via high-level parameter scaling;

[0194] -l0 is the symbol index of the first OFDM symbol that does not carry PUSCH after the first DMRS symbol in the PUSCH transmission.

[0195] When enabling TB processing on multiple time slots, the number of coded modulation symbols used for each layer of UCI information should be determined. The disclosed techniques can be used to implement the following methods.

[0196] Option 1: When When multiple time slots for TB processing are determined Based on the determination of multiple time slots for TB processing, then A single time slot was determined from among multiple time slots used for TB processing. Furthermore, Multiple time slots for TB processing were determined.

[0197] Option 2: When When a single time slot is determined from among multiple time slots used for TB processing, then A single time slot is determined based on multiple time slots used for TB processing. A single time slot was determined from among multiple time slots used for TB processing. Furthermore, Multiple time slots for TB processing were determined.

[0198] Option 3: When When multiple time slots for TB processing are determined Based on the determination of a single time slot among multiple time slots used for TB processing, then A single time slot was determined from among multiple time slots used for TB processing. Furthermore, Multiple time slots for TB processing were determined.

[0199] Option 4: When When a single time slot is determined from among multiple time slots used for TB processing Based on the determination of multiple time slots for TB processing A single time slot was determined from among multiple time slots used for TB processing. Furthermore, Multiple time slots for TB processing were determined.

[0200] Exemplary Example 7

[0201] Figure 8 The different inter-slot frequency hopping (FH) modes in the time domain for a PUSCH with 8 repetitions in TDD and an inter-slot FH beam size of 2 are shown, where (A) represents mode 1 with the inter-slot FH beam based on consecutive time slots, (B) represents mode 2 with the inter-slot FH beam based on available time slots, and (C) represents mode 3 with the inter-slot FH beam based on each group of consecutive available time slots.

[0202] For TDD operation, joint channel estimation can be performed only between PUSCH transmissions in consecutive UL time slots. The inter-slot FH mode may differ depending on the TDD configuration and the definition of an FH bundle. For example, as... Figure 8 As shown, three inter-slot FH modes are given based on a beam size of 2, and FH occurs between FH beams.

[0203] For Mode 1, the inter-slot FH bundle is based on consecutive time slots. That is, a bundle contains consecutive time slots, where consecutive time slots can be DL time slots or UL time slots. For Mode 2, the inter-slot FH bundle is based on available time slots. That is, a bundle can only include time slots used for actual PUSCH transmission. For Mode 3, the inter-slot FH bundle is based on each set of consecutive available time slots. That is, the bundle is re-divided within each set of consecutive UL time slots. Although the three modes above may seem similar because they all have three hops, joint channel estimation can only be performed in one hop. However, differences may exist if different TDD configurations or different bundle sizes are assumed. For example, if the bundle size is 4, Mode 3 can enable joint channel estimation in a single hop with three UL time slots. In some implementations, cross-slot channel estimation is performed on available consecutive resources within the bundle. In some implementations, the above methods are also used for PUCCH transmission or Msg3 transmission.

[0204] Exemplary Example 8

[0205] For initial Msg3 transmissions, scheduling can be performed via RAR UL grant or fallback RAR UL grant. Time-domain resources, such as the start symbol, the number of symbols used, and the mapping type, are first configured or predefined in a TDRA (Time Domain Resource Allocation) table. This TDRA table has multiple rows, and each row contains a time-domain resource for PUSCH scheduling. Then, a bit field in the RAR UL grant or fallback RAR UL grant is used to indicate a row of time-domain resources to the UE.

[0206] If a repetition of the initial Msg3 transmission is introduced, the repetition factor can be included in a new TDRA table, for example, by adding a column for the repetition factor to the TDRA table. A bit field in the RAR UL grant or fallback RAR UL grant indicates to the UE that a row in the TDRA table also contains the repetition factor.

[0207] For a new TDRA table, it can be introduced into the Pusch Common Configuration (pusch-ConfigCommon), the Pusch Configuration (pusch-Config), or both. Then, depending on whether a new TDRA table or a traditional table is configured, the TDRA table selection for the initial Msg3 transmission should be determined.

[0208] PUSCH TDRA table selection via RAR UL authorization or rollback RAR UL authorization scheduling:

[0209] In some embodiments, the new TDRA table is named PUSCH TimeDomainResourceAllocationList-r17.

[0210] If the PUSCH time-domain resource allocation list r17 from the pusch public configuration is included, the TDRA table selection should be determined. Table 2.1-1 below shows an example.

[0211] Table 2.1-1: PUSCH time-domain resource allocation applicable to PUSCH scheduling with MAC RAR or MAC rollback RAR

[0212]

[0213] If the PUSCH time-domain resource allocation list r17 is additionally included in the pushch configuration, the TDRA table selection should be determined. Table 2.1-2 below shows an example. In some embodiments, the UE may use the TDRA table in the pushch configuration for PUSCH scheduled via MAC RAR or MAC fallback RAR. That is, the last row in parentheses in Table 2.1-2 is used. In some embodiments, the UE may not use the TDRA table in the pushch configuration for PUSCH scheduled via MAC RAR or MAC fallback RAR. That is, the last row in parentheses in Table 2.1-2 is not used.

[0214] Table 2.1-2: PUSCH time-domain resource allocation applicable to PUSCH scheduling with MAC RAR or MAC rollback RAR.

[0215]

[0216] TDRA table selection for Msg3 retransmission

[0217] For Msg3 retransmissions, scheduling is performed using DCI format 0_0 scrambled with TC-RNTI. Time-domain resources, such as the start symbol, the number of symbols used, and the mapping type, are first configured or predefined in a TDRA (Time Domain Resource Allocation) table. This TDRA table has multiple rows, and each row contains a single time-domain resource for PUSCH scheduling. Then, a single bit field in the DCI format 0_0 scrambled with TC-RNTI is used to indicate a row of time-domain resources to the UE.

[0218] If repetitions are introduced for Msg3 retransmission, the repetition factor can be included in a new TDRA table, for example, by adding a column for the repetition factor to the TDRA table. Then, the UE is informed via a bit field in the TC-RNTI scrambled DCI format 0_0 that a row in the TDRA table also contains the repetition factor.

[0219] For new TDRA tables, they can be imported into the Pusch common configuration (pusch-ConfigCommon), the Pusch configuration (pusch-Config), or both. Then, depending on whether a new TDRA table or a traditional table is configured, the TDRA table selection for Msg3 retransmission should be determined.

[0220] If the PUSCH time-domain resource allocation list r17 from the pusch public configuration is introduced, the TDRA table selection should be determined. Tables 2.2-1 and 2.2-2 show examples of Case 1 and Case 2, respectively.

[0221] Case 1: DCI format 0_0 scrambled with TC-RNTI and "any public search space related to CORESET 0".

[0222] Case 2: DCI format 0_0 scrambled with TC-RNTI and "DCI format 0_0 in any public search space not related to CORESET 0, and in the UE-specific search space".

[0223] Table 2.2-1 PUSCH time-domain resource allocation applicable to Case 1

[0224]

[0225] Table 2.2-2 PUSCH time-domain resource allocation applicable to Case 2

[0226]

[0227] If the PUSCH-TimeDomainResourceAllocationListForDCI-Format0-0-r17 is additionally introduced in the pusch configuration (pusch-Config), then the TDRA table selection should be determined. Tables 2.2-3 and 2.2-4 show examples of Case 1 and Case 2, respectively.

[0228] Table 2.2-3 PUSCH time-domain resource allocation applicable to Case 1

[0229]

[0230] Table 2.2-4 shows the PUSCH time-domain resource allocation applicable to Case 2.

[0231]

[0232] In some embodiments, the PUSCH time-domain resource allocation list r17 in the above-described pushch configuration is the same RRC parameter as the PUSCH time-domain resource allocation list r17 for DCI format 0-0 in the pushch configuration.

[0233] Default table

[0234] If a TDRA table is not configured via SIB1 or dedicated RRC signaling, the UE will use a default table for time-domain resource allocation. However, the current default table does not contain a repetition factor. To address this issue, the disclosed techniques can be used to implement the following methods.

[0235] Alternative Option 1: For CE UE, the PUSCH time domain resource allocation list r17 must be included in the pusch common configuration.

[0236] Alternative solution 2: Add a repeating factor to the default table.

[0237] The repetition factor is greater than 1 only for the PUSCH duration of X OS. For example, X = 14.

[0238] Only for PUSCH mapping type A, the repetition factor is greater than 1.

[0239] Alternative Option 3: If the PUSCH time-domain resource allocation list r17 is not included in the pusch common configuration, then use other methods to determine the repetition factor.

[0240] Option 1: Use some bits in the RAR UL license to indicate the repetition factor.

[0241] Option 2: Use the default predefined value. For example, the predefined value is 1 (i.e., it is assumed that there are no duplicates in this case).

[0242] Exemplary Example 9

[0243] If the Msg3 transmission supports repetition, then inter-slot FH is also supported. Some solutions for indicating inter-slot FH are given below. In some embodiments, inter-slot FH can also be interpreted as inter-repetition FH.

[0244] Option 0: Introduce RRC parameter frequency hopping in the SIB message. If the field does not exist, frequency hopping is not configured. The intraSlot value enables "intra-slot frequency hopping", and the interSlot value enables "inter-slot frequency hopping".

[0245] Frequency hopping enumeration (ENUMERATED) {intraSlot, interSlot}

[0246] If the frequency hopping field in the RAR UL authorization or DCI 0_0 format scrambled by TC-RNTI is set to 1, the UE can perform PUSCH frequency hopping; otherwise, it will not perform PUSCH frequency hopping.

[0247] Option 1: Reinterpret the 1-bit frequency hopping flag scrambled via TC-RNTI in RAR UL license or DCI 0_0 format.

[0248] If the frequency hopping flag is 0, the UE transmits a PUSCH with no intra-slot frequency hopping but with inter-slot frequency hopping; otherwise, the UE transmits a PUSCH with intra-slot frequency hopping but without inter-slot frequency hopping.

[0249] Alternatively, an RRC parameter indicating whether the UE supports FH can be introduced in SIB1. If the UE supports FH, the 1-bit frequency hopping flag in RAR UL authorization or DCI 0_0 format scrambled via TC-RNTI will be further interpreted as above. Otherwise, the 1-bit FH flag will be ignored, or the 1-bit FH flag will be reinterpreted for other meanings, such as whether cross-slot channel estimation is enabled.

[0250] Option 2: Introduce a 1-bit inter-slot FH flag in the RAR license or DCI 0_0 format scrambled via TC-RNTI. Combined with a 1-bit intra-slot frequency hopping, the following combinations are possible.

[0251] • "00": No FH, including both no FH within a time slot and no FH between time slots.

[0252] • "01": Enable intra-slot FH, disable inter-slot FH

[0253] • "10": Enable inter-slot FH, disable intra-slot FH

[0254] • "11": Reserved bit state. Can be used for additional indication.

[0255] The reserved bit state can be used for other indications, such as enabling cross-slot channel estimation.

[0256] Exemplary Example 10

[0257] If the Msg3 transmission supports repetition, the indication of RV mode, cross-slot channel estimation, or enabling of enhanced PUSCH repetition type A should also be determined.

[0258] In Rel-15 / 16, the UE will always use RV0 Msg3 for initial transmission: the UE uses redundant version number 0 to transmit the transport block in the PUSCH scheduled by RAR UL authorization in the corresponding RAR message.

[0259] If Msg3 is repeated, consider the following approach:

[0260] Option 1: Use a fixed RV loop pattern, such as [0, 2, 3, 1].

[0261]

[0262] Option 2: Use a few bits (e.g., 1 bit or 2 bits) from the RAR UL grant or fallback RAR UL grant to indicate the first repeating RV index of the initial Msg3 transmission.

[0263] Option 3: Use a few bits in DCI format 1_0 with CRC scrambled by RA-RNTI to indicate the RV index of the first repeat of the initial transmission of Msg3.

[0264] Option 4: Use some implicit method to indicate the RV mode of the initial Msg3 transmission. For example, use the MCS bit field or PRACH configuration to indicate the RV index of the first repeat in the initial Msg3 transmission.

[0265] Option 5: Use an SIB message to indicate the RV mode of the initial Msg3 transmission. For example, use SIB1 to indicate the RV index of the first repeating RV in the initial Msg3 transmission.

[0266] In some embodiments, two or more of the above options may be used to indicate the RV mode of Msg3 transmission.

[0267] A similar approach can be applied to signaling related to cross-timeslot channel estimation. Specifically, some predefined methods can be used to define the behavior for performing cross-timeslot channel estimation, or several bits (e.g., 1 or 2 bits) in the RAR UL grant or fallback RAR UL grant can be used to indicate the relevant signaling for cross-timeslot channel estimation for the initial transmission of Msg3, or several bits in the DCI format 0_0 with CRC scrambled by TC-RNTI can be used to indicate the relevant signaling for cross-timeslot channel estimation for Msg3 retransmission, or some implicit methods can be used to indicate the relevant signaling for cross-timeslot channel estimation for Msg3 transmission, or SIB messages can be used to indicate the relevant signaling for cross-timeslot channel estimation for Msg3 transmission, using two or more of the above methods to indicate the relevant signaling for cross-timeslot channel estimation for Msg3 transmission.

[0268] Similar approaches can be applied to signaling associated with Enhanced PUSCH Repeat Type A. Specifically, the behavior of Enhanced PUSCH Repeat Type A can be defined using predefined methods, such as using a few bits (e.g., 1 or 2 bits) in the RAR UL grant or fallback RAR UL grant to indicate the signaling associated with Enhanced PUSCH Repeat Type A for initial Msg3 transmissions, or using a few bits in the DCI format 0_0 with a CRC scrambled by TC-RNTI to indicate the signaling associated with Enhanced PUSCH Repeat Type A for Msg3 retransmissions, or using some implicit methods to indicate the signaling associated with Enhanced PUSCH Repeat Type A for Msg3 transmissions, or using SIB messages to indicate the signaling associated with Enhanced PUSCH Repeat Type A for Msg3 transmissions, using two or more of the above methods to indicate the signaling associated with Enhanced PUSCH Repeat Type A for Msg3 transmissions.

[0269] Exemplary Example 11

[0270] Figure 9 The diagram shows a comparison of setting a random access contention resolution timer (ra-ContentionResolutionTimer) for conventional Msg3 transport and setting a random access contention resolution timer for Msg3 repeats with a repetition factor of 2, when TDD is configured as "DDDSU". Figure 10 The diagram shows a comparison between setting a random access contention resolution timer for conventional Msg3 transport and setting a random access contention resolution timer for Msg3 repeat with a repetition factor of 4, when the TDD configuration is "DDDDDDDSUU".

[0271] In the traditional mode, the random access contention resolution timer starts immediately after the Msg3 transmission ends. If Msg3 repetition is introduced, the timer will naturally start after all Msg3 repetitions have ended. Some relevant specifications are as follows.

[0272]

[0273] However, the gNB might be able to successfully detect Msg3 based on the first repetition. If the timer can only start at the end of the repetition, it could increase latency, potentially making it greater than with traditional retransmission schemes. Furthermore, this would waste more UL resources on subsequent repetitions.

[0274] In some embodiments, the timer is restarted after each repetition ends. In some embodiments, this is only applied to TDD cases.

[0275] A comparison of traditional behavior and reinforced behavior, such as Figure 9 As shown in the diagram. For schemes (A) 1 and (B) 2, it is assumed that Msg3 repeats twice (2). In scheme 1, the timer starts after all Msg3 repeats have ended. In scheme 2, the timer can be restarted after each Msg3 repeat has ended. If a reception of the PDCCH transmission is received before the second repeat, and if the duration between the end of the PDCCH and the start of the second repeat is greater than a timeline, the UE will cancel or may cancel the second repeat.

[0276] In some embodiments, the timer restarts after the end point of some / a set of consecutive repetitions. In some embodiments, this is only applied to TDD scenarios. This prevents the UE from unnecessarily refreshing the timer every repetition.

[0277] Figure 10An example is shown. For Scheme 1 and Scheme 2, assume that Msg3 repeats 4 times. In Scheme 1, the timer starts after all Msg3 repeats have ended. In Scheme 2, the timer can be restarted after every two consecutive Msg3 repeats have ended. If a PDCCH transmission is received before the third repeat, and if the duration between the end of the PDCCH and the start of the third repeat is greater than a timeline, the UE will cancel or may cancel the third and fourth repeats.

[0278] As described above, the disclosed techniques can be implemented in some embodiments to differentiate different schemes based on whether the number of repetitions is determined based on available UL time slots. The disclosed techniques can also be implemented in some embodiments to perform transmit power determination for cross-timeslot channel estimation and TB processing for multiple time slots. The disclosed techniques can also be implemented in some embodiments to perform TBS determination, time slot number indication, and UCI multiplexing on the PUSCH for TB processing for multiple time slots. The disclosed techniques can also be implemented in some embodiments to perform TDRA table selection for the initial transmission of Msg3. The disclosed techniques can also be implemented in some embodiments to indicate inter-timeslot / intra-timeslot FH, RV modes, and cross-timeslot channel estimation for Msg3 transmission. The disclosed techniques can also be implemented in some embodiments to provide the starting point of the random access contention resolution timer for Msg3 repetitions.

[0279] Figure 11 An example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0280] In some embodiments of the disclosed technology, the wireless communication method 1100 includes: at 1110, a network node configuring multi-slot transmission by determining the number of repeated transmissions based on available time slots according to rules for performing repeated transmissions in consecutive time slots; and at 1120, transmitting messages according to repeated transmissions.

[0281] Figure 12 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0282] In some embodiments of the disclosed technology, the wireless communication method 1200 includes: at 1210, a network node configuring multi-slot transmission by determining the transmission power of the transmission or repeated transmission according to rules for performing repeated transmissions in consecutive time slots; and at 1220, performing the transmission or repeated transmission.

[0283] Figure 13 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0284] In some embodiments of the disclosed technology, the wireless communication method 1300 includes: at 1310, a user equipment determines the availability of a transmission or repeated transmission to perform a transmission in multiple time slots; at 1320, the user equipment determines the availability of transport block processing on the multiple time slots; at 1330, upon determining that a transmission or repeated transmission and transport block processing on the multiple time slots are available, performing a first determination of the number of transmissions or repeated transmissions and the number of multiple time slots; and at 1340, performing a transmission based on the first determination.

[0285] Figure 14 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0286] In some embodiments of the disclosed technology, the wireless communication method 1400 includes: at 1410, a user equipment determines the availability of transmission or retransmission to perform transmission in multiple time slots; at 1420, the user equipment determines the availability of transport block processing on the multiple time slots; at 1430, when it is determined that transmission or retransmission and transport block processing on the multiple time slots are available, a transport block size is calculated based on a single time slot or multiple time slots; and at 1440, transmission or retransmission is performed based on the transport block size.

[0287] Figure 15 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0288] In some embodiments of the disclosed technology, a wireless communication method 1500 includes: at 1510, a user equipment (UE) determining the availability of transmission or retransmission for transmitting a Physical Uplink Shared Channel (PUSCH) in multiple uplink time slots; at 1520, the UE determining the availability of transport block processing on the multiple uplink time slots; at 1530, upon determining that transmission or retransmission and transport block processing on the multiple uplink time slots are available, multiplexing uplink control information (UCI) on the multiple uplink time slots associated with transport block processing; and at 1540, transmitting the uplink control information (UCI) and PUSCH to a network node.

[0289] Figure 16 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0290] In some embodiments of the disclosed technology, the wireless communication method 1600 includes: at 1610, a user equipment determining the availability of repeated transmissions for transmitting Msg3 to a network node; at 1620, configuring a first TDRA table that is different from an existing Time Domain Resource Allocation (TDRA) table; at 1630, determining that the first TDRA table includes a repetition factor, and performing repeated transmissions using the first TDRA table for time domain resource allocation; and at 1640, if it is determined that no TDRA table is configured, using a default table for time domain resource allocation.

[0291] Figure 17 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0292] In some embodiments of the disclosed technology, the wireless communication method 1700 includes: at 1710, determining the availability of repetitive transmissions for Msg3 transmission; at 1720, determining the availability of frequency hopping; and at 1730, when it is determined that repetitive transmissions and frequency hopping for Msg3 transmission are available, executing an instruction to perform frequency hopping between time slots.

[0293] Figure 18 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0294] In some embodiments of the disclosed technology, the wireless communication method 1800 includes: at 1810, determining the availability of Msg3 repeat transmission; and at 1820, when it is determined that Msg3 repeat transmission is available, performing an instruction to enable Redundancy Version (RV) mode, cross-slot channel estimation, and Enhanced PUSCH Repeat Type A.

[0295] Figure 19 Another example of a wireless communication method based on some embodiments of the disclosed technology is shown.

[0296] In some embodiments of the disclosed technology, the wireless communication method 1900 includes: at 1910, determining an inter-slot FH mode and an inter-slot FH bundle based on a time division duplex (TDD) configuration and the definition of a frequency hopping (FH) bundle; and at 1920, performing repeated transmissions using the inter-slot FH mode.

[0297] Figure 20An example of a wireless communication system (e.g., an LTE, 5G New Radio (NR) cellular network) including a radio access node 120 and one or more user equipment (UEs) 111, 112, and 113 is illustrated. In some embodiments, downlink transmissions (141, 142, 143) include control plane messages, wherein the control plane messages include processing commands for handling multiple user plane functions. The downlink transmissions follow uplink transmissions (131, 132, 133) that may be performed based on processing commands received by the UE. Similarly, user plane functions may be processed by the UE based on received processing commands for uplink transmissions. The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, terminal, mobile device, Internet of Things (IoT) device, etc.

[0298] Figure 21 This is a block diagram representation of a portion of a radio station based on one or more embodiments of the disclosed technology. Radio station 205 (e.g., a base station or wireless device (or UE)) may include processor electronics 210 (e.g., a microprocessor) that can implement one or more wireless technologies presented herein. Radio station 205 may include transceiver electronics 215 for transmitting and / or receiving wireless signals via one or more communication interfaces (e.g., antenna 220). Radio station 205 may include other communication interfaces for transmitting and receiving data. Radio station 205 may include one or more memories (not explicitly shown) configured to store information (e.g., data and / or instructions). In some embodiments, processor electronics 210 may include at least a portion of transceiver electronics 215. In some embodiments, at least a portion of the disclosed technologies, modules, or functions are implemented using radio station 205.

[0299] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product contained in a computer-readable medium, the computer program product including computer-executable instructions, such as program code, that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in such steps or processes.

[0300] Some embodiments of the disclosed examples may be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, implementations of hardware circuitry may include discrete analog and / or digital components, such as those integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include a digital signal processor (DSP), which is a special-purpose microprocessor with an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed herein. Similarly, various components or sub-components within each module may be implemented using software, hardware, or firmware. Connections between modules and / or between components within a module may be provided using any of the connection methods and media known in the art, including but not limited to communication via the Internet, wired networks, or wireless networks using appropriate protocols.

[0301] Some embodiments may preferably implement one or more of the following solutions listed in the terms format. The following terms are supported and further described in the foregoing examples and throughout the document. As used in the following terms and claims, a wireless terminal may be a user equipment, a mobile station, or any other wireless terminal including a fixed node, such as a base station. A network node includes a base station, wherein a base station includes a next-generation node B (gNB), an enhanced node B (eNB), or any other device acting as a base station. A resource range may refer to a range of time-frequency resources or blocks.

[0302] Clause 1. A method for wireless communication, comprising: a network node configuring multi-slot transmission by determining the number of repeated transmissions based on available time slots according to rules for performing repeated transmissions in consecutive time slots; and transmitting messages based on repeated transmissions.

[0303] Clause 2, the method according to Clause 1, further comprises: the user equipment receiving a radio resource control (RRC) signal from the network node, wherein the RRC signal includes an indication indicating the number of repeated transmissions is determined based on available time slots.

[0304] Clause 3. The method according to Clause 1 further includes: the user equipment receiving a downlink control information (DCI) or media access control element (MAC-CE) message from the network node, wherein the DCI or the MAC-CE message includes at least one bit to indicate the number of repeated transmissions determined based on available time slots.

[0305] Clause 4. The method described in Clause 1, wherein the rule is determined based on: determining whether initial access channel transmission enhancement is enabled, or determining whether Msg3 transmission is associated with more than one repetition.

[0306] Clause 5, the method described in Clause 1 further comprises: applying a Redundancy Version (RV) index to the repeated transmission based on the actual repeated transmission that does not conflict with the Slot Format Indicator (SFI) or another transmission.

[0307] Clause 6. The method according to Clause 1 further includes: applying a Redundancy Version (RV) index to the repeated transmission based on the total number of repeated transmissions including those that conflict with a Slot Format Indicator (SFI) or another transmission.

[0308] Clause 7. A method for wireless communication, comprising: a network node configuring multi-slot transmission by determining transmission power for a transmission or repeated transmission according to rules for performing repeated transmissions in consecutive time slots; and performing the transmission or repeated transmission.

[0309] Clause 8. The method according to Clause 7, wherein the transmission power of the transmission or repeated transmission is determined based on a single transmission opportunity or time slot among a plurality of time slots or transmission opportunities for joint channel estimation, wherein the single transmission opportunity or time slot has a maximum or minimum number of available resource elements.

[0310] Clause 9. The method according to Clause 7, wherein, where the Transport Block Size (TBS) is determined based on a single transport opportunity or time slot, the transport power of the transport or retransmission is determined based on a single transport opportunity or time slot.

[0311] Clause 10, the method according to Clause 7, wherein the transmission power of the transmission or repeated transmission is determined based on multiple transmission opportunities or time slots.

[0312] Clause 11. The method according to Clause 7, wherein, where the transport block size (TBS) is determined based on multiple transport opportunities or time slots, the transport power of the transport or retransmission is determined based on multiple transport opportunities or time slots.

[0313] Clause 12. A method for wireless communication, comprising: a user equipment determining the availability of a transmission or repeated transmission to perform the transmission in a plurality of time slots; the user equipment determining the availability of transport block processing on the plurality of time slots; upon determining that the transmission or repeated transmission and transport block processing on the plurality of time slots are available, performing a first determination of the number of transmissions or repeated transmissions and the number of the plurality of time slots; and performing the transmission based on the first determination.

[0314] Clause 13. The method according to Clause 12 further comprises: the user equipment receiving from the network node at least one of a Radio Resource Control (RRC) signal, a Downlink Control Information (DCI) message, or a Media Access Control Element (MAC-CE) message indicating the number of the plurality of time slots.

[0315] Clause 14. The method according to Clause 12 further includes performing joint coding on the number of the plurality of time slots used for transport block processing and the Time Domain Resource Allocation (TDRA) table.

[0316] Clause 15. The method according to Clause 12 further includes: determining a Redundancy Version (RV) pattern to be applied to the repeated transmission, such that an RV index is assigned to each repeated transmission.

[0317] Clause 16. The method according to Clause 15, wherein the repeated transmissions are arranged sequentially according to a redundancy version (RV) pattern on multiple repetitions, such that an RV index is assigned to each repeated transmission.

[0318] Clause 17. The method according to Clause 15, wherein the repeated transmission includes a repeated pattern distributed across multiple discontinuous time slots.

[0319] Clause 18, the method according to Clause 12, wherein the size of the FDRA field in the DCI is related to the number of time slots associated with the TB process.

[0320] Clause 19. The method described in Clause 12, wherein repeated transmission includes single-slot physical uplink shared channel (PUSCH) repetition.

[0321] Clause 20, the method according to Clause 12, wherein the transmission or retransmission includes multiple time slots for processing the transmission block.

[0322] Clause 21. The method according to Clause 20 further includes: determining that the transmission or retransmission conflicts with a slot format indicator (SFI) or another transmission; and performing an uplink transmission by omitting at least a portion of the retransmission.

[0323] Clause 22. A method for wireless communication, comprising: a user equipment determining the availability of a transmission or repeated transmission to perform the transmission in a plurality of time slots; the user equipment determining the availability of transport block processing on the plurality of time slots; calculating a transport block size based on a single time slot or the plurality of time slots when the transmission or repeated transmission and the transport block processing on the plurality of time slots are determined to be available; and performing the transmission or repeated transmission based on the transport block size.

[0324] Clause 23, the method according to Clause 22, wherein the transport block size is calculated based on a single time slot associated with the plurality of time slots used for transport block processing.

[0325] Clause 24. The method according to Clause 22, wherein the transport block size is calculated based on the plurality of time slots used for transport block processing.

[0326] Clause 25. The method according to Clause 24, wherein the transport block size is not greater than a threshold.

[0327] Clause 26. The method according to Clause 24, wherein the transport block size is limited by the data rate.

[0328] Clause 27. The method according to Clause 22 further includes: determining the number of symbols allocated to the transmission or repeated transmission and the number of bits in the transmission block.

[0329] Clause 28. The method according to Clause 27, wherein the number of symbols allocated to the transmission or repeated transmission is determined based on the number of symbols in one of the multiple time slots used for the transmission block processing, and the number of bits in the transmission block is determined based on one of the multiple time slots used for the transmission block processing.

[0330] Clause 29. The method according to Clause 27, wherein the number of symbols allocated to the transmission or repeated transmission is determined based on the number of symbols in a plurality of time slots used for the transmission block processing, and the number of bits in the transmission block is determined based on the plurality of time slots used for the transmission block processing.

[0331] Clause 30, the method according to Clause 27, wherein the number of symbols allocated to the transmission or repeated transmission is determined based on the number of symbols in one of a plurality of time slots used for the processing of the transport block, and the number of bits in the transport block is determined based on the plurality of time slots used for the processing of the transport block.

[0332] Clause 31. The method according to Clause 27, wherein the number of symbols allocated to the transmission or repeated transmission is determined based on the number of symbols in a plurality of time slots used for the processing of the transmission block, and the number of bits in the transmission block is determined based on one of the plurality of time slots used for the processing of the transmission block.

[0333] Clause 32. A method for wireless communication, comprising: a user equipment determining the availability of a transmission or retransmission for transmitting a Physical Uplink Shared Channel (PUSCH) in a plurality of uplink time slots; the user equipment determining the availability of transport block processing on the plurality of uplink time slots; when the transmission or retransmission and the transport block processing on the plurality of uplink time slots are determined to be available, multiplexing uplink control information (UCI) on the plurality of uplink time slots associated with the transport block processing; and transmitting the uplink control information (UCI) and the PUSCH to a network node.

[0334] Clause 33. The method according to Clause 32, wherein the UCI is multiplexed on a time slot overlapping with the Physical Uplink Control Channel (PUCCH), wherein the time slot includes a Dedicated Demodulation Reference Signal (DMRS) symbol.

[0335] Clause 34. The method according to Clause 32, wherein the UCI is multiplexed on a time slot that does not overlap with the Physical Uplink Control Channel (PUCCH) and is closest in the time domain to the start or end symbol of the PUCCH.

[0336] Clause 35. The method according to Clause 32, wherein the UCI is multiplexed over multiple time slots for processing the transport block that overlap with or do not overlap with the PUSCH transport.

[0337] Clause 36. The method according to Clause 32, wherein the first time slot of the plurality of time slots includes a dedicated demodulation reference signal (DMRS) symbol.

[0338] Clause 37. The method according to any one of Clauses 32 to 36, wherein the first symbol used for uplink control information (UCI) multiplexing satisfies the corresponding timeline conditions.

[0339] Clause 38. A method for wireless communication, comprising: a user equipment determining the availability of repeated transmissions for transmitting Msg3 to a network node; configuring a first TDRA table different from an existing Time Domain Resource Allocation (TDRA) table; determining that the first TDRA table includes a repetition factor; performing the repeated transmissions using the first TDRA table for time domain resource allocation; and, when it is determined that no TDRA table is configured, using a default table for time domain resource allocation.

[0340] Clause 39. The method according to Clause 38 further includes: adding a column for the repeatability factor in the first TDRA table.

[0341] Clause 40, the method according to Clause 39, wherein the bit field in the downlink control information (DCI) for the user equipment scrambled by the Temporary Cell Radio Network Temporary Identifier (TC-RNTI) indicates a row in the first TDRA table including the repetition factor.

[0342] Clause 41. The method according to Clause 38, wherein the first TDRA table is configured in the pusch common configuration (pusch-ConfigCommon), or in the pusch configuration (pusch-Config), or in both the pusch common configuration and the pusch configuration.

[0343] Clause 42. The method described in Clause 41 further includes: if the first TDRA table has been configured, performing a selection of the TDRA table for Msg3 retransmission or initial transmission.

[0344] Clause 43. The method described in Clause 38 further includes: when the first TDRA table is configured, performing the selection of the TDRA table for the initial transmission of Msg3 by random access response (RAR) uplink (UL) grant or fallback RAR UL grant.

[0345] Clause 44. The method described in Clause 38 further includes, in the absence of the TDRA table, indicating the repetition factor by including the PUSCH-TimeDomainResourceAllocationList-r17 in the pusch ConfigCommon.

[0346] Clause 45. The method according to Clause 38 further includes: indicating the repeating factor by adding the repeating factor to the default table when the TDRA table is not configured.

[0347] Clause 46. The method according to Clause 38 further includes: indicating the repetition factor by using one or more bits in the Random Access Response (RAR) uplink (UL) grant when the TDRA table is not configured.

[0348] Clause 47. A method for wireless communication, comprising: determining the availability of a repetitive transmission for Msg3 transmission; determining the availability of frequency hopping; and, upon determining that the repetitive transmission for Msg3 transmission and the frequency hopping are available, executing an instruction to perform frequency hopping between time slots.

[0349] Clause 48, the method according to Clause 47, wherein the indication includes RRC parameters associated with frequency hopping in the SIB message.

[0350] Clause 49. The method according to Clause 47, wherein the indication includes a one-bit frequency hopping flag in a RAR license or DCI format scrambled by TC-RNTI.

[0351] Clause 50. A method for wireless communication, comprising: determining the availability of Msg3 repetition transmission; and, upon determining that the Msg3 repetition transmission is available, performing an instruction to enable Redundancy Version (RV) mode, cross-slot channel estimation, and Enhanced PUSCH Repetition Type A.

[0352] Clause 51, the method according to Clause 50, wherein the indication of the RV mode includes a fixed RV cycle mode.

[0353] Clause 52, the method according to Clause 50 further comprises: performing an indication of a first repeating RV index for the initial transmission of Msg3 by using one or more bits of the RAR UL grant or rollback RAR UL grant, or by using one or more bits of a DCI format having a cyclic redundancy check (CRC) scrambled with a random access radio network temporary identifier (RA-RNTI).

[0354] Clause 53. The method according to Clause 50, wherein the cross-slot channel estimation is indicated by using one or more bits in the RAR UL grant or fallback RAR UL grant to indicate the cross-slot channel estimation for the initial transmission of Msg3.

[0355] Clause 54. The method according to Clause 50, wherein the enablement of the enhanced PUSCH repetition type A is indicated by using one or more bits in the RAR UL grant or fallback RAR UL grant to indicate signaling for the initial transmission of Msg3.

[0356] Clause 55, the method described in Clause 50 further includes: starting a timer after all repetitions of Msg3 have been completed.

[0357] Clause 56. The method described in Clause 50 further includes: restarting the timer after each repetition of Msg3 has completed.

[0358] Clause 57. The method described in Clause 50 further includes: restarting the timer after a set of consecutive repetitions has been completed.

[0359] Clause 58. The method according to any one of Clauses 55 to 57, wherein the timer includes a random access contention resolution timer.

[0360] Clause 59. A method for wireless communication, comprising: determining an inter-slot frequency hopping (FH) mode and an inter-slot FH bundle based on a time division duplex (TDD) configuration and a definition of a frequency hopping (FH) bundle; and performing repeated transmissions using the inter-slot FH mode.

[0361] Clause 60, the method according to Clause 59, wherein the inter-slot FH bundle is based on consecutive time slots.

[0362] Clause 61, the method according to Clause 59, wherein the inter-slot FH bundle is based on available time slots.

[0363] Clause 62, the method according to Clause 59, wherein the inter-slot FH bundle is based on each set of consecutively available time slots.

[0364] Clause 63. An apparatus for wireless communication, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method as described in any one of Clauses 1 to 62.

[0365] Clause 64. A computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method as described in any one of Clauses 1 to 62.

[0366] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product contained in a computer-readable medium, the computer program product including computer-executable instructions, such as program code, that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in such steps or processes.

[0367] Some embodiments of the disclosed examples may be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, implementations of the hardware circuitry may include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include a digital signal processor (DSP), which is a special-purpose microprocessor having an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed herein. Similarly, various components or sub-components within each module may be implemented using software, hardware, or firmware. Connections between modules and / or between components within a module may be provided using any of the connection methods and media known in the art, including but not limited to communication via the Internet, wired networks, or wireless networks using appropriate protocols.

[0368] Although this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or any potentially claimed content, but rather as descriptions of specific features characteristic of particular embodiments. Specific features described in the context of individual embodiments in this document may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as functioning in a particular combination, or even initially claimed in this manner, in some cases one or more features from the claimed combination may be removed from that combination, and the claimed combination may refer to a sub-combination or a variation thereof. Similarly, although operations are described in a specific order in the drawings, this should not be construed as requiring the operations to be performed in the specific order shown or in a sequential order, or requiring all shown operations to obtain the desired result.

[0369] Only a few implementations and examples have been described, and other implementations, enhancements and variations can be derived based on what is described and shown in this disclosure.

Claims

1. A method for wireless communication, comprising: User equipment determines the availability of transmission or repeated transmission to perform transmission in multiple time slots; The user equipment determines the availability of transport block processing on the plurality of time slots; When it is determined that the transmission or retransmission and the transport block processing on the plurality of time slots are available, a first determination is performed on the number of transmissions or retransmissions and the number of the plurality of time slots; and when it is determined that transport block processing on the plurality of time slots is available, the transport block size is calculated based on a single time slot or the plurality of time slots, wherein the number of available resource elements is the total number of resource elements in the plurality of time slots excluding the reference signal used for the transport block processing; and, The transmission or repeated transmission is performed based on the first determination or the transmission block size.

2. The method according to claim 1, further comprising: The user equipment receives from the network node at least one of a Radio Resource Control (RRC) signal indicating the number of the plurality of time slots, a Downlink Control Information (DCI) message, or a Media Access Control (MAC-CE) message; or Joint coding is performed on the number of the plurality of time slots used for the transport block processing and the Time Domain Resource Allocation (TDRA) table; or The redundant version RV mode to be applied to the repeated transmission is determined, such that an RV index is assigned to each repeated transmission.

3. The method according to claim 1, wherein, The size of the Frequency Domain Resource Allocation (FDRA) field in DCI is related to the number of time slots associated with the transport block processing.

4. The method according to claim 1, wherein, The repeated transmission includes single-slot physical uplink shared channel (PUSCH) repetition, or the transmission or repeated transmission includes multiple time slots for the processing of the transport block.

5. The method according to claim 1, wherein, When calculating the transport block size based on the plurality of time slots, the transport block size is calculated based on a single time slot associated with the plurality of time slots used for transport block processing or the plurality of time slots used for transport block processing.

6. The method according to claim 5, further comprising: Determine the number of symbols allocated to the transmission or repeated transmission and the number of bits in the transmission block.

7. An apparatus for wireless communication, comprising a memory and a processor, wherein, The processor reads code from the memory and implements the method according to any one of claims 1 to 6.

Images