CN108781137A - The report of enhancing and uplink Robust-Design - Google Patents

Abstract

Present disclose provides ENRR.Generating ENRR may include：The distribution to resource provided by eNodeB is provided, UL data transmissions are handled based on the distribution to DL resources provided by eNodeB, DL data are decoded based on the distribution to DL resources, determine the number of iterations of data transmission for decoding DL data, and excess duplicate reports (ENRR) are generated based on the number of iterations of the data transmission for decoding DL data.

Description

Enhanced reporting and uplink robustness design

related application

This application claims the benefit of U.S. Nonprovisional Patent Application Serial No. 62/336,394, filed May 13, 2016, and U.S. Nonprovisional Patent Application Serial No. 62/308,512, filed March 15, 2016, which It is hereby incorporated by reference in its entirety.

technical field

The present disclosure relates to excess number of repetitions report (ENRR), uplink compensation gap (uplink compensation gap, UCG) and early termination indication (early termination indication, ETI). Specifically, this disclosure relates to generating and processing ENRR, UCG, and ETI.

Description of drawings

FIG. 1 is a timing diagram of ENRR according to one embodiment.

Figure 2 is a timing diagram of UCG and ETI according to one embodiment.

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. 4 is a block diagram illustrating a method for configuring the number of repetitions of DL transmissions based on ENRR according to one embodiment.

Figure 5 is a block diagram illustrating a method for generating ENRR according to one embodiment.

Figure 6 is a block diagram illustrating a method for implementing UCG according to one embodiment.

Figure 7 is a block diagram illustrating a method for ETI according to one embodiment.

Figure 8 is a block diagram illustrating components of a device according to one embodiment.

Figure 9 is a block diagram illustrating components according to some embodiments.

Detailed ways

Wireless mobile communication technologies use various standards and protocols to generate and/or transmit data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to in the industry as Worldwide Interoperability for Microwave Access (WiMAX); ); and the IEEE 802.11 standard, commonly referred to in the industry as Wireless Local Area Network (WLAN) or Wi-Fi. In a 3GPP Radio Access Network (RAN) in an LTE system, a base station may include an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted Evolved Node B, Enhanced Node B, eNodeB or eNB) and and/or a Radio Network Controller (RNC) in E-UTRAN, which communicates with wireless communication devices called User Equipment (UE). In an LTE network, E-UTRAN may include multiple eNodeBs and may communicate with multiple UEs. LTE networks include radio access technologies (RATs) and a core radio network architecture that can provide high data rates, low latency, packet optimization, and improved system capacity and coverage.

Enhanced Machine Type Communication (eMTC) UEs and Narrowband (NB) Internet of Things (loT) UEs can use reporting mechanisms to improve UE/evolved Node B (eNodeB) communication. For example, UE and/or eNodeB may use ENRR, UCG, and ETI to improve UE/evolved Node B (eNodeB) communication. As used herein, the term "UE" may be used to refer to both NB UEs and non-NB UEs. In some examples, UEs may be used for eMTC.

Implementing ENRR can enhance the allocation of downlink (DL) resources. Implementing UCG can enhance uplink (UL) robustness by enabling UEs to compensate for frequency and timing references. Implementing ETI can optimize the eNodeB's allocation of uplink resources. ETI can be implemented during UCG for half-duplex frequency division duplex (HD-FDD) or as an uplink grant for full-duplex frequency division duplex (FDD).

When managing a UE in Coverage Enhanced (CE) mode, the mobile network can allocate UL and DL resources. Allocating UL and DL resources can be a trade-off between high latency/low data rate and repetition level. During the CE mode of operation, the UE may utilize repetition to overcome path loss to the eNodeB. For example, eMTC UEs can use repetition levels (RL) ranging from 1 to 2,048 repetitions, NB-loT UEs can use RLs ranging from 1 to 2,048 repetitions, and eNodeBs can also use RLs ranging from 1 to 2,048 repetitions. Duplicate RL. Extended UL operation may produce frequency errors, which may be exacerbated by temperature changes. The temperature variation may be a result of temperature variation of the UE's surrounding environment and heating of the power amplifier during continuous transmission. As used herein, repetition levels may define repetitions of data transfers. For example, a repetition level of 2,048 may describe 2,048 repetitions of data transmission to the UE and/or eNodeB.

Reference is now made to the drawings in which like reference numerals represent like elements. For clarity, the first digit of a reference number indicates the figure number in which the corresponding element is first used. In the following description, numerous specific details are provided to provide a thorough understanding of the embodiments disclosed herein. Those skilled in the art will recognize, however, that the embodiments described herein may be practiced without one or more of these specific details, or with other methods, components, or materials. Also, in some instances, well-known structures, materials, or operations are not shown or described in detail 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.

FIG. 1 is a timing diagram 100 of ENRR according to one embodiment. Sequence diagram 100 includes eNodeB 102 and UE 104 . The timing diagram also includes DL resource allocation 106-1 and 106-2, DL transmission 110-1 and 110-2, DL repetition (DL eNodeB repetition) 108-1 and 108-2, DL repetition (DL UE repetition) 112, UE Transmission start 114 , ENRR transmission 116 and optimal termination 118 .

DL transmissions 110-1 and 110-2 may include DL control data and DL shared data. For example, DL transmissions 110-1 and 110-2 may be DL control channels or DL shared channels, among other types of DL transmissions.

As used herein, ENRR can be defined in one or more of the following ways. For example, ENRR may be calculated as the difference between the number of repetitions 112 that the UE 104 used to successfully receive the DL transmission 110-1 and the number of repetitions 108-1 that the eNodeB 102 used to send the DL transmission 110-1, determined by the downlink Indicated by channel control information (DCI) or radio resource control (RRC) configuration. In some examples, DL transmissions may include DL shared channels.

In some examples, in addition to or instead of the previous example, the ENRR may also include an indication as to whether the UE 104 is capable of using a smaller number of repetitions 108-1 than the number of repetitions 108-1 that the eNodeB 102 used to send the DL transmission 110-1. Repeat 112 to successfully decode DL transmission 110-1 (eg, DL control channel). The DL transmission 110-1 may also include a machine physical downlink control channel (eg, M-PDCCH) for eMTC UEs and/or a narrowband physical downlink control channel (NB-PDCCH) for NB-IoT UEs. ENRR may also be defined as the difference between the number of repetitions 112 that UE 104 used to successfully decode DL transmission 110-1 and the maximum number of repetitions that eNodeB 102 is configured to send DL transmission 110-1 to UE 104. As used herein, the number of repetitions 108 - 1 that the eNodeB 102 uses to send the DL transmission 110 - 1 may be different from the maximum number of repetitions that the eNodeB 102 is configured to send the DL transmission 110 - 1 to the UE 104 . The number of repetitions 108-1 may vary for a given DL transmission, while the maximum number of repetitions may be static and not change for a given period of time. The number of repetitions 108-1 can be configured to be no greater than the maximum number of repetitions.

In some examples, if the number of early decodes of DL transmissions (e.g., including DL transmission 110-1) is equal to or greater than a parameter (e.g., a threshold) configured by radio resource control (RRC) signaling or successful early decoding of DL transmissions , the UE 104 may report a positive ENRR. As used herein, early decoding of DL transmission 110-1 may describe a number of transmissions 112 that is less than the number of transmissions 108-1. If the predefined number of instances of successful early decoding of DL transmission 110-1 is equal to two, then early decoding of a DL transmission (eg, including DL transmission 110-1) may occur two or more times before UE 104 reports a positive ENRR. A predefined number of instances of successful early decoding of DL transmissions may be specified or configured as a common setting for the radio link, and/or standardized for eMTC and/or NB-loT UEs in a UE-specific manner with a level of coverage enhancement set up.

