Patent Description:
In other examples (e.g., in a next generation, a new radio (NR), or <NUM> network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more DUs, in communication with a CU, may define an access node (e.g., which may be referred to as a BS, next generation NodeB (gNB or gNodeB), TRP, etc.). A BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or DU to a UE) and uplink channels (e.g., for transmissions from a UE to a BS or DU).

Relatedly, documents 3GPP R1-<NUM> and 3GPP R1-<NUM> describe physical uplink shared channel (PUSCH) enhancements for NR ultra-reliable low-latency communications (URLLC).

Embodiments and aspects that do not fall within the scope of the claims are merely examples used for explanation of the invention.

Aspects of the present disclosure discuss TDRA design for scheduling multiple consecutive transmissions (e.g. PUSCH transmissions) in a multi-TTI DCI while allowing for mini-slot allocation in the beginning, in the middle, and/or at the end of the multi-TTI allocation.

The techniques described herein may be used for various wireless communication technologies, such as 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), and other networks.

cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project <NUM>" (<NUM> GPP2).

NR access (e.g., <NUM> NR) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., <NUM> or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., <NUM> or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC).

For example, the wireless communication network <NUM> may be an NR system (e.g., a 5GNR network). In an aspect, as shown in <FIG>, each of the User Equipments (UEs) <NUM> may be configured to perform operations relating to time-domain resource allocation (TDRA) for multi-transmission time interval (TTI) grants, according to aspects described herein. In an aspect, as shown in <FIG> each of the BSs <NUM> may be configured to perform operations related to time-domain resource allocation (TDRA) for multi-transmission time interval (TTI) grants, according to aspects described herein.

As illustrated in <FIG>, the wireless communication network <NUM> may include a number of base stations (BSs) <NUM> and other network entities. A BS may be a station that communicates with user equipments (UEs). Each BS <NUM> may provide communication coverage for a particular geographic area. In some examples, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

Some UEs may be considered Internet-of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

A finely dashed line with double arrows indicates potentially interfering transmissions between a UE and a BS.

<FIG> illustrates example components of BS <NUM> and UE <NUM> (e.g., in the wireless communication network <NUM> of <FIG>), which may be used to implement aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform the various techniques and methods described herein. In an aspect, as shown in <FIG>, the controller/processor <NUM> of the BS <NUM> may be configured for time-domain resource allocation (TDRA) for multi-transmission time interval (TTI) grants, according to aspects described herein. In an aspect, as shown in <FIG>, the controller/processor <NUM> of the UE <NUM> may be configured for time-domain resource allocation (TDRA) for multi-transmission time interval (TTI) grants, according to aspects described herein.

The transmit processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a-232t. Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.

At the LTE <NUM>, the antennas 252a-252r may receive the downlink signals from the BS <NUM> and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.

The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the base station <NUM>.

The controllers/processors <NUM> and <NUM> may direct the operation at the BS <NUM> and the UE <NUM>, respectively. The controller/processor <NUM> and/or other processors and modules at the BS <NUM> may perform or direct the execution of processes for the techniques described herein.

Different systems utilize various options for Time-Domain Resource Allocation (TDRA) for transmissions (e.g., PUSCH/PDSCH transmissions) in a slot of an NR subframe.

For example, for UL grant (e.g., DCI formats 0_0 and 0_1) in NR (e.g., NR Release-<NUM>), TDRA is indicated as part of DCI. NR defines a number of options for allocating time domain resources for a transmission in a TDRA table, where each entry/row of the TDRA table defines a different allocation of time domain resources. A TDRA field in the DCI scheduling a transmission indicates one of the entries/rows from the TDRA table. A receiving UE decodes the DCI, identifies the indication in TDRA field and uses the resource allocation from the corresponding TDRA table entry for the scheduled transmission. In an aspect, the TDRA table may be a default table known to the network and the UE, or may be a configurable table that is configured via RRC signaling.

<FIG> illustrates an example default TDRA table 400A as defined by NR (e.g., NR Release <NUM>).

