Patent Description:
Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.

As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

<NPL>, discusses PUSCH repetitions within a slot. Regarding time-domain resource allocation, the document describes that in both cases of PUSCH mapping type A and type B the repetitions are performed by applying the same symbol allocation in consecutive slots. In order to enable the repetitions within a slot, additional semi-static signalling is needed to switch between potentially new repetition behavior and the legacy behavior. In that case, the signalling may be a part the configured grant configuration signalling and be common for both Type <NUM> and Type <NUM> or may be conveyed as part of time domain resource allocation table where each entry may be associated with particular repetition type. If aggregation is configured, the semi-statically derived starting symbol and duration may be assumed to be repeated in consecutive K groups of valid symbols, where K is the aggregation factor configured by RRC. The first group of valid symbols is directly derived from the time domain resource allocation field which signals starting symbol and length in symbols. The other groups of symbols have the same length as the first one and starting symbol index derived as the next valid symbol after the previous group of symbols in an aggregation. In other words, the allocations are repeated back-to-back without gaps within the valid symbols.

<NPL> describes mini-slot-based repetitions within a slot, proposing that both Type <NUM> and Type <NUM> PUSCH transmissions with configured grant, more than one mini-slot-based repetition within a slot should be supported. For both Type <NUM> and Type <NUM> PUSCH transmissions with configured grant, the multiple TOs for mini-slot-based K (><NUM>) repetitions within a slot are configured as following: UE determines the first mini-slot-based transmission occasion in each period to start in a symbol and have a time duration of L consecutive symbols; each of the other K-<NUM> mini-slot-based transmission occasions in one period consisting of L consecutive symbols immediately follows the previous TO but without crossing a slot boundary. The document further proposes that for both Type <NUM> and Type <NUM> PUSCH transmissions with configured grant, for indication of the repetition scheme in terms of either slot-based or mini-slot-based repetitions: explicit indication by introducing a new RRC parameter, or implicit indication by comparing the resource periodicity P with a predefined value.

The above and other objects are achieved by a user equipment (UE) that communicates via mini-slot-based repetitions, a base station that communicates via mini-slot repetitions and a communication method of a user equipment that communicates via mini-slot repetitions as defined in the independent claims, respectively.

A user equipment (UE) is described. The UE includes receiving circuitry configured to receive signaling that includes a configuration for a grant-free physical uplink shared channel (PUSCH) or a configuration for grant-based PUSCH. The UE also includes a higher layer processor configured to determine whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a transport block (TB). The UE further includes transmitting circuitry configured to transmit the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions.

The slot-based PUSCH repetitions may include PUSCH repetitions that use consecutive slots and the same time-domain resource allocation (e.g., starting symbol and/ or length) may be applied to each slot. The mini-slot-based PUSCH repetitions may include multiple PUSCH repetitions in one slot. Additionally or alternatively, the mini-slot-based PUSCH repetitions may include PUSCH repetitions in consecutive available slots that use different starting symbols or different durations.

In an approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions may be explicitly configured by radio resource control (RRC). In another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions may be based on a repetition parameter. In another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions is based on a periodicity. In another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions is based on a modulation and coding scheme (MCS) table. In another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions is based on a radio network temporary identifier (RNTI). In another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions is based on a downlink control information (DCI) format. In yet another approach, whether to apply slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions is based a slot configuration.

A base station (gNB) is also described. The gNB includes transmitting circuitry configured to send, to a UE, signaling that includes a configuration for a grant-free PUSCH or a configuration for grant-based PUSCH. The gNB also includes a higher layer processor configured to determine whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a TB. The gNB further includes receiving circuitry configured to receive the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions from the UE.

A method by a UE is also described. The method includes receiving signaling that comprises a configuration for a grant-free PUSCH or a configuration for grant-based PUSCH. The method also includes determining whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a TB. The method further includes transmitting the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions.

A method by a gNB is also described. The method includes transmitting, to a UE, signaling that includes a configuration for a grant-free physical uplink shared channel (PUSCH) or a configuration for grant-based PUSCH. The method also includes determining whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a TB. The method further includes receiving the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions from the UE.

The 3rd Generation Partnership Project, also referred to as "3GPP," is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems and devices.

At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>). 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 utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a 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 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to mean the more general term "wireless communication device. " A UE may also be more generally referred to as a terminal device.

In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms "base station," "Node B," "eNB," "gNB" and/or "HeNB" may be used interchangeably herein to mean the more general term "base station. " Furthermore, the term "base station" may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device.

It should be noted that as used herein, a "cell" may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a "cell" may be defined as "combination of downlink and optionally uplink resources. " The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

"Configured cells" are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. "Configured cell(s)" may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. "Configured cell(s)" for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). "Activated cells" are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). "Deactivated cells" are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a "cell" may be described in terms of differing dimensions. For example, a "cell" may have temporal, spatial (e.g., geographical) and frequency characteristics.

Fifth generation (<NUM>) 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 allow for enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as massive machine type communication (MMTC) like services. A new radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as a base station device.

Some configurations of the systems and methods described herein teach approaches for URLLC transmission and/or retransmission management to meet the latency and/or reliability requirement. Some requirements for URLLC relate to user (U)-plane latency and reliability. For URLLC, the target user plane latency is <NUM> milliseconds (ms) each way for both UL and DL. The target reliability is <NUM>-<NUM>-<NUM> for X bytes within <NUM> milliseconds (ms).

These URLLC-specific constraints make the hybrid automatic repeat request (HARQ) and retransmission mechanism design difficult. For example, the receiver must reply with a quick acknowledgement (ACK) or negative acknowledgement (NACK) or an uplink grant to meet the latency requirement, or the transmitter can retransmit immediately without waiting for ACK/NACK to enhance the reliability. On the other, grant-based or grant-free repetitions are supported to further enhance the reliability. How to terminate the repetitions is also an important issue. The described systems and methods teach URLLC HARQ and/or retransmission design in different cases.

Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to be limiting, but is merely representative of the systems and methods.

<FIG> is a block diagram illustrating one implementation of one or more base stations (gNBs) <NUM> and one or more user equipments (UEs) <NUM> in which systems and methods that achieve mini-slot-based repetitions. The one or more UEs <NUM> communicate with one or more gNBs <NUM> using one or more antennas 122a-n. For example, a UE <NUM> transmits electromagnetic signals to the gNB <NUM> and receives electromagnetic signals from the gNB <NUM> using the one or more antennas 122a-n. The gNB <NUM> communicates with the UE <NUM> using one or more antennas 180a-n.

The UE <NUM> and the gNB <NUM> may use one or more channels <NUM>, <NUM> to communicate with each other. For example, a UE <NUM> may transmit information or data to the gNB <NUM> using one or more uplink channels <NUM>. Examples of uplink channels <NUM> include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels <NUM> (e.g., PUSCH) may be used for transmitting UL data (i.e., Transport Block(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).

Here, 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 for transmitting the URLLC data. For the sake of simple description, the term "PUSCH" may mean any of (<NUM>) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (<NUM>) PUSCH or URLLC-PUSCH, (<NUM>) PUSCH and URLLC-PUSCH, or (<NUM>) only URLLC-PUSCH (e.g., not regular PUSCH).

Also, for example, uplink channels <NUM> may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR). The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)).

The CSI may include information indicating a channel quality of downlink. The SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. Namely, the SR may be used for requesting UL resources for transmitting UL data.

The one or more gNBs <NUM> may also transmit information or data to the one or more UEs <NUM> using one or more downlink channels <NUM>, for instance. Examples of downlink channels <NUM> include a PDCCH, a PDSCH, etc. Other kinds of channels may be used. The PDCCH may be used for transmitting Downlink Control Information (DCI).