If the number of early decodes of a DL transmission (e.g., including DL transmission 110-1) is less than a parameter configured by radio resource control (RRC) signaling or a predefined number of instances of successful early decoding of a DL transmission, the UE 104 may report Negative ENRR. If the predefined number of instances of successful early decoding of DL transmission 110-1 is equal to four, then early decoding of a DL transmission (eg, including DL transmission 110-1) may occur three or fewer times before UE 104 reports a negative ENRR.

The predefined number of instances of successful early decoding may be a percentage below the maximum number of repetitions that eNodeB 102 is configured to send DL transmission 110 - 1 to UE 104 . For example, UE 104 may report ENRR when repetitions 112 are below a predefined percentage of the maximum number of repetitions. The UE 104 may also report ENRR when the repetition 112 is a predefined percentage above the maximum number of repetitions.

The predefined number of instances of successful early decoding may also be the number of successful early decoding or repetitions 108-1. For example, UE 104 may report ENRR when repetition 112 is below the absolute number (eg, a predefined number of instances) of successful early decoding of transmission 108-1. UE 104 may report ENRR when repetition 112 is higher than the absolute number (eg, a predefined number of instances) of successful early decoding of repetition 108-1.

The predefined number of instances of successful early decoding may involve DL transmissions 110-1, e.g. (NB)PDCCH and/or Physical Downlink Shared Channel or NB Physical Downlink Shared Channel (NB)PDSCH, as well as other types of DL Transmission 110-1. A threshold may be defined as the absolute number of successful early decodes defined independently of repetition 108-1. The predefined number of instances of successful early decoding may be defined based on CE level or configured range of repetition 108-1.

The predefined number of instances of successful early decoding may be provided from eNodeB 102 to UE 104 or from UE 104 to eNodeB 102 via existing and/or new System Information Block(s) (SIBs). The predefined number of instances of successful early decoding may be provided from eNodeB 102 to UE 104 or from UE 104 to eNodeB 102 via dedicated RRC connection reconfiguration, message 4 (msg.4) (eg, RRC connection setup), or DCI.