As shown in <FIG>, default TDRA table 400A defines sixteen different time domain resource allocations for scheduling PUSCH transmissions, where each row of the table 400A defines a different resource allocation. For each TDRA option (e.g., each row) the columns of the table 400A include various parameters defining the details of the resource allocation. As shown in <FIG>, for each TDRA option (e.g., each row), the table 400A defines a Row index, a mapping type, a slot offset (K<NUM>), a starting symbol (S) and an allocation length L. The mapping type may be either mapping type A or B for the scheduled PUSCH transmission. The slot offset K<NUM> provides an offset relative to the slot in which the DCI was transmitted. For example, if n represents the slot in which the scheduling DCI was transmitted, PUSCH is transmitted in slot n+K<NUM>. The starting symbol S specifies the particular symbol of a slot (e.g., symbol <NUM>, <NUM>, <NUM>. <NUM>) at which the corresponding PUSCH transmission is scheduled to start. The allocation length L defines a symbol length of the PUSCH transmission from the starting symbol S. Alternatively, the starting symbol S and the allocation length L may be indicated jointly as Start and Length Indicator Value (SLIV).

<FIG> illustrates an example table 400B specifying values of j for use in determining starting symbol S as defined by NR (e.g., NR Release <NUM>).

The parameter µPUSCH as shown in table 400B specifies the subcarrier spacing. For example, the value <NUM>, <NUM>, <NUM> and <NUM> of µPUSCH represent subcarrier spacing of <NUM>, <NUM>, <NUM> and <NUM> respectively. As shown in <FIG>, the value of j is a function of the subcarrier spacing.

<FIG> illustrates an example table 400C specifying valid combinations of starting symbol S and allocation length L as defined by NR (e.g., NR Release <NUM>).

As shown in <FIG>, the values of S and L in table 400B are a function of the mapping type. In addition, the values of S and L are defined such that an allocation does not cross a slot boundary. For example, S+L-<NUM> is at most the last symbol in an allocated slot.

In certain aspects, as the TDRA field of the DCI indicates one of the entries/rows from the TDRA table, the bit length of the TDRA field is a function of the number of rows in the TDRA table. For example, bit-width of the TDRA field is <NUM> bits for indicating each of the sixteen TDRA options from the default TDRA table as shown in <FIG>.

In an aspect, the TDRA table may be a configurable (e.g., no default). For example, NR (e.g., NR Release <NUM>) specifies that TDRA field indicates one of the entries of the higher layer parameter pusch-TimeDomainAllocationList, if this higher layer parameter is configured. The higher layer parameter pusch-TimeDomainAllocationList is an RRC parameter defining a configurable TDRA table. If this parameter is not configured, the default TDRA table is used. In an aspect, the maximum number of TDRA options (e.g., entries) configured by the configurable TDRA table is sixteen. Thus, the bit-width of the TDRA field may be <NUM>-<NUM> depending on a number of entries configured in the configurable table. In an aspect, like the default table, the RRC parameter pusch-TimeDomainAllocationList specifies a mapping type, a slot offset (K<NUM>), a starting symbol (S) and an allocation length L for each configured TDRA entry. Additionally, the pusch-TimeDomainAllocationList specifies a maximum number of entries configured. In an aspect, the starting symbol S and the allocation length L is indicated jointly as Start and Length Indicator Value (SLIV).

In certain aspects, NR supports Multi-Transmission Time Interval (Multi-TTI) grants. A multi-TTI grant is generally a single grant (e.g., Downlink/Uplink grant) that schedules multiple transport blocks (TBs) (e.g., PDSCH or PUSCH) on multiple TTIs. In an aspect, a TTI includes a slot or a mini-slot of an NR subframe. Multi-TTI grants are particularly useful for multi-TTI PUSCH grants in NR based access to unlicensed spectrum (NRU). For example, without multi-TTI PUSCH grants, multiple downlink portions may have to be used for transmitting multiple PUSCH grants, which would not only cause additional overhead but would also involve multiple switches between downlink and uplink. Since NRU uses Listen-Before-Talk to gain access to a medium, switches between downlink and uplink may potentially lead to loss of medium.

In certain aspects, the current agreement in 3GPP standards regarding multi-TTI PUSCH grants in NRU states that "scheduling PUSCH over multiple slots/mini-slots by single DCI supports at least multiple continuous PUSCHs with separate TBs, where each TB is mapped to at most one slot or one mini-slot". It is envisioned that a similar agreement may be reached regarding multi-TTI PDSCH grants for NRU in the future.