Each of the one or more UEs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a UE operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in the UE <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the UE <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the gNB <NUM> using one or more antennas 122a-n. For example, the receiver <NUM> may receive and down convert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the gNB <NUM> using one or more antennas 122a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The UE <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce decoded signals <NUM>, which may include a UE-decoded signal <NUM> (also referred to as a first UE-decoded signal <NUM>). For example, the first UE-decoded signal <NUM> may comprise received payload data, which may be stored in a data buffer <NUM>. Another signal included in the decoded signals <NUM> (also referred to as a second UE-decoded signal <NUM>) may comprise overhead data and/ or control data. For example, the second UE-decoded signal <NUM> may provide data that may be used by the UE operations module <NUM> to perform one or more operations.

In general, the UE operations module <NUM> may enable the UE <NUM> to communicate with the one or more gNBs <NUM>. The UE operations module <NUM> may include a UE scheduling module <NUM>.

The UE scheduling module <NUM> may perform operations for mini-slot-based repetitions. In new radio (NR), a UE <NUM> may support multiple types of UL transmissions (PUSCH transmissions). The UL transmissions may include grant-based UL transmissions (e.g., UL transmissions with grant, dynamic grants, PUSCH transmissions with grant, PUSCH transmission scheduled by DCI (e.g., DCI format 0_0, DCI format 0_1)) and grant-free UL transmissions (e.g., UL transmissions without grant, configured grants, PUSCH transmissions with configured grant).

There may be two types of grant-free UL transmissions (e.g., UL transmissions without grant, with configured grants, PUSCH transmissions with configured grant). One type of grant-free UL transmission is a configured grant Type <NUM> and the other is configured grant Type <NUM>.

For Type <NUM> PUSCH transmissions with a configured grant, related parameters may be fully RRC-configured (e.g., configured by using RRC signaling). For example, parameters for resource allocation, such as time domain resource allocation (e.g., time-Domain Offset, timeDomainAllocation), frequency domain resource allocation (frequencyDomainAllocation), modulation and coding scheme (MCS) (e.g., mcsAndTBS), the antenna port value, the bit value for DMRS sequence initialization, precoding information and number of layers, SRS resource indicator (provided by antennaPort, dmrs-Seqlnitialization, precodingAndNumberOfLayers, and srs-Resourcelndicator respectively), the frequency offset between two frequency hops (frequencyHoppingOffset), etc., may be provided by RRC message (rrc-ConfiguredUplinkGrant).

Activation (e.g., PDCCH, DCI activation) may not be used for Type <NUM> configured grant. Namely, for configured grant Type <NUM>, an uplink grant is provided by RRC, and stored as configured uplink grant. The retransmission of configured grant type <NUM> may be scheduled by PDCCH with CRC scrambled by CS-RNTI (Configured Scheduling RNTI).

For Type <NUM> PUSCH transmissions with a configured grant, the related parameters follow the higher layer configuration (e.g., periodicity, the number of repetitions, etc.), and UL grant received on the DCI addressed to CS-RNTI (PDCCH with CRC scrambled by CS-RNTI, L1 activation and/or reactivation). Namely, for configured grant Type <NUM>, an uplink grant may be provided by PDCCH, and stored or cleared as a configured uplink grant based on L1 signaling indicating configured uplink grant activation or deactivation.

The retransmission of configured grant type <NUM> may be scheduled by PDCCH with CRC scrambled by CS-RNTI. Namely, retransmissions except for repetition of configured uplink grants may use uplink grants addressed to CS-RNTI. The UE <NUM> may not transmit anything on the resources configured for PUSCH transmissions with configured grant if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant.

Therefore, in NR, a UE <NUM> may support multiple types of uplink transmissions without grant (also referred to as grant-free (GF) uplink transmission or GF transmission or transmission by configured grant). A first type (Type <NUM>) of GF transmission may be a UL data transmission without grant that is only based on RRC (re)configuration without any L1 signaling. In a second type (Type <NUM>) of GF transmission, UL data transmission without grant is based on both RRC configuration and LI signaling for activation and/or deactivation for UL data transmission without grant. An example for RRC configuration is shown in Listing <NUM>.

For Type <NUM>, PDCCH activation is needed. Listing <NUM> and Listing <NUM> show examples of DCI format 0_0 (e.g., fallback DCI) and format 0_1, which may be used for activation of a Type <NUM> configured grant, and/or retransmission of Type <NUM> configured grant and/or Type <NUM> configured grant.

For both Type <NUM> and Type <NUM> PUSCH transmissions with a configured grant, when the UE <NUM> is configured with repK > <NUM>, the UE <NUM> may repeat the TB across the repK consecutive slots applying the same symbol allocation in each slot. The parameter repK may be referred as the configured number of transmission occasions for repetitions (including initial transmission) for a TB. If the UE procedure for determining slot configuration determines symbols of a slot allocated for PUSCH as downlink symbols, the transmission on that slot may be omitted for multi-slot PUSCH transmission.

For grant-based transmission, PUSCH transmission is scheduled by DCI (e.g., the DCI format 0_0 and the DCI format 0_1 shown above). The PUSCH may be assigned (e.g., scheduled) by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, a new-RNTI (e.g., a first RNTI), TC-RNTI, or SP-CSI-RNTI. The new-RNTI may be called MCS-C-RNTI in specifications. Some UE-specific PUSCH parameters may be configured by RRC. An example for RRC configuration is shown in Listing <NUM>. For example, pusch-AggregationFactor in PUSCH-Config indicates number of repetitions for data. When the UE <NUM> is configured with pusch-AggregationFactor > <NUM>, the same symbol allocation may be applied across the pusch-AggregationFactor consecutive slots and the PUSCH may be limited to a single transmission layer. The UE <NUM> may repeat the transport block (TB) across the pusch-AggregationFactor consecutive slots applying the same symbol allocation in each slot. If the UE procedure for determining the slot configuration, determines symbols of a slot allocated for PUSCH as downlink symbols, the transmission on that slot may be omitted for multi-slot PUSCH transmission.

For the PUSCH retransmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with new data indicator (NDI) equal to <NUM> (i.e., NDI=<NUM>), if the UE <NUM> is configured with pusch-AggregationFactor, the same symbol allocation may be applied across the pusch-AggregationFactor consecutive slots and the PUSCH may be limited to a single transmission layer. The UE <NUM> may repeat the TB across the pusch-AggregationFactor consecutive slots applying the same symbol allocation in each slot.

As mentioned above, for both grant-free transmission and grant-based transmission, if repetitions are configured, 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, which may be referred as slot-based repetitions herein. In another design, two or more PUSCH repetitions may be in one slot, or across a slot boundary in consecutive available slots. In yet another design, two or more PUSCH repetitions in consecutive available slots may be with one repetition in each slot with possibly different starting symbols and/or durations. The two or more PUSCH repetitions in one slot, or across a slot boundary in consecutive available slots, and/or two or more PUSCH repetitions in consecutive available slot (with possibly different starting symbols and/or durations) may be referred as mini-slot based repetitions.

Namely, for the slot-based repetitions, only one transmission occasion may be scheduled (e.g., allocated) within a slot (e.g., <NUM> OFDM symbols and/or <NUM> SC-FDMA symbols). Here, one transmission occasion may be corresponding to the PUSCH resources to be applied for the PUSCH transmission. And, the PUSCH resources (e.g., the one transmission occasion) may be identified (e.g., indicated, defined) by using the time-domain resource allocation. For example, the PUSCH resources (e.g., the one transmission occasion) may be identified by using the starting symbol and/or the length (i.e., the starting symbols and/or the length of the PUSCH resources). For example, for the slot-based repetitions, the same one transmission occasion may be used in the slot, wherein the same one transmission occasion may be applied for each consecutive slot.

