Method and apparatus for processing PUSCH repeated transmission in a wireless communication system

Abstract

A method performed by a user equipment (UE) is provided. The method includes: receiving a radio resource control (RRC) configuration including a first parameter configured with a first value and a second parameter configured with at least one second value. Each of the first value and the at least one second value indicates a number of PUSCH repetitions. The method also includes: receiving downlink control information (DCI) on a physical downlink control channel (PDCCH) that schedules a physical uplink shared channel (PUSCH) transmission; selecting one of the first parameter and the second parameter according to the DCI to determine a number of PUSCH repetitions for the PUSCH transmission; when the first parameter is selected, determining the number of PUSCH repetitions for the PUSCH transmission to be the first value; when the second parameter is selected, determining the number of PUSCH repetitions for the PUSCH transmission to be one of the at least one second value indicated by the DCI; and performing the PUSCH transmission a certain number of times based on the number of PUSCH repetitions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims the benefit of and priority to provisional U.S. patent application serial number 62 / 875,335, entitled “Operation among Enhanced Repetition of PUSCH Transmission,” filed on July 17, 2019 (“the '335 Provisional”). The contents of all of the above applications are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly, to methods and apparatus for handling repeated transmissions of a Physical Uplink (UL) Shared Channel (PUSCH) in a wireless communication system. Background Art

[0004] With the huge growth in the number of connected devices and the rapid increase in user / network traffic, various efforts have been made to improve different aspects of wireless communications in next-generation wireless communication systems (such as fifth-generation (5G) New Radio (NR)) by improving data rate, latency, reliability and mobility.

[0005] The 5G NR system is designed to provide flexibility and configurability to optimize network services and types to accommodate various use cases (such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC)).

[0006] However, as the demand for radio access continues to increase, there is a need to further improve wireless communications for next generation wireless communication systems. Summary of the Invention

[0007] The present disclosure relates to methods and apparatus for handling repetition of PUSCH transmissions in a wireless communication system.

[0008] According to one aspect of the present disclosure, a method for handling repeated transmissions in a wireless communication system, performed by a user equipment (UE), is provided. The method includes: the UE receiving a radio resource control (RRC) configuration including a first parameter configured with a first value and a second parameter configured with at least one second value. Each of the first value and the at least one second value indicates a physical uplink shared channel (PUSCH) repetition number. The method also includes: the UE receiving downlink control information (DCI) on a physical downlink control channel (PDCCH) that schedules PUSCH transmission; selecting one of the first parameter and the second parameter according to the DCI to determine a PUSCH repetition number for the PUSCH transmission; when the first parameter is selected, applying the first value as the PUSCH repetition number for the PUSCH transmission; when the second parameter is selected, determining the PUSCH repetition number for the PUSCH transmission to be one of the at least one second value indicated by the DCI; and performing the PUSCH transmission a certain number of times. The number is determined by the number of PUSCH repetitions used for the PUSCH transmission.

[0009] According to another aspect of the present disclosure, a method for handling repeated transmissions in a wireless communication system is provided. The UE includes: one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and at least one processor coupled to the one or more non-transitory computer-readable media. The at least one processor is configured to execute the computer-executable instructions to receive an RRC configuration including a first parameter configured with a first value and a second parameter configured with at least one second value. Each of the first value and the at least one second value indicates a number of PUSCH repetitions. The at least one processor is further configured to execute the computer-executable instructions to receive a DCI on a PDCCH scheduling a PUSCH transmission; select one of the first parameter and the second parameter based on the DCI to determine a number of PUSCH repetitions for the PUSCH transmission; when the first parameter is selected, apply the first value as the number of PUSCH repetitions for the PUSCH transmission; when the second parameter is selected, determine the number of PUSCH repetitions for the PUSCH transmission to be one of the at least one second value indicated by the DCI; and perform the PUSCH transmission a certain number of times. The number is determined by the number of PUSCH repetitions used for the PUSCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The aspects of the present disclosure are best understood when the following detailed description is read in conjunction with the accompanying drawings. Various features are not drawn to scale. The dimensions of various features may be arbitrarily increased or decreased for clarity of discussion.

[0011] Figure 1 FIG. 1 is a diagram illustrating PUSCH transmission scheduled by a PDCCH according to an embodiment of the present disclosure.

[0012] Figure 2 FIG. 1 is a diagram illustrating PUSCH transmission scheduled by a PDCCH according to an embodiment of the present disclosure.

[0013] Figure 3 is a diagram illustrating repetition of PUSCH transmission across downlink (DL) symbols or slot boundaries when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure.

[0014] Figure 4 is a diagram illustrating repetition of PUSCH transmission across DL symbols when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure.

[0015] Figure 5is a diagram illustrating PUSCH transmission corresponding to a UL grant having a value of S+L greater than the number of symbols per slot according to an embodiment of the present disclosure.

[0016] Figure 6 is a diagram illustrating repetition of PUSCH transmission across variable symbols when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure.

[0017] Figure 7 FIG. 1 is a diagram illustrating a user equipment (UE) switching between a dynamic indication mode and a non-dynamic indication mode according to an embodiment of the present disclosure.

[0018] Figure 8 A flowchart illustrating a procedure performed by a UE according to an embodiment of the present disclosure is shown.

[0019] Figure 9 A flowchart illustrating a procedure performed by a UE according to an embodiment of the present disclosure is shown.

[0020] Figure 10 A block diagram of a node for wireless communication is shown in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0021] The following description contains specific information related to exemplary embodiments of the present disclosure. The figures in this disclosure and the detailed description attached thereto relate only to exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Other variations and embodiments of the present disclosure will occur to those skilled in the art. Unless otherwise indicated, similar or corresponding elements in the accompanying drawings may be indicated by similar or corresponding reference numerals. In addition, the figures and illustrations in this disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0022] The following description contains specific information related to exemplary embodiments of the present disclosure. The figures in this disclosure and the accompanying detailed description are directed only to exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Those skilled in the art will recognize other variations and embodiments of the present disclosure. Unless otherwise indicated, similar or corresponding elements in the accompanying drawings may be indicated by similar or corresponding reference numerals. In addition, the figures and illustrations in this disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0023] For the purpose of consistency and ease of understanding, similar features are identified by numbers in the exemplary drawings (although not shown in some examples). However, features in different embodiments may differ in other aspects and should not be narrowly limited to what is shown in the drawings.

[0024] References to "one embodiment," "an embodiment," "an exemplary embodiment," "various embodiments," "some embodiments," "embodiments of the present disclosure," and the like may indicate that the embodiments of the present disclosure so described may include particular features, structures, or characteristics, but not every possible embodiment of the present disclosure necessarily includes the particular features, structures, or characteristics. Furthermore, repeated use of the phrases "in one embodiment," "in an exemplary embodiment," or "one embodiment" does not necessarily refer to the same embodiment, although it may. Furthermore, any use of a phrase like "an embodiment" in conjunction with "the present disclosure" does not in any way imply that all embodiments characterizing the present disclosure must include the particular features, structures, or characteristics, but rather should be understood to mean that "at least some embodiments of the present disclosure" include the recited particular features, structures, or characteristics. The term "coupled" is defined as connected, whether directly or indirectly through intermediate components, and is not necessarily limited to physical connections. The term "comprising," when utilized, means "including, but not necessarily limited to," and it specifically indicates an open-ended inclusion or subordination among the combinations, groups, series, and equivalents so described.

[0025] The term "and / or" herein is used only to describe the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists. In addition, the character " / " used herein generally indicates that the former and the latter associated objects are in an "or" relationship.

[0026] In addition, for the purpose of non-limiting explanation, specific details (such as functional entities, techniques, protocols, standards, etc.) are set forth to provide an understanding of the described technology. In other instances, detailed descriptions of well-known methods, techniques, systems, architectures, etc. are omitted to avoid obscuring the description with unnecessary detail.

[0027] It will be readily apparent to those skilled in the art that any one or more network functions or algorithms described in this disclosure may be implemented by hardware, software, or a combination of software and hardware. The functions described may correspond to modules that may be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and implement the one or more network functions or algorithms described. The microprocessor or general-purpose computer may be formed by an application-specific integrated circuit (ASIC), a programmable logic array, and / or using one or more digital signal processors (DSP). Although some of the exemplary embodiments described in this specification are oriented toward software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware or hardware or a combination of hardware and software are fully within the scope of this disclosure.

[0028] Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic tape cassettes, magnetic tapes, disk storage devices, or any other equivalent medium that can store computer-readable instructions.

[0029] A radio communication network architecture (e.g., a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system) typically includes at least one base station (BS), at least one UE, and one or more optional network elements that provide a connection to the network. The UE communicates with a network (e.g., a core network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Next-Generation Core (NGC), or the Internet) through a radio access network (RAN) established by the BS.

[0030] It should be noted that in this disclosure, a UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. For example, a UE may be a portable radio device, including, but not limited to, a mobile phone, a tablet, a wearable device, a sensor, or a personal digital assistant (PDA) with wireless communication capabilities. A UE is configured to receive signals from and transmit signals to one or more cells in a RAN over an air interface.

[0031] The BS may include, but is not limited to, a Node B (NB) in the Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) in LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in the Global System for Mobile communication (GSM) / GSM Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN), an ng-eNB in ​​an E-UTRA BS connected to a 5GC, a next generation Node B (gNB) in a 5G Access Network (5G-AN), and any other device capable of controlling radio communications and managing radio resources within a cell. The BS may be connected to the network via a radio interface to serve one or more UEs.

[0032] The BS may be configured to provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS based on basic wideband code division multiple access (W-CDMA) (commonly referred to as 3G), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, eLTE, NR (commonly referred to as 5G), and LTE-A Pro. However, the scope of the present disclosure should not be limited to the above-mentioned protocols.