In certain aspects, allowing allocation for mini-slots (instead of full slots) for at least some of the PUSCH transmissions scheduled by a multi-TTI grant is beneficial and in fact needed. In an aspect, mini-slot allocation may need to be allowed at the beginning (e.g., one or more initial PUSCH transmissions) of a multi-TTI transmission (scheduled by multi-TTI grant), to enable more Listen Before Talk (LBT) opportunities for the UE in the beginning of the multi-TTI transmission. In an aspect, mini-slot allocation may need to be allowed anywhere in the middle of a multi-TTI transmission. For example, if a PUSCH transmission in the middle of the multi-TTI transmission corresponds to a retransmission and Code Block Group Transmission Information (CBGTI) field in the DCI indicates only some of the CBGs require retransmission (e.g. <NUM> out of <NUM>), a smaller number of resources (e.g., only some symbols of a slot and not the entire slot) are needed for the retransmission. In an aspect, since the Frequency Domain Resource Allocation (FDRA) is likely to be the same for all PUSCHs, the TDRA may indicate a smaller number of symbols than a full slot. In an aspect, mini-slot allocation may need to be allowed at the end of a multi-TTI transmission. For example, when there is not enough data in the UE buffer that would take an entire slot for a last PUSCH transmission, the last PUSCH transmission may be allocated a subset of symbols in the slot and the transmission may end a few symbols before the slot boundary.

In an aspect, the TDRA designs discussed in aspects of the present disclosure include TDRA table designs defining a number of time domain resource allocations for a multi-TTI grant. In an aspect, the discussed TDRA tables may be used as default TDRA tables (with fixed table size) or may be configured via RRC signaling (e.g., configurable entries/rows). In an aspect, the proposed TDRA table designs provide an acceptable tradeoff between scheduling flexibility and RRC overhead/TDRA field bit-width. For example, while providing scheduling flexibility in terms of the number of TDRA allocation options (e.g., number of entries/rows of the TDRA table) is important, the bit-width of the TDRA field (determined by the number of entries/rows in the TDRA table) should not be too large to avoid increasing the DCI size by too much. Additionally, a large TDRA table size including a large number of TDRA entries/rows results in a large RRC overhead to convey the table configuration. Thus, a tradeoff is needed between the scheduling flexibility offered by the TDRA table design and the size of the TDRA table.

It may be noted that while aspects of the present disclosure discuss TDRA designs with reference to multi-TTI PUSCH grants, some of the discussed TDRA designs are applicable to multi-TTI PDSCH grants.

In certain aspects, certain concepts relating to multi-TTI grants in Licensed-Assisted Access (LAA) may be leveraged for reducing the DCI size for multi-TTI grants in NR.

Multi-TTI grant in LAA uses DCI formats 0B/4B in accordance with 3GPP LTE specifications. The LTE specifications include several definitions for multi-TTI UL grants. According to the LTE specifications, a "maxNumberOfSchedSubframes" parameter is configured via Radio Resource Control (RRC) signaling. This parameter configures a maximum number of TTIs (e.g., <NUM> or <NUM> subframes) that may be scheduled by a multi-TTI grant. DCI is used to dynamically indicate how many TTIs or subframes are actually scheduled by a particular. In an aspect, the DCI uses <NUM> bit or <NUM> bits for this dynamic indication based on the maximum number of scheduled TTIs configured via RRC signaling being <NUM> or <NUM> TTIs respectively. In an aspect, the DCI size is independent of the number of TTIs scheduled dynamically, and is only a function of the maximum number of scheduled TTIs that is semi-statically configured via RRC signaling.

In certain aspects, the TDRA designs discussed in aspects of the present disclosure follow certain assumptions. For example, similar to the LAA design, a maximum number of PUSCH transmissions (represented by parameter N) (or TTIs assuming one PUSCH transmission per TTI) that can be schedule by a single multi-TTI grant (e.g., DCI) is configured via RRC signaling. An actual number of PUSCH transmissions (represented by the parameter n) scheduled by a particular multi-TTI grant (e.g., DCI) is indicated in the DCI, where n<=N. Additionally, it is assumed that no single PUSCH transmission can cross a slot boundary, that is, the start symbol and end symbol of each PUSCH transmission is within a single slot. Another assumption is that PUSCH transmissions scheduled by a multi-TTI grant are consecutive in the time domain, with no gaps between two consecutive PUSCH transmissions when scheduled by a single multi-TTI grant.