Additionally or alternatively, for the mini-slot based repetitions, two or more transmission occasions may be allocated within a slot. Here, each transmission occasion may be corresponding to the PUSCH resources to be applied for the PUSCH transmission. For example, two or more time-domain resource allocations (two or more values of the starting symbols and/or two or more values of the length) are used for scheduling of the PUSCH resources (e.g., the transmission occasions) in the slot. And, each PUSCH resource (e.g., each transmission occasion) may be identified by using each time-domain resource allocation. For example, the PUSCH resources (e.g., each transmission occasion) may be identified by using each value of the starting symbol and/or each value of the length. For example, for the mini-slot based repetitions, the two or more transmission occasions may be used in the slot, wherein each of the two or more transmission occasions may be identified by using each starting symbol and/or each length. Namely, different starting symbol(s) and/or different length(s) may be applied for the two or more transmission occasions in the slot.

Additionally or alternatively, for the mini-slot based repetitions, each transmission occasion identified by using each starting symbol and/or each length may be applied for each slot (e.g., each consecutive slot). Namely, different starting symbol(s) and/or different length(s) may be applied for two or more transmission occasions in two or more slot.

In an example, if the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that two or more PUSCH repetitions are allowed to perform in one slot, after one of repetitions (including initial transmission) for a TB is finished in a slot, the immediately next repetition may use the remaining available symbols in the slot. Namely, in the slot, the transmission occasion(s) (e.g., the remaining available symbol(s)) may be used for the repetitions (e.g., the next repetition in the slot). As described above, the available symbols (e.g., the transmission occasion) may be defined as L_r consecutive uplink symbols (i.e., consecutive symbols) started from symbol S_r (i.e., starting symbols), where symbol S_r may be defined as the first uplink symbol (or the first uplink symbol of first L_r consecutive uplink symbols in the slot) and L_r is defined as the length of the repetition or initial transmission (e.g., symbol(s)). For example, for a second transmission of the repetitions in a slot, the symbols S_r may be defined as the first uplink symbol after a first transmission of the repetitions in the slot is performed (or the first uplink symbol of first L_r consecutive uplink symbols after a first transmission of the repetitions in the slot is performed, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>). If there are no L_r consecutive uplink symbols in the slot (e.g., after the first transmission of the repetitions in the slot is performed) according to the UE procedure for determining slot configuration, the immediately next repetition (e.g., the second transmission of the repetitions in the slot) may be skipped in the slot (e.g., dropped in the slot, not performed in the slot) or the immediately next repetition in the slot may be omitted (e.g., omitted in the slot).

Namely, the gNB <NUM> may configure, by using the RRC message, information used for configuring that the mini-slot based repetitions are performed. And, in a case that the mini-slot based repetitions are performed, if there is no transmission occasion for a transmission in the slot, the UE <NUM> may skip (e.g., drop, not perform, and/or omit) the transmission. Here, as described above, the transmission occasion (e.g., each transmission occasion in the slot) may be identified (e.g., indicated by the gNB <NUM> using the DCI format 0_0 and/or 0_1) by using the time domain resource allocation (e.g., each time domain resource allocation (e.g., each starting symbol and/or each length)). Namely, the UE <NUM> may perform, in the slot, the transmission of the repetitions (e.g., the first transmission of the repetitions, the transmission in the repetitions) on the transmission occasion (i.e., if the transmission occasion is identified by using the time domain resource allocation). Also, the UE <NUM> may skip, in the slot, the transmission of the repetitions (e.g., the second transmission of the repetitions, the transmission in the repetitions) if there are no transmission occasion (i.e., if there are no transmission occasion identified based on the time domain resource allocation).

In yet another design, the available symbols (e.g., transmission occasion) may be defined as L_r consecutive symbols (uplink symbols and/or flexible symbols) started from symbol S_r, where symbol S_r is the first symbol (uplink symbol and/or flexible symbol) after the repetition in the slot (or the first symbol (uplink symbols and/or flexible symbols) of first L_r consecutive symbols (uplink symbols and/or flexible symbols) after the repetition in the slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>) and L_r is the length of the repetition or initial transmission. If there are no L_r consecutive symbols (uplink symbols and/or flexible symbols) in the slot after the repetition according to the UE procedure for determining slot configuration, the immediately next repetition may skip the slot or the immediately next repetition in the slot may be omitted. Namely, L_r consecutive symbols may include uplink symbols and/or flexible symbols.

In yet another example, if the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that two or more PUSCH repetitions are allowed to perform in one slot and different repetitions may use different lengths (numbers of symbols), after one of repetitions (including initial transmission) for a TB is finished in a slot, the immediately next repetition may use the remaining available symbols in the slot. The available symbols (e.g., transmission occasion) may be defined as L_rd consecutive uplink symbols started from symbol S_rd, where symbol S_rd is the first uplink symbol after the repetition in the slot (or the first uplink symbol of first L_rd consecutive uplink symbols after the repetition in the slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>) 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 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., <NUM>, <NUM>, -<NUM>, -<NUM>, <NUM>)). L_rd may be determined by the slot configuration (e.g., L_rd is the number of remaining consecutive uplink symbols in the slot). If there are no L_rd consecutive uplink symbols in the slot after the repetition according to the UE procedure for determining slot configuration, the immediately next repetition may skip the slot or the immediately next repetition in the slot may be omitted.

In yet another design, the available symbols (e.g., transmission occasion) may be defined as L_rd consecutive symbols (uplink symbols and/or flexible symbols) started from symbol S_rd, where symbol S_rd is the first symbol (uplink symbol and/or flexible symbol) after the repetition in the slot (or the first symbol (uplink symbols and/or flexible symbols) of first L_rd consecutive symbols (uplink symbols and/or flexible symbols) after the repetition in the slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>) 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 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., <NUM>, <NUM>, -<NUM>, -<NUM>, <NUM>)). L_rd may be determined by the slot configuration (e.g., L_rd may be the number of remaining consecutive uplink symbols and/or flexible symbols in the slot). If there are no L_rd consecutive symbols (uplink symbols and/or flexible symbols) in the slot after the repetition according to the UE procedure for determining slot configuration, the immediately next repetition may skip the slot or the immediately next repetition in the slot may be omitted.

When the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that two or more PUSCH repetitions are allowed to perform in one slot, the two or more PUSCH repetitions may or may not share a demodulation reference signal (DMRS (e.g., DMRS associated with the PUSCH transmission)). Whether the two or more PUSCH repetitions share DMRS or not may be configured by RRC, or indicated by L1/L2 signaling. For example, if the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that two or more PUSCH repetitions are allowed to perform in one slot and two or more PUSCH repetitions may share DMRS, the DMRS of the first repetition in the slot may be reused by the following repetition(s) in the slot. Namely, the gNB <NUM> may transmit, by using the RRC message and/or the DCI format(s) (e.g., the DCI format 0_0 and/or 0_l), information used for indicating that whether the DMRS(s) associated with the PUSCH transmission is shared for the repetitions or not in the slot (and/or across the slots).

For repetitions in consecutive slots, the same start symbol may or may not be applied in each slot. Namely, after one or more repetitions of a TB in a slot is finished, the repetition in the next slot may start at a symbol, which may be different from the start symbol of repetition(s) in previous slot(s), the start symbol of initial transmission, the start symbol indicated by PDCCH (e.g., Type <NUM> configured grant activation), or the start symbol configured by RRC (e.g., Type <NUM> configured grant configuration).