The eNodeB 102 may utilize the ENRR to configure the repetition 108-2 and/or subsequent repetitions of the DL transmission. For example, eNodeB 102 may utilize ENRR to trigger configuration of repeat 108-2 that is larger or smaller than repeat 108-1. In some examples, different types of indications can be configured. This may be a supplementary report of the ENRR (based on the UE's estimate of the number of additional repetitions that may be required to decode the information correctly), known as a short number of repetitions report (SNRR).

ENRR may indicate repetition 112 . ENRR may include one or more bits to indicate the number of repetitions 112 . For example, ENRR may include two or more bits to report three or more repeats beyond repeat 108-1.

If the UE 104 is configured with a set of repetitions {4,8,16,32,64,128,256,512}, the (NB)PDSCH is sent using 128 repetitions (e.g., repetition 108-1), and the number of repetitions 112 is between 32 and 64 ( For example, 32<repeat 112≤64), then, taking 2 bits as an example, the UE may indicate bit 01 as ENRR to indicate that the repeat 112 is between 32 and 64 repeats. That is, bit 01 may identify an index of the repeated set {4, 8, 16, 32, 64, 128, 256, 512} below the currently selected index. The currently selected index may be 5 if the repeat 108-1 is configured as 128 repeats. ENRR including bit 01 identifies a decimal index that is one less than index 5, where repetition 108-1 is configured to identify index 4 from the repetition set. The index 4 of the repetition set may identify 64 repetitions and the number of identification repetitions 112 is between 32 and 64.

The ENRR may include bits 00, 01, 10, and 11 in the two ENRR examples. Bit 00 may correspond to T _-1 <X≤T ₀ , bit 01 may correspond to T _-2 <X≤T ₁ , bit 10 may correspond to T _-3 <X≤T _-2 , and bit 11 may correspond to X≤ T _-3 . X may indicate UE repetition 112 . T ₀ corresponds to a configured number of repetitions 108-1 (eg, 128). T _-1 corresponds to the number of replicates 64 in the replicate set. T ₋₁ may identify an index (eg, 4) that is less than an index (eg, 5) associated with the configured number of repetitions 108-1. T ₋₂ corresponds to a repeat number of 32 and two indices (eg, 3) less than the index associated with the configured number of repeats 108-1. T ₋₃ corresponds to a repeat number of 16 and three indices (eg, 2) less than the index associated with the configured number of repeats 108-1.

In some examples, ENRR may include a single bit to report whether repeat 112 is significantly smaller than repeat 108-1. As used herein, significantly smaller may describe less than a predefined threshold of repeat 108-1. Significantly smaller thresholds can be configured through common RRC. A significantly smaller threshold may be the number of repeats that repeat 112 is less than repeat 108-1 , or T ₀ /(2 ^W ) repeats that repeat 112 is less than repeat 108-1 , where W is a positive integer.

ENRR may also include (similar to the 2-bit example above) feedback for the number N of DL shared channel receptions or DL control channel receptions that have been received. For the case of DL control channel reception, N may correspond to instances where valid DCI was successfully detected.

ENRR may also include some bits needed to encode repetition 112 . ENRR may also include some bits to indicate repetition 112 . For example, if the repetition 108-1 is configured with a repetition level (x ₁ , x ₂ , . . . , _xm ) for the DL transmission 110-1, the ENRR may report x _n or fewer repetitions 112.

In some examples, ENRR may include a single bit to represent positive ENRR and negative ENRR. For example, a first bit value (eg, 1 bit) may represent positive ENRR, and a second bit value (eg, 2 bits) may represent negative ENRR.

ENRR may be provided by UE 104 using layer 1 feedback. Layer 1 feedback may include, for example, uplink control information (UCI). The ENRR may be sent by the UE 104 via DL Hybrid Automatic Repeat Request Acknowledgment (DL HARQ-ACK) feedback, at least when the ENRR corresponds to early decoding of the DL shared channel.

ENRR transmission may be triggered (eg, requested) by the eNodeB using fields in the DL DCI that schedule PDSCH or NB-PDSCH. For NB-IoT, if CSI reporting is not supported and/or not configured, the CSI request field may be reinterpreted to indicate a request for ENRR transmission on scheduled (NB)PUSCH resources.

If ENRR is sent together with HARQ-ACK feedback, the scheduling of (NB)PUSCH resources may be the same resources as those used for transmission of DL HARQ-ACK feedback. (NB)PUSCH resources may be indicated using a combination of resources configured by higher layers. (NB)PUSCH resources may be offset in time and/or frequency domain as indicated by DL DCI. The offset of the (NB)PUSCH in the frequency domain may be determined, at least in part, implicitly based on a starting subframe of the (NB)PDCCH and/or (NB)PDSCH. ENRR may also be sent together with UL shared channel (SCH) transmission on (NB)PUSCH in a similar manner to power headroom report (PHR) transmission.

The ENRR may also be sent using a MAC Control Element (MAC CE) and/or as an RRC message in response to a trigger received from the eNodeB 102 . Triggering can be indicated through MAC CE or UE-specific RRC messages. ENRR may be generated and/or sent as a new MAC CE. An ENRR MAC CE may be identified by a MAC Protocol Data Unit (PDU) subheader with a Logical Channel ID (LCID). For example, a common control channel (CCCH) may be included at index 00000, an identification of a logical channel may be included at index 00001-01010, a CCCH may be included at index 01011, ENRR may be included at index 01100, and multiple Reserved LCID values may be included at index 1101-10101, a truncated sidelink buffer status report (BSR) may be included at index 10111, a dual connectivity PHR may be included at index 1100, Extended PHR may be included at index 1101, PHR may be included at index 11010, Cell Radio Network Temporary Identifier (C-RNTI) may be included at index 11011, shortened BSR may be included at 11100, short BSR may Included at 11101, long BSR may be included at 11110, and index 11111 may include padding.

In some examples, the ENRR may be generated and/or sent with the PHR MAC CE using one or two available reserved bits. If the ENRR is included in the PHR MAC CE, the ENRR may indicate the repetition used in the DL transmission 110-1 (eg, including control and/or data), even though the PHR includes information related to the UL transmission.

The PHR MAC Control Element is identified by the MAC PDU subheader with LCID as described above. The PHR MAC Control Element may have a fixed size and may consist of a single octet. If a reserved bit is set to 0, one of the two bits can be used for the ENRR indication (indicated at V). If a single bit V is used for ENRR, a bit value of 1 may indicate positive ENRR, and a bit value of 0 may indicate neutral ENRR and/or negative ENRR. A neutral ENRR may indicate that repetition 112 is equal to repetition 108-1 and/or within a predetermined threshold of repetition 108-1. If two bits V are used for ENRR, a bit value of 00 can indicate the presence of a neutral ENRR value and/or a baseline of negative ENRR, while other bit values can describe positive ENRR and repeat 112 less than repeat 108 as previously stated How many.

A power headroom (PH) field indicates a power headroom level. The length of the field is 6 bits. ENRR can be provided through the PH field. The reported PH and corresponding power headroom level may include ENRR in one or two most significant bits.

The eNodeB 102 generates the DL resource allocation transmission and provides the DL resource allocation transmission to the UE 104 . The DL resource allocation transmission may allocate resources for number of tones, subcarrier (SC) spacing, modulation and coding scheme (MCS), and/or RL among other DL resource allocations. UE 104 may receive, decode and/or process DL resource allocation 106-1. The eNodeB 102 generates and/or provides DL transmission 110-1. DL transmission 110-1 may include data, control information and/or UL resource allocations. UL resources may include number of tones, SC interval, MCS, RL, and ENRR requests. The ENRR request may request ENRR from UE 104 . The eNodeB 102 may be configured to generate and/or send a DL transmission 110-1 using multiple repetitions 108-1. For example, if the number of repetitions 108-1 is set to 16, the DL transmission 110-1 may be sent 16 times continuously, or intermittently with another transmission 16 times.

UE 104 may determine repetition 112 for decoding and/or successfully processing DL transmission 110-1. In FIG. 1, repeat 112 may be smaller than repeat 108-1.

After receiving the repetition 108-1 of the DL transmission 110-1, the UE 104 may begin 114 the UL transmission 116. UL transmission 116 may include data and/or ENRR. The eNodeB 102 may generate and/or provide a DL resource allocation 106-2. The eNodeB 102 may also generate and/or provide DL transmission 110-2. DL transmission 110-2 may or may not include ENRR. The eNodeB 102 may generate and/or provide the DL transmission 110-2 with a number of repetitions 108-2. The number of repetitions 108-2 may be configured based on ENRR. That is, the number of repetitions 108-2 may be configured to conform, for example, to repetitions 112 described in ENRR. The repetition 108-2 may be configured to provide optimal termination 118 of the DL transmission 110-2. Optimal termination 118 of DL transmission 110-2 may describe the termination of DL transmission 110-2 sent with repetition 108-2, wherein repetition 108-2 is closely aligned with repetition 112. For example, optimal termination 118 may include repetitions 108-2 equal to the repetitions used by UE 104 to decode, receive, and/or process DL transmission 110-2.

FIG. 2 is a timing diagram 200 of UCG and ETI according to one embodiment. Sequence diagram 200 includes eNodeB 202 and UE 204 similar to eNodeB 102 and UE 104 in FIG. 1 . Timing diagram 200 also includes DL resource allocation 206, DL transmission 208, UL transmissions 216-1 and 216-2, and uplink backoff gaps (UCGs) 224-1 and 224-2.

The UE 204 may be configured with UCG by higher layers based on the coverage level of the UE 204 or the coverage class of the UE 204 . In some examples, a UE 204 with repetition of the highest L level in its set of configured repetition levels may be configured with a UCG, where L is specified or configured in a cell-specific manner. That is, the UE 204 among the UEs served by the eNodeB 202 with the maximum number of repetitions 206 may automatically be configured with a UCG.

When the coverage level or the number of repetitions of the UE 204 is above a threshold, the UE 204 may be configured with UCG. For example, UE 204 may be configured with a UCG if UE 204 is configured with a number of repetitions 206 that is at least greater than the number of repetitions another UE is configured with.

The level of coverage enhancement for UE 204 may be determined based on the selected or used repetition level (eg, number of repetitions) for the most recent transmission of the NB-IoT UE's Physical Random Access Channel (PRACH) or NB-PRACH. The UCG may be applied to the UE 204 if the (NB)PRACH repetition level is above a specified or configured threshold. The mapping from the (NB)PRACH repetition level can be applied for (NB)PRACH transmissions as well as for (NB)PUSCH transmissions (including message 3 transmissions) until the RRC connection is established or at least until message 4 is received. The UCG may be applied to the UE based on the UE's (NB)PRACH repetition level, which may be used for subsequent (NB)PUSCH transmissions.

For (NB)PUSCH transmission, the applicability of UCG may be based on the number of repetitions indicated in the UL grant carried by the UL DCI or in the Random Access Response (RAR) in the case of message 3 . For a (NB)PRACH transmission initiated by a (NB)PDCCH order, the applicability of the UCG may be based on the starting (NB)PRACH repetition level or the number of (NB)PRACH repetitions indicated in the DL DCI carrying the (NB)PDCCH order.

For NB-loT, not all subframes can be used or configured for NB-loT DL transmission. Such DL subframes are null DL subframes, and those DL subframes and those carrying narrowband primary and secondary synchronization signals (NPSS/NSSS) may not carry narrowband reference signals (N-RS). Therefore, subframes may be less useful for half-duplex frequency division duplex (HD-FDD) UEs to track frequency estimates or to average/filter across subframes to improve the accuracy of the estimates. The UCG length of the UCG may be defined according to the number of DL valid subframes for which the UE receives, processes and/or decodes the N-RS.

The number of DL valid subframes for which the UE may assume the presence of N-RS may be a function of the DL Signal-to-Noise Ratio (SINR), which may be based, for example, on the DL Reference Signal Received Power (RSRP) or variants thereof . The number of valid subframes can also be defined as a function of the coverage level of the UE, which can be determined by the maximum number of repetitions of the configured UE-specific search space for NB-PDCCH, the number of repetitions for NB-PUSCH transmission , NB-PRACH repetition level, and/or CE mode (as configured by eNodeB 202 for UE 204 or implicitly determined by UE 204) is presented.

The length 222 of the UCG may be a function of the DL SINR. DL SINR may be based on DL RSRP. In some examples, the length 222 of the UCG may be defined as a function of the coverage level of the UE 204, which may be determined by the maximum number of repetitions of the configured UE 204 specific search space for the NB-PDCCH, for the narrowband physical uplink One of the combination of the number of repetitions of the shared channel (NB-PUSCH) transmission, the (NB)PRACH repetition level, and/or the CE mode (as configured by the eNodeB 202 for the UE 204 or implicitly determined by the UE 204) or more to represent.

For eNodeB 202 to send an early termination indication (ETI) during UCG 224-2, UE 204 may monitor the DL control channel at least during a certain portion of UCG 224-2. A specific part of the UCG 224-2 may describe a specific subframe among DL available subframes and/or a specific subframe with a specific periodicity within the UCG 224-2. Monitoring of the DL control channel by UE 204 may be configured based on a boolean flag. For example, bit 1 may command UE 204 to monitor the DL control channel, and bit 0 may command UE 204 not to monitor the DL control channel. The Boolean flag may be sent using a cell-common RRC (SIB) message and/or via a dedicated RRC message (eg, during RRC connection establishment).

Associated with a Boolean flag for enabling/disabling monitoring by UE 204, UE 204 may be configured to monitor UE-specific Search Space (USS). ETI may be indicated by DCI (eg, already existing DCI). The DCI may identify the newly defined UL grant for the newly defined transport block carrying the original UL grant. One or more fields of the original UL grant may be changed to indicate that the already existing DCI is an ETI for a specific UL process. The ETI may also be indicated by a new DCI format with a compact size that the UE monitors during UCGs (eg, UCGs 224-1 and 224-2).

If multiple HARQ processes are supported for UL transmission, the UCGs 224-1 and 224-2 for each HARQ process may, via the UCGs 224-1 and 224-2's initiators relative to the UL transmission for the specific HARQ process The starting subframe of the frame is uniquely identified for each HARQ process. Furthermore, the unique identifier can be used to implicitly identify the HARQ process to which the ETI corresponds.

Multiple HARQ processes can be provided by a single UCG. The DCI indicating the ETI may provide the identity of the HARQ process corresponding to the ETI. Also, ETIs corresponding to multiple HARQ processes can be carried in the same DCI.

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

The patterns of UCGs 224-1 and 224-2 may be based on existing measurement gaps (eg, spanning a duration of 6 milliseconds (ms)). That is, the patterns of UCGs 224-1 and 224-2 may be based on UCG length and 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 in the middle of an entire UL burst including multiple repetitions of the rate matching block. A rate matching block corresponds to a set of subframes for mapping a single (NB)PDSCH transport block.

The precise time offset relative to the starting subframe of the UL burst can be configured in a UE-specific way via higher layers, and possibly with a further offset for the higher layer indication time offset carried by the UL grant. Furthermore, UCGs may only occur between complete repeated sets of rate-matched blocks.

The eNodeB 202 can generate the DL resource assignment 206 and provide the DL resource assignment 206 to the UE 204 . DL resource allocation 206 may include number of tones, SC interval, MCR, and/or RL, among other resource allocations.

The eNodeB 202 can also generate and/or provide DL transmissions 208 using multiple repetitions 206 . DL transmission 208 may include data transmission and/or UL resource allocation. UL resource allocation may include number of tones, SC interval, MCS, and RL. UL resource allocation may also include ENRR. UE 204 may process and/or decode DL transmission 208 and begin 214 (eg, initiate) sending UL transmission 216-1 (eg, UL data transmission).

UL data transmissions including UL transmissions 216 - 1 and 216 - 2 may start at 214 and end at 228 . The eNodeB 202 may begin (220) receive the UL transmission 216-1. The eNodeB 202 may generate, encode and/or transmit a UCG 224 - 1 with a UCG length 222 . The UCG length 222 may provide (NB)RS for compensation measurements. UL transmissions, including UL transmissions 216-1 and 216-2, may include multiple repetitions of the UL transmission. The length of the UL transmission may cause the UE 204 to drift in frequency. UCG enables UE 204 to recalibrate itself using (NB)RS to compensate for frequency drift.

The UE 204 can use the (NB)RS to measure 226-1 frequency and compensate its frequency and timing reference. UE 204 may continue (227) with UL transmission 216-2. The eNodeB 202 may terminate (230) the demodulation early. That is, when receiving an uplink transmission with a particular RL, eNodeB 202 may demodulate the uplink data using a smaller number of repetitions than the RL configured for UL transmissions 216-1 and/or 216-2. As used herein, demodulation may include successfully receiving UL transmissions provided via UL transmissions 216-1 and 216-2. eNodeB 202 may allocate resources for transmission by UCG 224-2. During UCG 224-1 and 224-2, the (NB)RS sent by the eNodeB can be used by the UE to perform frequency and timing compensation measurements. The eNodeB can further generate, encode and send ETI. If sent, the ETI may order the UE 204 to terminate the UL transmission. UE 204 can measure DL frequency and compensate for frequency and timing references. UE 204 may also decode (228), process and/or receive the ETI. UE 204 may terminate the UL transmission in response to receiving the ETI.

Figure 3 is a block diagram illustrating electronic device circuitry, which may be eNodeB circuitry, user equipment (UE) circuitry, network node circuitry, or some other type of circuitry, according to one embodiment. 3 shows an electronic device 300 according to various embodiments, which may be an eNodeB, UE, or some other type of electronic device; or may be incorporated into an eNodeB, UE, or some other type of electronic device ; or may otherwise be part of an eNodeB, UE, or some other type of electronic device. Specifically, the electronic device 300 may be logic and/or circuits that may be at least partially implemented in one or more of hardware, software, and/or firmware. In an embodiment, electronics logic may include radio transmit/transmitter logic (e.g., first transmitter logic 377) and receive/receiver logic (e.g., first receive logic 377) coupled to control logic 373 and/or processor 371. device logic 383). In an embodiment, 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 may be incorporated into a first device and the first receiver logic 383 may be incorporated into a second device, or the transmitter logic 377 and receiver logic 383 may be incorporated into a Any combination of control logic 373, memory 379, and/or processor 371 may be in separate devices. Electronic device 300 may be coupled to, or may include, one or more antenna elements 385 of one or more antennas. Electronic device 300 and/or components of electronic device 300 may be configured to perform operations similar to those described elsewhere in this disclosure.

