WO2017160351A1 - Enhanced reporting and uplink robustness design - Google Patents

Abstract

The present disclosure provides an ENRR. Generating an ENRR can include processing an allocation of resources provided by an eNodeB, processing a UL data transmission based on the allocation of DL resources provided by an eNodeB, decoding the DL data based on the allocation of DL resources, determining a quantity of repetitions of a data transmission used to decode the DL data, and generating an excess number of repetitions report (ENRR) based on the quantity of repetitions of the data transmission used to decode the DL data.

Description

ENHANCED REPORTING AND UPLINK ROBUSTNESS DESIGN Related Applications

[0001] This application claims the benefit of United States non-provisional patent Application No. 62/336,394, filed May 13,2016, and United States non-provisional patent Application No. 62/308,512, filed March 15, 2016, both of which are incorporated by reference herein in their entirety.

Technical Field

[0002] The present disclosure relates to an excess number of repetitions report (ENRR), an uplink compensation gap (UCG), and an early termination indication (ETI). In particular, the present disclosure relates to generating and processing the ENRR, the UCG, and the ETI.

Brief Description of the Drawings

[0003] FIG. 1 is a timing diagram for an ENRR according to one embodiment.

[0004] FIG. 2 is a timing diagram for a UCG and an ETI according to one embodiment.

[0005] FIG. 3 is a block diagram illustrating electronic device circuitry that may be eNodeB circuitry, user equipment (UE) circuitry, network node circuitry, or some other type of circuitry according to one embodiment.

[0006] FIG. 4 is a block diagram illustrating a method for configuring a quantity of repetitions of a DL transmission based on an ENRR according to one embodiment.

[0007] FIG. 5 is a block diagram illustrating a method for generating an ENRR according to one embodiment.

[0008] FIG. 6 is a block diagram illustrating a method for implementing a UCG according to one embodiment.

[0009] FIG. 7 is a block diagram illustrating a method for an ETI according to one embodiment. [0010] FIG. 8 is a block diagram illustrating components of a device according to one embodiment.

[0011] FIG. 9 is a block diagram illustrating components according to some embodiments.

Detailed Description of Preferred Embodiments

[0012] Wireless mobile communication technology uses various standards and protocols to generate and/or transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, a 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.1 1 standard, which is commonly known to industry groups as Wireless Local Area Network (WLAN) or Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, a base station may include Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controllers (RNCs) in the E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In LTE networks, the E-UTRAN may include a plurality of eNodeBs and may communicate with the plurality of UEs. LTE networks include a radio access technology (RAT) and core radio network architecture that can provide high data rate, low latency, packet optimization, and improved system capacity and coverage.

[0013] Enhanced machine type communications (eMTC) UEs and narrow band (NB) internet of things (loT) UEs can use reporting mechanisms to improve

UE/evolved node B (eNodeB) communications. For example, an ENRR, a UCG, and an ETI can be used by a UE and/or an eNodeB to improve UE/evolved node B (eNodeB) communications. As used herein, the term "UE" is used to represent both NB UEs and non-NB UEs. In some examples, the UE can be used for eMTC.

[0014] Implementing the ENRR can enhance the allocation of downlink (DL) resources. Implementing a UCG can enhance the robustness of an uplink (UL) by enabling the UE to compensate for a frequency and timing reference. Implementing an ETI can optimize the allocation of uplink resources by an eNodeB. The ETI can be implemented during the UCG for half-duplex frequency division duplex (HD-FDD) or as an uplink grant for full-duplex frequency division duplex (FDD). [0015] When managing UEs in coverage enhancement (CE) mode, a mobile network can allocate UL and DL resources. Allocating UL and DL resources can be a tradeoff between high latency/low data rate and repetition levels. During CE modes of operation, the UE may utilize repetitions to overcome the path loss to the eNodeB. For example, eMTC UEs may utilize repetition levels (RL) ranging from 1 to 2,048 repetitions, NB-loT UEs may utilize RLs ranging from 1 to 2,048 repetitions, and eNodeBs may also utilize RLs ranging from 1 to 2,048 repetitions. Extended UL operation can lead to frequency errors and can be exacerbated by variations in temperature. Variations in temperature can be due to temperature changes in the environment around the UE as well as a consequence of the power amplifier heating over the period of continuous transmission. As used herein, a repetition level can define a repetition of a data transmission. For example, a repetition level of 2,048 can describe 2,048 repetitions of a data transmission to a UE and/or to an eNodeB.

[0016] Reference is now made to the figures, in which like reference numerals refer to like elements. For clarity, the first digit of a reference numeral indicates the figure number in which the corresponding element is first used. In the following description, numerous specific details are provided for a thorough understanding of the embodiments disclosed herein. However, those skilled in the art will recognize that the embodiments described herein can be practiced without one or more of the specific details, or with other methods, components, or materials. Further, in some cases, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0017] FIG. 1 is a timing diagram 100 for an ENRR according to one embodiment. The timing diagram 100 includes an eNodeB 102 and a UE 104. The timing diagram also includes DL resource allocations 106-1 and 106-2, DL transmissions 1 10-1 and 1 10-2, DL repetitions (DL eNodeB repetitions) 108-1 and 108-2, DL repetitions (DL UE repetitions) 1 12, a UE transmission start 1 14, an ENRR transmission 1 16, and an optimal termination 1 18.

[0018] The DL transmissions 1 10-1 and 1 10-2 can include DL control data and DL shared data. For example, the DL transmissions 1 10-1 and 1 10-2 can be a DL control channel or a DL shared channel, among other types of DL transmissions. [0019] As used herein the ENRR can be defined in one or more of the following manners. For example, the ENRR can be calculated as the difference between the number of repetitions 1 12 used by the UE 104 to successfully receive a DL transmission 1 10-1 and the number of repetitions 108-1 used by the eNodeB 102 to transmit the DL transmission 1 10-1 as indicated by the downlink control information (DCI) or the radio resource control (RRC) configuration. In some example, the DL transmission can include a DL shared channel.

[0020] In some examples, the ENRR can also include, in addition or as an alternative of the previous example, an indication of whether the UE 104 was able to decode the DL transmission 1 10-1 (e.g., DL control channel) successfully with a lower quantity of repetitions 1 12 than the number of repetitions 108-1 used by the eNodeB 102 to transmit the DL transmission 1 10-1 . The DL transmission 1 10-1 can also include a machine physical downlink control channel (e.g., M-PDCCH) for eMTC UEs and/or narrowband physical downlink control channel (NB-PDCCH) for NB-loT UEs. The ENRR can also be defined as the difference between the quantity of repetitions 1 12 used by the UE 104 to successfully decode the DL transmission 1 10-1 and the maximum quantity of repetitions that the eNodeB 102 is configured to transmit the DL transmission 1 10-1 to the UE 104. As used herein, the quantity of repetitions 108-1 used by the eNodeB 102 to transmit the DL transmission 1 10-1 can be different from the maximum quantity of repetitions that the eNodeB 102 is configured to transmit the DL transmission 1 10-1 to the UE 104. The quantity of repetitions 108-1 can change on a given DL transmission while the maximum quantity of repetitions can be static for a given period of time and does not change for the given period of time. The quantity of repetitions 108-1 can be configured to be no greater than the maximum quantity of repetitions.

[0021] In some examples, a UE 104 can report a positive ENRR if the quantity of early decodings of the DL transmissions (e.g., including the DL transmission 1 10-1 ) is equal to or greater than a parameter (e.g., threshold) configured by radio resource control (RRC) signaling or a predefined number of instances of successful early decoding of the DL transmissions. As used herein, an early decoding of the DL transmission 1 10-1 can describe the quantity of transmissions 1 12 that is less than the quantity of transmissions 108-1 . If the predefined number of instances of successful early decoding of the DL transmission 1 10-1 is equal to two, then the early decoding of the DL transmissions (e.g., including the DL transmission 1 10-1 ) can occur two or more times before the UE 104 reports a positive ENRR. The predefined number of instances of successful early decoding of the DL transmissions can be specified or configured in a manner that is specific to the UE's coverage enhancement level, as a common setting for the radio link, and/or as a standardized setting for eMTCs and/or NB-loT UEs.