In an example, if the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that PUSCH repetition(s) in consecutive slot(s) are allowed to start at a different symbol and the length of repetition(s) should keep the same, after one or more of repetitions (including initial transmission) for a TB is finished in a slot, the next repetition in the consecutive slot may start at symbol S_d in the consecutive slot. The start symbol S_d may be defined as the first uplink symbol in the consecutive slot according to the UE procedure for determining slot configuration or the first symbol of available symbols for the repetition in the consecutive slot (or the first symbol of first L_r consecutive uplink symbols in the consecutive slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, or an indicated start position by RRC or L1/L2 signaling). The available symbols (e.g., transmission occasion) for the repetition in the consecutive slot may be defined as L_r consecutive uplink in the consecutive slot, where L_r is the length of the repetition in the previous slot or initial transmission or the length configured by RRC (e.g., Type <NUM> configured grant configuration) or indicated by PDCCH (e.g., Type <NUM> configured grant activation). If there are no L_r consecutive uplink symbols in the consecutive slot after the repetition according to the UE procedure for determining slot configuration, the next repetition in the consecutive slot may skip the slot or the next repetition in the consecutive slot may be omitted.

In yet another design, the start symbol S_d may be defined as the first uplink and/or flexible symbol in the consecutive slot according to the UE procedure for determining slot configuration or the first symbol of available symbols for the repetition in the consecutive slot (or the first symbol of first L_r consecutive symbols (uplink symbols and/ or flexible symbols) in the consecutive slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, or an indicated start position by RRC or L1/L2 signaling). The available symbols (e.g., transmission occasion) in the consecutive slot may be defined as L_r consecutive symbols (uplink symbols and/or flexible symbols) in the consecutive slot, where L_r is the length of the repetition in the previous slot or initial transmission or the length configured by RRC (e.g., Type <NUM> configured grant configuration) or indicated by PDCCH (e.g., Type <NUM> configured grant activation). If there are no L_r consecutive symbols (uplink symbols and/or flexible symbols) in the consecutive slot according to the UE procedure for determining slot configuration, the next repetition in the consecutive slot may skip the slot or the next repetition in the consecutive slot may be omitted.

In yet another example, if the UE <NUM> is configured by RRC, or indicated by L1/L2 signaling, that PUSCH repetition(s) in consecutive slot(s) are allowed to start at a different symbol and the length of repetition(s) can be different, after one or more of repetitions (including initial transmission) for a TB is finished in a slot, the next repetition in the consecutive slot may start at symbol S_d in the consecutive slot. The start symbol S_d may be defined as the first uplink symbol in the consecutive slot according to the UE procedure for determining slot configuration or the first symbol of available symbols for the repetition in the consecutive slot (or the first symbol of first L_rd consecutive uplink symbols in the consecutive slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, or an indicated start position by RRC or L1/L2 signaling). The available symbols (e.g., transmission occasion) for the repetition in the consecutive slot may be defined as L_rd consecutive uplink in the consecutive slot, where L_rd may be a different length compared to the length of the repetition in a previous slot or initial transmission or the length configured by RRC (e.g., Type <NUM> configured grant configuration) or indicated by PDCCH (e.g., Type <NUM> configured grant activation), which is denoted by L_r. L_rd may be configured by RRC or indicated by L1/L2 signaling or fixed by 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., <NUM>, <NUM>, -<NUM>, -<NUM>, <NUM>)). L_rd may be determined by the slot configuration (e.g., L_rd is the number of consecutive uplink symbols in the consecutive slot, or the maximum number of consecutive uplink symbols in the consecutive slot). If there are no L_rd consecutive uplink symbols in the consecutive slot according to the UE procedure for determining slot configuration, the next repetition in the consecutive slot may skip the slot or the next repetition in the consecutive slot may be omitted.

In yet another design, the start symbol S_d may be defined as the first uplink and/or flexible symbol in the consecutive slot according to the UE procedure for determining slot configuration or the first symbol of available symbols for the repetition in the consecutive slot (or the first symbol of first L_rd consecutive symbols (uplink symbols and/or flexible symbols) in the consecutive slot, or a predefined start position, e.g., symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, symbol #<NUM>, or an indicated start position by RRC or L1/L2 signaling). The available symbols (e.g., transmission occasion) in the consecutive slot may be defined as L_rd consecutive symbols (uplink symbols and/or flexible symbols) in the consecutive slot, where L_rd may be a different length compared to the length of the repetition in the previous slot or initial transmission or the length configured by RRC (e.g., Type <NUM> configured grant configuration) or indicated by PDCCH (e.g., Type <NUM> configured grant activation), which is denoted by L_r. L_rd may be configured by RRC or indicated by L1/L2 signaling or fixed by 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., <NUM>, <NUM>, -<NUM>, -<NUM>, <NUM>). L_rd may be determined by the slot configuration (e.g., L_rd is the number of consecutive uplink and/or flexible symbols in the consecutive slot, or the maximum number of consecutive uplink and/or flexible symbols in the consecutive slot). If there are no L_rd consecutive symbols (uplink symbols and/or flexible symbols) in the consecutive slot according to the UE procedure for determining slot configuration, the next repetition in the consecutive slot may skip the slot or the next repetition in the consecutive slot may be omitted.

PUSCH preparation time N_2 [symbols] may be defined as the minimum time for the UE <NUM> to prepare PUSCH for a TB. N_2 may be determined by numerology and/ or UE capability. N_2 may be defined in the specification and/or configured by RRC and/or indicated by L1/L2 signaling. PUSCH preparation time for a repetition which is not an initial transmission may or may not be same as the PUSCH preparation time for the initial transmission. The PUSCH preparation time for a repetition which is not an initial transmission may be denoted by N_2r. N_2r may be determined by numerology and/or UE capability. N_2r may be defined in the specification and/or configured by RRC and/or indicated by L1/L2 signaling.

If a UE <NUM> is configured by higher layers to transmit PUSCH repetition (which may not be an initial transmission) in a set of symbols of a slot as mentioned above and the UE <NUM> detects a DCI format l_0, DCI format 1_1, or DCI format 0_l indicating to the UE <NUM> to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then the UE <NUM> does not expect to cancel the transmission in symbols from the subset of symbols that occur, relative to a last symbol of a control resource set where the UE <NUM> detects the DCI format l_0 or the DCI format 1_1 or the DCI format 0_l, after a number of symbols that is smaller than the PUSCH preparation time for the repetition as mentioned above, or the UE <NUM> cancels the PUSCH repetition in remaining symbols from the set of symbols.

If a UE <NUM> is scheduled by a DCI transmit PUSCH over multiple slots and different start symbols and/or lengths may be applied for each repetition as mentioned above, and if a higher layer parameter, when provided to the UE <NUM>, indicates that, for a slot from the multiple slots, at least one symbol from a set of symbols where the UE <NUM> is scheduled PUSCH transmission in the slot is a downlink symbol, the UE <NUM> does not transmit the PUSCH in the slot.

For a set of symbols of a slot indicated to a UE <NUM> as flexible by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated), when provided to the UE <NUM>, or when higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are not provided to the UE <NUM>, and if the UE <NUM> detects a DCI format 2_0 providing a format for the slot using a slot format value (e.g., other than <NUM>), if the UE <NUM> is configured by higher layers to transmit PUSCH repetition in the set of symbols of the slot as mentioned above, then the UE <NUM> may transmit the PUSCH repetition in the slot only if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as uplink.

The UE <NUM> may not expect to detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as downlink or flexible if the set of symbols of the slot includes symbols corresponding to any repetition of a PUSCH transmission as mentioned above.

If a UE <NUM> is configured by higher layers to transmit a PUSCH repetition in a set of symbols of a slot as mentioned above and the UE <NUM> detects a DCI format 2_0 with a slot format value (e.g., other than <NUM>) that indicates a slot format with a subset of symbols from the set of symbols as downlink or flexible, or the UE <NUM> detects a DCI format l_0, DCI format 1_1, or DCI format 0_l indicating to the UE <NUM> to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then the UE <NUM> may not expect to cancel the transmission in symbols from the subset of symbols that occur, relative to a last symbol of a CORESET where the UE <NUM> detects the DCI format 2_0 or the DCI format l_0 or the DCI format 1_1 or the DCI format 0_1 after a number of symbols that is smaller than the PUSCH preparation time for the repetition as mentioned above, or the UE <NUM> cancels the PUSCH repetition in remaining symbols from the set of symbols.