<FIG> illustrates example operations <NUM> performed by a base station (BS) for allocating time domain resource allocation for a multi-TTI grant, in accordance with aspects of the claimed invention.

Operations <NUM> begin, at <NUM>, by allocating time domain resources for a plurality of physical uplink shared channel (PUSCH) transmissions (e.g., corresponding to transport blocks), according to a Time Domain Resource Allocation (TDRA) pattern selected from a TDRA table designed for multi-PUSCH grants.

At <NUM>, the BS transmits downlink control information (DCI) scheduling the plurality of PUSCH transmissions, wherein the DCI comprises an indication of the TDRA pattern selected from the TDRA table.

<FIG> illustrates example operations <NUM> performed by a user equipment (UE) for determining time domain resource allocation for a multi-TTI grant, in accordance with aspects of the claimed invention.

Operations <NUM> begin, at <NUM>, by receiving downlink control information (DCI) scheduling a plurality of physical uplink shared channel (PUSCH) transmissions (e.g., corresponding to transport blocks), wherein time domain resources are allocated for the plurality of PUSCH transmissions according to a Time Domain Resource Allocation (TDRA) pattern selected from a TDRA table designed for multi-PUSCH grants and the DCI comprises an indication of the TDRA pattern.

At <NUM>, the UE determines, based on the indication, the TDRA pattern from the TDRA table.

At <NUM>, the UE determines, based on the determined TDRA pattern, the allocation of the time domain resources for the plurality of PUSCH transmissions.

In an aspect, each row of the TDRA table corresponds to a different TDRA pattern, and where each TDRA pattern is defined by allocation information in a plurality of columns of the TDRA table corresponding to the row for the TDRA pattern, where each TDRA pattern defines a different pattern for allocating time domain resources in the plurality of TTIs for the plurality of transmissions. In an aspect, the TDRA indication transmitted in the DCI indicates to a particular row/TDRA pattern form the TDRA table. In an aspect, each TTI includes a full slot or a mini-slot, wherein each TTI is assigned one transmission (PUSCH) such that different TTIs are assigned different PUSCH transmissions.

<FIG> illustrates a TDRA table design 700A for multi-TTI grants (PUSCH grants), in accordance with certain aspects of the claimed invention.

As shown in <FIG>, each entry/row of the TDRA table 700A defines a different TDRA pattern for allocation of time domain resources. In some cases, each entry/row of the TDRA table 700A includes time domain resource allocations for the maximum number of PUSCH transmissions N that can be scheduled by a particular multi-TTI grant. However, as noted above, the actual number (n) of PUSCH transmissions scheduled by a particular multi-TTI grant may be less than the maximum number N (e.g., n<=N). Thus, a particular multi-TTI grant may use only 'n' number of allocations of the 'N' allocations defined in a particular TDRA pattern from the TDRA table 700A. The example TDRA table 700a is designed for N=<NUM>.

Extending a TDRA table as described herein generally allows a DCI to indicate single or multiple continuous PUSCH transmissions in any slot of the multiple scheduled slots. In some cases, the maximum number of PUSCHs that can be configured in a row of the TDRA table is <NUM>. The actual number of scheduled PUSCHs, however, may be signaled by the number of indicated valid SLIVs in the row of the TDRA table signaled in the DCI (e.g., up to the limit of <NUM>).

As shown in <FIG>, each entry/row of the TDRA table 700A is identified by a Row index that identifies a unique TDRA pattern. Each entry/row includes a slot offset (K2) and a starting symbol (S) for the first PUSCH transmission scheduled by the multi-TTI grant. According to the claimed invention, each TDRA pattern comprises a slot offset only for the first scheduled PUSCH transmission. Each entry/row further includes an allocation length (Li) for each PUSCH i, wherein i = <NUM>-N.

Since the PUSCH allocations are assumed to be consecutive without any gap between consecutive transmissions, the start symbol for each subsequent PUSCH transmission (after the first PUSCH transmission) may be determined based on the length Li of a previous transmission. Thus, the starting symbol for a PUSCH j may be given as <MAT>, where S is the starting symbol for the first PUSCH transmission. Therefore, in some cases, the starting symbol may only be provided for the first PUSCH transmission. In some cases, however (e.g., to avoid having to perform the aforementioned calculation), the starting symbol Sj may be provided for each PUSCH j in addition to the allocation length Lj. That is, in such cases, each PUSCH j of a row is provided its own SLIV.