[0022] The UE 104 can report a negative ENRR if the quantity of early decodings of the DL transmissions (e.g., including the DL transmission 1 10-1 ) is less than a parameter configured by radio resource control (RRC) signaling or a predefined number of instances of successful early decoding of the DL transmissions. If the predefined number of instances of successful early decoding of the DL transmission 1 10-1 is equal to four, then the early decoding of the DL transmissions (e.g., including the DL transmission 1 10-1 ) can occur three or fewer times before the UE 104 reports a negative ENRR.

[0023] The predefined number of instances of successful early decoding can be a percentage below the maximum number of repetitions that the eNodeB 102 is configured to transmit the DL transmission 1 10-1 to the UE 104. For example, the UE 104 can report the ENRR when the repetitions 1 12 are a predefined percentage below the maximum number of repetitions. The UE 104 can also report the ENRR when the repetitions 1 12 are a predefined percentage above the maximum number of repetitions.

[0024] The predefined number of instances of successful early decoding can also be an quantity of successful early decodings or the repetitions 108-1. For example, the UE 104 can report the ENRR when the repetitions 1 12 are an absolute quantity of successful early decodings (e.g., a predefined number of instances) below the transmissions 108-1 . The UE 104 can report the ENRR when the repetitions 1 12 are an absolute quantity of successful early decodings (e.g., a predefined number of instances) above the repetitions 108-1 .

[0025] The predefined number of instances of successful early decodings can refer to the DL transmission 1 10-1 such as a (NB)PDCCH and/or a physical downlink shared channel or a NB physical downlink shared channel (NB)PDSCH, among other types of DL transmission 1 10-1. The threshold can be defined as an absolute number of successful early decoding that is defined independently of the repetitions 108-1 . The predefined number of instances of successful early decodings can be defined based on the CE level or configure range of the repetitions 108-1 . [0026] The predefined number of instances of successful early decodings can be provided from an eNodeB 102 to a UE 104 or from the UE 104 to the eNodeB 102 through an existing and/or new system information block (SIB(s)). The predefined number of instances of successful early decodings can be provided from an eNodeB 102 to a UE 104 or from the UE 104 to the eNodeB 102 through a dedicated RRC connection reconfiguration, an msg.4 such as an RRC connection setup, or a DCI.

[0027] The eNodeB 102 can utilize the ENRR to configure the repetitions 108-2 and/or subsequent repetitions of the DL transmission. For example, the eNodeB 102 can utilize the ENRR to trigger a configuration of the repetitions 108-2 to be greater or lower than the repetitions 108-1 . In some examples, a different kind of indication can be configured. This may be a complementary report to ENRR based on the UE's estimation of the number of additional repetitions it may need to decode the information correctly, termed the short number of repetitions report (SNRR).

[0028] The ENRR can indicate the repetitions 1 12. The ENRR can include one or more bits to indicate the quantity of repetitions 1 12. For example, the ENRR can include two or more bits to report three or more repetitions in excess of the

repetitions 108-1 .

[0029] If the UE 104 is configured with the set of repetitions {4, 8, 16, 32, 64, 128, 256, 512}, the (NB)PDSCH is transmitted using 128 repetitions (e.g. , repetitions 108- 1 ), and the quantity of repetitions 1 12 is between 32 and 64 (e.g. , 32 < repetitions 1 12 < 64), then, for the 2-bit example, the UE can indicate the bits 01 as the ENRR to indicate that the repetitions 1 12 are between 32 and 64 repetitions. That is, the bits 01 can identify an index of the repetition set {4, 8, 16, 32, 64, 128, 256, 512} below the currently selected index. The currently selected index can be 5 if the repetitions 108-1 are configured to 128 repetitions. The ENRR including bits 01 identify a base ten index of 1 below the index 5 for which the repetitions 108-1 are configured to identify an index 4 from the repetition set. The index 4 of the repetition set can identify 64 repetitions and identify that the quantity of repetitions 1 12 is between 32 and 64.

[0030] In the two ENRR examples, the ENRR can include bits 00, 01 , 10, and 1 1 . The bits 00 can correspond to T_₁ < X ≤ T₀, the bits 01 can correspond to T_₂ < X ≤ 7 , the bits 10 can correspond to T_₃ < X ≤ T_₂ , and the bits 1 1 can

correspond to X ≤ T_₃. X can represent the UE repetitions 1 12. T₀ corresponds to the configured quantity of repetitions 108-1 (e.g. , 128). T_₁ corresponds to the quantity of repetitions 64 from the repetition set. T_ can identify an index (e.g. , 4) below the index associated with the configure quantity of repetitions 108-1 (e.g. , 5). T_2 corresponds to the quantity of repetitions 32 and two indexes (e.g. , 3) below the index associated with the configure quantity of repetitions 108-1 . T_₃ corresponds to the quantity of repetitions 16 and three indexes (e.g. , 2) below the index associated with the configure quantity of repetitions 108-1 .

[0031] In some examples, the ENRR can include a single bit to report whether the repetitions 1 12 are significantly less than the repetitions 108-1 . As used herein, significantly less can describe a predefined threshold below the repetitions 108-1 . The significantly less threshold can be configured by a common RRC. The significantly less threshold can be a quantity of repetitions that the repetitions 1 12 are below the repetitions 108-1 or r₀/(2^w) repetitions that the repetitions 1 12 are below the repetitions 108-1 where W is a positive integer.

[0032] The ENRR can also include feedback similar to the 2-bit example above for a number, N, of already received DL shared channel receptions or DL control channel receptions. For the case of DL control channel receptions, N can

correspond to the instances of successful detection of a valid DCI.

[0033] The ENRR can also include a quantity of bits needed to encode the repetitions 1 12. The ENRR can also include a quantity of bits used to indicate the repetitions 1 12. For example, if the repetitions 108-1 are configured with repetition levels (x-i , x₂, ... , x_m) for the DL transmission 1 10-1 , then the ENRR can report x_n or lower repetitions 1 12.

[0034] In some examples, the ENRR can include a single bit to represent a positive ENRR and a negative ENRR. For example, a first bit value (e.g. , 1 bit) can represent a positive ENRR and a second bit value (e.g. , 2 bits) can represent a negative ENRR.

[0035] The ENRR can be provided by the UE 104 utilizing a Layer 1 feedback. A Layer 1 feedback can include, for example, an uplink control information (UCI). The ENRR can be transmitted by the UE 104 via a DL hybrid automatic repeat request acknowledgement (DL HARQ-ACK) feedback, at least, when the ENRR corresponds to the early decoding of the DL shared channel. [0036] The ENRR transmission can be triggered (e.g., requested) by the eNodeB using a field in the DL DCI scheduling the PDSCH or the NB-PDSCH. For NB-loT, if no CSI reporting is supported and/or configured, the CSI request field can be reinterpreted to indicate the request of an ENRR transmission on a scheduled (NB)PUSCH resource.

[0037] The scheduling of the (NB)PUSCH resource can be the same resource as that used for the transmission of the DL HARQ-ACK feedback if the ENRR is sent along with the HARQ-ACK feedback. The (NB)PUSCH resources can be indicated using a combination of higher-layer configured resources. The (NB)PUSCH resources can be offset in either time domain and/or frequency domain as indicated by a DL DCI. The offset of the (NB)PUSCH in the frequency domain can be at least in part implicitly determined based on a starting subframe of the (NB)PDCCH and/or the (NB)PDSCH. The ENRR can also be transmitted along with the UL shared channel (SCH) transmission on (NB)PUSCH in a manner similar to the power headroom report (PHR) transmission.

[0038] The ENRR can also be transmitted using a MAC control element (MAC CE) and/or as an RRC message in response to a trigger received from the eNodeB 102. The trigger can be indicated via a MAC CE or UE-specific RRC message. The ENRR can be generated and/or transmitted as a new MAC CE. The ENRR MAC CE can be identified by a MAC protocol data unit (PDU) subheader with logical channel ID (LCID). For example, a common control channel (CCCH) can be included at index 00000, an identity of the logical channel can be included at indices 00001 - 01010, the CCCH can be included at index 0101 1 , an ENRR can be included at index 01 100, a plurality of reserved LCID values can be included at indices 1 101 - 10101 , a truncated sidelink buffer status report (BSR) can be included at index 101 1 1 , a dual connectivity PHR can be included at index 1 100, an extended PHR can be included at index 1 101 , a PHR can be included at index 1 1010, the cell radio network temporary identifier (C-RNTI) can be included at index 1 101 1 , the truncated BSR can be included at 1 1 100, the short BSR can be included at 1 1 101 , the long BSR can be included at 1 1 1 10, and an index 1 1 1 1 1 can include padding.

