User equipment, base station and signaling for enhanced uplink transmission

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive signaling, the signaling including a configuration for a configured authorized physical uplink shared channel (PUSCH) or a configuration based on an authorized PUSCH. The UE also includes a high-level processor configured to determine whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the authorized PUSCH. The UE also includes a transmission circuit configured to transmit these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the authorized PUSCH.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and more particularly to user equipment, base stations and signaling for enhanced uplink transmission. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for multiple wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with a wireless communication device.

[0003] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the invention

[0005] In one example, a user equipment (UE) communicating with a base station includes: a receiving circuit, the receiving circuit being configured to: receive a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, and receive an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission; a transmitting circuit, the transmitting circuit being configured to: perform the CG PUSCH transmission based on the first information, perform the GB PUSCH transmission based on the second information based on detection of a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), and perform retransmission of the CG PUSCH transmission based on the second information based on detection of a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1.

[0006] In one example, a base station device that communicates with a user equipment (UE) includes: a transmission circuit, which is configured to: transmit a radio resource control (RRC) message including first information, the first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, and transmit an RRC message including second information, the second information indicating a repetition type for a grant-based (GB) PUSCH transmission; a receiving circuit, which is configured to: receive the CG PUSCH transmission based on the first information, based on the transmission of a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), based on the second information to receive the GB PUSCH transmission, based on the transmission of a PDCCH with a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1, and based on the second information to receive a retransmission of the CG PUSCH transmission.

[0007] In one example, a communication method for a user equipment includes: receiving a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, receiving an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission, performing the CG PUSCH transmission based on the first information, performing the GB PUSCH transmission based on the second information based on detecting a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), and performing retransmission of the CGPUSCH transmission based on the second information based on detecting a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI)=1.

[0008] In one example, a communication method for a base station device includes: transmitting a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmitting an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission, and a receiving circuit configured to: receive the CG PUSCH transmission based on the first information, based on the transmission of a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), based on the second information to receive the GB PUSCH transmission, based on the transmission of a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1, and based on the second information to receive a retransmission of the CG PUSCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] [ Figure 1 ] Figure 1 is a block diagram illustrating one specific implementation of one or more base stations (gNBs) and one or more user equipments (UEs) for enhanced uplink transmission.

[0010] [ Figure 2 ] Figure 2 is a diagram showing an example of a resource grid for a downlink.

[0011] [ Figure 3 ] Figure 3 is a diagram showing an example of a resource grid for uplink.

[0012] [ Figure 4 ] Figure 4 Several examples of parameters are shown.

[0013] [ Figure 5 ] Figure 5 Shown for Figure 4 An example of a subframe structure with the parameters shown in FIG.

[0014] [ Figure 6 ] Figure 6 Examples of time slots and sub-time slots are shown.

[0015] [ Figure 7 ] Figure 7 An example of a scheduling timeline is shown.

[0016] [ Figure 8 ] Figure 8 An example of a DL control channel monitoring region is shown.

[0017] [ Fig. 9 ] Fig. 9 An example of a DL control channel comprising more than one control channel element is shown.

[0018] [ Fig.10 ] Fig.10 An example of a UL control channel structure is shown.

[0019] [ Fig.11 ] Fig.11 is a block diagram illustrating a specific implementation of a gNB.

[0020] [ Fig.12 ] Fig.12 is a block diagram illustrating a specific implementation of a UE.

[0021] [ Fig.13 ] Fig.13 Various components that may be utilized in a UE are shown.

[0022] [ Fig.14 ] Fig.14 Various components that may be utilized in a gNB are shown.

[0023] [ Fig.15 ] Fig.15 is a block diagram illustrating a specific implementation of a UE in which systems and methods implement mini-slot based repetition.

[0024] [ Fig.16 ] Fig.16 is a block diagram illustrating a specific implementation of a gNB in ​​which systems and methods implement mini-slot based repetition.

[0025] [ Fig.17 ] Fig.17 is a flow chart illustrating a method performed by a UE.

[0026] [ Fig.18 ] Fig.18 is a flow chart illustrating a method performed by a gNB. DETAILED DESCRIPTION

[0027] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive signaling, the signaling including a configuration for a configured authorized physical uplink shared channel (PUSCH) or a configuration based on an authorized PUSCH. The UE also includes a high-level processor configured to determine whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the authorized PUSCH. The UE also includes a transmission circuit configured to transmit these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the authorized PUSCH.

[0028] In one method, one uplink (UL) grant for grant-based PUSCH and one configured grant configuration for configured grant PUSCH are used to support one or more actual PUSCH repetitions in one slot, or two or more actual PUSCH repetitions across slot boundaries in consecutive available slots.

[0029] In another method, one UL grant for grant-based PUSCH and one configured grant configuration for configured grant PUSCH are used to support one or more PUSCH repetitions in one slot, or two or more PUSCH repetitions across slot boundaries in consecutive available slots.

[0030] The present invention also describes a base station (gNB). The gNB includes a transmission circuit configured to transmit signaling to a UE, the signaling including a configuration for a configured authorized PUSCH or a PUSCH based on the authorization. The gNB also includes a higher-level processor configured to determine whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the PUSCH based on the authorization. The gNB also includes a receiving circuit configured to receive multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or the PUSCH based on the authorization from the UE.

[0031] A method performed by a UE is also described. The method also includes receiving signaling that includes a configuration for a configured authorized PUSCH or a PUSCH based on the grant. The method also includes determining whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the PUSCH based on the grant. The method also includes transmitting multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or the PUSCH based on the grant.

[0032] A method performed by a gNB is also described. The method includes transmitting signaling to a UE, the signaling including a configuration for a configured granted PUSCH or a grant-based PUSCH. The method also includes determining whether to use multi-segment transmission and mini-slot repetition for the configured granted PUSCH or for the grant-based PUSCH. The method also includes receiving multi-segment transmission and mini-slot repetition for the configured granted PUSCH or the grant-based PUSCH from the UE.

[0033] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that aims to develop globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems and devices.

[0034] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0035] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, and / or 12). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0036] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". UE may also be more generally referred to as a terminal device.

[0037] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "Node B", "eNB", "gNB" and / or "HeNB" may be used interchangeably herein to represent the more general term "base station". In addition, the term "base station" may be used to represent an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0038] It should be noted that as used herein, a "cell" may be any communication channel that is specified by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced) and all or a subset thereof, so that it is adopted by 3GPP as an authorized band (e.g., frequency band) for communication between eNBs and UEs. It should also be noted that in the E-UTRA and E-UTRAN general description, as used herein, a "cell" may be defined as "a combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.

[0039] "Configured cells" are those cells that the UE is aware of and is permitted by the eNB to transmit or receive information. "Configured cells" may be serving cells. The UE may receive system information and perform required measurements on all configured cells. "Configured cells" for a radio connection may include a primary cell and / or zero, one or more secondary cells. "Activated cells" are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells whose physical downlink control channel (PDCCH) the UE monitors, and in the case of downlink transmissions, those cells whose physical downlink shared channel (PDSCH) the UE decodes. "Deactivated cells" are those configured cells where the UE does not monitor the transmission PDCCH. It should be noted that "cells" may be described in different dimensions. For example, a "cell" may have time, space (e.g., geographic) and frequency characteristics.

[0040] The fifth generation (5G) cellular communications (also referred to as "new radio", "new radio access technology" or "NR" by 3GPP) envisions the use of time, frequency and / or space resources to enable services such as enhanced mobile broadband (eMBB) communications and ultra-reliable low latency communications (URLLC) services and massive machine type communications (MMTC). New radio (NR) base stations may be referred to as gNBs. gNBs may also be more generally referred to as base station devices.

[0041] Some configurations of the systems and methods described herein teach methods for URLLC transmission and / or retransmission management to meet delay and / or reliability requirements. Some requirements of URLLC relate to user (U)-plane delay and reliability. For URLLC, the target user plane delay is 0.5 milliseconds (ms) for both UL and DL. For X bytes within 1 millisecond (ms), the target reliability is 1-10 -5 .

[0042] These URLLC-specific constraints make it difficult to design hybrid automatic repeat request (HARQ) and retransmission mechanisms. For example, the receiver must respond with a quick acknowledgment (ACK) or negative acknowledgment (NACK) or uplink grant to meet the delay requirements, or the transmitter can retransmit immediately without waiting for ACK / NACK to improve reliability. On the other hand, authorization-based or authorization-free repetitions are supported to further improve reliability. How to terminate repetition is also an important issue. The system and method teach URLLC HARQ and / or retransmission design in different situations.

[0043] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0044] Figure 1 1 is a block diagram illustrating one specific implementation of one or more base stations (gNBs) 160 and one or more user equipment (UEs) 102 for enhanced uplink transmission. One or more UEs 102 use one or more antennas 122a-n to communicate with one or more gNBs 160. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more antennas 122a-n. gNB 160 communicates with UE 102 using one or more antennas 180a-n.

[0045] The UE 102 and the gNB 160 may communicate with each other using one or more channels 119, 121. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, the uplink channel 121 (e.g., PUSCH) may be used to transmit UL data (i.e., transport blocks), MAC PDUs, and / or UL-SCH (Uplink Shared Channel).

[0046] Here, the UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different physical uplink shared channel from PUSCH) may be defined to transmit URLLC data. For simplicity of description, the term "PUSCH" may represent any of the following: (1) only PUSCH (e.g., conventional PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not conventional PUSCH).

[0047] Also, for example, the uplink channel 121 may be used to transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI) and / or a scheduling request (SR). The HARQ-ACK may include information indicating a positive acknowledgement (ACK) or a negative acknowledgement (NACK) of DL data (i.e., a transport block), a medium access control protocol data unit (MAC PDU) and / or a DL-SCH (downlink shared channel).

[0048] The CSI may include information indicating the channel quality of the downlink. The SR may be used to request UL-SCH (Uplink Shared Channel) resources for new transmission and / or retransmission. That is, the SR may be used to request UL resources for transmitting UL data.

[0049] For example, one or more gNBs 160 may also use one or more downlink channels 119 to transmit information or data to one or more UEs 102. Examples of downlink channels 119 include PDCCH, PDSCH, etc. Other types of channels may be used. PDCCH may be used to transmit downlink control information (DCI).

[0050] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0051] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0052] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as the second UE-decoded signal 110) may include overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0053] Generally speaking, the UE operation module 124 can enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.

[0054] The UE scheduling module 126 may perform operations for mini-slot based repetition. In New Radio (NR), the UE 102 may support multiple types of UL transmissions (PUSCH transmissions). The UL transmissions may include grant-based UL transmissions (e.g., UL transmissions with grants, dynamic grants, PUSCH transmissions with grants, PUSCH transmissions scheduled by DCI (e.g., DCI format 0_0, DCI format 0_1)) and grant-free UL transmissions (e.g., UL transmissions without grants or configured grants, PUSCH transmissions with configured grants).

[0055] There may be two types of grant-free UL transmissions (eg, no grant, UL transmission with a configured grant, PUSCH transmission with a configured grant). One type of grant-free UL transmission is a configured grant type 1, and the other is a configured grant type 2.

[0056] For type 1 PUSCH transmission with a configured grant, the relevant parameters may be fully RRC configured (e.g., configured using RRC signaling). For example, parameters for resource allocation such as time-domain resource allocation (time-DomainOffset, timeDomainAllocation), frequency-domain resource allocation (frequencyDomainAllocation), modulation and coding scheme (MCS) (e.g., mcsAndTBS), antenna port value, bit value for DMRS sequence initialization, precoding information and number of layers, SRS resource indicator (provided by an-tennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator, respectively), frequency offset between two frequency jumps (frequencyHoppingOffset), etc. may be provided by an RRC message (rrc-ConfiguredUplinkGrant).

[0057] Activation (e.g., PDCCH, DCI activation) may not be used for type 1 configured grants. That is, for configured grant type 1, the uplink grant is provided through RRC and is stored as the configured uplink grant. Retransmissions of configured grant type 1 may be scheduled by PDCCH with a CRC scrambled by CS-RNTI (configured scheduling RNTI).