For a set of symbols of a slot that are indicated as flexible by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated), when provided to a UE <NUM>, or when higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are not provided to the UE <NUM>, and if the UE <NUM> does not detect a DCI format 2_0 providing a slot format for the slot, if the UE <NUM> is configured by higher layers to transmit PUSCH repetition in the set of symbols of the slot as mentioned above, the UE <NUM> may not transmit the PUSCH repetition in the slot in symbols from the set of symbols in the slot, if any, starting from a symbol that is a number of symbols equal to the PUSCH preparation time N_2r for the corresponding PUSCH timing capability after a last symbol of a control resource set where the UE <NUM> is configured to monitor PDCCH for DCI format 2_0, or the UE <NUM> may not expect to cancel the transmission of the PUSCH repetition in symbols from the set of symbols in the slot, if any, starting before a symbol that is a number of symbols equal to the PUSCH preparation time N_2r for the corresponding PUSCH timing capability after a last symbol of a CORESET where the UE is configured to monitor PDCCH for DCI format 2_0.

As mentioned above, there may be two kinds of PUSCH repetitions. One may be referred to as slot-based repetition(s), which means 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 as mini-slot-based repetition(s), which means multiple PUSCH repetitions may be in one slot and/or PUSCH repetitions in consecutive available slots may use different starting symbols and/or durations/lengths.

Whether to apply slot-based repetitions or mini-slot-based repetitions and/or how to switch between slot-based repetitions and mini-slot-based repetitions is described herein.