[0039] In some examples, the ENRR can be generated and/or transmitted with the PHR MAC CE using one or two of the reserved bits available. If the ENRR is included in the PHR MAC CE, then the ENRR can indicate the repetitions used in the DL transmission 1 10-1 (e.g., including control and/or data) even though the PHR includes information related to the UL transmissions.

[0040] The PHR MAC control element is identified by a MAC PDU subheader with LCID as specified above. The PHR MAC control element can have a fixed size and can consist of a single octet. If a reserved bit is set to 0, then one of the two bits can be used for ENRR indication (represented at V). If a single V bit is used for ENRR, then a 1 bit value can indicate a positive ENRR and a 0 bit value can indicate a neutral ENRR and/or a negative ENRR. A neutral ENRR can indicate that the repetitions 1 12 are equal to the repetitions 108-1 and/or within a predefined threshold from the repetitions 108-1. If two V bits are used for ENRR, then 00 bit values can indicate a baseline where there is a neutral ENRR value and/or a negative ENRR and the other bit values can describe a positive ENRR and how much lower the repetitions 1 12 are than the repetitions 108 as previously described.

[0041] The power headroom (PH) field indicates the power headroom level. The length of the field is 6 bits. The ENRR can be provided via the PH field. The reported PH and the corresponding power headroom levels can include the ENRR in the one or two most significant bits.

[0042] The eNodeB 102 generates and provides a DL resource allocation transmission to the UE 104. The DL resource allocation transmission can allocate resources for the number of tones, subcarrier (SC) spacing, modulation and coding schemes (MCS), and/or RL, among other DL resource allocations. The UE 104 can receive, decode, and/or process the DL resource allocation 106-1 . The eNodeB 102 generates and/or provides the DL transmission 1 10-1 . The DL transmission 1 10-1 can include data, control information, and/or an UL resource allocation. The UL resource can include number tones, SC spacing, MCS, RL, and an ENRR request. The ENRR request can request an ENRR from the UE 104. The eNodeB 102 can be configured to generate and/or transmit the DL transmission 1 10-1 using a plurality of repetitions 108-1 . For example, if the quantity of repetitions 108-1 is set to 16, then the DL transmission 1 10-1 can be transmitted 16 times consecutively or intermittently with another transmission.

[0043] The UE 104 can determine the repetitions 1 12 used to decode and/or successfully process the DL transmission 1 10-1 . In FIG. 1 , the repetitions 1 12 can be less than the repetitions 108-1 . [0044] After receiving the repetitions 108-1 of the DL transmission 1 10-1 , the UE 104 can start 1 14 the UL transmission 1 16. The UL transmission 1 16 can include data and/or the ENRR. The eNodeB 102 can generate and/or provide the DL resource allocation 106-2. The eNodeB 102 can also generate and/or provide the DL transmission 1 10-2. The DL transmission 1 10-2 may or may not include the ENRR. The eNodeB 102 can generate and/or provide the DL transmission 1 10-2 with a quantity of repetitions 108-2. The quantity of repetitions 108-2 can be configured based on the ENRR. That is, the quantity of repetitions 108-2 can be configured, for example, to concede with the repetitions 1 12 described in the ENRR. The repetitions 108-2 can be configured to provide an optimal termination 1 18 of the DL transmission 1 10-2. The optimal termination 1 18 of the DL transmission 1 10-2 can describe a termination of the DL transmission 1 10-2 that transmitted with repetitions 108-2 where the repetitions 108-2 are closely aligned with the repetitions 1 12. For example, the optimal termination 1 18 can include the repetitions 108-2 that are equal to the repetitions used by the UE 104 to decode, receive, and/or process the DL transmission 1 10-2.

[0045] FIG. 2 is a timing diagram 200 for a UCG and an ETI according to one embodiment. The timing diagram 200 includes the eNodeB 202 and the UE 204 that are analogous to eNodeB 102 and UE 104 in FIG. 1 . The timing diagram 200 also includes a DL resource allocation 206, a DL transmission 208, UL transmissions 216-1 and 216-2, and uplink compensation gaps (UCGs) 224-1 and 224-2.

[0046] The UE 204 may be configured by a higher layer with a UCG based on the UE's 204 coverage level or the UE's 204 coverage class. In some examples, the UE 204 with a highest L level of repetitions in its configured set of repetition levels can be configured with a UCG, where L is specified or configured in a cell-specific manner. That is, the UE 204 from the UEs that the eNodeB 202 services with a greatest quantity of repetitions 206 can automatically be configured with a UCG.

[0047] The UE 204 can be configured with a UCG when the UE's 204 coverage level or the quantity of repetitions is above a threshold. For example, the UE 204 can be configured with the UCG if the UE 204 is configured with the quantity of repetitions 206 that is at least greater than the quantity of repetitions with which a different UE is configured.

[0048] The UE's 204 coverage enhancement level can be determined based on the repetition level (e.g., quantity of repetitions) selected for or used for the most recent transmission of the physical random access channel (PRACH) or NB-PRACH for NB-loT UEs. The UCG can be applied for a UE 204 if the (NB)PRACH repetition level is higher than a specified or configured threshold. The mapping from the (NB)PRACH repetition level can be applied to (NB)PRACH transmissions as well as for (NB)PUSCH transmissions including message 3 transmissions until an RRC connection is established or at least until a message 4 is received. The UCG can be applied for a UE based on the UE's (NB)PRACH repetition level, which can be used for subsequent (NB)PUSCH transmissions.

[0049] For (NB)PUSCH transmissions, the applicability of the UCG can be based on the quantity of repetitions indicated in the UL grant carried by the UL DCI or in the random access response (RAR) in cases of a message 3. For (NB)PRACH transmission initiated by an (NB)PDCCH order, the applicability of the UCG can be based on the number of repetitions of the (NB)PRACH or the starting (NB)PRACH repetition level as indicated in the DL DCI carrying the (NB)PDCCH order.

[0050] For NB-loT, not all subframes may be available or configured for NB-loT DL transmissions. Such DL subframes that are invalid DL subframes, as well as those carrying narrowband primary and secondary synchronization signals

(NPSS/NSSS), may not carry a narrowband reference signal (N-RS). Thus, the subframes may not be useful for a half-duplex frequency division duplex (HD-FDD) UE for tracking of the frequency estimate or for cross-subframe averaging/filtering to improve the accuracy of the estimates. The UCG length for the UCG can be defined in terms of the number of DL valid subframes for which the UE receives, processes, and/or decodes the N-RS.

[0051] The number of DL valid subframes for which the UE can assume the presence of the N-RS can be a function of the DL signal to noise ratio (SINR) that can, for instance, be based on the DL reference signal received power (RSRP) or its variants. The number of valid subframes can also be defined as a function of the coverage level of the UE that could be presented by one or a combination of the number of maximum repetitions for the configured UE-specific search space for NB- PDCCH, the number of repetitions for the NB-PUSCH transmission, the NB-PRACH repetition level, and/or the CE mode as configured for the UE 204 by the eNodeB 202 or implicitly determined by the UE 204.

[0052] A length 222 of the UCG can be function of the DL SINR. The DL SINR can be based on the DL RSRP. In some examples, the length 222 of the UCG can be defined as a function of the coverage level of the UE 204 that can be represented by one or more of a combination of the number of maximum repetitions for the configured UE 204 specific search space for an NBPDCCH, the number of repetitions for the narrowband physical uplink shared channel (NB-PUSCH) transmission, the (NB)PRACH repetition level, and/or the CE mode as configured for the UE 204 by the eNodeB 202 or implicitly determined by the UE 204.