[0058] For type 2 PUSCH transmission with a configured grant, the relevant parameters follow the higher layer configuration (e.g., periodicity, number of repetitions, etc.) and the UL grant received on the DCI addressed to the CS-RNTI (PDCCH with CRC scrambled by the CS-RNTI, L1 activation and / or reactivation). That is, for a configured grant type 2, the uplink grant may be provided by the PDCCH and stored or cleared as the configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant.

[0059] Retransmissions of a configured grant type 2 may be scheduled by a PDCCH with a CRC scrambled by the CS-RNTI (e.g., with NDI=1). That is, retransmissions other than repeated configured uplink grants may use uplink grants addressed to the CS-RNTI. If higher layers do not deliver a transport block for transmission on resources allocated for uplink transmission without a grant, the UE 102 may not transmit anything on resources configured for PUSCH transmission with a configured grant.

[0060] Thus, in NR, the UE 102 may support multiple types of uplink transmissions without a grant (also referred to as grant-free (GF) uplink transmissions or GF transmissions or transmissions with a configured grant). A first type (Type 1) of GF transmissions may be UL data transmissions without a grant, which may be based solely on RRC (re)configuration without any L1 signaling. In a second type (Type 2) of GF transmissions, UL data transmissions without a grant are based on RRC configuration and L1 signaling for activation and / or deactivation of UL data transmissions without a grant. An example of an RRC configuration is shown in Listing 1.

[0061]

[0062]

[0063]

[0064]

[0065] List 1

[0066] PDCCH activation is required for Type 2. Listing 2 and Listing 3 show examples of DCI format 0_0 (eg, fallback DCI) and format 0_1, which can be used to activate a grant configured for Type 2, and / or retransmit a grant configured for Type 2 and / or a grant configured for Type 1.

[0067]

[0068] List 2

[0069]

[0070] List 3

[0071] For both type 1 and type 2 PUSCH transmissions with configured grants, when the UE 102 is configured with repK>1, the UE 102 may repeat the TB across repK consecutive slots, thereby applying the same symbol allocation in each slot. The parameter repK may be referred to as the configured number of transmission opportunities for the repetition of the TB (including the initial transmission). If the UE process for determining the slot configuration determines that the symbol of the slot allocated for PUSCH is a downlink symbol, then for a multi-slot PUSCH transmission, the transmission on that slot may be omitted.

[0072] For grant-based transmissions, PUSCH transmissions are scheduled by DCI (e.g., DCI format 0_0 and DCI format 0_1 ​​shown above). PUSCH may be allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with a CRC scrambled by C-RNTI, new-RNTI (e.g., first RNTI), TC-RNTI, or SP-CSI-RNTI. In the specification, new-RNTI may be referred to as MCS-C-RNTI. Some UE-specific PUSCH parameters may be configured by RRC (i.e., using RRC messages (RRC signaling)). An example of an RRC configuration is shown in Listing 4. For example, the pusch-AggregationFactor in PUSCH-Config indicates the number of repetitions of the data. When UE 102 is configured with pusch-AggregationFactor>1, the same symbol allocation may be applied across pusch-AggregationFactor consecutive time slots, and PUSCH may be limited to a single transport layer. The UE 102 may repeat the transport blocks (TBs) across pusch-AggregationFactor consecutive time slots, thereby applying the same symbol allocation in each time slot. If the UE process for determining the time slot configuration determines that the symbols of the time slot allocated for PUSCH are downlink symbols, then for multi-slot PUSCH transmission, the transmission on this time slot may be omitted.

[0073] For PUSCH retransmissions scheduled by PDCCH with CRC scrambled by CS-RNTI with NDI=1, the parameters in pusch-Config may be applied to PUSCH transmissions, except p0-NominalWithoutGrant, p0-PUSCH-Alpha, powerControl-LoopToUse, pathlossReferenceIndex, mcs-Table, mcs-TableTransformPrecoder and transformPrecoder which may be provided in configuredGrantConfig.

[0074] For PUSCH retransmissions scheduled by PDCCH with CRC scrambled by CS-RNTI with new data indicator (NDI) equal to 1 (i.e., NDI=1), if UE 102 is configured with pusch-AggregationFactor, the same symbol allocation may be applied across pusch-AggregationFactor consecutive slots, and PUSCH may be limited to a single transport layer. UE 102 may repeat TBs across pusch-AggregationFactor consecutive slots, thereby applying the same symbol allocation in each slot.

[0075]

[0076]

[0077]

[0078]

[0079] List 4

[0080] As described above, for both unlicensed transmission and authorized-based transmission, if repetition is configured for UE 102, for repetition, consecutive time slots and the same time domain resource allocation (e.g., starting symbol and / or length) may be applied to each time slot, which may be referred to as time slot-based repetition in this article. In another design, two or more PUSCH repetitions may be scheduled and / or configured in one time slot, or two or more PUSCH repetitions may be scheduled and / or configured across time slot boundaries in consecutive available time slots. In yet another design, two or more PUSCH repetitions in consecutive available time slots may have one repetition in each time slot where the starting symbol and / or duration may be different. Two or more PUSCH repetitions in one time slot or across time slot boundaries in consecutive available time slots, and / or two or more PUSCH repetitions in consecutive available time slots (where the starting symbol and / or duration may be different) may be referred to as micro-slot-based repetitions.

[0081] That is, for slot-based repetition, only one transmission opportunity may be scheduled (e.g., allocated) within a slot (e.g., 14 OFDM symbols and / or 14 SC-FDMA symbols). Here, one transmission opportunity may correspond to a PUSCH resource to be applied to PUSCH transmission. And, the PUSCH resource (e.g., the one transmission opportunity) may be identified (e.g., indicated, defined) by using time domain resource allocation. For example, the PUSCH resource (e.g., the one transmission opportunity) may be identified by using a starting symbol and / or a length (i.e., a starting symbol and / or a length of the PUSCH resource). For example, for slot-based repetition, the same transmission opportunity may be used in a slot, wherein the same transmission opportunity may be applied for each consecutive slot.

[0082] Additionally or alternatively, for repetition based on mini-slots, two or more transmission opportunities may be scheduled (e.g., allocated) within a time slot. Here, each transmission opportunity may correspond to a PUSCH resource to be applied to a PUSCH transmission. For example, two or more time domain resource allocations (two or more values ​​of the start symbol and / or two or more values ​​of the length) are used to schedule PUSCH resources (e.g., transmission opportunities) in a time slot. And, each PUSCH resource (e.g., each transmission opportunity) may be identified by using each time domain resource allocation. For example, a PUSCH resource (e.g., each transmission opportunity) may be identified by using each value of the start symbol and / or each value of the length. For example, for repetition based on mini-slots, the two or more transmission opportunities may be used in a time slot, wherein each transmission opportunity in the two or more transmission opportunities may be identified by using each start symbol and / or each length. That is, different start symbols and / or different lengths may be applied to two or more transmission opportunities in a time slot.

[0083] Additionally or alternatively, for repetition based on mini-slots, each transmission opportunity identified by using each start symbol and / or each length may be applied for each time slot (e.g., each consecutive time slot). That is, different start symbols and / or different lengths may be applied for two or more transmission opportunities in two or more time slots.

[0084] In one example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions in one time slot, the next repetition immediately after completing one of the repetitions of the TB (including the initial transmission) in the time slot can use the remaining available symbols in the time slot. That is, in the time slot, the transmission opportunity (e.g., the remaining available symbol) can be used for repetition (e.g., the next repetition in the time slot). As described above, the available symbols (e.g., the transmission opportunity) can be defined as L_r consecutive uplink symbols (i.e., consecutive symbols) starting from the symbol S_r (i.e., the starting symbol), where the symbol S_r can be defined as the first uplink symbol (or the first uplink symbol of the first L_r consecutive uplink symbols in the time slot), and L_r is defined as the length of the repetition or initial transmission (e.g., symbol). For example, for a repeated second transmission in a time slot, the symbol S_r may be defined as the first uplink symbol after the repeated first transmission in the time slot is performed (or the first uplink symbol among the first L_r consecutive uplink symbols after the repeated first transmission in the time slot is performed, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10). If there are no L_r consecutive uplink symbols in the time slot according to the UE process for determining the time slot configuration (e.g., after the repeated first transmission in the time slot is performed), the next repetition (e.g., the repeated second transmission in the time slot) may be skipped in the time slot (e.g., discarded in the time slot, not performed in the time slot), or the next repetition in the time slot may be omitted (e.g., omitted in the time slot).

[0085] That is, the gNB 160 may configure information for configuring the execution of mini-slot-based repetition by using an RRC message. And, in the case of performing mini-slot-based repetition, if there is no transmission opportunity for transmission in the time slot, the UE 102 may skip (e.g., discard, not perform and / or omit) the transmission. Here, as described above, the transmission opportunity (e.g., each transmission opportunity in the time slot) may be identified (e.g., indicated by the gNB 160 using DCI formats 0_0 and / or 0_1) by using time domain resource allocation (e.g., each time domain resource allocation (e.g., each start symbol and / or each length)). That is, the UE 102 may perform repeated transmissions (e.g., repeated first transmissions, transmissions in repetitions) on the transmission opportunities in the time slot (i.e., if the transmission opportunities are identified by using time domain resource allocations). In addition, if there is no transmission opportunity (i.e., if there is no transmission opportunity identified based on the time domain resource allocation), the UE 102 may skip repeated transmissions (e.g., repeated second transmissions, transmissions in repetitions) in the time slot.