In a design, whether to apply slot-based repetitions or mini-slot-based repetitions may be explicitly configured by RRC. For example, for a grant-free PUSCH transmission (e.g., Type <NUM> configured grant or Type <NUM> configured grant), if an RRC parameter mini-slot-repetition-enabler in a configured grant configuration (e.g., ConfiguredGrantConfig) is configured or indicated as true, mini-slot-based repetitions may be applied. If the RRC parameter mini-slot-repetition-enabler in a configured grant configuration (e.g., ConfiguredGrantConfig) is not configured or it is indicated as false, slot-based repetitions may be applied. For grant-based PUSCH transmission (e.g., PUSCH assigned (e.g., scheduled) by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if a RRC parameter mini-slot-repetition-enabler in PUSCH configuration (e.g., PUSCH-Config) is configured or indicated as true, mini-slot-based repetitions may be applied. If the RRC parameter mini-slot-repetition-enabler in PUSCH configuration (e.g., PUSCH-Config) is not configured or it is indicated as false, slot-based repetitions may be applied. For retransmission of grant-free transmission (e.g., PUSCH scheduled by a DCI format 0_0/0_l with CRC scrambled by CS-RNTI with NDI=<NUM>), whether to apply slot-based repetitions or mini-slot-based repetitions may follow the RRC parameter in a configured grant configuration as above or follow the RRC parameter in PUSCH configuration as above.

In yet another design, slot-based repetitions and mini-slot-based repetitions may use different parameters indicating the number of repetitions (also referred to herein as a repetition parameter). For example, for a grant-free PUSCH transmission (e.g., Type <NUM> configured grant or Type <NUM> configured grant), if a RRC parameter repK-new (indicating the number of repetitions for mini-slot-based repetitions) which is different from repK (indicating the number of repetitions for slot-based repetitions) in a configured grant configuration (e.g., ConfiguredGrantConfig) is configured and/or indicated as greater than <NUM>, mini-slot-based repetitions may be applied. If both repK-new and repK are configured, repK-new may override repK and/or mini-slot-based repetitions may be applied. In yet another example, if both repK-new and repK are configured, repK may override repK-new and/or slot-based repetitions may be applied.

For grant-based PUSCH transmission (e.g., PUSCH assigned (e.g., scheduled) by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if a RRC parameter pusch-AggregationFactor-new (indicating the number of repetitions for mini-slot-based repetitions) which is different from pusch-AggregationFactor (indicating the number of repetitions for slot-based repetitions) in PUSCH configuration (e.g., PUSCH-Config) is configured and/or indicated as greater than <NUM>, mini-slot-based repetitions may be applied. If both pusch-AggregationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor-new may override pusch-AggregationFactor and/or mini-slot-based repetitions may be applied. In yet another example, if both pusch-AggregationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor may override pusch-AggregationFactor-new and/or slot-based repetitions may be applied. For retransmission of a grant-free transmission (e.g., PUSCH scheduled by a DCI format 0_0/0_1 with CRC scrambled by CS-RNTI with NDI=<NUM>), whether to apply slot-based repetitions or mini-slot-based repetitions may follow the RRC parameter in a configured grant configuration as above or may follow the RRC parameter in PUSCH configuration as above.

In yet another design, whether to apply slot-based repetitions or mini-slot-based repetitions may depend on a periodicity parameter. For example, for grant-free PUSCH transmission (e.g., Type <NUM> configured grant or Type <NUM> configured grant), if a RRC parameter periodicity in a configured grant configuration (e.g., Configured-GrantConfig) is greater than (or less than) a threshold, mini-slot-based repetitions may be applied. If the RRC parameter periodicity in configured grant configuration (e.g., ConfiguredGrantConfig) is less than (or greater than) a threshold, slot-based repetitions may be applied.

In yet another design, whether to apply slot-based repetitions or mini-slot-based repetitions may depend on a modulation and coding scheme (MCS) table. For example, for a grant-free PUSCH transmission (e.g., Type <NUM> configured grant or Type <NUM> configured grant) and/or retransmission of a grant-free transmission (e.g., PUSCH scheduled by a DCI format 0_0/0_l with CRC scrambled by CS-RNTI with NDI=<NUM>), if a low spectral efficiency (SE) MCS table is configured (e.g., a RRC parameter mcs-Table or mcs-TableTransformPrecoder in configured grant configuration (e.g., ConfiguredGrantConfig) is configured as qam64LowSE), mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another design, if a low SE MCS table is configured (e.g., a RRC parameter mcs-Table or mcs-TableTransformPrecoder in configured grant configuration (e.g., Configured-GrantConfig) is configured as qam64LowSE), slot-based repetitions may be applied, otherwise, mini-slot-based repetitions may be applied. For grant-based PUSCH transmission (e.g., PUSCH assigned (e.g., scheduled) by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI. ), if a low SE MCS table is configured (e.g., a RRC parameter mcs-Table or mcs-TableTransformPrecoder in PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another design, if low SE MCS table is configured (e.g., a RRC parameter mcs-Table or mcs-TableTransformPrecoder in PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), slot-based repetitions may be applied, otherwise, mini-slot-based repetitions may be applied.

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

In yet another design, whether to apply slot-based repetitions or mini-slot-based repetitions may depend on a downlink control information (DCI) format. For example, mini-slot-based repetitions 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 repetitions. Namely, for PUSCH transmission scheduled by the new DCI format and/or grant-free transmission activated by the new DCI format, mini-slot-based repetitions may be applied when repetitions are enabled. The new DCI-format may include an indication for mini-slot-repetitions and/or a parameter indicating a number of mini-slot-based repetitions.

In yet another design, whether to apply slot-based repetitions or mini-slot-based repetitions may depend on a slot configuration. For example, if a slot configuration period configured by RRC is larger than (or smaller than) a threshold, mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another example, if a number of slots with only downlink symbols configured by RRC is larger than (or smaller than) a threshold, mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another example, if a number of slots with only uplink symbols configured by RRC is larger than (or smaller than) a threshold, mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another example, if a number of downlink symbols configured by RRC is larger than (or smaller than) a threshold, mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied. In yet another example, if a number of uplink symbols configured by RRC is larger than (or smaller than) a threshold, mini-slot-based repetitions may be applied, otherwise, slot-based repetitions may be applied.

When mini-slot-based repetitions are configured and/or enabled as mentioned above, fallback behavior (e.g., slot-based repetitions may be applied even if mini-slot-based repetitions are configured/enabled) may be supported in some cases. In a design, if the UE <NUM> detects fallback DCI (e.g., DCI format 0_0) in CSS (e.g., CORESET #<NUM>), the UE <NUM> may perform slot-based repetitions even if mini-slot-based repetitions are configured/enabled as mentioned above. For example, if mini-slot-based repetitions are configured by RRC, if the UE <NUM> detects fallback DCI (e.g., DCI format 0_0) in CSS (e.g., CORESET #<NUM>), the UE <NUM> may perform slot-based repetitions. If both repK-new (pusch-AggregationFactor-new) and repK (pusch-AggregationFactor) are configured, in the case that the UE <NUM> detects fallback DCI (e.g., DCI format 0_0) in CSS (e.g., CORESET #<NUM>), the UE <NUM> may perform slot-based repetitions and the repetition number repK (pusch-AggregationFactor) may be applied. In yet another design, the UE <NUM> may perform slot-based repetitions according to RNTI. For example, if a new RNTI (e.g., REP-C-RNTI) is configured for mini-slot-based repetitions but the UE <NUM> detects a DCI with CRC scrambled by a different RNTI (e.g., C-RNTI), the UE <NUM> may perform slot-based repetitions.

Namely, in a case that the DCI format 0_0 is detected in the CSS, the slot-based repetition may be used. For example, even if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format 0_0 is detected in the CSS, the UE <NUM> may perform the slot-based repetitions. Namely, if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) is detected in the USS, the UE <NUM> may perform the mini slot-based repetitions.

X[<NUM>] Additionally or alternatively, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_l) is detected in the CORESET #<NUM> (i.e., the CORESET with the index "<NUM>"), the slot-based repetition may be used. For example, even if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) is detected in the CORESET #<NUM>, the UE <NUM> may perform the slot-based repetitions. Namely, if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) is detected in the CORESET other than in the CORESET #<NUM>, the UE <NUM> may perform the mini slot-based repetitions.

Additionally or alternatively, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_l) is detected in the search space set #<NUM> (i.e., the search space set with the index "<NUM>"), the slot-based repetition may be used. For example, even if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) is detected in the search space set #<NUM>, the UE <NUM> may perform the slot-based repetitions. Namely, if the mini-slot based repetitions are configured as being enabled, in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) is detected in the search space set other than the search space set #<NUM>, the UE <NUM> may perform the mini slot-based repetitions.

The UE operations module <NUM> may provide information <NUM> to the one or more receivers <NUM>. For example, the UE operations module <NUM> may inform the receiver(s) <NUM> when to receive retransmissions.

The UE operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the UE operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the UE operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the UE operations module <NUM> may instruct the encoder <NUM> to encode transmission data <NUM> and/or other information <NUM>. The other information <NUM> may include PDSCH HARQ-ACK information.

The UE operations module <NUM> may provide information <NUM> to the modulator <NUM>. For example, the UE operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The UE operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the UE operations module <NUM> may instruct the one or more transmitters <NUM> when to transmit a signal to the gNB <NUM>. For instance, the one or more transmitters <NUM> may transmit during a UL subframe. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more gNBs <NUM>.

Each of the one or more gNBs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a gNB operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in a gNB <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the gNB <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the UE <NUM> using one or more antennas 180a-n. For example, the receiver <NUM> may receive and down convert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the UE <NUM> using one or more antennas 180a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The gNB <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce one or more decoded signals <NUM>, <NUM>. For example, a first eNB-decoded signal <NUM> may comprise received pay load data, which may be stored in a data buffer <NUM>. A second eNB-decoded signal <NUM> may comprise overhead data and/or control data. For example, the second eNB-decoded signal <NUM> may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module <NUM> to perform one or more operations.

In general, the gNB operations module <NUM> may enable the gNB <NUM> to communicate with the one or more UEs <NUM>. The gNB operations module <NUM> may include a gNB scheduling module <NUM>. The gNB scheduling module <NUM> may perform operations for mini-slot-based repetitions as described herein.

The gNB operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the gNB operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the gNB operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the gNB operations module <NUM> may instruct the encoder <NUM> to encode information <NUM>, including transmission data <NUM>.

The encoder <NUM> may encode transmission data <NUM> and/or other information included in the information <NUM> provided by the gNB operations module <NUM>. For example, encoding the data <NUM> and/or other information included in the information <NUM> may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder <NUM> may provide encoded data <NUM> to the modulator <NUM>. The transmission data <NUM> may include network data to be relayed to the UE <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the modulator <NUM>. This information <NUM> may include instructions for the modulator <NUM>. For example, the gNB operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the gNB operations module <NUM> may instruct the one or more transmitters <NUM> when to (or when not to) transmit a signal to the UE(s) <NUM>. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more UEs <NUM>.

It should be noted that a DL subframe may be transmitted from the gNB <NUM> to one or more UEs <NUM> and that a UL subframe may be transmitted from one or more UEs <NUM> to the gNB <NUM>. Furthermore, both the gNB <NUM> and the one or more UEs <NUM> may transmit data in a standard special subframe.

It should also be noted that one or more of the elements or parts thereof included in the eNB(s) <NUM> and UE(s) <NUM> may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

URLLC may coexist with other services (e.g., eMBB). Due to the latency requirement, URLLC may have a highest priority in some approaches. Some examples of URLLC coexistence with other services are given herein (e.g., in one or more of the following Figure descriptions).

<FIG> is a diagram illustrating one example of a resource grid for the downlink. The resource grid illustrated in <FIG> may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with <FIG>.

In <FIG>, one downlink subframe <NUM> may include two downlink slots <NUM>. NDLRB is downlink bandwidth configuration of the serving cell, expressed in multiples of NRBSC, where NRBSC is a resource block <NUM> size in the frequency domain expressed as a number of subcarriers, and NDLsymb is the number of OFDM symbols <NUM> in a downlink slot <NUM>. A resource block <NUM> may include a number of resource elements (RE) <NUM>.

For a PCell, NDLRB is broadcast as a part of system information. For an SCell (including an Licensed Assisted Access (LAA) SCell), NDLRB is configured by a RRC message dedicated to a UE <NUM>. For PDSCH mapping, the available RE <NUM> may be the RE <NUM> whose index <NUM> fulfils l ≧ ldata,start and/or ldata,start≧l in a subframe.

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

The downlink RB includes twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in time domain. A region defined by one sub-carrier in frequency domain and one OFDM symbol in time domain is referred to as a resource element (RE) and is uniquely identified by the index pair (k,l) in a slot, where k and <NUM> are indices in the frequency and time domains, respectively. While downlink subframes in one component carrier (CC) are discussed herein, downlink subframes are defined for each CC and downlink subframes are substantially in synchronization with each other among CCs.

<FIG> is a diagram illustrating one example of a resource grid for the uplink. The resource grid illustrated in <FIG> may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with <FIG>.

In <FIG>, one uplink subframe <NUM> may include two uplink slots <NUM>. NULRB is uplink bandwidth configuration of the serving cell, expressed in multiples of NRBSC, where NRBSC is a resource block <NUM> size in the frequency domain expressed as a number of subcarriers, and NULsymb is the number of SC-FDMA symbols <NUM> in an uplink slot <NUM>. A resource block <NUM> may include a number of resource elements (RE) <NUM>.

For a PCell, NULRB is broadcast as a part of system information. For an SCell (including an EAA SCell), NULRB is configured by a RRC message dedicated to a UE <NUM>.

In the uplink, in addition to CP-OFDM, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) access scheme may be employed, which is also referred to as Discrete Fourier Transform-Spreading OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH and the like may be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. The uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair includes two uplink RBs that are continuous in the time domain.