[0033] The BS may be capable of operating to provide radio coverage to a specific geographical area using multiple cells included in the RAN. The BS may support the operation of cells. Each cell may be operable to provide services to at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage (for example, each cell schedules DL and optional uplink (UL) resources to at least one UE within its radio coverage for DL ​​and optional UL packet transmission). The BS may communicate with one or more UEs in the radio communication system through multiple cells. The cell may allocate sidelink (SL) resources for supporting proximity services (ProSe). Each cell may have a coverage area that overlaps with other cells. In the case of MR-DC, the primary cell of an MCG or SCG may be referred to as a special cell (SpCell). PCell may refer to the SpCell of an MCG. PSCell may refer to the SpCell of an SCG. MCG means a group of serving cells associated with an MN consisting of an SpCell and optionally one or more secondary cells (SCell). SCG means a group of serving cells associated with a SN, consisting of an SpCell and optionally one or more SCells.

[0034] As discussed above, the frame structure of NR is designed to support flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while meeting high reliability, high data rate, and low latency requirements. The orthogonal frequency-division multiplexing (OFDM) technology agreed upon in the 3rd Generation Partnership Project (3GPP) can be used as the baseline for the NR waveform. Scalable OFDM digital schemes such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used. In addition, two coding schemes are considered for NR: (1) low-density parity-check (LDPC) codes and (2) polar codes. The coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0035] Furthermore, it is considered that the transmission time interval of a single NR frame should include at least DL transmission data, a guard period, and UL transmission data, where the corresponding portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable, for example, based on the NR network dynamics. In addition, sidelink resources can be provided in the NR frame to support ProSe services.

[0036] In 3GPP Release 16 (Rel-16) NR wireless communication systems, a UE can be configured to periodically, discontinuously, or continuously monitor the PDCCH in the time domain and identify possible dynamic UL grants (scheduling) scheduled by the gNB via the PDCCH. For example, the UL grant may be received on a (UE-specific) Directed Call Information (DCI) with cyclic redundancy check (CRC) bits scrambled by a UE-specific Radio Network Temporary Identifier (RNTI) (e.g., Cell-RNTI (C-RNTI)). The DCI may be located by the UE via blind decoding on the PDCCH. The DCI may indicate the UL grant for the Physical Uplink Shared Channel (PUSCH). For example, the DCI may indicate the time and frequency location of the PUSCH. Once the UL grant is obtained, the UE may perform a corresponding UL data transmission (or "PUSCH transmission") on the PUSCH by utilizing the UL grant. For example, the PUSCH transmission may include transmitting a transport block (TB) at the UE. It should be noted that in some embodiments of the present disclosure, the term "PUSCH transmission / repetition" and the term "TB transmission / repetition" are interchangeable.

[0037] In some embodiments, one or more PUSCH transmissions may be dynamically scheduled by a BS (e.g., gNB) via a UL grant in a DCI, or by a Type 1 or Type 2 configuration grant.

[0038] Figure 1 FIG is a diagram showing PUSCH transmission scheduled by PDCCH according to an embodiment of the present disclosure. It should be noted that even in Figure 1 In the exemplary embodiment shown, each subframe (e.g., subframe n and subframe n+1) includes two time slots (e.g., time slot 0 and time slot 1). However, in other embodiments of the present disclosure, each subframe may include any number of time slots. For example, the number of time slots in each subframe may be determined based on a parameter set configuration. Additionally, each time slot may contain a fixed number of symbols.

[0039] like Figure 1As shown, three parameters, K2, S, and L, may be used to determine the time location and duration of a PUSCH 104 scheduled by a PDCCH 102. For example, parameter K2 may be used to determine the slot offset between a time slot (e.g., slot 0) containing a PDCCH (e.g., PDCCH 102) carrying DCI indicating a PUSCH resource assignment and a time slot (e.g., slot 1) containing PUSCH resources assigned by the DCI (e.g., PUSCH 104). Parameter S may be the index of the starting symbol of the scheduled PUSCH (e.g., PUSCH 104) in the time slot indicated by K2 (e.g., slot 1). Parameter L may be the number of consecutive symbols of the scheduled PUSCH (e.g., PUSCH 104) in the indicated time slot (e.g., slot 1).

[0040] In some embodiments, the values ​​of K2, S, and L for each dynamic grant from the BS may be derived by the UE based on the configuration of the parameter set for the bandwidth part (BWP) and / or an index contained in the DCI (e.g., time domain resource assignment).

[0041] Figure 2 FIG is a diagram showing a PUSCH scheduled by a PDCCH according to an embodiment of the present disclosure. Figure 2 As shown, there are two time slots in each subframe (e.g., time slot 0 and time slot 1), and each time slot contains 14 symbols (e.g., symbol 0 to symbol 13). Figure 2 In the exemplary embodiment shown, parameters K2, S, and L are configured as "1," "3," and "5," respectively. Therefore, the UL resources scheduled by the BS on the PUSCH may start at symbol 3 of slot 1 and end at symbol 7 of slot 1.

[0042] In an NR wireless communication system, a PUSCH repetition scheme may be used to improve the reliability of data transmission. The PUSCH repetition scheme may include the UE repeatedly performing PUSCH transmissions, wherein the number of times the UE performs PUSCH transmissions may be referred to as the PUSCH repetition number. It should be noted that in some embodiments of the present disclosure, the phrases "PUSCH repetition number," "nominal PUSCH repetition number," "repetition number," "nominal repetition number," "repetition number of PUSCH transmissions," "nominal repetition number of PUSCH transmissions," and "PUSCH transmission number" may be interchangeable.

[0043] In some embodiments, to meet the requirements of URLLC, a PUSCH repetition scheme may be implemented such that the UE repeatedly performs PUSCH transmissions in several consecutive time slots, where each repeated PUSCH transmission (or "PUSCH repetition") in each time slot may have the same symbol allocation (e.g., corresponding to the same values ​​of S and L). This type of PUSCH repetition scheme may be referred to as a slot-based repetition scheme.

[0044] In some embodiments, an improved PUSCH repetition scheme is provided. Compared to a slot-based repetition scheme, the improved PUSCH repetition scheme can shorten the time interval between each two adjacent PUSCH repetitions to reduce the total transmission time required for transmission delays interspersed between PUSCH repetitions. For example, the enhanced PUSCH repetition scheme can allow a UE to perform one or more repeated PUSCH transmissions (or "PUSCH repetitions") in a slot. In addition, the number of PUSCH repetitions can be expected to support dynamic changes for each dynamic scheduling. The improved PUSCH repetition scheme can be referred to as a non-slot-based repetition scheme.

[0045] In some embodiments, when a BS schedules a UE to perform PUSCH transmission, the BS may dynamically instruct the UE to perform PUSCH transmission using a slot-based repetition scheme or a non-slot-based repetition scheme.

[0046] In some embodiments, a non-slot-based repetition scheme may include the following operations (e.g., operations (a) to (f)). However, it should be noted that the listed operations are shown for illustrative purposes only and are not intended to limit the scope of the present disclosure. For example, in some embodiments of the present disclosure, a non-slot-based repetition scheme may not include one or more of the following operations.

[0047] Operations (a) to (f) may include:

[0048] (a) The BS (e.g., gNB) may indicate to the UE the time slot offset (K2) between the time slot containing the PDCCH scheduling the PUSCH transmission and the time slot containing the scheduled PUSCH transmission;

[0049] (b) The BS may indicate to the UE the starting symbol (S) of the PUSCH transmission;

[0050] (c) The BS may indicate the length (L) of the current PUSCH transmission to the UE, where the length of the PUSCH transmission may be represented by the number of symbols;

[0051] (d) The BS may indicate to the UE the (nominal) number of repetitions for the current PUSCH transmission (e.g., the number of times this PUSCH transmission should be repeated by the UE);

[0052] (e) the UE may perform repeated PUSCH transmission (or second PUSCH repetition) starting from a first upcoming UL symbol immediately after a current PUSCH transmission (or first PUSCH repetition) scheduled by the BS ends; and

[0053] (f) Each PUSCH repetition may start from the first upcoming UL symbol after the end of the previous PUSCH repetition.

[0054] In general, each PUSCH repetition may occupy L consecutive symbols. However, if the timing of L consecutive symbols corresponding to a PUSCH repetition (or PUSCH transmission) crosses a DL symbol or slot boundary, then from the perspective of the physical (PHY) layer, the PUSCH repetition may be divided into two or more actual PUSCH transmissions.

[0055] Figure 3 FIG is a diagram illustrating repetition of PUSCH transmission (or “PUSCH repetition”) across DL symbol or slot boundaries when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure. Figure 3 The non-slot-based repetition scheme shown is for illustrative purposes only and is not intended to limit the scope of the present disclosure.

[0056] like Figure 3 As shown, each of the time slots (e.g., time slot 0 and time slot 1) may include 14 symbols (e.g., symbol 0 to symbol 13). Each symbol designated by the letter "U" is a UL symbol, and each symbol designated by the letter "D" is a DL symbol. Figure 3 In the illustrated embodiment, the value of S, the value of L, and the number of PUSCH repetitions configured by the BS (e.g., gNB) are 3, 4, and 3, respectively.