[0086] In yet another design, available symbols (e.g., transmission opportunities) may be limited to L_r consecutive symbols (uplink symbols and / or flexible symbols) starting from symbol S_r, where symbol S_r is the first symbol (uplink symbol and / or flexible symbol) after a repetition in a slot (or the first symbol (uplink symbol and / or flexible symbol) among the first L_r consecutive symbols (uplink symbols and / or flexible symbols) after a repetition in a slot, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_r is the length of a repetition or initial transmission. If there are no L_r consecutive symbols (uplink symbols and / or flexible symbols) after a repetition in a slot according to a UE process for determining a slot configuration, the next repetition may skip the slot, or the next repetition in the slot may be omitted. That is, L_r consecutive symbols may include uplink symbols and / or flexible symbols.

[0087] In yet another example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions in one time slot, and different repetitions may use different lengths (number of symbols), then the next repetition immediately following one of the repetitions (including initial transmission) of the TB in the time slot may use the remaining available symbols in the time slot. Available symbols (e.g., transmission opportunities) may be defined as L_rd consecutive uplink symbols starting from symbol S_rd, where symbol S_rd is the first uplink symbol after the repetition in the time slot (or the first uplink symbol in the first L_rd consecutive uplink symbols after the repetition in the time slot, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_rd may be a different length compared to the length of the repetition or initial transmission (i.e., L_r). L_rd may be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd may be determined by L_r (e.g., L_rd=L_r-L_delta and L_delta may be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd may be determined by the slot configuration (e.g., L_rd is the number of consecutive uplink symbols remaining in the slot). If there are not L_rd consecutive uplink symbols in the slot after a repetition according to the UE process for determining the slot configuration, the next repetition may skip the slot, or the next repetition in the slot may be omitted.

[0088] In yet another design, available symbols (e.g., transmission opportunities) may be limited to L_rd consecutive symbols (uplink symbols and / or flexible symbols) starting from symbol S_rd, where symbol S_rd is the first symbol (uplink symbol and / or flexible symbol) after a repetition in a time slot (or the first symbol (uplink symbol and / or flexible symbol) among the first L_rd consecutive symbols (uplink symbols and / or flexible symbols) after a repetition in a time slot, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_rd may be a different length than the length of the repetition or initial transmission (i.e., L_r). L_rd may be configured by RRC or indicated by L1 / L2 signaling or fixed by a specification. L_rd may be determined by L_r (e.g., L_rd=L_r-L_delta and L_delta may be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd may be determined by the slot configuration (e.g., L_rd may be the number of consecutive uplink symbols and / or flexible symbols remaining in the slot). If there are no L_rd consecutive symbols (uplink symbols and / or flexible symbols) in the slot after a repetition according to the UE process for determining the slot configuration, the immediately next repetition may skip the slot, or the immediately next repetition in the slot may be omitted.

[0089] When the UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions to be performed in one time slot, the two or more PUSCH repetitions may or may not share a demodulation reference signal (DMRS (e.g., a DMRS associated with a PUSCH transmission)). Whether the two or more PUSCH repetitions share the DMRS may be configured by RRC or indicated by L1 / L2 signaling. For example, if the UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions to be performed in one time slot, and the two or more PUSCH repetitions may share the DMRS, the DMRS of the first repetition in the time slot may be reused by subsequent repetitions in the time slot. That is, the gNB 160 may transmit information indicating whether the repetitions in a time slot (and / or across time slots) share the DMRS associated with a PUSCH transmission by using an RRC message and / or a DCI format (e.g., DCI format 0_0 and / or 0_1).

[0090] For repetitions in consecutive time slots, the same starting symbol may or may not be applied in each time slot. That is, after completing one or more repetitions of a TB in a time slot, the repetition in the next time slot may start at a symbol that is different from the starting symbol of the repetition in the previous time slot, the starting symbol of the initial transmission, the starting symbol indicated by the PDCCH (e.g., the grant activation of the Class 2 configuration), or the starting symbol configured by the RRC (e.g., the grant configuration of the Class 1 configuration).

[0091] In one example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow PUSCH repetitions in consecutive time slots to start at different symbols, and the length of the repetition should remain unchanged, then after one or more repetitions of the TB in the time slot are completed (including the initial transmission), the next repetition in the consecutive time slot can start at the symbol S_d in the consecutive time slot. The starting symbol S_d can be defined as the first uplink symbol in the consecutive time slot according to the UE process for determining the time slot configuration, or the first symbol in the available symbols for repetition in the consecutive time slot (or the first symbol in the first L_r consecutive uplink symbols in the consecutive time slot, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling). The available symbols (e.g., transmission opportunities) for repetition in consecutive time slots may be limited to L_r consecutive uplink symbols in consecutive time slots, where L_r is the length of the repetition or initial transmission in the previous time slot or the length configured by RRC (e.g., grant configuration of Class 1 configuration) or the length indicated by PDCCH (e.g., grant activation of Class 2 configuration). If there are no L_r consecutive uplink symbols after repetition in the consecutive time slot according to the UE process for determining the time slot configuration, the next repetition in the consecutive time slot may skip the time slot, or the next repetition in the connected time slot may be omitted.

[0092] In yet another design, the start symbol S_d may be defined as the first uplink symbol and / or flexible symbol in consecutive time slots, or the first symbol among available symbols for repetition in consecutive time slots (or the first symbol among the first L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling) according to a UE process for determining time slot configuration. Available symbols (e.g., transmission opportunities) in consecutive time slots may be defined as L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, where L_r is the length of a repetition or initial transmission in a previous time slot, or a length configured by RRC (e.g., grant configuration of a Class 1 configuration) or a length indicated by PDCCH (e.g., grant activation of a Class 2 configuration). If there are no L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots according to the UE process for determining time slot configuration, the next repetition in the consecutive time slot may skip the time slot, or the next repetition in the connected time slot may be omitted.

[0093] In yet another example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow PUSCH repetitions in consecutive time slots to start at different symbols, and the lengths of the repetitions may be different, then after one or more repetitions of the repetitions of the TB (including the initial transmission) are completed in the time slot, the next repetition in the consecutive time slot may start at the symbol S_d in the consecutive time slot. The starting symbol S_d may be defined as the first uplink symbol in the consecutive time slot, or the first symbol in the available symbols for repetition in the consecutive time slot (or the first symbol in the first L_rd consecutive uplink symbols in the consecutive time slot, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling) according to the UE process for determining the time slot configuration. The available symbols for repetition in consecutive time slots (e.g., transmission opportunities) may be limited to L_rd consecutive uplink symbols in consecutive time slots, where L_rd may be a different length compared to the length indicated by L_r, which is the length of the repetition or initial transmission in the previous time slot or the length configured by RRC (e.g., grant configuration of Class 1 configuration) or the length indicated by PDCCH (e.g., grant activation of Class 2 configuration). L_rd may be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd may be determined by L_r (e.g., L_rd=L_r-L_delta and L_delta may be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd may be determined by the time slot configuration (e.g., L_rd is the number of consecutive uplink symbols in consecutive time slots, or the maximum number of consecutive uplink symbols in consecutive time slots). If there are no L_rd consecutive uplink symbols in consecutive time slots according to the UE procedure for determining time slot configuration, the next repetition in the consecutive time slot may skip the time slot, or the next repetition in the connected time slot may be omitted.

[0094] In yet another design, the start symbol S_d may be defined as the first uplink symbol and / or flexible symbol in consecutive time slots, or the first symbol among available symbols for repetition in consecutive time slots (or the first symbol among the first L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling) according to a UE process for determining a time slot configuration. Available symbols (e.g., transmission opportunities) in consecutive time slots may be defined as L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, where L_rd may be a different length compared to a length indicated by L_r, which is a length of a repetition or initial transmission in a previous time slot or a length configured by RRC (e.g., a grant configuration of a Class 1 configuration) or a length indicated by PDCCH (e.g., a grant activation of a Class 2 configuration). L_rd may be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd may be determined by L_r, for example, L_rd=L_r-L_delta and L_delta may be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0). L_rd may be determined by the slot configuration (e.g., L_rd is the number of consecutive uplink and / or flexible symbols in consecutive slots, or the maximum number of consecutive uplink and / or flexible symbols in consecutive slots). If there are no L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive slots according to the UE process for determining the slot configuration, the next repetition in the consecutive slot may skip the slot, or the next repetition in the connected slot may be omitted.

[0095] The PUSCH preparation time N_2 [symbol] may be defined as the minimum time taken by UE 102 to prepare PUSCH for a TB. N_2 may be determined by parameters and / or UE capabilities. N_2 may be defined in the specification and / or configured by RRC and / or indicated by L1 / L2 signaling. The repeated PUSCH preparation time for non-initial transmission may be the same as or different from the PUSCH preparation time for initial transmission. The repeated PUSCH preparation time for non-initial transmission may be represented by N_2r. N_2r may be determined by parameters and / or UE capabilities. N_2r may be defined in the specification and / or configured by RRC and / or indicated by L1 / L2 signaling.

[0096] If UE 102 is configured by higher layers to transmit PUSCH repetitions (which may not be initial transmissions) in a group of symbols in a time slot as described above, and UE 102 detects DCI format 1_0, DCI format 1_1, or DCI format 0_1 ​​indicating that UE 102 receives CSI-RS or PDSCH in a subset of symbols from the group of symbols, then UE 102 does not expect to cancel transmissions in certain symbols from the group of symbols, which occur after a number of symbols less than the PUSCH preparation time for repetitions as described above relative to the last symbol of the control resource set in which UE 102 detects DCI format 1_0, DCI format 1_1, or DCI format 0_1, or UE 102 cancels PUSCH repetitions in the remaining symbols in the group of symbols.

[0097] If UE 102 is scheduled by DCI to transmit PUSCH on multiple time slots and a different starting symbol and / or length may be applied for each repetition as described above, and if higher layer parameters (when provided to UE 102) indicate that for a time slot from the multiple time slots, at least one symbol in a set of symbols in which UE 102 is scheduled for PUSCH transmission in the time slot is a downlink symbol, then UE 102 does not transmit PUSCH in the time slot.

[0098] The slot format includes downlink symbols, uplink symbols, and flexible symbols. The slot format may be indicated by an RRC message (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) and / or dynamic signaling (e.g., slot format indicator (SFI), dynamic SFI, DCI format 2_0, information included in DCI format 2_0). The downlink symbols, uplink symbols, and flexible symbols configured by using the RRC message may be named semi-static UL symbols, semi-static DL symbols, and semi-static flexible symbols, respectively. That is, the gNB 160 may transmit information for configuring the semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols by using the RRC message. The UE 102 may determine the semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols based on the information included in the RRC message. The downlink symbols, uplink symbols, and flexible symbols indicated by using dynamic signaling may be named dynamic UL symbols, dynamic DL symbols, and dynamic flexible symbols, respectively. That is, the gNB 160 may transmit information indicating a dynamic UL symbol, a dynamic DL symbol, and / or a dynamic flexible symbol by using dynamic signaling. The UE 102 may determine the dynamic UL symbol, the dynamic DL symbol, and / or the dynamic flexible symbol based on the information included in the dynamic signaling.

[0099] For a group of symbols indicated to UE 102 as a flexible time slot by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated, when provided to UE 102), or when higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are not provided to UE 102, and when UE 102 detects DCI format 2_0 that provides a format for the time slot using a time slot format value (e.g., other than 255), if UE 102 is configured by higher layers to transmit PUSCH repetitions in a group of symbols of the time slot as described above, UE 102 can only transmit PUSCH repetitions in the time slot if the SFI index field value in DCI format 2_0 indicates a group of symbols of the time slot as uplink.

[0100] If a set of symbols for a time slot includes symbols corresponding to any repetitions of a PUSCH transmission as described above, the UE 102 may not expect to detect in DCI format 2_0 that the set of symbols for the time slot is indicated as a downlink or flexible SFI index field value.

[0101] If UE 102 is configured by higher layers to transmit PUSCH repetitions in a group of symbols of a time slot as described above, and UE 102 detects DCI format 2_0 with a time slot format value (e.g., other than 255) indicating a time slot format when a symbol subset of the group of symbols is downlink or flexible, or UE 102 detects DCI format 1_0, DCI format 1_1, or DCI format 0_1 ​​indicating that UE 102 receives CSI-RS or PDSCH in a symbol subset from the group of symbols, then UE 102 may not desire to cancel transmissions in certain symbols from the group of symbols, which occur relative to the last symbol of the CORESET in which UE 102 detects DCI format 2_0, DCI format 1_0, DCI format 1_1, or DCI format 0_1 ​​after a number of symbols less than the PUSCH preparation time for repetition as described above, or UE 102 cancels PUSCH repetitions in the remaining symbols in the group of symbols.

[0102] For a set of symbols of a time slot indicated as being flexible by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated, when provided to UE 102), or when higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are not provided to UE 102, and in the event that UE 102 does not detect DCI format 2_0 that provides a time slot format for the time slot, if UE 102 is configured by higher layers to transmit PUSCH repetitions in a set of symbols of the time slot as described above, then UE 102 may not transmit PUSCH repetitions in some symbols of the set of symbols of the time slot, if any, that start after the last symbol of a control resource set of DCI format 2_0 in which UE 102 is configured to monitor PDCCH and before a symbol that is a number of symbols equal to the PUSCH preparation time N_2r of the corresponding PUSCH timing capability, or the UE 102 It may not be desirable to cancel PUSCH repetitions in certain symbols from the set of symbols in a time slot, if any, that start after the last symbol of a CORESET of DCI format 2_0 in which the UE is configured to monitor PDCCH and before a number of symbols that is equal to the PUSCH preparation time N_2r of the corresponding PUSCH timing capability.

[0103] As described above, there may be two types of PUSCH repetitions. One may be referred to as slot-based repetition, which means that the repetitions may use consecutive slots and the same time domain resource allocation (e.g., starting symbol and / or length) may be applied to each slot. The other may be referred to as mini-slot-based repetition, which means that multiple PUSCH repetitions may be in one slot and / or PUSCH repetitions in consecutive available slots may use different starting symbols and / or duration / length.

[0104] This document describes whether to apply slot-based repetition or mini-slot-based repetition and / or how to switch between slot-based repetition and mini-slot-based repetition.

[0105] In one design, whether slot-based repetition or mini-slot-based repetition is applied may be explicitly configured by RRC (i.e., by using RRC messages (RRC signaling)). For example, for grant-free PUSCH transmission (e.g., a grant configured in type 1 or a grant configured in type 2), if the RRC parameter mini-slot-repetition-enabler in the configured grant configuration (e.g., Configured-GrantConfig) is configured or indicated as true, mini-slot-based repetition may be applied. If the RRC parameter mini-slot-repetition-enabler in the configured grant configuration (e.g., ConfiguredGrantConfig) is not configured or is indicated as false, slot-based repetition may be applied. For grant-based PUSCH transmissions (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if the RRC parameter mini-slot-repetition-enabler in the PUSCH configuration (e.g., PUSCH-Config) is configured or indicated as true, mini-slot based repetition may be applied. If the RRC parameter mini-slot-repetition-enabler in the PUSCH configuration (e.g., PUSCH-Config) is not configured or it is indicated as false, slot-based repetition may be applied. For retransmissions of grant-free transmissions (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI with NDI=1), whether slot-based repetition or mini-slot-based repetition is applied may follow the RRC parameters in the grant configuration configured as above, or follow the RRC parameters in the PUSCH configuration as above.

[0106] In yet another design, timeslot-based repetition and mini-slot-based repetition may use different parameters (also referred to herein as repetition parameters) to indicate the number of repetitions. For example, for unlicensed PUSCH transmission (e.g., a Class 1 configured grant or a Class 2 configured grant), if the RRC parameter repK-new (indicating the number of repetitions for mini-slot-based repetition) is configured and / or indicated as being greater than 1, mini-slot-based repetition may be applied, and the RRC parameter repK-new may be different from the repK (indicating the number of repetitions for timeslot-based repetition) in the configured grant configuration (e.g., ConfiguredGrantConfig). If both repK-new and repK are configured, repK-new may overwrite repK, and / or mini-slot-based repetition may be applied. If both repK-new and repK are configured, repK may overwrite repK-new, and / or timeslot-based repetition may be applied.

[0107] For grant-based PUSCH transmissions (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with a CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), mini-slot-based repetition may be applied if the RRC parameter pusch-AggregationFactor-new (indicating the number of repetitions for mini-slot-based repetition) is configured and / or indicated as greater than 1, which RRC parameter pusch-AggregationFactor-new may be different from the pusch-AggregationFactor (indicating the number of repetitions for slot-based repetition) in the PUSCH configuration (e.g., PUSCH-Config). If both pusch-AggregationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor-new may override pusch-AggregationFactor and / or mini-slot-based repetition may be applied. In yet another example, if both pusch-Aggre-gationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor may overwrite pusch-AggregationFactor-new, and / or slot-based repetition may be applied. For retransmissions of ungranted transmissions (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI with NDI=1), whether slot-based repetition or mini-slot-based repetition is applied may follow the RRC parameters in the grant configuration configured above, or may follow the RRC parameters in the PUSCH configuration configured above.

[0108] In yet another design, whether slot-based repetition or mini-slot-based repetition is applied may depend on a periodicity parameter. For example, for grant-free PUSCH transmission (e.g., a Class 1 configured grant or a Class 2 configured grant), if the RRC parameter periodicity in the configured grant configuration (e.g., Configured-GrantConfig) is greater than (or less than) a certain value (e.g., a single predetermined value and / or threshold), mini-slot-based repetition may be applied. If the RRC parameter periodicity in the configured grant configuration (e.g., ConfiguredGrantConfig) is less than (or greater than) a certain value (e.g., a single predetermined value and / or threshold), slot-based repetition may be applied.

[0109] In yet another design, whether to apply slot-based repetition or mini-slot-based repetition may depend on a modulation and coding scheme (MCS) table. For example, for ungranted PUSCH transmissions (e.g., grants configured in class 1 or grants configured in class 2) and / or retransmissions of grant-free transmissions (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI with NDI=1), if a low spectral efficiency (SE) MCS table is configured (e.g., RRC parameter mcs-Table or mcs-TableTransformPrecoder in a configured grant configuration (e.g., Config-uredGrantConfig) is configured as qam64LowSE), mini-slot-based repetition may be applied, otherwise, slot-based repetition may be applied. In yet another design, if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the configured grant configuration (e.g., Configured-GrantConfig) is configured as qam64LowSE), then slot-based repetition may be applied, otherwise, mini-slot-based repetition may be applied. For grant-based PUSCH transmission (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with a CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), then mini-slot-based repetition may be applied, otherwise, slot-based repetition may be applied. In another design, if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), time slot based repetition may be applied, otherwise, mini-slot based repetition may be applied.

[0110] In yet another design, whether to apply slot-based repetition or mini-slot-based repetition may depend on a radio network temporary identifier (RNTI). For example, for PUSCH transmissions scheduled by DCI format 0_0 / 0_1 with a CRC scrambled by MCS-C-RNTI, and repetitions are configured, mini-slot-based repetition (or slot-based repetition) may always be applied. In yet another example, a new RNTI (e.g., REP-C-RNTI) may be introduced for mini-slot-based repetition. That is, for PUSCH transmissions scheduled by a DCI format with a CRC scrambled by REP-C-RNTI, and repetitions are configured, mini-slot-based repetition may always be applied.

[0111] In yet another design, whether to apply time slot-based repetition or mini-slot-based repetition may depend on the downlink control information (DCI) format. For example, mini-slot-based repetition may be applied only when non-fallback DCI (e.g., DCI format 0_1) is used. In yet another example, a new DCI format may be introduced for mini-slot-based repetition. That is, for PUSCH transmissions scheduled by the new DCI format and / or unlicensed transmissions activated by the new DCI format, when repetition is enabled, mini-slot-based repetition is enabled. The new DCI format may include an indication for mini-slot repetition and / or a parameter indicating the number of mini-slot-based repetitions.

[0112] In yet another design, whether to apply repetition based on time slots or repetition based on mini-time slots may depend on the time slot configuration. For example, if the time slot configuration period configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied. In yet another example, if the number of time slots with only downlink symbols configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied. In yet another example, if the number of time slots with only uplink symbols configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied. In yet another example, if the number of downlink symbols configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied. In yet another example, if the number of uplink symbols configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied. In yet another example, if the number of uplink symbols configured by RRC is greater than (or less than) a threshold, repetition based on mini-time slots may be applied, otherwise, repetition based on time slots may be applied.

[0113] When mini-slot-based repetition is configured and / or enabled as described above, fallback behavior may be supported in some cases (e.g., even if mini-slot-based repetition is configured / enabled, slot-based repetition may be applied (e.g., for certain conditions)). In one design, if UE 102 detects fallback DCI (e.g., DCI format 0_0) in a CSS (e.g., and / or a CSS associated with CORESET#0), UE 102 may perform slot-based repetition as described above even if mini-slot-based repetition is configured / enabled. For example, if mini-slot-based repetition is configured by RRC (i.e., RRC message (RRC signaling)), if UE 102 detects fallback DCI (e.g., DCI format 0_0) in a CSS (e.g., and / or a CSS associated with CORESET#0), UE 102 may perform slot-based repetition. If both repK-new (pusch-AggregationFactor-new) and repK (pusch-AggregationFactor) are configured, then in the event that UE 102 detects a fallback DCI (e.g., DCI format 0_0) in a CSS (e.g., and / or a CSS associated with CORESET#0), UE 102 may perform slot-based repetition and may apply the number of repetitions repK (pusch-AggregationFactor). In yet another design, UE 102 may perform slot-based repetition based on the RNTI used to scramble the CRC attached to the DCI. For example, if a new RNTI (e.g., REP-C-RNTI) is configured for mini-slot-based repetition, and if UE 102 detects a DCI with a CRC scrambled by a different RNTI (e.g., C-RNTI), UE 102 may perform slot-based repetition.

[0114] That is, in the case where DCI format 0_0 is detected in the CSS, slot-based repetition may be used (e.g., by UE 102). For example, even if mini-slot-based repetition is configured to be enabled, in the case where DCI format 0_0 is detected in the CSS, UE 102 may perform slot-based repetition. That is, if mini-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the USS, UE 102 may perform mini-slot-based repetition.

[0115] Additionally or alternatively, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0 (i.e., a CORESET with index “0”), slot-based repetition may be used. For example, even if mini-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0 (e.g., a search space (e.g., CSS) associated with CORESET #0), the UE 102 may perform slot-based repetition. That is, if mini-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than in CORESET #0, the UE 102 may perform mini-slot-based repetition.

[0116] Additionally or alternatively, slot-based repetition may be used in the event that a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set #0 (i.e., the search space set with index "0"). For example, even if mini-slot-based repetition is configured to be enabled, UE 102 may perform slot-based repetition in the event that a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set #0. That is, if mini-slot-based repetition is configured to be enabled, UE 102 may perform mini-slot-based repetition in the event that a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a search space set other than search space set #0.

[0117] For configured grants and / or grant-based PUSCH transmissions, multi-segment transmissions and mini-slot repetitions may also be supported. Mini-slot repetitions and / or multi-segment transmissions may be enabled and / or configured jointly or individually for each configured grant and / or each PUSCH configuration.

[0118] For example, one UL grant for dynamic PUSCH and one configured grant for granted PUSCH configured via Option A may be used to support one or more actual PUSCH repetitions in a slot, or two or more actual PUSCH repetitions across slot boundaries in consecutive available slots. The number of repetitions signaled by gNB 160 (dynamically signaled, such as indicated by DCI, or semi-statically signaled, such as configured by RRC, or a combination thereof) may represent a "nominal" number of repetitions. The actual number of repetitions may be greater than the nominal number. The time domain resource allocation (TDRA) field in the DCI or the TDRA parameter in a grant of a Type 1 configuration indicates the resources used for the first "nominal" repetition. The time domain resources for the remaining repetitions are derived based on at least the resources used for the first repetition and the UL / DL direction of the symbol. If the "nominal" repetition (transmission opportunity) crosses a time slot boundary or a DL / UL switching point, the "nominal" repetition (transmission opportunity) may be split into multiple PUSCH repetitions (transmission opportunities), with one PUSCH repetition (transmission opportunity) in each UL cycle in the time slot (this behavior may be referred to as segmentation here). In the case where multiple configurations of configured authorizations and / or multiple configurations of PUSCH transmissions are supported, option A may be configured and / or enabled individually or collectively for each configured authorization configuration and / or each PUSCH transmission configuration. One or more new tables of TDRA may be introduced for option A. The new table of TDRA may be fixed by a specification (e.g., a default table). The new table of TDRA may be RRC configured. The new table of TDRA may generally be configured for multiple configurations of configured authorizations and / or multiple configurations of PUSCH transmissions. The new table of TDRA may be configured and / or enabled individually for each configured authorization configuration and / or each PUSCH transmission configuration. How to determine the table of TDRA may follow the same process as the determination of the other parameters described above.

[0119] In yet another example, one or more PUSCH repetitions in a time slot are supported using a UL grant for dynamic PUSCH and a configured grant configuration for a grant PUSCH configured by option B, or two or more PUSCH repetitions across time slot boundaries in consecutive available time slots. The time domain resource allocation (TDRA) field in the DCI or the TDRA parameter in the grant configured by type 1 indicates an entry in a table configured by a high layer. The number of repetitions, the starting symbol of each repetition, the length of each repetition, and the mapping of repetitions to time slots can be obtained from each entry in the table. More than one repetition can be mapped to a time slot. The resource allocation for each repetition is included in a time slot. The repetition of each transmission is included in a UL cycle in the time slot. In the case where multiple configurations of the configured grant and / or multiple configurations of PUSCH transmission are supported, option B can be configured and / or enabled separately or jointly for each configured grant configuration and / or each PUSCH transmission configuration. One or more new tables of TDRA can be introduced for option B. The new table of TDRA can be fixed by a specification (e.g., a default table). The new table of TDRA can be RRC configured. The new table of TDRA can generally be configured for multiple configurations of the configured grant and / or multiple configurations of PUSCH transmission. The new table of TDRA can be configured and / or enabled separately for each configured grant configuration and / or each PUSCH transmission configuration. How to determine the table of TDRA can follow the same process as the other parameter determinations described above.

[0120] Option A and Option B may be supported simultaneously. For example, Option A may be enabled and / or configured for one of the plurality of configurations, while Option B may be enabled and / or configured for another of the plurality of configurations. In yet another example, Option A (or Option B) may be enabled and / or configured for a configured grant, while Option B (or Option A) may be enabled and / or configured for grant-based PUSCH. In yet another example, Option A (or Option B) may be enabled and / or configured for a configured Grant Type 1, while Option B (or Option A) may be enabled and / or configured for a configured Grant Type 2.

[0121] Frequency hopping may be supported for both Option A and Option B. For Option A, dynamic indication of the nominal number of repetitions in DCI-scheduled dynamic PUSCH is supported for PUSCH enhancement. The dynamic indication may be enabled or disabled by the gNB.

[0122] Option A can be used with the following updates: The Time Domain Resource Allocation (TDRA) field in the DCI or the TDRA parameter in the grant of a Type 1 configuration indicates the resources used for the first "nominal" repetition. In addition, the detailed interaction with the process of UL / DL direction determination is described below.

[0123] Four cases are considered here. The first case (Case 1) is for a dynamic grant (DG) PUSCH (e.g., DGPUSCH transmission). That is, UL transmission (e.g., PUSCH transmission) (including repetitions) can be dynamically scheduled by an uplink grant in a DCI (e.g., a DCI format for uplink with a CRC scrambled by a C-RNTI). The second case (Case 2) is for a configured grant (CG) PUSCH (e.g., a CG PUSCH transmission, including repetitions) other than the first Class 2 CG PUSCH transmission (including all repetitions) activated by a UL grant (e.g., the first PUSCH transmission corresponding to a Class 2 CG). The third case (Case 3) is for the first Class 2 CG PUSCH transmission (including all repetitions) activated by a UL grant. The fourth case (Case 4) is for a PUSCH retransmission corresponding to a configured grant. That is, PUSCH retransmissions (including repetitions) are scheduled by a PDCCH with a CRC scrambled by a CS-RNTI with NDI=1. In different situations, mini-slot repetition and / or multi-segment transmission may have different interactions with the UL / DL direction determination process.

[0124] For DG PUSCH transmission (case 1), how to handle the interaction of enhanced PUSCH (including mini-slot repetition and / or multi-segment transmission) with the DL / UL direction may depend on whether the configuration on the dynamic SFI is configured. Here, the configuration on the dynamic SFI may include information indicating that monitoring of DCI format 2_0 (as described above) is configured to the UE 102. That is, for DG PUSCH transmission, based on whether the configuration on the dynamic SFI is configured, the UE 102 may determine the interaction with the process in the UL / DL direction.

[0125] For DG PUSCH transmission, for the case where dynamic SFI is not configured (e.g., in this case) (case 1-1), semi-static flexible symbols may be used for PUSCH transmission (e.g., DG PUSCH transmission). Segmentation may occur around semi-static DL symbols. That is, the PUSCH may be divided into two or more PUSCHs around the semi-static DL symbols (e.g., based on the position of the semi-static DL symbols (e.g., time domain position)). The processing method here may be referred to as option 1-1. That is, option 1-1 may include that PUSCH transmission may be performed on semi-static flexible symbols. Additionally or alternatively, option 1-1 may include that segmentation of the PUSCH occurs around the semi-static DL symbols used for PUSCH transmission.

[0126] Here, the semi-static UL symbol, the semi-static DL symbol, and / or the semi-static flexible symbol may be configured by using an RRC message. That is, the gNB 160 may transmit information for configuring the semi-static UL symbol, the semi-static DL symbol, and / or the semi-static flexible symbol by using an RRC message. The UE 102 may determine the semi-static UL symbol, the semi-static DL symbol, and / or the semi-static flexible symbol based on the information included in the RRC message.

[0127] For DG PUSCH transmission, for the case where dynamic SFI is configured (e.g., in this case) (case 1-2), the behavior (e.g., interaction with the process in the UL / DL direction) may not depend on (e.g., may be independent of) the dynamic SFI, which may be referred to as option 1-2-1. For example, for option 1-2-1-1, the same processing method as option 1-1 may be applied. That is, semi-static flexible symbols are used for PUSCH (e.g., DG PUSCH transmission). Segmentation occurs around the semi-static DL symbols. However, a conflict may occur between the dynamic SFI (e.g., DL symbols indicated by the dynamic SFI (e.g., information included in DCI format 2_0)) and symbols indicated by information included in the RRC message for PUSCH transmission (e.g., flexible symbols), which may or may not be considered an error case. In one design (option 1-2-1-1a), the UE does not expect any semi-static flexible symbols to be indicated as DL within the PUSCH transmission time window. In yet another design (option 1-2-1-1b), no error condition is defined, and generally speaking, all semi-static flexible symbols are used for PUSCH within the PUSCH transmission time window. That is, UE 102 may perform PUSCH transmission in semi-static flexible symbols (e.g., symbols assumed to be used for UL transmission). In yet another example (option 1-2-1-2), semi-static DL and / or semi-static flexible symbols are not used for PUSCH. Segmentation occurs around semi-static DL symbols and / or semi-static flexible symbols. In yet another example (option 1-2-1-3), a dynamic indication in the UL grant is used for which group of semi-static flexible symbols is used for PUSCH. Segmentation occurs around invalid symbols of semi-static DL and dynamic indication. In yet another example (option 1-2-1-4), predefined rules are used to determine which group of semi-static flexible symbols are used for PUSCH transmission. Segmentation occurs around semi-static DL and invalid symbols defined in the rules. That is, UE 102 can perform PUSCH transmission in this set of semi-static flexible symbols, and the set of semi-static symbols used for PUSCH transmission can be specified (for example, by specification) and is known information between gNB 160 and UE 102.

[0128] For DG PUSCH transmission, for the case where dynamic SFI is configured (case 1-2), the behavior may depend on the dynamic SFI, which may be referred to as option 1-2-2. That is, the UE may use the SFI to determine the symbols used to perform PUSCH transmission. For example (option 1-2-2-1), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, segmentation occurs around semi-static DL symbols and / or dynamic DL symbols and / or dynamic flexible symbols. Here, the dynamic DL symbols and / or dynamic flexible symbols may be indicated by the SFI included in DCI format 2_0. In another example (option 1-2-2-2), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, dynamic flexible symbols are used for PUSCH transmission. Segmentation occurs around semi-static DL symbols and / or dynamic DL symbols. In yet another example (option 1-2-2-3), in a case where a configuration on a dynamic SFI is configured and an SFI included in a DCI format 2_0 is received, dynamic flexible symbols are used for PUSCH transmission. If a repetition (e.g., a transmission opportunity (e.g., repeated)) collides with a dynamic DL symbol, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including repetition)). In yet another example (option 1-2-2-4), in a case where a configuration on a dynamic SFI is configured and an SFI included in a DCI format 2_0 is received, if a repetition (e.g., a transmission opportunity (e.g., repeated)) collides with a dynamic DL symbol and / or a dynamic flexible symbol, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including repetition)). In yet another example (option 1-2-2-5), when configuration on dynamic SFI is configured and SFI included in DCI format 2_0 is not received, if a repetition (e.g., (e.g., repeated) transmission opportunity) conflicts with a semi-static flexible symbol, the repetition is not transmitted (e.g., UE 102 may not perform a PUSCH transmission (e.g., including a repetition)).