[0053] For the eNodeB 202 to transmit an early transmission indication (ETI) during the UCG 224-2, the UE 204 can monitor the DL control channel at least during certain parts of the UCG 224-2. A certain part of the UCG 224-2 can describe a specific subframe, in the DL available subframes, and/or with certain periodicity within the UCG 224-2. The UE 204 monitoring of the DL control channel can be configured based on a boolean flag. For example, a 1 bit can instruct the UE 204 to monitor the DL control channel and a 0 bit can instruct the UE 204 not to monitor the DL control channel. The boolean flag can be transmitted using a cell-common RRC (SIB) message and/or via a dedicated RRC message (e.g., during RRC connection setup).

[0054] Associated with the boolean flag to enable/disable monitoring by the UE 204, the UE 204 can be configured to monitor UE-specific search space (USS) within the UCG (e.g., UCGs 224-1 and 224-2) for DL control channel indicating an ETI. The ETI can be indicated via the DCI (e.g., an already existing DCI). The DCI can identify a newly defined UL grant for a newly defined transport block that carries the original UL grant. The original UL gran can have one or more field changes to indicate that the already existing DCI is an ETI for the particular UL process. The ETI can also be indicated via a new DCI format with a compact size that the UE monitors during the UCG (e.g., UCGs 224-1 and 224-2).

[0055] If multiple HARQ processes are supported for the UL transmission, the UCGs 224-1 and 224-2 for each HARQ process can be uniquely identifiable for each HARQ process via the starting subframe of the UCGs 224-2 and 224-2 relative to the starting subframe of the UL transmission for a particular HARQ process. Further, the unique identifier can be used to implicitly identify the HARQ process to which the ETI corresponds.

[0056] Multiple HARQ processes can be provided via a single UCG. The DCI indicating the ETI can provide the identification for the HARQ process to which the ETI corresponds. Further, the ETIs corresponding to multiple HARQ processes can be carried in a same DCI.

[0057] The UCGs 224-1 and 224-2 can be configured such that each UCG length includes the transmission of the PSS and/or SSS and/or the physical broadcast channel (e.g., PBCH or NB-PBCH for eMTC or NB-loT UEs, respectively) to enable tracking and correction of a frequency drift that the UE 204 may have experienced. The USGs 224-1 and 224-2 can also be configured with a specific USG period. The USG period can define the interval between subsequent USGs (e.g., interval between the UCG 224-1 and the UCG 224-2).

[0058] The pattern of the UCGs 224-1 and 224-2 can be based on existing measurement gaps (e.g., spanning a duration of 6 milliseconds (ms)). That is, the pattern of the UCGs 224-1 and 224-2 can be based on the UCG length and the UCG period. The frequency of such gaps may be specified or configured in a cell-specific manner. In some examples, a single UCG may be configured approximately at the middle of the entire UL burst of transmissions including a number of repetitions of the rate-matched block. A rate-matched block corresponds to the set of subframes that are used to map a single (NB)PDSCH transport block.

[0059] The exact time-offset with respect to the starting subframe of the UL burst can be configured in a UE-specific manner via higher layers and possibly with a further offset to the higher layer-indicated time-offset that is carried by the UL grant. Further, the UCG may only appear in between complete sets of repetitions of the rate-matched blocks.

[0060] The eNodeB 202 can generate and provide the DL resource allocations 206 to the UE 204. The DL resource allocations 206 can include the number tones, the SC spacing, the MCR, and/or the RL, among other resource allocations.

[0061] The eNodeB 202 can also generate and/or provide the DL transmission 208 using a plurality of repetitions 206. The DL transmission 208 can include a data transmission and/or UL resource allocation. The UL resource allocation can include the number tones, the SC spacing, the MCS, and the RL. The UL resource allocation can also include the ENRR. The UE 204 can process and/or decode the DL transmission 208 and start 214 (e.g., initiate) transmission of the UL transmission 216-1 (e.g., UL data transmission).

[0062] The UL data transmission including the UL transmissions 216-1 and 216-2 can begin at 214 and end at 228. The eNodeB 202 can begin 220 reception of the UL transmission 216-1 . The eNodeB 202 can generate, encode, and/or transmit the UCG 224-1 with a UCG length 222. The UCG length 222 can provide the (NB)RS for compensation measurements. The UL transmission including the UL

transmissions 216-1 and 216-2 can include a number of repetitions of the UL transmission. The length of the UL transmission can result in frequency drift by the UE 204. The UCG provides the UE 204 to recalibrate itself using the (NB)RS to compensate for the frequency drift.

[0063] The UE 204 can measure 226-1 the frequency using the (NB)RS and compensates its frequency and timing reference. The UE 204 can continue 227 the UL transmission 216-2. The eNodeB 202 can terminate 230 the demodulation early. That is, when receiving uplink transmissions with a certain RL, the eNodeB 202 can demodulate the uplink data using a fewer number of repetitions than the configured RL for the UL transmissions 216-1 and/or 216-2. As used here, the demodulation can include the successful reception of the UL transmission provided via the UL transmissions 216-1 and 216-2. The eNodeB 202 can allocate resources for the transmission of the UCG 224-2. During the UCGs 224-1 and 224-2, the (NB)RS transmitted by the eNodeB is available for the UE to perform frequency and timing compensation measurements. The eNodeB can further generate, encode, and transmit the ETI. If transmitted, the ETI can instruct the UE 204 to terminate the UL transmission. The UE 204 can measure the DL frequency and compensate the frequency and timing reference. The UE 204 can also decode 228, process, and/or receive the ETI. The UE 204 can terminate the UL transmission in response to receiving the ETI.

[0064] FIG. 3 is a block diagram illustrating electronic device circuitry that may be eNodeB circuitry, user equipment (UE) circuitry, network node circuitry, or some other type of circuitry according to one embodiment. FIG. 3 illustrates an electronic device 300 that may be, or may be incorporated into or otherwise part of, an eNodeB, a UE, or some other type of electronic device in accordance with various embodiments. Specifically, the electronic device 300 may be logic and/or circuitry that may be at least partially implemented in one or more of hardware, software, and/or firmware. In embodiments, the electronic device logic may include radio transmit/transmitter logic (e.g., a first transmitter logic 377) and receive/receiver logic (e.g., a first receiver logic 383) coupled to a control logic 373 and/or a processor 371 . In embodiments, the transmit/transmitter and/or receive/receiver logic may be elements or modules of transceiver logic. The first transmitter logic 377 and the first receiver logic 383 may be housed in separate devices. For example, the first transmitter logic 377 can be incorporated into a first device while the first receiver logic 383 is incorporated into a second device, or the transmitter logic 377 and the receiver logic 383 can be incorporated into a device separate from a device including any combination of the control logic 373, a memory 379, and/or the processor 371 . The electronic device 300 may be coupled with or include one or more antenna elements 385 of one or more antennas. The electronic device 300 and/or the components of the electronic device 300 may be configured to perform operations similar to those described elsewhere in this disclosure.

[0065] In embodiments where the electronic device 300 implements, is

incorporated into, or is otherwise part of a UE and/or an eNodeB, or device portion thereof, the electronic device 300 can detect a blockage for AP services. The processor 371 may be coupled to the first receiver and the first transmitter. The memory 379 may be coupled to the processor 371 having control logic instructions thereon that, when executed, generate, encode, receive, and/or decode ENRRs, UCGs, and ETIs.

[0066] In embodiments where the electronic device 300 receives data, generates data, and/or transmits data to/from a UE to implement a downlink signal including the extended synchronization signal (ESS), the processor 371 may be coupled to a receiver and a transmitter. The memory 379 may be coupled to the processor 371 having control logic 373 instructions thereon that, when executed, may be able to generate the ESS using a root index generated from a physical cell ID.