In some cases, each entry/row further includes a mapping type of each PUSCH i. It may be noted that, i = <NUM>,<NUM>,. N, which means that the maximum number of PUSCHs (N) are considered in the table design 700A, since the actual number of PUSCH scheduled (n) is not an RRC parameter and can change dynamically. In an aspect, when the actual number of PUSCHs n<N, information from the table for i = n + <NUM>,. , N is not used.

<FIG> illustrates an example allocation 700B according to TDRA patterns defined the table 700A, in accordance with certain aspects of the present disclosure.

As shown in <FIG>, allocation <NUM> corresponds to a multi-TTI grant allocating time domain resources according to the TDRA pattern corresponding to Row index <NUM> from the TDRA table 700A. Similarly, allocation <NUM> corresponds to a multi-TTI grant allocating time domain resources according to the TDRA pattern corresponding to Row index <NUM> from the TDRA table 700A. As shown, each of the allocations <NUM> and <NUM> shows allocation of time domain resources over three time slots, the first slot in each case carrying the DCI scheduling the corresponding multi-TTI grant. Allocation <NUM> assumes the actual number of scheduled transmissions n=<NUM> and allocation <NUM> assumes n=<NUM>.

As shown in allocation <NUM>, the first PUSCH transmission (PUSCH <NUM>) starts in slot <NUM>, as the value of slot K2 in row index <NUM> is ` <NUM>', which means an offset of one slot from the slot carrying the DCI grant. As shown, PUSCH <NUM> starts at symbol #<NUM> as indicated by the value of starting symbol S (assuming symbol index ranges from <NUM>-<NUM>), and is allocated <NUM> symbols (L1=<NUM>). Since the assumption is that all PUSCH transmissions are consecutive, PUSCH <NUM> starts at symbol #<NUM> which is the consecutive symbol after the last symbol of PUSCH <NUM> and is allocated <NUM> symbols (L2=<NUM>). PUSCH <NUM> starts at the first symbol of slot #<NUM> and is allocated the entire slot which is <NUM> symbols (L3=<NUM>). In an aspect, since n=<NUM>, allocation <NUM> does not use information relating to the fourth allocation (L4 and mapping for i=<NUM>) from the table 700A.

Similarly, allocation <NUM> allocates time domain resource in accordance with TDRA pattern defined in Row index <NUM>. As shown, since n=<NUM>, allocation <NUM> uses information relating to all four allocations from the TDRA table 700A.

In an aspect, as shown in allocations <NUM> and <NUM>, a PUSCH allocation cannot cross the slot boundary, meaning the start symbol and end symbol for each PUSCH j need to be in the same slot. This may be characterized by: <MAT>.

In certain aspects, a table format of a TDRA table (e.g., TDRA table 700A) is defined by the number of columns for an entry/row in the table and the allowed values for each column. In an aspect, the table format is a function of N (max number of PUSCHs that can be scheduled by a multi-TTI grant). In an aspect, the table format determines the RRC overhead (e.g. number of bits for configuring each entry/row) when the table is configurable (i.e. not a default table).

In certain aspects, if a slot contains more than one PUSCH allocation, only the first one can be mapping type A (it can also be mapping type B), but the other PUSCHs in the slot have to be mapping type B. This may be seen from TDRA table 700A.

In certain aspects, the table size of a TDRA table (e.g., TDRA table 700A) is defined by the number of entries/rows allowed in the TDRA table. In an aspect, the table size of a TDRA table can be a function of N. This is because if a larger number of PUSCH transmissions are allowed to be scheduled by multi-TTI grant, more flexibility for TDRA is needed, which translates to more TDRA patterns or more entries/rows in the TDRA table. For example, if N=<NUM>, max 4bits in DCI (<NUM> entries) are allowed, if N=<NUM>, max 5bits in DCI (<NUM> entries) are allowed, if N=<NUM>, max 6bits in DCI (<NUM> entries) are allowed. In an aspect, the table size determines the DCI overhead, as the amount of bits needed to indicate an entry of the TDRA table in the TDRA field of the DCI is a function of the number of entries/rows in the TDRA table. In an aspect, the table size also determines the RRC overhead when the table is configurable.

In certain aspects, as shown in the table format of TDRA table 700A, the values of Li and mapping types are not completely independent. Hence, the information for configuring each entry of the TDRA table may be compressed.

<FIG> illustrates an example design of a compressed TDRA table 800A for multi-TTI grants (e.g., PUSCH grants), in accordance with certain aspects of the present disclosure.

In an aspect, each row/entry of the TDRA table 800A is identified by a unique row index and defines a different TDRA pattern for the multi-TTI grant. As shown in <FIG>, each row/entry includes a slot offset (K2) and starting symbol (S) for a first PUSCH transmission. Each row/entry further includes a number of scheduled slots (K) including partially allocated slots (e.g., first or last slots) and fully allocated slots (e.g., middle slots). Each row/entry further includes a member ID vector, the member ID vector including one member ID for each scheduled slot. For example, as shown in <FIG>, row index <NUM> has K=<NUM> and the corresponding member ID vector includes two member IDs. In an aspect, each member ID of the member ID vector defines the mini-slot structure for a corresponding scheduled slot, wherein each member ID points to a unique entry/row of a mini-slot table, wherein each row of the mini-slot table defines a mini-slot structure for a given slot.

<FIG> illustrates an example mini-slot table 800B for defining a mini-slot structure for a given slot, in accordance with certain aspects of the present disclosure.

As shown in <FIG>, each row/entry of the mini-slot table 800B is identified by a unique member ID and defines a different mini-slot structure for a given slot. Each row/entry of the mini-slot table 800B defines a number of mini-slots (M) per slot, a length vector of size M-<NUM> defining a length of each mini-slot, a mapping type (A or B) for the first mini-slot of the given slot and a presence/absence of the last mini-slot in the given slot.

In an aspect, the number of mini-slots (M) per slot may be limited. For example, max M=<NUM>, meaning each slot can be divided into at most <NUM> mini-slots. In an aspect the vector indicating the length of each mini-slot is of length M-<NUM> since the length of the last mini-slot of the given slot is not needed, as it is known given the other values. For example, given there are <NUM> symbols per slot, for the first slot sum of length should be equal to <NUM>-S, and for other slots sum needs to be equal to <NUM>. In an aspect, the information regarding the presence/absence of the last mini-slot is useful when the last few symbols are not allocated. As shown in table 800B, a one-bit value is used to indicate the presence/absence of the last mini-slot in the given slot, wherein a value of '<NUM>' indicates a presence of the last mini-slot and a value of '<NUM>' indicates an absence of the last mini-slot. Alternatively, instead of explicitly indicating the presence/absence of the last mini-slot, the value of n (actual number of PUSCHs) indicated in the DCI may be used to determine this information. For example, if PUSCH n is scheduled in a particular slot, and there are multiple mini-slots in the particular slot, the remaining mini-slots in the slot after the PUSCH n has been transmitted are not transmitted.

<FIG> illustrates an example allocation 800C according to TDRA patterns defined the table 800A, in accordance with certain aspects of the present disclosure.

As shown in <FIG>, allocation <NUM> corresponds to a multi-TTI grant allocating time domain resources according to the TDRA pattern corresponding to Row index <NUM> from the TDRA table 800A. Similarly, allocation <NUM> corresponds to a multi-TTI grant allocating time domain resources according to the TDRA pattern corresponding to Row index <NUM> from the TDRA table 800A. As shown, each of the allocations <NUM> and <NUM> shows allocation of time domain resources over three time slots, the first slot in each case carrying the DCI scheduling the corresponding multi-TTI grant.

As shown in allocation <NUM>, the first PUSCH transmission (PUSCH <NUM>) starts in slot <NUM>, as the value of slot K2 in row index <NUM> is ` <NUM>', which means an offset of one slot from the slot carrying the DCI grant. As shown, PUSCH <NUM> starts at symbol #<NUM> as indicated by the value of starting symbol S (assuming symbol index ranges from <NUM>-<NUM>). Row index <NUM> indicates that two slots are to be scheduled and the member ID vector indicates member ID <NUM> for the mini-slot structure of the first slot and indicates member ID <NUM> for the mini-slot structure of the second slot. As shown, the mini-slots within the two slots of allocation <NUM> are allocated in accordance with the mini-slot table 800B. Looking at member ID #<NUM> of the mini-slot table 800B, <NUM> mini-slots are to be scheduled in the first scheduled slot, and the length of the first mini-slot in the first scheduled slot is <NUM> symbols. Since the last column of member ID <NUM> indicates a presence of the last mini-slot in the slot, the second mini-slot of the first scheduled slot (which is the last mini-slot of the slot) occupies the remaining slots of the first scheduled slot. Looking at member ID #<NUM> of the mini-slot table 800B, <NUM> mini-slot is to be scheduled in the second scheduled slot. Since the last column of member ID <NUM> indicates a presence of the last mini-slot in the slot, the mini-slot of the second scheduled slot (which is the last mini-slot of the slot) occupies all slots of the second scheduled slot.

