Scheduling for Improved Throughput in Extended Machine-Type Communication

Abstract

Methods, systems, and devices for wireless communications are described. A frame, a scheduling instance, a scheduling period, etc. may include a set of downlink subframes and a set of uplink subframes. At least one control message transmitted in the downlink subframe may schedule a set of data messages in the downlink subframes of the frame. The downlink subframe may also include data messages scheduled by control messages of a previous frame. Furthermore, feedback timing for data messages of a frame may be determined based on corresponding control messages (e.g., from the current frame and the previous frame). Feedback responses corresponding to data messages may be bundled and transmitted in the set of uplink subframes. Using this cross-frame scheduling technique, frame resources may be efficiently utilized.

Description

Technical Field

[0001] Cross-reference This patent application claims the benefit of PCT Application No. PCT / CN2019 / 088328, filed on May 24, 2019 and assigned to the assignee of this application, entitled "SCHEDULING FOR IMPROVED THROUGHPUT IN ENHANCED MACHINE-TYPE COMMUNICATION" by ZAKI et al.

[0002] In general, the following relates to wireless communication, and more particularly, to scheduling for feedback responses.

Background Art

[0003] Wireless communication systems have been widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-connection systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems sometimes referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-connection communication system may include several base stations or network access nodes that each simultaneously support communication for a plurality of communication devices, sometimes referred to as User Equipment (UE).

[0004] A wireless communication system may schedule communication resources according to a frame. Some sub-frames of the frame may be allocated for downlink communication, and other sub-frames of the frame may be allocated for uplink communication. In some cases, data messages may be scheduled in one or more downlink frames by a downlink control channel in the frame. Feedback responses (e.g., acknowledgment responses (ACK) and negative acknowledgment responses (NAK)) for data messages in the frame may be allocated to uplink sub-frames in the frame. Due to scheduling limitations, some downlink sub-frames in the frame may not contain downlink data messages. Thus, some potential resources may be wasted or not utilized for communication, which may result in communication inefficiency.

Summary of the Invention

Means for Solving the Problems

[0005] The techniques described relate to improved methods, systems, devices, and apparatuses that support scheduling for feedback responses. Generally, the techniques described involve receiving at least one control message within a set of downlink sub-frames in a current scheduling instance (e.g., a frame), and receiving a plurality of data messages within the set of downlink sub-frames in the current scheduling instance. In some cases, some of the data messages are scheduled by a control message, and other data messages of the scheduling instance are scheduled by one or more control messages of a previous scheduling instance. Feedback timing for the data messages may be determined based on the control message, and one or more feedback responses may be transmitted during uplink sub-frames of the current scheduling instance.

[0006] To support the described scheduling, various scheduling techniques may be implemented. In some cases, a delayed scheduling technique may be used by a control message to schedule a data message in a next scheduling instance (e.g., after one or more bundled feedback responses in a current scheduling instance). Additionally, a modification of the feedback timing indication may be used to support the addition of data messages in a scheduling instance. The technique may also include alternating the feedback process between adjacent scheduling instances, where the control message in the current scheduling instance and the feedback process associated with the control message in a previous scheduling instance may be processed simultaneously. In some cases, downlink control information (DCI) may be used to indicate the feedback process, feedback timing, and scheduling for one or more data messages in a scheduling instance.

[0007] A method of wireless communication in a UE is described. The method includes receiving at least one control message within a set of downlink subframes in a current scheduling instance, and receiving a set of data messages within the set of downlink subframes in the current scheduling instance, wherein a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and wherein a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance; determining a feedback timing for each of the set of data messages, wherein the feedback timing for the first subset of the set of data messages is based on at least one control message, and wherein the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance; and transmitting one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0008] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions cause the apparatus to receive at least one control message within a set of downlink subframes in a current scheduling instance, receive a set of data messages within the set of downlink subframes in the current scheduling instance, wherein a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and wherein a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance, determine a feedback timing for each of the set of data messages, wherein the feedback timing for the first subset of the set of data messages is based on at least one control message, and wherein the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance, and transmit one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages, and may be executable by a processor.

[0009] Another apparatus for wireless communication in a UE is described. The apparatus receives at least one control message within a set of downlink subframes in a current scheduling instance, and receives a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance, and determines feedback timing for each of the set of data messages, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance, and may include means for transmitting one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0010] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code includes receiving at least one control message within a set of downlink subframes in a current scheduling instance, and receiving a set of data messages within the set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance, and determining feedback timing for each of the set of data messages, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance, and transmitting one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages, and may include instructions executable by a processor for performing the above.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving a set of data messages may include operations, features, means, or instructions for receiving a second subset of the set of data messages after a downlink shared channel scheduling delay including subframes for transmission of one or more bundled additional feedback responses during a previous scheduling instance.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving at least one control message may cause one or more additional data messages to be scheduled in a next scheduling instance after a downlink shared channel scheduling delay that causes one or more bundled feedback responses to be transmitted during an uplink subframe in a current scheduling instance, and may include operations, features, means, or instructions for receiving at least one control message to schedule one or more additional data messages.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for processing simultaneous HARQ processes related to at least one control message received within a set of downlink subframes of a current scheduling instance and one or more control messages received in a previous scheduling instance.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying a HARQ identifier (ID) field in a first control message of the at least one control message and comparing a value of the HARQ ID field included in the first control message with a HARQ ID field threshold.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a value of the HARQ ID field in the first control message may be greater than a HARQ ID field threshold and determining a downlink shared channel scheduling delay associated with the first control message based on a HARQ ACK delay field in the first control message.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that the value of the HARQ ID field in a first control message may be greater than a HARQ ID field threshold value and determining a HARQ process ID associated with the first control message based on the HARQ ACK delay field in the first control message.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that the value of the HARQ ID field in a first control message may be greater than a HARQ ID field threshold value and determining a feedback delay associated with the first control message based on the HARQ ID field.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining a downlink shared channel scheduling delay associated with a first control message, a HARQ process ID associated with the first control message, and a feedback delay associated with the first control message based on the value of the HARQ ID field being less than or equal to a HARQ ID field threshold value, where the downlink shared channel scheduling delay may be the smaller of two available downlink shared channel scheduling delay values, the HARQ process ID may be equal to the value of the HARQ ID field, and the feedback delay may be indicated by the HARQ ACK delay field in the first control message.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, two available downlink channel scheduling delay values include two downlink subframes and seven downlink subframes, where the determined downlink shared channel scheduling delay may be two downlink subframes based on the value of the HARQ ID field being less than or equal to the HARQ ID field threshold.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying an extended scheduling field in a first control message of at least one control message and determining a downlink shared channel scheduling delay associated with the first control message, a HARQ process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message based on the value of the extended scheduling field.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying a HARQ process identifier (ID) associated with each of one or more control messages received in a previous scheduling instance and identifying a HARQ process ID associated with at least one control message of a current scheduling instance, where the HARQ process ID associated with one or more control messages received in a previous scheduling instance may be different from the HARQ process ID associated with at least one control message of a current scheduling instance.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving a set of data messages within a set of downlink subframes in a current scheduling instance may include operations, features, means, or instructions for receiving more than 10 data messages within the set of downlink subframes in the current scheduling instance.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving a set of data messages may include operations, features, means, or instructions for receiving a second subset of the set of data messages after a downlink shared channel scheduling delay of 7 subframes.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining feedback timing for each of a set of data messages may include operations, features, means, or instructions for determining a feedback delay for one of the set of data messages, which is 12 subframes or 13 subframes.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving each of a set of data messages within each of at least 11 downlink subframes including the set of downlink subframes.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving at least one control message may include operations, features, means, or instructions for receiving a first control message of the at least one control message, and the first control message schedules a plurality of data messages.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a plurality of data messages scheduled by a first control message exceed a threshold number of data messages, and identifying a scheduling gap between a first portion of the plurality of data messages that may be less than or equal to the threshold number and a second portion of the plurality of data messages that exceed the threshold number, where the scheduling gap facilitates reception of the second portion of the plurality of data messages in a next scheduling instance subsequent to the current scheduling instance.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the threshold number of data messages may be 10.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a set of data messages within a set of downlink subframes in a current scheduling instance, where each downlink subframe of the set of downlink subframes includes a data message of the set of data messages.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the current scheduling instance may be scheduled for enhanced machine type communication (eMTC).

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying a set of HARQ process identifiers (IDs) corresponding to a set of data messages, where the set of HARQ process IDs includes at least 12 HARQ process IDs.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for overbooking a subset of a set of HARQ process identifiers.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for storing each of a set of HARQ process identifiers.

[0034] A method of wireless communication in a base station is described. The method includes transmitting at least one control message within a set of downlink subframes in a current scheduling instance, and transmitting a set of data messages within the set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and receiving one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0035] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions cause the apparatus to transmit at least one control message within a set of downlink subframes in a current scheduling instance, and to transmit a set of data messages within the set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and to receive one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages, which may be executable by the processor.

[0036] Another apparatus for wireless communication at a base station is described. The apparatus transmits at least one control message within a set of downlink subframes in a current scheduling instance and transmits a set of data messages within the set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and includes means for receiving one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0037] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code includes transmitting at least one control message within a set of downlink subframes in a current scheduling instance, and transmitting a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where feedback timing for the first subset of the set of data messages is based on at least one control message, and where feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and receiving one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages, and may include instructions executable by a processor for performing the above.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a set of data messages may include operations, features, means, or instructions for transmitting a second subset of the set of data messages after a downlink shared channel scheduling delay including subframes for receiving one or more bundled additional feedback responses during one or more previous scheduling instances.

[0039] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting at least one control message may include operations, features, means, or instructions for scheduling one or more additional data messages in a next scheduling instance after receiving one or more bundled feedback responses during an uplink subframe in a current scheduling instance, where the scheduling of the one or more additional data messages is caused by a downlink shared channel scheduling delay.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting at least one control message may include operations, features, means, or instructions for transmitting a hybrid automatic repeat request (HARQ) identifier (ID) field within a first control message of the at least one control message.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a value of a HARQ ID field that is greater than a HARQ ID field threshold and using a HARQ acknowledgement (ACK) delay field included in the first control message to indicate a downlink shared channel scheduling delay associated with the first control message, where the indicating may be based on the value of the HARQ ID field in the first control message being greater than the HARQ ID field threshold.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a value of a HARQ ID field that is greater than a HARQ ID field threshold and using a HARQ acknowledgment (ACK) delay field in a first control message to indicate a HARQ process ID associated with the first control message, where the indication may be based on the value of the HARQ ID field in the first control message being greater than the HARQ ID field threshold.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a value of a HARQ ID field that is greater than a HARQ ID field threshold and, based on the HARQ ID field, indicating a feedback delay associated with a first control message, where the indication may be based on the HARQ ID field in the first control message being greater than the HARQ ID field threshold.

[0044] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a value of a HARQ ID field that is less than or equal to a HARQ ID field threshold and, based on the value of the HARQ ID field being less than or equal to the HARQ ID field threshold, indicating a downlink shared channel scheduling delay associated with a first control message, a HARQ process ID associated with the first control message, and a feedback delay associated with the first control message, where the downlink shared channel scheduling delay may be the lesser of two available downlink shared channel scheduling delay values, the HARQ process ID may be equal to the value of the HARQ ID field, and the feedback delay may be indicated by a HARQ acknowledgment (ACK) delay field in the first control message.