[0067] As used herein, the term "logic" may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, the processor 371 (shared, dedicated, or group), and/or the memory 379 (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide

the described functionality. Specifically, the logic may be at least partially

implemented in, or an element of, hardware, software, and/or firmware. In some embodiments, the electronic device logic may be implemented in, or functions associated with the logic may be implemented by, one or more software or firmware modules. [0068] FIG. 4 is a block diagram illustrating a method 440 for configuring a quantity of repetitions of a DL transmission based on an ENRR according to one embodiment. The method 440 can include allocating 442 DL resources for a first DL data to be transmitted with a first quantity of repetitions, generating 444 the first DL data to be transmitted with the first quantity of repetitions, processing 446 the ENRR received from a UE, and configuring 448 a second quantity of repetitions of a second DL data based on the ENRR.

[0069] The method 440 can further include allocating DL resources for the second DL transmission with the second quantity of repetitions and generating the second DL transmission with the second quantity of repetitions. The first quantity of repetitions of the first DL transmission can be less than the second quantity of repetitions of the second DL transmission. The first quantity of repetitions of the first DL transmission can be greater than the second quantity of repetitions of the second DL transmission.

[0070] The ENRR can describe a third quantity of repetitions used by the UE to successfully receive the first data transmission. The ENRR can be a difference between the first quantity of repetitions and the third quantity of repetitions. The ENRR can be a difference between a maximum number of repetitions associated with the UE and the third quantity of repetitions. The ENRR can be positive based on a determination that the third quantity of repetitions is less than a first threshold, and the ENRR can be negative based on a determination that the third quantity of repetitions is greater than a second threshold.

[0071] FIG. 5 is a block diagram illustrating a method 550 for generating an ENRR according to one embodiment. The method 550 includes processing 552 an allocation of DL resources provided by an eNodeB, decoding 554 a DL data based on the allocation of DL resources, determining 556 a quantity of repetitions of the data transmission used to decode the DL data, and generating 558 an ENRR based on the quantity of repetitions of the data transmission used to decode the DL data.

[0072] The method 550 can further include generating the ENRR as layer 1 feedback. The layer 1 feedback is part of the UCI, wherein the instructions to generate the ENRR comprise further instructions to generate the ENRR as part of a DL HARQ-ACK. The ENRR can be generated as part of a MAC element. The method 550 can further include generating the ENRR as part of a newly defined MAC element. The method 550 can further include generating the ENRR as part of the MAC control element. The method 550 can also include generating the ENRR as part of a previously defined MAC element.

[0073] FIG. 6 is a block diagram illustrating a method 660 for implementing a UCG according to one embodiment. The method 660 includes allocating 662 UL resources for UL data, wherein the allocation includes a UCG, processing 664 UL data from a UE, implementing 668 a first UCG by making the RS available to the UE for compensation measurements, processing 670 additional UL data from the UE, and implementing 672 a second UCG by making the RS available to the UE and generating the ETI to terminate the UL data.

[0074] The method 660 can further include including the UCG in the allocation of UL resources based on a determination that a quantity of repetitions of a DL transmission is greater than a threshold. The method 660 can further include including the UCG in the allocation of UL resources based on a coverage level of the UE.

[0075] The coverage level of the UE can be based on a quantity of repetitions of at least one of a physical random access channel (PRACH) and a

narrowband PRACH (NB-PRACH). The coverage level of the UE can be based on a quantity of repetitions of a DL transmission provided by at least one of a UL DCI and a RAR. The coverage level of the UE can be based on a quantity of repetitions of a DL transmission provided by a DL DCI and a RAR.

[0076] FIG. 7 is a block diagram illustrating a method 780 for an ETI according to one embodiment. The method 780 can include processing 782 an allocation of UL resources, generating 784 UL data based on the allocation of UL resources, processing 786 an RS from an eNodeB received during a UCG, configuring 788 a UE based on the RS during the UCG scheduled in the allocation of UL resources, processing 792 an ETI from the eNodeB received in the UCG, and terminating 794 a UL transmission based on the ETI.

[0077] The method 780 can further include processing the RS during a first UCG, configuring the UE during a first USG, and processing the ETI in a second UCG. The length of the UCG is based on a quantity of DL subframes labeled as valid. The quantity of DL subframes is labeled as valid based on an expectation of successful reception of the DL subframes by the UE. The length of the UCG is based on a DL SINR. The DL SINR can be based on a DL reference signal received power

(RSRP). [0078] The length of the UCG can be based on a coverage level of the UE. The coverage level of the UE is based on at least one of a first quantity of maximum repetitions of a DL transmission, a second quantity of repetitions of an NPUSCH transmission, a third quantity of repetitions of a PRACH, a fourth quantity of repetitions of an NPRACH, and a CE mode of the UE.

[0079] FIG. 8 is a block diagram illustrating components of a device according to one embodiment. In some embodiments, the device may include application circuitry 803, baseband circuitry 805, radio frequency (RF) circuitry 807, front-end module (FEM) circuitry 809, and one or more antennas 814, coupled together at least as shown in FIG. 8. Any combination or subset of these components can be included, for example, in a UE device or an eNodeB device.

[0080] The application circuitry 803 may include one or more application processors. By way of non-limiting example, the application circuitry 803 may include one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processor(s) may be operably coupled and/or include memory/storage, and may be configured to execute instructions stored in the memory/storage to enable various applications

and/or operating systems to run on the system.

[0081] By way of non-limiting example, the baseband circuitry 805 may include one or more single-core or multi-core processors. The baseband circuitry 805 may include one or more baseband processors and/or control logic. The baseband circuitry 805 may be configured to process baseband signals received from a receive signal path of the RF circuitry 807. The baseband circuitry 805 may also be configured to generate baseband signals for a transmit signal path of the RF circuitry 807. The baseband circuitry 805 may interface with the application circuitry 803 for generation and processing of the baseband signals, and for controlling operations of the RF circuitry 807.

[0082] By way of non-limiting example, the baseband circuitry 805 may include at least one of a second generation (2G) baseband processor 81 1 A, a third generation (3G) baseband processor 81 1 B, a fourth generation (4G) baseband processor 81 1 C, and other baseband processor(s) 81 1 D for other existing generations and

generations in development or to be developed in the future (e.g., fifth generation (5G), sixth generation (6G), etc.). The baseband circuitry 805 (e.g., at least one of the baseband processors 81 1 A-81 1 D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 807. By way of non-limiting example, the radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency shifting, other functions, and combinations thereof. In some embodiments,

modulation/demodulation circuitry of the baseband circuitry 805 may be programmed to perform Fast-Fourier Transform (FFT), precoding, and constellation

mapping/demapping functions, other functions, and combinations thereof. In some embodiments, encoding/decoding circuitry of the baseband circuitry 805 may be programmed to perform convolutions, tail-biting convolutions, turbo, Viterbi, and Low Density Parity Check (LDPC) encoder/decoder functions, other functions, and combinations thereof. Embodiments of modulation/demodulation and

encoder/decoder functions are not limited to these examples, and may include other suitable functions.

[0083] In some embodiments, the baseband circuitry 805 may include elements of a protocol stack. By way of non-limiting example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol include, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 81 1 E of the baseband circuitry 805 may be

programmed to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry 805 may include one or more audio digital signal processor(s) (DSP) 81 1 F. The audio DSP(s) 81 1 F may include elements for compression/decompression and echo cancellation. The audio DSP(s) 81 1 F may also include other suitable processing elements.

[0084] The baseband circuitry 805 may further include a memory/storage 81 1 G. The memory/storage 81 1 G may include data and/or instructions for operations performed by the processors of the baseband circuitry 805 stored thereon. In some embodiments, the memory/storage 81 1 G may include any combination of suitable volatile memory and/or non-volatile memory. The memory/storage 81 1 G may also include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc. In some embodiments, the memory/storage 81 1 G may be shared among the various processors or dedicated to particular processors.

[0085] Components of the baseband circuitry 805 may be suitably combined in a single chip or a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 805 and the application circuitry 803 may be

implemented together, such as, for example, on a system on a chip (SOC).

[0086] In some embodiments, the baseband circuitry 805 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 805 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 805 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0087] The RF circuitry 807 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 807 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. The RF circuitry 807 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 809, and provide baseband signals to the baseband circuitry 805. The RF circuitry 807 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 805, and provide RF output signals to the FEM circuitry 809 for

transmission.

[0088] In some embodiments, the RF circuitry 807 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 807 may include a mixer circuitry 813A, an amplifier circuitry 813B, and a filter circuitry 813C. The transmit signal path of the RF circuitry 807 may include the filter circuitry 813C and the mixer circuitry 813A. The RF circuitry 807 may further include a synthesizer circuitry 813D configured to synthesize a frequency for use by the mixer circuitry 813A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 813A of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 809 based on the synthesized frequency provided by the synthesizer circuitry 813D. The amplifier circuitry 813B may be configured to amplify the down-converted signals.

[0089] The filter circuitry 813C may include a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 805 for further processing. In some embodiments, the output baseband signals may include zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 813A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0090] In some embodiments, the mixer circuitry 813A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 813D to generate RF output signals for the FEM circuitry 809. The baseband signals may be provided by the baseband circuitry 805 and may be filtered by the filter circuitry 813C. The filter circuitry 813C may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0091] In some embodiments, the mixer circuitry 813A of the receive signal path and the mixer circuitry 813A of the transmit signal path may include two or more mixers, and may be arranged for quadrature downconversion and/or upconversion, respectively. In some embodiments, the mixer circuitry 813A of the receive signal path and the mixer circuitry 813A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 813A of the receive signal path and the mixer circuitry 813A of the transmit signal path may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 813A of the receive signal path and the mixer circuitry 813A of the transmit signal path may be configured for super-heterodyne operation.