Similarly, allocation <NUM> allocates time domain resource in accordance with TDRA pattern defined in Row index <NUM>, wherein the mini-slot structure of the scheduled slots is decided by the defined member IDs of the mini-slot table 800B.

In certain aspects, since the TDRA table 800A does not define the mini-slot structure of each scheduled slot (unlike table 700A of <FIG>), the RRC overhead is lower if the table 800A is configurable.

In an aspect, the number of slots K<=N as the number of slots is smaller than max number of PUSCHs since a PUSCH cannot cross the slot boundary.

In an aspect, in order to further reduce RRC overhead, additional restrictions may be introduced. For example, a maximum number of slots K_max may be defined. Alternatively, multi-TTI PUSCH may be limited such that only the first slot (or the first two slots) can contain mini-slots and the rest are full-slot PUSCH (i.e. mini-slots only allowed in the beginning). For example, K=<NUM> (or K=<NUM>), and only the structure of the first (or first two) slots are indicated, and the rest of the PUSCHs (to be determined by value n in the DCI) are full-slots.

In certain aspects, a member of the mini-slot table 800B may be used in multiple entries/rows of the TDRA table 800A (i.e. can be defined once and used multiple times). This may help further reduce the RRC overhead.

member ID=<NUM> can be used as part of an entry/row configuration from the TDRA table 800A for any entries/row that has one full-slot PUSCH among the multiple scheduled PUSCHs.