[0129] For CG PUSCH transmissions other than the first 2 types of CG PUSCH transmissions (including all repetitions) activated by UL authorization (Case 2), how to handle the interaction of enhanced PUSCH (including mini-slot repetitions and / or multi-segment transmissions) with the DL / UL direction may depend on whether the configuration on the dynamic SFI is configured.

[0130] For CG PUSCH transmissions other than the first Class 2 CG PUSCH transmissions, for the case where dynamic SFI is not configured (case 2-1), semi-static flexible symbols may be used for PUSCH. Segmentation may occur around semi-static DL symbols. The processing method here may be referred to as Option 2-1.

[0131] For CG PUSCH transmissions other than the first 2 types of CG PUSCH transmissions, for the case where dynamic SFI is configured (case 2-2), the behavior (e.g., interaction with the process in the UL / DL direction) may not depend on (e.g., may be independent of) the dynamic SFI, which may be referred to as option 2-2-1. For example, for option 2-2-1-1, semi-static DL symbols and / or semi-static flexible symbols are not used for PUSCH. Segmentation occurs around the semi-static DL and / or semi-static flexible symbols. In another example (option 2-2-1-2), a predefined rule is used to determine which set of semi-static flexible symbols is used for PUSCH transmission. Segmentation occurs around the semi-static DL and invalid symbols defined in the rule. That is, the UE 102 can perform PUSCH transmission in the set of semi-static flexible symbols, and the set of semi-static symbols used for PUSCH transmission can be specified (e.g., by a specification) and is known information between the gNB 160 and the UE 102.