The uplink RB may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM and/or DFT-S-OFDM symbols in time domain. A region defined by one sub-carrier in the frequency domain and one OFDM and/or DFT-S-OFDM symbol in the time domain is referred to as a RE and is uniquely identified by the index pair (k,l) in a slot, where k and <NUM> are indices in the frequency and time domains, respectively. While uplink subframes in one component carrier (CC) are discussed herein, uplink subframes are defined for each CC.

<FIG> shows examples of several numerologies <NUM>. The numerology #<NUM>401a may be a basic numerology (e.g., a reference numerology). For example, a RE 495a of the basic numerology 401a may be defined with subcarrier spacing 405a of <NUM> in frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in time domain (i.e., symbol length #<NUM>403a), where Ts denotes a baseband sampling time unit defined as <NUM>/(<NUM>*<NUM>) seconds. For the i-th numerology, the subcarrier spacing <NUM> may be equal to <NUM>*<NUM>i and the effective OFDM symbol length <NUM>*<NUM>-i *Ts. It may cause the symbol length is <NUM>*<NUM>-i *Ts + CP length (e.g., <NUM>*<NUM>-i *Ts or <NUM>*<NUM>-i *Ts). In other words, the subcarrier spacing of the i+l-th numerology is a double of the one for the i-th numerology, and the symbol length of the i+l-th numerology is a half of the one for the i-th numerology. <FIG> shows four numerologies, but the system may support another number of numerologies. Furthermore, the system does not have to support all of the O-th to the I-th numerologies, i=<NUM>, <NUM>,.

For example, the first UE transmission on the first SPS resource as above mentioned may be performed only on the numerology #<NUM> (e.g., a subcarrier spacing of <NUM>). Here, the UE <NUM> may acquire (detect) the numerology #<NUM> based on a synchronization signal. Also, the UE <NUM> may receive a dedicated RRC signal including information (e.g., a handover command) configuring the numerology #<NUM>. The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on the numerology #<NUM>, the numerology #<NUM> (a subcarrier spacing of <NUM>), and/or the numerology #<NUM> (a subcarrier spacing of <NUM>).

Also, the second UL transmission on the second SPS resource as above mentioned may be performed only on the numerology #<NUM>. Here, for example, the UE <NUM> may receive System Information (e.g., Master Information Block (MIB) and/or System Information Block (SIB)) including information configuring the numerology #<NUM> and/or the numerology #<NUM>.

Also, the UE <NUM> may receive the dedicated RRC signal including information (e.g., the handover command) configuring the numerology #<NUM> and/or the numerology #<NUM>. The System Information (e.g., MIB) may be transmitted on BCH (Broadcast Channel) and/or the dedicated RRC signal. The System Information (e.g., SIB) may contain information relevant when evaluating if a UE <NUM> is allowed to access a cell and/or defines the scheduling of other system information. The System Information (SIB) may contain radio resource configuration information that is common for multiple UEs <NUM>. Namely, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of UL transmissions (e.g., each of UL-SCH transmissions, each of PUSCH transmissions). Also, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of DL transmissions (each of PDCCH transmissions).

<FIG> shows examples of subframe structures for the numerologies <NUM> that are shown in <FIG>. Given that a slot <NUM> includes NDLsymb (or NULsymb) = <NUM> symbols, the slot length of the i+l-th numerology <NUM> is a half of the one for the i-th numerology <NUM>, and eventually the number of slots <NUM> in a subframe (i.e., <NUM>) becomes double. It may be noted that a radio frame may include <NUM> subframes, and the radio frame length may be equal to <NUM>.

<FIG> shows examples of slots <NUM> and sub-slots <NUM>. If a sub-slot <NUM> is not configured by higher layer, the UE <NUM> and the eNB and/or gNB <NUM> may only use a slot <NUM> as a scheduling unit. More specifically, a given transport block may be allocated to a slot <NUM>. If the sub-slot <NUM> is configured by higher layer, the UE <NUM> and the eNB and/or gNB <NUM> may use the sub-slot <NUM> as well as the slot <NUM>. The sub-slot <NUM> may include one or more OFDM symbols. The maximum number of OFDM symbols that constitute the sub-slot <NUM> may be NDLsymb-l (or NULsymb -l).

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 (e.g., by DCI format).

The sub-slot <NUM> may start at any symbol within a slot <NUM> unless it collides with a control channel. There could be restrictions of mini-slot length based on restrictions on starting position. For example, the sub-slot <NUM> with the length of NDLsymb-l (or NULsymb -<NUM>) may start at the second symbol in a slot <NUM>. The starting position of a sub-slot <NUM> may be indicated by a physical layer control channel (e.g., by DCI format). Alternatively, the starting position of a sub-slot <NUM> may be derived from information (e.g., search space index, blind decoding candidate index, frequency and/or time resource indices, PRB index, a control channel element index, control channel element aggregation level, an antenna port index, etc.) of the physical layer control channel which schedules the data in the concerned sub-slot <NUM>.

In cases when the sub-slot <NUM> is configured, a given transport block may be allocated to either a slot <NUM>, a sub-slot <NUM>, aggregated sub-slots <NUM> or aggregated sub-slot(s) <NUM> and slot <NUM>. This unit may also be a unit for HARQ-ACK bit generation.

<FIG> shows examples of scheduling timelines <NUM>. For a normal DL scheduling timeline 709a, DL control channels are mapped the initial part of a slot 783a. The DL control channels <NUM> schedule DL shared channels 713a in the same slot 783a. HARQ-ACKs for the DL shared channels 713a (i.e., HARQ-ACKs each of which indicates whether or not transport block in each DL shared channel 713a is detected successfully) are reported via UL control channels 715a in a later slot 783b. In this instance, a given slot <NUM> may contain either one of DL transmission and UL transmission.

For a normal UL scheduling timeline 709b, DL control channels 711b are mapped the initial part of a slot 783c. The DL control channels 711b schedule UL shared channels 717a in a later slot 783d. For these cases, the association timing (time shift) between the DL slot 783c and the UL slot 783d may be fixed or configured by higher layer signaling. Alternatively, it may be indicated by a physical layer control channel (e.g., the DL assignment DCI format, the UL grant DCI format, or another DCI format such as UE-common signaling DCI format which may be monitored in common search space).

For a self-contained base DL scheduling timeline 709c, DL control channels 711c are mapped to the initial part of a slot 783e. The DL control channels 711c schedule DL shared channels 713b in the same slot 783e. HARQ-ACKs for the DL shared channels 713b are reported in UL control channels 715b, which are mapped at the ending part of the slot 783e.

For a self-contained base UL scheduling timeline 709d, DL control channels 711d are mapped to the initial part of a slot 783f. The DL control channels 711d schedule UL shared channels 717b in the same slot 783f. For these cases, the slot 783f may contain DL and UL portions, and there may be a guard period between the DL and UL transmissions.

The use of a self-contained slot may be upon a configuration of self-contained slot. Alternatively, the use of a self-contained slot may be upon a configuration of the sub-slot. Yet alternatively, the use of a self-contained slot may be upon a configuration of shortened physical channel (e.g., PDSCH, PUSCH, PUCCH, etc.).