[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, two available downlink channel scheduling delay values include two downlink subframes and seven downlink subframes, where the determined downlink shared channel scheduling delay may be two downlink subframes based on the value of the HARQ ID field being less than or equal to the HARQ ID field threshold.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting at least one control message may include transmitting an extended scheduling field in a first control message of the at least one control message, and based on the value of the extended scheduling field, operations, features, means, or instructions for indicating a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message.

[0047] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for indicating a HARQ process identifier (ID) associated with at least one of one or more control messages transmitted in a previous scheduling instance and indicating a HARQ process ID for a hybrid automatic repeat request (HARQ) associated with at least one control message of a current scheduling instance, where the HARQ process ID associated with at least one of one or more control messages transmitted in a previous scheduling instance may be different from the HARQ process ID associated with at least one control message of the current scheduling instance.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a set of data messages within a set of downlink subframes in a current scheduling instance may include operations, features, means, or instructions for transmitting more than 10 data messages within a set of downlink subframes in the current scheduling instance.

[0049] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a set of data messages may include operations, features, means, or instructions for transmitting a second subset of the set of data messages after a downlink shared channel scheduling delay of 7 subframes.

[0050] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for indicating a feedback delay for one of the sets of data messages of 12 subframes or 13 subframes.

[0051] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a set of data messages may include operations, features, means, or instructions for transmitting each of the set of data messages within each of at least 11 downlink subframes including the set of downlink subframes.

[0052] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting at least one control message may include operations, features, means, or instructions for transmitting a first control message of the at least one control message, the first control message scheduling a plurality of data messages.

[0053] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a first control message may include operations, features, means, or instructions for determining that a plurality of data messages scheduled by the first control message exceeds a threshold number of data messages, and identifying a scheduling gap between a first portion of the plurality of data messages that may be less than or equal to the threshold number and a second portion of the plurality of data messages that exceeds the threshold number, where the scheduling gap facilitates transmission of the second portion of the plurality of data messages in a next scheduling instance subsequent to the current scheduling instance.

[0054] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the threshold number of data messages may be 10.

[0055] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a set of data messages may include operations, features, means, or instructions for transmitting the set of data messages within a set of downlink subframes in a current scheduling instance, where each downlink subframe of the set of downlink subframes includes a data message of the set of data messages.

[0056] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the current scheduling instance may be scheduled for enhanced machine type communication (eMTC). BRIEF DESCRIPTION OF THE DRAWINGS

[0057]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4A

Figure 4B

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

DETAILED DESCRIPTION OF THE INVENTION

[0058] A wireless communication system may schedule communication resources according to a frame, a scheduling period, or a scheduling instance, which may correspond to a set of subframes. A scheduling instance (e.g., a frame) may include a set of subframes allocated for downlink communication and a set of subframes for uplink communication. A downlink subframe may include resources allocated for control information and scheduling information, as well as resources allocated for data. In some cases, data messages may be scheduled within one or more downlink frames by a downlink control channel in a scheduling instance. Feedback responses (e.g., an acknowledgement response (ACK) and a negative acknowledgement response (NAK)) for data messages in a frame may be allocated to an uplink subframe in the current scheduling instance or in the next scheduling instance. The implementations and techniques described herein may be utilized to increase the utilization of resources in a scheduling instance and thus to increase the communication efficiency in a wireless communication system.

[0059] In some cases, a scheduling instance may include a set of downlink subframes and a set of uplink subframes. At least one control message transmitted in a downlink subframe may schedule a set of data messages in the downlink subframes of the scheduling instance. The downlink subframe may also include data messages scheduled by control messages of a previous scheduling instance. Further, the feedback timing for data messages of a scheduling instance may be determined based on corresponding control messages (e.g., from the current scheduling instance and a previous scheduling instance). The feedback response corresponding to the data message may be bundled and transmitted in a set of uplink subframes. Using this cross-frame scheduling technique, the resources of a scheduling instance can be utilized efficiently.

[0060] To support efficient utilization of scheduling instances, extended scheduling delays, hybrid automatic repeat request (HARQ) process alternation, and extended feedback timing delays may be implemented. In some cases, an extended scheduling delay may be used by a control message in the current scheduling instance to schedule data resources in the next scheduling instance after transmission of a bundled feedback response for a data message in the current frame. HARQ process alternation techniques may be used to simultaneously process HARQ processes associated with data scheduled by a previous scheduling instance and data scheduled by the current scheduling instance. An extended feedback timing delay may be used to transmit feedback (ACK / NAK) for additional data messages in a scheduling instance. This technique may be implemented based on a downlink control information (DCI) field value, or a modification of the DCI field (e.g., an increased DCI payload).

[0061] Aspects of the present disclosure may be described with reference to scheduling instances, but it should be understood that the features described may be implemented with respect to frames, scheduling periods, scheduling patterns, and the like. For example, a set of downlink subframes may span multiple "frames", and thus, this feature may be implemented with respect to a scheduling instance. Thus, since a set of downlink subframes or uplink subframes may span multiple frames, the use of the term "frame" should not be construed to represent one set of subframes having a downlink set of subframes and an uplink set of subframes. Frames, scheduling instances, scheduling patterns, etc. may correspond to any set of subframes.

[0062] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further described with respect to another wireless communication system, a scheduling format indicating data scheduling and HARQ scheduling, a DCI table for scheduling, an exemplary frame pattern, and a process flow diagram. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts regarding scheduling for feedback responses.

[0063] FIG. 1 shows an example of a wireless communication system 100 that supports scheduling for feedback responses according to aspects of the present disclosure. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support extended broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices.

[0064] Base station 105 may wirelessly communicate with UE 115 via one or more base station antennas. The base station 105 described in this specification may include a transceiver base station, a radio base station, an access point, a wireless transceiver, a Node B, an eNode B (eNB), a next-generation Node B or a giga Node B (any of which may sometimes be referred to as a gNB), a home Node B, a home eNode B, or some other suitable term, or may be so referred to by those skilled in the art. The wireless communication system 100 may include different types of base stations 105 (e.g., macro base stations or small cell base stations). The UE 115 described in this specification may be able to communicate with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0065] Each base station 105 may be associated with a specific geographic coverage area 110 in which communication with various UEs 115 is supported. Each base station 105 may provide communication coverage to its respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105 or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may sometimes be referred to as forward link transmissions, and uplink transmissions may sometimes be referred to as reverse link transmissions.

[0066] The geographical coverage area 110 for the base station 105 may be divided into sectors that form a part of the geographical coverage area 110, and each sector may be associated with a cell. For example, each base station 105 may provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, the base station 105 may be movable and thus may provide a communication coverage area for a moving geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies may overlap, and the overlapping geographical coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro network or an NR network in which different types of base stations 105 provide coverage for various geographical coverage areas 110.

[0067] The term "cell" refers to a logical communication entity used for communication with a base station 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that provide access for different types of devices. In some cases, the term "cell" may refer to a part of the geographical coverage area 110 (e.g., a sector) over which the logical entity operates.

[0068] UE115 may be distributed throughout the wireless communication system 100, and each UE115 may be fixed or mobile. UE115 may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client. UE115 may be a cellular phone, a smartphone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, a video device, etc.), a camera, a gaming device, a navigation / positioning device (e.g., GPS (Global Positioning System), Beidou, GLONASS, or Galileo, ground-based device-based, e.g., GNSS (Global Navigation Satellite System) device, etc.), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicle device, a meter (e.g., a parking meter, an electric meter, a gas meter, a water meter), a monitor, a fuel pump, an appliance (e.g., kitchen appliances, a washing machine, a dryer), a location tag, a medical / health management device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless medium or a wired medium, etc. In some examples, UE115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Everything (IoE) device, or an MTC device, etc., which may be implemented in various articles such as appliances, drones, robots, vehicles, meters, etc.

[0069] Some UEs 115, such as MTC devices or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to a data communication technology that enables devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from a device that integrates sensors or meters to measure or capture information and relays that information to a central server or application program that can utilize the information, or presents the information to a human who can interact with the program or application. Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing. In one aspect, the techniques disclosed herein may be applicable to MTC UEs or IoT UEs. MTC UEs or IoT UEs may include MTC / extended MTC (also referred to as CAT-M, Cat M1, eMTC) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (extended further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (extended NB-IoT), FeNB-IoT (further extended NB-IoT), etc.

[0070] Some UEs 115 may be configured to adopt an operation mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power-saving "deep sleep" mode when not involved in active communication, or operating over a limited bandwidth (e.g., in accordance with narrowband communication). In some cases, the UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

[0071] In some cases, the UE 115 may also be able to communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) protocol or a device-to-device (D2D) protocol). One or more of the groups of UEs 115 that utilize D2D communication may be within the geographical coverage area 110 of the base station 105. Other UEs 115 within such a group may be outside the geographical coverage area 110 of the base station 105, or may in some cases be unable to receive transmissions from the base station 105. In some cases, the group of UEs 115 that communicate via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to all other UEs 115 within the group. In some cases, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without the involvement of the base station 105.

[0072] The base station 105 can communicate with the core network 130 and with each other. For example, the base station 105 can interface with the core network 130 through a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other either directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) via a backhaul link 134 (e.g., via X2, Xn, or other interfaces).

[0073] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access functions, routing functions, or mobility functions. The core network 130 can be an evolved packet core (EPC), and the EPC can include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets can be transferred through an S-GW that can itself be connected to a P-GW. The P-GW can provide IP address allocation as well as other functions. The P-GW can be connected to a network operator IP service. The operator IP service can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet switched (PS) streaming service.

[0074] At least some of the network devices, such as base station 105, may include sub-components such as access network entities, and the access network entities may be an example of an access node controller (ANC). Each access network entity may communicate with UE115 through some other access network transmission entities, which may be called radio heads, smart radio heads, or transmission / reception points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or integrated within a single network device (e.g., base station 105).

[0075] Wireless communication system 100 may typically operate using one or more frequency bands in the range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz has wavelengths ranging from about 1 decimeter to 1 meter, so it is called the ultra-high frequency (UHF) region or the decimeter band. UHF waves may be blocked or redirected by buildings and environmental characteristics. However, the waves can penetrate structures well enough for a macrocell to provide service to a UE115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmissions using lower frequencies and longer waves in the short-wave (HF) or very-high frequency (VHF) portions of the spectrum below 300 MHz.

[0076] Wireless communication system 100 may also operate in the super-high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also called the centimeter band. The SHF region includes bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which may be opportunistically used by devices that may be able to tolerate interference from other users.

[0077] Wireless communication system 100 may also operate in the extremely high frequency (EHF) band of the spectrum, also known as the millimeter wave band (e.g., from 30 GHz to 300 GHz). In some examples, wireless communication system 100 may support millimeter wave (mmW) communication between UE 115 and base station 105, and the EHF antennas of each device may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within UE 115. However, EHF transmission propagation may be conditioned on even greater atmospheric attenuation and shorter distances than SHF or UHF transmission. The techniques disclosed herein may be employed across transmissions using one or more different frequency bands, and the designated use of the bands across these frequency bands may vary by country or regulatory body.