[0132] For CG PUSCH transmissions other than the first Class 2 CG PUSCH transmissions, for the case where dynamic SFI is configured (in this case) (Case 2-2), the behavior (e.g., interaction with the process in the UL / DL direction) may depend on the dynamic SFI, which may be referred to as Option 2-2-2. That is, the UE may use the SFI to determine the symbols used to perform PUSCH transmission. For example (Option 2-2-2-1), in the case where the configuration on the dynamic SFI is configured and the SFI included in the DCI format 2_0 is received, segmentation occurs around semi-static DL symbols and dynamic DL and / or flexible symbols. Here, the dynamic DL symbols and / or dynamic flexible symbols may be indicated by the SFI included in the DCI format 2_0. In yet another example (option 2-2-2-2), in a case where the configuration on the dynamic SFI is configured and the SFI included in the DCI format 2_0 is received, if the repetition (e.g., the (e.g., repeated) transmission opportunity) collides with the semi-static DL symbol and / or the dynamic DL and / or the dynamic flexible symbol, the repetition is not transmitted (e.g., the UE 102 may not perform PUSCH transmission (e.g., including repetition)). In yet another example (option 2-2-2-3), in a case where the configuration on the dynamic SFI is configured and the SFI included in the DCI format 2_0 is not received, if the repetition (e.g., the (e.g., repeated) transmission opportunity) collides with the semi-static flexible symbol, the repetition is not transmitted (e.g., the UE 102 may not perform PUSCH transmission (e.g., including repetition)).