[0057] It should be noted that the number of PUSCH repetitions configured / signaled by the BS (e.g., gNB) to the UE may be referred to as the nominal repetition number, which may be different from the actual number of PUSCH transmissions performed by the UE from the perspective of the PHY layer. Figure 3As shown, because the values ​​of S and L are 3 and 4 respectively, the UE may know that the UL resources scheduled by the BS on the PUSCH transmission 302 may span from symbol 3 to symbol 6 in time slot 0. In addition, in the embodiment, because the nominal number of repetitions is 3, the UE may need to repeat the PUSCH transmission 302 (the first (nominal) PUSCH repetition) twice more at the upcoming UL symbol. As described above, the value of L is 4, so each nominal repetition may include four UL symbols. However, because symbol 9 of time slot 0 is a DL symbol, the second (nominal) PUSCH repetition may be divided into two actual PUSCH transmissions (or "actual PUSCH repetitions"). As Figure 3 As shown, the actual PUSCH repetition 304 may span from symbol 7 to symbol 8 of time slot 0, and the actual PUSCH repetition 306 may span from symbol 10 to symbol 11 of time slot 0. These two actual PUSCH repetitions 304 and 306 may occupy a total of four symbols, so they may be equivalent to the second (nominal) PUSCH repetition. Similarly, because the third (nominal) PUSCH repetition covers the slot boundary between time slot 0 and time slot 1, the third (nominal) PUSCH repetition may be divided into two actual PUSCH repetitions 308 and 310, where the actual PUSCH repetition 308 may span from symbol 12 to symbol 13 of time slot 0, and the actual PUSCH repetition 310 may span from symbol 0 to symbol 1 of time slot 1. Therefore, in Figure 3 In the illustrated embodiment, the actual number of PUSCH repetitions (eg, five) may be greater than the nominal number of PUSCH repetitions (eg, three).

[0058] In some embodiments, the value of L may represent the total number of UL symbols allocated for PUSCH transmission. Therefore, the total number of UL symbols required for one PUSCH / TB repetition may be limited by the value of L.

[0059] Figure 4 FIG is a diagram illustrating repetition of PUSCH transmission across DL symbols when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure. Figure 4In the illustrated embodiment, the DCI may include a field / index indicating that, for a PUSCH transmission, S has a value of 3, L has a value of 4, and a nominal repetition number of 2. In this case, the UL resources scheduled by the BS (e.g., gNB) on the PUSCH may begin at symbol 3 of slot 0. Furthermore, because L is configured as 4 and symbol 5 of slot 0 is a DL symbol, the UE may need to split the initial PUSCH transmission into two actual PUSCH transmissions: a first actual PUSCH transmission 402 spanning from symbol 3 to symbol 4 of slot 0, and a second actual PUSCH transmission 404 spanning from symbol 6 to symbol 7 of slot 0. Therefore, the total occupancy of UL symbols for the initial PUSCH transmission (or "first nominal repetition") remains at 4.

[0060] In some embodiments, the UE may be configured with a repetition list, and the field / index included in the DCI may be a row / entry index of the repetition list (e.g., a Time Domain Resource Allocation (TDRA) index). In some embodiments, the repetition list may be included in a TDRA table. An example of a repetition list is shown in Table 1.

[0061] Table 1

[0062] Row Index <![CDATA[K2]]> S L R 0 1 3 4 2 1 1 4 6 3 2 2 2 4 4

[0063] As shown in Table 1, the repetition list may include several entries (or rows). Each entry in the repetition list may be indexed by a row index and include a set of parameters for configuring PUSCH transmission, such as parameters K2, S, L, and R, wherein each value of parameter R in the repetition list may represent a specific number of PUSCH repetitions, and the definitions of parameters K2, S, and L refer to Figure 1 and Figure 2 Described.

[0064] In some embodiments, the BS may indicate to the UE via specific signaling (e.g., DCI) which entry in the repetition list to use. The UE may determine the resource location and / or the number of PUSCH repetitions for the PUSCH transmission based on one or more values ​​in the indicated entries of the repetition list. For example, according to Table 1, if the BS sends a DCI including a row index of "0" to the UE, the UE may know that when performing PUSCH transmission scheduled by the DCI, the first entry / row in the repetition list should be applied. As shown in Table 1, the values ​​of K2, S, L, and R in the first entry / row in the repetition list are "1", "3", "4", and "2", respectively. In this case, the number of PUSCH repetitions used for the PUSCH transmission corresponding to the DCI is 2, as shown in Table 1. Figure 4 shown.

[0065] It should be noted that the embodiments in Table 1 are shown for illustrative purposes only and are not intended to limit the scope of the present disclosure. For example, the repeat list may include any combination of parameter R and / or other parameters / indexes. In another example, the repeat list may only include one or more values ​​of parameter R (or "one or more R values").

[0066] In some embodiments, a repetition list (e.g., including one or more R values) and a TDRA table may be separate tables, wherein each R value in the repetition list may be associated with a set of parameters (e.g., S, L, and / or K2) included in the TDRA table. For example, the repetition list may include several R values, such as "2," "3," and "4," wherein the R value "2" may be associated with a set of parameters K2, S, and L included in the first row / entry of the TDRA table (e.g., "1," "3," and "4," respectively), the R value "3" may be associated with a set of parameters K2, S, and L included in the second row / entry of the TDRA table (e.g., "1," "4," and "6," respectively), and the R value "4" may be associated with a set of parameters K2, S, and L included in the third row / entry of the TDRA table (e.g., "2," "2," and "4," respectively). In this case, the TDRA table may not include one or more R values. In addition, if the UE receives a DCI including a TDRA field indicating a row / entry of a TDRA table, the UE may apply a set of parameters included in the indicated row / entry of the TDRA table and an R value (in a repetition list) associated with the indicated row / entry of the TDRA table for the PUSCH repetition scheme. For example, when the PUSCH repetition scheme is applied for PUSCH transmission, if the TDRA field of the DCI indicates the first row / entry of the TDRA table, the UE may determine that the values ​​of K2, S, L, and R are "1," "3," "4," and "2," respectively.

[0067] Case A: Discontinuous Reception (DRX) operation with a non-slot-based repetition scheme

[0068] In some embodiments, the UE's Medium Access Control (MAC) entity may be configured by the gNB (e.g., via the RRC layer) to perform a DRX procedure that controls PDCCH monitoring activity for a specific Radio Network Temporary Identifier (RNTI) corresponding to the MAC entity. The specific RNTI may be a Cell-RNTI (C-RNTI), a Configured Scheduling-RNTI (CS-RNTI), an Interruption-RNTI (INT-RNTI), a Slot Format Indication-RNTI (SFI-RNTI), a Semi-Persistent-Channel State Information-RNTI (SP-CSI-RNTI), a Transmit Power-PUCCH-RNTI (TPC-PUCCH-RNTI), a TPC-PUSCH-RNTI, or a Transmit Power-Sounding Reference Signal-RNTI (TPC-SRS-RNTI). When the UE is in the RRC connected state (RRC connected state, RRC_CONNECTED), and if the UE is configured with DRX functionality, the MAC entity of the UE may monitor the PDCCH discontinuously in the time domain during the DRX procedure. For example, even if no data transmission occurs, the MAC entity may periodically monitor the control channel according to the configuration from the BS and the actual traffic pattern. In other words, even if no data transmission occurs, the UE may monitor the PDCCH within a preconfigured time period (e.g., active time). However, if data transmission occurs during the active time, the UE may remain in an active state to complete the data transmission. During the active time, the UE may monitor the PDCCH for one or more possible data transmission / reception indications. During the DRX procedure, the UE may handle the PDCCH monitoring operation by maintaining several timers in the MAC layer of the UE. The timer may include, for example, an on-duration timer, a DRX inactivity timer, a UL retransmission timer, a DL retransmission timer, a UL round trip time (RTT) timer, and a DL RTT timer.

[0069] In some embodiments, the lengths of the on-duration timer, DRX inactivity timer, UL retransmission timer, DL retransmission timer, UL RTT timer, and DL RTT timer may be preconfigured by the BS (e.g., gNB) via parameters drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerUL, and drx-HARQ-RTT-TimerDL, respectively.

[0070] In some embodiments, parameters such as drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerUL, and drx-HARQ-RTT-TimerDL may be configured by the BS via a UE-specific DL RRC message.

[0071] When a UE is within its active time and the monitored PDCCH indicates an UL transmission, it may start an UL RTT timer for the corresponding Hybrid Automatic Repeat Request (HARQ) process. The UL RTT timer may be maintained by the MAC entity on a per-UL HARQ process basis. The UL RTT timer may be used to calculate the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity. The length of the UL RTT timer may be related to the gNB processing time / capability. However, in current communication systems, the manner in which a UE (e.g., its MAC entity) handles the UL RTT timer for a non-slot-based repetition scheme for a corresponding PUSCH transmission remains undefined (e.g., the start timing of the UL RTT timer is undefined). Furthermore, because the corresponding MAC behavior remains undefined, the power savings gained by the DRX function may be lost due to improper synchronization between the gNB and the UE.

[0072] As described above, the BS may indicate the UL resources to the UE on the PUSCH via the DCI. For example, the DCI may include a TDRA field / index indicating the time position and duration of the PUSCH transmission (e.g., a row / entry index of a TDRA table, as shown in Table 1). In response to receiving the DCI, the UE may perform the corresponding PUSCH transmission by utilizing the UL resources. If the UE is configured to perform a PUSCH repetition scheme, the time domain of the UL resources indicated by the TDRA field (e.g., one or more indicated symbols and / or time slots) may be used as the UL resources for the first nominal repetition of the PUSCH transmission. In the following cases 1, 2, and 3, various RTT timer operations for DRX under the PUSCH repetition scheme are provided.

[0073] Case 1

[0074] In some embodiments, the value of S+L may be greater than the total number of symbols in a time slot. Assuming that each time slot contains 14 symbols, in order to meet the low latency requirements of the URLLC service, an UL grant with an S+L value greater than 14 may be applied.

[0075] Figure 5 is a diagram illustrating PUSCH transmission corresponding to a UL grant having a value of S+L greater than the number of symbols per slot (eg, 14 symbols) according to an embodiment of the present disclosure.