[0078] In some cases, wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz ISM band. When operating in an unlicensed radio frequency spectrum band, wireless devices such as base station 105 and UE 115 may employ a listen-before-talk (LBT) procedure to ensure that the frequency channel is clear before transmitting data. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration coordinated with a component carrier operating in the licensed band (e.g., LAA). Operation in the unlicensed spectrum may include downlink transmission, uplink transmission, peer-to-peer transmission, or combinations thereof. Duplexing in the unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.

[0079] In some examples, base station 105 or UE 115 may be equipped with multiple antennas, and such antennas can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication system 100 may use a certain transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. The multiple signals can be transmitted by the transmitting device via, for example, different antennas or different combinations of antennas. Similarly, the multiple signals can be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams. The different spatial layers may be associated with different antenna ports used for channel measurement and channel reporting. MIMO techniques include single-user MIMO (SU-MIMO) where multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO) where multiple spatial layers are transmitted to multiple devices.

[0080] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting device or a receiving device (e.g., base station 105 or UE 115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that signals propagating in a particular orientation with respect to the antenna array undergo constructive interference while other signals undergo destructive interference. Adjustment of the signals communicated through the antenna elements may include the transmitting device or the receiving device applying some amplitude and phase offsets to the signals conveyed through each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0081] In one example, base station 105 may use multiple antennas or antenna arrays to direct beamforming operations for directional communication with UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions, which may include the signals being transmitted according to different sets of beamforming weights associated with the different directions of transmission. Transmission in different beam directions may be used to identify (e.g., by a receiving device such as base station 105 or UE 115) a beam direction for subsequent transmission and / or reception by base station 105.

[0082] Some signals, such as data signals associated with a particular receiving device, may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with a receiving device such as UE115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, UE115 may receive one or more of the signals transmitted by base station 105 in different directions, and UE115 may report to base station 105 an indication of the signal that UE115 received with the highest signal quality or otherwise acceptable signal quality. These techniques are described with reference to signals transmitted by base station 105 in one or more directions, but UE115 may employ similar techniques for transmitting signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE115) or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0083] A receiving device (e.g., UE115 which may be an example of a mmW receiving device) may attempt multiple receive beams when receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from base station 105. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, by processing received signals from different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" with different receive beams or receive directions. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). The single receive beam may be aligned in a beam direction determined at least in part based on listening with different receive beam directions (e.g., a beam direction determined to have maximum signal strength, maximum signal-to-noise ratio, or otherwise acceptable signal quality at least in part based on listening with multiple beam directions).

[0084] In some cases, the antennas of base station 105 or UE 115 may be arranged within one or more antenna arrays that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be placed together in an antenna assembly such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be arranged in various geographical locations. Base station 105 may have an antenna array having several rows and columns of antenna ports that it can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO operations or beamforming operations.

[0085] In some cases, wireless communication system 100 may be a packet-based network that operates according to a hierarchical protocol stack. In the user plane, communication in the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication via logical channels. The Media Access Control (MAC) layer may perform priority handling and multiplexing of logical channels onto transport channels. The MAC layer may also use Hybrid Automatic Repeat reQuest (HARQ) to perform retransmissions in the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may establish, configure, and maintain an RRC connection between UE 115 and base station 105 or core network 130 that supports radio bearers for user plane data. In the physical layer, transport channels may be mapped to physical channels.

[0086] In some cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is one technique for increasing the likelihood that data is correctly received over the communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput in the MAC layer under poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback in the same slot for data received in a previous symbol in that particular slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0087] Time intervals in LTE or NR may be expressed as multiples of a basic time unit that, for example, refers to a sampling period of T s = 1 / 30,720,000 seconds. The time intervals of communication resources may be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period is T f = 307,200T sIt can be expressed as such. The radio frame can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. The subframe may be further divided into two slots each having a duration of 0.5 ms, and each slot may include 6 or 7 modulated symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). Excluding the cyclic prefix, each symbol period may include 2048 sampling periods. In some cases, the subframe may be the minimum scheduling unit of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than the subframe or may be dynamically selected (e.g., within a burst of shortened TTIs (sTTIs) or within a selected component carrier using sTTIs).

[0088] In some wireless communication systems, a slot can be further divided into a plurality of mini-slots including one or more symbols. In some cases, the symbol or mini-slot of the mini-slot may be the minimum unit of scheduling. The duration of each symbol may vary, for example, depending on the subcarrier spacing or the operating frequency band. Further, some wireless communication systems may perform slot aggregation where a plurality of slots or mini-slots are aggregated together for use in communication between the UE 115 and the base station 105.

[0089] The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication over communication link 125. For example, a carrier of communication link 125 may include a portion of a radio frequency spectrum band that operates according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. A carrier may be associated with a predefined frequency channel (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be arranged according to a channel raster for discovery by UE 115. A carrier may be a downlink or uplink (e.g., in FDD mode) or may be configured to carry downlink communication and uplink communication (e.g., in TDD mode). In some examples, the signal waveform transmitted via a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

[0090] The organizational structure of carriers may vary for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR). For example, communication via a carrier may be organized according to a TTI or slot, each of which may include user data and control information or control signaling to support decoding of the user data. A carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate the operation for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate the operation with respect to other carriers.

[0091] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, control information transmitted within a physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0092] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) for a carrier of a particular radio access technology. In some examples, each served UE 115 may be configured for operation over a portion or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using a narrowband protocol type associated with a predetermined portion or range (e.g., a set of subcarriers or RBs) within the carrier (e.g., "in-band" deployment of the narrowband protocol type).

[0093] In a system that employs the MCM technique, a resource element can consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements the UE115 receives and the higher the order of the modulation scheme, the higher the data rate can be for the UE115. In an MIMO system, the wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate for communication with the UE115.

[0094] A device (e.g., the base station 105 or the UE115) of the wireless communication system 100 may have a hardware configuration that supports communication via a specific carrier bandwidth or may be configured to support communication via one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and / or a UE115 that supports simultaneous communication via carriers associated with two or more different carrier bandwidths.

[0095] The wireless communication system 100 may support communication with the UE115 on multiple cells or carriers, and this function may sometimes be referred to as carrier aggregation or multi-carrier operation. The UE115 may be configured with a plurality of downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both FDD component carriers and TDD component carriers.

[0096] In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). The eCC can be characterized by one or more features including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, the eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have sub-optimal or non-ideal backhaul links). The eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., when two or more operators are permitted to use the spectrum). The eCC characterized by a wide carrier bandwidth may include one or more segments that can be utilized by a UE 115 that is not capable of monitoring the overall carrier bandwidth, or may be otherwise configured to use a limited carrier bandwidth (e.g., to conserve power).

[0097] In some cases, the eCC may utilize a symbol duration different from that of other component carriers, which may include the use of a shortened symbol duration compared to the symbol duration of other component carriers. The shorter symbol duration may be related to an increased spacing between adjacent sub-carriers. A device such as a UE 115 or a base station 105 that utilizes the eCC can transmit a wideband signal at the shortened symbol duration (e.g., 16.67 microseconds) according to, for example, a frequency channel or a carrier bandwidth of 20, 40, 60, 80 MHz, etc. The TTI in the eCC can consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) may be variable.

[0098] The wireless communication system 100 may be an NR system that can utilize any combination of licensed spectrum bands, shared spectrum bands, and unlicensed spectrum bands. The flexibility of the eCC symbol duration and subcarrier spacing may enable the use of eCC across multiple spectrums. In some examples, the NR shared spectrum can increase spectrum utilization and spectral efficiency, particularly through dynamic (e.g., across the frequency domain) vertical sharing and (e.g., across the time domain) horizontal sharing of resources.

[0099] UE 115 and base station 105 may communicate using the frame scheduling techniques described herein. For example, base station 105 may transmit a frame to UE 115, where the frame includes a set of downlink subframes that include a plurality of data messages. Some of the data messages in the downlink subframes of the current frame are scheduled based on at least one control message received in the current frame, but some of the data messages may be scheduled by one or more control messages in a previous frame.

[0100] The techniques described may be utilized to improve resource utilization and communication efficiency. One implementation may enable UE 115 to process more data using fewer resources, or in other words, UE 115 may be able to utilize existing resources efficiently. Since UE 115 may be able to receive more data using the same or fewer resources, UE 115 may conserve power and extend battery life.

[0101] In some cases, techniques with extended scheduling delays may be implemented to support frame scheduling. For example, base station 105 may indicate a delayed schedule (e.g., via DCI) for a data message, where the delayed schedule indication schedules the data message in the next frame or scheduling instance after the transmission of the bundled feedback response in the current frame or scheduling instance. To support such scheduling, HARQ process alternation may be used such that the HARQ process corresponding to the data message scheduled by a previous scheduling instance is processed in the current scheduling instance. The HARQ process may also include an indication of feedback timing, and in some cases, the feedback timing may be extended (compared to the current instance schedule) such that an ACK or NAK corresponding to the data message received in the current scheduling instance can be transmitted in the current scheduling instance.

[0102] To support various scheduling techniques, DCI can be used to display various parameters. DCI can be used to display an increased number of HARQ processes, a modified HARQ ACK delay value, an extended acceptable PDSCH scheduling delay, etc. In some cases, DCI can be used to display various parameters without increasing the DCI payload size. For example, existing DCI fields can enable scheduling with increased maximum throughput in DCI. In another case, the DCI payload may be increased to support scheduling with increased maximum throughput in DCI. For example, additional bits, sometimes referred to as extended scheduling fields, can be used to support scheduling with increased maximum throughput. The techniques described herein can support ACK delay options of 12 subframes and 13 subframes, as well as a PDSCH scheduling delay of N+7.

[0103] FIG. 2 shows an example of a communication system 200 that supports scheduling for feedback response according to various aspects of the present disclosure. In some examples, communication system 200 may implement aspects of wireless communication system 100. Communication system 200 includes base station 105-a and UE 115-a. UE 115-a and base station 105-a communicate via communication link 125, and the communication may include downlink communication and uplink communication. The downlink communication and uplink communication may be allocated according to one or more scheduling instances (e.g., frames) such as scheduling pattern 230. Scheduling pattern 230 is divided into various subframes such as subframe 225. A set 205 of subframes may be allocated for downlink communication, and a set 210 of subframes may be allocated for uplink communication. Each subframe may include control resources (e.g., a machine type communication physical downlink control channel (MPDCCH)) and data resources (e.g., a physical downlink shared channel (PDSCH)). The control resources (e.g., control message 215-a) may include information for scheduling data resources (e.g., data message 220-a). Thus, each subframe of set 205 of downlink subframes may include a control message (e.g., control message 215-a) and a data message (e.g., data message 220-a).