<FIG> shows examples of DL control channel monitoring regions. One or more sets of PRB(s) may be configured for DL control channel monitoring. In other words, a control resource set is, in the frequency domain, a set of PRBs within which the UE <NUM> attempts to blindly decode downlink control information, where the PRBs may or may not be frequency contiguous, a UE <NUM> may have one or more control resource sets, and one DCI message may be located within one control resource set. In the frequency-domain, a PRB is the resource unit size (which may or may not include Demodulation reference signals (DMRS)) for a control channel. A DL shared channel may start at a later OFDM symbol than the one(s) which carries the detected DL control channel. Alternatively, the DL shared channel may start at (or earlier than) an OFDM symbol than the last OFDM symbol which carries the detected DL control channel. In other words, dynamic reuse of at least part of resources in the control resource sets for data for the same or a different UE <NUM>, at least in the frequency domain may be supported.

<FIG> shows examples of DL control channel which includes more than one control channel elements. When the control resource set spans multiple OFDM symbols, a 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 REs defined by a single PRB and a single OFDM symbol. If more than one DL control channel elements are used for a single DL control channel transmission, DL control channel element aggregation may be performed.

The number of aggregated DL control channel elements is referred to as DL control channel element aggregation level. The DL control channel element aggregation level may be <NUM> or <NUM> to the power of an integer. The gNB <NUM> may inform a UE <NUM> of 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, the DL control channel element aggregation is performed within an OFDM symbol, namely multiple DL control channel elements within an OFDM symbol are aggregated. Otherwise, DL control channel elements in different OFDM symbols can be aggregated.

<FIG> shows examples of UL control channel structures. UL control channel may be mapped on REs which are defined by a PRB and a slot in frequency and time domains, respectively. This UL control channel may be referred to as a long format (or just the 1st format). UL control channels may be mapped on REs on a limited OFDM symbols in time domain. This may be referred to as a short format (or just the 2nd format). The UL control channels with a short format may be mapped on REs within a single PRB. Alternatively, the UL control channels with a short format may be mapped on REs within multiple PRBs. For example, interlaced mapping may be applied, namely the UL control channel may be mapped to every N PRBs (e.g., <NUM> or <NUM>) within a system bandwidth.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM>. The gNB <NUM> may include a higher layer processor <NUM>, a DL transmitter <NUM>, a UL receiver <NUM>, and one or more antenna <NUM>. The DL transmitter <NUM> may include a PDCCH transmitter <NUM> and a PDSCH transmitter <NUM>. The UL receiver <NUM> may include a PUCCH receiver <NUM> and a PUSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the DL transmitter's and the UL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send and/or acquire higher layer messages such as an RRC message and MAC message to and/or from a UE's higher layer. The higher layer processor <NUM> may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.

The DL transmitter <NUM> may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas <NUM>. The UL receiver <NUM> may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas <NUM> and de-multiplex them. The PUCCH receiver <NUM> may provide the higher layer processor <NUM> UCI. The PUSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

<FIG> is a block diagram illustrating one implementation of a UE <NUM>. The UE <NUM> may include a higher layer processor <NUM>, a UL transmitter <NUM>, a DL receiver <NUM>, and one or more antenna <NUM>. The UL transmitter <NUM> may include a PUCCH transmitter <NUM> and a PUSCH transmitter <NUM>. The DL receiver <NUM> may include a PDCCH receiver <NUM> and a PDSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the UL transmitter's and the DL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send and/or acquire higher layer messages such as an RRC message and MAC message to and/or from a UE's higher layer. The higher layer processor <NUM> may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter <NUM> UCI.

The DL receiver <NUM> may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas <NUM> and de-multiplex them. The PDCCH receiver <NUM> may provide the higher layer processor <NUM> DCI. The PDSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

It should be noted that names of physical channels described herein are examples. The other names such as "NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH", "new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH" or the like can be used.

<FIG> illustrates various components that may be utilized in a UE <NUM>. The UE <NUM> described in connection with <FIG> may be implemented in accordance with the UE <NUM> described in connection with <FIG>. The UE <NUM> includes a processor <NUM> that controls operation of the UE <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1307a and data 1309a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random-access memory (NVRAM). Instructions 1307b and data 1309b may also reside in the processor <NUM>. Instructions 1307b and/or data 1309b loaded into the processor <NUM> may also include instructions 1307a and/or data 1309a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1307b may be executed by the processor <NUM> to implement the methods described above.

The UE <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1322a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

<FIG> illustrates various components that may be utilized in a gNB <NUM>. The gNB <NUM> described in connection with <FIG> may be implemented in accordance with the gNB <NUM> described in connection with <FIG>. The gNB <NUM> includes a processor <NUM> that controls operation of the gNB <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1407a and data 1409a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random-access memory (NVRAM). Instructions 1407b and data 1409b may also reside in the processor <NUM>. Instructions 1407b and/or data 1409b loaded into the processor <NUM> may also include instructions 1407a and/or data 1409a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1407b may be executed by the processor <NUM> to implement the methods described above.

The gNB <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1480a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

The various components of the gNB <NUM> are coupled together by a bus system <NUM>, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. The gNB <NUM> may also include a digital signal processor (DSP) <NUM> for use in processing signals. The gNB <NUM> may also include a communications interface <NUM> that provides user access to the functions of the gNB <NUM>. The gNB <NUM> illustrated in <FIG> is a functional block diagram rather than a listing of specific components.

<FIG> is a block diagram illustrating one implementation of a UE <NUM> in which systems and methods that achieve mini-slot-based repetitions. The UE <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM> in which systems and methods that achieve mini-slot-based repetitions. The gNB <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

<FIG> is a flow diagram illustrating a method <NUM> by a user equipment (UE) <NUM>. The UE <NUM> may receive <NUM> signaling that includes a configuration for a grant-free physical uplink shared channel (PUSCH) or a configuration for grant-based PUSCH. The UE <NUM> may determine <NUM> whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a transport block (TB). The UE <NUM> may transmit <NUM> the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions.

<FIG> is a flow diagram illustrating a method <NUM> by a base station (gNB) <NUM>. The gNB <NUM> may transmit <NUM>, to a user equipment (UE) <NUM>, signaling that includes a configuration for a grant-free physical uplink shared channel (PUSCH) or a configuration for grant-based PUSCH. The gNB <NUM> may determine <NUM> whether to use slot-based PUSCH repetitions or mini-slot-based PUSCH repetitions of a transport block (TB). The gNB <NUM> may receive <NUM> the slot-based PUSCH repetitions or the mini-slot-based PUSCH repetitions from the UE <NUM>.

The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. The term "computer-readable medium," as used herein, may denote a computer- and/or processor-readable medium that is non-transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified.

It is to be understood that the precise configuration and components illustrated above is not limiting. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein.

A program running on the gNB <NUM> or the UE <NUM> according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB <NUM> and the UE <NUM> according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB <NUM> and the UE <NUM> may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned implementations may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a com-bination 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 circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Claim 1:
A user equipment (<NUM>), UE, that communicates via mini-slot-based repetitions, the UE comprising:
receiving circuitry (<NUM>) configured to receive:
a radio resource control, RRC, message, the RRC message comprising first information used for configuring a first number of repetitions for physical uplink shared channel, PUSCH, transmissions,
the RRC message comprising second information used for configuring a second number of repetitions for PUSCH transmissions, and
the RRC message comprising third information used for indicating a repetition type from a set of repetition types, the set of the repetition types comprising a first repetition type and a second repetition type, the first repetition type indicating only one repetition to be transmitted within a slot, the second repetition type indicating more than one repetition to be transmitted within the slot; and
transmitting circuitry (<NUM>) configured to perform, based on the third information, either the first number of repetitions for the PUSCH transmissions or the second number of repetitions for the PUSCH transmissions, wherein
the transmitting circuitry performs the second number of repetitions for the PUSCH transmissions in a case that the third information indicates the second repetition type.