[0092] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In such embodiments, the RF circuitry 807 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 805 may include a digital baseband interface to communicate with the RF circuitry 807.

[0093] In some dual-mode embodiments, separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0094] In some embodiments, the synthesizer circuitry 813D may include one or more of a fractional-N synthesizer and a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuitry 813D may include a delta-sigma synthesizer, a frequency multiplier, a synthesizer comprising a phase-locked loop with a frequency divider, other synthesizers, and combinations thereof.

[0095] The synthesizer circuitry 813D may be configured to synthesize an output frequency for use by the mixer circuitry 813A of the RF circuitry 807 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 813D may be a fractional N/N+1 synthesizer.

[0096] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 805 or the application circuitry 803 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 803.

[0097] The synthesizer circuitry 813D of the RF circuitry 807 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may include a dual modulus divider (DMD), and the phase accumulator may include a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry-out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements; a phase detector; a charge pump; and a D-type flip-flop. In such embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL may provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle. [0098] In some embodiments, the synthesizer circuitry 813D may be configured to generate a carrier frequency as the output frequency. In some embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency, etc.) and used in conjunction with a quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, the RF circuitry 807 may include an IQ/polar converter.

[0099] The FEM circuitry 809 may include a receive signal path, which may include circuitry configured to operate on RF signals received from the one or more antennas 814, amplify the received signals, and provide the amplified versions of the received signals to the RF circuitry 807 for further processing. The FEM circuitry 809 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 807 for transmission by at least one of the one or more antennas 814.

[0100] In some embodiments, the FEM circuitry 809 may include a TX/RX switch configured to switch between a transmit mode and a receive mode operation. The FEM circuitry 809 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 809 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 807). The transmit signal path of the FEM circuitry 809 may include a power amplifier (PA) configured to amplify input RF signals (e.g., provided by the RF circuitry 807), and one or more filters configured to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 814).

[0101] In some embodiments, the device may include additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.

[0102] In some embodiments, the device may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.

[0103] FIG. 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory/storage devices 920, and one or more communication resources 930, which are communicatively coupled via a bus 940.

[0104] The processors 910 (e.g., 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 radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 912 and a processor 914. The memory/storage devices 920 may include main memory, disk storage, or any suitable combination thereof.

[0105] The communication resources 930 may include interconnection and/or network interface components or other suitable devices to communicate with one or more peripheral devices 904 and/or one or more databases 91 1 via a network 908. For example, the communication resources 930 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular

communication components, Near Field Communication (NFC) components,

Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0106] Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least one of the processors 910 to perform any one or more of the methodologies discussed herein. The instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor's cache memory), the memory/storage devices 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 and/or the databases 91 1 . Accordingly, the memory of the processors 910, the memory/storage devices 920, the peripheral devices 904, and the databases 91 1 are examples of computer-readable and machine-readable media.

Example Embodiments [0107] Example 1 is an apparatus of a user equipment (UE). The apparatus generates an excess number of repetitions report (ENRR), including electronic memory to store downlink (DL) data The apparatus generates an excess number of repetitions report (ENRR), including one or more baseband processors designed to process an allocation of DL resources provided by an evolved node B (eNodeB) and decode the DL data based on the allocation of DL resources. The apparatus generates an excess number of repetitions report (ENRR), including one or more baseband processors designed to determine a quantity of repetitions of a data transmission used to decode the DL data, and generate an excess number of repetitions report (ENRR) based on the quantity of repetitions of the data

transmission used to decode the DL data.

[0108] Example 2 is the apparatus of Example 1 , where the allocation of DL resources is transmitted over a machine physical downlink control channel (M- PDCCH) or a narrowband physical downlink control channel (NB-PDCCH).

[0109] Example 3 is the apparatus of Example 1 , where the one or more processors designed to generate the ENRR are further designed to generate the ENRR in a narrowband physical uplink shared channel (NB-PUSCH).

[0110] Example 4 is the apparatus of Example 3, where the one or more processors designed to generate the ENRR are further designed to generate the ENRR as layer 1 feedback.

[0111] Example 5 is the apparatus of Example 4, where the layer 1 feedback is part of the uplink control information (UCI).

[0112] Example 6 is the apparatus of Example 1 , where the one or more processors designed to generate the ENRR are further designed to generate the ENRR as part of a DL hybrid automatic repeat request acknowledgement (HARQ- ACK).

[0113] Example 7 is the apparatus of Example 1 , where the one or more processors designed to generate the ENRR are further designed to generate the ENRR as part of a medium access control (MAC) element.

[0114] Example 8 is the apparatus of Example 7, where the one or more processors designed to generate the ENRR as part of a MAC control element are further designed to generate the ENRR as part of a newly defined MAC element. ' [0115] Example 9 is the apparatus of Example 7, where the one or more processors designed to generate the ENRR as part of the MAC control element are further designed to generate the ENRR as part of a previously defined MAC element.

[0116] Example 10 is an apparatus of an evolved node B (eNodeB). The apparatus is designed for a variety of repetitions of a data transmission of the eNodeB including electronic memory to store an excess number of repetitions report (ENRR). The apparatus is designed for a variety of repetitions of a data

transmission of the eNodeB including one or more baseband processors designed to allocate downlink (DL) resources for a first DL data to be transmitted with a first quantity of repetitions, and generate the first DL data to be transmitted with the first quantity of repetitions. The apparatus is designed for a variety of repetitions of a data transmission of the eNodeB including one or more baseband processors designed to process the ENRR received from a user equipment (UE), and design a second quantity of repetitions of a second DL data based on the ENRR.

[0117] Example 1 1 is the apparatus of Example 10, where the one or more baseband processors are further designed to allocate DL resources for the second DL data to be transmitted with the second quantity of repetitions. And generate the second DL data to be transmitted with the second quantity of repetitions.

[0118] Example 12 is the apparatus of Example 10, where the first quantity of repetitions of the first DL data is less than the second quantity of repetitions of the second DL data.

[0119] Example 13 is the apparatus of Example 10, where the first quantity of repetitions of the first DL data is greater than the second quantity of repetitions of the second DL data.

[0120] Example 14 is the apparatus of Example 10, where the ENRR describes a third quantity of repetitions used by the UE to successfully receive the first data.

[0121] Example 15 is the apparatus of Example 14, where the ENRR is a difference between the first quantity of repetitions and the third quantity of

repetitions.

[0122] Example 16 is the apparatus of Example 14, where the ENRR is a difference between a maximum number of repetitions associated with the UE and the third quantity of repetitions.

[0123] Example 17 is the apparatus of Example 14, where the ENRR is positive based on a determination that the third quantity of repetitions is less than a first threshold and the ENRR is negative based on a determination that the third quantity of repetitions is greater than a second threshold.

[0124] Example 18 is an apparatus of an evolved node B (eNodeB). The apparatus implements an uplink compensation gap (UCG) and generating an early termination indication (ETI), including electronic memory to store a reference signal (RS) and the ETI. The apparatus has one or more baseband processing units designed to allocate uplink (UL) resources for UL data , where the allocation includes the UCG, and process the UL data from a user equipment (UE). The apparatus has one or more baseband processing units designed to implement a first UCG by making the RS available to the UE for compensation measurements, and process additional UL data from the UE. The apparatus has one or more baseband processing units designedto implement a second UCG by further configuring the one or more baseband processing units to make the RS available to the UE, and generate the ETI to terminate a transmission of the UL data.