[0104] The control message can schedule the timing of the data message and the feedback timing for each data message. The feedback timing can indicate a location within a set 210 of uplink subframes for transmitting a feedback response related to the data message (e.g., a hybrid automatic repeat request (HARQ) acknowledgement response (ACK) or non-acknowledgement response (NAK)). In some cases, a particular control message can schedule a plurality of data messages, including the location of the data message (e.g., scheduling delay) and the feedback timing for the data message (e.g., feedback delay). In some cases, the scheduling information can be transmitted in the downlink control information (DCI) resources of the data channel. In some cases, feedback is allocated to one of the subframes of the set 210 of uplink subframes. For example, the feedback related to data message D1 can be allocated to uplink subframe U0, and the feedback related to data message D2 can be allocated to uplink subframe U1.

[0105] Using the techniques described herein, base station 105-a and UE 115-a may communicate according to scheduling pattern 230, which may include data messages D-1 and D-2 and control messages M10 and M11. To achieve the illustrated scheduling pattern or scheduling instance 230 that includes data messages D-1 and / or D-2 and control messages M10 and / or M11, the maximum number of HARQ processes may be increased, the HARQ ACK delay value may be modified, the allowable PDSCH scheduling delay may be extended, fields in the DCI may be modified without modifying the DCI payload size, and / or the DCI payload size may be increased. In some cases, some data messages of scheduling pattern 230 may be scheduled according to the control messages of scheduling pattern 230, and other data messages of scheduling pattern 230 may be scheduled according to one or more control messages of a previous frame. Thus, the feedback timing for a particular data message may be scheduled according to the control messages of the current scheduling pattern 230 or the control messages from a previous scheduling pattern / scheduling instance.

[0106] In some cases, data messages D-2 and D-1 may be received after a downlink shared channel (e.g., PDSCH) scheduling delay, which includes subframes for the transmission of one or more bundled additional feedback responses during a previous scheduling instance. For example, a previous scheduling instance may include a set of downlink subframes including control messages and / or data messages, and a set of uplink subframes following that, including resources for transmitting ACK / NAK related to the data messages. Further, the control messages in the previous scheduling instance may schedule data messages such as D-2 and D-1 in the current scheduling pattern 230. Thus, the control messages in the previous scheduling instance may schedule the reception of data messages (in the current scheduling pattern 230) after the transmission of one or more ACK / NACKs for the data messages in the previous scheduling instance.

[0107] The techniques described may enable UE115-a and base station 105-a to utilize resources more efficiently. UE115-a may receive additional data from the base station via existing resources and using this scheduling technique. For example, using the techniques described herein, UE115-a may receive data within data messages D-2 and / or D-1 that may not include resources in other scheduling instance allocation techniques. Thus, UE115-a and base station 105-a may communicate more efficiently than may be allowable in existing scheduling instance allocation techniques.

[0108] FIG. 3A and FIG. 3B illustrate exemplary scheduling instance formats 300 and 315 that support scheduling for feedback responses according to various aspects of the present disclosure. In some examples, frame scheduling instance 300 may be implemented by aspects of wireless communication system 100. Scheduling instances 300 and 315 include a set of subframes for downlink and a set of frames for uplink communication. The set of subframes allocated for downlink communication may include various control messages (e.g., M0 - M13) and various data messages (e.g., D0 - D13). To achieve peak throughput for scheduling instances 300 and 315, devices (e.g., UE115 and base station 105) may utilize 14 HARQ processes for HARQ scheduling and feedback for the data messages of the scheduling instance. To support 14 HARQ processes, that number of soft channel bits may be allocated to UE115 for processing that number of HARQ processes. In other cases, UE115 may not support that number of soft channel bits for processing that number of HARQ processes. In such cases, UE115 may support overbooking of the HARQ memory used to monitor the HARQ processes. For example, UE115 may store received soft channel bits corresponding to at least 8 of the most recent HARQ identifiers (IDs).

[0109] When UE115 supports up to 14 HARQ processes, UE115 may support the scheduling instance 300 shown in FIG. 3A. In scheduling instance 300, the HARQ processes associated with control messages M10, M11, M12, and M13 may be alternatively scheduled. The alternative scheduling may result in the feedback (e.g., ACK / NAK) associated with control messages M10 and M11 being sent after the scheduling instance for the HARQ processes associated with M12 and M13. In other words, the feedback associated with control messages M10 and M11 may be sent in one of the uplink subframes 30-32 that follow control messages M12 and M13. Thus, the HARQ processes associated with M12 and M13 may be different from those associated with M10 and M11 (e.g., having different HARQ process IDs). In some cases, the scheduling pattern 300 may have a maximum throughput of 706 kbps (e.g., (12 downlink subframes / total 17 subframes) * 1000 kbps = 706 kbps).

[0110] In the scheduling instance 300 of FIG. 3A, the data messages D12 and D13 of the scheduling instance 310-a can be scheduled by one or more control messages in a previous scheduling instance. In some cases, the scheduling instance 310-a may be a set of consecutive downlink subframes, such as those indicated by consecutive downlink subframes 0 to 11. Similarly, the data messages D10 and D11 of the scheduling instance 310-b can be scheduled by one or more of the control messages in the previous scheduling instance 310-a. In some cases, the scheduling instance 310-b may be a set of consecutive downlink subframes, such as those indicated by consecutive downlink subframes 17 to 28. This scheduling can be the result of the scheduling delay indicated by each control message. For example, the control message M10 can indicate a scheduling delay of N + 7 for the data message D10.

[0111] When the UE supports a maximum of 12 HARQ processes, the UE 115 may support the pattern 315 shown in FIG. 3B. In the scheduling instance 315, the HARQ processes associated with the control messages M10 and M11 can be alternatively scheduled. The alternative scheduling can be the result of the feedback (e.g., ACK / NAK) associated with the control message M10 being transmitted after the scheduling instance for the HARQ process associated with M11. In other words, the feedback associated with the control message M10 can be transmitted in one of the uplink subframes 30 to 32 after the control message M11. Thus, the HARQ process associated with M11 may be different from the HARQ process associated with M10. In some cases, the pattern 315 may have a maximum throughput of 647 kbps (e.g., (11 downlink subframes / total 17 subframes) * 1000 kbps = 647 kbps).

[0112] In the scheduling instance 315 of FIG. 3B, the data message D11 of the scheduling instance 310-c can be scheduled by one or more control messages in a previous scheduling instance. In some cases, the scheduling instance 310-c may be a set of consecutive downlink subframes, such as those indicated by consecutive downlink subframes 0 to 10. Similarly, the data message D10 of the scheduling instance 310-d can be scheduled by one or more of the control messages in the previous scheduling instance 310-c. In some cases, the scheduling instance 310-d may be a set of consecutive downlink subframes, such as those indicated by consecutive downlink subframes 17 to 27. This scheduling can be the result of the scheduling delay indicated by each control message. For example, the control message M10 can indicate a scheduling delay of N + 7 for the data message D10.

[0113] Figures 4A and 4B illustrate examples of tables 400 and 430 that support scheduling for feedback responses according to various aspects of the present disclosure. In some examples, tables 400 and 430 may be implemented by aspects of wireless communication system 100. Tables 400 and 430 show exemplary values that may be used by UE 115 and / or base station 105 to schedule and determine resource and feedback schedules using scheduling instances / scheduling patterns as described herein. Tables 400 and 430 may be used to determine HARQ ID, scheduling delay, and feedback delay (e.g., ACK delay) based on various information included in the DCI. The DCI may include a field for indicating an ACK delay of 11 subframes, but the scheduling pattern (e.g., as described with respect to FIG. 3) may utilize an ACK delay of 12 or 13 subframes. Similarly, the DCI may support a PDSCH decoding delay (e.g., scheduling delay) of N+2, but the scheduling instance (e.g., as described with respect to FIG. 3) may utilize a delay of N+7. The DCI may support a 3-bit ACK delay field and a 4-bit HARQ ID field. Using tables 400 and 430, the DCI may support ACK delays of 12 and 13 and a PDSCH decoding delay of N+7 without increasing the DCI payload (e.g., by adding another bit).

[0114] The information shown in Tables 400 and 430 may be used when the HARQ_ID field is greater than a threshold. In some cases, when the HARQ_ID value is 9 or less, the scheduling delay may be determined or allocated as N+2, where HARQ ID is the actual HARQ_ID field value and the 3-bit ACK delay field indicates a value in the ACK delay table. However, when the HARQ_ID field value exceeds 9, the HARQ-ID, scheduling delay, and ACK delay used may be determined based on the HARQ-ACK delay field and the HARQ_ID field and in accordance with Tables 400 and 430. It should be understood that the information shown in Tables 400 and 430 is merely exemplary and other values may be utilized. When the HARQ-ID field value is greater than 9, the HARQ-ACK delay field 405 in the DCI may be used to determine the actual HARQ ID 410 and scheduling delay 415 as shown in Table 400 of FIG. 4A. For example, when the HARQ_ID field is greater than 9, the HARQ-ACK delay field 405 having the value "010" may indicate an actual HARQ ID 410 of 11 and a scheduling delay 415 of N+2. Similarly, when the HARQ_ID field is greater than 9, the HARQ-ACK delay field 405 having the value "011" may indicate an actual HARQ ID 410 of 11 and a scheduling delay 415 of N+7.

[0115] Furthermore, as shown in table 430 of FIG. 4B, the HARQ_ID field 420 can be used to determine the feedback timing (e.g., ACK delay 425) when the HARQ ID is greater than 9. For example, if the HARQ_ID field 420 has a value of 10, the corresponding ACK delay 425 may be 4 subframes. Thus, using the techniques shown in tables 400 and 430, the base station 105 can schedule data resources and corresponding feedback responses (e.g., HARQ processes and feedback timing) for a scheduling instance that includes resources as shown with respect to FIGS. 2 and 3. Further, the UE 115 can be configured to determine a data schedule and feedback response (e.g., HARQ process ID and feedback timing) for a scheduling instance that includes resources as shown with respect to FIGS. 2 and 3.

[0116] FIG. 5 shows an example of a table 500 that supports scheduling for feedback responses according to various aspects of the present disclosure. In some examples, the table 500 may be implemented by aspects of the wireless communication system 100. The table 500 shows possible scheduling parameters that use an extended scheduling bit 510 as a DCI field. For example, the DCI may include a HARQ_ACK delay field and an extended scheduling field 510 that may be used to indicate a HARQ_ACK delay value 515 and a scheduling delay 520. In one example, if the HARQ-ACK delay field 505 has a value of "101" and the extended scheduling field 510 has a value of "0" (i.e., extended scheduling is turned off), the HARQ-Ack delay value 515 may be 9 and the scheduling delay 520 may be N + 2. Similarly, if the HARQ-ACK delay field 505 includes a value of "101" and the extended scheduling field 510 includes a value of "1" (i.e., extended scheduling is turned on), the HARQ_ACK delay value 515 may be 9 and the scheduling delay 520 may be N + 7. It should be understood that the values included in the table 500 are for illustrative purposes only and that other values may be included in accordance with aspects of the present disclosure. In some cases, the scheduling technique may be supported by the table 500 by including a 4-bit HARQ-ACK delay field or by adding a separate field. In either case, the bit may be referred to as an extended scheduling field.