[0133] For the first Class 2 CG PUSCH transmission (including all repetitions) activated by UL grant (Case 3), the same behavior as for DGPUSCH (Case 1) may be used (e.g., processing method, interaction with UL / DL direction determination procedures). Any option adopted / indicated / configured for Case 1 (e.g., option 1-1, option 1-2-1, option 1-2-1-1, option 1-2-1-1a, option 1-2-1-1b, option 1-2-1-2, option 1-2-1-3, option 1-2-1-4, option 1-2-2, option 1-2-2-1, option 1-2-2-2, option 1-2-2-3, option 1-2-2-4, and / or option 1-2-2-5) may also be applied to Case 3. The behaviors for Case 1 and Case 3 may be adopted / indicated / configured jointly or separately. For example, the gNB 160 may configure the behaviors for Case 1 and Case 3 jointly (e.g., by using RRC messages). Additionally or alternatively, the gNB 160 may configure behaviors for Case 1 and Case 3 separately (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 1 and Case 3 jointly (e.g., by using a MAC CE and / or a DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 1 and Case 3 separately (e.g., by using a MAC CE and / or a DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, the behaviors for Case 1 and Case 3 may be jointly specified by a specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, the behaviors for Case 1 and Case 3 may be specified separately by a specification and may be known information between the gNB 160 and the UE 102. Case 1 may use one of the above options, while Case 3 may use a different one of the above options. For example, option 1-2-1 and / or its sub-options (or option 1-2-2 and / or its sub-options) may be adopted / indicated / configured for case 1, while option 1-2-2 and / or its sub-options (or option 1-2-1 and / or its sub-options) may be adopted / indicated / configured for case 3. Option 1-2-1-2 (or option 1-2-1-1) may be adopted / indicated / configured for case 1, while option 1-2-1-1 (or option 1-2-1-2) may be adopted / indicated / configured for case 3. Option 1-2-2-2 (or option 1-2-2-1) may be adopted / indicated / configured for case 1, while option 1-2-2-1 (or option 1-2-2-2) may be adopted / indicated / configured for case 3. Option 1-2-2-1 (or option 1-2-2-4) may be adopted / indicated / configured for case 1, while option 1-2-2-4 (or option 1-2-2-1) may be adopted / indicated / configured for case 3.Option 1-2-2-3 (or option 1-2-2-4) may be employed / indicated / configured for case 1, while option 1-2-2-4 (or option 1-2-2-3) may be employed / indicated / configured for case 3.

[0134] For the first Class 2 CG PUSCH (including all repetitions) activated by an UL grant (Case 3), the same behavior as for a CG PUSCH without an associated UL grant (Case 2) may be used. Any option adopted / indicated / configured for Case 2 (e.g., option 2-1, option 2-2-1, option 2-2-1-1, option 2-2-1-2, option 2-2-2, option 2-2-2-1, option 2-2-2-2, or option 2-2-2-3) may also be applied to Case 3. The behaviors for Case 2 and Case 3 may be adopted / indicated / configured jointly or separately. For example, the gNB 160 may configure the behaviors for Case 2 and Case 3 jointly (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may configure the behaviors for Case 2 and Case 3 separately (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 2 and Case 3 jointly (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 2 and Case 3 separately (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, the behaviors for Case 2 and Case 3 may be commonly specified by the specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, the behaviors for Case 2 and Case 3 may be separately specified by the specification and may be known information between the gNB 160 and the UE 102. Case 2 may use one of the above options, while Case 3 may use a different one of the above options. For example, option 2-2-1 and / or its sub-options (or option 2-2-2 and / or its sub-options) may be adopted / indicated / configured for case 2, while option 2-2-2 and / or its sub-options (or option 2-2-1 and / or its sub-options) may be adopted / indicated / configured for case 3. Option 2-2-1-2 (or option 2-2-1-1) may be adopted / indicated / configured for case 2, while option 2-2-1-1 (or option 2-2-1-2) may be adopted / indicated / configured for case 3. Option 2-2-2-2 (or option 2-2-2-1) may be adopted / indicated / configured for case 2, while option 2-2-2-1 (or option 2-2-2-2) may be adopted / indicated / configured for case 3.

[0135] For the first Class 2 CG PUSCH (including all repetitions) activated by UL grant (Case 3), different behaviors may be adopted / indicated / configured. For example (Option 3-1), semi-static flexible symbols are used for PUSCH regardless of whether dynamic SFI is configured, and segmentation occurs around semi-static DL symbols. In yet another example (Option 3-2), only semi-static UL symbols are used for PUSCH regardless of whether dynamic SFI is configured, and segmentation occurs around semi-static DL and / or semi-static flexible symbols. In yet another example (Option 3-3), if a repetition collides with a semi-static flexible symbol, then the repetition is not transmitted, regardless of whether dynamic SFI is configured. In yet another example (Option 3-4), semi-static flexible symbols are used for PUSCH regardless of whether dynamic SFI is configured, and if a repetition collides with a semi-static DL symbol, then the repetition is not transmitted.

[0136] For configured granted PUSCH retransmissions (including repetitions) (case 4), the same behavior as for DG PUSCH (case 1) may be used (e.g., processing method, interaction with UL / DL direction determination procedures). Any options adopted / indicated / configured for case 1 (e.g., option 1-1, option 1-2-1, option 1-2-1-1, option 1-2-1-1a, option 1-2-1-1b, option 1-2-1-2, option 1-2-1-3, option 1-2-1-4, option 1-2-2, option 1-2-2-1, option 1-2-2-2, option 1-2-2-3, option 1-2-2-4, and / or option 1-2-2-5) may also be applied to case 4. The behaviors for case 1 and case 4 may be adopted / indicated / configured jointly or separately. For example, the gNB 160 may configure the behaviors for case 1 and case 4 jointly (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may configure behaviors for Case 1 and Case 4 separately (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 1 and Case 4 jointly (e.g., by using a MAC CE and / or a DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 1 and Case 4 separately (e.g., by using a MAC CE and / or a DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, the behaviors for Case 1 and Case 4 may be jointly specified by a specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, the behaviors for Case 1 and Case 4 may be specified separately by a specification and may be known information between the gNB 160 and the UE 102. Case 1 may use one of the above options, while Case 4 may use a different one of the above options. For example, option 1-2-1 and / or its sub-options (or option 1-2-2 and / or its sub-options) may be adopted / indicated / configured for case 1, while option 1-2-2 and / or its sub-options (or option 1-2-1 and / or its sub-options) may be adopted / indicated / configured for case 4. Option 1-2-1-2 (or option 1-2-1-1) may be adopted / indicated / configured for case 1, while option 1-2-1-1 (or option 1-2-1-2) may be adopted / indicated / configured for case 4. Option 1-2-2-2 (or option 1-2-2-1) may be adopted / indicated / configured for case 1, while option 1-2-2-1 (or option 1-2-2-2) may be adopted / indicated / configured for case 4. Option 1-2-2-1 (or option 1-2-2-4) may be employed / indicated / configured for case 1, while option 1-2-2-4 (or option 1-2-2-1) may be employed / indicated / configured for case 4.Option 1-2-2-3 (or option 1-2-2-4) may be employed / indicated / configured for case 1, while option 1-2-2-4 (or option 1-2-2-3) may be employed / indicated / configured for case 4.

[0137] Additionally or alternatively, for PUSCH retransmissions (including repetitions) with a configured grant (Case 4), the same behavior as for CG PUSCH without an associated UL grant (Case 2) may be used. Any option adopted / indicated / configured for Case 2 (e.g., option 2-1, option 2-2-1, option 2-2-1-1, option 2-2-1-2, option 2-2-2, option 2-2-2-1, option 2-2-2-2, or option 2-2-2-3) may also be applied to Case 4. The behaviors for Case 2 and Case 4 may be adopted / indicated / configured jointly or separately. For example, the gNB 160 may configure the behaviors for Case 2 and Case 4 jointly (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may configure the behaviors for Case 2 and Case 4 separately (e.g., by using an RRC message). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 2 and Case 4 jointly (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, the gNB 160 may indicate behaviors for Case 2 and Case 4 separately (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, the behaviors for Case 2 and Case 4 may be commonly specified by the specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, the behaviors for Case 2 and Case 4 may be separately specified by the specification and may be known information between the gNB 160 and the UE 102. Case 2 may use one of the above options, while Case 4 may use a different one of the above options. For example, option 2-2-1 and / or its sub-options (or option 2-2-2 and / or its sub-options) may be adopted / indicated / configured for case 2, while option 2-2-2 and / or its sub-options (or option 2-2-1 and / or its sub-options) may be adopted / indicated / configured for case 4. Option 2-2-1-2 (or option 2-2-1-1) may be adopted / indicated / configured for case 2, while option 2-2-1-1 (or option 2-2-1-2) may be adopted / indicated / configured for case 4. Option 2-2-2-2 (or option 2-2-2-1) may be adopted / indicated / configured for case 2, while option 2-2-2-1 (or option 2-2-2-2) may be adopted / indicated / configured for case 4.

[0138] For configured authorized PUSCH retransmissions (including repetitions) (Case 4), different behaviors may be adopted / indicated / configured. For example (Option 4-1), semi-static flexible symbols are used for PUSCH regardless of whether dynamic SFI is configured, and segmentation occurs around semi-static DL symbols. In another example (Option 4-2), only semi-static UL symbols are used for PUSCH regardless of whether dynamic SFI is configured, and segmentation occurs around semi-static DL and / or semi-static flexible symbols. In another example (Option 4-3), if a repetition collides with a semi-static flexible symbol, the repetition is not transmitted, regardless of whether dynamic SFI is configured. In another example (Option 4-4), semi-static flexible symbols are used for PUSCH regardless of whether dynamic SFI is configured, and if a repetition collides with a semi-static DL symbol, the repetition is not transmitted.

[0139] For the above behavior, segmentation can always be performed at the time slot boundary. That is, UE 102 can always apply segmentation to PUSCH transmission (DG PUSCH transmission, CG 1 type PUSCH transmission, CG 2 type PUSCH transmission and / or retransmission corresponding to CG1 type and / or CG 2 type PUSCH transmission) at the time slot boundary.

[0140] In the case where a repetition is not transmitted as described above, the entire repetition may be discarded, or only the repetition at the colliding symbol may be discarded. In another design, a delay of the repetition may be applied. In the case where dynamic SFI is not configured and a symbol collision occurs as described above, a delay may be applied. When a repetition collides with a semi-static flexible symbol, a delay may be applied.

[0141] To handle collisions with SSB (synchronization and PBCH (Physical Broadcast Channel) blocks) and / or PRACH symbols, any of the above behaviors may also be adopted / indicated / configured.

[0142] With respect to how to interpret the length L of all PUSCH transmissions (e.g., the number of symbols used for repetitions, PUSCH transmissions, transmission opportunities, or nominal repetitions) and the number of repetitions K, the time window in which valid symbols (e.g., UL symbols and / or flexible symbols indicated by RRC messages and / or dynamic signaling) are available for transmission is L*K. In yet another design, the time window in which valid symbols (e.g., UL symbols and / or flexible symbols indicated by RRC messages and / or dynamic signaling) are available for transmission may be longer than L*K symbols, and the time window may be extended at least in the case of semi-static DL symbols. The extension of the time window may also be applied in the case of dynamic DL symbols and / or semi-static flexible symbols and / or reserved symbols (if defined) and / or SSB symbols and / or Class 0 CSS in CORESET#0 (as indicated by MIB). The maximum time window size may be defined in the specification, configured by RRC messages and / or indicated by L1 signaling (e.g., DCI, PDCCH) and / or MAC CE.

[0143] The UE operations module 124 may provide the information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.

[0144] The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of the modulation pattern expected for transmissions from the gNB 160.

[0145] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding expected for the transmission from the gNB 160.

[0146] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0147] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0148] The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of the type of modulation (e.g., constellation mapping) to be used for transmission to the gNB 160. The modulator 154 may modulate the coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0149] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may up-convert the modulated signal 156 and transmit the modulated signal to the one or more gNBs 160.

[0150] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0151] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0152] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may decode the signal using the decoder 166. The decoder 166 may produce one or more decoded signals 164, 168. For example, the signal 164 decoded by the first eNB may include received payload data, which may be stored in the data buffer 162. The signal 168 decoded by the second eNB may include overhead data and / or control data. For example, the signal 168 decoded by the second eNB may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operations module 182 may use to perform one or more operations.

[0153] In general, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include a gNB scheduling module 194. The gNB scheduling module 194 may perform operations for mini-slot based repetition as described herein.

[0154] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0155] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding expected for transmissions from one or more UEs 102.

[0156] The gNB operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.

[0157] The encoder 109 may encode the transmission data 105 and / or other information included in the information 101 provided by the gNB operation module 182. For example, encoding the transmission data 105 and / or other information included in the information 101 may involve error detection and / or correction coding, mapping the data to space, time and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0158] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of the type of modulation (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0159] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (or when not) to transmit signals to the one or more UEs 102. The one or more transmitters 117 may up-convert the modulated signal 115 and transmit the modulated signal to the one or more UEs 102.

[0160] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0161] It should also be noted that one or more of the elements or components thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0162] URLLC can coexist with other services (e.g., eMBB). Due to latency requirements, in some methods, URLLC may have the highest priority. This article provides some examples of URLLC coexisting with other services (e.g., in one or more of the following figures).

[0163] Figure 2 is a diagram showing an example of a resource grid for a downlink. Figure 2 The resource grid shown may be used in some specific implementations of the systems and methods disclosed herein. Figure 1 More details about the resource grid are given.

[0164] exist Figure 2 In the embodiment, a downlink subframe 269 may include two downlink time slots 283. DL RB N is the downlink bandwidth configuration of the serving cell. RB sc Multiples of N RB sc is the size of resource block 289 in the frequency domain, expressed as the number of subcarriers, and N DL symb is the number of OFDM symbols 287 in the downlink time slot 283. A resource block 289 may include a plurality of resource elements (REs) 291.

[0165] For PCell, N DL RB Broadcast as part of system information. For SCell (including Licensed Assisted Access (LAA) SCell), N DL RB The configuration is performed through an RRC message dedicated to the UE 102. For PDSCH mapping, the available RE 291 may be the RE 291 whose index 1 satisfies 1≥1 in the subframe. 数据，开始 And / or 1 数据，结束 ≥1.

[0166] In the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH, etc. may be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs), which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair includes two downlink RBs that are consecutive in the time domain.

[0167] A downlink RB includes twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and the time domain, respectively. Although a downlink subframe in one component carrier (CC) is discussed herein, a downlink subframe is defined for each CC, and the downlink subframes are substantially synchronized with each other between CCs.

[0168] Figure 3 is a diagram showing an example of a resource grid for uplink. Figure 3The resource grid shown may be used in some specific implementations of the systems and methods disclosed herein. Figure 1 More details about the resource grid are given.

[0169] exist Figure 3 In the embodiment, an uplink subframe 369 may include two uplink time slots 383. UL RB N is the uplink bandwidth configuration of the serving cell. RB sc Multiples of N RB sc is the size of resource block 389 in the frequency domain, expressed as the number of subcarriers, and N UL 符号 is the number of SC-FDMA symbols 393 in the uplink slot 383. A resource block 389 may include a plurality of resource elements (REs) 391.

[0170] For PCell, N UL RB Broadcast as part of system information. For SCell (including LAA SCell), N UL RB The configuration is performed through an RRC message dedicated to UE 102.

[0171] In the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme can also be adopted, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH, etc. can be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair includes two uplink RBs that are consecutive in the time domain.

[0172] An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM and / or DFT-S-OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM and / or DFT-S-OFDM symbol in the time domain is called an RE and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and time domain, respectively. Although this article discusses an uplink subframe in one component carrier (CC), an uplink subframe is defined for each CC.

[0173] Figure 4Several examples of parameters 401 are shown. Parameter #1 401a may be a basic parameter (e.g., a reference parameter). For example, RE 495a of basic parameter 401a may be defined as having a subcarrier spacing 405a of 15kHz in the frequency domain and a length of 2048Ts+CP (e.g., 160Ts or 144Ts) in the time domain (i.e., symbol length #1 403a), where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds. For the i-th parameter, subcarrier spacing 405 may be equal to 15*2 i And the effective OFDM symbol length is 2048*2 -i *Ts. This makes the symbol length 2048*2 -i *Ts+CP length (e.g., 160*2 -i *Ts or 144*2 -i *Ts). In other words, the subcarrier spacing of the i+1th parameter is twice the subcarrier spacing of the ith parameter, and the symbol length of the i+1th parameter is half the symbol length of the ith parameter. Figure 4 Four parameters are shown, but the system may support another number of parameters. Furthermore, the system does not necessarily support all of the 0th to Ith parameters (i=0, 1, ..., I).

[0174] For example, the first UL transmission on the first SPS resource as described above may be performed only on parameter #1 (e.g., subcarrier spacing is 15 kHz). Here, UE 102 may acquire (detect) parameter #1 based on the synchronization signal. In addition, UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) configuring parameter #1. The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on parameter #1, parameter #2 (subcarrier spacing is 30 kHz), and / or parameter #3 (subcarrier spacing is 60 kHz).

[0175] In addition, the second UL transmission on the second SPS resource as described above may be performed only on parameter #3. Here, for example, UE 102 may receive system information (e.g., master information block (MIB) and / or system information block (SIB)) including information configuring parameter #2 and / or parameter #3.

[0176] In addition, UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) for configuring parameter #2 and / or parameter #3. System information (e.g., MIB) may be transmitted on a BCH (broadcast channel) and / or a dedicated RRC signal. System information (e.g., SIB) may include information about when to evaluate whether UE 102 is allowed to access a cell and / or define scheduling of other system information. System information (SIB) may include radio resource configuration information common to multiple UEs 102. That is, the dedicated RRC signal may include each of a plurality of parameter configurations (first parameters, second parameters, and / or third parameters) for each of the UL transmissions (e.g., each of the UL-SCH transmissions, each of the PUSCH transmissions). Moreover, the dedicated RRC signal may include each of a plurality of parameter configurations (first parameters, second parameters, and / or third parameters) for each of the DL transmissions (e.g., each of the PDCCH transmissions).

[0177] Figure 5 Shows Figure 4 An example of a subframe structure of parameters 501 is shown in FIG. Considering that time slot 283 includes N DL Symb (or N UL Symb )=7 symbols, the slot length of the i+1th parameter 501 is half the slot length of the i-th parameter 501, and the number of slots 283 in a subframe (e.g., 1 ms) is ultimately doubled. It should be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

[0178] Figure 6 An example of a time slot 683 and a sub-time slot 607 is shown. If the sub-time slot 607 is not configured by a higher layer, the UE 102 and the eNB and / or gNB 160 may use only the time slot 683 as a scheduling unit. More specifically, a given transport block may be assigned to the time slot 683. If the sub-time slot 607 is configured by a higher layer, the UE 102 and the eNB and / or gNB 160 may use the sub-time slot 607 as well as the time slot 683. The sub-time slot 607 may include one or more OFDM symbols. The maximum number of OFDM symbols constituting the sub-time slot 607 may be N. DL symb -1(or N UL symb -1).

[0179] The sub-slot length may be configured by higher layer signaling. Alternatively, the sub-slot length may be indicated by a physical layer control channel (eg, via a DCI format).

[0180] Subslot 607 can start from any symbol in slot 683 unless it conflicts with the control channel. Based on the starting position restriction, the length of the minislot may be limited. For example, the length is N DL symb -1(or N UL symb -1) may start from the second symbol in slot 683. The starting position of sub-slot 607 may be indicated by a physical layer control channel (e.g., by a DCI format). Alternatively, the starting position of sub-slot 607 may be derived from information of a physical layer control channel that schedules data in sub-slot 607 (e.g., a search space index, a blind decoding candidate index, a frequency and / or time resource index, a PRB index, a control channel element index, a control channel element aggregation level, an antenna port index, etc.).

[0181] Where subslots 607 are configured, a given transport block may be allocated to slot 683, subslot 607, aggregated subslots 607, or aggregated subslots 607 and slot 683. This unit may also be a unit for HARQ-ACK bit generation.

[0182] Figure 7 An example of a scheduling timeline 709 is shown. For a normal DL scheduling timeline 709a, a DL control channel is mapped to the initial part of a time slot 783a. A DL control channel 711 schedules a DL shared channel 713a in the same time slot 783a. The HARQ-ACK for the DL shared channel 713a (i.e., each HARQ-ACK indicating whether a transport block in each DL shared channel 713a is successfully detected) is reported via a UL control channel 715a in a subsequent time slot 783b. In this case, a given time slot 783 may contain one of a DL transmission and a UL transmission.

[0183] For the normal UL scheduling timeline 709b, the DL control channel 711b is mapped to the initial part of the time slot 783c. The DL control channel 711b schedules the UL shared channel 717a in the next time slot 783d. For these cases, the associated timing (time offset) between the DL time slot 783c and the UL time slot 783d can be fixed or configured by high-layer signaling. Alternatively, it can be indicated by a physical layer control channel (e.g., a DL allocation DCI format, a UL authorization DCI format, or another DCI format, such as a UE common signaling DCI format that can be monitored in a common search space).

[0184] For the self-contained basic DL scheduling timeline 709c, the DL control channel 711c is mapped to the initial part of the time slot 783e. The DL control channel 711c schedules the DL shared channel 713b in the same time slot 783e. The HARQ-ACK for the DL shared channel 713b is reported in the UL control channels 715b, which are mapped in the end part of the time slot 783e.

[0185] For the self-contained basic UL scheduling timeline 709d, the DL control channel 711d is mapped to the initial part of the time slot 783f. The DL control channel 711d schedules the UL shared channel 717b in the same time slot 783f. For these cases, the time slot 783f may contain a DL part and a UL part, and there may be a guard period between the DL transmission and the UL transmission.

[0186] The use of self-contained time slots may be based on the configuration of self-contained time slots. Alternatively, the use of self-contained time slots may be based on the configuration of sub-time slots. Still alternatively, the use of self-contained time slots may be based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0187] Figure 8 An example of a DL control channel monitoring area is shown. One or more groups of PRBs may be configured for DL ​​control channel monitoring. In other words, a control resource set is a group of PRBs in the frequency domain within which UE 102 attempts to blindly decode downlink control information, wherein the PRBs may or may not be frequency continuous, UE 102 may have one or more control resource sets, and one DCI message may be located in one control resource set. In the frequency domain, a PRB is a resource unit size for a control channel (which may or may not include a demodulation reference signal (DMRS)). A DL shared channel may start at an OFDM symbol later than a symbol carrying a detected DL control channel. Alternatively, a DL shared channel may start at the last OFDM symbol carrying a detected DL control channel (or at a symbol earlier than the last OFDM symbol). In other words, dynamic reuse of at least a portion of resources in a control resource set for data of the same or different UEs 102 may be supported at least in the frequency domain.

[0188] Fig. 9 An example of a DL control channel including more than one control channel element is shown. When the control resource set spans multiple OFDM symbols, the control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped on an RE defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for a single DL control channel transmission, DL control channel element aggregation may be performed.

[0189] The number of aggregated DL control channel elements is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to an integer power. The gNB 160 may inform the UE 102 which control channel candidates are mapped to each subset of OFDM symbols in the control resource set. If one DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, i.e., multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements may be aggregated in different OFDM symbols.

[0190] Fig.10 An example of a UL control channel structure is shown. The UL control channel may be mapped on REs defined by PRBs and time slots in the frequency domain and time domain, respectively. The UL control channel may be referred to as a long format (or just a first format). The UL control channel may be mapped on REs on a limited OFDM symbol in the time domain. This may be referred to as a short format (or just a second format). A UL control channel with a short format may be mapped on REs within a single PRB. Alternatively, a UL control channel with a short format may be mapped on REs within multiple PRBs. For example, staggered mapping may be applied, i.e., the UL control channel may be mapped to every N PRBs (e.g., 5 or 10) within the system bandwidth.

[0191] Fig.11 1 is a block diagram illustrating one specific implementation of a gNB 1160. The gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0192] The high-level processor 1123 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1123 may obtain a transport block from the physical layer. The high-level processor 1123 may send and / or obtain high-level messages such as RRC messages and MAC messages to and / or from the high-level layer of the UE. The high-level processor 1123 may provide a transport block to the PDSCH transmitter and provide a transmission parameter related to the transport block to the PDCCH transmitter.

[0193] The DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmit antenna 1131. The UL receiver 1133 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1131. The PUCCH receiver 1135 may provide UCI to the higher layer processor 1123. The PUSCH receiver 1137 may provide the received transport block to the higher layer processor 1123.

[0194] Fig.12 1 is a block diagram illustrating one specific implementation of UE 1202. UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0195] The high-level processor 1223 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1223 may obtain a transport block from the physical layer. The high-level processor 1223 may send and / or obtain high-level messages such as RRC messages and MAC messages to and / or from the high-level layer of the UE. The high-level processor 1223 may provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0196] The DL receiver 1243 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1231. The PDCCH receiver 1245 may provide the DCI to the higher layer processor 1223. The PDSCH receiver 1247 may provide the higher layer processor 1223 with the received transport block.