[0125] Example 19 is the apparatus of Example 18, where the one or more processing units are further designed to include the UCG in the allocation of UL resources based on a determination that a quantity of repetitions of a downlink (DL) transmission is greater than a threshold.

[0126] Example 20 is the apparatus of Example 18, where the one or more processing units are further designed to include the UCG in the allocation of UL resources based on a coverage level of the UE.

[0127] Example 21 is the apparatus of Example 20, where the coverage level of the UE is based on a quantity of repetitions of at least one of a physical random access channel (PRACH) and a narrowband PRACH (NPRACH).

[0128] Example 22 is the apparatus of Example 20, where the coverage level of the UE is based on a quantity of repetitions of a DL transmission provided by at least one of a UL downlink control information (DCI) and a random access response (RAR).

[0129] Example 23 is the apparatus of Example 20, where the coverage level of the UE is based on a quantity of repetitions of a DL transmission provided by a DL DCI and a RAR.

[0130] Example 24 is a computer-readable storage medium. The computer- readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to process, at a user equipment (UE), an allocation of uplink (UL) resources, and generate UL data based on the allocation of UL resources. The computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to process a reference signal (RS) from an evolved node B

(eNodeB) received during an uplink compensation gap (UCG), and design the UE based on the RS during the UCG scheduled in the allocation of UL resources. The computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to process an early termination indicator (ETI) from the eNodeB received in the UCG, and terminate a UL transmission based on the ETI.

[0131] Example 25 is the computer-readable storage medium of Example 24, where the instructions to process the RS during the UCG contains further

instructions to process the RS during a first UCG, and design the UE during the UCG contains further instructions to design the UE during a first USG, and also process the ETI in the UCG contains further instructions to process the ETI in a second UCG.

[0132] Example 26 is the computer-readable storage medium of Example 24, where a length of the UCG is based on a quantity of downlink (DL) subframes labeled as valid.

[0133] Example 27 is the computer-readable storage medium of Example 24, where the quantity of DL subframes is labeled as valid based on an expectation of successful reception of the DL subframes by the UE.

[0134] Example 28 is the computer-readable storage medium of Example 24, where a length of the UCG is based on a DL signal to noise ratio (SINR).

[0135] Example 29 is the computer-readable storage medium of Example 28, where the DL SINR is based on a DL reference signal received power (RSRP).

[0136] Example 30 is the computer-readable storage medium of Example 24, where the coverage level of the UE is based on at least one of; a first quantity of maximum repetitions of a DL transmission, a second quantity of repetitions of a narrowband physical uplink shared channel (NB-PUSCH) transmission, a third quantity of repetitions of a physical random access channel (PRACH), a fourth quantity of repetitions of a narrowband PRACH (NB-PRACH), and a coverage enhancement (CE) mode of the UE.

[0137] Example 31 is a method for generating an excess number of repetitions report (ENRR). The method includes processing an allocation of download (DL) resources provided by an evolved node B (eNodeB), and decoding DL data based on the allocation of DL resources. The method includes determining a quantity of repetitions of a data transmission used to decode the DL data, and generating an excess number of repetitions report (ENRR) based on the quantity of repetitions of the data transmission used to decode the DL data.

[0138] Example 32 is the apparatus of Example 31 , where the allocation of DL resources is transmitted over a machine physical downlink control channel (M- PDCCH) or a narrowband physical downlink control channel (NB-PDCCH).

[0139] Example 33 is the method of Example 31 , where generating the ENRR further includes generating the ENRR in a narrowband physical uplink shared channel (NB-PUSCH).

[0140] Example 34 is the method of Example 33, where generating the ENRR further includes generating the ENRR as layer 1 feedback.

[0141] Example 35 is the method of Example 34, where the layer 1 feedback is part of the uplink control information (UCI).

[0142] Example 36 is the method of Example 31 , where generating the ENRR further includes generating the ENRR as part of a DL hybrid automatic repeat request acknowledgement (HARQ-ACK).

[0143] Example 37 is the method of Example 31 , where generating the ENRR further includes generating the ENRR as part of a medium access control (MAC) element.

[0144] Example 38 is the method of Example 37, where generating the ENRR as part of a MAC control element further includes generating the ENRR as part of a newly defined MAC element.

[0145] Example 39 is the method of Example 37, where generating the ENRR as part of the MAC control element further includes generate the ENRR as part of a previously defined MAC element.

[0146] Example 40 is a method for configuring a variety of repetitions of a data transmission of an eNodeB. The method includes allocating downlink (DL) resources for a first DL data to be transmitted with a first quantity of repetitions, and generating the first DL data to be transmitted with the first quantity of repetitions. The method includes processing an excess number of repetitions report (ENRR) received from a user equipment (UE), and configuring a second quantity of repetitions of a second DL data based on the ENRR. [0147] Example 41 is the method of Example 40, further including allocating DL resources for the second DL data to be transmitted with the second quantity of repetitions, and generating the second DL data to be transmitted with the second quantity of repetitions.

[0148] Example 42 is the method of Example 40, where the first quantity of repetitions of the first DL data is less than the second quantity of repetitions of the second DL data.

[0149] Example 43 is the method of Example 40, where the first quantity of repetitions of the first DL data is greater than the second quantity of repetitions of the second DL data.

[0150] Example 44 is the method of Example 40, where the ENRR describes a third quantity of repetitions used by the UE to successfully receive the first data.

[0151] Example 45 is the method of Example 44, where the ENRR is a difference between the first quantity of repetitions and the third quantity of repetitions.

[0152] Example 46 is the method of Example 44, where the ENRR is a difference between a maximum number of repetitions associated with the UE and the third quantity of repetitions.

[0153] Example 47 is the method of Example 44, where the ENRR is positive based on a determination that the third quantity of repetitions is less than a first threshold and the ENRR is negative based on a determination that the third quantity of repetitions is greater than a second threshold.

[0154] Example 48 is a method for implementing an uplink compensation gap (UCG) and generating an early termination indication (ETI). The method includes allocating uplink (UL) resources for UL data , where the allocation includes the UCG, and processing the UL data from a user equipment (UE). The method includes implementing a first UCG by making a reference signal (RS) available to the UE for compensation measurements, and processing additional UL data from the UE. The method includes implementing a second UCG by making the RS available to the UE, and generating the ETI to terminate a transmission of the UL data.

[0155] Example 49 is the method of Example 48, further including including the UCG in the allocation of UL resources based on a determination that a quantity of repetitions of a downlink (DL) transmission is greater than a threshold.

[0156] Example 50 is the method of Example 48, further including including the UCG in the allocation of UL resources based on a coverage level of the UE. [0157] Example 51 is the method of Example 50, where the coverage level of the UE is based on a quantity of repetitions of at least one of a physical random access channel (PRACH) and a narrowband PRACH (NPRACH).

[0158] Example 52 is the method of Example 50, where the coverage level of the

UE is based on a quantity of repetitions of a DL transmission provided by at least one of a UL downlink control information (DCI) and a random access response

(RAR).

[0159] Example 53 is the method of Example 50, where the coverage level of the UE is based on a quantity of repetitions of a DL transmission provided by a DL DCI and a RAR.

[0160] Example 54 is a method. The method includes processing, at a user equipment (UE), an allocation of uplink (UL) resources, and generating UL data based on the allocation of UL resources. The method includes processing a reference signal (RS) from an evolved node B (eNodeB) received during an uplink compensation gap (UCG), and configuring the UE based on the RS during the UCG scheduled in the allocation of UL resources. The method includes processing an early termination indicator (ETI) from the eNodeB received in the UCG, and terminating a UL transmission based on the ETI.

[0161] Example 55 is the method of Example 54, where processing the RS during the UCG further includes processing the RS during a first UCG, and configuring the UE during the UCG further includes configuring the UE during a first USG, and further processing the ETI in the UCG further includes processing the ETI in a second UCG.

[0162] Example 56 is the method of Example 54, where a length of the UCG is based on a quantity of downlink (DL) subframes labeled as valid.

[0163] Example 57 is the method of Example 54, where the quantity of DL subframes is labeled as valid based on an expectation of successful reception of the DL subframes by the UE.

[0164] Example 58. Is the method of Example 54, where a length of the UCG is based on a DL signal to noise ratio (SINR).

[0165] Example 59 is the method of Example 58, where the DL SINR is based on a DL reference signal received power (RSRP).