In some embodiments, the electronic device 300 implements a UE, and/or an eNodeB, or a device part thereof, or the electronic device 300 is incorporated into a UE, and/or an eNodeB, or a device part thereof, or the electronic device 300 becomes a UE in other ways , and/or eNodeB, or a part of its device portion, the electronic device 300 may detect blocking of AP service. Processor 371 may be coupled to the first receiver and the first transmitter. Memory 379 may be coupled to processor 371 having control logic instructions thereon that when executed generate, encode, receive and/or detect ENRR, UCG and ETI.

In some embodiments thereof, the electronic device 300 receives data from the UE, generates data, and/or sends data to the UE to implement a downlink signal including an Extended Synchronization Signal (ESS), and the processor 371 may be coupled to the receiver and Transmitter. Memory 379 may be coupled to processor 371 having control logic 373 instructions thereon which, when executed, can generate an ESS using the root index generated from the physical cell ID.

As used herein, the term "logic" may be, may be part of, or may include: an Application Specific Integrated Circuit (ASIC), an electronic circuit, (shared, dedicated or group processor 371 and/or memory (shared, dedicated, or grouped) 379, combinational logic, and/or other suitable hardware components that provide the described functionality. In particular, the logic may be at least partially implemented in hardware, software and/or firmware, or in elements thereof. In some embodiments, electronic device logic may be implemented by one or more software modules or firmware modules, or functions associated with the logic may be implemented by one or more software modules or firmware modules.

FIG. 4 is a block diagram illustrating a method 440 for configuring the number of repetitions of DL transmissions based on ENRR, according to one embodiment. The method 440 may include allocating (442) DL resources for first DL data to be sent with the first number of repetitions, generating (444) the first DL data to be sent with the first number of repetitions, processing (446) receiving from the UE The received ENRR, and configure (448) a second repetition number of the second DL data based on the ENRR.

Method 440 may also include allocating DL resources for the second DL transmission with the second number of repetitions, and generating the second DL transmission with the second number of repetitions. The first repetition number of the first DL transmission may be smaller than the second repetition number of the second DL transmission. The first repetition number of the first DL transmission may be greater than the second repetition number of the second DL transmission.

ENRR may describe a third number of repetitions used by the UE to successfully receive the first data transmission. ENRR may be the difference between the first number of repetitions and the third number of repetitions. ENRR may be the difference between the maximum repetition number associated with the UE and the third repetition number. The ENRR may be positive based on determining the third number of repetitions is less than the first threshold, and the ENRR may be negative based on determining the third number of repetitions is greater than the second threshold.

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

Method 550 may also include generating ENRR as layer 1 feedback. Layer 1 feedback is part of UCI, where the instructions to generate ENRR include further instructions to generate ENRR as part of DL HARQ-ACK. ENRR can be generated as part of the MAC element. Method 550 may also include generating ENRR as part of the newly defined MAC element. Method 550 may also include generating ENRR as part of a MAC control element. Method 550 may also include generating ENRR as part of a previously defined MAC element.

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

Method 660 can also include including UCGs in the allocation of UL resources based on determining that the number of repetitions of the DL transmission is greater than a threshold. Method 660 can also include including the UCG in the allocation of UL resources based on the coverage level of the UE.

The UE's coverage level may be based on the number of repetitions of at least one of a Physical Random Access Channel (PRACH) and a Narrowband PRACH (NB-PRACH). The UE's coverage level may be based on the number of repetitions of DL transmissions provided by at least one of UL DCI and RAR. The UE's coverage level may be based on the number of repetitions of DL transmissions provided by DL DCI and RAR.

FIG. 7 is a block diagram illustrating a method 780 for ETI according to one embodiment. Method 780 may include processing (782) an allocation of UL resources, generating (784) UL data based on the allocation of UL resources, processing (786) RSs received during the UCG from the eNodeB, based on the allocation of UL resources The UE is configured (788) with the RS during the UCG scheduled in the UCG, processes (792) the ETI received in the UCG from the eNodeB, and terminates (794) the UL transmission based on the ETI.

Method 780 may also include processing the RS during the first UCG, configuring the UE during the first UCG, and processing the ETI in the second UCG. The length of the UCG is based on the number of DL subframes marked as valid. The number of DL subframes are marked as valid based on the UE's expectation to successfully receive the DL subframes. The length of UCG is based on DL SINR. DL SINR may be based on DL Reference Signal Received Power (RSRP).

The length of the UCG may be based on the UE's coverage level. The UE's coverage level is based on at least one of a first maximum repetition number of DL transmissions, a second repetition number of NPUSCH transmissions, a third repetition number of PRACH, a fourth repetition number of NPRACH, and a CE mode of the UE.

Figure 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 to each other as at least as shown in FIG. 8 . Any combination or subset of these components may be included in, for example, a UE device or an eNodeB device.

Application circuitry 803 may include one or more application processors. As a non-limiting example, application circuitry 803 may include one or more single-core or multi-core processors. The processor(s) may include any combination of general and special purpose processors (eg, graphics processors, application processors, etc.). The processor(s) may be operably coupled with and/or may include a memory/storage device, and may be configured to execute instructions stored in the memory/storage device to enable various applications and/or or operating system running on the system.

As a non-limiting example, baseband circuitry 805 may include one or more single-core or multi-core processors. Baseband circuitry 805 may include one or more baseband processors and/or control logic. Baseband circuitry 805 may be configured to process baseband signals received from the receive signal path of RF circuitry 807 . The baseband circuit 805 may also be configured to generate a baseband signal for the transmit signal path of the RF circuit 807 . Baseband circuitry 805 may interact with application circuitry 803 for generating and processing baseband signals and for controlling the operation of RF circuitry 807 .

As a non-limiting example, baseband circuitry 805 may include a second generation (2G) baseband processor 811A, a third generation (3G) baseband processor 811B, a fourth generation (4G) baseband processor 811C, and other existing At least one of the (one or more) other baseband processors 811D of a generation (eg, fifth generation (5G), sixth generation (6G), etc.) that is currently being developed or will be developed in the future. Baseband circuitry 805 (eg, at least one of baseband processors 811A-811D) may handle various radio control functions that enable communication via RF circuitry 807 with one or more radio networks. As non-limiting examples, radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency shifting, other functions, and combinations thereof. In some embodiments, the modulation/demodulation circuitry of 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, the encoding/decoding circuitry of baseband circuitry 805 can be programmed to perform convolution, tailbiting convolution, turbo, Viterbi, and low-density parity-check (LDPC) encoder/decoder functions, among other functions , and their combinations. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality.

In some embodiments, baseband circuitry 805 may include elements of a protocol stack. As non-limiting examples, elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocols include, for example, Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) elements. A central processing unit (CPU) 811E of the baseband circuit 805 may be programmed to run elements of a protocol stack for PHY, MAC, RLC, PDCP, and/or RRC layer signaling. In some embodiments, baseband circuitry 805 may include one or more audio digital signal processors (DSPs) 811F. Audio DSP(s) 81 IF may include elements for compression/decompression and echo cancellation. Audio DSP(s) 81 IF may also include other suitable processing elements.

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