[0117] Figure 6 shows an example of a scheduling pattern or scheduling instance 600 that supports scheduling for feedback responses according to an aspect of the present disclosure. In some examples, the scheduling pattern 600 may implement aspects of the wireless communication system 100. The scheduling pattern 600 includes an exemplary frame (e.g., a scheduling instance) 620 having corresponding ACK delays 605 and ACK groups 610. The ACK delays 605 and ACK groups 610 may correspond to respective subframes of the scheduling instance 620. For example, the ACK delay 605 corresponding to the data message M3 (e.g., subframe 3) may be 11, and the ACK group 610 may be U0. Thus, a feedback response (e.g., ACK or NAK) for the data message D1 may be transmitted 11 subframes after the data message D1 is received, corresponding to the ACK group U0. (E.g., subframe 13 of a set of uplink subframes.)

[0118] Feedback responses may be bundled and transmitted such that multiple ACK / NAKs for multiple data messages can be transmitted within the same scheduling instance or frame. In some cases, a NAK is transmitted when at least one of the data messages corresponding to the bundle results in a NAK. For example, for the ACK group U0, if one of the data messages D-2, D0, D2, or D6 results in a NAK response, a NAK may be transmitted in the uplink subframe 13 (e.g., group U0). However, if none of the data messages corresponding to the group U0 require a NAK, an ACK may be transmitted in the uplink subframe 13 (e.g., group U0). Scheduling techniques as described with respect to FIGS. 2-5 may be utilized to implement the bundled feedback as shown in the exemplary scheduling pattern 600.

[0119] Data messages D-2 and D-1 can be scheduled by one or more control messages in a previous scheduling instance. Further, control messages M10 and M11 can schedule one or more data messages in the next scheduling instance. Scheduling pattern 600 can correspond to scheduling with maximum throughput. In some cases, scheduling pattern 600 may be implemented with a schedule having throughput lower than the maximum. For example, scheduling instance 620 may include control messages up to M10 (e.g., not including M11), and data messages up to D-1 (e.g., not including D-2). In some cases, scheduling instance 620 may include a scheduling instance comprising a set of consecutive downlink subframes, such as indicated by consecutive downlink subframes 0 to 11.

[0120] In some cases, the scheduling techniques described herein can support up to 12 data messages per scheduling instance (such as indicated by scheduling pattern 600). In some cases, the amount of data messages can be configured by upper layer parameters. For example, when a throughput extension parameter is set to "on", a parameter indicating the number of data messages may be set to 12.

[0121] In some examples, multiple data messages may be scheduled by a single control message (e.g., a single DCI). Thus, a single DCI may schedule each of messages D0 - D9, and an additional two data messages (e.g., D - 2 and D - 1) in the next scheduling instance. Thus, ten data messages (transmission blocks (TBs)) may be successively scheduled, and then a fixed scheduling delay may be indicated for the data messages (e.g., TB10 / 11) in the next scheduling instance. One exemplary technique for performing such scheduling may include determining whether the number of TBs is below a threshold (e.g., ten). If the number of TBs is less than the threshold (e.g., ten), the TBs may be successively scheduled, and then a gap may be introduced for HARQ - ACK feedback. Any remaining TBs (e.g., more than the threshold) may be transmitted after the HARQ - ACK feedback.

[0122] FIG. 7 shows an example of a process flow 700 that supports scheduling instance scheduling for feedback responses, according to an aspect of the present disclosure. In some examples, the process flow 700 may illustrate aspects of a wireless communication system 100. The process flow 700 may include a base station 105 - b and a UE 115 - b. At 705, the base station 105 - b may transmit at least one control message to the UE 115 - b within a set of downlink subframes in the current scheduling instance 715 - a. At 710, the base station 105 - b transmits a plurality of data messages to the UE 115 - b within a set of downlink subframes in the current scheduling instance 715 - a. A first subset of the plurality of data messages may be transmitted according to at least one control message transmitted at 705, while another subset of the plurality of data messages is transmitted according to one or more control messages of a previous scheduling instance.

[0123] At 720, UE 115-b determines the feedback timing for each of a plurality of data messages. The feedback timing for a first subset of the plurality of data messages may be based on at least one control message, and the feedback timing for a second subset of the plurality of data messages may be based on one or more control messages received in a previous scheduling instance.

[0124] At 725, UE 115-b transmits one or more bundled feedback responses to base station 105-b during the uplink subframes in the current scheduling instance 715-a.

[0125] At 730, base station 105-b may transmit at least one control message to UE 115-b within a set of downlink subframes in the next scheduling instance 715-b. At 735, base station 105-b transmits a plurality of data messages to UE 115-b within a set of downlink subframes in the next scheduling instance 715-b. A first subset of the plurality of data messages may be transmitted in accordance with at least one control message transmitted at 730, while another subset of the plurality of data messages is transmitted in accordance with one or more control messages of the previous scheduling instance 715-a.

[0126] At 740, UE 115-b determines the feedback timing for each of a plurality of data messages. The feedback timing for a first subset of the plurality of data messages may be based on at least one control message received at 730, and the feedback timing for a second subset of the plurality of data messages may be based on one or more control messages received in the previous scheduling instance 715-a (e.g., received at 705).

[0127] At 745, UE 115-b transmits one or more bundled feedback responses to base station 105-b during uplink subframes in the current scheduling instance 715-a.

[0128] FIG. 8 shows a block diagram 800 of a device 805 that supports scheduling of a scheduling instance for feedback responses, according to an aspect of the present disclosure. Device 805 may be an example of an aspect of UE 115 as described herein. Device 805 may include a receiver 810, a communication manager 815, and a transmitter 820. Device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] Receiver 810 may receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to scheduling of a scheduling instance for feedback responses). The information may be communicated to other components of device 805. Receiver 810 may be an example of an aspect of transceiver 1120 described with reference to FIG. 11. Receiver 810 may utilize a single antenna or a set of antennas.

[0130] The communication manager 815 may receive at least one control message within a set of downlink subframes in the current scheduling instance, and receive a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance, and determine feedback timing for each of the set of data messages, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance, and transmit one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages. The communication manager 815 may be an example of an aspect of the communication manager 1110 described herein.

[0131] The communication manager 815 or its subcomponents may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. When implemented in code executed by a processor, the functionality of the communication manager 815 or its subcomponents may be executed by a general-purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0132] The communication manager 815 or its sub-components may be physically located in various positions, including where the functional parts are distributed to be implemented by one or more physical components at different physical locations. In some examples, the communication manager 815 or its sub-components may be separate and distinct components according to various aspects of the present disclosure. In some examples, the communication manager 815 or its sub-components may include, but are not limited to, input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in the present disclosure, or combinations thereof according to various aspects of the present disclosure, and may be combined with one or more other hardware components.

[0133] Actions performed by the communication manager 815 as described herein may be implemented to realize one or more potential advantages. One implementation may enable the UE 115 to process more data using fewer resources, or in other words, the UE 115 may be able to utilize existing resources efficiently. Since the UE 115 may be able to receive more data using the same or fewer resources, the UE 115 may save power and extend battery life.

[0134] Based on receiving data scheduled by control messages in the current scheduling instance and data scheduled by control messages in previous scheduling instances, the processor of UE115 (e.g., controlling receiver 810 and transmitter 820) may efficiently receive and process data scheduled by the previous scheduling instance. The processor of UE115 may receive the scheduled data, increase the processing clock, or activate one or more processing units for similar mechanisms within UE115. Thus, when data scheduled by a previous scheduling instance is received, the processor may be prepared to respond more efficiently (e.g., based on the scheduled feedback timing) through a reduction in ramp-up in processing power.

[0135] Transmitter 820 may transmit signals generated by other components of device 805. In some examples, transmitter 820 may be co-located with receiver 810 within a transceiver module. For example, transmitter 820 may be an example of an aspect of transceiver 1120 described with reference to FIG. 11. Transmitter 820 may utilize a single antenna or a set of antennas.

[0136] FIG. 9 shows a block diagram 900 of a device 905 that supports scheduling instance scheduling for feedback response according to an aspect of the present disclosure. Device 905 may be an example of device 805 or an aspect of UE115 as described herein. Device 905 may include a receiver 910, a communication manager 915, and a transmitter 940. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0137] Receiver 910 can receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to scheduling instance scheduling for feedback responses, etc.). The information may be communicated to other components of device 905. Receiver 910 may be an example of the aspect of transceiver 1120 described with reference to FIG. 11. Receiver 910 may utilize a single antenna or a set of antennas.

[0138] Communication manager 915 may be an example of the aspect of communication manager 815 as described herein. Communication manager 915 may include a control message interface 920, a data message interface 925, a feedback timing component 930, and a feedback response component 935. Communication manager 915 may be an example of the aspect of communication manager 1110 described herein. Control message interface 920 can receive at least one control message within a set of downlink subframes in the current scheduling instance.

[0139] Data message interface 925 can receive a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance.

[0140] The feedback timing component 930 may determine the feedback timing for each of a set of data messages, where the feedback timing for a first subset of the set of data messages is based on at least one control message, and where the feedback timing for a second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance. The feedback response component 935 may transmit one or more bundled feedback responses during an uplink subframe in a current scheduling instance and in accordance with the feedback timing for each of the set of data messages.

[0141] The transmitter 940 may transmit signals generated by other components of the device 905. In some examples, the transmitter 940 may be co-located with the receiver 910 within a transceiver module. For example, the transmitter 940 may be an example of an aspect of the transceiver 1120 described with reference to FIG. 11. The transmitter 940 may utilize a single antenna or a set of antennas.

[0142] FIG. 10 shows a block diagram 1000 of a communication manager 1005 that supports scheduling instance scheduling for feedback response, according to an aspect of the present disclosure. The communication manager 1005 may be an example of an aspect of the communication manager 815, the communication manager 915, or the communication manager 1110 described herein. The communication manager 1005 may include a control message interface 1010, a data message interface 1015, a feedback timing component 1020, a feedback response component 1025, a HARQ component 1030, and a scheduling component 1035. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses). The control message interface 1010 may receive at least one control message within a set of downlink subframes in the current scheduling instance.

[0143] In some examples, the control message interface 1010 may receive at least one control message that schedules one or more additional data messages in a next scheduling instance after a downlink shared channel scheduling delay that causes one or more additional data messages to be scheduled in the next scheduling instance after transmission of one or more bundled feedback responses during uplink subframes in the current scheduling instance. In some examples, the control message interface 1010 may receive a first control message of at least one control message, and the first control message schedules a plurality of data messages.

[0144] The data message interface 1015 may receive a set of data messages within a set of downlink subframes in a current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance.

[0145] In some examples, the data message interface 1015 may receive a second subset of the set of data messages after a downlink shared channel scheduling delay including a subframe for transmitting one or more bundled additional feedback responses during a previous scheduling instance. In some examples, the data message interface 1015 may receive more than 10 data messages within a set of downlink subframes in a current scheduling instance. In some examples, the data message interface 1015 may receive a second subset of the set of data messages after a downlink shared channel scheduling delay of 7 subframes.

[0146] In some examples, the data message interface 1015 may receive each of the set of data messages in each of at least 11 downlink subframes including the set of downlink subframes. In some examples, the data message interface 1015 may receive a set of data messages within a set of downlink subframes in a current scheduling instance, where each downlink subframe of the set of downlink subframes includes a data message of the set of data messages.