member ID=<NUM> can be used as part of an entry/row configuration from the TDRA table 800A for any entries/rows corresponding to the first scheduled PUSCH (of multiple scheduled PUSCHs) that occupies until the end of the first slot.

member ID=<NUM> can be used as part of an entry/row configuration for multiple structures. A first example is when member ID=<NUM> is used as the first member ID (corresponding to the first scheduled slot) of an entry/row from the TDRA table 800A and S=<NUM>. A second example is when member ID=<NUM> is used as the first member ID (corresponding to the first scheduled slot) of an entry/row from the TDRA table 800A and S=<NUM>. A third example is when member ID=<NUM> is used as other than the first member ID of an entry/row from the TDRA table 800A. <FIG> illustrates these three examples for member ID=<NUM>.

<FIG> illustrates an example TDRA when one entry/row from the TDRA table 800B covers multiple multi-TTI grant allocations, in accordance with certain aspects of the present disclosure. As shown in <FIG> the row index <NUM> is used to allocate time domain resources for two different multi-TTI grant allocations <NUM> and <NUM>. As shown, the member ID vector assigns member IDs to the three slots based on the example allocations discussed above. The actual number of PUSCH transmissions scheduled for allocation <NUM> is n=<NUM>. Thus, allocation <NUM> uses only the first two slot allocations from the table. Allocation <NUM> has n=<NUM> and uses allocations defined for all <NUM> slots from the table.

For example, instructions for performing the operations described herein and illustrated in <FIG> and <FIG>.

Claim 1:
A method of wireless communication by a user equipment, UE, comprising:
receiving (<NUM>) downlink control information, DCI, scheduling a plurality of physical uplink shared channel, PUSCH, transmissions for corresponding transport blocks, TBs, wherein time domain resources are allocated for the plurality of PUSCH transmissions according to a time domain resource allocation, TDRA, pattern
selected from a TDRA table designed for multi-transmission time interval, multi-TTI, PUSCH grants and the DCI comprises an indication of the TDRA pattern, wherein each TDRA pattern comprises a slot offset only for the first scheduled PUSCH transmission of the plurality of scheduled PUSCH transmissions;
determining (<NUM>), based on the indication, the TDRA pattern from the TDRA table; and
determining (<NUM>), based on the determined TDRA pattern, the allocation of the time domain resources for the plurality of PUSCH transmissions.