[0166] Example 60 is the method of Example 54, where the coverage level of the UE is based on at least one of; a first quantity of maximum repetitions of a DL transmission, a second quantity of repetitions of a narrowband physical uplink shared channel (NB-PUSCH) transmission, a third quantity of repetitions of a physical random access channel (PRACH), a fourth quantity of repetitions of a narrowband PRACH (NB-PRACH), and a coverage enhancement (CE) mode of the UE.

[0167] Example 61 is at least one computer-readable storage medium having stored thereon computer-readable instructions, when executed, to implement a method as exemplified in any of Examples 31 -60.

[0168] Example 62 is an apparatus including a manner to perform a method as exemplified in any of Examples 31 -60.

[0169] Example 63 is a method for performing a method as exemplified in any of Examples 31 -60.

[0170] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, a non-transitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or another medium for storing electronic data. The eNodeB (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter

component, a processing component, and/or a clock component or timer component. One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or an interpreted language, and combined with hardware implementations. [0171] It should be understood that many of the functional units described in this specification may be implemented as one or more components, which is a term used to more particularly emphasize their implementation independence. For example, a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.

[0172] Components may also be implemented in software for execution by various types of processors. An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function.

Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.

[0173] Indeed, a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code

segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The components may be passive or active, including agents operable to perform desired functions.

[0174] Reference throughout this specification to "an example" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment. Thus, appearances of the phrase "in an example" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0175] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on its presentation in a common group without indications to the contrary. In addition, various embodiments and examples may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of embodiments.

[0176] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the embodiments are not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1 . An apparatus of a user equipment (UE) to generate an excess number of repetitions report (ENRR), comprising:

electronic memory to store downlink (DL) data; and

one or more baseband processors configured to:

process an allocation of DL resources provided by an evolved node B

(eNodeB);

decode the DL data based on the allocation of DL resources;

determine a quantity of repetitions of a data transmission used to decode the DL data; and

generate an excess number of repetitions report (ENRR) based on the quantity of repetitions of the data transmission used to decode the DL data.

2. The apparatus of claim 1 , wherein the allocation of DL resources is transmitted over a machine physical downlink control channel (M-PDCCH) or a narrowband physical downlink control channel (NB-PDCCH).

3. The apparatus of claim 1 , wherein the one or more processors configured to generate the ENRR are further configured to generate the ENRR in a narrowband physical uplink shared channel (NB-PUSCH).

4. The apparatus of claim 3, wherein the one or more processors configured to generate the ENRR are further configured to generate the ENRR as layer 1 feedback.

5. The apparatus of claim 4, wherein the layer 1 feedback is part of the uplink control information (UCI).

6. The apparatus as in claims 1 , 2, 3, 4, or 5, wherein the one or more processors configured to generate the ENRR are further configured to generate the ENRR as part of a DL hybrid automatic repeat request acknowledgement (HARQ- ACK).

7. The apparatus as in claims 1 , 2, 3, 4, or 5, wherein the one or more processors configured to generate the ENRR are further configured to generate the ENRR as part of a medium access control (MAC) element.

8. The apparatus of claim 7, wherein the one or more processors configured to generate the ENRR as part of a MAC control element are further configured to generate the ENRR as part of a newly defined MAC element.

9. The apparatus of claim 7, wherein the one or more processors configured to generate the ENRR as part of the MAC control element are further configured to generate the ENRR as part of a previously defined MAC element.

10. An apparatus of an evolved node B (eNodeB) to configure a plurality of repetitions of a data transmission of the eNodeB, comprising:

electronic memory to store an excess number of repetitions report (ENRR); and

one or more baseband processors configured to:

allocate downlink (DL) resources for a first DL data to be transmitted with a first quantity of repetitions;

generate the first DL data to be transmitted with the first quantity of repetitions;

process the ENRR received from a user equipment (UE); and configure a second quantity of repetitions of a second DL data based on the ENRR.

1 1 . The apparatus of claim 10, wherein the one or more baseband processors are further configured to:

allocate DL resources for the second DL data to be transmitted with the second quantity of repetitions; and

generate the second DL data to be transmitted with the second quantity of repetitions.

12. The apparatus as in claims 10 or 1 1 , wherein the first quantity of repetitions of the first DL data is less than the second quantity of repetitions of the second DL data.

13. The apparatus as in claims 10 or 1 1 , wherein the first quantity of repetitions of the first DL data is greater than the second quantity of repetitions of the second DL data.

14. The apparatus as in claims 10 or 1 1 , wherein the ENRR describes a third quantity of repetitions used by the UE to successfully receive the first data.

15. The apparatus of claim 14, wherein the ENRR is a difference between the first quantity of repetitions and the third quantity of repetitions.

16. The apparatus of claim 14, wherein the ENRR is a difference between a maximum number of repetitions associated with the UE and the third quantity of repetitions.

17. The apparatus of claim 14, wherein the ENRR is positive based on a determination that the third quantity of repetitions is less than a first threshold and the ENRR is negative based on a determination that the third quantity of repetitions is greater than a second threshold.

18. An apparatus of an evolved node B (eNodeB) to implementing an uplink compensation gap (UCG) and generating an early termination indication (ETI), comprising:

electronic memory to store a reference signal (RS) and the ETI; and one or more baseband processing units configured to:

allocate uplink (UL) resources for UL data , wherein the allocation includes the UCG;

process the UL data from a user equipment (UE);

implement a first UCG by making the RS available to the UE for compensation measurements;

process additional UL data from the UE; and

implement a second UCG by further configuring the one or more baseband processing units to:

make the RS available to the UE; and

generate the ETI to terminate a transmission of the UL data.

19. The apparatus of claim 18, wherein the one or more processing units are further configured to include the UCG in the allocation of UL resources based on a determination that a quantity of repetitions of a downlink (DL) transmission is greater than a threshold.

20. The apparatus of claim 18, wherein the one or more processing units are further configured to include the UCG in the allocation of UL resources based on a coverage level of the UE.

21 . The apparatus of claim 20, wherein the coverage level of the UE is based on a quantity of repetitions of at least one of a physical random access channel (PRACH) and a narrowband PRACH (NPRACH).

22. The apparatus as in claims 20 or 21 , wherein the coverage level of the UE is based on a quantity of repetitions of a DL transmission provided by at least one of a UL downlink control information (DCI) and a random access response (RAR).

23. The apparatus as in claims 20 or 21 , wherein the coverage level of the UE is based on a quantity of repetitions of a DL transmission provided by a DL DCI and a RAR.

24. A computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to:

process, at a user equipment (UE), an allocation of uplink (UL) resources; generate UL data based on the allocation of UL resources;

process a reference signal (RS) from an evolved node B (eNodeB) received during an uplink compensation gap (UCG);

configure the UE based on the RS during the UCG scheduled in the allocation of UL resources;

process an early termination indicator (ETI) from the eNodeB received in the UCG; and

terminate a UL transmission based on the ETI.

25. The computer-readable storage medium of claim 24, wherein the instructions to:

process the RS during the UCG comprise further instructions to process the RS during a first UCG;

configure the UE during the UCG comprise further instructions to configure the UE during a first USG; and

process the ETI in the UCG comprise further instructions to process the ETI in a second UCG.

26. The computer-readable storage medium of claim 24, wherein a length of the UCG is based on a quantity of downlink (DL) subframes labeled as valid.

27. The computer-readable storage medium of claim 24, wherein the quantity of DL subframes is labeled as valid based on an expectation of successful reception of the DL subframes by the UE.

28. The computer-readable storage medium of claim 24, wherein a length of the UCG is based on a DL signal to noise ratio (SINR).

29. The computer-readable storage medium of claim 28, wherein the DL SINR is based on a DL reference signal received power (RSRP).

30. The computer-readable storage medium as in claims 24, 25, 26, 27, 28, or 29, wherein the coverage level of the UE is based on at least one of:

a first quantity of maximum repetitions of a DL transmission;

a second quantity of repetitions of a narrowband physical uplink shared channel (NB-PUSCH) transmission;

a third quantity of repetitions of a physical random access channel (PRACH); a fourth quantity of repetitions of a narrowband PRACH (NB-PRACH); and a coverage enhancement (CE) mode of the UE.