[0076] The UE may receive DCI from the gNB. The DCI may include a TDRA field indicating UL resources for PUSCH transmission. In some embodiments, the TDRA field may be a row index included in a TDRA table (e.g., as shown in Table 1). In some embodiments, the TDRA field may be a row / entry index indicating a row / entry included in the TDRA table, but the row / entry index may not be included in the TDRA table (e.g., in the case where the column of "row index" in Table 1 is removed). In this case, the TDRA table may include one or more parameters such as S, L, K2 and / or R, in addition to one or more row indexes. The UE may know which row / entry in the TDRA table the TDRA field of the DCI indicates according to the preconfigured mapping rule. For example, when the value of the TDRA field is "1", the UE may know that the parameters included in the first row / entry in the TDRA table (e.g., S, L, K2 and / or R) are selected; when the value of the TDRA field is "2", the UE may know that the parameters included in the second row / entry in the TDRA table (e.g., S, L, K2 and / or R) are selected, and so on. Figure 5 In the embodiment shown, the values ​​of S and L addressed by the TDRA field are 12 and 4 respectively. Figure 5As shown, the UL resources scheduled by the gNB on the PUSCH may span from symbol 12 of slot 0 to symbol 1 of slot 1, occupying four consecutive UL symbols. Note that the PUSCH transmission corresponding to the UL grant (or "first nominal repetition") spans the slot boundary between slot 0 and slot 1. Therefore, the first nominal repetition can be divided into two actual PUSCH transmissions 502 and 504. Furthermore, because the nominal repetition number is configured as 2 by the gNB via an indicator, the second nominal PUSCH transmission 506 under a non-slot-based repetition scheme may span from symbol 2 of slot 1 to symbol 5 of slot 1.

[0077] When the UE is configured with a DRX function (e.g., the UE is performing a DRX procedure), if the UE receives an UL grant, the MAC entity of the UE may start the UL RTT timer. As described above, the start timing of the UL RTT timer may be in the first symbol immediately after the end of the "first repetition" of the corresponding PUSCH transmission. From the perspective of the UL grant, the first repetition of the PUSCH transmission may be the first nominal PUSCH transmission (e.g., Figure 5 1 in slot 0). However, from an actual transmission perspective, the first repetition of a PUSCH transmission may be the first actual PUSCH transmission (e.g., actual PUSCH transmission 502). Therefore, the operation of the UL RTT timer may be affected by different definitions of the "first repetition" of a PUSCH transmission.

[0078] From the perspective of UL grant: the UL resources for the first repetition of the corresponding PUSCH transmission can be dynamically granted by the gNB. Figure 5 As shown, the UL resource indicated by TDRA (the value of L is 4) may start from symbol 12 of time slot 0 to symbol 1 of time slot 1. From the perspective of UL grant, the start timing of the UL RTT timer may be at the first symbol after the end of the UL resource granted for the first repetition of the corresponding PUSCH transmission. That is, from the perspective of UL grant, the UL RTT timer may be started at symbol 2 of time slot 1 (for example, Figure 5 Start at Alt.a) marked in.

[0079] From the perspective of actual transmission: Figure 5As shown, the first nominal repetition of the PUSCH transmission is split into two actual PUSCH repetitions 502 and 504 due to the slot boundary between slot 0 and slot 1. The first actual PUSCH repetition 502 may span from symbol 12 of slot 0 to symbol 13 of slot 0. The second actual PUSCH repetition 504 may span from symbol 0 of slot 1 to symbol 1 of slot 1. From the perspective of the actual PUSCH transmission, the start timing of the UL RTT timer may be at the first symbol just after the first actual PUSCH repetition. That is, the UL RTT timer may be started at symbol 0 of slot 1 (e.g., Figure 5 Start at Alt.b) marked in.

[0080] The corresponding text proposals (TP) are shown in Tables 2, 3 and 4.

[0081] Table 2

[0082]

[0083] Table 3

[0084]

[0085] Table 4

[0086]

[0087] In some embodiments, a PUSCH transmission corresponding to a dynamic UL grant may span at least one DL symbol and / or variable symbols. This may also affect the operation of the UL RTT timer.

[0088] refer to Figure 4 , the DCI may include a TDRA field indicating the UL resources used for PUSCH transmission, where the values ​​of S and L addressed by the TDRA field are 3 and 4, respectively. In addition, the nominal repetition number is configured as 2 by an indicator from the gNB. The UL resources scheduled by the gNB on the PUSCH may start at symbol 3 of slot 0 and occupy the following three UL symbols (i.e., a total of four UL symbols). Figure 4 As shown, because the first nominal repetition corresponding to the UL grant spans one DL symbol (i.e., symbol 5 of slot 0), the first nominal repetition is split into two actual PUSCH repetitions 402 and 404. In addition, the second nominal PUSCH transmission 406 may span from symbol 8 of slot 0 to symbol 11 of slot 1.

[0089] As described above, if the UL RTT timer is configured to start at the first symbol immediately after the "first repetition" of the PUSCH transmission, the start timing of the UL RTT timer may be different because the definition of "first repetition" may be different from the perspective of the UL grant and the perspective of the actual transmission. For example, from the perspective of the UL grant, the first repetition of the PUSCH transmission may be the first nominal PUSCH transmission. From the perspective of the actual transmission, the first repetition of the PUSCH transmission may be the first actual PUSCH transmission. Figure 4 Describes the details of the corresponding timer operation.