[0197] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "New Generation-(G)PDCCH, GPDSCH, GPUCCH, and GPUSCH," etc.

[0198] Fig.13 Various components that may be used in a UE 1302 are shown. Fig.13 The UE 1302 described may be based on the combination of Figure 11302 is implemented by the UE 102 described in the embodiment of the present invention. The UE 1302 includes a processor 1303 that controls the operation of the UE 1302. The processor 1303 may also be referred to as a central processing unit (CPU). The memory 1305 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 1307a and data 1309a to the processor 1303. A portion of the memory 1305 may also include a non-volatile random access memory (NVRAM). The instructions 1307b and data 1309b may also reside in the processor 1303. The instructions 1307b and / or data 1309b loaded into the processor 1303 may also include instructions 1307a and / or data 1309a from the memory 1305, which are loaded for execution or processing by the processor 1303. The instructions 1307b may be executed by the processor 1303 to implement the above method.

[0199] The UE 1302 may also include a housing that houses one or more transmitters 1358 and one or more receivers 1320 to allow transmission and reception of data. The transmitters 1358 and receivers 1320 may be combined into one or more transceivers 1318. One or more antennas 1322a-n are attached to the housing and electrically coupled to the transceiver 1318.

[0200] The various components of UE 1302 are coupled together via a bus system 1311 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Fig.13 1302 is shown as a bus system 1311. UE 1302 may also include a digital signal processor (DSP) 1313 for processing signals. UE 1302 may also include a communication interface 1315 that provides a user with access to the functionality of UE 1302. Fig.13 The UE 1302 is shown as a functional block diagram rather than a listing of specific components.