In some embodiments, the components of the baseband circuit 805 may be suitably combined in a single chip or a single chipset, or suitably arranged on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 805 and the application circuit 803 may be implemented together, for example, on a system-on-chip (SOC).

In some embodiments, baseband circuitry 805 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 805 may support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN) ) to communicate. In some embodiments, the baseband circuit 805 is configured to support radio communication of more than one wireless protocol, and these embodiments may be referred to as multi-mode baseband circuits.

RF circuitry 807 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 807 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuitry 807 may include a receive signal path, which may include circuitry for downconverting the RF signal received from FEM circuitry 809 and providing the baseband signal to baseband circuitry 805 . RF circuitry 807 may also include a transmit signal path, which may include circuitry for upconverting the baseband signal provided by baseband circuitry 805 and providing an RF output signal to FEM circuitry 809 for transmission.

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

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

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

In some embodiments, the mixer circuit 813A of the receive signal path and the mixer circuit 813A of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion or up-conversion, respectively. frequency conversion. In some embodiments, the mixer circuit 813A of the receive signal path and the mixer circuit 813A of the transmit signal path may comprise two or more mixers and may be arranged for image rejection (e.g., Hartley image inhibition). In some embodiments, the mixer circuit 813A of the receive signal path and the mixer circuit 813A of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuit 813A of the receive signal path and the mixer circuit 813A of the transmit signal path may be configured for superheterodyne operation.

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

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

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

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

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. Depending on the desired output frequency, the frequency divider control input can be provided by the baseband circuit 805 or the application circuit 803 . In some embodiments, the divider control input (eg, N) may be determined from a lookup table based on the channel indicated by the application circuit 803 .