[0147] The feedback timing component 1020 may determine the feedback timing for each of a set of data messages, where the feedback timing for a first subset of the set of data messages is based on at least one control message, and where the feedback timing for a second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance. In some examples, the feedback timing component 1020 may determine a feedback delay associated with a first control message based on a HARQ ID field. In some examples, the feedback timing component 1020 may determine a feedback delay for one of the set of data messages that is 12 subframes or 13 subframes. The feedback response component 1025 may transmit one or more bundled feedback responses during an uplink subframe in a current scheduling instance and in accordance with the feedback timing for each of the set of data messages.

[0148] In some cases, the current scheduling instance is scheduled for enhanced machine type communication (eMTC). The HARQ component 1030 may process concurrent HARQ processes associated with at least one control message received within a set of downlink subframes of the current scheduling instance and one or more control messages received in a previous scheduling instance.

[0149] In some examples, the HARQ component 1030 may identify a HARQ identifier (ID) field within a first control message of at least one control message. In some examples, the HARQ component 1030 may compare a value of the HARQ ID field included in the first control message to a HARQ ID field threshold.

[0150] In some examples, the HARQ component 1030 may determine that the value of the HARQ ID field in the first control message is greater than the HARQ ID field threshold. In some examples, the HARQ component 1030 may determine the HARQ process ID associated with the first control message based on the HARQ ACK delay field in the first control message.

[0151] In some examples, the HARQ component 1030 may determine the downlink shared channel scheduling delay associated with the first control message, the HARQ process ID associated with the first control message, and the feedback delay associated with the first control message based on the value of the HARQ ID field being less than or equal to the HARQ ID field threshold, where the downlink shared channel scheduling delay is the smaller of two available downlink shared channel scheduling delay values, the HARQ process ID is equal to the value of the HARQ ID field, and the feedback delay is indicated by the HARQ ACK delay field in the first control message.

[0152] In some examples, the two available downlink channel scheduling delay values include two downlink subframes and seven downlink subframes, and the HARQ component 1030 may determine the downlink shared channel scheduling delay as the two downlink subframes based on the value of the HARQ ID field being less than or equal to the HARQ ID field threshold.

[0153] In some examples, the HARQ component 1030 may identify an extended scheduling field in a first control message of at least one control message. In some examples, the HARQ component 1030 may determine a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message based on the value of the extended scheduling field.

[0154] In some examples, the HARQ component 1030 may identify a HARQ process identifier (ID) associated with each of one or more control messages received in a previous scheduling instance. In some examples, the HARQ component 1030 may identify a hybrid automatic repeat request (HARQ) process ID associated with at least one control message of a current scheduling instance, where the HARQ process ID associated with one or more control messages received in a previous scheduling instance is different from the HARQ process ID associated with at least one control message of the current scheduling instance.

[0155] In some examples, the HARQ component 1030 may identify a plurality of hybrid automatic repeat request (HARQ) process identifiers (IDs) corresponding to a plurality of data messages, where the plurality of HARQ process IDs comprises at least 12 HARQ process IDs. In some cases, the HARQ component 1030 may overbook a subset of the plurality of HARQ process identifiers. In some cases, the HARQ component 1030 may store each of the plurality of HARQ process identifiers.

[0156] The scheduling component 1035 may determine the downlink shared channel scheduling delay associated with the first control message based on the HARQ ACK delay field in the first control message. In some examples, the scheduling component 1035 may determine that a plurality of data messages scheduled by the first control message exceed a threshold number of data messages.

[0157] In some examples, the scheduling component 1035 may identify a scheduling gap between a first portion of a plurality of data messages that is less than or equal to the threshold number and a second portion of a plurality of data messages that exceeds the threshold number, where the scheduling gap facilitates reception of the second portion of the plurality of data messages in a next scheduling instance subsequent to the current scheduling instance. In some cases, the threshold number of data messages is 10.

[0158] FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports scheduling instance scheduling for feedback responses, according to an aspect of the present disclosure. The device 1105 may be or may include an example of the components of device 805, device 905, or UE 115 as described herein. The device 1105 may include components for bi-directional voice and data communication including components for transmitting and receiving communication, including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically via one or more buses (e.g., bus 1145).

[0159] The communication manager 1110 may receive at least one control message within a set of downlink subframes in the current scheduling instance, and receive a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance, and determine feedback timing for each of the set of data messages, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance, and transmit one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0160] The I / O controller 1115 can manage input and output signals for the device 1105. The I / O controller 1115 can also manage peripheral devices not integrated within the device 1105. In some cases, the I / O controller 1115 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1115 may utilize an operating system such as iOS (registered trademark), ANDROID (registered trademark), MS-DOS (registered trademark), MS-WINDOWS (registered trademark), OS / 2 (registered trademark), UNIX (registered trademark), LINUX (registered trademark), or another known operating system. In other cases, the I / O controller 1115 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with the device 1105 via the I / O controller 1115 or via hardware components controlled by the I / O controller 1115.

[0161] As described above, the transceiver 1120 can communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, the transceiver 1120 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1120 may also include a modem for modulating packets for transmission and providing the modulated packets to the antenna and for demodulating packets received from the antenna.

[0162] In some cases, the wireless device may include a single antenna 1125. However, in some cases, the device may have two or more antennas 1125 capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0163] Memory 1130 may include RAM and ROM. Memory 1130 may store computer-readable computer-executable code 1135 that, when executed, includes instructions to cause a processor to perform the various functions described herein. In some cases, memory 1130 may particularly include BIOS that can control basic hardware or software operations, such as interactions with peripheral components or peripheral devices.

[0164] Processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, individual gate or transistor logic components, individual hardware components, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated within processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks that support scheduling instance scheduling for feedback response).

[0165] Code 1135 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. Code 1135 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1135 may not be directly executable by processor 1140, but may cause a computer to perform the functions described herein (e.g., when compiled and executed).

[0166] Figure 12 shows a block diagram 1200 of a device 1205 that supports scheduling instance scheduling for feedback response, according to an aspect of the present disclosure. The device 1205 may be an example of an aspect of the base station 105 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] The receiver 1210 may receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to scheduling instance scheduling for feedback response). The information may be communicated to other components of the device 1205. The receiver 1210 may be an example of an aspect of the transceiver 1520 described with reference to FIG. 15. The receiver 1210 may utilize a single antenna or a set of antennas.

[0168] The communication manager 1215 may transmit at least one control message within a set of downlink subframes in the current scheduling instance, and transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and receive one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages. The communication manager 1215 may be an example of the aspect of the communication manager 1510 described herein.

[0169] The communication manager 1215 or its subcomponents may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. When implemented in code executed by a processor, the functions of the communication manager 1215 or its subcomponents may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), an FPGA, or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0170] The communication manager 1215 or its sub-components may be physically located in various positions, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, the communication manager 1215 or its sub-components may be separate and distinct components according to various aspects of the present disclosure. In some examples, the communication manager 1215 or its sub-components may be combined with one or more other hardware components including, but not limited to, input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in the present disclosure, or combinations thereof according to various aspects of the present disclosure.

[0171] The transmitter 1220 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1220 may be co-located with the receiver 1210 within a transceiver module. For example, the transmitter 1220 may be an example of an aspect of the transceiver 1520 described with reference to FIG. 15. The transmitter 1220 may utilize a single antenna or a set of antennas.

[0172] FIG. 13 shows a block diagram 1300 of a device 1305 that supports scheduling instance scheduling for feedback responses, according to an aspect of the present disclosure. The device 1305 may be an example of the device 1205, or an aspect of the base station 105 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1335. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0173] Receiver 1310 can receive information such as control information related to packets, user data, or various information channels (e.g., control channels, data channels, and information related to scheduling instance scheduling for feedback responses, etc.). The information may be conveyed to other components of device 1305. Receiver 1310 may be an example of the aspect of transceiver 1520 described with reference to FIG. 15. Receiver 1310 may utilize a single antenna or a set of antennas.

[0174] Communication manager 1315 may be an example of the aspect of communication manager 1215 as described herein. Communication manager 1315 may include a control message interface 1320, a data message interface 1325, and a feedback response component 1330. Communication manager 1315 may be an example of the aspect of communication manager 1510 described herein. Control message interface 1320 may transmit at least one control message within a set of downlink subframes in the current scheduling instance.

[0175] The data message interface 1325 may transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance. The feedback response component 1330 may receive one or more bundled feedback responses during the uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0176] The transmitter 1335 may transmit signals generated by other components of the device 1305. In some examples, the transmitter 1335 may be co-located with the receiver 1310 within a transceiver module. For example, the transmitter 1335 may be an example of an aspect of the transceiver 1520 described with reference to FIG. 15. The transmitter 1335 may utilize a single antenna or a set of antennas.

[0177] FIG. 14 shows a block diagram 1400 of a communication manager 1405 that supports scheduling instance scheduling for feedback response, according to an aspect of the present disclosure. The communication manager 1405 may be an example of an aspect of the communication manager 1215, the communication manager 1315, or the communication manager 1510 described herein. The communication manager 1405 may include a control message interface 1410, a data message interface 1415, a feedback response component 1420, a HARQ component 1425, a scheduling component 1430, and a feedback timing component 1435. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses). The control message interface 1410 may transmit at least one control message within a set of downlink subframes in a current scheduling instance.

[0178] In some examples, the control message interface 1410 may transmit at least one control message that schedules one or more additional data messages after a downlink shared channel scheduling delay that causes one or more additional data messages to be scheduled in a next scheduling instance after receipt of one or more bundled feedback responses during an uplink subframe in the current scheduling instance. In some examples, the control message interface 1410 may transmit a first control message of at least one control message, and the first control message schedules a plurality of data messages.

[0179] The data message interface 1415 may transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance.

[0180] In some examples, the data message interface 1415 may transmit a second subset of the set of data messages after a downlink shared channel scheduling delay including a subframe for receiving one or more bundled additional feedback responses during a previous scheduling instance. In some examples, the data message interface 1415 may transmit more than 10 data messages within a set of downlink subframes in the current scheduling instance.

[0181] In some examples, the data message interface 1415 may transmit a second subset of the set of data messages after a downlink shared channel scheduling delay of 7 subframes. In some examples, the data message interface 1415 may transmit each of the set of data messages within each of at least 11 downlink subframes including the set of downlink subframes. In some examples, the data message interface 1415 may determine that the number of data messages scheduled by a first control message exceeds a threshold number of data messages.

[0182] In some examples, the data message interface 1415 may transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where each downlink subframe of the set of downlink subframes includes a data message of the set of data messages. The feedback response component 1420 may receive one or more bundled feedback responses during the uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0183] The HARQ component 1425 may transmit a HARQ identifier (ID) field in a first control message of at least one control message. In some examples, the HARQ component 1425 may select a value of the HARQ ID field that is greater than a HARQ ID field threshold.

[0184] In some examples, the HARQ component 1425 may use a HARQ acknowledgment (ACK) delay field in the first control message to indicate a HARQ process ID associated with the first control message, where the indication is based on the value of the HARQ ID field in the first control message being greater than a HARQ ID field threshold. In some examples, the HARQ component 1425 may select a value of the HARQ ID field that is less than or equal to the HARQ ID field threshold.