[0201] Fig.14 Various components that may be used in gNB 1460 are shown. Fig.14 The gNB 1460 described may be configured in accordance with the Figure 11407a and data 1409a. The gNB 1460 may be implemented by the gNB 1460 described herein. The gNB 1460 includes a processor 1403 that controls the operation of the gNB 1460. The processor 1403 may also be referred to as a central processing unit (CPU). The memory 1405 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of the two memories, or any type of device that can store information) provides instructions 1407a and data 1409a to the processor 1403. A portion of the memory 1405 may also include a non-volatile random access memory (NVRAM). The instructions 1407b and data 1409b may also reside in the processor 1403. The instructions 1407b and / or data 1409b loaded into the processor 1403 may also include instructions 1407a and / or data 1409a from the memory 1405, which are loaded for execution or processing by the processor 1403. The instructions 1407b may be executed by the processor 1403 to implement the above method.

[0202] The gNB 1460 may also include a housing that houses one or more transmitters 1417 and one or more receivers 1478 to allow transmission and reception of data. The transmitters 1417 and receivers 1478 may be combined into one or more transceivers 1476. One or more antennas 1480a-n are attached to the housing and electrically coupled to the transceivers 1476.

[0203] The various components of gNB 1460 are coupled together via bus system 1411 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Fig.14 1411. The gNB 1460 may also include a digital signal processor (DSP) 1413 for processing signals. The gNB 1460 may also include a communication interface 1415 that provides a user with a function of accessing the gNB 1460. Fig.14 The gNB 1460 shown is a functional block diagram rather than a listing of specific components.

[0204] Fig.15 is a block diagram showing a specific implementation of UE 1502, wherein the system and method are implemented

[0205] The UE 1502 includes a transmitting device 1558, a receiving device 1520, and a control device 1524. The transmitting device 1558, the receiving device 1520, and the control device 1524 may be configured to perform the above Figure 1 One or more of the functions described. Fig.13 Shows Fig.15 Various other structures can be implemented to achieve Figure 1For example, the DSP may be implemented by software.

[0206] Fig.16 is a block diagram illustrating a specific implementation of a gNB 1660 in which systems and methods implement mini-slot based repetition. The gNB 1660 includes a transmitting device 1623, a receiving device 1678, and a control device 1682. The transmitting device 1623, the receiving device 1678, and the control device 1682 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Fig.14 Shows Fig.16 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0207] Fig.17 1700 is a flow chart illustrating a method 1700 performed by a user equipment (UE) 102. The UE 102 may receive signaling including a configuration for a configured granted physical uplink shared channel (PUSCH) or grant-based PUSCH 1702. The UE 102 may determine whether to use multi-segment transmission and mini-slot repetition for the configured granted PUSCH or grant-based PUSCH 1704. The UE 102 may transmit multi-segment transmission and mini-slot repetition for the configured granted PUSCH or grant-based PUSCH 1706.

[0208] In one method, one uplink (UL) grant for grant-based PUSCH and one configured grant configuration for configured grant PUSCH are used to support one or more actual PUSCH repetitions in one slot, or two or more actual PUSCH repetitions across slot boundaries in consecutive available slots.

[0209] In another method, one UL grant for grant-based PUSCH and one configured grant configuration for configured grant PUSCH are used to support one or more PUSCH repetitions in one slot, or two or more PUSCH repetitions across slot boundaries in consecutive available slots.

[0210] Fig.181800 is a flow chart illustrating a method 1800 performed by a base station (gNB) 160. The gNB 160 may transmit signaling to a user equipment (UE) 102, the signaling including a configuration for a configured granted physical uplink shared channel (PUSCH) or grant-based PUSCH 1802. The gNB 160 may determine whether to use multi-segment transmission and mini-slot repetition for the configured granted PUSCH or grant-based PUSCH 1804. The gNB 160 may receive multi-segment transmission and mini-slot repetition for the configured granted PUSCH or grant-based PUSCH 1806.

[0211] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example, and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Optical disks, where disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.

[0212] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0213] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0214] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[0215] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls the CPU, etc. in a manner that realizes the functions according to the system and method (a program that causes the computer to operate). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, the information is stored in various ROMs or HDDs, and is read by the CPU whenever necessary for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, nonvolatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., a magnetic tape, a floppy disk, etc.), etc. is possible. In addition, in some cases, the above-mentioned functions according to the system and method are realized by running the loaded program, and in addition, the functions according to the system and method are realized based on instructions from the program and in combination with an operating system or other application programs.

[0216] In addition, in the case where the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transferred to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. In addition, some or all of the gNB 160 and UE 102 according to the above-mentioned system and method may be implemented as LSI, which is a typical integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into a chip separately, and some or all of the functional blocks may be integrated into a chip. In addition, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. In addition, if an integrated circuit technology that replaces LSI emerges as semiconductor technology continues to advance, an integrated circuit applying the technology may also be used.

[0217] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned specific implementations can be implemented or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each of the above-mentioned circuits may be configured by a digital circuit, or may be configured by an analog circuit. In addition, when a technology for making an integrated circuit that replaces the current integrated circuit appears due to advances in semiconductor technology, the integrated circuit produced by the technology can also be used.

[0218] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B, and / or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be interpreted as meaning one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" should be understood to refer to one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" should be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

[0219] In one example, a user equipment (UE) includes: a receiving circuit configured to receive signaling including a configuration for a configured authorized physical uplink shared channel (PUSCH) or a configuration based on an authorized PUSCH; a higher-level processor configured to determine whether to use multi-segment transmissions and mini-slot repetitions for the configured authorized PUSCH or for the authorized PUSCH; and a transmitting circuit configured to transmit these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the authorized PUSCH.

[0220] In one example, according to the UE, an uplink (UL) grant for the grant-based PUSCH and a configured grant configuration for the configured granted PUSCH are used to support one or more actual PUSCH repetitions in a timeslot, or two or more actual PUSCH repetitions across timeslot boundaries in consecutive available timeslots.

[0221] In one example, according to the UE, one or more PUSCH repetitions in a timeslot, or two or more PUSCH repetitions across timeslot boundaries in consecutive available timeslots are supported using one UL grant for the grant-based PUSCH and one configured grant configuration for the configured grant PUSCH.

[0222] In one example, a base station (gNB) includes: a transmission circuit configured to transmit signaling to a user equipment (UE), the signaling including a configuration for a configured authorized physical uplink shared channel (PUSCH) or a configuration based on an authorization; a higher-level processor configured to determine whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the authorization-based PUSCH; and a receiving circuit configured to receive these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the authorization-based PUSCH from the UE.

[0223] In one example, according to the gNB, one or more actual PUSCH repetitions in a timeslot or two or more actual PUSCH repetitions across timeslot boundaries in consecutive available timeslots are supported using an uplink (UL) grant for the grant-based PUSCH and a configured grant configuration for the configured granted PUSCH.

[0224] In one example, according to the gNB, one or more PUSCH repetitions in a timeslot or two or more PUSCH repetitions across timeslot boundaries in consecutive available timeslots are supported using one UL grant for the grant-based PUSCH and one configured grant configuration for the configured granted PUSCH.

[0225] In one example, a method performed by a user equipment (UE) includes: receiving signaling including a configuration for a configured authorized physical uplink shared channel (PUSCH) or a configuration based on an authorization-based PUSCH; determining whether to use multi-segment transmissions and mini-slot repetitions for the configured authorized PUSCH or for the authorization-based PUSCH; and transmitting these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the authorization-based PUSCH.

[0226] In one example, a method performed by a base station (gNB) includes: transmitting signaling to a user equipment (UE), the signaling including configuration for a configured authorized physical uplink shared channel (PUSCH) or a grant-based PUSCH; determining whether to use multi-segment transmission and mini-slot repetition for the configured authorized PUSCH or for the grant-based PUSCH; and receiving these multi-segment transmissions and these mini-slot repetitions for the configured authorized PUSCH or the grant-based PUSCH from the UE.

[0227] In one example, a user equipment (UE) communicating with a base station includes: a receiving circuit, the receiving circuit being configured to: receive a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, and receive an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission; a transmitting circuit, the transmitting circuit being configured to: perform the CG PUSCH transmission based on the first information, perform the GB PUSCH transmission based on the second information based on detection of a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), and perform retransmission of the CG PUSCH transmission based on the second information based on detection of a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1.

[0228] In one example, a base station device that communicates with a user equipment (UE) includes: a transmission circuit, which is configured to: transmit a radio resource control (RRC) message including first information, the first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, and transmit an RRC message including second information, the second information indicating a repetition type for a grant-based (GB) PUSCH transmission; a receiving circuit, which is configured to: receive the CG PUSCH transmission based on the first information, based on the transmission of a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), based on the second information to receive the GB PUSCH transmission, based on the transmission of a PDCCH with a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1, and based on the second information to receive a retransmission of the CG PUSCH transmission.

[0229] In one example, a communication method for a user equipment includes: receiving a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, receiving an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission, performing the CG PUSCH transmission based on the first information, performing the GB PUSCH transmission based on the second information based on detecting a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), and performing retransmission of the CGPUSCH transmission based on the second information based on detecting a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI)=1.

[0230] In one example, a communication method for a base station device includes: transmitting a radio resource control (RRC) message including first information indicating a repetition type for a configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmitting an RRC message including second information indicating a repetition type for a grant-based (GB) PUSCH transmission, and a receiving circuit configured to: receive the CG PUSCH transmission based on the first information, based on the transmission of a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), based on the second information to receive the GB PUSCH transmission, based on the transmission of a PDCCH having a CRC scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1, and based on the second information to receive a retransmission of the CG PUSCH transmission.

[0231] <Cross Reference>

[0232] This nonprovisional patent application claims priority under 35 U.S.C. §119 to provisional patent application No. 62,904,868, filed on September 24, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A user equipment UE communicating with a base station, the UE comprising: A receiving circuit, wherein the receiving circuit is configured to: receiving a radio resource control RRC message including first information indicating a repetition type for a configured granted CG physical uplink shared channel PUSCH transmission, The RRC message further includes second information indicating a repetition type for grant-based GB PUSCH transmission, A transmission circuit, wherein the transmission circuit is configured to: performing the CG PUSCH transmission based on the first information, performing the GB PUSCH transmission based on the second information based on detecting a physical downlink control channel PDCCH having a cyclic redundancy check CRC scrambled by a cell radio network temporary identifier C-RNTI, Based on detecting the PDCCH having the CRC scrambled by the configured scheduling radio network temporary identifier CS-RNTI of the new data indicator NDI=1, retransmission of the CG PUSCH transmission is performed based on the second information.

2. A base station device for communicating with a user equipment UE, the base station device comprising: A transmission circuit, wherein the transmission circuit is configured to: transmitting a radio resource control RRC message including first information indicating a repetition type for a configured granted CG physical uplink shared channel PUSCH transmission, The RRC message further includes second information indicating a repetition type for grant-based GB PUSCH transmission, A receiving circuit, wherein the receiving circuit is configured to: receiving the CG PUSCH transmission based on the first information, receiving said GB PUSCH transmission based on said second information based on a transmission of a physical downlink control channel PDCCH with a cyclic redundancy check CRC scrambled by a cell radio network temporary identifier C-RNTI, Based on transmission of a PDCCH with a CRC scrambled by a configured scheduling radio network temporary identifier CS-RNTI with a new data indicator NDI=1, a retransmission of the CG PUSCH transmission is received based on the second information.

3. A communication method of a user equipment, the communication method comprising: receiving a radio resource control RRC message including first information indicating a repetition type for a configured granted CG physical uplink shared channel PUSCH transmission, The RRC message further includes second information indicating a repetition type for grant-based GB PUSCH transmission, performing the CG PUSCH transmission based on the first information, performing the GB PUSCH transmission based on the second information based on detecting a physical downlink control channel PDCCH having a cyclic redundancy check CRC scrambled by a cell radio network temporary identifier C-RNTI, Based on detecting the PDCCH having the CRC scrambled by the configured scheduling radio network temporary identifier CS-RNTI of the new data indicator NDI=1, retransmission of the CG PUSCH transmission is performed based on the second information.

Images