The synthesizer circuit 813D of the RF circuit 807 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may comprise a dual mode frequency divider (DMD), and the phase accumulator may comprise a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (eg, based on carry) to provide a fractional divide ratio. In some example embodiments, a 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 up the VCO cycle into at most Nd equal phase groupings, where Nd is the number of delay elements in the delay line. In this way, the DLL can provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 813D may be configured to generate a carrier frequency as an 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 is used in conjunction with a quadrature generator and frequency divider circuit to generate a A plurality of signals of different phases from each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuit 807 may include an IQ/polarity converter.

FEM circuitry 809 may include receive signal paths, which may include RF signals configured to manipulate received RF signals from one or more antennas 814, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 807 for circuit for further processing. FEM circuitry 809 may also include a transmit signal path, which may include circuitry configured to amplify a signal for transmission provided by RF circuitry 807 for transmission by at least one of one or more antennas 814 .

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

In some embodiments, a device may include additional elements such as memory/storage, a display, a camera, one or more sensors, input/output (I/O) interfaces, other elements, or combinations thereof.

In some embodiments, a device may be configured to perform one or more procedures, techniques and/or methods described herein, or portions thereof.

9 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments . Specifically, FIG. 9 shows a diagram of a hardware resource 900 that includes one or more processors (or processor cores) 910, one or more memory/storage devices 920, and one or more communication resources 930 , all of which are communicatively coupled via a bus 940 .

