CN113541902A - Apparatus for use in user equipment - Google Patents

Abstract

The present application relates to an apparatus for use in a User Equipment (UE), the apparatus comprising: a Radio Frequency (RF) interface; and a processor circuit coupled to the RF interface, the processor circuit to: receiving, via an RF interface, Downlink Control Information (DCI) that schedules a Physical Downlink Shared Channel (PDSCH) transmission having repetitions; receiving, via an RF interface, a PDSCH transmission based on the DCI; and transmitting HARQ-ACK information for the PDSCH transmission via the RF interface.

Description

Apparatus for use in user equipment

Priority requirement

This application is based on and claims priority from PCT application PCT/CN2020/084730, filed on day 14, month 4, 2020, the contents of which are incorporated herein by reference in their entirety.

Technical Field

Embodiments of the present disclosure relate generally to the field of wireless communications, and more particularly, to an apparatus for use in a User Equipment (UE).

Background

The fifth generation (5G) New Radio (NR) specification caters to support for various vertical services and use cases including enhanced mobile broadband (eMBB) services and ultra-reliable low latency communication (URLLC) services. It is desirable to provide support for use cases and Low Power Wide Area (LPWA) networks of extremely low complexity/cost devices through Machine Type Communication (MTC) and narrowband internet of things (NB-IoT) technologies to achieve ultimate coverage and ultra-long battery life.

Recently, it has been recognized that it would be advantageous to support a class of NR User Equipment (UE) with complexity and power consumption levels lower than Rel-15 NR User Equipment (UE), which caters to use cases such as Industrial Wireless Sensor Networks (IWSN), certain types of wearable devices, and video surveillance devices, to fill the gap between current LPWA solutions and eMBB solutions in NR, further facilitating the smooth migration of currently deployed frequency bands from 3.5G and 4G technologies to 5G (NR) technologies, serving related use cases requiring relatively low to moderate reference (e.g., median) and peak user throughput, lower device complexity, smaller device form factor, and longer battery life.

Drawings

Embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

Fig. 1 illustrates a flow diagram of a method for use in a UE in accordance with some embodiments of the present disclosure.

Fig. 2 shows an example of transmission of a PDSCH repetition in the case where the PDSCH repetition partially overlaps certain uplink symbols.

Fig. 3 shows PDSCH aggregation factor and scaling F for each row in the TDRA allocation table₂An example of the configuration of (1).

Fig. 4 shows an example of early termination for an FDD system.

Fig. 5 shows another example of early termination for a TDD system.

Fig. 6 shows yet another example of early termination for a TDD system.

Fig. 7 shows an example of early termination based on updated CSI information.

Fig. 8 shows an example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition.

Fig. 9 shows another example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition.

Fig. 10 shows yet another example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition.

Fig. 11 shows a schematic diagram of a network according to various embodiments of the present disclosure.

Fig. 12 shows a schematic diagram of a wireless network in accordance with various embodiments of the present disclosure.

Fig. 13 illustrates a block diagram of components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments of the present disclosure.

Detailed Description

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the disclosure to others skilled in the art. It will be apparent, however, to one skilled in the art that many alternative embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. It will be apparent, however, to one skilled in the art that alternative embodiments may be practiced without these specific details. In other instances, well-known features may be omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are used repeatedly herein. Such phrases are not generally referring to the same embodiment; however, they may also relate to the same embodiment. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. The phrases "A or B" and "A/B" mean "(A), (B), or (A and B)".

With the development of 5G technology, a reduced capability (RedCap) NR UE can be defined that can be served using the currently specified 5G NR framework with necessary adaptations and enhancements to minimize any adverse impact on network resource utilization, system spectral efficiency, and operational efficiency while limiting device complexity and power consumption.

Some major factors of UE complexity include: the need to support wide channel bandwidth values for Downlink (DL) and Uplink (UL) in the NR (Rel-15 NR mandates support of carriers with bandwidths up to 100MHz (bw) in the frequency band of frequency range 1(FR1) and up to 400MHz in the frequency band of frequency range 2(FR 2)), and the number of receive antennas (Rx antennas) in the DL (most FR1 bands require 4 Rx antennas except for the lowest requirement that the 700MHz band has 2 Rx antennas). Thus, a potential direction to limit UE complexity is to reduce the UE BW requirements and the number of Rx antennas. However, the reliability and coverage of DL reception may be adversely affected, and mechanisms such as Physical Downlink Shared Channel (PDSCH) reception with repetition (e.g., via a slot aggregation approach, where PDSCH transmission is repeated for an indicated number of consecutive available slots) may be considered as a necessary factor to compensate for the reduced coverage due to the reduced number of BW and Rx antennas in the DL.

In NR Rel-15, PDSCH transmission with repetition is supported, which improves the reliability of DL transmission. The number of consecutive slots for PDSCH transmission with repetition is highA layer parameter PDSCH aggregation factor (i.e., PDSCH-aggregation factor) configuration. The Redundancy Version (RV) for the nth (where n is 0, 1, … PDSCH-aggregation factor-1) transmission opportunity (i.e., the nth repetition with repeated PDSCH transmission) applied to a Transport Block (TB) is indicated by the Downlink Control Information (DCI) scheduling the PDSCH transmission with a fixed RV cycle pattern c [ 0231 ]]And rv_idDetermine, i.e., rv (n) ═ mod (c (n) + rv_id,4). PDSCH reception in a certain time slot of a multi-slot PDSCH reception is omitted under certain circumstances (e.g., PDSCH repetition in that time slot overlaps with one or more uplink symbols in that time slot according to a semi-static Time Division Duplex (TDD) UL/DL configuration).

Considering the reduced capability of a recap NR UE, e.g., a UE equipped with a smaller number of Rx antennas, it is expected that having repeated PDSCH transmissions may become more important in a recap NR operation.

Fig. 1 illustrates a flow diagram of a method for use in a UE (e.g., a reccap NR UE) in accordance with some embodiments of the present disclosure. As shown in fig. 1, the method 100 includes: s102, receiving Downlink Control Information (DCI) scheduling a PDSCH transmission with repetition; s104, receiving PDSCH transmission based on DCI; and S106, transmitting HARQ-ACK information for PDSCH transmission.

Specific details of various aspects of the method 100 are described below.

Reduction of number of actual PDSCH repetitions

For PDSCH transmission with repetition, PDSCH reception in a certain time slot of multi-slot PDSCH reception is omitted under certain conditions (e.g., PDSCH repetition in that time slot overlaps with uplink symbols in that time slot according to a semi-static TDD UL/DL configuration). As a result, the actual number of slots for PDSCH transmission is reduced to N, N ≦ N, which is equal to the PDSCH-aggregation factor value configured for PDSCH transmission by the higher layer signaling. The effective coding rate of TBs carried by PDSCH transmissions is increased compared to the case where all N repetitions of the PDSCH transmission are available for reception.

In one embodiment of the present disclosure, the UE may skip decoding of the TB if the actual number of repetitions of PDSCH transmission (also referred to as actual PDSCH repetition number) n is less than a threshold Tn. In this case, the effective coding rate of the TB may become too high to be decoded correctly by the UE, but the UE may still buffer the soft bits of the TB in the n slots of the actual PDSCH repetition. Therefore, when the gbb schedules retransmission of the same TB, soft combining before TB decoding becomes possible.

In one option, the threshold Tn may be predefined in the 5G NR specification or configured by higher layers via NR Residual Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling separately for each pdsch-aggregation factor value. Tn-0 may be predefined or configured for a certain PDSCH-aggregation factor value or values, which in practice means that the UE always reports HARQ-ACK information for PDSCH transmissions for these PDSCH-aggregation factor values.

In one option, the threshold Tn depends on a Modulation Coding Scheme (MCS) field value in the DCI in addition to the pdsch-aggregation factor value. Thus, for a certain pdsch-aggregation factor value, the threshold Tn may be configured separately for each MCS field value or each subset of MCS field values. Tn may be equal to or greater than 0.

In one option, the UE may skip transmission of HARQ-ACK information for TBs (i.e., HARQ-ACK information for PDSCH transmissions) if n is less than the threshold Tn. If this TB is the only TB in the HARQ-ACK codebook, the UE does not report HARQ-ACK information for this TB, which will save Physical Uplink Control Channel (PUCCH) resources. Since repetition may also be configured for PUCCH transmission, PUCCH resources in multiple slots are saved. On the other hand, if this TB is one of the TBs in the HARQ-ACK codebook and a Reed-Muller (Reed-Muller) code is used, it is possible to determine HARQ-ACK information, i.e., NACK, for this TB using an advanced decoding scheme. Accordingly, link performance and/or UL resource efficiency may be improved.