[0090] From the perspective of UL grant: UL resources for the first nominal repetition of the corresponding PUSCH transmission can be dynamically granted by the gNB. Figure 4 As shown, the UL resources indicated by TDRA (where the value of L is indicated as 4) may include symbols 3, 4, 6, and 7 of time slot 0. From the perspective of UL grant, the start timing of the UL RTT timer may be at the first symbol immediately after the end of the UL resource granted for the first nominal repetition of the corresponding PUSCH transmission. Figure 4 As shown, in one embodiment, the UL RTT timer may be set at symbol 8 of slot 0 (e.g., Figure 4 Start at the timing marked as "Alt.a" in the figure.

[0091] From the perspective of actual transmission: Figure 4 As shown, the first nominal repetition of the PUSCH transmission is split into two actual PUSCH repetitions 402 and 404 due to the slot boundary between slot 0 and slot 1. The first actual PUSCH repetition 402 may span from symbol 3 of slot 0 to symbol 4 of slot 0. The second actual PUSCH repetition 404 may span from symbol 6 of slot 0 to symbol 7 of slot 0. From the perspective of actual transmission, the start timing of the UL RTT timer may be at the first symbol immediately after the first actual PUSCH repetition. Figure 4 As shown, in one embodiment, the UL RTT timer may be set at symbol 5 of slot 0 (e.g., Figure 4 Start at the timing marked as "Alt.b" in the figure.

[0092] Figure 6 FIG is a diagram illustrating repetition of PUSCH transmission across variable symbols when a non-slot-based repetition scheme is applied according to an embodiment of the present disclosure. Figure 6 As shown, the dynamic scheduling of PUSCH transmission 602 indicated by DCI can span variable symbols (which are in Figure 68.213). The variable symbol may be dynamically configured as a DL symbol or a UL symbol via the sfi-RNTI (as defined in the 3GPP Technical Specification (TS) 38.213). The DCI may include a TDRA field indicating the UL resources used for PUSCH transmission, where the values ​​of S and L addressed by the TDRA field are 3 and 4, respectively. In addition, the nominal number of repetitions is configured to be 2 by an indicator from the BS. If the variable symbol is used as the UL symbol, the first nominal PUSCH transmission 602 may span from symbol 3 of time slot 0 to symbol 6 of time slot 0, and the second nominal PUSCH 604 may span from symbol 7 of time slot 0 to symbol 10 of time slot 0. In this case, the UL RTT timer may start at the first symbol (e.g., symbol 7 of time slot 0) immediately after the end of the first nominal PUSCH transmission 602. If the variable symbol is used as the DL symbol, the operation of the UL RTT timer may be the same as the reference symbol. Figure 4 The cases described are the same (from the UL grant perspective or the actual transmission perspective).

[0093] Case B: Dynamically indicating the number of repetitions of PUSCH transmission

[0094] In some embodiments, in non-slot-based repetition schemes, a dynamic indication (DI) functionality may be provided that enables the gNB to dynamically indicate to the UE the nominal number of repetitions to be used for each dynamic scheduling (or to enable the gNB to indicate the nominal number of repetitions to the UE on a per-dynamic scheduling basis). Additionally, an enable / disable DI (EDDI) mechanism may be provided to enable or disable the DI functionality.

[0095] Figure 7 FIG is a diagram illustrating a UE switching between a dynamic indication mode and a non-dynamic indication mode according to an embodiment of the present disclosure. Figure 7 As shown, the UE can operate in dynamic indication mode 702 or non-dynamic indication mode 704. When the gNB has DL functionality enabled, the UE can operate in dynamic indication mode 702, in which the BS (e.g., the gNB) can indicate the nominal number of repetitions for PUSCH transmissions to the UE via dynamic scheduling signaling (e.g., DCI and / or MAC CE signaling). In contrast, when DL functionality is disabled, the UE can operate in non-dynamic indication mode 704, in which the nominal number of repetitions for PUSCH transmissions can be predefined or preconfigured by the BS via RRC signaling. Whether the UE should operate in dynamic indication mode 702 or non-dynamic indication mode 704 can be controlled by the EDDI mechanism. The following cases describe examples of UE behavior when operating in dynamic indication mode 702 or non-dynamic indication mode 704.

[0096] Case 1:

[0097] In some embodiments, when the UE is in dynamic indication mode, the nominal number of repetitions may be determined by an indicator from the gNB. For example, the indicator may be a DCI field included in the DCI scheduling the UL grant corresponding to the PUSCH transmission. When the PUSCH transmission corresponding to the UL grant is configured to be performed with a non-slot-based repetition scheme, the nominal number of repetitions is determined by an indicator (e.g., a DCI field) received from the gNB. Examples of how the UE determines the nominal number of repetitions based on the received indicator are provided in subcases 1.1 through 1.12 below.

[0098] Subcase 1.1: In some embodiments, the indicator may be a bitstream (content) representing a DCI field that explicitly or implicitly indicates a value for a nominal number of repetitions of a PUSCH transmission corresponding to a UL grant scheduled by the DCI.

[0099] Subcase 1.2: In some embodiments, the indicator can be a bitstream (content) representing a DCI field that explicitly or implicitly indicates a value for a row index of a mapping table. The mapping table can be predefined (e.g., in a 3GPP TS) or preconfigured by the gNB via a DL RRC message. The mapping table can define the association / mapping between the row index and the nominal number of repetitions for the PUSCH transmission scheduled by the DCI.

[0100] Subcase 1.3: In some embodiments, the indicator may be a bitstream (content) of a DCI field that may represent a value of an element index that explicitly or implicitly indicates a repetition list (e.g., pusch-AggregationFactor-urllcList). pusch-AggregationFactor-urllcList may be predefined (e.g., in a 3GPP TS) or preconfigured by the gNB via a downlink (DL) RRC message. pusch-AggregationFactor-urllcList may contain one or more values ​​(e.g., one or more R values ​​shown in Table 1), each indicating a specific number of nominal repetitions for PUSCH transmissions scheduled by the DCI. The value of the element index may indicate which of the one or more R values ​​in the repetition list the UE should apply for PUSCH transmission. For example, when the value of the element index is 0, the UE may select / apply the value / parameter in the first element / row / entry of pusch-AggregationFactor-urllcList; when the value of the element index is 1, the UE may select / apply the value / parameter in the second element / row / entry of pusch-AggregationFactor-urllcList, and so on. In some embodiments, the repetition list (e.g., pusch-AggregationFactor-urllcList) may be configured by the BS on at least one of a UE basis, a serving cell group basis, a serving cell basis, a UL BWP basis, and a configuration grant configuration basis.

[0101] Subcase 1.4: In some embodiments, the indicator may be a bitstream (content) representing a DCI field that explicitly or implicitly indicates the value of a coefficient or parameter. In this case, the nominal number of repetitions for a PUSCH transmission corresponding to a UL grant scheduled by the DCI may be the result of (or obtained by) multiplying the value of the coefficient by the value of a PUSCH aggregation factor (e.g., pusch-AggregationFactor) or the value of a URLLC PUSCH aggregation factor (e.g., pusch-AggregationFactor-urllc). pusch-AggregationFactor may be an existing parameter provided in 3GPP TS 38.331, while pusch-AggregationFactor-urllc may be a newly introduced parameter configured by the gNB to indicate the nominal number of repetitions to the UE. In some embodiments, pusch-AggregationFactor-urllc may be sent by the gNB via a DL RRC message. The pusch-AggregationFactor-urllc may be configured by the gNB on at least one of a UE basis, a serving cell group basis, a serving cell basis, a UL BWP basis, and a configured grant configuration basis. For example, if the pusch-AggregationFactor-urllc is configured by the gNB based on the UL BWP and the gNB schedules PUSCH on the UL BWP, if the gNB indicates that a non-slot-based repetition scheme should be applied to PUSCH transmission, the UE may apply the pusch-AggregationFactor-urllc corresponding to the UL BWP to determine the nominal number of repetitions for PUSCH transmission on the UL BWP.

[0102] Subcase 1.5: The main difference between subcases 1.5 and 1.4 is that the nominal number of repetitions of PUSCH transmission scheduled by DCI can be the result of (or obtained by) adding the value of the coefficient and the value of pusch-AggregationFactor (or the value of pusch-AggregationFactor-urllc).

[0103] Subcase 1.6: The main difference between Subcase 1.6 and 1.4 is that the nominal number of repetitions for a PUSCH transmission scheduled by DCI may be the result of (or obtained by) dividing the value of the coefficient by the value of the coefficient and the value of pusch-AggregationFactor (or the value of pusch-AggregationFactor-urllc). In some other embodiments, the nominal number of repetitions for a PUSCH transmission may be the result of (or obtained by) dividing the value of pusch-AggregationFactor (or the value of pusch-AggregationFactor-urllc) by the value of the coefficient.

[0104] Subcase 1.7: In some embodiments, if the DCI is used to schedule PUSCH on a specific serving cell group / serving cell / UL BWP, the indicator may be a DCI field (e.g., a zero-bit field) included in the DCI. In this case, the DCI field may only apply to PUSCH transmissions on one or more specific serving cell groups / serving cells / UL BWPs.

[0105] Subcase 1.8: In some embodiments, the indicator (e.g., DCI field) may only be present in DCI with CRC bits scrambled by a specific type of UE-specific RNTI. In another embodiment, the UE may apply the indicator only when the indicator (e.g., DCI field) is in DCI with CRC bits scrambled by a specific type of (UE-specific) RNTI.

[0106] Subcase 1.9: In some embodiments, the mapping table and pusch-AggregationFactor-urllcList described in the above subcase may be configured based on the serving cell group / serving cell / UL BWP. In this case, the nominal number of repetitions for PUSCH transmissions on the serving cell group / serving cell / UL BWP may be determined by the mapping table or pusch-AggregationFactor-urllcList corresponding to the serving cell group / serving cell / UL BWP. In another example, PUSCH transmissions scheduled by DCI received on the serving cell group / serving cell / UL BWP may be subject to the mapping table or AggregationFactor-urllcList of the serving cell group / serving cell / UL BWP.

[0107] Subcase 1.10: In some embodiments, the number of bits of the DCI field included in the DCI may be determined by RRC configuration. For example, the DCI field may be determined by the number of elements included in pushch-AggregationFactor-urllcList. For example, the DCI field may be determined as [log2(number of elements in pushch-AggregationFactor-urllcList)].

[0108] Subcase 1.11: In some embodiments, the DCI field may be included in the DCI with (only) CRC bits scrambled by the CS-RNTI (e.g., as provided in 3GPP TS 38.331) configured by the gNB to activate the configuration grant Type II.

[0109] Subcase 1.12: In some embodiments, the DCI field may be (only) included in the Configuration Grant Configuration Information Element (IE) (e.g., ConfiguredGrantConfig IE) (e.g., as provided in 3GPP TS 38.331) applied by the gNB to activate Configuration Grant Type 1 configuration.

[0110] Case 2:

[0111] In some embodiments, when the UE is in the dynamic indication mode 702, the gNB may indicate to the UE via one or more specific indications to switch to the non-dynamic indication mode 704 (e.g., Figure 7 The following subcase describes an example of the indication.

[0112] Subcase 2.1: In some embodiments, a BS (e.g., a gNB) may indicate to a UE whether to operate in dynamic indication mode 702 or non-dynamic indication mode 704 by sending DCI to the UE. In some embodiments, the DCI may have a specific DCI format. For example, upon receiving / detecting a specific DCI format, the UE may operate in dynamic indication mode 702. In contrast, if the UE receives / detects another DCI format, the UE may operate in non-dynamic indication mode 704.

[0113] Subcase 2.2: In some embodiments, a BS (e.g., a gNB) may use a DCI field (indication) included in a DCI to indicate to the UE whether to operate in dynamic indication mode 702 or non-dynamic indication mode 704. In one embodiment, the DCI field may be a single-bit field. For example, if the content of the DCI field is "0," the UE may operate in dynamic indication mode 702. In contrast, if the content of the DCI field is "1," the UE may operate in non-dynamic indication mode 704.

[0114] Subcase 2.3: The main difference between subcase 2.3 and subcase 2.2 is that whether the UE should operate in dynamic indication mode 702 or non-dynamic indication mode 704 may be indicated by the specific value of the DCI field introduced in case 1 of scenario 2. For example, when the content / value of the DCI field is set to a first value by the gNB, the UE may switch to non-dynamic indication mode 704 (e.g., Figure 7 When the content / value of the DCI field is set to the second value by the gNB, the UE may switch from the non-dynamic indication mode 704 to the dynamic indication mode 702 (e.g., as shown in FIG. Figure 7 (indicated by path a in ).

[0115] Subcase 2.4: In some embodiments, the gNB may indicate to the UE via a MAC Control Element (CE) whether the UE should operate in dynamic indication mode 702 or non-dynamic indication mode 704. For example, one or more fields included in the MAC CE may be used to indicate to the UE whether the UE should operate in dynamic indication mode 702 or non-dynamic indication mode 704 for each serving cell group / serving cell / BWP / UL BWP / PUSCH. In some embodiments, the UE may default to operating in dynamic indication mode 702 or non-dynamic indication mode 704 to perform PUSCH transmission on each serving cell group / serving cell / UL BWP. For example, after a serving cell group is configured and before receiving a MAC CE corresponding to the serving cell group, the UE may default to performing PUSCH transmission on the serving cell group in dynamic indication mode 702 or non-dynamic indication mode 704. For example, after a serving cell is configured and before a MAC CE corresponding to the serving cell is received, the UE may perform PUSCH transmission on the serving cell group in the dynamic indication mode 702 or the non-dynamic indication mode 704 by default. For example, after a UL BWP is configured and before a MAC CE corresponding to the UL BWP is received, the UE may perform PUSCH transmission on the UL BWP in the dynamic indication mode 702 or the non-dynamic indication mode 704 by default.

[0116] Subcase 2.5: The main difference between Subcase 2.4 and Subcase 2.3 is that the gNB may indicate to the UE via a first MAC CE that it is operating in dynamic indication mode 702 and may indicate to the UE via a second MAC CE that it is operating in non-dynamic indication mode 704. One or more fields included in the first / second MAC CE may be used to indicate to the UE whether to operate in dynamic indication mode 702 or non-dynamic indication mode 704 for each serving cell group / serving cell / BWP / UL BWP / PUSCH.

[0117] Subcase 2.6: In some embodiments, the gNB may indicate to the UE via a specific RNTI whether the UE should operate in dynamic indication mode 702 or non-dynamic indication mode 704. The specific RNTI may be configured by the gNB via one or more DL RRC messages based on the serving cell group / serving cell / UL BWP. For example, upon receiving DCI with CRC bits scrambled by a specific RNTI, the UE may perform PUSCH transmission on the serving cell group / serving cell / UL BWP in dynamic indication mode 702 until the UE again receives DCI with CRC bits scrambled by the specific RNTI. In some embodiments, the UE may default to operating in dynamic indication mode 702 or non-dynamic indication mode 704 to perform PUSCH transmission on each serving cell group / serving cell / UL BWP. For example, after a serving cell group is configured and before receiving DCI with CRC bits scrambled by a specific RNTI corresponding to the serving cell group, the UE may default to performing PUSCH transmission on the serving cell group in dynamic indication mode 702 or non-dynamic indication mode 704. For example, after a serving cell is configured and activated and before receiving DCI with CRC bits scrambled by a specific RNTI corresponding to the serving cell, the UE may perform PUSCH transmission on the serving cell in the dynamic indication mode 702 or the non-dynamic indication mode 704 by default. For example, after a UL BWP is configured and activated and before receiving DCI with CRC bits scrambled by a specific RNTI corresponding to the UL BWP, the UE may perform PUSCH transmission on the serving cell in the dynamic indication mode 702 or the non-dynamic indication mode 704 by default.

[0118] Subcase 2.7: The main difference between Subcase 2.6 and Subcase 2.7 is that the gNB can indicate to the UE via a specific RNTI that it is operating in dynamic indication mode 702 and indicate to the UE via another specific RNTI that it is operating in non-dynamic indication mode 704.

[0119] Subcase 2.8: In some embodiments, the default mode (e.g., dynamic indication mode 702 or non-dynamic indication mode 704) for a serving cell group / serving cell / UL BWP may be configured by the gNB via one or more DL RRC messages. For example, the UE may perform PUSCH transmission on the serving cell group / serving cell / UL BWP in the default mode before receiving the corresponding MAC CE or DCI.

[0120] Subcase 2.9: In some embodiments, the UE may be configured with a timer. Upon receiving an indication (e.g., MAC CE, DCI, or RNTI) instructing the UE to switch to an operating mode different from the default mode (e.g., dynamic indication mode 702 or non-dynamic indication mode 704), the UE may start a timer. When the timer expires, the UE may automatically switch from the operating mode to the default mode without receiving further instructions from the gNB. In some embodiments, upon receiving a (specific) UL grant, the UE may restart the timer. In some embodiments, the timer may be maintained / configured on a per-serving cell group / serving cell / UL BWP basis. The timer length may be preconfigured by the gNB via a DL RRC message.

[0121] Case 3:

[0122] Figure 8 A flowchart of a procedure executed by a UE according to an embodiment of the present disclosure is shown. Figure 8 As shown, in action 802, the UE may operate in a dynamic indication mode. In action 804, the UE may receive an indication to switch to a non-dynamic indication mode. In action 806, the UE may perform specific operations in response to receiving the indication. Examples of specific operations are described in one or more sub-cases below.

[0123] Subcase 3.1: In some embodiments, the DCI may include a first DCI field that indicates to the UE that it is operating in dynamic indication mode. In this case, the nominal number of repetitions of the PUSCH transmission may be indicated by a second DCI field, such as an existing DCI field (e.g., which is provided in current 3GPP TS 38.212). For example, when an existing DCI field is used as the second DCI field, the content of the existing DCI field may be changed to indicate to the UE the nominal number of repetitions of the PUSCH transmission corresponding to the UL grant scheduled by the DCI. In addition, the details of how the existing DCI field indicates the nominal number of repetitions to the UE may be implemented based on one or more embodiments described in Case 1 of Scenario B. On the other hand, if the first DCI field indicates to the UE that it is operating in non-dynamic indication mode, the second DCI field may remain the same as it is defined in 3GPP TS 38.212. In some embodiments, the first DCI field and the second DCI field may be included in the DCI that schedules the UL grant. In this case, if the UE is configured to perform PUSCH transmission corresponding to the UL grant based on a non-slot-based repetition scheme, the nominal number of repetitions of the PUSCH transmission may be determined by the first DCI field and the second DCI field received from the gNB. For example, the first DCI field may (implicitly) indicate whether the PUSCH transmission should be performed based on the PUSCH repetition scheme, and the second DCI field may explicitly indicate the row / entry in the TDRA table (e.g., via the row / entry index of the TDRA table).

[0124] Subcase 3.2: In some embodiments, when operating in non-dynamic indication mode, the UE may fall back to applying a slot-based repetition scheme for PUSCH transmission. The number of PUSCH repetitions for a PUSCH transmission may be configured, for example, by a pusch-aggregation factor as defined in 3GPP TS 38.331.

[0125] Subcase 3.3: In some embodiments, when operating in non-dynamic indication mode, the UE may apply a non-slot-based repetition scheme to perform PUSCH transmissions. The nominal number of repetitions for PUSCH transmissions may be a fixed value configured, for example, by pusch-Aggregationfactor-urllc.

[0126] Case 4: In some embodiments, the nominal number of repetitions may be implicitly indicated by a TDRA index (e.g., a row / entry index indicating a row / entry included in a TDRA table). One or more non-slot-based repetition scheme-specific TDRA tables at the UE may be preconfigured by the gNB or predefined in the 3GPP TS. For example, as shown in Table 1, each row / entry in the TDRA table may define a mapping / association between a specific number of nominal repetitions (e.g., an R value) used to configure PUSCH transmissions and a set of parameters (including at least one of K2, S, and L). In some embodiments, the TDRA tables configured in the UE may apply to different cyclic prefix (CP) modes (e.g., normal CP or extended CP). Upon receiving a TDRA value (e.g., a row / entry index of a TDRA table), the UE may determine the R value and a set of parameters (e.g., K2, L, and / or S values) to be applied to the PUSCH transmission based on the corresponding TDRA table. In some embodiments, the UE may be configured with at least one first TDRA table configured for a non-slot-based repetition scheme and at least one second TDRA table configured for a slot-based repetition scheme. In some other embodiments, the UE may be configured with at least one first TDRA table configured for a dynamic indication mode and at least one second TDRA table configured for a non-dynamic indication mode.

[0127] Subcase 4.1: In some other embodiments, the TDRA table may include one or more indicators, each of which may not directly indicate a nominal number of repetitions for PUSCH transmission. Instead, each indicator may be associated with (or indicate) a nominal number of repetitions. In this case, the UE may determine the nominal number of repetitions based on the one or more indicators. For example, based on certain predefined / preconfigured mapping rules, when the value of the indicator is "1," the UE may determine the nominal number of repetitions to be "2," and when the value of the indicator is "2," the UE may determine the nominal number of repetitions to be "4."

[0128] Case 5:

[0129] In some embodiments, the gNB may configure a parameter, pusch-AggregationFactor-urllc, for one or more specific UL BWPs and another parameter, pusch-AggregationFactor-urllc, for the serving cell. In this case, the UE may know that PUSCH transmissions on a specific UL BWP (which is configured with pusch-AggregationFactor-urllc) should be performed based on a non-slot-based repetition scheme by setting the nominal number of repetitions to the value of pusch-AggregationFactor-urllc configured for the specific UL BWP. In contrast, if the PUSCH transmission is on a UL BWP not configured with pusch-AggregationFactor-urllc, the UE may perform PUSCH transmissions based on a non-slot-based repetition scheme by setting the nominal number of repetitions to the value of pusch-AggregationFactor-urllc of the serving cell configured for the UL BWP.

[0130] Subcase 5.1: In some embodiments, similar to Case 5, the gNB may configure a parameter pusch-AggregationFactor-urllc for one or more specific serving cells and another parameter pusch-AggregationFactor-urllc for a serving cell group. In this case, the UE may know that PUSCH transmissions on a serving cell configured with pusch-AggregationFactor-urllc should be performed based on a non-slot-based repetition scheme by setting the nominal number of repetitions to the value of pusch-AggregationFactor-urllc configured for the specific serving cell. In contrast, if the PUSCH transmission is on a serving cell not configured with pusch-AggregationFactor-urllc, the UE may perform PUSCH transmissions based on a non-slot-based repetition scheme by setting the nominal number of repetitions of the PUSCH transmission to the value of pusch-AggregationFactor-urllc configured for the serving cell group.

[0131] Figure 9 Flowchart showing a procedure performed by a UE according to an embodiment of the present disclosure. It should be noted that although actions 902, 904, 906, 908, 910 and 912 are depicted as Figure 9 Individual actions are shown as separate boxes, but these individually depicted actions should not be construed as being order dependent. Figure 9The order in which the actions performed in 902 are described is not intended to be construed as limiting, and any number of the described blocks may be combined in any order to implement the method or an alternative method. However, in some embodiments of the present disclosure, one or more of actions 902, 904, 906, 908, 910, and 912 may be omitted.

[0132] like Figure 9 As shown, in action 902, the UE may receive an RRC configuration including a first parameter configured with a first value and a second parameter configured with at least one second value. Each of the first value and the one or more second values ​​respectively indicates a number of PUSCH repetitions. In some embodiments, the first parameter and the second parameter may correspond to different information elements (IEs) in the RRC configuration, wherein the first parameter may point to a single first value and the second parameter may point to (or may be) a repetition list including one or more second values ​​(e.g., one or more R values ​​shown in Table 1). In some embodiments, the first parameter and the second parameter may be based on a serving cell group / serving cell / BWP configuration.

[0133] In act 904, the UE may receive DCI on the PDCCH scheduling the PUSCH transmission.

[0134] In action 906, the UE may select a first parameter or a second parameter based on the DCI to determine the number of PUSCH repetitions for PUSCH transmission. In some embodiments, the UE may select the first parameter or the second parameter based on the DCI field / DCI format of the received DCI. For example, because each DCI format may have its own corresponding DCI field, when performing blind decoding, the UE may determine the DCI format of the DCI by checking whether the DCI can be successfully decoded through a set of DCI fields. In this case, when the DCI has a DCI format associated with a second parameter and includes an index indicating one of one or more second values, the UE may select the second parameter to determine the number of PUSCH repetitions for PUSCH transmission. In some embodiments, the second parameter (e.g., a repetition list) may define an association between an index (e.g., a row / entry index of the repetition list) and a set of values, the set of values ​​including a third value (e.g., a value of S) indicating the starting symbol of the PUSCH transmission and a fourth value (e.g., a value of L) indicating the number of consecutive symbols of the PUSCH transmission.

[0135] In action 908, when the first parameter is selected, the UE may determine the number of PUSCH repetitions for PUSCH transmission as the first value. For example, if the first parameter is configured with a first value of "2", the UE may determine that the number of PUSCH repetitions for PUSCH transmission is 2. In another example, the first value may not directly represent the number of PUSCH repetitions for PUSCH transmission, but may have a preconfigured / predefined mapping relationship with the number of PUSCH repetitions for PUSCH transmission (for example, the first value may be used as an index of the number of PUSCH repetitions for PUSCH transmission). In this case, the UE may determine the number of PUSCH repetitions for PUSCH transmission based on the first value and the preconfigured / predefined mapping relationship.

[0136] In action 910, when the second parameter is selected, the UE may determine the number of PUSCH repetitions for PUSCH transmission as at least one second value indicated by the DCI. For example, if the second parameter is configured with several second values, such as "2", "3", and "4", and the DCI (e.g., a DCI field included in the DCI) indicates the second value (e.g., "3"), the UE may determine that the number of PUSCH repetitions for PUSCH transmission is 3. In another example, the second value may not directly indicate the number of PUSCH repetitions for PUSCH transmission, but may have a preconfigured / predefined mapping relationship with the number of PUSCH repetitions for PUSCH transmission (e.g., the second value may be used as an index of the number of PUSCH repetitions for PUSCH transmission). In this case, the UE may determine the number of PUSCH repetitions for PUSCH transmission based on the second value and the preconfigured / predefined mapping relationship.

[0137] In action 912, the UE may perform PUSCH transmission a certain number of times based on the PUSCH repetition number for PUSCH transmission (e.g., the UE may repeat PUSCH transmission between a group of consecutive UL symbols) (e.g., the number of times PUSCH transmission is performed may be determined by (or equal to) the PUSCH repetition number for PUSCH transmission. For example, if the second parameter is selected and the indicated second value included in the second parameter (e.g., repetition list) is "4", the UE may determine that the PUSCH repetition number for PUSCH transmission scheduled by DCI is 4 (if the second value directly indicates the PUSCH repetition number for PUSCH transmission). In this case, the UE may perform an initial transmission of the scheduled PUSCH / TB, and then repeat the initial transmission of the scheduled PUSCH / TB three times. Therefore, the total number of PUSCH / TB transmissions performed by the UE is 4 (i.e., one initial PUSCH / TB transmission (or "first PUSCH / TB repetition") + three repeated PUSCH / TB transmissions (or "second, third, and fourth PUSCH / TB repetitions")).

[0138] In some embodiments, each of the above (sub)cases may be applied when one or more specific conditions are met. For example, the specific conditions may include:

[0139] The UE is configured with specific access stratum (AS) layer functions (e.g., Packet Data Convergence Protocol (PDCP) replication function);

[0140] (b) The UE is configured with a specific AS layer function (e.g., PDCP duplication function) and the specific AS layer function is activated; and

[0141] (c) The UE is configured with RRC connections with two or more gNBs / eNBs.

[0142] The following provides non-limiting descriptions of some terms.

[0143] Cell: In some embodiments, a cell (e.g., PCell or SCell) may be a radio network object that can be uniquely identified by a UE through corresponding identification information that may be broadcast by UTRAN access points in a geographical area. A cell may operate in Frequency Division Duplex (FDD) or Time Division Duplex (TDD) mode.

[0144] Serving cell: In some embodiments, for a UE in the RRC_CONNECTED state and not configured with Carrier Aggregation (CA) / Dual Connectivity (DC), the UE may be configured with only one serving cell (e.g., PCell). For a UE operating in the RRC_CONNECTED state and configured with CA / DC, the UE may be configured with multiple serving cells, including SpCells and one or more SCells.

[0145] CA: In some embodiments, in the case of CA, two or more component carriers (CCs) may be aggregated. The UE may receive or transmit signals simultaneously on one or more CCs according to its capabilities. Both contiguous CCs and non-contiguous CCs may support CA. When CA is applied, frame timing and system frame number (SFN) may be aligned across aggregated cells. In some embodiments, the maximum number of CCs configured for the UE may be 16 for DL ​​and 16 for UL. When CA is configured, the UE may have only one RRC connection with the network. During RRC connection establishment / reestablishment / handover, one serving cell may provide non-access stratum (NAS) mobility information, and upon RRC connection reestablishment / handover, one serving cell may provide security input, where the serving cell may be referred to as a PCell. Depending on the capabilities of the UE, the SCell may be configured to form a set of serving cells for the UE together with the PCell. Therefore, a set of serving cells configured for the UE always consists of one PCell and one or more SCells.

[0146] Configuration grant: In some embodiments, for configuration grant type 1, the RRC entity may directly provide the configuration uplink grant (including periodicity). For configuration grant type 2, the RRC entity may define the periodicity of the PUSCH resources of the CG, and the PDCCH addressed to the configuration scheduling-RNTI (CS-RNTI) may signal and activate or deactivate the configuration uplink grant. That is, the PDCCH addressed to the CS-RNTI may indicate that the configuration uplink grant may be reused according to the periodicity defined by the RRC entity until the set uplink grant is deactivated. When the configuration uplink grant is active, if the UE cannot find its C-RNTI / CS-RNTI / MCS-C-RNTI on one or more PDCCHs, an UL transmission according to the configuration uplink grant may be performed. If the UE receives its C-RNTI / CS-RNTI / MCS-C-RNTI on one or more PDCCHs, the PDCCH allocation may overwrite the configuration uplink grant. In some embodiments, the use of MCS-C-RNTI may be equivalent to the use of C-RNTI in the MAC procedure (except for the C-RNTI MAC CE).

[0147] HARQ: In some embodiments, HARQ processes can be used to ensure transmission between two or more peer entities at Layer 1 (e.g., the PHY layer). When the PHY layer is not configured for DL / UL spatial multiplexing, a single HARQ process can support a TB. When the PHY layer is configured for DL / UL spatial multiplexing, a single HARQ process can support one or more TBs. Each serving cell can correspond to a HARQ entity, where each HARQ entity can support parallel processing of DL and UL HARQ processes.

[0148] HARQ Acknowledgement (HARQ-ACK): In some embodiments, HARQ-ACK may include a 1-bit indicator, where when the bit value of the indicator is "0", the HARQ-ACK may be a negative acknowledgement (NACK), and when the bit value of the indicator is "1", it may be a positive acknowledgement (ACK).

[0149] Timers: In some embodiments, the UE's MAC entity may set one or more timers for specific purposes (such as triggering uplink signaling retransmissions or limiting uplink signaling retransmission periods). When a timer maintained by the MAC entity (e.g., a timer described in various embodiments of the present invention) is started, the timer may begin running until it stops or expires. Furthermore, when a timer is not started, it may not run. A timer may be started while it is not running. Furthermore, a timer may be restarted while it is running. In some embodiments, a timer may always start or restart from an initial value, where the initial value may be configured by the gNB via downlink RRC signaling, but is not limited to this.

[0150] BWP: In some embodiments, a BWP may be a subset of the total cell bandwidth of a cell. Bandwidth Adaptation (BA) is achieved by configuring one or more BWPs for the UE and informing the UE which of the configured BWPs is the currently active BWP. To implement the BA mechanism on the PCell, the gNB may configure one or more UL and DL BWPs for the UE. In the case of carrier aggregation, to implement the BA mechanism on the SCell, the gNB may configure at least one or more DL BWPs for the UE (this means that no UL BWP may be configured for the UE). For the PCell, the initial BWP may be the BWP used for initial access. For one or more SCells, the initial BWP may be the BWP configured for the UE to first operate during the SCell activation procedure. In some embodiments, the UE may be configured with a first active UL BWP using the firstActiveUplinkBWP IE field. If the first active UL BWP is configured for the SpCell, the firstActiveUplinkBWP IE field may contain the ID of the UL BWP to be activated when performing RRC (re)configuration. If this field is not present, RRC (re)configuration may not trigger a BWP switch. If the first active uplink BWP is configured for the SCell, the firstActiveUplinkBWP IE field may contain the ID of the UL BWP to be used upon MAC activation of the SCell.

[0151] PDCCH: In some embodiments, the gNB can dynamically allocate resources to the UE via the C-RNTI / MCS-C-RNTI / CS-RNTI on one or more PDCCHs. When DL reception is enabled for the UE, the UE can always monitor the PDCCH(s) for possible assignments (e.g., DRX activity, if configured). In some embodiments, when Carrying Out Carriers (CARs) is configured, the same C-RNTI can be applied to all serving cells.

[0152] Physical Downlink Shared Channel (PDSCH) / PUSCH: In some embodiments, the PDCCH may be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH.

[0153] Time Alignment Timer: In some embodiments, the RRC entity may configure an initial value for a time alignment timer. A time alignment timer (e.g., timeAlignmentTimer) may be used to maintain UL time alignment, where the time alignment timer may be configured and maintained based on a Timing Advance Group (TAG). The time alignment timer may be used to control the length of time that a MAC entity considers a serving cell belonging to an associated TAG to be aligned with UL time.

[0154] Start and Length Indicator (SLIV): In some embodiments, SLIV may be used for time domain allocation of PUSCH / PDSCH. SLIV may define the starting symbol and the number of consecutive symbols used for PUSCH / PDSCH allocation.

[0155] TB: Data from an upper layer (eg, MAC layer / entity) to a PHY layer may generally be referred to as a TB.

[0156] It should be noted that the terms, definitions, and abbreviations described in this disclosure may be derived from existing documents (European Telecommunications Standards Institute (ETSI), International Telecommunication Union (ITU), etc.) or newly created by 3GPP experts.

[0157] In some embodiments, the Reference Signal (RS) ID may be replaced by one or more other IDs used to explicitly or implicitly indicate the new beam to the gNB.

[0158] In some embodiments, the DL RRC message may be an RRC reconfiguration message (e.g., RRCReconfiguration), an RRC recovery message (e.g., RRCResume), an RRC re-establishment message (e.g., RRCReestablishment), an RRC setup message (e.g., RRCSetup), or any other DL unicast RRC message.

[0159] In some embodiments, a beam may be considered as a spatial filter. For example, a wireless device (e.g., a UE) may apply a spatial filter in the analog domain by adjusting the phase and / or amplitude of a signal before sending the signal through a corresponding antenna element. In another example, a spatial filter may be applied in the digital domain through a multi-input multi-output (MIMO) technology in a wireless communication system. For example, a UE may perform PUSCH transmission through a specific beam that serves as a specific spatial / digital domain filter. In some embodiments, a beam may be represented by (or correspond to) an antenna, an antenna port, an antenna element, a group of antennas, a group of antenna ports, or a group of antenna elements. In some embodiments, a beam may be formed by (or associated with) a specific RS resource. A beam may be equivalent to a spatial filter through which an electromagnetic (EM) wave is radiated.

[0160] In some embodiments, the signaling sent means that a MAC CE / MAC protocol data unit (PDU) / layer 1 signaling / higher layer signaling including the signaling (or corresponding thereto) is starting to be sent, is completely sent, or has been delivered to a corresponding HARQ process / buffer for transmission. In some embodiments, the signaling sent means that corresponding HARQ-ACK feedback for a specific MAC PDU has been received, where the specific MAC PDU may include a MAC CE / layer 1 signaling / higher layer signaling including the signaling (or corresponding thereto). In some embodiments, the signaling sent means that a MAC CE / MAC PDU corresponding to the signaling has been constructed or generated.

[0161] In some embodiments, HARQ-ACK feedback may be implemented using DCI formats 0_0, 0_1, or one or more other DCI formats received by the UE from the gNB on the PDCCH. In some embodiments, the received DCI may include a New Data Indicator (NDI), which may be set to a specific value (e.g., 1). In addition, the DCI may indicate a HARQ process ID that is the same as the HARQ process ID applied to (or indicated by) the HARQ process transmitted by the MAC PDU (which carries the Beam Failure Recovery request (BFRQ) MAC CE).

[0162] In some embodiments, the PDCCH may be sent by the gNB to the UE, and the UE may receive the PDCCH from the gNB. Similarly, the PDSCH may be sent by the gNB to the UE, and the UE may receive the PDSCH from the gNB. For UL transmissions, the PUSCH / PUCCH may be sent by the UE to the gNB, and the PUSCH / Physical Uplink Control Channel (PUCCH) may be received by the gNB.

[0163] In some embodiments, a PDSCH / PUSCH transmission may span multiple symbols in the time domain, where the duration of the PDSCH / PUSCH (transmission) may be a time interval starting from the beginning of the first symbol of the PDSCH / PUSCH (transmission) and ending at the end of the last symbol of the PDSCH / PUSCH (transmission).

[0164] In some implementations, the terms "interrupt," "stop," "cancel," and "skip" may be interchangeable.

[0165] Figure 10 A block diagram of a node for wireless communication according to various aspects of the present disclosure is shown. Figure 10 As shown, the node 1000 may include a transceiver 1006, a processor 1008, a memory 1002, one or more presentation components 1004, and at least one antenna 1010. The node 1000 may also include an RF spectrum band module, a BS communication module, a network communication module, a system communication management module, an input / output (I / O) port, an I / O component, and a power supply ( Figure 10 Each of these components may communicate with each other directly or indirectly via one or more buses 1024. In one embodiment, the node 1000 may be a processor that executes the methods described herein, for example, with reference to FIG. Figures 1 to 9 The various functions of a UE or BS are described.

[0166] The transceiver 1006, having a transmitter 1016 (e.g., transmitting / transmission circuitry) and a receiver 1018 (e.g., receiving / reception circuitry), can be configured to transmit and / or receive time and / or frequency resource partitioning information. In some embodiments, the transceiver 1006 can be configured to transmit in different types of subframes and time slots, including but not limited to usable, unusable, and flexibly usable subframe and time slot formats. The transceiver 1006 can be configured to receive data and control channels.

[0167] Node 1000 may include a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by node 1000, and include both volatile (and non-volatile) media and removable (and non-removable) media. By way of example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media may include both volatile (and non-volatile) and removable (and non-removable) media, which are implemented according to any method or technology for storing information, such as computer-readable information.

[0168] Computer storage media include RAM, ROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disk (DVD) (or other optical disk storage devices), cassettes, magnetic tape, magnetic disk storage devices (or other magnetic storage devices), etc. Computer storage media do not include propagating data signals. Communication media can typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and include any information delivery media. The term "modulated data signal" may refer to a signal having one or more characteristics set or changed in a manner that encodes information in the signal. By way of example (and not limitation), communication media may include wired media (such as a wired network or a direct wired connection) and wireless media (such as acoustic, radio frequency (RF), infrared, and other wireless media). Any combination of the above media should also be included within the scope of computer-readable media.

[0169] The memory 1002 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 1002 may be removable, non-removable, or a combination thereof. For example, the memory 1002 may include solid-state memory, a hard drive, an optical drive, etc. Figure 10 As shown, the memory 1002 may store computer-readable and / or executable instructions 1014 (e.g., software code) that, when executed, cause the processor 1008 to perform the operations described herein, for example, with reference to Figures 1 to 9 Alternatively, the instructions 1014 may not be directly executable by the processor 1008, but rather may be configured to cause the node 1000 (eg, when compiled and executed) to perform the various functions described herein.

[0170] The processor 1008 (e.g., having processing circuitry) may include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 1008 may include a memory. The processor 1008 may process data 1012 and instructions 1014 received from the memory 1002, as well as information transmitted through the transceiver 1006, the baseband communication module, and / or the network communication module. The processor 1008 may also process information to be transmitted to the transceiver 1006 for transmission to the network communication module via the antenna 1010 for transmission to the core network.

[0171] One or more presentation components 1004 can present data indications to a person or other device. Examples of presentation components 1004 can include a display device, a speaker, a printing component, a vibration component, and the like.

[0172] According to the above description, without departing from the scope of the concepts described in this application, various technologies can be used to realize these concepts. In addition, although these concepts have been described by specific reference to certain embodiments, those of ordinary skill in the art will recognize that, without departing from the scope of these concepts, changes can be made in form and detail. Thus, the described embodiments are considered to be illustrative and non-restrictive in all aspects. It should also be understood that the application is not limited to the specific embodiments described above, but many rearrangements, modifications and replacements are possible without departing from the scope of this disclosure.

Claims

1. A method for handling repeated transmission in a wireless communication system, performed by a user equipment (UE), the method comprising: receiving a radio resource control (RRC) configuration including a first parameter configured with a first value and a second parameter configured with at least one second value, each of the first value and the at least one second value indicating a physical uplink shared channel (PUSCH) repetition number; Receiving downlink control information (DCI) on a physical downlink control channel (PDCCH) that schedules PUSCH transmission; selecting one of the first parameter and the second parameter according to the DCI to determine a number of PUSCH repetitions for the PUSCH transmission; When the first parameter is selected, determining the number of PUSCH repetitions used for the PUSCH transmission as the first value; when the second parameter is selected, determining the number of PUSCH repetitions for the PUSCH transmission as one of the at least one second value indicated by an index included in the DCI, wherein the second parameter defines an association between the index and a set of values ​​including a third value indicating a starting symbol of the PUSCH transmission and a fourth value indicating a number of consecutive symbols of the PUSCH transmission; and The PUSCH transmission is performed a number of times based on the PUSCH repetition number for the PUSCH transmission.

2. The method of claim 1, further comprising: When the DCI has a DCI format associated with the second parameter and includes the index indicating the one of the at least one second value, the second parameter is selected to determine the number of PUSCH repetitions for the PUSCH transmission.

3. The method according to claim 1, wherein The first parameter and the second parameter are configured based on a bandwidth part BWP.

4. A user equipment (UE) for processing repeated transmission in a wireless communication system, the UE comprising: one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; as well as at least one processor coupled to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to: receiving a radio resource control (RRC) configuration including a first parameter configured with a first value and a second parameter configured with at least one second value, each of the first value and the at least one second value indicating a physical uplink shared channel (PUSCH) repetition number; Receiving downlink control information (DCI) on a physical downlink control channel (PDCCH) that schedules PUSCH transmission; selecting one of the first parameter and the second parameter according to the DCI to determine a number of PUSCH repetitions for the PUSCH transmission; When the first parameter is selected, determining the number of PUSCH repetitions used for the PUSCH transmission as the first value; when the second parameter is selected, determining the number of PUSCH repetitions for the PUSCH transmission as one of the at least one second value indicated by an index included in the DCI, wherein the second parameter defines an association between the index and a set of values ​​including a third value indicating a starting symbol of the PUSCH transmission and a fourth value indicating a number of consecutive symbols of the PUSCH transmission; and The PUSCH transmission is performed a certain number of times based on the PUSCH repetition number for the PUSCH transmission.

5. The UE according to claim 4, wherein: The at least one processor is further configured to execute the computer-executable instructions to: When the DCI has a DCI format associated with the second parameter and includes the index indicating the one of the at least one second value, the second parameter is selected to determine the number of PUSCH repetitions for the PUSCH transmission.

6. The UE according to claim 4, wherein: The first parameter and the second parameter are configured based on a bandwidth part BWP.

Images