Processor 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) (e.g., 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, processor 912 and processor 914 . Memory/storage 920 may include main memory, disk storage, or any suitable combination thereof.

Communication resources 930 may include interconnection and/or network interface components or other suitable devices for communicating with one or more peripheral devices 904 and/or one or more databases 911 over network 908 . For example, communication resources 930 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, near field communication (NFC) components, components (for example, low power consumption), components, and other communication components.

Instructions 950 may include software, programs, applications, applets, apps, or other executable code for causing at least one processor 910 to perform any one or more of the methods discussed herein. Instructions 950 may reside wholly or partially within at least one processor 910 (eg, within a processor's cache memory), memory/storage device 920 , or any suitable combination thereof. Furthermore, any portion of instructions 950 may be transferred from any combination of peripheral devices 904 and/or database 911 to hardware resource 900 . Thus, memory of processor 910, memory/storage 920, peripherals 904, and database 911 are examples of computer-readable and machine-readable media.

example embodiment

Example 1 is an apparatus of a user equipment (UE). An Excess Repeat Report (ENRR) is generated by a device that includes electronic memory for storing downlink (DL) data. An excess repetition report (ENRR) is generated by an apparatus comprising one or more baseband processors designed to handle allocation of DL resources provided by an evolved Node B (eNodeB) and to decode DL data based on the allocation of DL resources. An excess repetition report (ENRR) is generated by a device comprising one or more baseband processors designed to determine the number of repetitions of data transmissions used to decode DL data and based on the number of repetitions of data transmissions used to decode DL data Generate Excess Repetition Report (ENRR).

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

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

Example 4 is the apparatus of example 3, wherein the one or more processors configured to generate the ENRR are also configured to generate the ENRR as layer 1 feedback.

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

Example 6 is the apparatus of example 1, wherein the one or more processors configured to generate the ENRR are also configured to generate the ENRR as part of a DL hybrid automatic repeat request acknowledgment (HARQ-ACK).

Example 7 is the apparatus of example 1, wherein the one or more processors configured to generate the ENRR are also configured to generate the ENRR as part of a medium access control (MAC) element.

Example 8 is the apparatus of example 7, wherein the one or more processors configured to generate the ENRR as part of the MAC control element are also configured to generate the ENRR as part of the newly defined MAC element.

Example 9 is the apparatus of example 7, wherein the one or more processors configured to generate ENRR as part of a MAC control element are also configured to generate ENRR as part of a previously defined MAC element.

Example 10 is an evolved Node B (eNodeB) device. The device is designed for various repetitions of data transmission by the eNodeB, the device comprising an electronic memory for storing excess repetition reports (ENRR). means designed for various repetitions of data transmission by the eNodeB, the apparatus comprising one or more baseband processors designed to allocate downlink (DL) resources for first DL data to be sent with a first number of repetitions, And first DL data to be transmitted with the first repetition number is generated. The apparatus is designed for various iterations of data transmission by the eNodeB, the apparatus includes one or more baseband processors, is designed to process the ENRR received from the user equipment (UE), and based on the ENRR to design the first DL data Two repetitions.

Example 11 is the apparatus of example 10, wherein the one or more baseband processors are further configured to allocate DL resources for the second DL data to be sent with the second number of repetitions. And, second DL data to be transmitted with a second repetition number is generated.

Example 12 is the apparatus of example 10, wherein the first number of repetitions of the first DL data is less than the second number of repetitions of the second DL data.

Example 13 is the apparatus of example 10, wherein the first repetition number of the first DL data is greater than the second repetition number of the second DL data.

Example 14 is the apparatus of example 10, wherein the ENRR describes a third number of repetitions used by the UE to successfully receive the first data.

Example 15 is the apparatus of example 14, wherein ENRR is the difference between the first number of repetitions and the third number of repetitions.

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

Example 17 is the apparatus of example 14, wherein the ENRR is positive based on determining the third number of repetitions is less than the first threshold, and the ENRR is negative based on determining the third number of repetitions is greater than the second threshold.

Example 18 is an evolved Node B (eNodeB) device. An apparatus implements an uplink backoff gap (UCG) and generates an early termination indication (ETI), the apparatus comprising electronic memory for storing a reference signal (RS) and the ETI. The apparatus has one or more baseband processing units designed to allocate UL resources for uplink (UL) data, wherein the allocation includes a UCG, and to process the UL data from a user equipment (UE). The apparatus has one or more baseband processing units designed to implement the first UCG by making the RS available to the UE for compensation measurements and to process additional UL data from the UE. The device has one or more baseband processing units and is designed to implement the second UCG by further configuring the one or more baseband processing units to make the RS available to the UE and generate an ETI to terminate transmission of UL data.

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

Example 20 is the apparatus of example 18, wherein the one or more processing units are further configured to include the UCG in the allocation of UC resources based on the coverage level of the UE.

Example 21 is the apparatus of example 20, wherein the coverage level of the UE is based on a repetition number of at least one of a Physical Random Access Channel (PRACH) and a Narrowband PRACH (NPRACH).

Example 22 is the apparatus of example 20, wherein the UE's coverage level is based on a repetition number of DL transmissions provided by at least one of UL Downlink Control Information (DCI) and Random Access Response (RAR).

Example 23 is the apparatus of example 20, wherein the UE's coverage level is based on a repetition number of DL transmissions provided by DL DCI and RAR.

Example 24 is a computer readable storage medium. A computer-readable storage medium has stored thereon instructions that, when implemented by a computing device, cause the computing device to process allocation of uplink (UL) resources at a user equipment (UE) and generate UL data based on the allocation of UL resources . A computer-readable storage medium has stored thereon instructions that, when implemented by a computing device, cause the computing device to process a reference signal (RS) received during an uplink backoff gap (UCG) from an evolved Node B (eNodeB) And the UE is designed during the UCG based on the RS, wherein the UCG is scheduled in the allocation of UL resources. A computer-readable storage medium has stored thereon instructions that, when implemented by a computing device, cause the computing device to process an early termination indicator (ETI) received in the UCG from an eNodeB and terminate UL transmissions based on the ETI.

Example 25 is the computer-readable storage medium of example 24, wherein the instructions for processing the RS during the UCG include further instructions for processing the RS during the first UCG, and the instructions for designing the UE during the UCG include for The further instructions of the UE are designed during the first UCG, and the instructions for processing the ETI in the UCG include further instructions for processing the ETI in the second UCG.

Example 26 is the computer-readable storage medium of example 24, wherein the length of the UCG is based on a number of downlink (DL) subframes marked valid.

Example 27 is the computer-readable storage medium of example 24, wherein the number of DL subframes is marked as valid based on the UE's expectation to successfully receive the DL subframes.

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

Example 29 is the computer-readable storage medium of example 28, wherein the DL SINR is based on DL Reference Signal Received Power (RSRP).

Example 30 is the computer-readable storage medium of example 24, wherein the UE's coverage level is based on at least one of: a first maximum repetition number of DL transmissions; a second repetition number of narrowband physical uplink shared channel (NB-PUSCH) transmissions ; a third repetition number of the Physical Random Access Channel (PRACH); a fourth repetition number of the Narrowband PRACH (NB-PRACH); and a Coverage Enhancement (CE) mode of the UE.

Example 31 is a method for generating an excess repetition report (ENRR). The method includes processing allocation of downlink (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 repetition number of data transmissions used to decode DL data, and generating an excess repetition report (ENRR) based on the number of repetitions of data transmissions used to decode DL data.

Example 32 is the method of example 31, wherein the allocation of DL resources is sent over a machine physical downlink control channel (M-PDCCH) or a narrowband physical downlink control channel (NB-PDCCH).

Example 33 is the method of example 31, wherein generating the ENRR further comprises generating the ENRR in a narrowband physical uplink shared channel (NB-PUSCH).

Example 34 is the method of example 33, wherein generating the ENRR further comprises generating the ENRR as Layer 1 feedback.

Example 35 is the method of example 34, wherein the layer 1 feedback is part of uplink control information (UCI).

Example 36 is the method of example 31, wherein generating the ENRR further comprises generating the ENRR as part of a DL Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

Example 37 is the method of example 31, wherein generating the ENRR further comprises generating the ENRR as part of a medium access control (MAC) element.

Example 38 is the method of example 37, wherein generating the ENRR as part of the MAC control element further comprises generating the ENRR as part of the newly defined MAC element.

Example 39 is the method of example 37, wherein generating the ENRR as part of the MAC control element further comprises generating the ENRR as part of a previously defined MAC element.

Example 40 is a method for configuring various iterations of data transmission of an eNodeB. The method includes allocating downlink (DL) resources for first DL data to be transmitted with a first number of repetitions, and generating the first DL data to be transmitted with the first number of repetitions. The method includes processing an excess repetition report (ENRR) received from a user equipment (UE), and configuring a second repetition amount of the second DL data based on the ENRR.

Example 41 is the method of example 40, further comprising allocating DL resources for the second DL data to be sent with the second number of repetitions and generating the second DL data to be sent with the second number of repetitions.

Example 42 is the method of example 40, wherein the first number of repetitions of the first DL data is less than the second number of repetitions of the second DL data.

Example 43 is the method of example 40, wherein the first number of repetitions of the first DL data is greater than the second number of repetitions of the second DL data.

Example 44 is the method of example 40, wherein the ENRR describes a third number of repetitions used by the UE to successfully receive the first data.

Example 45 is the method of example 44, wherein ENRR is the difference between the first number of repetitions and the third number of repetitions.

Example 46 is the method of example 44, wherein ENRR is a difference between a maximum repetition number associated with the UE and a third repetition number.

Example 47 is the method of example 44, wherein the ENRR is positive based on determining the third number of repetitions is less than the first threshold, and the ENRR is negative based on determining the third number of repetitions is greater than the second threshold.

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

Example 49 is the method of example 48, further comprising including the UCG in the allocation of UL resources based on determining that the number of repetitions of the downlink (DL) transmission is greater than a threshold.

Example 50 is the method of example 48, further comprising including the UCG in the allocation of UL resources based on the coverage level of the UE.

Example 51 is the method of example 50, wherein the UE's coverage level is based on a repetition number of at least one of a Physical Random Access Channel (PRACH) and a Narrowband PRACH (NPRACH).

Example 52 is the method of example 50, wherein the UE's coverage level is based on a repetition number of DL transmissions provided by at least one of UL Downlink Control Information (DCI) and Random Access Response (RAR).

Example 53 is the method of example 50, wherein the UE's coverage level is based on a repetition number of DL transmissions provided by DL DCI and RAR.

Example 54 is one way. The method includes processing, at a user equipment (UE), 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 backoff gap (UCG), and configuring the UE during the UCG based on the RS, wherein the UCG is in allocation of UL resources Scheduling. The method includes processing an Early Termination Indicator (ETI) received in the UCG from the eNodeB, and terminating the UL transmission based on the ETI.

Example 55 is the method of example 54, wherein processing the RS during the UCG further includes processing the RS during the first UCG, and configuring the UE during the UCG further includes configuring the UE during the first UCG, and further processing the ETI in the UCG further includes ETI is processed in the second UCG.

Example 56 is the method of example 54, wherein the length of the UCG is based on the number of downlink (DL) subframes marked valid.

Example 57 is the method of example 54, wherein the number of DL subframes is marked as valid based on the UE's expectation to successfully receive the DL subframes.

Example 58 is the method of example 54, wherein the length of the UCG is based on a DL signal-to-noise ratio (SINR).

Example 59 is the method of example 58, wherein the DL SINR is based on DL Reference Signal Received Power (RSRP).

Example 60 is the method of example 54, wherein the UE's coverage level is based on at least one of: a first maximum repetition number of DL transmissions; a second repetition number of narrowband physical uplink shared channel (NB-PUSCH) transmissions; physical random access The third repetition number of the incoming channel (PRACH); the fourth repetition number of the narrowband PRACH (NB-PRACH); and the coverage enhancement (CE) mode of the UE.

Example 61 is at least one computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions being configured to, when executed, implement the method of any one of Examples 31-60.

Example 62 is an apparatus comprising means for performing the method of any of Examples 31-60.

Example 63 is a method for performing the method of any one of Examples 31-60.

The various technologies, or aspects or portions thereof, may take the form of program code (i.e., instructions) embodied on a tangible medium (e.g., floppy disk, CD-ROM, hard drive, non-transitory computer-readable storage medium , or any other machine-readable storage medium), where when the program code is loaded and executed by a machine (eg, a computer), the machine becomes a means for implementing 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 non-volatile memory and/or storage elements), at least one input device , and at least one output device. Volatile and nonvolatile memory and/or storage elements can be RAM, EPROM, flash drives, optical drives, magnetic hard drives, or another medium for storing electronic data. The eNodeB (or other base station) and UE (or other mobile station) may also include transceiver components, counter components, processing components, and/or clock or timer components. One or more programs that may implement or utilize the various techniques described herein may use application programming interfaces (APIs), reusable controls, and the like. Such programs can be implemented in a high-level procedural-oriented or object-oriented programming language to communicate with the computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language and combined with a hardware implementation.

It should be understood that many functional units described in this specification may be implemented as one or more components, and component is a term used to further 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 (eg, logic chips), transistors, or other discrete components. Components may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and so forth.

Components may also be implemented in software executed by various types of processors. An identified component of executable code may, for example, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. However, the executables that identify a component need not be physically located together, but may include distinct instructions stored in different locations that, when logically joined together, constitute the component and achieve the purpose specified by the component.

Indeed, an element of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, different programs, and several storage devices. Similarly, operational data may be identified or illustrated herein as being within components, and may be embodied in any suitable form or organized within any suitable type of data structure. Operational Data may be collected as a single data set or may be distributed across different locations (including across different storage devices), and may exist at least in part only as electronic signals on a system or network. Components can be passive or active, including agents operable to perform desired functions.

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.

A plurality of items, structural elements, constituent elements, and/or materials used herein may be presented in a common list for convenience. However, these lists should be considered as each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be regarded as de facto equivalent to any other member of the same list solely based on occurrence in a common group without indications to the contrary. Furthermore, various embodiments and examples and substitutions for various components thereof may be referred to herein. It should be understood that such embodiments, examples, and alternatives are not considered to be virtually equivalent to each other, but should be considered as separate and independent representations.

While 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 its principles. It should be noted that there are many alternative ways of implementing the processes and apparatus described herein. Accordingly, the embodiments herein are to be considered as illustrative rather than restrictive, and these embodiments are not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims (30)

1. the device of user equipment (UE) of the one kind for generating excess duplicate reports (ENRR), including：

Electronic memory, for storing downlink (DL) data；And

One or more baseband processor, are configured as：

The distribution to DL resources provided by evolution node B (eNodeB) is provided；

The DL data are decoded based on the distribution to DL resources；

Determine the number of iterations of the data transmission for decoding the DL data；And

Excess duplicate reports (ENRR) are generated based on the number of iterations of the data transmission for decoding the DL data.

2. the apparatus according to claim 1, wherein the distribution to DL resources is to control to believe by machine physical downlink What road (M-PDCCH) or narrowband physical downlink control channel (NB-PDCCH) were sent.

3. the apparatus according to claim 1, wherein be configurable to generate one or more of processors of the ENRR It is additionally configured to generate the ENRR in narrowband physical uplink shared channel (NB-PUSCH).

4. device according to claim 3, wherein be configurable to generate one or more of processors of the ENRR It is additionally configured to generate the ENRR as the feedback of layer 1.

5. device according to claim 4, wherein the feedback of the layer 1 is one of uplink control information (UCI) Point.

6. according to the device described in claim 1,2,3,4 or 5, wherein be configurable to generate the one or more of the ENRR Processor is additionally configured to generate the part that the ENRR confirms (HARQ-ACK) as DL hybrid automatic repeat-requests.

7. according to the device described in claim 1,2,3,4 or 5, wherein be configurable to generate the one or more of the ENRR Processor is additionally configured to generate a parts of the ENRR as medium access control (MAC) element.

8. device according to claim 7, wherein be configurable to generate one of the ENRR as MAC controlling elements The one or more processors divided are additionally configured to generate a parts of the ENRR as the MAC elements newly defined.

9. device according to claim 7, wherein be configurable to generate one of the ENRR as MAC controlling elements The one or more processors divided are additionally configured to generate a parts of the ENRR as the MAC elements of previous definition.

10. the device of the eNodeB of multiple repetitions of data transmission of the one kind for configuring evolution node B (eNodeB), packet It includes：

Electronic memory, for storing excess duplicate reports (ENRR)；And

One or more baseband processor, are configured as：

Downlink (DL) resource of distribution for the first DL data sent with the first number of iterations；

Generate the first DL data sent with first number of iterations；

Handle the ENRR received from user equipment (UE)；And

The second number of iterations of the 2nd DL data is configured based on the ENRR.

11. device according to claim 10, wherein one or more of baseband processor are additionally configured to：

DL resource of the distribution for the 2nd DL data sent with second number of iterations；And

Generate the 2nd DL data sent with second number of iterations.

12. the device according to claim 10 or 11, wherein first number of iterations of the first DL data is less than Second number of iterations of the 2nd DL data.

13. the device according to claim 10 or 11, wherein first number of iterations of the first DL data is more than Second number of iterations of the 2nd DL data.

14. the device according to claim 10 or 11, wherein the ENRR is described by the UE for being properly received the The third repeating quantity of one data.

15. device according to claim 14, wherein the ENRR is first number of iterations and the third repeating Difference between quantity.

16. device according to claim 14, wherein the ENRR be maximum number of iterations associated with the UE with Difference between the third repeating quantity.

17. device according to claim 14, wherein be less than first threshold, institute based on the determining the third repeating quantity It is positive to state ENRR；And based on the third repeating quantity is determined more than second threshold, the ENRR is negative.

18. a kind of evolution node B for realizing uplink compensation gap (UCG) and generation termination instruction (ETI) in advance (eNodeB) device, including：

Electronic memory, for storing reference signal (RS) and the ETI；And

One or more baseband processing units, are configured as：

UL resource of the distribution for uplink (UL) data, wherein the distribution includes

The UCG；

The UL data of the processing from user equipment (UE)；

By making the RS can be used for the UE the first UCG is realized to compensate measurement；

Handle the additional UL data from the UE；And

The 2nd UCG is realized by further configuring one or more of following operations of baseband processing units execution：

The RS is set to can be used for the UE；And

The ETI is generated to terminate the transmission of the UL data.

19. device according to claim 18, wherein one or more of processing units are additionally configured to based on determination The number of iterations of downlink (DL) transmission is more than threshold value, is including the UCG to the distribution of UL resources.

20. device according to claim 18, wherein one or more of processing units are additionally configured to based on described The covering of UE is horizontal, is including the UCG to the distribution of UL resources.

21. device according to claim 20, wherein the covering level of the UE is based on Physical Random Access Channel (PRACH) and the number of iterations of at least one of narrowband PRACH (NPRACH).

22. the device according to claim 20 or 21, wherein the covering level of the UE is based on being controlled by UL downlinks The number of iterations for the DL transmission that at least one of information (DCI) and random access response (RAR) provide.

23. the device according to claim 20 or 21, wherein the covering level of the UE is based on being carried by DL DCI and RAR The number of iterations of the DL transmission of confession.

24. a kind of computer readable storage medium is stored thereon with instruction, described instruction by computing device when being realized so that The computing device executes following operation：

Distribution of the processing to uplink (UL) resource at user equipment (UE)；

UL data are generated based on the distribution to UL resources；

The reference signal that uplink compensation gap (UCG) during receives of the processing from evolution node B (eNodeB) (RS)；

Based on the RS, the UE is configured during the UCG, wherein the UCG be described to the distribution of UL resources in quilt Scheduling；

Handle the indicator of termination in advance (ETI) received in the UCG from the eNodeB；And

UL transmission is terminated based on the ETI.

25. computer readable storage medium according to claim 24, wherein

Instruction for the RS during handling the UCG further includes the instruction for handling the RS during the first UCG；

Instruction for configuring the UE during the UCG further includes the instruction for configuring the UE during the first UCG； And

Instruction for handling the ETI in the UCG further includes the instruction for handling the ETI in the 2nd UCG.

26. computer readable storage medium according to claim 24, wherein the length of the UCG is based on being marked as The quantity of effective downlink (DL) subframe.

27. computer readable storage medium according to claim 24, wherein be properly received DL subframe based on the UE It is expected that by the DL subframe of the quantity labeled as effective.

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

29. computer readable storage medium according to claim 28, wherein the DL SINR are based on DL reference signals Receive power (RSRP).

30. according to the computer readable storage medium described in claim 24,25,26,27,28 or 29, wherein the UE's covers Lid is horizontal to be based at least one of the following：

First maximum number of iterations of DL transmission；

Second number of iterations of narrowband Physical Uplink Shared Channel (NB-PUSCH) transmission；

The third repeating quantity of Physical Random Access Channel (PRACH)；

The 4th number of iterations of narrowband PRACH (NB-PRACH)；And

Coverage enhancement (CE) pattern of the UE.