[0185] In some examples, the HARQ component 1425 may display a downlink shared channel scheduling delay associated with a first control message, a HARQ process ID associated with the first control message, and a feedback delay associated with the first control message based on the value of the HARQ ID field being less than or equal to a HARQ ID field threshold, where the downlink shared channel scheduling delay is the lesser of two available downlink shared channel scheduling delay values, the HARQ process ID is equal to the value of the HARQ ID field, and the feedback delay is indicated by a HARQ acknowledgment (ACK) delay field in the first control message. In some examples, the HARQ component 1425 may display a HARQ process identifier (ID) associated with at least one of one or more control messages transmitted in a previous scheduling instance.

[0186] In some examples, the two available downlink channel scheduling delay values are two downlink subframes and seven downlink subframes, and the HARQ component 1425 may determine a downlink shared channel scheduling delay of two downlink subframes based on the value of the HARQ ID field being less than or equal to a HARQ ID field threshold.

[0187] In some examples, the HARQ component 1425 may display a hybrid automatic repeat request HARQ process ID associated with at least one control message of a current scheduling instance, where the HARQ process ID associated with at least one of one or more control messages transmitted in a previous scheduling instance is different from the HARQ process ID associated with at least one control message of the current scheduling instance.

[0188] The scheduling component 1430 may indicate a downlink shared channel scheduling delay associated with a first control message using a HARQ acknowledgment (ACK) delay field included in the first control message, where the indication is based on the value of the HARQ ID field in the first control message being greater than a HARQ ID field threshold. In some examples, the scheduling component 1430 may transmit an extended scheduling field in the first control message of at least one control message.

[0189] In some examples, the scheduling component 1430 may indicate a downlink shared channel scheduling delay associated with the first control message, a HARQ process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message based on the value of the extended scheduling field. In some examples, the scheduling component 1430 may indicate a feedback delay for one of a set of data messages that is 12 subframes or 13 subframes.

[0190] In some examples, the scheduling component 1430 may identify a scheduling gap between a first portion of a plurality of data messages that is less than a threshold number and a second portion of a plurality of data messages that is greater than the threshold number, where the scheduling gap facilitates transmission of the second portion of the plurality of data messages in a next scheduling instance subsequent to the current scheduling instance. Optionally, the threshold number of data messages is 10.

[0191] The feedback timing component 1435 may indicate a feedback delay associated with a first control message based on the HARQ ID field, where the indication is based on the HARQ ID field in the first control message being greater than a HARQ ID field threshold. In some cases, the current scheduling instance is scheduled for enhanced machine type communication (eMTC).

[0192] FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports scheduling instance scheduling for feedback responses, according to an aspect of the present disclosure. The device 1505 may be or include an example of a component of the device 1205, the device 1305, or the base station 105 as described herein. The device 1505 may include components for sending and receiving communication, including components for two-way voice and data communication, including a communication manager 1510, a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communication manager 1545. These components may communicate electronically via one or more buses (e.g., bus 1550).

[0193] The communication manager 1510 may transmit at least one control message within a set of downlink subframes in the current scheduling instance, and may transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance, and may receive one or more bundled feedback responses during uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages.

[0194] The network communication manager 1515 may manage communication with a core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1515 may manage the transfer of data communication for client devices such as one or more UEs 115.

[0195] As described above, the transceiver 1520 may communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, the transceiver 1520 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1520 may also include a modem for modulating packets for transmission and providing the modulated packets to the antenna, and for demodulating packets received from the antenna.

[0196] In some cases, the wireless device may include a single antenna 1525. However, in some cases, the device may have two or more antennas 1525 capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0197] The memory 1530 may include RAM, ROM, or a combination thereof. The memory 1530 may store computer-readable code 1535 that includes instructions that cause the device to perform various functions described herein when executed by a processor (e.g., processor 1540). In some cases, the memory 1530 may include a BIOS that can control basic hardware or software operations, such as interactions with peripheral components or devices.

[0198] The processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic component, discrete hardware component, or any combination thereof). In some cases, the processor 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated within the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause the device 1505 to perform various functions (e.g., functions that support scheduling instance scheduling for feedback response or tasks).

[0199] The inter-site communication manager 1545 may manage communication with other base stations 105 and may include a controller or scheduler for controlling communication with the UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1545 may coordinate scheduling for transmission to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1545 may provide an X2 interface within the LTE / LTE-A wireless communication network technology for communicating between base stations 105.

[0200] The code 1535 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1535 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code 1535 may not be directly executable by the processor 1540 but may cause a computer to perform the functions described herein (e.g., when compiled and executed).

[0201] FIG. 16 shows a flowchart illustrating a method 1600 for supporting scheduling instance scheduling for feedback response according to an aspect of the present disclosure. The operations of method 1600 may be performed by the UE 115 or components thereof as described herein. For example, the operations of method 1600 may be executed by a communication manager as described with reference to FIGS. 8-11. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0202] At 1605, the UE may receive at least one control message within a set of downlink subframes in the current scheduling instance. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a control message interface as described with reference to FIGS. 8 - 11.

[0203] At 1610, the UE may receive a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance. The operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a data message interface as described with reference to FIGS. 8 - 11.

[0204] At 1615, the UE may determine feedback timing for each of the set of data messages, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance. The operation of 1615 may be performed according to the methods described herein. In some examples, aspects of the operation of 1615 may be performed by a feedback timing component as described with reference to FIGS. 8 - 11.

[0205] At 1620, the UE may transmit one or more bundled feedback responses during the uplink subframes in the current scheduling instance and in accordance with the feedback timing for each of the set of data messages. The operation of 1620 may be performed according to the methods described herein. In some examples, aspects of the operation of 1620 may be performed by feedback response components as described with reference to FIGS. 8 - 11.

[0206] FIG. 17 shows a flowchart illustrating a method 1700 for supporting scheduling instance scheduling for feedback responses according to an aspect of the present disclosure. The operations of method 1700 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1700 may be performed by a communication manager as described with reference to FIGS. 8 - 11. In some examples, the UE may execute a set of instructions for controlling the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0207] At 1705, the UE may receive at least one control message within a set of downlink subframes in the current scheduling instance. The operation of 1705 may be performed according to the methods described herein. In some examples, aspects of the operation of 1705 may be performed by a control message interface as described with reference to FIGS. 8 - 11.

[0208] At 1710, the UE may receive at least one control message that schedules one or more additional data messages in a next scheduling instance after a downlink shared channel scheduling delay that causes the one or more additional data messages to be scheduled in the next scheduling instance after transmission of one or more bundled feedback responses during the uplink subframes in the current scheduling instance. The operation of 1710 may be performed according to the methods described herein. In some examples, aspects of the operation of 1710 may be performed by a control message interface as described with reference to FIGS. 8 - 11.

[0209] At 1715, the UE may receive a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is received according to at least one control message in the current scheduling instance, and where a second subset of the set of data messages is received according to one or more control messages received in a previous scheduling instance. The operation of 1715 may be performed according to the methods described herein. In some examples, aspects of the operation of 1715 may be performed by a data message interface as described with reference to FIGS. 8 - 11.

[0210] At 1720, the UE may receive a second subset of the set of data messages after a downlink shared channel scheduling delay that includes subframes for transmission of one or more bundled additional feedback responses during a previous scheduling instance. The operation of 1720 may be performed according to the methods described herein. In some examples, aspects of the operation of 1720 may be performed by a data message interface as described with reference to FIGS. 8 - 11.

[0211] In 1725, the UE may determine the feedback timing for each of a set of data messages, where the feedback timing for a first subset of the set of data messages is based on at least one control message, and where the feedback timing for a second subset of the set of data messages is based on one or more control messages received in a previous scheduling instance. The operation of 1725 may be performed according to the methods described herein. In some examples, aspects of the operation of 1725 may be performed by feedback timing components as described with reference to FIGS. 8 - 11.

[0212] In 1730, the UE may transmit one or more bundled feedback responses during an uplink subframe in a current scheduling instance and according to the feedback timing for each of a set of data messages. The operation of 1730 may be performed according to the methods described herein. In some examples, aspects of the operation of 1730 may be performed by feedback response components as described with reference to FIGS. 8 - 11.

[0213] FIG. 18 shows a flowchart illustrating a method 1800 for supporting scheduling instance scheduling for feedback responses, according to an aspect of the present disclosure. The operations of method 1800 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of method 1800 may be performed by a communication manager as described with reference to FIGS. 12 - 15. In some examples, the base station may execute a set of instructions for controlling functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0214] In 1805, the base station may transmit at least one control message within a set of downlink subframes in the current scheduling instance. The operation of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be performed by a control message interface as described with reference to FIGS. 12-15.

[0215] In 1810, the base station may transmit a set of data messages within a set of downlink subframes in the current scheduling instance, where a first subset of the set of data messages is transmitted according to at least one control message in the current scheduling instance, where a second subset of the set of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, where the feedback timing for the first subset of the set of data messages is based on at least one control message, and where the feedback timing for the second subset of the set of data messages is based on one or more control messages transmitted in a previous scheduling instance. The operation of 1810 may be performed according to the methods described herein. In some examples, aspects of the operation of 1810 may be performed by a data message interface as described with reference to FIGS. 12-15.

[0216] In 1815, the base station may receive one or more bundled feedback responses during the uplink subframes in the current scheduling instance and according to the feedback timing for each of the set of data messages. The operation of 1815 may be performed according to the methods described herein. In some examples, aspects of the operation of 1815 may be performed by a feedback response component as described with reference to FIGS. 12-15.

[0217] Note that the methods described herein are to describe possible implementations, that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0218] The techniques described herein may be used for various wireless communication systems such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. CDMA systems may implement wireless technologies such as CDMA2000, universal terrestrial radio access (UTRA). CDMA2000 may cover the IS-2000 standard, the IS-95 standard, and the IS-856 standard. The IS-2000 release is often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, high rate packet data (HRPD), etc. UTRA includes wideband CDMA (WCDMA (registered trademark)), and other variations of CDMA. TDMA systems may implement wireless technologies such as the global system for mobile communications (GSM).

[0219] An OFDMA system may implement wireless technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from a group called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from a group called the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and wireless technologies described herein as well as other systems and wireless technologies. Aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described by way of example and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, but the techniques described herein are applicable beyond the examples of LTE, LTE-A, LTE-A Pro, or NR.

[0220] Macro cells generally cover a relatively large geographical area (e.g., several kilometers in radius) and may enable unrestricted access by UEs subscribed to the services of a network provider. Small cells may be associated with low-power base stations as compared to macro cells, and small cells may operate in the same or different frequency bands as macro cells (e.g., licensed frequency bands, unlicensed frequency bands, etc.). Small cells may include, according to various examples, picocells, femtocells, and microcells. Picocells may, for example, cover a small geographical area and may enable unrestricted access by UEs subscribed to the services of a network provider. Femtocells may also cover a small geographical area (e.g., a home) and may provide restricted access by UEs associated with the femtocell (e.g., UEs within a closed subscriber group (CSG), UEs for users in a home, etc.). The eNB for macro cells may be called a macro eNB. The eNB for small cells may be called a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communication using one or more component carriers.