In another option, the UE may skip decoding of the TB if the number of actual PDSCH repetitions, n, is less than a threshold Tn, but expect to send HARQ-ACK information for PDSCH transmissions. This approach ensures robustness to lost DL allocations.

In one option, the UE may skip sending HARQ-ACK information for a TB if the PDSCH transmission is the initial transmission of the TB carried by the PDSCH transmission and n is less than a threshold Tn. Otherwise, the UE needs to report HARQ-ACK information for the TB. In the latter case, the effective coding rate of the TB is reduced after soft HARQ combining. Accordingly, the UE may decode the TB and report HARQ-ACK information for the TB.

In one embodiment of the present disclosure, if the number of actual PDSCH repetitions, n, is reduced, i.e., n<N, then a scaling factor F may be applied in determining a Transport Block Size (TBS) to apply to PDSCH transmission₁(i.e., the UE may be based on the scaling factor F₁Determine TBS to apply to PDSCH transmission). N is equal to the PDSCH-aggregation factor value configured for PDSCH transmission by the higher layer signaling. Scaling factor F₁May be less than or equal to 1, which compensates for the loss of the effective coding rate of the TB.

In one option, the scaling factor F₁May be N/N. Thus, the effective coding rate of the scaled TBS is the same or similar to the effective coding rate of the TBS when all N repetitions of the PDSCH transmission are transmitted.

In one option, the scaling factor F may be selected from a set of scaling factors₁. For example, the value range of n can be divided into a plurality of regions, and different scaling factors F can be applied to different regions₁. In particular, for a region of N containing up to N, F₁May be 1.

In one embodiment of the present disclosure, the RV cycle may be applied to actual PDSCH repetition. Thus, transmission of the systematic bits is guaranteed while transmission of the systematic bits and the parity bits are balanced. That is, the UE may determine an RV cycle applied to actual repetition of PDSCH transmission based on the DCI.

In one embodiment of the disclosure, if all symbols of a PDSCH repetition of a dynamically scheduled PDSCH transmission cannot be transmitted in a time slot, e.g., the PDSCH repetition overlaps with one or more uplink and/or variable symbols in the time slot according to a semi-static TDD UL/DL configuration and/or a time Slot Format Indicator (SFI) for the time slot, the PDSCH repetition may be transmitted on available symbolsThe PDSCH repeats. Implemented by the gNB to ensure that PDSCH can fit over available symbols. Alternatively, if the number of available symbols for PDSCH repetition is equal to or greater than a threshold of X symbols, PDSCH repetition may be transmitted on the available symbols. X may be predefined or configured by higher layer signaling such as MIB, RMSI, or RRC signaling. For example, X may be 2, and PDSCH type B with 2 symbols may be transmitted on two symbols. Scaling factor F₁May be determined by the total time/frequency resources and available time/frequency resources of the N PDSCH repetitions.

Fig. 2 shows one example of transmission of PDSCH repetitions in the case where the PDSCH repetitions partially overlap with certain uplink symbols. In this case, symbols overlapping with the uplink symbols may be omitted. On the other hand, PDSCH transmission is still applied to the remaining available symbols of the PDSCH repetition.

TBS scaling

To achieve reliable DL transmission, PDSCH transmission with repetition is introduced, which fundamentally reduces the effective coding rate of TBs carried by PDSCH transmission. It maintains the TBS but results in a longer HARQ round trip delay (RTT). On the other hand, in order to reduce the effective coding rate of the TB, another method is to utilize the scaling factor F without changing the amount of time/frequency resources₂To reduce TBS, F₂Less than or equal to 1. It maintains the HARQ RTT but results in a TBS reduction. In effect, the PDSCH transmission with repetition can be enabled at the same time and the TBS can be scaled down, balancing TBS and HARQ-RTT.

In one embodiment of the present disclosure, the scaling factor F₂Configured for PDSCH transmission by higher layer signaling, and a scaling factor F₂Can be independent of the configuration of the pdsch-AggregationaFactor. Optionally, a scaling factor F₂The pdsch-aggregation factor configuration can be separately configured for each configuration by higher layer signaling. Configured scaling factor F₂May be applied to all MCS values. Optionally, different scaling factors F are configured for different subsets of MCS values₂. It is also possible to configure the scaling factor F for PDSCH transmission without repetition by higher layer signaling₂。

In one embodiment of the present disclosure, the scaling factor F₂May be dynamically indicated by a separate field in the DCI. In one option, the scaling factor F may be indicated in non-fallback DCI (i.e., DCI format 1_1 and/or 1_2) or fallback DCI (i.e., DCI format 1_0)₂. In another option, for fallback DCI, the scaling factor F is not applied₂。

Optionally, a scaling factor F₂May be additional parameters configured for each row in an allocation table for Time Domain Resource Allocation (TDRA) except for a slot offset K0, a Starting and Length Indication Value (SLIV) of the PDSCH, and a PDSCH mapping type. Optionally, a scaling factor F₂And the PDSCH-aggregation factor value may be two additional parameters configured for each row of the allocation table for the TDRA, except for the slot offset K0, the starting and length indication values of the PDSCH, and the PDSCH mapping type. For example, fig. 3 shows PDSCH aggregation factor and scaling F for each row in the TDRA allocation table₂An example of the configuration of (1).

Early termination with repeated PDSCH transmission

For PDSCH transmissions with N repetitions, it is possible for the UE to correctly decode the TBs carried by the PDSCH transmission based on less than N repetitions. For example, the gNB may conservatively schedule TBs after secondary cell (SCell) activation due to the rather limited available Channel State Information (CSI). Thus, if the channel conditions are actually much better than the assumption of the gNB, the UE can successfully decode the TB based on the first few of the N repetitions of the PDSCH transmission. If the gNB is able to recognize that the UE is likely to decode the TB with less than N repetitions, the gNB may terminate the PDSCH transmission before sending all N repetitions of the PDSCH transmission. In this scheme, although the PDSCH transmission of the TB is terminated early, the transmission timing of HARQ-ACK information for the TB is not changed. That is, HARQ-ACK information for TBs is still transmitted in slots derived based on the nth repetition of PDSCH transmission and PDSCH-to-HARQ feedback timing indicator in DCI.

In one embodiment of the disclosure, the gNB may decide whether to terminate PDSCH transmission prematurely based on HARQ-ACK information reported by the UE for PDSCH transmission with repetition. For PDSCH transmission with N repetitions, M HARQ-ACK feedback opportunities are allocated to the UE, where M < N. The UE may report HARQ-ACK information for the TB at each of the M HARQ-ACK feedback opportunities until an ACK (positive acknowledgement) is reported for the TB. Alternatively, if the UE decodes the TB with less than N repetitions, the UE may report an ACK in the first HARQ-ACK feedback opportunity (if PDSCH processing time is sufficient). However, no NACK (negative acknowledgement) is reported. On the other hand, if the UE did receive all N repetitions of the TB, the UE reports HARQ-ACK information for the TB in the last one of the M HARQ-ACK feedback opportunities. Whether M > 1HARQ-ACK feedback opportunities are supported for PDSCH transmission with repetition may be UE capability.

Note that the same mechanism regarding PUCCH resource determination may be used for early termination of PDSCH transmission in each opportunity. Further, for each opportunity, the UE reports HARQ-ACK information for the PDSCH transmission based on the PDSCH-to-HARQ-timing indicator field.

Fig. 4 shows an example of early termination for an FDD system. As shown in fig. 4, N-8 repetitions of PDSCH transmission may be allocated on consecutive slots in the DL carrier, while M-4 PUCCH resources may be allocated on the UL carrier. The UE may report an ACK in the first PUCCH resource if the UE can correctly decode the TB based on only the first two repetitions of the PDSCH transmission. After calculating the processing time for both the gNB and the UE, the gNB may repeat starting to terminate transmission of the TB from the fifth PDSCH.

Fig. 5 shows another example of early termination for a TDD system. By configuring the appropriate TDD UL/DL configuration, one PUCCH resource may be allocated to the UE after every two repetitions of PDSCH transmission.

If the UE can correctly decode the TB based on only the first two repetitions of the PDSCH transmission, and there is sufficient processing time between the 2 nd repetition (i.e., repetition #2) of the PDSCH transmission and the first PUCCH resource, the UE may report an ACK in the first PUCCH resource. Assuming there is sufficient processing time between the first PUCCH resource and the third repetition of PDSCH transmission (i.e., repetition #3), the gNB may terminate transmission of the TB starting from repetition #3 of PDSCH transmission. On the other hand, if the earliest repetition of the PDSCH transmission with sufficient processing time from the first PUCCH resource is the 4 th repetition of the PDSCH transmission (i.e., repetition #4), the gNB may still transmit repetition #3 of the PDSCH transmission and terminate transmission of the TB from repetition #4 of the PDSCH transmission.

Fig. 6 shows yet another example of early termination for a TDD system. In fig. 6, considering the UE processing time for PDSCH decoding, if the UE can correctly decode the TB based on only the first two repetitions of PDSCH transmission, the UE can report an ACK in the first PUCCH resource with sufficient processing time between repetition #2 of PDSCH transmission and the first PUCCH resource. The gNB still sends repetition #3 of the PDSCH transmission. If there is not enough processing time between the first PUCCH resource and repetition #4 of the PDSCH transmission, the gNB may also need to send repetition #4 of the PDSCH transmission.

In one embodiment of the present disclosure, the gNB may decide whether to prematurely terminate PDSCH transmissions with repetitions based on its own scheduling. For example, if a new CSI report is received from the UE indicating better channel conditions, the gNB may send only X repetitions of the TB, X ≦ N. Here, X is determined based on information at the gNB so that it is possible for the UE to correctly receive the TB at a desired error rate.

Fig. 7 shows an example of early termination based on updated CSI information. As shown in fig. 7, once the gNB receives the updated CSI information and learns better channel conditions for the UE, the gNB may terminate transmission of the TB from the fourth repetition of the PDSCH transmission.

In the above embodiments, if the gNB decides to prematurely terminate the PDSCH transmission with repetition, the gNB may transmit new DCI to explicitly indicate early termination information of the PDSCH transmission. Optionally, the new DCI may indicate that the remaining PDSCH of the TB is repeatedly preempted, e.g., by DCI format 2_1 for the preemption indication. Alternatively, the gNB may schedule a new PDSCH transmission with or without repetition that carries a new TB to the same UE, overlapping the PDSCH transmission with repetition that is to be terminated early. Thus, PDSCH transmissions with repetition terminate from the first overlapping slot. Alternatively, if the UE receives DCI scheduling a new PDSCH transmission and indicating the same HARQ process number as an ongoing PDSCH transmission with repetitions, the UE considers all remaining PDSCH repetitions of the ongoing PDSCH transmission to be terminated. Assuming that the index of the last symbol of DCI is a and the processing time for DCI is B, the UE may consider that the PDSCH repetition scheduled after symbol index a + B is terminated.

Type 1HARQ-ACK codebook

In NR Rel-15, timing values K are fed back based on a set of PDSCH-to-HARQ-values₁A set of row indices of a TDRA table, an active DL bandwidth part (BWP) and a subcarrier spacing of the active UL BWP, and a type 1HARQ-ACK codebook generated by TDD-UL-DL-configuration common parameter (TDD-UL-DL-configuration common) and TDD-UL-DL-configuration dedicated parameter (TDD-UL-DL-configuration Dedicated) configured by higher layer signaling. Feedback timing value K for a certain PDSCH-to-HARQ-feedback₁If at least one row of the TDRA table does not overlap with UL symbols of the tdd-UL-DL-configuration common and tdd-UL-DL-configuration dedicated configurations, one or more HARQ-ACK opportunities may be allocated corresponding to the PDSCH-to-HARQ _ feedback timing value K1. Allocating only one HARQ-ACK opportunity to the PDSCH-to-HARQ-feedback timing value K if the UE does not indicate the ability to receive more than one unicast PDSCH transmission per slot₁. Otherwise, determining a timing value K for the PDSCH-to-HARQ feedback by non-overlapping Start and Length Indication Values (SLIVs) according to the TDRA table and the configured tdd-UL-DL-configuration common and tdd-UL-DL-configuration dedicated₁The number of allocated HARQ-ACK opportunities.

Feedback timing value K for a certain PDSCH-to-HARQ _ feedback in case PDSCH transmission with repetition is configured₁A timing value K for the PDSCH-to-HARQ feedback if at least one PDSCH repetition can be sent in a certain time slot of the PDSCH-aggregation factor time slots₁One or more HARQ-ACK opportunities are allocated. The type 1HARQ-ACK codebook in Rel-15 only checks for overlap of SLIVs in slots. However, for PDSCH transmissions with repetition, overlap across slots is not considered. I.e. with a certain PDSCH-to-HARQ feedbackTiming value K₁The associated PDSCH transmission with repetition may be associated with another PDSCH-to-HARQ _ feedback timing value K₁The associated PDSCH transmissions with repetitions overlap.

In one embodiment of the present disclosure, the size of the type 1HARQ-ACK codebook may be further reduced by considering the overlap of PDSCH transmissions with repetitions across the time slots used for these PDSCH transmissions, which is particularly advantageous for a reccap NR UE, since the UE may have a limited number of transmit antennas, which limits uplink performance. A set of PDSCH-to-HARQ _ feedback timing values K may be transmitted₁Into one or more subsets. One PDSCH-to-HARQ-feedback timing value K₁Pertaining only to PDSCH-to-HARQ-feedback timing value K₁A subset of (a). For UL slot n, based on the subcarrier spacing of active DL-BWP and active UL-BWP, if a certain PDSCH-to-HARQ _ feedback timing value K₁PDSCH transmission that is not available for scheduling HARQ-ACK transmission in UL slot n, then it does not belong to any K₁A subset. If a set of PDSCH-to-HARQ-feedback timing values K₁Division into M subsets, M>1, then there is one PDSCH-to-HARQ feedback timing value K in each of the M subsets₁Make timing values K feedback with M PDSCH-to-HARQ-₁The associated PDSCH transmissions with repetitions do not overlap. In each subset, feedback timing value K with a certain PDSCH-to-HARQ-in that subset₁The associated PDSCH transmission with repetition may be associated with all other PDSCH-to-HARQ _ feedback timing values K in the subset₁The associated PDSCH transmissions with repetitions overlap.

In one option, the timing value K is fed back for the configured PDSCH-aggregation factor and PDSCH-to-HARQ _ feedback₁May correspond to a PDSCH-to-HARQ feedback timing value K₁Allocates zero, one, or multiple HARQ-ACK opportunities. Timing value K for PDSCH-to-HARQ-feedback₁Is equal to the maximum number of non-overlapping available SLIVs, based on a set of row indices of the TDRA table, subcarrier spacing of active DL BWP and active UL BWP, and tdd-UL-DL-configuration common and tdd-UL-DL-ConfigurationDedicated. According to the configured tdd-UL-DL-configuration Common and tdd-UL-DL-configuration dedicated, if the SLIV associated with a row of the TDRA table is not associated with a PDSCH-AggregationFactor time slot by that K₁Any one K in the subset₁And if the determined UL symbols in at least one time slot are overlapped, the SLIV is considered to be available.

In one option, for the configured pdsch-aggregation factor and slot timing value K₁May correspond to the K₁The subset is allocated at most one HARQ-ACK opportunity. If at least one row of the TDRA table does not correspond to the K of the pdsch-aggregation factor time slots₁Any one K in the subset₁Determining that UL symbols in the at least one slot overlap, corresponding to the K according to the configured tdd-UL-DL-configuration Common and tdd-UL-DL-configuration determined₁The subset allocates one HARQ-ACK opportunity. Otherwise, no assignment corresponds to this K₁HARQ-ACK opportunities for the subset.

Fig. 8 shows an example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition. As shown in fig. 8, configured K₁Values of 9, 8, 7, 6, 5, 4, 3 and 2. Two HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook. For using K₁A potential PDSCH transmission scheduled with a value of 9, 8, 7 or 6, i.e., PDSCH transmission 401, 402, 403 or 404, uses the first HARQ-ACK opportunity. On the other hand, for using K₁Potential PDSCH transmissions, i.e., PDSCH transmissions 405, 406, 407, or 408, scheduled with values of 5, 4, 3, or 2 use the second HARQ-ACK opportunity.

In one option, if the pdsch-aggregation factor value can be dynamically indicated by, for example, DCI format 1_1 and/or 1_2, and the minimum pdsch-aggregation factor value that can be indicated is a factor of all other pdsch-aggregation factor values that can be indicated, a type 1HARQ-ACK codebook can be generated with the minimum pdsch-aggregation factor value that can be indicated. For PDSCH transmissions scheduled with a larger PDSCH-aggregation factor value and ending in a certain slot, the same HARQ-ACK opportunity may be determined as for PDSCH transmissions scheduled with the smallest PDSCH-aggregation factor value that can be indicated and ending in the same slot.

Fig. 9 shows another example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition. Assume that the RRC signaling configures the values 4 and 2 for the pdsch-aggregation factor. The type 1HARQ-ACK codebook may be derived from a pdsch aggregation factor value of 2. In this example, K is configured₁Values of 5, 4, 3 and 2. Two HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook. For using K₁A value 5 or 4 scheduled PDSCH transmission, i.e., PDSCH transmission 541, 542, 521, or 522, uses the first HARQ-ACK opportunity. On the other hand, for using K₁A value 3 or 2 scheduled PDSCH transmission, i.e., PDSCH transmission 543, 544, 523, or 524, uses the second HARQ-ACK opportunity.

In one embodiment of the present disclosure, the type 1HARQ-ACK codebook may be generated from the minimum specifiable PDSCH-aggregation factor value of DCI format 1_1 and/or 1_2, and the HARQ-ACK opportunities in the type 1HARQ-ACK codebook are also applied to the PDSCH scheduled by DCI format 1_ 0. Corresponding to HARQ-ACK opportunities in the type 1HARQ-ACK codebook, if the same HARQ-ACK opportunity is not used by another PDSCH transmission with repetition scheduled by DCI format 1_1 or 1_2, a maximum of one PDSCH transmission may be scheduled through DCI format 1_ 0.

In one option, for a PDSCH transmission in a certain slot scheduled by DCI format 1_0, the HARQ-ACK opportunity for that PDSCH transmission is the same as the HARQ-ACK opportunity for a PDSCH transmission that may be scheduled by DCI format 1_1 or 1_2, has the smallest PDSCH-aggregation factor that can be indicated, and ends in the same slot.

Fig. 10 shows yet another example of a type 1HARQ-ACK codebook for PDSCH transmission with repetition. Two HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook. For using K₁A value 5 or 4 scheduled PDSCH transmission, i.e., PDSCH transmission 641, 642, 621, 622, 611, or 612, uses the first HARQ-ACK opportunity. On the other hand, for using K₁A value 3 or 2 scheduled PDSCH transmission, i.e., PDSCH transmission 643, 644, 623, 624, 613, or 614, uses the second HARQ-ACK opportunity. PDSCH transmissions 611-614 are PDs potentially scheduled by DCI format 1_0SCH transmission.

In another option, if a PDSCH transmission with repetition can be scheduled by DCI format 1_0, then for a PDSCH transmission scheduled by DCI format 1_0 and ending in a certain slot, the HARQ-ACK opportunity for that PDSCH is the same as the HARQ-ACK opportunity for a PDSCH transmission with repetition that can be scheduled by DCI format 1_1 or 1_2, has the smallest PDSCH-aggregation factor that can be indicated, and ends in the same slot.

In NR Rel-15, a group of K is available₁The value is predefined K ═ {8, 7, 6, 5, 4, 3, 2, 1}, whereas K for DCI formats 1_1 or 1_2₁The set of values may be configured by higher layer signaling. According to the design, only the set K and the set K configured for the DCI format 1_1 or 1_2 through high-layer signaling₁K in the intersection of (1)₁The value may be for DCI format 1_ 0.

In one embodiment of the present disclosure, if a PDSCH transmission with repetition may be scheduled by DCI format 1_0 and the PDSCH-aggregation factor value of DCI format 1_0 may be different from the PDSCH-aggregation factor value of DCI formats 1_1 and/or 1_2, the type 1HARQ-ACK codebook may be generated by the minimum value of the PDSCH-aggregation factors of DCI formats 1_0, 1_1, and 1_ 2. The available value or set of values for the pdsch-aggregation factor of DCI format 1_0 may be predefined or configured by a main system information block (MIB), a System Information (SI) message, or UE-specific RRC signaling. For PDSCH transmissions scheduled with a larger PDSCH-aggregation factor value, the same HARQ-ACK opportunity may be determined as for PDSCH transmissions scheduled with the smallest PDSCH-aggregation factor that can be indicated and ending in the same slot.

System and implementation

Fig. 11-12 illustrate various systems, devices, and components that can implement aspects of the disclosed embodiments.

Fig. 11 shows a schematic diagram of a network 1100 according to various embodiments of the present disclosure. The network 1100 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G/NR systems. However, the exemplary embodiments are not limited in this respect and the described embodiments may be applied to other networks, such as future 3GPP systems and the like, which benefit from the principles described herein.

Network 1100 may include a UE 1102, which may include any mobile or non-mobile computing device designed to communicate with a Radio Access Network (RAN)1104 via an over-the-air connection. The UE 1102 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a heads-up display device, an in-vehicle diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic/engine control unit, an electronic/engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network device, a machine-type communication device, a machine-to-machine (M2M) or device-to-device (D2D) device, an internet of things device, and/or the like.

In some embodiments, network 1100 may include multiple UEs directly coupled to each other through secondary link interfaces. The UE may be an M2M/D2D device that communicates using a physical secondary link channel (e.g., without limitation, a physical secondary link broadcast channel (PSBCH), a physical secondary link discovery channel (PSDCH), a physical secondary link shared channel (PSSCH), a physical secondary link control channel (PSCCH), a physical secondary link fundamental channel (PSFCH), etc.).

In some embodiments, the UE 1102 may also communicate with an Access Point (AP)1106 over an over-the-air connection. AP 1106 may manage WLAN connections, which may be used to offload some/all network traffic from RAN 1104. The connection between the UE 1102 and the AP 1106 may be in accordance with any IEEE 802.11 protocol, wherein the AP 1106 may be wireless fidelity (WiFi)

A router. In some embodiments, UE 1102, RAN 1104, and AP 1106 may utilize cellular Wireless Local Area Network (WLAN) aggregation (e.g., LTE-WLAN aggregation (LWA)/lightweight ip (lwip)). Cellular WLAN aggregation may involve a UE 1102 configured by the RAN 1104 to utilize both cellular radio resources and WLAN resources.

The RAN 1104 may include one or more access nodes, e.g., AN 1108. The AN 1108 may terminate the air interface protocols of the UE 1102 by providing access stratum protocols including radio resource control protocol (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and L1 protocols. In this manner, the AN 1108 may enable a data/voice connection between the Core Network (CN)1120 and the UE 1102. In some embodiments, the AN 1108 may be implemented in a discrete device, or as one or more software entities running on a server computer (as part of a virtual network, which may be referred to as a distributed ran (cran) or virtual baseband unit pool, for example). AN 1108 may be referred to as a Base Station (BS), next generation base station (gNB), RAN node, evolved node b (enb), next generation enb (ng enb), node b (nodeb), roadside unit (RSU), TRxP, Transmission Reception Point (TRP), etc. The AN 1108 may be a macrocell base station or a low power base station for providing microcells, picocells, or other similar cells having smaller coverage areas, smaller user capacities, or higher bandwidths than macrocells.

In embodiments where the RAN 1104 comprises multiple ANs, they may be coupled to each other through AN X2 interface (if the RAN 1104 is AN LTE RAN) or AN Xn interface (if the RAN 1104 is a 5G RAN). In some embodiments, the X2/Xn interface, which may be separated into a control/user plane interface, may allow the AN to communicate information related to handover, data/context transfer, mobility, load management, interference coordination, and the like.

The AN of RAN 1104 can manage one or more cells, groups of cells, component carriers, etc., respectively, to provide UE 1102 with AN air interface for network access. The UE 1102 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 1104. For example, UE 1102 and RAN 1104 may use carrier aggregation to allow UE 1102 to connect with multiple component carriers, each corresponding to a primary cell (Pcell) or a secondary cell (Scell). In a dual connectivity scenario, the first AN may be a master node providing a Master Cell Group (MCG) and the second AN may be a secondary node providing a Secondary Cell Group (SCG). The first/second AN may be any combination of eNB, gNB, ng eNB, etc.

RAN 1104 may provide an air interface over a licensed spectrum or an unlicensed spectrum. To operate in unlicensed spectrum, a node may use a License Assisted Access (LAA), enhanced LAA (elaa), and/or further enhanced LAA (felaa) mechanism based on the Carrier Aggregation (CA) technique of PCell/Scell. Prior to accessing the unlicensed spectrum, the node may perform a media/carrier sensing operation based on, for example, a Listen Before Talk (LBT) protocol.

In a vehicle-to-everything (V2X) scenario, the UE 1102 or AN 1108 may be or act as a Road Side Unit (RSU), which may refer to any transport infrastructure entity for V2X communications. The RSU may be implemented in or by AN appropriate AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; RSUs implemented in the next generation nodeb (gNB) or implemented by the gNB may be referred to as "gNB-type RSUs" or the like. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the curb side that provides connection support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high speed events (e.g., collision avoidance, traffic warnings, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, RAN 1104 may be an LTE RAN 1110 including an evolved node b (eNB), e.g., eNB 1112. The LTE RAN 1110 may provide an LTE air interface with the following features: SCS at 15 kHz; SC-FDMA waveform for UL and CP-OFDM waveform for DL; turbo codes for data and TBCC for control, etc. The LTE air interface can rely on the CSI-RS to carry out CSI acquisition and beam management; relying on a PDSCH/PDCCH demodulation reference signal (DMRS) to demodulate the PDSCH/PDCCH; and relying on CRS for cell search and initial acquisition, channel quality measurements, and channel estimation, and on channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate on the sub-6 GHz band.

In some embodiments, RAN 1104 may be a Next Generation (NG) -RAN1114 having a gNB (e.g., gNB 1116) or a gn-eNB (e.g., NG-eNB 1118). The gNB 1116 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1116 may be connected to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 1118 may also be connected with the 5G core over the NG interface, but may be connected with the UE over the LTE air interface. The gNB 1116 and the ng-eNB 1118 may be connected to each other through an Xn interface.

In some embodiments, the NG interface may be divided into two parts, a NG user plane (NG-U) interface, which carries traffic data between nodes of the UPF 1148 and the NG-RAN1114 (e.g., the N3 interface), and a NG control plane (NG-C) interface, which is a signaling interface between the access and mobility management function (AMF)1144 and nodes of the NG-RAN1114 (e.g., the N2 interface).

The NG-RAN1114 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM for UL, and DFT-s-OFDM; polarity, repetition, simplex, and reed-muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; performing phase tracking of the PDSCH using the PTRS; and time tracking using the tracking reference signal. The 5G-NR air interface may operate over the FR1 frequency band, which includes a sub-6 GHz frequency band, or the FR2 frequency band, which includes a 24.25GHz to 52.6GHz frequency band. The 5G-NR air interface may include SSBs, which are regions of a downlink resource grid including PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may use BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE 1102 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When the BWP change is indicated to the UE 1102, the SCS of the transmission also changes. Another use case for BWP is related to power saving. In particular, the UE 1102 may be configured with multiple BWPs with different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs containing a smaller number of PRBs may be used for data transmission with smaller traffic load while allowing power savings at the UE 1102 and, in some cases, at the gNB 1116. BWPs containing a large number of PRBs may be used in scenarios with higher traffic loads.

RAN 1104 is communicatively coupled to CN 1120, which comprises network elements, to provide various functions to support data and telecommunications services to customers/subscribers (e.g., users of UE 1102). The components of CN 1120 may be implemented in one physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN 1120 onto physical computing/storage resources in servers, switches, and the like. Logical instances of CN 1120 may be referred to as network slices and logical instances of a portion of CN 1120 may be referred to as network subslices.

In some embodiments, CN 1120 may be LTE CN 1122, which may also be referred to as EPC. LTE CN 1122 may include a Mobility Management Entity (MME)1124, a Serving Gateway (SGW)1126, a serving General Packet Radio Service (GPRS) support node (SGSN)1128, a Home Subscriber Server (HSS)1130, a Proxy Gateway (PGW)1132, and a policy control and charging rules function (PCRF)1134, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of LTE CN 1122 can be briefly introduced as follows.

The MME 1124 may implement mobility management functions to track the current location of the UE 1102 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, etc.

The SGW 1126 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1122. SGW 1126 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, billing, and some policy enforcement.

The SGSN 1128 may track the location of the UE 1102 and perform security functions and access control. In addition, SGSN 1128 may perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1124; MME selection for handover, etc. An S3 reference point between the MME 1124 and the SGSN 1128 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active state.

HSS 1130 may include a database for network users that includes subscription-related information that supports network entities handling communication sessions. HSS 1130 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependency, etc. An S6a reference point between HSS 1130 and MME 1124 may enable the transmission of subscription and authentication data for authenticating/authorizing user access to LTE CN 1120.

PGW 1132 may terminate the SGi interface towards a Data Network (DN)1136, which may include an application/content server 1138. The PGW 1132 may route data packets between the LTE CN 1122 and the data network 1136. PGW 1132 may be coupled to SGW 1126 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1132 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Additionally, the SGi reference point between PGW 1132 and data network 1136 may be, for example, an operator external public, private PDN, or an operator internal packet data network for providing IMS services. PGW 1132 may be coupled to PCRF 1134 via a Gx reference point.

PCRF 1134 is a policy and charging control element of LTE CN 1122. The PCRF 1134 may be communicatively coupled to the application/content server 1138 to determine appropriate quality of service (QoS) and charging parameters for the service flow. PCRF 1132 may provide relevant rules to PCEF (via the Gx reference point) with appropriate Traffic Flow Templates (TFTs) and QoS Class Identifiers (QCIs).

In some embodiments, CN 1120 may be a 5G core network (5GC) 1140. The 5GC 1140 may include an authentication server function (AUSF)1142, an access and mobility management function (AMF)1144, a Session Management Function (SMF)1146, a User Plane Function (UPF)1148, a Network Slice Selection Function (NSSF)1150, a network open function (NEF)1152, an NF storage function (NRF)1154, a Policy Control Function (PCF)1156, a Unified Data Management (UDM)1158, and an Application Function (AF)1160, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of the 5GC 1140 can be briefly described as follows.

The AUSF1142 may store data for authentication of the UE 1102 and process authentication related functions. The AUSF1142 may facilitate a common authentication framework for various access types. The AUSF1142 may exhibit a Nausf service based interface in addition to communicating with other elements of the 5GC 1140 through reference points as shown.

The AMF 1144 may allow other functions of the 5GC 1140 to communicate with the UE 1102 and the RAN 1104 and subscribe to notification of a mobility event with respect to the UE 1102. The AMF 1144 may be responsible for registration management (e.g., registering the UE 1102), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. AMF 1144 may provide for transmission of Session Management (SM) messages between UE 1102 and SMF 1146 and act as a transparent proxy for routing SM messages. The AMF 1144 may also provide for the transmission of SMS messages between the UE 1102 and the SMSF. The AMF 1144 may interact with the AUSF1142 and the UE 1102 to perform various security anchoring and context management functions. Further, AMF 1144 may be a termination point of the RAN CP interface, which may include or be an N2 reference point between RAN 1104 and AMF 1144; the AMF 1144 may act as a termination point for NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 1144 may also support NAS signaling with the UE 1102 over the N3 IWF interface.

The SMF 1146 may be responsible for SM (e.g., tunnel management between the UPF 1148 and the AN 1108, session establishment); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring flow control at the UPF 1148 to route traffic to the appropriate destination; termination of the interface to the policy control function; controlling a portion of policy enforcement, charging, and QoS; lawful interception (for SM events and interface to the LI system); terminate the SM portion of the NAS message; a downlink data notification; initiating AN specific SM message (sent to AN 1108 over N2 through AMF 1144); and determining an SSC pattern for the session. SM may refer to management of PDU sessions, and a PDU session or "session" may refer to a PDU connection service that provides or enables exchange of PDUs between the UE 1102 and the data network 1136.

The UPF 1148 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point to interconnect with the data network 1136, and a branch point to support multi-homed PDU sessions. The UPF 1148 may also perform packet routing and forwarding, perform packet inspection, perform user plane part of policy rules, lawful intercepted packets (IP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1148 may include an uplink classifier to support routing of traffic flows to a data network.

The NSSF 1150 may select a set of network slice instances that serve the UE 1102. NSSF 1150 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and mapping to a single NSSAI (S-NSSAI) of the subscription, if desired. The NSSF 1150 may also determine a set of AMFs to be used to serve the UE 1102, or determine a list of candidate AMFs, based on a suitable configuration and possibly by querying the NRF 1154. The selection of a set of network slice instances for the UE 1102 may be triggered by the AMF 1144 (with which the UE 1102 registers by interacting with the NSSF 1150), which may result in a change in the AMF. NSSF 1150 may interact with AMF 1144 via N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Further, the NSSF 1150 may expose an interface based on the NSSF service.

NEF 1152 may securely disclose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 1160), edge computing or fog computing systems, and the like. In these embodiments, NEF 1152 may authenticate, authorize, or limit AF. NEF 1152 may also translate information exchanged with AF 1160 and information exchanged with internal network functions. For example, the NEF 1152 may convert between the AF service identifier and the internal 5GC information. NEF 1152 may also receive information from other NFs based on their public capabilities. This information may be stored as structured data at NEF 1152 or at data store NF using a standardized interface. NEF 1152 may then re-expose the stored information to other NFs and AFs, or for other purposes such as analysis. In addition, NEF 1152 may expose an interface based on the Nnef service.

NRF 1154 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1154 also maintains information on available NF instances and the services it supports. As used herein, the terms "instantiate," "instance," and the like may refer to creating an instance, "instance" may refer to a specific occurrence of an object, which may occur, for example, during execution of program code. Further, NRF 1154 may expose an interface based on an nrrf service.

PCF 1156 may provide policy rules to control plane functions to perform them and may also support a unified policy framework to manage network behavior. The PCF 1156 may also implement a front end to access subscription information related to policy decisions in the UDR of the UDM 1158. In addition to communicating with functions through reference points as shown, PCF 1156 also presents an interface based on Npcf services.

The UDM 1158 may process subscription-related information to support network entities handling communication sessions and may store subscription data for the UE 1102. For example, subscription data may be communicated via the N8 reference point between UDM 1158 and AMF 1144. The UDM 1158 may comprise two parts: application front end and User Data Record (UDR). The UDR may store policy data and subscription data for UDM 1158 and PCF 1156, and/or structured data and application data for exposure for NEF 1152 (including PFD for application detection, application request information for multiple UEs 1102). UDR 221 may expose an Nudr service-based interface to allow UDM 1158, PCF 1156, and NEF 1152 to access a particular collection of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE (UDM front end) that is responsible for handling credentials, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. UDM 1158 may expose a numm service based interface in addition to communicating with other NFs through reference points as shown.

AF 1160 may provide application impact on traffic routing, provide access to NEF, and interact with policy framework for policy control.

In some embodiments, the 5GC 1140 may enable edge computing by selecting operator/third party services geographically close to the point where the UE 1102 connects to the network. This may reduce delay and load on the network. To provide an edge computing implementation, the 5GC 1140 may select a UPF 1148 close to the UE 1102 and perform traffic steering from the UPF 1148 to the data network 1136 over an N6 interface. This may be based on UE subscription data, UE location, and information provided by AF 1160. In this way, AF 1160 may influence UPF (re) selection and traffic routing. Based on operator deployment, the network operator may allow AF 1160 to interact directly with the relevant NFs when AF 1160 is considered a trusted entity. In addition, AF 1160 may expose interfaces based on Naf services.

The data network 1136 may represent various network operator services, internet access, or third party services that may be provided by one or more servers, including, for example, an application/content server 1138.

Fig. 12 schematically illustrates a wireless network 1200 in accordance with various embodiments. The wireless network 1200 may include a UE 1202 in wireless communication with AN 1204. The UE 1202 and the AN 1204 may be similar to and substantially interchangeable with like-named components described elsewhere herein.

The UE 1202 may be communicatively coupled with AN 1204 via a connection 1206. Connection 1206 is shown as an air interface to enable communicative coupling and may be consistent with a cellular communication protocol operating at millimeter-wave or sub-6 GHz frequencies, such as the LTE protocol or the 5G NR protocol.

The UE 1202 may include a host platform 1208 coupled with a modem platform 1210. Host platform 1208 may include application processing circuitry 1212, which may be coupled with protocol processing circuitry 1214 of modem platform 1210. The application processing circuitry 1212 may run various applications of source/receiver application data for the UE 1202. The application processing circuitry 1212 may also implement one or more layers of operations to send/receive application data to/from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

The protocol processing circuitry 1214 may implement one or more layers of operations to facilitate the transmission or reception of data over connection 1206. Layer operations implemented by the protocol processing circuitry 1214 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

The modem platform 1210 may further include digital baseband circuitry 1216, which digital baseband circuitry 1216 may implement one or more layer operations of "lower" layer operations performed by the protocol processing circuitry 1214 in the network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, wherein these functions may include one or more of space-time, space-frequency, or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem platform 1210 may further include transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, and RF front end (RFFE) circuitry 1224, which may include or be connected to one or more antenna panels 1226. Briefly, the transmit circuitry 1218 may include digital-to-analog converters, mixers, Intermediate Frequency (IF) components, and the like; the receive circuit 1220 may include an analog-to-digital converter, a mixer, IF components, etc.; RF circuitry 1222 may include low noise amplifiers, power tracking components, and so forth; RFFE circuitry 1224 can include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of components of transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, RFFE circuitry 1224, and antenna panel 1226 (collectively, "transmit/receive components") may be specific to details of a particular implementation, e.g., whether the communication is Time Division Multiplexed (TDM) or Frequency Division Multiplexed (FDM), at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in a plurality of parallel transmit/receive chains, and may be arranged in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1214 may include one or more instances of control circuitry (not shown) to provide control functionality for the transmit/receive components.

UE reception may be established by and via antenna panel 1226, RFFE circuitry 1224, RF circuitry 1222, receive circuitry 1220, digital baseband circuitry 1216, and protocol processing circuitry 1214. In some embodiments, antenna panel 1226 may receive transmissions from AN 1204 by receiving beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 1226.

UE transmissions may be established via and through the protocol processing circuitry 1214, the digital baseband circuitry 1216, the transmit circuitry 1218, the RF circuitry 1222, the RFFE circuitry 1224, and the antenna panel 1226. In some embodiments, a transmit component of UE 1204 may apply a spatial filter to the data to be transmitted to form a transmit beam transmitted by the antenna elements of antenna panel 1226.

Similar to UE 1202, AN 1204 can include a host platform 1228 coupled with a modem platform 1230. The host platform 1228 may include application processing circuitry 1232 coupled to protocol processing circuitry 1234 of the modem platform 1230. The modem platform may also include digital baseband circuitry 1236, transmit circuitry 1238, receive circuitry 1240, RF circuitry 1242, RFFE circuitry 1244, and antenna panel 1246. The components of AN 1204 can be similar to, and substantially interchangeable with, the synonymous components of UE 1202. In addition to performing data transmission/reception as described above, the components of AN 1208 may perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 13 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments. In particular, fig. 13 shows a schematic diagram of hardware resources 1300, hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory/storage devices 1320, and one or more communication resources 1330, where each of these processors, memory/storage devices, and communication resources may be communicatively coupled via a bus 1340 or other interface circuitry. For embodiments utilizing node virtualization (e.g., Network Function Virtualization (NFV)), hypervisor 1302 may be executed to provide an execution environment for one or more network slices/subslices to utilize hardware resources 1300.

Processor 1310 may include, for example, processor 1312 and processor 1314. The processor 1310 may be, for example, a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Radio Frequency Integrated Circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

Memory/storage 1320 may include a main memory, a disk storage device, or any suitable combination thereof. The memory/storage 1320 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, and the like.

Communication resources 1330 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 130 via a network 13084 or one or more databases 1306 or other network elements. For example, communication resources 1330 can include wired communication components (e.g., for coupling via USB, ethernet, etc.), cellular communication components, Near Field Communication (NFC) components, wireless communication components, and/or the like,

(or

Low energy) assembly,

Components, and other communication components.

The instructions 1350 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 1310 to perform any one or more of the methods discussed herein. The instructions 1350 may reside, completely or partially, within at least one of the processor 1310 (e.g., in a cache of the processor), the memory/storage 1320, or any suitable combination thereof. Further, any portion of instructions 1350 may be transmitted to hardware resource 1300 from any combination of peripherals 1304 or database 1306. Thus, the memory of processor 1310, memory/storage 1320, peripherals 1304, and database 1306 are examples of computer-readable and machine-readable media.

The following paragraphs describe examples of various embodiments.

Example 1 includes an apparatus for use in a User Equipment (UE), comprising: a Radio Frequency (RF) interface; and a processor circuit coupled to the RF interface, the processor circuit to: receiving, via the RF interface, Downlink Control Information (DCI) that schedules a Physical Downlink Shared Channel (PDSCH) transmission having repetitions; receiving, via the RF interface, the PDSCH transmission based on the DCI; and transmitting HARQ-ACK information for the PDSCH transmission via the RF interface.

Example 2 includes the apparatus of example 1, wherein the processor circuit is further to: skipping decoding of a Transport Block (TB) carried by the PDSCH transmission when the actual number of repetitions of the PDSCH transmission is less than a threshold.

Example 3 includes the apparatus of example 2, wherein the processor circuit is further to: determining the threshold based on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 4 includes the apparatus of example 2, wherein the processor circuit is further to: skipping transmission of HARQ-ACK information for the PDSCH transmission when the PDSCH transmission is an initial PDSCH transmission.

Example 5 includes the apparatus of example 1, wherein the processor circuit is further to: determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor when an actual number of repetitions of the PDSCH transmission is less than a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 6 includes the apparatus of example 5, wherein the scaling factor is equal to an actual number of repetitions of the PDSCH transmission divided by the PDSCH aggregation factor value, or the scaling factor is selected from a set of scaling factors based on the actual number of repetitions of the PDSCH transmission.

Example 7 includes the apparatus of example 1, wherein the processor circuit is further to: determining a Redundancy Version (RV) cycle to apply to an actual repetition of the PDSCH transmission based on the DCI.

Example 8 includes the apparatus of example 1, wherein the processor circuit is further to: receiving a repetition of the PDSCH transmission on an available symbol for the PDSCH transmission in a slot when a number of the available symbols for the repetition is greater than a threshold.

Example 9 includes the apparatus of example 1, wherein the processor circuit is further to: determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor, wherein the scaling factor is configured for the PDSCH transmission by higher layer signaling.

Example 10 includes the apparatus of example 9, wherein the scaling factor depends on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 11 includes the apparatus of example 9, wherein the scaling factor is dynamically indicated by a separate field in the DCI or as an additional parameter in a Time Domain Resource Allocation (TDRA) table indexed by a TDRA field in the DCI.

Example 12 includes the apparatus of example 1, wherein the processor circuit is further to: transmitting HARQ-ACK information for the PDSCH transmission with correct decoding of Transport Blocks (TBs) carried by the PDSCH transmission prior to receiving all repetitions of the PDSCH transmission.

Example 13 includes the apparatus of example 1, wherein the processor circuit is further to: generating a type 1HARQ-ACK codebook considering an overlap of PDSCH transmissions spanning slots for PDSCH transmissions having the overlap, wherein HARQ-ACK information for the PDSCH transmissions is contained in the type 1HARQ-ACK codebook.

Example 14 includes the apparatus of example 13, wherein the processor circuit is further to: for a subset of PDSCH-to-HARQ _ feedback timing values, allocating one or more HARQ-ACK opportunities in the type 1HARQ-ACK codebook corresponding to the subset of PDSCH-to-HARQ _ feedback timing values.

Example 15 includes the apparatus of example 13, wherein the processor circuit is further to: for a subset of PDSCH-to-HARQ _ feedback timing values, at most one HARQ-ACK opportunity corresponding to the subset of PDSCH-to-HARQ _ feedback timing values is allocated in the type 1HARQ-ACK codebook.

Example 16 includes the apparatus of example 15, wherein the processor circuit is further to: allocating one HARQ-ACK opportunity corresponding to a subset of the PDSCH-to-HARQ feedback timing values in the type 1HARQ-ACK codebook based on a time division duplex-UL-DL-configuration common parameter and a time division duplex-UL-DL-configuration dedicated parameter configured by higher layer signaling when at least one row in a Time Domain Resource Allocation (TDRA) table does not overlap with an uplink symbol in at least one time slot determined by any one PDSH-to-HARQ _ feedback timing value in the subset of the PDSCH-to-HARQ _ feedback timing values in a time slot used for the PDSCH transmission.

Example 17 includes the apparatus of example 15, wherein the processor circuit is further to: generating the type 1HARQ-ACK codebook based on the minimum PDSCH aggregation factor value that can be indicated when PDSCH aggregation factor values can be dynamically indicated by various DCI formats and the minimum PDSCH aggregation factor value that can be indicated is a factor of all other PDSCH aggregation factor values that can be indicated.

Example 18 includes the apparatus of example 17, wherein the processor circuit is further to: for a PDSCH transmission scheduled with a PDSCH aggregation factor value larger than the minimum indictable PDSCH aggregation factor value and ending in one time slot, allocating the same HARQ-ACK opportunity in the type 1HARQ-ACK codebook as a PDSCH transmission scheduled with the minimum indictable PDSCH aggregation factor value and ending in the same time slot.

Example 19 includes the apparatus of example 15, wherein the processor circuit is further to: for PDSCH transmissions scheduled by DCI format 1_0 with or without repetition, HARQ-ACK opportunities not used by another PDSCH transmission scheduled by DCI format 1_1 or 1_2 with repetition are allocated in the type 1HARQ-ACK codebook.

Example 20 includes the apparatus of example 19, wherein the processor circuit is further to: for PDSCH transmissions scheduled by the DCI format 1_0 and ending in one slot with or without repetition, the same HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook as for the PDSCH transmissions with repetition scheduled by the DCI format 1_1 or 1_2 and ending in the same slot.

Example 21 includes a method for use in a User Equipment (UE), comprising: receiving, via a Radio Frequency (RF) interface, Downlink Control Information (DCI) that schedules a Physical Downlink Shared Channel (PDSCH) transmission having repetitions; receiving, via the RF interface, the PDSCH transmission based on the DCI; and transmitting HARQ-ACK information for the PDSCH transmission via the RF interface.

Example 22 includes the method of example 21, further comprising: skipping decoding of a Transport Block (TB) carried by the PDSCH transmission when the actual number of repetitions of the PDSCH transmission is less than a threshold.

Example 23 includes the method of example 22, further comprising: determining the threshold based on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 24 includes the method of example 22, further comprising: skipping transmission of HARQ-ACK information for the PDSCH transmission when the PDSCH transmission is an initial PDSCH transmission.

Example 25 includes the method of example 21, further comprising: determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor when an actual number of repetitions of the PDSCH transmission is less than a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 26 includes the method of example 25, wherein the scaling factor is equal to an actual number of repetitions of the PDSCH transmission divided by the PDSCH aggregation factor value, or the scaling factor is selected from a set of scaling factors based on the actual number of repetitions of the PDSCH transmission.

Example 27 includes the method of example 21, further comprising: determining a Redundancy Version (RV) cycle to apply to an actual repetition of the PDSCH transmission based on the DCI.

Example 28 includes the method of example 21, further comprising: receiving a repetition of the PDSCH transmission on an available symbol for the PDSCH transmission in a slot when a number of the available symbols for the repetition is greater than a threshold.

Example 29 includes the method of example 21, further comprising: determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor, wherein the scaling factor is configured for the PDSCH transmission by higher layer signaling.

Example 30 includes the method of example 29, wherein the scaling factor depends on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

Example 31 includes the method of example 29, wherein the scaling factor is dynamically indicated by a separate field in the DCI or as an additional parameter in a Time Domain Resource Allocation (TDRA) table indexed by a TDRA field in the DCI.

Example 32 includes the method of example 21, further comprising: transmitting HARQ-ACK information for the PDSCH transmission with correct decoding of Transport Blocks (TBs) carried by the PDSCH transmission prior to receiving all repetitions of the PDSCH transmission.

Example 33 includes the method of example 21, further comprising: generating a type 1HARQ-ACK codebook considering an overlap of PDSCH transmissions spanning slots for PDSCH transmissions having the overlap, wherein HARQ-ACK information for the PDSCH transmissions is contained in the type 1HARQ-ACK codebook.

Example 34 includes the method of example 33, further comprising: for a subset of PDSCH-to-HARQ _ feedback timing values, allocating one or more HARQ-ACK opportunities in the type 1HARQ-ACK codebook corresponding to the subset of PDSCH-to-HARQ _ feedback timing values.

Example 35 includes the method of example 33, further comprising: for a subset of PDSCH-to-HARQ _ feedback timing values, at most one HARQ-ACK opportunity corresponding to the subset of PDSCH-to-HARQ _ feedback timing values is allocated in the type 1HARQ-ACK codebook.

Example 36 includes the method of example 35, further comprising: allocating one HARQ-ACK opportunity corresponding to a subset of the PDSCH-to-HARQ feedback timing values in the type 1HARQ-ACK codebook based on a time division duplex-UL-DL-configuration common parameter and a time division duplex-UL-DL-configuration dedicated parameter configured by higher layer signaling when at least one row in a Time Domain Resource Allocation (TDRA) table does not overlap with an uplink symbol in at least one time slot determined by any one PDSH-to-HARQ _ feedback timing value in the subset of the PDSCH-to-HARQ _ feedback timing values in a time slot used for the PDSCH transmission.

Example 37 includes the method of example 35, further comprising: generating the type 1HARQ-ACK codebook based on the minimum PDSCH aggregation factor value that can be indicated when PDSCH aggregation factor values can be dynamically indicated by various DCI formats and the minimum PDSCH aggregation factor value that can be indicated is a factor of all other PDSCH aggregation factor values that can be indicated.

Example 38 includes the method of example 37, further comprising: for a PDSCH transmission scheduled with a PDSCH aggregation factor value larger than the minimum indictable PDSCH aggregation factor value and ending in one time slot, allocating the same HARQ-ACK opportunity in the type 1HARQ-ACK codebook as a PDSCH transmission scheduled with the minimum indictable PDSCH aggregation factor value and ending in the same time slot.

Example 39 includes the method of example 35, further comprising: for PDSCH transmissions scheduled by DCI format 1_0 with or without repetition, HARQ-ACK opportunities not used by another PDSCH transmission scheduled by DCI format 1_1 or 1_2 with repetition are allocated in the type 1HARQ-ACK codebook.

Example 40 includes the method of example 39, further comprising: for PDSCH transmissions scheduled by the DCI format 1_0 and ending in one slot with or without repetition, the same HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook as for the PDSCH transmissions with repetition scheduled by the DCI format 1_1 or 1_2 and ending in the same slot.

Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that the embodiments described herein be limited only by the claims and the equivalents thereof.

Claims (25)

1. An apparatus to be used in a User Equipment (UE), comprising:

a Radio Frequency (RF) interface; and

a processor circuit coupled to the RF interface, the processor circuit to:

receiving, via the RF interface, Downlink Control Information (DCI) that schedules a Physical Downlink Shared Channel (PDSCH) transmission having repetitions;

receiving, via the RF interface, the PDSCH transmission based on the DCI; and

transmitting, via the RF interface, HARQ-ACK information for the PDSCH transmission.

2. The apparatus of claim 1, wherein the processor circuit is further to:

skipping decoding of a Transport Block (TB) carried by the PDSCH transmission when the actual number of repetitions of the PDSCH transmission is less than a threshold.

3. The apparatus of claim 2, wherein the processor circuit is further to:

determining the threshold based on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

4. The apparatus of claim 2, wherein the processor circuit is further to:

skipping transmission of HARQ-ACK information for the PDSCH transmission when the PDSCH transmission is an initial PDSCH transmission.

5. The apparatus of claim 1, wherein the processor circuit is further to:

determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor when an actual number of repetitions of the PDSCH transmission is less than a PDSCH aggregation factor value configured for the PDSCH transmission by higher layer signaling.

6. The apparatus of claim 5, wherein the scaling factor is equal to an actual number of repetitions of the PDSCH transmission divided by the PDSCH aggregation factor value, or the scaling factor is selected from a set of scaling factors based on the actual number of repetitions of the PDSCH transmission.

7. The apparatus of claim 1, wherein the processor circuit is further to:

determining a Redundancy Version (RV) cycle of an actual repetition application for transmission to the PDSCH based on the DCI.

8. The apparatus of claim 1, wherein the processor circuit is further to:

receiving a repetition of the PDSCH transmission on an available symbol for the PDSCH transmission in a slot when a number of the available symbols for the repetition is greater than a threshold.

9. The apparatus of claim 1, wherein the processor circuit is further to:

determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor, wherein the scaling factor is configured for the PDSCH transmission by higher layer signaling.

10. The apparatus of claim 9, wherein the scaling factor depends on a Modulation Coding Scheme (MCS) field value in the DCI or a PDSCH aggregation factor value configured by higher layer signaling for the PDSCH transmission.

11. The apparatus of claim 9, wherein the scaling factor is dynamically indicated by a separate field in the DCI or as an additional parameter in a Time Domain Resource Allocation (TDRA) table indexed by a TDRA field in the DCI.

12. The apparatus of claim 1, wherein the processor circuit is further to:

transmitting HARQ-ACK information for the PDSCH transmission with correct decoding of Transport Blocks (TBs) carried by the PDSCH transmission prior to receiving all repetitions of the PDSCH transmission.

13. The apparatus of claim 1, wherein the processor circuit is further to:

generating a type 1HARQ-ACK codebook in view of overlapping of PDSCH transmissions having repetitions across slots used for the PDSCH transmissions, wherein HARQ-ACK information for the PDSCH transmissions is contained in the type 1HARQ-ACK codebook.

14. The apparatus of claim 13, wherein the processor circuit is further to:

for a subset of PDSCH-to-HARQ _ feedback timing values, allocating one or more HARQ-ACK opportunities in the type 1HARQ-ACK codebook corresponding to the subset of PDSCH-to-HARQ _ feedback timing values.

15. The apparatus of claim 13, wherein the processor circuit is further to:

for a subset of PDSCH-to-HARQ _ feedback timing values, at most one HARQ-ACK opportunity corresponding to the subset of PDSCH-to-HARQ _ feedback timing values is allocated in the type 1HARQ-ACK codebook.

16. The apparatus of claim 15, wherein the processor circuit is further to:

allocating one HARQ-ACK opportunity corresponding to a subset of the PDSCH-to-HARQ feedback timing values in the type 1HARQ-ACK codebook based on a Time Division Duplex (TDD) -Uplink (UL) -Downlink (DL) -configuration common parameter and a TDD-UL-DL-configuration dedicated parameter configured by higher layer signaling when at least one row in a Time Domain Resource Allocation (TDRA) table does not overlap with an uplink symbol in at least one slot determined by any one PDSH-to-HARQ feedback timing value in the subset of the PDSCH-to-HARQ feedback timing values in a slot for the PDSCH transmission.

17. The apparatus of claim 15, wherein the processor circuit is further to:

generating the type 1HARQ-ACK codebook based on the minimum PDSCH aggregation factor value that can be indicated when the PDSCH aggregation factor value can be dynamically indicated by various DCI formats and the minimum PDSCH aggregation factor value that can be indicated is a factor of all other PDSCH aggregation factor values that can be indicated.

18. The apparatus of claim 17, wherein the processor circuit is further to:

for a PDSCH transmission scheduled with a PDSCH aggregation factor value larger than the minimum indictable PDSCH aggregation factor value and ending in one time slot, allocating the same HARQ-ACK opportunity in the type 1HARQ-ACK codebook as a PDSCH transmission scheduled with the minimum indictable PDSCH aggregation factor value and ending in the same time slot.

19. The apparatus of claim 15, wherein the processor circuit is further to:

for PDSCH transmissions scheduled by DCI format 1_0 with or without repetition, HARQ-ACK opportunities not used by another PDSCH transmission scheduled by DCI format 1_1 or 1_2 with repetition are allocated in the type 1HARQ-ACK codebook.

20. The apparatus of claim 19, wherein the processor circuit is further to:

for PDSCH transmissions with or without repetition scheduled by the DCI format 1_0 and ending in one slot, the same HARQ-ACK opportunities are allocated in the type 1HARQ-ACK codebook as PDSCH transmissions with repetition scheduled by the DCI format 1_1 or 1_2 and ending in the same slot.

21. A computer-readable storage medium having instructions stored thereon, which when executed by one or more processors, cause the one or more processors to:

receiving, via a Radio Frequency (RF) interface, Downlink Control Information (DCI) that schedules a Physical Downlink Shared Channel (PDSCH) transmission having repetitions;

receiving, via the RF interface, the PDSCH transmission based on the DCI; and

transmitting, via the RF interface, HARQ-ACK information for the PDSCH transmission.

22. The computer-readable storage medium of claim 21, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

skipping decoding of a Transport Block (TB) carried by the PDSCH transmission when the actual number of repetitions of the PDSCH transmission is less than a threshold.

23. The computer-readable storage medium of claim 21, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

determining a Transport Block Size (TBS) to apply to the PDSCH transmission based on a scaling factor, wherein the scaling factor is configured for the PDSCH transmission by higher layer signaling.

24. The computer-readable storage medium of claim 21, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

transmitting HARQ-ACK information for the PDSCH transmission with correct decoding of Transport Blocks (TBs) carried by the PDSCH transmission prior to receiving all repetitions of the PDSCH transmission.

25. The computer-readable storage medium of claim 21, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:

a type 1HARQ-ACK codebook is generated considering PDSCH transmissions with overlap spanning the overlap of slots for the PDSCHs, wherein HARQ-ACK information for the PDSCH transmissions is contained in the type 1HARQ-ACK codebook.

Images