[0221] The wireless communication system described herein may support synchronous operation or asynchronous operation. In the case of synchronous operation, base stations may have similar scheduling instance timings, and transmissions from different base stations may be approximately time-aligned. In the case of asynchronous operation, base stations may have different scheduling instance timings, and transmissions from different base stations may not be time-aligned. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0222] The information and signals described in this specification may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0223] The various illustrative blocks and modules described in connection with the disclosure of this specification may be implemented or executed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0224] The functions described in this specification may be implemented in hardware, software executed by a processor, or any combination thereof. Software is broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. When implemented in software executed by a processor, the functions may be stored on a computer-readable medium as one or more instructions or code, or transmitted via a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various positions, including being distributed such that portions of the functions are implemented in different physical locations.

[0225] A computer-readable medium includes both non-transitory computer storage media and communication media including any medium that can facilitate transfer of a computer program from one place to another. The non-transitory storage media may be any available media that can be accessed by a general purpose computer or a dedicated computer. By way of example and not limitation, non-transitory computer-readable media may include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose computer or a dedicated computer or a general purpose processor or a dedicated processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, the terms disk and disc include CD, laser disk (registered trademark) (disc), optical disc (disc), digital versatile disc (DVD) (disc), floppy disk (disk), and Blu-ray (registered trademark) disc (disc), where disk typically magnetically reproduces data and disc optically reproduces data using a laser. Combinations of the above are also included within the scope of computer-readable media.

[0226] As used herein, including within the claims, "or" as used in a listing of items (e.g., a listing of items that ends with phrases such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase "based on" as used herein should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, the phrase "based on" as used herein shall be construed in the same manner as the phrase "at least partially based on". The term "and / or" as used herein, when used in a listing of two or more items, means that any one of the listed items may be employed alone or any combination of two or more of the listed items may be employed. For example, if a composition is described as including components A, B, and / or C, the composition can include A only, B only, C only, A and B in combination, A and C in combination, B and C in combination, or A, B, and C in combination.

[0227] In the accompanying drawings, like components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the like components. If only the first reference label is used herein, the description is applicable to any of the like components having the same first reference label regardless of the second reference label or any other subsequent reference labels.

[0228] The description set forth in this specification with respect to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The embodiments for carrying out the invention include specific details for bringing about an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the examples being described.

[0229] The description in this specification is provided to enable one skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure is not limited to the examples and designs described in this specification, and the broadest scope consistent with the principles and novel features disclosed herein should be accorded.

Description of Reference Numerals

[0230] 100 Wireless communication system 105 Base station 110 Geographical coverage area 115 User equipment (UE) 125 Communication link 130 Core network 132, 134 Backhaul link 200 Communication system 205, 210 Set of subframes 215 Control message 220 Data message 225 Subframe 230 Scheduling pattern 300 Scheduling instance, scheduling instance format 310 Scheduling instance 315 Scheduling Instance, Scheduling Instance Format 400 Table 405 HARQ-ACK Delay Field 410 Actual HARQ ID 415 Scheduling Delay 420 HARQ_ID Field 425 ACK Delay 430 Table 500 Table 505 HARQ-ACK Delay Field 510 Extended Scheduling Field, Extended Scheduling Bit 515 HARQ_ACK Delay Value 520 Scheduling Delay 600 Scheduling Pattern 605 ACK Delay 610 ACK Group 620 Scheduling Instance 805 Device 810 Receiver 815 Communication Manager 820 Transmitter 905 Device 910 Receiver 915 Communication Manager 920 Control Message Interface 925 Data Message Interface 930 Feedback Timing Component 935 Feedback Response Component 940 Transmitter 1005 Communication Manager 1010 Control Message Interface 1015 Data Message Interface 1020 Feedback Timing Component 1025 Feedback Response Component 1030 HARQ Component 1035 Scheduling Component 1100 System 1105 Device 1110 Communication Manager 1115 I / O Controller 1120 Transceiver 1125 Antenna 1130 Memory 1135 Code 1140 Processor 1145 Bus 1205 Device 1210 Receiver 1215 Communication Manager 1220 Transmitter 1305 Device 1310 Receiver 1315 Communication Manager 1320 Control Message Interface 1325 Data Message Interface 1330 Feedback Response Component 1335 Transmitter 1405 Communication Manager 1410 Control Message Interface 1415 Data Message Interface 1420 Feedback Response Component 1425 HARQ Component 1430 Scheduling Component 1435 Feedback Timing Component 1500 System 1505 Device 1510 Communication Manager 1515 Network Communication Manager 1520 Transceiver 1525 Antenna 1530 Memory 1535 Code 1540 Processor 1545 Inter - station Communication Manager 1550 Bus

Claims

1. A method for wireless communication in a user equipment (UE), comprising: receiving at least one control message within a set of downlink subframes in a current scheduling instance; receiving a plurality of data messages within the set of downlink subframes in the current scheduling instance, wherein a first subset of the plurality of data messages is received according to the at least one control message in the current scheduling instance, and a second subset of the plurality of data messages is received according to one or more control messages received in a previous scheduling instance; determining feedback timing for each of the plurality of data messages, wherein the feedback timing for the first subset of the plurality of data messages is based on the at least one control message, and the feedback timing for the second subset of the plurality of data messages is based on the one or more control messages received in the previous scheduling instance; transmitting, according to a feedback response group associated with each subframe, one or more bundled feedback responses bundled according to the feedback timing for each of the plurality of data messages, during uplink subframes in the current scheduling instance and according to the feedback timing for each of the plurality of data messages; identifying an extended scheduling field in a first control message among the at least one control message; and determining, based on a value of the extended scheduling field, a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message. A method further comprising the above steps.

2. The step of receiving the plurality of data messages is ​ ​ ​ ​ ​ After a downlink shared channel scheduling delay including a subframe for transmitting one or more bundled additional feedback responses during the previous scheduling instance, receiving the second subset of the plurality of data messages, or Receiving the second subset of the plurality of data messages after a downlink shared channel scheduling delay of seven subframes, or Receiving each of the plurality of data messages within each of at least 11 downlink subframes comprising the set of downlink subframes, or Further comprising receiving the plurality of data messages within the set of downlink subframes in the current scheduling instance, each downlink subframe of the set of downlink subframes including a data message of the plurality of data messages, The method according to claim 1.

3. The step of receiving the at least one control message is After transmitting the one or more bundled feedback responses during uplink subframes in the current scheduling instance, receiving the at least one control message for scheduling one or more additional data messages after a downlink shared channel scheduling delay that causes the one or more additional data messages to be scheduled in the next scheduling instance, or Comprising receiving a first control message of the at least one control message, the first control message scheduling a plurality of data messages, The method according to claim 1.

4. Processing a simultaneous hybrid automatic repeat request (HARQ) process related to the at least one control message received within the set of downlink subframes of the current scheduling instance and the one or more control messages received in the previous scheduling instance The method according to claim 1, further comprising.

5. Identifying a hybrid automatic repeat request (HARQ) identifier (ID) field in a first control message among the at least one control message; Comparing a value of the HARQ ID field included in the first control message with a HARQ ID field threshold; The method according to claim 1, further comprising: **Claim 6** Identifying a hybrid automatic repeat request (HARQ) process identifier (ID) associated with each of the one or more control messages received in the previous scheduling instance; Identifying the HARQ process ID associated with the at least one control message in the current scheduling instance; The method according to claim 1, further comprising: the HARQ process ID associated with the one or more control messages received in the previous scheduling instance is different from the HARQ process ID associated with the at least one control message in the current scheduling instance. The method according to claim 1. **Claim 7** The step of receiving the plurality of data messages within the set of downlink subframes in the current scheduling instance comprises: Receiving more than 10 data messages within the set of downlink subframes in the current scheduling instance. The method according to claim 1. **Claim 8** The step of determining feedback timing for each of the plurality of data messages comprises: Determining a feedback delay for one of the plurality of data messages, such as 12 subframes or 13 subframes. The method according to claim 1. **Claim 9** The method according to claim 1, wherein the current scheduling instance is scheduled for enhanced machine type communication (eMTC). **Claim 10** A method for wireless communication at a base station, comprising: Transmitting at least one control message within a set of downlink subframes in a current scheduling instance; Transmitting a plurality of data messages within the set of downlink subframes in the current scheduling instance, A first subset of the plurality of data messages is transmitted according to the at least one control message in the current scheduling instance, a second subset of the plurality of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, feedback timing for the first subset of the plurality of data messages is based on the at least one control message, the feedback timing for the second subset of the plurality of data messages is based on the one or more control messages transmitted in the previous scheduling instance, steps; receiving, during an uplink subframe in the current scheduling instance and according to the feedback timing for each of the plurality of data messages, one or more bundled feedback responses bundled according to a feedback response group associated with each subframe; comprising the step of transmitting the at least one control message is transmitting an extended scheduling field in a first control message of the at least one control message; displaying a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message based on a value of the extended scheduling field; A method comprising

11. An apparatus for wireless communication in a user equipment (UE), means for receiving at least one control message within a set of downlink subframes in a current scheduling instance; means for receiving a plurality of data messages within the set of downlink subframes in the current scheduling instance, wherein a first subset of the plurality of data messages is received according to the at least one control message in the current scheduling instance, means for receiving a second subset of the plurality of data messages according to one or more control messages received in a previous scheduling instance; means for determining feedback timing for each of the plurality of data messages, wherein the feedback timing for the first subset of the plurality of data messages is based on the at least one control message, means for determining feedback timing for the second subset of the plurality of data messages based on the one or more control messages received in the previous scheduling instance; means for transmitting, during uplink subframes in the current scheduling instance and according to the feedback timing for each of the plurality of data messages, one or more bundled feedback responses bundled according to a feedback response group associated with each subframe; comprising means for identifying an extended scheduling field in a first control message among the at least one control message; means for determining a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message based on a value of the extended scheduling field; An apparatus further comprising.

12. The apparatus according to claim 11, further comprising means for performing the method according to any one of claims 2 to 8.

13. An apparatus for wireless communication in a base station, means for transmitting at least one control message within a set of downlink subframes in a current scheduling instance; means for transmitting a plurality of data messages within the set of downlink subframes in the current scheduling instance, wherein a first subset of the plurality of data messages is transmitted according to the at least one control message in the current scheduling instance, A second subset of the plurality of data messages is transmitted according to one or more control messages transmitted in a previous scheduling instance, The feedback timing for the first subset of the plurality of data messages is based on the at least one control message, means for the feedback timing for the second subset of the plurality of data messages being based on the one or more control messages transmitted in the previous scheduling instance; means for receiving one or more bundled feedback responses bundled according to a feedback response group associated with each subframe, during an uplink subframe in the current scheduling instance and according to the feedback timing for each of the plurality of data messages; comprising the means for transmitting the at least one control message, means for transmitting an extended scheduling field in a first control message of the at least one control message; means for displaying a downlink shared channel scheduling delay associated with the first control message, a hybrid automatic repeat request (HARQ) process identifier (ID) associated with the first control message, and a feedback delay associated with the first control message, based on a value of the extended scheduling field; An apparatus comprising. **Claim 14** A non-transitory computer-readable recording medium storing code for wireless communication, the code comprising instructions executable by a processor for performing the method according to any one of claims 1 to 10.

Images