Techniques for scheduling communication resources

Abstract

Techniques for wireless communications are described. Control information for pre-scheduling of communication resources can be received, and communications can be performed based on the control information using pre-scheduling techniques. A scheduling type for the control information can be determined using configuration information, an indication included in the control information, or both. A wireless device that is pre-scheduled for the communication resources can refrain from starting or restarting an inactivity timer based on the received control information. Further, the wireless device that is pre-scheduled for the communication resources can refrain from starting a retransmission timer based on the received control information. Additionally, the wireless device that is pre-scheduled for the communication resources can also refrain from transmitting a scheduling request based on a duration until a next instance of the pre-scheduled communication resources is expected to occur.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 501,873, filed October 14, 2021, entitled “TECHNIQUES FOR SCHEDULING COMMUNICATION RESOURCES”, filed by Meylan et al., which claims priority to U.S. Provisional Patent Application No. 63 / 093,065, filed October 16, 2020, entitled “TECHNIQUES FOR SCHEDULING COMMUNICATION RESOURCES”, which has been assigned to the assignee of this application. Technical Field

[0003] The following text relates to wireless communication, including techniques for scheduling communication resources. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)).

[0005] The base station can schedule communication resources (e.g., downlink resources or uplink resources) for the UE. The base station can indicate to the UE the set of communication resources that have been scheduled for the UE, and the base station and the UE can communicate with each other on the scheduled communication resources. Summary of the Invention

[0006] Techniques that support techniques for scheduling communication resources are described. Control information for pre-scheduling of communication resources can be received, and communications can be performed based on the control information using pre-scheduling techniques. A scheduling type for the control information can be determined using configuration information, an indication included in the control information, or both. A wireless device that is pre-scheduled for communication resources can refrain from starting or restarting an inactivity timer based on the received control information. Further, the wireless device that is pre-scheduled for communication resources can refrain from starting a retransmission timer based on the received control information. Additionally, the wireless device that is pre-scheduled for communication resources can also refrain from transmitting a scheduling request based on a duration until a next instance of the pre-scheduled communication resources is expected to occur.

[0007] A method for wireless communication at a user equipment (UE) is described. The method can include receiving control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources, and communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0008] An apparatus for wireless communication at a UE is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to receive control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources, and communicate using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus can include means for receiving control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources, and means for communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0010] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code can include instructions executable by a processor to receive control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources, and communicate using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0011] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the control information can be received in a downlink control information message, and the method, apparatuses, and non-transitory computer- readable medium can further include operations, features, means, or instructions for decoding the downlink control information message, and determining that the pre-scheduling type can be associated with the control information based on an indicator included in the decoded downlink control information message.

[0012] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the control information can be received in a downlink control information message, and the method, apparatuses, and non-transitory computer- readable medium can further include operations, features, means, or instructions for identifying an index of a slot, symbol, or resource block for a control channel or a shared channel in which the downlink control information message can be received or an uplink transmission scheduled by the downlink control information message can be performed, and determining that the pre-scheduling type can be associated with the downlink control information message based on the index of the slot, the symbol, or the resource block.

[0013] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the control information can be received in a downlink control information message, and the method, apparatuses, and non-transitory computer- readable medium can further include operations, features, means, or instructions for receiving radio resource control information indicating a configuration for the pre- scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information that can be associated with the pre-scheduling type, and determining that the pre-scheduling type can be associated with the downlink control information message based on the configuration and a location of the downlink control information message in a control channel or a location of the shared channel.

[0014] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining a scheduling type of the control information or the uplink transmission, and determining whether to start an inactivity timer based on the determined scheduling type.

[0015] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from starting an inactivity timer after receiving the control information based on the control information being associated with the pre-scheduling type, and refraining from restarting the inactivity timer after receiving the control information based on the control information being associated with the pre-scheduling type.

[0016] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying a discontinuous reception on interval, determining that the control information can be received in a first portion of the discontinuous reception on interval, and refraining from starting or restarting an inactivity timer based on receiving the control information in the first portion of the discontinuous reception on interval.

[0017] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying a discontinuous reception on interval, determining that the control information can be received in a second portion of the discontinuous reception on interval, and starting or restarting an inactivity timer based on receiving the control information in the second portion of the discontinuous reception on interval.

[0018] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from starting a retransmission timer after receiving the control information based on the control information being associated with the pre-scheduling type.

[0019] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from starting a retransmission timer after receiving the control information based on an indicator included in the control information.

[0020] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from starting a retransmission timer after receiving the control information based on a radio resource control configuration.

[0021] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying a discontinuous reception on duration interval, determining that the control information can be received in a first portion of the discontinuous reception on duration interval, and refraining from starting or restarting a retransmission timer based on receiving the control information in the first portion of the discontinuous reception on duration interval.

[0022] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying a discontinuous reception on duration interval, determining that the control information can be received in a second portion of the discontinuous reception on duration interval, and starting or restarting a retransmission timer based on receiving the control information in the second portion of the discontinuous reception on duration interval.

[0023] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from transmitting a request for uplink resources based on the set of uplink resources being scheduled by the control information.

[0024] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining a first duration associated with transmitting the request for uplink resources and being scheduled with the requested uplink resources, determining a second duration until the set of uplink resources can be scheduled by the control information, and refraining from transmitting the request for uplink resources based on the second duration being less than the first duration.

[0025] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining a duration until a second set of uplink resources can be scheduled by a second control information of the pre-scheduling type, and refraining from transmitting a request for uplink resources based on the duration being less than a threshold.

[0026] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the threshold can be based on a second duration associated with transmitting the request for uplink resources and being scheduled with the requested uplink resources.

[0027] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the threshold can be based on a quality of service of a set of data at the UE that triggers the scheduling request.

[0028] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information that can be associated with the pre-scheduling type, determining a timing for which uplink resources are scheduled in response to a transmitted scheduling request, and determining whether to transmit a scheduling request based on the timing and the configuration for the pre-scheduling type.

[0029] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving radio resource control information indicating recurring uplink resource locations configured for the UE and that the pre-scheduling type can be associated with the recurring uplink resource locations, where receiving the control information includes receiving medium access control information indicating that one or more of the recurring uplink resource locations include the set of uplink resources.

[0030] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining a scheduling type associated with the control information from a set of multiple scheduling types, where the set of multiple scheduling types includes a first pre-scheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of the one or more requests for uplink resources, a second pre-scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource locations indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources, a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for uplink resources, and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource locations indicated by the fourth scheduling type.

[0031] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the pre-scheduling type dynamically schedules uplink resources without receiving a request for uplink resources.

[0032] A method for wireless communication at a base station is described. The method can include selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE, and transmitting control information scheduling the set of uplink resources for the UE according to the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0033] An apparatus for wireless communication at a base station is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to select a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE, and transmit control information scheduling the set of uplink resources for the UE according to the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0034] Another apparatus for wireless communication at a base station is described. The apparatus can include means for selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE, and means for transmitting control information scheduling the set of uplink resources for the UE according to the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0035] A non-transitory computer-readable medium storing code for wireless communications at a base station is described. The code can include instructions executable by a processor to select a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE, and transmit control information scheduling the set of uplink resources for the UE according to the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0036] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for scheduling the set of uplink resources using the pre-scheduling type based on the selection, and generating a downlink control information message based on using the pre-scheduling type, the downlink control information message including an indication that the downlink control information message can be associated with the pre-scheduling type, where transmitting the control information includes transmitting the downlink control information message.

[0037] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for scheduling the set of uplink resources using the pre-scheduling type based on the selection, and generating a downlink control information message based on using the pre-scheduling type, where transmitting the control information includes transmitting the downlink control information message using a slot index, a symbol index, or a resource block index of a control channel or a shared channel that is associated with the pre-scheduling type.

[0038] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency, or any combination thereof for receiving control information that can be associated with the pre-scheduling type.

[0039] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting radio resource control information indicating recurring uplink resource locations configured for the UE and that the pre-scheduling type can be associated with the recurring uplink resource locations, where transmitting the control information includes transmitting medium access control information indicating that one or more of the recurring uplink resource locations includes the set of uplink resources.

[0040] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining the pre-scheduling type from a set of multiple scheduling types, the set of multiple scheduling types including: a first pre-scheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of the one or more requests for uplink resources; a second pre-scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource locations indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources; a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource locations indicated by the fourth scheduling type.

[0041] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the control information can be transmitted based on a discontinuous reception cycle configured for the UE. BRIEF DESCRIPTION OF DRAWINGS

[0042] Figure 1 An example of a wireless communication system that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure.

[0043] Figure 2 An example of a wireless communication system that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure.

[0044] Figure 3An example of a timing diagram that supports techniques for scheduling communication resources is shown.

[0045] Figure 4 An example of a timing diagram that supports techniques for scheduling communication resources is shown.

[0046] Figure 5 An example of a process flow that supports techniques for scheduling communication resources is shown.

[0047] Figure 6 And 7 A block diagram of a device that supports techniques for scheduling communication resources is shown.

[0048] Figure 8 A block diagram of a communications manager that supports techniques for scheduling communication resources is shown.

[0049] Figure 9 A diagram of a system including a device that supports techniques for scheduling communication resources is shown.

[0050] Figure 10 And 11 A block diagram of a device that supports techniques for scheduling communication resources is shown.

[0051] Figure 12 A block diagram of a communications manager that supports techniques for scheduling communication resources is shown.

[0052] Figure 13 A diagram of a system including a device that supports techniques for scheduling communication resources is shown.

[0053] Figure 14 And 15 A flow diagram illustrating a method that supports techniques for scheduling communication resources is shown. DETAILED DESCRIPTION

[0054] A scheduling device (e.g., a base station) can schedule communication resources for wireless devices to perform communications. In some examples, a base station can dynamically schedule uplink resources for a wireless device by sending a scheduling message to the wireless device after receiving a request for resources from the wireless device. In such cases, the base station can be referred to as using a "dynamic scheduling technique." In some examples, a base station can schedule uplink resources by allocating a set of recurring uplink resources to a wireless device before receiving a request from the wireless device. In such cases, the base station can be referred to as using a "semi-static scheduling technique." In some examples, a base station can dynamically schedule uplink resources by sending an unsolicited scheduling message to a wireless device before receiving a request from the wireless device, the unsolicited scheduling message allocating a set of resources to the wireless device. In such cases, the scheduling can be referred to as using a "pre-scheduling technique."

[0055] A wireless device (e.g., a user equipment (UE)) can be configured with a discontinuous reception (DRX) cycle. During a first interval of the DRX cycle (which can be referred to as a "DRX off interval"), the wireless device can not be scheduled with communication resources, and the wireless device can enter an inactive state. During a second interval (which can be referred to as a "DRX on interval"), the wireless device can be scheduled with communication resources, and the wireless device can enter an active state to search for scheduling messages (which can also be referred to as "scheduling grants"). In some examples, the wireless device can remain in the active state after the end of the DRX on interval, e.g., if the wireless device is scheduled with communication resources that occur in a subsequent DRX off interval. In some examples, the wireless device uses an inactivity timer in conjunction with the end of the DRX on interval to determine when to return to the inactive state. In some cases, the wireless device starts the inactivity timer upon receiving a scheduling grant and remains in the active state until the end of the DRX on interval and the inactivity timer expires. In some examples, a scheduling device can schedule communication resources according to a DRX cycle configured for a wireless device, e.g., the scheduling device can schedule communication resources (or a set of initial communication resources) that occur within a DRX on interval.

[0056] A wireless device (e.g., a UE) can also be configured to support one or more hybrid automatic repeat request (HARQ) processes. In some examples, the wireless device starts a retransmission timer after receiving a scheduling grant (e.g., after waiting for a HARQ round trip duration). When the retransmission timer is started, the wireless device can enter and remain in the active state until the retransmission timer expires, e.g., to receive a retransmission of data. In some examples, the wireless device remains in the active state until the end of the DRX on interval, the inactivity timer expires, and the retransmission timer expires.

[0057] In some examples, a wireless device can start an inactivity timer and / or a retransmission timer after receiving a scheduling grant associated with a dynamic scheduling technique (which can also be referred to as a “dynamic grant”) or after receiving a scheduling grant associated with a pre-scheduling technique (which can also be referred to as a “pre-scheduling grant”). Thus, even though a pre-scheduling grant schedules only uplink resources that occur during a DRX ON interval configured for a receiving device, the receiving device can restart an inactivity timer and / or a retransmission timer after receiving the pre-scheduling grant. Moreover, the receiving device can be unable to determine when (or if) the scheduling device will issue a next pre-scheduling grant. Thus, even though a scheduling request occurs in an uplink resource that occurs after an uplink resource scheduled by an upcoming pre-scheduling grant, the receiving device can send a scheduling request to the scheduling device instead of waiting for the upcoming pre-scheduling grant.

[0058] To prevent a receiving device from unnecessarily extending an amount of time that the receiving device is in an active state, a scheduling device can indicate that a scheduling message includes a pre-scheduling grant, and the receiving device can not start (or restart) an inactivity timer after determining that the scheduling message includes the pre-scheduling grant. Moreover, to prevent a receiving device from unnecessarily increasing signaling overhead for uplink scheduling, a scheduling device can indicate a pre-scheduling grant configuration for a receiving device that indicates when a pre-scheduling grant is scheduled to occur.

[0059] In some examples, a receiving device can receive control information that schedules an uplink resource for the receiving device. The receiving device can determine a scheduling type (e.g., dynamic, semi-static, pre-scheduled, etc.) associated with the control information. In some examples, the receiving device determines that the control information includes a pre-scheduling grant based on an indicator of the scheduling type included in the control information (e.g., in a downlink control information (DCI) message) or in previously and currently received control information (e.g., in medium access control (MAC) messages and radio resource control (RRC) messages). In some examples, the receiving device determines that the control information includes a pre-scheduling grant based on a format (e.g., a DCI format) for the control information. In some examples, the receiving device determines that the control information includes a pre-scheduling grant based on an index of a slot, symbol, or resource block in which the control information is received.

[0060] In some examples, the receiving device can perform a DRX operation based on determining that the scheduling message includes the pre-scheduled grant. For example, the receiving device can refrain from starting or restarting an inactivity timer after receiving the control information based on determining that the scheduling message includes the pre-scheduled grant. By not starting or continuing the inactivity timer, the receiving device can enter an inactive state more quickly than if the inactivity timer were started or restarted. Similarly, the receiving device can perform a HARQ operation based on determining that the scheduling message includes the pre-scheduled grant. For example, the receiving device can refrain from starting a retransmission timer after receiving the control information based on determining that the scheduling message includes the pre-scheduled grant. By not starting the retransmission timer, the receiving device can refrain from entering an active state.

[0061] In some examples, a transmitting device can transmit control information to a receiving device indicating a pre-scheduled configuration for the receiving device. The control information can indicate a periodicity at which a pre-scheduled grant can be transmitted to the receiving device, an offset for the pre-scheduled grant, a frequency location, or any combination thereof. The receiving device can use the determined configuration to determine when an upcoming pre-scheduled grant is to be transmitted, a location of the pre-scheduled grant within a time interval, a frequency location of the pre-scheduled grant, or any combination thereof. Prior to transmitting a scheduling request (SR), the receiving device can determine a duration until a next pre-scheduled grant is to be transmitted, and in some examples, the receiving device can refrain from transmitting the SR if the duration is below a threshold. By determining whether to transmit the SR based on determining when the next pre-scheduled grant is to be transmitted, the receiving device can avoid increasing signaling overhead associated with scheduling uplink transmissions.

[0062] Aspects of the disclosure are first described in the context of a wireless communications system. Aspects of the disclosure are also described in the context of timing diagrams and process flows. Aspects of the disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts that relate to techniques for scheduling communications resources, and the operations of those aspects are described with reference to these diagrams.

[0063] Figure 1 An example of a wireless communications system 100 that supports techniques for scheduling communications resources is shown in accordance with various aspects of the disclosure. The wireless communications system 100 can include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 can 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 examples, the wireless communications system 100 can support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices, or any combination thereof.

[0064] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, within which UE 115 and base station 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographical area where base station 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0065] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or another network device), such as... Figure 1 As shown.

[0066] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or another interface). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0067] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station transceiver, radio base station, access point, radio transceiver, node B, evolved node B (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), home node B, home evolved node B, or some other suitable term.

[0068] A UE 115 can include or can be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” can also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 can also include or can be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 can include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which can be implemented in various objects such as appliances, or vehicles, meters, or various

[0069] The UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115 and base stations 105 that can sometimes act as relays or Figure 1 as shown.

[0070] The UEs 115 and the base stations 105 can wirelessly communicate with one another via one or more communication links 125 over one or more carriers. The term “carrier” can refer to a set of radio frequency spectrum resources (e.g., frequency resources, time resources, code resources, and / or

[0071] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Extended OFDM (DFT-S-OFDM). In a system employing MCM, a resource element can consist of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and 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, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0072] It can be in the basic unit of time (which can be, for example, T) s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N f The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0073] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0074] A subframe, a slot, a mini-slot, or a symbol can be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and can be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system 100 can be dynamically selected (e.g., in the form of a burst of shortened TTIs (sTTIs)).

[0075] Physical channels can be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel can be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel can be defined by multiple symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information according to one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. An aggregation level for a control channel candidate can refer to a quantity of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets can include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets configured for sending control information to a specific UE 115.

[0076] In some examples, a base station 105 can be movable and therefore provide communication coverage for a moving geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communications system 100 can include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0077] The wireless communications system 100 can be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 can be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. UEs 115 can be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions). Ultra-reliable communications can include private communications or group communications and can be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions can include prioritization of services, and the mission critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission critical, and ultra-reliable low- latency can be used interchangeably herein.

[0078] In some examples, UEs 115 can also be able to communicate directly with each other using a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communications can be within the geographic coverage area 110 of a base station 105. Other UEs 115 in such a group can be outside the geographic coverage area 110 of a base station 105 or be otherwise unable to receive transmissions from a base station 105. In some examples, groups of the UEs 115 communicating via D2D communications can utilize a one-to-many (1 :M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.

[0079] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or 5G core (5GC), which can include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets to and from user equipment (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the core network 130. User IP packets can be transferred through the user plane entity, which can provide IP address allocation as well as other functions. The user plane entity can be connected to the IP services 150 for one or more network operators. The IP services 150 can include access to the Internet, Intranet(s), an IP multimedia subsystem (IMS), or a packet- switched streaming service.

[0080] Some of the network devices, such as a base station 105, can include subcomponents such as an access network entity 140, which can be an example of an access node controller (ANC). Each access network entity 140 can communicate with UEs 115 through one or more other access network transmission entities 145, which can be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transmission entity 145 can include one or more antenna panels. In some configurations, various functions of each access network entity 140 or base station 105 can be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105).

[0081] The wireless communications system 100 can operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0082] Wireless communications system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communications system 100 can employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency spectrum band, such as the 5 GHz industrial, scientific and medical (ISM) band. When operating in unlicensed frequency spectrum bands, devices such as base stations 105 and UEs 115 can employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed frequency spectrum bands can be based on a carrier aggregation configuration in which a component carrier operates in a licensed frequency spectrum band (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0083] Base stations 105 or UEs 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station 105 or a UE 115 can be co-located within one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a base station 105 can be located in different geographic locations. A base station 105 can have an antenna array with a number of rows and columns of antenna ports that the base station 105 can use to support beamforming of communications to or from a UE 115. Similarly, a UE 115 can have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels can support radio frequency beamforming of signals transmitted via antenna ports.

[0084] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer a beam of energy in the manner of an antenna beam. The beams can be formed by combining signals transmitted by antennas of the antenna elements of an antenna array in such a way that the antenna elements act as a single antenna with a directionality pattern, which can be predictable. The beams can be formed for transmission or reception, respectively, and can be referred to as transmission beams or reception beams. The beams can be formed by adjusting signals transmitted or received by the antenna elements of the antenna array such that the signals transmitted or received by the antenna elements constructively interfere with each other while destructively interfering with signals transmitted or received by other antenna elements. The adjustments can include amplitude adjustments, phase adjustments, or both. The adjustments can be made in accordance with a direction of the beam relative to the antenna array, which can be determined based on a direction of arrival of received signals or a direction of departure of transmitted signals.

[0085] Wireless communications system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP -based. A Radio Link Control (RLC) layer can perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer can perform priority handling and multiplexing of logical channels into transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both, to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or core network 130, which supports radio bearers for user plane data. At the physical layer, transport channels can be mapped to physical channels.

[0086] The UEs 115 and the base stations 105 can support retransmissions of data to increase the likelihood that data is received successfully. HARQ feedback is one technique used to increase the likelihood that data is received correctly over a communication link 125. HARQ can include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device can support same-slot HARQ feedback, where the device can provide HARQ feedback in a specific time slot for data received in a previous time slot. In other cases, the device can provide HARQ feedback in a subsequent time slot or according to some other timing.

[0087] The base stations 105 can assign a set of uplink resources to a UE 115 and indicate a location of the set of uplink resources to the UE 115. The UE 115 can use the uplink resources to transmit uplink communications to the base station 105. The process by which resources are assigned and indicated to a UE 115 can also be referred to as scheduling. The base station 105 can schedule the UE 115 using control information (e.g., RRC information, DCI, or both). In some examples, the UE 115 can request that the base station 105 schedule the UE 115 for uplink communications. To request to be scheduled, the UE 115 can transmit an SR to the base station 105. The UE 115 can also transmit a buffer status report (BSR) to the base station 105 indicating an amount of data that the UE 115 has to transmit to the base station 105. In some examples, the base station 105 can schedule an amount of uplink resources sufficient to support transmission of the amount of data indicated by the UE 115.

[0088] In some examples, the base station 105 can dynamically schedule the UE 115 using DCI signaling, e.g., after receiving an SR from the UE 115. In such cases, the base station 105 can transmit a DCI message indicating a set of uplink resources allocated to the UE 115. To schedule the UE 115 a second time, the base station 105 can transmit another DCI message indicating another set of uplink resources. The other set of uplink resources can use different frequency resources than the first set of uplink resources. In some examples, the base station 105 can continue to transmit DCI messages scheduling the UE 115 for uplink resources until the amount of data indicated by the UE 115 in a BSR has been transmitted. Dynamically scheduling the UE 115 for uplink communications can prevent the base station 105 from committing uplink resources that can not be used to the UE 115, that is, the base station 105 can allocate an amount of uplink resources having a capacity that matches (or nearly matches) the size of the data to be transmitted from the UE 115. Signaling for dynamically scheduling uplink resources can be referred to as dynamic grant. Further, the uplink resources that are dynamically scheduled can be referred to as dynamic uplink resources.

[0089] In some examples, the base station 105 can semi-statically schedule the UE 115 using a combination of RRC and DCI signaling. In such cases, the base station 105 can transmit an RRC message indicating uplink resource locations configured for the UE 115. For example, the RRC message can indicate a set of recurring uplink resource locations, where uplink resources occurring during the set of recurring uplink resource locations can be allocated to the UE 115 if activated. To activate the semi-static uplink resources, the base station 105 can transmit a single DCI message to the UE 115 indicating that uplink resources occurring within the set of recurring uplink resource locations are allocated to the UE 115. The UE 115 can determine that uplink resources corresponding to the set of recurring uplink resource locations are allocated to the UE 115 for an indeterminate amount of time (e.g., until receiving a DCI message deactivating the semi-static uplink resources), while uplink resources dynamically scheduled by the DCI message can be deterministic. Semi-static scheduling can result in a preemptive scheduling of the UE 115 for uplink communications based on the UE 115’s expected uplink activity. Preemptively scheduling the UE 115 for uplink communications can reduce (relative to dynamic scheduling) the number of SRs transmitted from the UE 115 to the base station 105, thereby reducing signaling overhead associated with uplink scheduling. Signaling for semi-statically scheduling uplink resources can be referred to as configured grant. Further, the uplink resources that are semi-statically scheduled can be referred to as semi-static uplink resources.

[0090] In some examples, base station 105 can dynamically and preemptively schedule UE 115 using DCI signaling. In such cases, base station 105 can transmit a DCI message that schedules a set of uplink resources for UE 115. Base station 105 can transmit the DCI message without knowing or receiving an indication that UE 115 has data, but expecting that UE 115 has data to transmit to base station 105. The size of the set of uplink resources scheduled by base station 105 can be based on an estimate of the amount of data that UE 115 must transmit to base station 105. The signaling for dynamically and preemptively scheduling uplink resources can be referred to as a pre-scheduling grant. The pre-scheduling grant can provide the benefits of a configured grant (e.g., reduced signaling overhead for uplink scheduling) without the adverse effects of a configured grant (e.g., commitment of resources). Further, the uplink resources that are dynamically and preemptively scheduled can be referred to as pre-scheduled resources.

[0091] Wireless communications system 100 can support techniques for conserving energy at UEs 115. In some examples, wireless communications system 100 can use a discontinuous scheduling technique that enables UEs 115 to enter an inactive (or sleep state) during a predetermined interval during which base station 105 is refrained from scheduling communication resources for UE 115. In some examples, UE 115 can be configured with a DRX cycle having a first interval (which can be referred to as a DRX off) during which (initial) communication resources can not be scheduled for UE 115 and UE 115 enters an inactive state. The DRX cycle can also have a second interval (which can be referred to as a DRX on) during which (initial) communication resources can be scheduled for UE 115 and UE 115 enters an active state. During the DRX on interval, UE 115 can monitor control resources (e.g., physical downlink control channel (PDCCH) resources) for DCI messages intended for UE 115.

[0092] In some examples, the UE 115 can use an inactivity timer (which can be referred to as a drx-InactivityTimer) to remain in an active state after the end of a DRX on-interval, e.g., to support downlink and / or uplink communications that extend longer than the DRX on-interval. In such cases, the UE 115 can start the inactivity timer after receiving a DCI message, and can restart the inactivity timer if a subsequent DCI message is received before the inactivity expires or the end of the DRX on-interval. In some examples, after the inactivity timer is started or restarted, the expiration of the inactivity timer can occur after the end of the DRX on-interval, and the UE 115 can remain in an active state until the DRX on-interval has ended and the inactivity timer has expired. In some examples, the UE 115 can restart the inactivity timer each time a DCI message is received (assuming the DCI messages are not separated by a duration that exceeds the length of the inactivity timer), thereby remaining in an active state until the occurrence of the last scheduled communication resource.

[0093] In some examples, when using semi-static scheduling, the base station 105 can semi-statically schedule recurring communication resources for the UE 115 that fall within the DRX on-interval without transmitting any DCI messages. Thus, the UE 115 can use the semi-static communication resources without starting or restarting the inactivity timer. When using dynamic scheduling, the base station 105 can dynamically schedule a set of communication resources using corresponding DCI messages, and can schedule communication resources that occur in the DRX off-interval to support the amount of data to be transmitted to / from the UE 115. Similarly, when using pre-scheduling, the base station 105 can dynamically schedule a set of communication resources using corresponding DCI messages. However, in some examples, the base station 105 can refrain from pre-scheduling communication resources that occur within the DRX off-interval, that is, the base station can only pre-schedule communication resources that occur within the DRX on-interval.

[0094] The wireless communications system can also support techniques for improving reliability of communications between wireless devices (e.g., base stations 105 and UEs 115), such as HARQ techniques. In some examples, a wireless device (e.g., a UE 115) can initiate a HARQ retransmission timer (which can be referred to as drx-RetransmissionTimerUL) after performing an uplink transmission scheduled by a scheduling grant. In some examples, the wireless device can initiate the HARQ retransmission timer after a HARQ round trip duration (which can be referred to as drx-HARQ-RTT-TimerUL) from an end of the uplink transmission scheduled by the scheduling grant has expired (e.g., has reached a threshold value). After initiating the HARQ retransmission timer, the UE 115 can enter an active state until the HARQ retransmission timer expires. While the UE 115 is in the active state, the base station 105 can schedule a retransmission. In some examples, additional HARQ retransmissions can have little benefit, for example, when the additional HARQ retransmissions are incompatible with latency requirements for the data packet. In some examples, additional HARQ retransmissions can be beneficial, for example, when the data packet has relaxed latency requirements.

[0095] In some examples, a wireless device can initiate an inactivity timer and / or a retransmission timer after receiving a dynamic grant or after receiving a pre-scheduled grant, for example, based on being unable to distinguish between the dynamic grant and the pre-scheduled grant. Accordingly, the receiving device can restart the inactivity timer and / or the retransmission timer after receiving the pre-scheduled grant, even though the pre-scheduled grant only schedules uplink resources that occur during a DRX ON interval configured for the receiving device, thereby unnecessarily extending an amount of time that the receiving device operates in an active state. Further, the receiving device can be unable to determine when (or if) the scheduling device will issue a next pre-scheduled grant. Accordingly, the receiving device can send a scheduling request to the scheduling device instead of waiting for the upcoming pre-scheduled grant, even though the scheduling request produces an uplink transmission that occurs after uplink resources scheduled by the upcoming pre-scheduled grant, thereby increasing signaling overhead for uplink scheduling and decreasing resource utilization for the system.

[0096] To prevent the receiving device from unnecessarily extending an amount of time that the receiving device is in an active state, the scheduling device can indicate that a scheduling message includes (or is) a pre-scheduled grant, and the receiving device can refrain from initiating (or restarting) an inactivity timer after determining that the scheduling message includes (or is) the pre-scheduled grant. Further, to prevent the receiving device from unnecessarily increasing signaling overhead for uplink scheduling, the scheduling device can indicate a pre-scheduled grant configuration for the receiving device that indicates when the pre-scheduled grant is scheduled to occur.

[0097] In some examples, a receiving device can receive control information (e.g., RRC information, DCI, or a combination thereof) that schedules an uplink resource for the receiving device. The receiving device can determine a scheduling type (e.g., dynamic, semi-static, pre-scheduled, and / or the like) associated with the control information. In some examples, the receiving device determines that the control information includes (or is) a pre-scheduled grant based on an indicator of the scheduling type included in the control information (e.g., in a DCI message) or in previously and currently received control information (e.g., in MAC messages and RRC messages). In some examples, the receiving device determines that the control information includes (or is) a pre-scheduled grant based on a format (e.g., a DCI format) for the control information. In some examples, the receiving device determines that the control information includes (or is) a pre-scheduled grant based on an index of a slot, symbol, or resource block in which the control information is received.

[0098] In some examples, the receiving device can perform a DRX operation based on determining that the scheduling message includes (or is) a pre-scheduled grant. For example, the receiving device can refrain from starting or restarting an inactivity timer after receiving the control information based on determining that the scheduling message includes (or is) a pre-scheduled grant. By not starting or continuing the inactivity timer, the receiving device can enter an inactive state more quickly as compared to a case where the inactivity timer is started or restarted. Similarly, the receiving device can perform a HARQ operation based on determining that the scheduling message includes (or is) a pre-scheduled grant. For example, the receiving device can refrain from starting a retransmission timer after receiving the control information based on determining that the scheduling message includes (or is) a pre-scheduled grant. By not starting the retransmission timer, the receiving device can refrain from entering an active state.

[0099] In some examples, a transmitting device can transmit control information to a receiving device indicating a pre-scheduled configuration for the receiving device. The control information can indicate a periodicity at which a pre-scheduled grant can be transmitted to the receiving device, an offset for the pre-scheduled grant, a frequency location, or any combination thereof. The receiving device can use the determined configuration to determine when an upcoming pre-scheduled grant is to be transmitted, a location of the pre-scheduled grant within a time interval, a frequency location of the pre-scheduled grant, or any combination thereof. Prior to transmitting an SR, the receiving device can determine a duration until a next pre-scheduled grant is to be transmitted, and in some examples, the receiving device can refrain from transmitting the SR if the duration is below a threshold. By determining whether to transmit an SR based on determining when a next pre-scheduled grant is to be transmitted, the receiving device can avoid increasing signaling overhead associated with scheduling uplink transmissions.

[0100] Figure 2 An example of a wireless communication subsystem that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure.

[0101] Wireless communication subsystem 200 can be an example of aspects of wireless communication system 100 and can include a base station 205 and a UE 215. Base station 205 and UE 215 can be examples of the base station and UE described in Figure 1 Figure 1 Base station 205 and UE 215 can communicate with each other within coverage area 210, as described in

[0102] In some examples, base station 205 can configure a DRX cycle for UE 215 that configures a DRX off and a DRX on interval for UE 215. Base station 205 can refrain from scheduling (initial) communication resources for UE 215 during the DRX off interval and can schedule (initial) communication resources for UE 215 during the DRX on interval. Thus, UE 215 can enter an inactive state during the DRX off interval and an active state during the DRX on interval to search for scheduling messages. In some examples, UE 215 can remain in the active state after the end of the DRX on interval if an inactivity timer has not expired. Base station 205 can also configure one or more HARQ processes for UE 215 that support retransmission of data. Base station 205 can also indicate a length of a HARQ retransmission timer to UE 215 that indicates a period of time during which a retransmission of a data packet can be transmitted. In some examples, UE 215 can remain in the active state after the end of the DRX on interval and / or expiration of the inactivity timer if the HARQ retransmission timer has not expired.

[0103] ​In some examples, the base station 205 can transmit scheduling information 220 to the UE 215 via the downlink 225. The scheduling information 220 can be used to dynamically or semi-statically schedule uplink resources for the UE 215. The scheduling information 220 can also be used to dynamically and preemptively schedule uplink resources for the UE 215. In some examples, RRC signaling, DCI signaling, or any combination thereof can be used to convey the scheduling information 220 to the UE 215. The scheduling information 220 can also include configuration information for one or more scheduling types (which can also be referred to as scheduling schemes, scheduling modes, or scheduling configurations). For example, the scheduling information 220 can indicate a set of uplink resource locations (in time) configured for the UE 215 (e.g., by indicating a periodicity and offset parameter for the uplink resource locations), which can be activated by a DCI trigger, such as if a semi-static scheduling type is used. In some examples, the pre-scheduling information indicates a time at which the network is planning (with a high likelihood) to provide an opportunity for uplink transmission, independent of a previous request in a scheduling request for uplink resources transmitted from the UE 215. In some examples, the scheduling information 220 can indicate a set of downlink control resource locations configured for the UE 215 to receive a pre-scheduling grant (e.g., by indicating a periodicity, offset parameter, frequency location, symbol index, slot index, resource block index, or any combination thereof for the downlink control resource locations), such as if a pre-scheduled scheduling type is used. The pre-scheduling grant can be or include control information that is used to preemptively schedule uplink resources for the UE (e.g., based on a determination that the UE can have data to transmit, without receiving a scheduling request from the UE, and / or the like). The scheduling information 220 can also indicate an indication of a scheduling type (e.g., dynamic, semi-static, or pre-scheduled) associated with a scheduling grant received at the UE 215.

[0104] In some examples, the UE 215 determines whether the scheduling information 220 is being used to dynamically, semi-statically, or dynamically and preemptively schedule uplink resources for the UE 215. In some examples, the UE 215 determines the scheduling type associated with received control information based on an indication included in the received or previous control information, a format used for the control information, a type of control information, an index of a slot, symbol, or resource block in which the control information is received, and / or the like.

[0105] The UE 215 can change its behavior based on whether the scheduling information is dynamic, semi-static, or pre-scheduled type. For example, the UE 215 can refrain from starting or restarting an inactivity timer after performing an uplink transmission using pre-scheduled uplink resources (e.g., based on performing the uplink transmission at a time indicated by the pre-scheduled grant). In some examples, the UE 215 can refrain from starting or restarting the inactivity timer after receiving a DCI message if the DCI message is being used to pre-schedule uplink resources for the UE 215. By refraining from starting or restarting the inactivity timer, the UE 215 can enter an inactive state earlier, and thus conserve energy at the UE 215, as compared to a case where the inactivity timer has already been started or restarted. Similarly, the UE 215 can refrain from starting a HARQ retransmission timer after receiving a DCI message if the DCI message is being used to pre-schedule uplink resources for the UE 215. By refraining from starting the HARQ retransmission timer, the UE 215 can avoid entering an active state, and thus conserve energy at the UE 215.

[0106] The UE 215 can also determine whether to transmit an SR based on the received configuration information for pre-scheduled type. For example, after generating data (e.g., uplink data 230) at the UE 215 and triggering an SR, the UE 215 can determine when a next pre-scheduled grant will be received, e.g., based on the periodicity and offset information received from the base station 205. If the UE 215 determines that the next pre-scheduled grant is scheduled to be received within a threshold duration of the grant that will be obtained via the SR, the UE 215 can refrain from transmitting the SR, and instead wait for the pre-scheduled grant to transmit the uplink data 230 via the uplink 240. If the next pre-scheduled grant is scheduled to be received after the end of the threshold duration, the UE 215 can transmit a scheduling request 235 to the base station 205 via the uplink 240 to obtain uplink resources for transmitting the uplink data 230. By waiting for the pre-scheduled grant, the UE 215 can reduce overhead signaling to obtain uplink resources from the base station 205, can avoid unnecessary issuance of uplink resources, and can enable the UE 215 to transmit the uplink data 230 more quickly (as compared to a case where the UE 215 uses uplink resources obtained with the scheduling request 235).

[0107] Figure 3 An example of a timing diagram that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure. The timing diagram 300 can depict the transmission of control and data signals over wireless communication resources with reference to a configured DRX cycle and / or HARQ process.

[0108] In some examples, a receiving device (e.g., a UE) is configured with a DRX cycle having periodic on-intervals punctured with periodic off-intervals. During an on-interval, the receiving device can be in an active state, where the receiving device is actively listening for signals transmitted from another device (e.g., a base station). During an off-interval, the receiving device can be in an inactive state, where the receiving device can disable circuitry used to receive signals. The receiving device can remain in the active state during the start of the off-interval if an inactivity timer at the receiving device has not expired.

[0109] In some examples, the receiving device receives a control message in a first downlink resource 305 during a first on-interval 345. The first downlink resource 305 can be a downlink control channel resource (e.g., a PDCCH resource). The control message can be a DCI message associated with a dynamic scheduling type (or dynamic grant) and transmitted in response to an SR from the receiving device. The control message can also indicate that a first uplink resource 310 is scheduled for the receiving device. The first uplink resource 310 can be an uplink control resource (e.g., a physical uplink control channel (PUCCH) resource) and / or an uplink data resource (e.g., a physical uplink shared channel (PUSCH) resource). In some examples, the control message can also schedule a downlink data resource (e.g., a physical downlink shared channel (PDSCH) resource). The receiving device can determine that the DCI message comprises (or is) a dynamic grant and can start an inactivity timer at a first time 335. The inactivity timer can not be set to expire until after the end of the first on-interval 345. Further, at a third time 342, the receiving device can start a retransmission timer associated with the first HARQ process. In some examples, the receiving device can start the retransmission timer after transmitting an uplink transmission during a resource scheduled by the DCI message. In some examples, the receiving device can wait to start the retransmission timer after waiting for a HARQ round trip time. The receiving device can enter the active state while the retransmission timer is active. The retransmission timer can start after the end of the first on-interval 345.

[0110] The receiving device can receive a second control message in the second downlink resource 315. The second control message can similarly be a DCI message associated with a dynamic scheduling type, and can indicate that a second uplink resource 320 is scheduled for the receiving device. The second control message can be transmitted to schedule additional uplink resources based on the BSR received from the receiving device. The receiving device can determine that the second DCI message includes (or is) a dynamic grant, and can restart (or re-start) the inactivity timer at a second time 340. In some examples, the second control message is the last of a plurality of control messages transmitted to the receiving device, and the receiving device can enter an inactive state upon expiration of the inactivity timer within an off-interval 350. Further, at a fourth time 344, the receiving device can start a second retransmission timer associated with the first HARQ process. In some examples, the receiving device can wait to start the second retransmission timer until after a round-trip time expires. The second retransmission timer can start after an end of the first on-interval 345.

[0111] In some examples, the receiving device receives a third control message in a third downlink resource 325. The third control message can be a DCI message associated with a pre-scheduling type, and can have been preemptively transmitted by the scheduling device in anticipation of a need for uplink resources at the receiving device (e.g., based on a determination that the receiving device can have data to transmit to the scheduling device). The control message can also indicate that a third uplink resource 330 is scheduled for the receiving device. In some examples, the third uplink resource 330 occurs entirely within a second on-interval 355. In some examples, the receiving device receives a plurality of control messages in the second on-interval 355, each control message having a pre-scheduling type. In this regard and with reference to FIG. 3, the receiving device can receive a first control message 310, a second control message 315, and a third control message 325. The first control message 310 can be a DCI message associated with a dynamic scheduling type, the second control message 315 can be a DCI message associated with a dynamic scheduling type, and the third control message 325 can be a DCI message associated with a pre-scheduling type. Figure 4 Techniques used by the receiving device to determine that the third control message includes (or is) a pre-scheduling grant are described in more detail.

[0112] Based on determining that the third control message includes (or is) a pre-scheduling grant, or based on determining that the uplink transmission has a pre-scheduling type, the receiving device can refrain from starting the inactivity timer. Similarly, the receiving device can refrain from starting the retransmission timer. As a result, the receiving device can return to an inactive state at an end of the second on-interval 355. Further, during a retransmission interval, the receiving device can not return to an active state. By not starting the inactivity, the receiving device can return to an inactive state more quickly as compared to a case in which the inactivity had been started upon receiving the third control message. By not starting the retransmission timer, the receiving device can avoid entering an active state during a retransmission interval as compared to a case in which the retransmission timer had been started after performing the uplink transmission scheduled by the third control message.

[0113] In some examples, the receiving device can receive the dynamic grant prior to or concurrently with receiving the pre-scheduled grant. In such cases, the receiving device can start the inactivity upon receiving the dynamic grant and refrain from restarting the inactivity timer (or continue running the inactivity timer) upon receiving the pre-scheduled grant. Further, the receiving device can start the retransmission timer upon performing the transmission scheduled by the dynamic grant and refrain from starting another retransmission timer upon performing the retransmission scheduled by the pre-scheduled grant. By not restarting the inactivity timer, the receiving device can return to the inactive state more quickly than if the inactivity timer had been restarted. By not starting the second retransmission timer, the receiving device can avoid re-entering the active state.

[0114] In some examples, the receiving device can receive the pre-scheduled grant prior to receiving the dynamic grant. In such cases, the receiving device can refrain from starting the inactivity timer and / or the retransmission timer until receiving the dynamic grant. By starting the inactivity timer upon receiving the dynamic grant, the receiving device can remain in the active state to ensure that the receiving device receives the downlink data scheduled by the dynamic grant and / or utilizes any uplink control resources scheduled by the dynamic grant. Similarly, by starting the retransmission timer upon receiving the second control message, the receiving device can enter the active state during the retransmission interval to ensure that the retransmission of the data packet is received. This operation can enable the pre-scheduled and dynamic scheduling types to cooperatively be used to schedule a sufficient amount of resources for the receiving device, while ensuring that the receiving device remains in the active state for a sufficient amount of time.

[0115] In some examples, upon receiving the pre-scheduled grant, the receiving device can determine whether to start or restart the inactivity timer and / or start the retransmission timer based on when the pre-scheduled grant is received within the on-interval. In some examples, the receiving device can refrain from starting (or restarting) the inactivity timer and / or the retransmission timer based on receiving the pre-scheduled grant in a first portion of the on-interval (e.g., a first third of the on-interval or a first half of the on-interval). And the receiving device can start (or restart) the inactivity timer and / or the retransmission timer based on receiving the pre-scheduled grant in a second portion of the interval (e.g., a second half of the on-interval or a last third of the on-interval), in which case the pre-scheduled grant can (or more likely) schedule the communication resources that occur in a subsequent off-interval.

[0116] Figure 4 An example of a timing diagram that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure. The timing diagram 400 can depict the location of uplink resources that can potentially be scheduled by an SR relative to the location of uplink resources that can be scheduled by a periodic pre-scheduled grant.

[0117] In some examples, at time 403, an event that triggers transmission of an SR can occur at the UE, e.g., arrival of uplink data can exceed or a threshold associated with data generated at the UE for transmission to the base station. After the event occurs, the UE can determine whether to use an SR resource occurring in an upcoming SR occasion, such as SR occasion 405, to send a scheduling request to obtain a grant of uplink resources or to wait until the pre-scheduled uplink resources are scheduled to occur. In some examples, SR occasions are configured to occur periodically for the UE. Thus, the UE can determine a duration of time between time 403 and an occurrence of SR occasion 405 (this duration of time can be referred to as an SR occasion delay). The UE can also determine a second duration of time between an occurrence of SR occasion 405 and an occurrence of a control resource (e.g., a PDCCH resource) to be scheduled in response to the SR sent in SR occasion 405, such as SR control resource 410 (the second duration of time can be referred to as an SR occasion to PDCCH delay). Additionally, the UE can determine a third duration of time between an occurrence of SR control resource 410 and an uplink data resource (e.g., a PUSCH resource) to be scheduled by downlink control information included in SR control resource 410, e.g., SR uplink resource 415 (the third duration of time can be referred to as a PDCCH to PUSCH delay). Additionally or alternatively, the UE can determine an SR to PUSCH delay that indicates a fourth duration of time between SR occasion 405 and SR uplink resource 415.

[0118] In some examples, the UE determines the SR occasion to PDCCH delay, the PDCCH to PUSCH delay, and / or the SR occasion to PUSCH delay based on past measurements or resource configurations for the UE. The UE can use the determined durations to predict an SR delay 420, which can indicate a duration between an occurrence of an event that triggers a SR and a grant of uplink resources. The UE can similarly determine a duration between an occurrence of an event that triggers a SR and a grant of pre-scheduled uplink resources, such as pre-scheduled uplink resources 430. In some examples, the UE can determine a first duration between an occurrence of an SR trigger event and an occurrence of a control resource, such as pre-scheduled control resources 425. In some examples, the UE can determine a second duration between the pre-scheduled control resources 425 and the uplink data resources, such as pre-scheduled control resources 430 (e.g., based on past measurements, configuration information, etc.). The UE can use the determined durations to predict a pre-scheduled delay 435. The threshold can depend on a quality of service (QoS) of the traffic that triggers the scheduling request. For example, for real-time traffic, the threshold can be smaller compared to delay-tolerant traffic. By basing the threshold on the QoS of the traffic, the wireless communication system can balance power and latency considerations with scheduling request resource loading.

[0119] In some examples, the UE compares a length of the SR delay 420 to a length of the pre-scheduled delay 435 to determine whether to transmit a SR in the SR occasion 405 or to refrain from transmitting a SR in the SR occasion 405. If the UE refrains from transmitting a SR, the UE can wait until the pre-scheduled uplink resources 430 are scheduled to transmit uplink data that triggered the SR event at time 403. In some examples, the UE can transmit a SR in the SR occasion 405 based on determining that a difference between the pre-scheduled delay 435 and the SR delay 420 exceeds a threshold. In some examples, the UE can transmit a SR in the SR occasion 405 based on determining that a difference between a duration between time 403 and the SR control resources 410 and a duration between time 403 and the pre-scheduled control resources 425 exceeds a threshold.

[0120] In some examples, the UE can refrain from transmitting a SR in the SR occasion 405 based on determining that a difference between the pre-scheduled delay 435 and the SR delay 420 is below a threshold. In some examples, the UE can refrain from transmitting a SR in the SR occasion 405 after determining that the difference is below a threshold, even if the SR uplink resources occur before the pre-scheduled uplink resources. In some examples, the UE can transmit a SR in the SR occasion 405 based on determining that a difference between a duration between time 403 and the SR control resources 410 and a duration between time 403 and the pre-scheduled control resources 425 is below a threshold.

[0121] Figure 5 An example of a process flow that supports techniques for scheduling communication resources, in accordance with various aspects of the present disclosure is shown.

[0122] Process flow 500 can be performed by base station 505 and UE 515, which can be examples of the base stations or UEs described above with reference to FIGs. 1-4. In some examples, process flow 500 illustrates an example sequence of operations performed to support scheduling communication resources. For example, process flow 500 depicts operations for determining a scheduling type of a scheduling message and communicating based on the determined scheduling type. Figure 1 And 2 It is to be understood that one or more of the operations described in process flow 500 can be performed earlier or later in the process, omitted, replaced, supplemented, or performed in combination with another operation. Moreover, additional operations described herein that are not included in process flow 500 can be included.

[0123] It is to be understood that one or more of the operations described in process flow 500 can be performed earlier or later in the process, omitted, replaced, supplemented, or performed in combination with another operation. Moreover, additional operations described herein that are not included in process flow 500 can be included.

[0124] At arrow 520, base station 505 and UE 515 can exchange control messages (e.g., RRC messages or MAC control elements) including configuration information for communications between base station 505 and UE 515. In some examples, base station 505 can indicate that a pre-scheduling type is enabled to schedule communication resources for UE 515. In some examples, base station 505 can also indicate configuration details for the pre-scheduling type. For example, base station 505 can indicate a periodicity at which a pre-scheduling grant will be transmitted to UE 515. Base station 505 can also indicate an offset for the pre-scheduling grant to indicate an offset for transmitting the pre-scheduling grant. UE 515 can use the periodicity and the offset to identify a starting slot for the pre-scheduling grant and a time between pre-scheduling grants. In some examples, base station 505 can indicate that a scheduling grant received in a particular slot (e.g., in a second slot of an interval) is associated with pre-scheduling.

[0125] In some examples, base station 505 transmits an RRC message to configure uplink resource locations that can be semi-statically scheduled for UE 515. The RRC message can include a periodicity and an offset for the uplink resource locations. The RRC message can also include an indicator indicating that the uplink resource locations are to be used for pre-scheduling rather than semi-static scheduling. In such cases, a control information trigger (e.g., a MAC-CE) can be used to activate a subset of the uplink resource locations for pre-scheduling.

[0126] In some examples, the base station 505 transmits an RRC message configuring a length of a retransmission timer for pre-scheduled transmissions that is different from a length of a retransmission timer for dynamically scheduled transmissions. The retransmission timer associated with pre-scheduling can be referred to as drx-RetransmissionTimerULPSG. In some examples, the duration of the pre-scheduled retransmission timer can be shorter than the duration of the dynamic retransmission timer. Similarly, the base station 505 can transmit an RRC message configuring a length of a pre-scheduled inactivity timer that is different from a length of a dynamic inactivity timer. The pre-scheduled inactivity timer can be referred to as drx-InactivityTimerPSG. In some examples, the duration of the pre-scheduled inactivity timer can be shorter than the duration of the dynamic inactivity timer.

[0127] At block 525, the base station 505 can determine a scheduling type to use for scheduling uplink control resources for the UE 515. In some examples, the base station 505 selects a pre-scheduling type, a dynamic scheduling type, a semi-static scheduling type, or any combination thereof.

[0128] At arrow 530, the base station 505 can transmit one or more scheduling messages to the UE 515. In some examples, one or more of the scheduling messages are DCI messages. In some examples, one or more of the scheduling messages are MAC-CEs. Further, one or more of the scheduling messages can be associated with a dynamic scheduling type (can be a dynamic grant), and one or more of the scheduling messages can be associated with a pre-scheduling type (can be a pre-scheduled grant). In some examples, the base station 505 transmits a DCI message associated with a dynamic scheduling type after receiving a SR (and in some examples, a BSR) from the UE 515. In some examples, the base station 505 transmits a scheduling message associated with a pre-scheduling type based on a pre-scheduling period configured for the UE 515.

[0129] In some examples, if a pre-scheduling message schedules an uplink resource occurring during a DRX off interval configured for the UE 515, the base station 505 can also transmit one or more dynamic scheduling messages with, before, or after the pre-scheduling message to trigger an inactivity timer at the UE 515. In some examples, the one or more dynamic scheduling messages can not schedule any resources for the UE 515.

[0130] At block 535, the UE 515 can determine a scheduling type associated with the one or more scheduling messages received at the UE 515. In some examples, the UE 515 determines that a received scheduling message has a pre-scheduled type based at least in part on an indication included in the scheduling message (e.g., based on an indicator included in a DCI message). In some examples, the UE 515 determines that a received scheduling message has a pre-scheduled type based at least in part on a format used for the scheduling message (e.g., based on a DCI format used for a DCI message). In some examples, the UE 515 determines that a received scheduling message has a pre-scheduled type based at least in part on an index of a slot in which the scheduling message is received, e.g., if the scheduling message is received in a second slot of a frame and / or during a first portion of a DRX on interval.

[0131] At block 540, the UE 515 can manage an inactivity timer based on the scheduling type determined for the received scheduling message. In some examples, after determining that a received DCI message includes (or is) a dynamic grant, the UE 515 can start (or restart) an inactivity timer and monitor for additional DCI information until the inactivity timer expires.

[0132] In some examples, after determining that a received DCI message includes (or is) a pre-scheduled grant, the UE 515 can refrain from starting an inactivity timer. In some examples, after determining that a received DCI message includes (or is) a pre-scheduled grant, the UE 515 can start a pre-scheduled inactivity timer, which can have a shorter duration than a dynamic inactivity timer. If an inactivity timer has already been started, the UE 515 can continue running the inactivity timer (or not restart the inactivity timer) after receiving the pre-scheduled grant. In some examples, if an inactivity timer has already been started, the UE 515 can continue running a dynamic inactivity timer and start (or restart) a pre-scheduled inactivity timer after receiving the pre-scheduled grant.

[0133] In some examples, after receiving a MAC-CE, the UE 515 can refrain from starting an inactivity timer. In some examples, after receiving a MAC-CE, the UE 515 can start a pre-scheduled inactivity timer. If an inactivity timer has already been started, the UE 515 can continue running the inactivity timer (or not restart the inactivity timer) after receiving the pre-scheduled grant. In some examples, if an inactivity timer has already been started, the UE 515 can continue running a dynamic inactivity timer and start (or restart) a pre-scheduled inactivity timer after receiving the pre-scheduled grant.

[0134] In some examples, the UE 515 can refrain from starting or restarting the inactivity timer based on determining that the pre-scheduled grant is received in a first portion of the DRX on-duration (e.g., a first third of the DRX on-duration, a first half of the DRX on-duration, or a middle third of the DRX on-duration). In some examples, the UE 515 can start or restart the inactivity timer based on determining that the pre-scheduled grant is received in a second portion of the DRX on-duration (e.g., a middle third of the DRX on-duration, a last third of the DRX on-duration, a second half of the DRX on-duration). In some examples, the UE 515 can start or restart the pre-scheduled inactivity timer based on determining that the pre-scheduled grant is received in a second portion of the DRX on-duration (e.g., a middle third of the DRX on-duration, a second half of the DRX on-duration, or a last third of the DRX on-duration).

[0135] The UE 515 can also manage the HARQ round trip timer and / or the HARQ retransmission timer based on the scheduling type determined for the received scheduling message. In some examples, after determining that the received DCI message includes (or is) a dynamic grant, the UE 515 can start the retransmission timer and monitor for a retransmission until the retransmission timer expires.

[0136] In some examples, after determining that the received DCI message includes (or is) a pre-scheduled grant, the UE 515 can refrain from starting the round trip timer and / or the retransmission timer. In some examples, after determining that the received DCI message includes (or is) a pre-scheduled grant, the UE 515 can refrain from starting the retransmission timer based on receiving a DCI message that includes an indication that the UE 515 is commanded not to start the retransmission timer for the pre-scheduled grant, e.g., by indicating that there is no HARQ retransmission associated with the received pre-scheduled grant. In some examples, after determining that the received DCI message includes (or is) a pre-scheduled grant, the UE 515 can refrain from starting the retransmission timer based on receiving an RRC message that commands the UE 515 not to start the retransmission timer for the pre-scheduled grant.

[0137] In some examples, after determining that the received DCI message includes (or is) a pre-scheduled grant, the UE 515 can start a pre-scheduled retransmission timer that is shorter than a dynamic retransmission timer, e.g. drx-RetransmissionTimerULPSG. In such cases, the UE 515 can start the pre-scheduled retransmission timer after the HARQ round trip timer expires.

[0138] In some examples, after determining that the received DCI message includes (or is) a prescheduled grant, the UE 515 can determine whether to start a retransmission timer (e.g., a dynamic retransmission timer or a prescheduled transmission timer) based on a location within a DRX on-interval of the prescheduled grant. For example, the UE 515 can refrain from starting the retransmission timer based on the prescheduled grant occurring in a first portion of the DRX on-interval (e.g., a first third of the DRX on-interval, a first half of the DRX on-interval, or a middle third of the DRX on-interval). Alternatively, the UE 515 can start the retransmission timer based on the prescheduled grant occurring in a second portion of the DRX on-interval (e.g., a middle third of the DRX on-interval, a second half of the DRX on-interval, or a last third of the DRX on-interval).

[0139] At block 545, the UE 515 can identify uplink resources based on the received scheduling message. In some examples, the UE 515 can identify uplink data resources and / or uplink control resources based on the received scheduling message. In some examples, if the received scheduling message includes (or is) a dynamic grant, the UE 515 can identify uplink resources that occur during a DRX off-interval configured for the UE 515. In some examples, if the received scheduling message includes (or is) a prescheduled grant, the UE 515 can determine that the uplink resources occur within a DRX on-interval configured for the UE 515.

[0140] At arrow 550, the UE 515 can transmit uplink information to the base station 505 using the uplink resources identified based on the one or more received scheduling messages. In some examples, the UE 515 can transmit control information on uplink control resources (e.g., PUCCH resources) and data on uplink data resources (e.g., PUSCH resources) indicated by the one or more received scheduling messages. In some examples, if a prescheduled message is received, the UE 515 can transmit all uplink information to the base station 505 during a DRX on-interval configured for the UE 515.

[0141] At block 555, the UE 515 can determine that an event that triggers transmission of an SR has occurred. In some examples, the UE 515 can determine that an SR event has occurred when an amount of data stored in a buffer exceeds a threshold value. In some examples, the UE 515 can determine that an SR event has occurred when time-sensitive data is generated at the UE 515.

[0142] At block 560, the UE 515 can identify when a next pre-scheduled grant is scheduled to be transmitted from the base station 505, e.g., based on previously received periodicity and offset information for the pre-scheduled type. The UE 515 can then determine whether to transmit a scheduling request or wait for the next pre-scheduled grant based on the configuration information. In some examples, the UE 515 can determine a duration until the next pre-scheduled grant is scheduled to be received. If the duration exceeds a threshold, the UE 515 can determine to transmit a scheduling request to the base station 505. If the duration is less than the threshold, the UE 515 can forgo transmission of the scheduling request and wait for the next pre-scheduled grant. In some examples, the duration is based at least in part on a time-sensitivity of the data to be transmitted, e.g., the duration can be shorter if the data is time-sensitive. In some examples, the UE 515 can determine whether to transmit a scheduling request based on whether a pre-scheduled grant will be received first or a dynamic scheduling grant triggered by the SR, e.g., if the pre-scheduled grant will be received before the dynamic scheduling grant, the UE 515 can wait for the pre-scheduled grant.

[0143] In some examples, the UE 515 can determine a difference between a time at which an uplink resource is to be scheduled by a pre-scheduled grant and a time at which resources can be scheduled in response to a scheduling request. In some examples, the UE 515 can determine a difference between a time at which a pre-scheduled grant is scheduled to be received and a time at which a dynamic grant is expected to be received in response to a scheduling request. In both cases, the UE 515 can determine whether to transmit an SR based on the difference, e.g., if the difference is greater than a threshold, the UE 515 can transmit the SR. In some examples, the threshold is based on a time-sensitivity of the data to be transmitted.

[0144] At arrow 565, if the UE 515 determines not to wait for the pre-scheduled grant, the UE 515 can transmit an SR to the base station 505 requesting that the base station 505 schedule uplink resources for the UE 515 to transmit data to the base station 505.

[0145] At block 570, if the UE 515 determines to wait for the pre-scheduled grant, the UE 515 can wait for the pre-scheduled grant to be transmitted by the base station 505.

[0146] At arrow 575, the base station 505 can transmit a second scheduling message to the UE 515. In some examples, the second scheduling message comprises (or is) a dynamic grant and is transmitted in response to a scheduling request received from the UE 515. In other examples, the second scheduling message comprises (or is) a pre-scheduled grant and is transmitted according to a pre-scheduled configuration.

[0147] At arrow 580, the UE 515 can transmit uplink information to the base station 505 using the uplink resources indicated by the received second scheduling message. In some examples, the UE 515 determines whether to start or restart the inactivity timer based on whether the scheduling message includes (or is) a dynamic grant or a prescheduled grant, as described herein.

[0148] In some examples, the UE 515 generates data in accordance with the prescheduled configuration. That is, the UE 515 can modify its operation such that (when possible) uplink data is generated to coincide with (or to be synchronized with) the occurrence of the prescheduled grant, e.g., the UE 515 can expedite data generation to occur prior to the prescheduled uplink resource occasion.

[0149] In some examples, the downlink scheduling message can similarly be configured as a prescheduled grant. That is, the base station 505 can transmit a downlink scheduling grant that causes similar behavior at the UE 515, which in some examples can be referred to as a downlink prescheduled grant. In some examples, if the base station 505 transmits a downlink prescheduled grant to the UE 515, the UE 515 can refrain from starting (or restarting) the inactivity timer upon receiving the downlink prescheduled grant. Upon receiving the downlink prescheduled grant, the UE 515 can start (or restart) the prescheduled inactivity timer. The UE 515 can not start the round trip timer and / or the retransmission timer after receiving the downlink prescheduled grant. Or the UE 515 can use the prescheduled retransmission timer after receiving the downlink prescheduled grant.

[0150] Figure 6 A block diagram 600 of a device 605 that supports techniques for scheduling communication resources is shown, in accordance with various aspects of the present disclosure. The device 605 can be an example of aspects of a UE 115 as described herein. The device 605 can include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0151] The receiver 610 can provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources). Information can be passed on to other components of the device 605. The receiver 610 can utilize a single antenna or a set of multiple antennas.

[0152] The transmitter 615 can provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels related to size-based neural network selection for autoencoder-based communications, data channels, information channels). In some examples, the transmitter 615 can be collocated with a receiver 610 in a transceiver component. The transmitter 615 can utilize a single antenna or a set of multiple antennas.

[0153] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof can be examples of means for performing various aspects of techniques for scheduling communication resources as described herein.

[0154] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof can be implemented in hardware (e.g., in communication management circuitry). The circuitry can include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (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 the present disclosure.

[0155] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof can be implemented in code (e.g., as communication management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof can be executed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices.

[0156] In some examples, the communication manager 620 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 can receive information from the receiver 610, transmit information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both, to receive information, transmit information, or perform various other operations as described herein.

[0157] The communications manager 620 can support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager 620 can be configured to provide or support a means for receiving control information that schedules a set of uplink resources for the UE in accordance with a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources. The communications manager 620 can be configured to provide or support a means for communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0158] By including or configuring the communications manager 620 in accordance with examples as described herein, the device 605 (e.g., a processor of the device 605 that controls or is otherwise coupled to the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof) can support techniques for reducing power consumption and signaling overhead associated with performing uplink communications.

[0159] Figure 7 A block diagram 700 of a device 705 that supports techniques for scheduling communication resources is shown in accordance with various aspects of the present disclosure. The device 705 can be an example of aspects of a device 605 or a UE 115 as described herein. The device 705 can include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0160] The receiver 710 can provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources). Information can be passed on to other components of the device 705. The receiver 710 can utilize a single antenna or a set of multiple antennas.

[0161] The transmitter 715 can provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources). In some examples, the transmitter 715 can be collocated with a receiver 710 in a transceiver component. The transmitter 715 can utilize a single antenna or a set of multiple antennas.

[0162] The device 705, or various components thereof, can be an example of means for performing various aspects of techniques for scheduling communication resources as described herein. For example, the communication manager 720 can include a scheduling component 725, a communication component 730, or any combination thereof. The communication manager 720 can be an example of aspects of the communication manager 620 as described herein. In some examples, the communication manager 720, or various components thereof, can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both, to receive information, transmit information, or perform various other operations as described herein.

[0163] According to examples as disclosed herein, the communication manager 720 can support wireless communication at a UE. The scheduling component 725 can be configured to provide or support a means for receiving control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources. The communication component 730 can be configured to provide or support a means for communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0164] Figure 8 A block diagram 800 of a communication manager 820 that supports techniques for scheduling communication resources in accordance with aspects of the present disclosure is shown. The communication manager 820 can be an example of aspects of a communication manager 620, a communication manager 720, or both as described herein. The communication manager 820, or various components thereof, can be an example of means for performing various aspects of techniques for scheduling communication resources as described herein. For example, the communication manager 820 can include a scheduling component 825, a communication component 830, a decoding component 835, a pre-scheduling component 840, a DRX component 845, a HARQ component 850, a SR component 855, or any combination thereof. Each of these components can communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0165] The communications manager 820 can support wireless communication at a UE in accordance with examples as disclosed herein. The scheduling component 825 can be configured as or otherwise support a means for receiving control information that schedules a set of uplink resources for the UE in accordance with a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources. The communications component 830 can be configured as or otherwise support a means for communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0166] In some examples, the control information is received in a downlink control information message, and the decoding component 835 can be configured as or otherwise support a means for decoding the downlink control information message. In some examples, the control information is received in a downlink control information message, and the scheduling component 825 can be configured as or otherwise support a means for determining that the pre-scheduling type is associated with the control information based on an indicator included in the decoded downlink control information message.

[0167] In some examples, the control information is received in a downlink control information message, and the pre-scheduling component 840 can be configured as or otherwise support a means for identifying an index of a slot, symbol, or resource block in which to receive the downlink control information message or perform an uplink transmission scheduled by the downlink control information message for a control channel or a shared channel. In some examples, the control information is received in a downlink control information message, and the pre-scheduling component 840 can be configured as or otherwise support a means for determining that the pre-scheduling type is associated with the downlink control information message based on the index of the slot, symbol, or resource block.

[0168] In some examples, the control information is received in a downlink control information message, and the pre-scheduling component 840 can be configured as or otherwise support a means for receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the pre-scheduling type. In some examples, the control information is received in a downlink control information message, and the pre-scheduling component 840 can be configured as or otherwise support a means for determining that the pre-scheduling type is associated with the downlink control information message based on the configuration and a location of the downlink control information message in a control channel or a location of a shared channel.

[0169] In some examples, the scheduling component 825 can be configured as or otherwise support a means for determining a scheduling type of control information or an uplink transmission. In some examples, the DRX component 845 can be configured as or otherwise support a means for determining whether to start an inactivity timer based on the determined scheduling type.

[0170] In some examples, the DRX component 845 can be configured as or otherwise support a means for refraining from starting the inactivity timer after receiving the control information based on the control information being associated with a pre-scheduling type. In some examples, the DRX component 845 can be configured as or otherwise support a means for refraining from restarting the inactivity timer after receiving the control information based on the control information being associated with a pre-scheduling type.

[0171] In some examples, the DRX component 845 can be configured as or otherwise support a means for identifying a discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for determining that the control information is received in a first portion of the discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for refraining from starting or restarting the inactivity timer based on receiving the control information in the first portion of the discontinuous reception on interval.

[0172] In some examples, the DRX component 845 can be configured as or otherwise support a means for identifying a discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for determining that the control information is received in a second portion of the discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for starting or restarting the inactivity timer based on receiving the control information in the second portion of the discontinuous reception on interval.

[0173] In some examples, the HARQ component 850 can be configured as or otherwise support a means for refraining from starting a retransmission timer after receiving the control information based on the control information being associated with a pre-scheduling type.

[0174] In some examples, the HARQ component 850 can be configured as or otherwise support a means for refraining from starting the retransmission timer after receiving the control information based on an indicator included in the control information.

[0175] In some examples, the HARQ component 850 can be configured as or otherwise support a means for refraining from starting the retransmission timer after receiving the control information based on a radio resource control configuration.

[0176] In some examples, the DRX component 845 can be configured as or otherwise support a means for identifying a discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for determining that control information is received in a first portion of the discontinuous reception on interval. In some examples, the HARQ component 850 can be configured as or otherwise support a means for refraining from starting or restarting a retransmission timer based on receiving the control information in the first portion of the discontinuous reception on interval.

[0177] In some examples, the DRX component 845 can be configured as or otherwise support a means for identifying a discontinuous reception on interval. In some examples, the DRX component 845 can be configured as or otherwise support a means for determining that control information is received in a second portion of the discontinuous reception on interval. In some examples, the HARQ component 850 can be configured as or otherwise support a means for starting or restarting a retransmission timer based on receiving the control information in the second portion of the discontinuous reception on interval.

[0178] In some examples, the SR component 855 can be configured as or otherwise support a means for refraining from transmitting a request for the set of uplink resources based on the set of uplink resources being scheduled by the control information.

[0179] In some examples, the SR component 855 can be configured as or otherwise support a means for determining a first duration associated with transmitting the request for the uplink resources and being scheduled the requested uplink resources. In some examples, the SR component 855 can be configured as or otherwise support a means for determining a second duration until the set of uplink resources will be scheduled by the control information. In some examples, the SR component 855 can be configured as or otherwise support a means for refraining from transmitting the request for the uplink resources based on the second duration being less than the first duration.

[0180] In some examples, the SR component 855 can be configured as or otherwise support a means for determining a duration until a second set of uplink resources will be scheduled by a second control information of a pre-scheduling type. In some examples, the SR component 855 can be configured as or otherwise support a means for refraining from transmitting the request for the uplink resources based on the duration being less than a threshold.

[0181] In some examples, the threshold is based on a second duration associated with transmitting the request for the uplink resources and being scheduled the requested uplink resources.

[0182] In some examples, the threshold is based on a quality of service of a set of data at the UE that triggered the scheduling request.

[0183] In some examples, the prescheduling component 840 can be configured as or otherwise support a means for receiving radio resource control information indicating a configuration for a prescheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the prescheduling type. In some examples, the SR component 855 can be configured as or otherwise support a means for determining a timing for uplink resources scheduled in response to the transmitted scheduling request. In some examples, the SR component 855 can be configured as or otherwise support a means for determining whether to transmit a scheduling request based on the timing and the configuration for the prescheduling type.

[0184] In some examples, the scheduling component 825 can be configured as or otherwise support a means for receiving radio resource control information indicating recurring uplink resource locations configured for the UE and that a prescheduling type is associated with the recurring uplink resource locations, where receiving the control information includes receiving medium access control information indicating that one or more of the recurring uplink resource locations include a set of uplink resources.

[0185] In some examples, the scheduling component 825 can be configured as or otherwise support a means for determining a scheduling type associated with the control information from a set of multiple scheduling types, where the set of multiple scheduling types includes: a first prescheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of one or more requests for uplink resources; a second prescheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource locations indicated by the second prescheduling type in anticipation of one or more requests for uplink resources; a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource locations indicated by the fourth scheduling type.

[0186] In some examples, the pre-scheduling type dynamically schedules the uplink resources without receiving a request for the uplink resources.

[0187] Figure 9 A diagram illustrates a system 900 including a device 905 that supports techniques for scheduling communication resources in accordance with various aspects of the present disclosure. The device 905 can be an example of or include the components of device 605, device 705, or a UE 115 as described herein. The device 905 can communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof. The device 905 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 910, an I / O controller 915, a transceiver 920, an antenna 925, memory 930, code 935, and a processor 940. These components can be in electronic communication or otherwise

[0188] The I / O controller 915 can manage input and output signals for the device 905. The I / O controller 915 can also manage peripherals not integrated into the device 905. In some cases, the I / O controller 915 can represent a physical connection or port to an external peripheral. In some cases, the I / O controller 915 can utilize an operating system such as iOS®, ANDROID®, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, OS X®, UNIX®,

[0189] In some cases, the device 905 can include the antenna 925. However, in some other cases, a device 905 can have more than one antenna, which can be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 920 can communicate bi-directionally, via one or more antennas, wired, or wireless links as described herein. For example, the transceiver 920 can represent a wireless transceiver and can communicate bi-directionally with another wireless transceiver. The transceiver 920 can also include a modem to modulate the packets and to provide the modulated packets to one or more antennas for transmission, and to demodulate packets received from one or more antennas. The transceiver 920, or the transceiver 920 and one or more antennas, can be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination thereof, or a component thereof, as described herein.

[0190] The memory 930 can include random access memory (RAM) and read-only memory (ROM). The memory 930 can store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 can be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 935 can not be directly executable by the processor 940 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 930 can include, among other things, a basic I / O system (BIOS), which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0191] The processor 940 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 can be configured to operate a memory array. In some other cases, a memory controller can be integrated into the processor 940. The processor 940 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting techniques for scheduling communication resources). For example, the device 905 or a component of the device 905 can include the processor 940 and the memory 930 coupled to the processor 940, the processor 940 and the memory 930 being configured to perform various functions described herein.

[0192] The communications manager 910 can support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager 910 can be configured to provide or support a means for receiving control information that schedules a set of uplink resources for the UE in accordance with a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources. The communications manager 910 can be configured to provide or support a means for communicating using the set of uplink resources based on the control information being associated with the pre-scheduling type.

[0193] In some examples, the communications manager 910 can be configured to perform or support performance of various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 920, the one or more antennas, or any combination thereof. Although the communications manager 910 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 910 can be supported by or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the processor 940 to cause the device 905 to perform various aspects of techniques for scheduling communication resources as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support performance of such operations.

[0194] Figure 10 A block diagram 1000 of a device 1005 that supports techniques for scheduling communication resources is shown, in accordance with aspects of the present disclosure. The device 1005 can be an example of aspects of a base station 105 as described herein. The device 1005 can include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0195] The receiver 1010 can provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources). Information can be passed on to other components of the device 1005. The receiver 1010 can utilize a single antenna or a set of multiple antennas.

[0196] The transmitter 1015 can provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels related to size-based neural network selection for autoencoder-based communications, data channels, information channels). In some examples, the transmitter 1015 can be collocated with the receiver 1010 in a transceiver component. The transmitter 1015 can utilize a single antenna or a set of multiple antennas.

[0197] The communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be examples of means for performing various aspects of techniques for scheduling communication resources as described herein.

[0198] In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be implemented in hardware (e.g., in communications management circuitry). The circuitry can include a processor, a DSP, an ASIC, a 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 the present disclosure.

[0199] Additionally or alternatively, in some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be executed by a general-purpose processor, a DSP, a CPU, an ASIC, a FPGA, or any combination of these or other programmable logic devices.

[0200] In some examples, the communications manager 1020 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 can receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to receive information, transmit information, or perform various other operations as described herein.

[0201] The communications manager 1020 can support wireless communication at a base station in accordance with examples as disclosed herein. For example, the communications manager 1020 can be configured to provide or support a means for selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE. The communications manager 1020 can be configured to provide or support a means for transmitting control information scheduling the set of uplink resources for the UE in accordance with the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0202] Figure 11 A block diagram 1100 of a device 1105 that supports techniques for scheduling communication resources in accordance with aspects of the present disclosure is shown. The device 1105 can be an example of aspects of a device 1005 or a base station 105 as described herein. The device 1105 can include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0203] The receiver 1110 can provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources). Information can be passed on to other components of the device 1105. The receiver 1110 can utilize a single antenna or a set of multiple antennas.

[0204] The transmitter 1115 can provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling communication resources based on automatic encoder based communications). In some examples, the transmitter 1115 can be collocated with the receiver 1110 in a transceiver component. The transmitter 1115 can utilize a single antenna or a set of multiple antennas.

[0205] The apparatus 1105, or various components of the apparatus 1105, can be an example of means for performing various aspects of techniques for scheduling communication resources as described herein. For example, the communications manager 1120 can include a base station scheduling component 1125, a transmission component 1130, or any combination thereof. The communications manager 1120 can be an example of aspects of the communications manager 1020 as described herein. In some examples, the communications manager 1120, or various components thereof, can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 can receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both, to receive information, send information, or perform various other operations as described herein.

[0206] The communications manager 1120 can support wireless communication at a base station in accordance with examples as disclosed herein. The base station scheduling component 1125 can be configured to provide or support a means for selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE. The transmission component 1130 can be configured to provide or support a means for transmitting control information scheduling the set of uplink resources for the UE in accordance with the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0207] By including or configuring the communications manager 1120 in accordance with examples as described herein, the apparatus 1105 can support techniques for reducing power consumption of a UE and reducing signaling overhead associated with performing uplink communications.

[0208] Figure 12 A block diagram 1200 illustrating a communications manager 1220 that supports techniques for scheduling communication resources in accordance with aspects of the present disclosure is shown. The communications manager 1220 can be an example of aspects of a communications manager 1020, a communications manager 1120, or both. The communications manager 1220, or various components thereof, can be an example of means for performing various aspects of techniques for scheduling communication resources as described herein. For example, the communications manager 1220 can include a base station scheduling component 1225, a transmission component 1230, a base station pre-scheduling component 1235, or any combination thereof. Each of these components can communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0209] The communications manager 1220 can support wireless communication at a base station in accordance with examples as disclosed herein. The base station scheduling component 1225 can be configured to provide or support a means for selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for the uplink resources from the UE. The transmission component 1230 can be configured to provide or support a means for transmitting control information, the control information scheduling the set of uplink resources for the UE in accordance with the selected pre-scheduling type, where the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0210] In some examples, the base station pre-scheduling component 1235 can be configured to provide or support a means for scheduling the set of uplink resources using the pre-scheduling type based on the selection. In some examples, the base station pre-scheduling component 1235 can be configured to provide or support a means for generating a downlink control information message based on using the pre-scheduling type, the downlink control information message including an indication that the downlink control information message is associated with the pre-scheduling type, where transmitting the control information includes transmitting the downlink control information message.

[0211] In some examples, the base station pre-scheduling component 1235 can be configured to provide or support a means for scheduling the set of uplink resources using the pre-scheduling type based on the selection. In some examples, the base station pre-scheduling component 1235 can be configured to provide or support a means for generating a downlink control information message based on using the pre-scheduling type, where transmitting the control information includes transmitting the downlink control information message using a slot index, a symbol index, or a resource block index of a control channel or a shared channel that is associated with the pre-scheduling type.

[0212] In some examples, the base station pre-scheduling component 1235 can be configured to provide or support a means for transmitting radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency, or any combination thereof for receiving control information associated with the pre-scheduling type.

[0213] In some examples, the base station scheduling component 1225 can be configured to provide or support a means for transmitting radio resource control information indicating a recurring uplink resource location configured for the UE and the pre-scheduling type being associated with the recurring uplink resource location, where transmitting the control information includes transmitting medium access control information indicating that one or more of the recurring uplink resource locations include the set of uplink resources.

[0214] In some examples, the base station scheduling component 1225 can be configured to provide or support a means for determining a pre-scheduling type from a set of multiple scheduling types, where the set of multiple scheduling types includes: a first pre-scheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of one or more requests for the uplink resources; a second pre-scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource locations in anticipation of one or more requests for the uplink resources; a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for the uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource locations.

[0215] In some examples, the control information is transmitted based on a discontinuous reception cycle configured for the UE.

[0216] Figure 13 A diagram illustrates a system 1300 including a device 1305 that supports techniques for scheduling communications resources in accordance with various aspects of the present disclosure. The device 1305 can be an example of or include the components of device 1005, device 1105, or a base station 105 as described herein. The device 1305 can communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof. The device 1305 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communication manager 1310, a network communications manager 1315, a transceiver 1320, an antenna 1325, memory 1330, code 1335, a processor 1340, and an inter-station communications manager 1345. These components can be in electronic communication or otherwise

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

[0218] In some cases, the device 1305 can include a single antenna 1325. However, in some other cases, the device 1305 can have more than one antenna, which can be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1320 can communicate bi-directionally, via one or more antennas, wired, or wireless links as described herein. For example, the transceiver 1320 can represent a wireless transceiver and can communicate bi-directionally with another wireless transceiver. The transceiver 1320 can also include a modem to modulate the packets and to demodulate packets received from one or more antennas, 1320 can be an example of a transmitter 1015, a transmitter 1115, a receiver 1010, a receiver 1110, or any combination thereof, or a component thereof, as described herein.

[0219] The memory 1330 can include RAM and ROM. The memory 1330 can store computer-readable, computer-executable code 1335 including instructions that, when executed by the processor 1340, cause the device 1305 to perform various functions described herein. The code 1335 can be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1335 can not be directly executable by the processor 1340 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 1330 can contain, among other things, a BIOS which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0220] The processor 1340 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 can be configured to operate a memory array using a memory controller. In some other cases, a memory controller can be integrated into the processor 1340. The processor 1340 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1330) to cause the device 1305 to perform various functions (e.g., functions or tasks in support of techniques for scheduling communication resources). For example, the device 1305 or a component of the device 1305 can include the processor 1340 and the memory 1330 coupled to the processor 1340, the processor 1340 and the memory 1330 being configured to perform various functions described herein.

[0221] Inter-site communication manager 1345 can manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1345 can coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1345 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0222] According to the examples disclosed herein, the communication manager 1310 can support wireless communication at a base station. For example, the communication manager 1310 can be configured to provide or support elements for selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type being used to pre-schedule a set of uplink resources for the UE before receiving one or more requests for uplink resources from the UE. The communication manager 1310 can be configured to provide or support elements for transmitting control information that schedules the set of uplink resources for the UE according to the selected pre-scheduling type, wherein the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information.

[0223] In some examples, the communication manager 1310 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 1320, one or more antennas, or any combination thereof. Although the communication manager 1310 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1310 may be supported or performed by the processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform various aspects of the techniques for scheduling communication resources as described herein, or the processor 1340 and memory 1330 may be otherwise configured to perform or support such operations.

[0224] Figure 14 A flowchart illustrating a method 1400 supporting techniques for scheduling communication resources according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be performed by, as described in reference... Figures 1 to 9 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively, the UE can use dedicated hardware to perform aspects of the described function.

[0225] At 1405, the method may include: receiving control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled before the UE sends one or more requests for uplink resources. The operation at 1405 can be performed according to the method described herein. In some examples, aspects of the operation at 1405 may be determined by reference to... Figure 8 The described scheduling component 825 is used for execution.

[0226] At 1410, the method may include: communicating using a set of uplink resources based on control information associated with a pre-scheduling type. The operation at 1410 can be performed according to the method described herein. In some examples, aspects of the operation at 1410 may be derived from, as referenced... Figure 8 The described communication component 830 is used to perform this.

[0227] Figure 15 A flowchart illustrating a method 1500 for scheduling communication resources, according to various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a base station or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 1 to 5 as well as Figures 10 to 13 The described base station 105 performs this function. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the described function. Alternatively, the base station may use dedicated hardware to perform aspects of the described function.

[0228] At 1505, the method may include: selecting a pre-scheduling type for scheduling uplink resources for the UE, the pre-scheduling type being used to pre-schedule a set of uplink resources for the UE before receiving one or more requests for uplink resources from the UE. The operation at 1505 can be performed according to the method described herein. In some examples, aspects of the operation at 1505 may be derived from, as referenced... Figure 12 The base station scheduling component 1225 described herein is used to perform this task.

[0229] At 1510, the method may include: transmitting control information that schedules a set of uplink resources for the UE according to a selected pre-scheduling type, wherein the selected pre-scheduling type associated with the control information is indicated based on transmitting the control information. The operation at 1510 can be performed according to the method described herein. In some examples, aspects of the operation at 1510 may be derived from, as referenced... Figure 12 The described sending component 1230 is used to execute this.

[0230] The following provides an overview of various aspects of this disclosure:

[0231] Aspect 1 : A method for wireless communication at a UE, comprising: receiving control information that schedules a set of uplink resources for the UE according to a pre-scheduling type, the set of uplink resources being pre-scheduled prior to the UE transmitting one or more requests for uplink resources; and communicating using the set of uplink resources based at least in part on the control information being associated with the pre-scheduling type.

[0232] Aspect 2: The method of aspect 1, wherein the control information is received in a downlink control information message, the method further comprising: decoding the downlink control information message; and determining that the pre-scheduling type is associated with the control information based at least in part on an indicator included in the decoded downlink control information message.

[0233] Aspect 3: The method of any of aspects 1-2, wherein the control information is received in a downlink control information message, the method further comprising: identifying an index of a slot, a symbol, or a resource block of a control channel or a shared channel in which the downlink control information message is received or an uplink transmission scheduled by the downlink control information message is performed; and determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the index of the slot, the symbol, or the resource block.

[0234] Aspect 4: The method of any of aspects 1-3, wherein the control information is received in a downlink control information message, the method further comprising: receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the pre-scheduling type; and determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the configuration and a location of the downlink control information message in a control channel or a location of the shared channel.

[0235] Aspect 5: The method of any of aspects 1-4, further comprising: determining a scheduling type of the control information or an uplink transmission; and determining whether to start an inactivity timer based at least in part on the determined scheduling type.

[0236] Aspect 6: The method of any of aspects 1-5, further comprising: refraining from starting an inactivity timer after receiving the control information based at least in part on the control information being associated with the pre-scheduling type; or refraining from restarting the inactivity timer after receiving the control information based at least in part on the control information being associated with the pre-scheduling type.

[0237] Aspect 7: The method of any of aspects 1 through 6, further comprising: identifying a discontinuous reception on interval; determining that the control information is received in a first portion of the discontinuous reception on interval; and refraining from starting or restarting an inactivity timer based at least in part on receiving the control information in the first portion of the discontinuous reception on interval.

[0238] Aspect 8: The method of any of aspects 1 through 7, further comprising: identifying a discontinuous reception on interval; determining that the control information is received in a second portion of the discontinuous reception on interval; and starting or restarting an inactivity timer based at least in part on receiving the control information in the second portion of the discontinuous reception on interval.

[0239] Aspect 9: The method of any of aspects 1 through 8, further comprising: refraining from starting a retransmission timer after receiving the control information based at least in part on the control information being associated with the pre-scheduling type.

[0240] Aspect 10: The method of any of aspects 1 through 9, further comprising: refraining from starting a retransmission timer after receiving the control information based at least in part on an indicator included in the control information.

[0241] Aspect 11: The method of any of aspects 1 through 10, further comprising: refraining from starting a retransmission timer after receiving the control information based at least in part on a radio resource control configuration.

[0242] Aspect 12: The method of any of aspects 1 through 11, further comprising: identifying a discontinuous reception on interval; determining that the control information is received in a first portion of the discontinuous reception on interval; and refraining from starting or restarting a retransmission timer based at least in part on receiving the control information in the first portion of the discontinuous reception on interval.

[0243] Aspect 13: The method of any of aspects 1 through 12, further comprising: identifying a discontinuous reception on interval; determining that the control information is received in a second portion of the discontinuous reception on interval; and starting or restarting a retransmission timer based at least in part on receiving the control information in the second portion of the discontinuous reception on interval.

[0244] Aspect 14: The method of any of aspects 1 through 13, further comprising: refraining from transmitting a request for uplink resources based at least in part on the set of uplink resources being scheduled by the control information.

[0245] Aspect 15: The method of Aspect 14, further comprising: determining a first duration associated with transmitting the request for uplink resources and being scheduled the requested uplink resources; determining a second duration until the set of uplink resources will be scheduled by the control information; and refraining from transmitting the request for uplink resources based at least in part on the second duration being less than the first duration.

[0246] Aspect 16: The method of any one of Aspects 1-15, further comprising: determining a duration until a second set of uplink resources will be scheduled by a second control information of the pre-scheduling type; and refraining from transmitting a request for uplink resources based at least in part on the duration being less than a threshold.

[0247] Aspect 17: The method of Aspect 16, wherein the threshold is based at least in part on a second duration associated with transmitting the request for uplink resources and being scheduled the requested uplink resources.

[0248] Aspect 18: The method of any one of Aspects 16-17, wherein the threshold is based at least in part on a quality of service of a set of data at the UE that triggered the scheduling request.

[0249] Aspect 19: The method of any one of Aspects 1-18, further comprising: receiving radio resource control information indicating a configuration for the pre- scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof, for receiving control information associated with the pre-scheduling type; determining a timing for being scheduled uplink resources in response to a transmitted scheduling request; and determining whether to transmit a scheduling request based at least in part on the timing and the configuration for the pre-scheduling type.

[0250] Aspect 20: The method of any one of Aspects 1-19, further comprising: receiving radio resource control information indicating a recurring uplink resource location configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource location, wherein receiving the control information comprises receiving medium access control information indicating that one or more of the recurring uplink resource locations include the set of uplink resources.

[0251] Aspect 21 : The method of any one of aspects 1 through 20, further comprising: determining a scheduling type associated with the control information from a plurality of scheduling types, wherein the plurality of scheduling types comprises: a first pre-scheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of the one or more requests for uplink resources; a second pre-scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource locations indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources; a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource locations indicated by the fourth scheduling type.

[0252] Aspect 22: The method of any one of aspects 1 through 21, wherein the pre-scheduling type dynamically schedules uplink resources without receiving a request for uplink resources.

[0253] Aspect 23 : A method for wireless communication at a base station, comprising: selecting a pre-scheduling type for scheduling uplink resources for a UE, the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE; and transmitting control information that schedules the set of uplink resources for the UE according to the selected pre-scheduling type, wherein the selected pre-scheduling type associated with the control information is indicated based at least in part on transmitting the control information.

[0254] Aspect 24: The method of aspect 23, further comprising: scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generating a downlink control information message that includes an indication that the downlink control information message is associated with the pre-scheduling type based at least in part on using the pre-scheduling type, wherein transmitting the control information comprises transmitting the downlink control information message.

[0255] Aspect 25: The method of any of aspects 23 through 24, further comprising: scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generating a downlink control information message based at least in part on using the pre-scheduling type, wherein transmitting the control information comprises transmitting the downlink control information message using a slot index, a symbol index, or a resource block index of a control channel or a shared channel associated with the pre-scheduling type.

[0256] Aspect 26: The method of any of aspects 23 through 25, further comprising: transmitting radio resource control information indicating a configuration for the pre-scheduling type, the configuration comprising a periodicity, an offset, a frequency, or any combination thereof for receiving control information associated with the pre-scheduling type.

[0257] Aspect 27: The method of any of aspects 23 through 26, further comprising: transmitting radio resource control information indicating a recurring uplink resource location configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource location, wherein transmitting the control information comprises transmitting medium access control information indicating that one or more of the recurring uplink resource location comprises the set of uplink resources.

[0258] Aspect 28: The method of any of aspects 23 through 27, further comprising: determining the pre-scheduling type from a plurality of scheduling types, the plurality of scheduling types comprising: a first pre-scheduling type that uses downlink control information to dynamically schedule uplink resources in anticipation of the one or more requests for uplink resources; a second pre-scheduling type that uses radio resource control information to statically indicate a recurring uplink resource location and uses medium access control information triggers to dynamically schedule uplink resources using one or more of the recurring uplink resource location indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources; a third scheduling type that uses downlink control information to dynamically schedule uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate a recurring uplink resource location and uses downlink control information triggers to semi-statically schedule uplink resources in the recurring uplink resource location indicated by the fourth scheduling type.

[0259] Aspect 29: The method of any of aspects 23-28, wherein the control information is transmitted based at least in part on a discontinuous reception cycle configured for the UE.

[0260] Aspect 30: An apparatus for wireless communication at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 1-22.

[0261] Aspect 31: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any of aspects 1-22.

[0262] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any of aspects 1-22.

[0263] Aspect 33: An apparatus for wireless communication at a base station, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 23-29.

[0264] Aspect 34: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any of aspects 23-29.

[0265] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of aspects 23-29.

[0266] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps can be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods can be combined.

[0267] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems can be described with reference to the techniques described herein, it should be readily understood that the

[0268] Information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0269] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0270] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions can also be physically located at various positions, including being distributed as discrete components or

[0271] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium 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 or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a 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 computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0272] As used herein, including in the claims “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list 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, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” can be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0273] In the drawings, like reference numerals can be used to denote similar components throughout the several views. Further, various components of the same type can be distinguished from each other by following the convention of numbering them with the first numeral assigned to the component type followed by a dash and a second numeral demonstrating the particular instance of the component. If, in the specification, only the first numeral is used to refer to a component, then only that component and not its particular instance is being discussed.

[0274] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that can be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, can 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 described examples.

[0275] The description herein is presented to enable those skilled in the art to make and use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; in response to receiving the first scheduling grant, starting an inactivity timer, a retransmission timer, or both; receiving, in a downlink control information message, downlink control information that pre-schedules a set of uplink resources for the UE prior to the UE requesting uplink resources; in response to the downlink control information pre-scheduling the set of uplink resources for the UE according to a pre-scheduling type, refraining from restarting the inactivity timer, the retransmission timer, or both, wherein an expiration of the inactivity timer, the retransmission timer, or both, is determined relative to the starting of the inactivity timer, the retransmission timer, or both, in response to receiving the first scheduling grant; and communicating using the set of uplink resources based at least in part on the downlink control information being associated with the pre-scheduling type.

2. The method of claim 1, further comprising: decoding the downlink control information message; and determining that the pre-scheduling type is associated with the downlink control information based at least in part on an indicator included in the decoded downlink control information message.

3. The method of claim 1, further comprising: identifying an index of a slot, a symbol, or a resource block for a control channel or a shared channel in which the downlink control information message is received or an uplink transmission scheduled by the downlink control information message is performed; and determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the index of the slot, the symbol, or the resource block.

4. The method of claim 1, further comprising: receiving radio resource control information indicating a configuration for the pre- scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the pre- scheduling type; and determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the configuration and a location of the downlink control information message in a control channel or a location of a shared channel.

5. The method of claim 1, further comprising: determining a scheduling type of the downlink control information or an uplink transmission; and determining whether to start the inactivity timer based at least in part on the determined scheduling type.

6. The method of claim 1, further comprising: identifying a discontinuous reception on interval; determining that the downlink control information is received in a first portion of the discontinuous reception on interval; and refraining from starting or restarting the inactivity timer based at least in part on the downlink control information being received in the first portion of the discontinuous reception on interval.

7. The method of claim 1, further comprising: identifying a discontinuous reception on interval; ​ ​ ​ ​ ​ determining that the downlink control information is received in a second portion of the discontinuous reception on duration interval; and starting or restarting the inactivity timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on duration interval.

8. The method of claim 1, further comprising: avoiding starting the retransmission timer after receiving the downlink control information based at least in part on an indicator included in the downlink control information.

9. The method of claim 1, further comprising: avoiding starting the retransmission timer after receiving the downlink control information based at least in part on a radio resource control configuration.

10. The method of claim 1, further comprising: identifying a discontinuous reception on duration interval; determining that the downlink control information is received in a first portion of the discontinuous reception on duration interval; and avoiding starting or restarting the retransmission timer based at least in part on receiving the downlink control information in the first portion of the discontinuous reception on duration interval.

11. The method of claim 1, further comprising: identifying a discontinuous reception on duration interval; determining that the downlink control information is received in a second portion of the discontinuous reception on duration interval; and starting or restarting the retransmission timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on duration interval.

12. The method of claim 1, further comprising: avoiding transmitting a request for uplink resources based at least in part on the set of uplink resources being scheduled by the downlink control information.

13. The method of claim 12, further comprising: determining a first duration associated with transmitting the request for uplink resources and being scheduled with the requested uplink resources; determining a second duration until the set of uplink resources will be scheduled by the downlink control information; and avoiding transmitting the request for uplink resources based at least in part on the second duration being less than the first duration.

14. The method of claim 1, further comprising: determining a duration until a second set of uplink resources will be scheduled by a second downlink control information of the pre-scheduling type; and avoiding transmitting a request for uplink resources based at least in part on the duration being less than a threshold.

15. The method of claim 14, wherein, the threshold is based at least in part on a second duration associated with transmitting the request for uplink resources and being scheduled with the requested uplink resources.

16. The method of claim 14, wherein, the threshold is based at least in part on a quality of service of a set of data at the UE that triggers the scheduling request.

17. The method of claim 1, further comprising: receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof, for receiving control information associated with the pre-scheduling type; determining a timing for being scheduled uplink resources in response to a transmitted scheduling request; and determining whether to transmit a scheduling request based at least in part on the timing and the configuration for the pre-scheduling type.

18. The method of claim 1, further comprising: receiving radio resource control information indicating a recurring uplink resource position configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource position, wherein receiving the downlink control information comprises: receiving medium access control information indicating that one or more of the recurring uplink resource positions include the set of uplink resources.

19. The method of claim 1, further comprising: determining a scheduling type associated with the downlink control information from a plurality of scheduling types, wherein the plurality of scheduling types comprises: a first pre-scheduling type that uses the downlink control information to dynamically schedule uplink resources in anticipation of one or more requests for uplink resources; a second pre-scheduling type that uses radio resource control information to statically indicate a recurring uplink resource position and uses medium access control information triggers to dynamically schedule the set of uplink resources using one or more of the recurring uplink resource positions indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources; a third scheduling type that uses the downlink control information to dynamically schedule the set of uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate a recurring uplink resource position and uses downlink control information triggers to semi-statically schedule the set of uplink resources in the recurring uplink resource position indicated by the fourth scheduling type.

20. The method of claim 1, wherein, the pre-scheduling type dynamically schedules uplink resources without receiving a request for uplink resources.

21. A method for wireless communication at a network device, comprising: transmitting one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; selecting a pre-scheduling type for scheduling uplink resources for a user equipment (UE), the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE; and transmitting downlink control information in a downlink control information message prior to receiving a request for uplink resources from the UE, the downlink control information pre-scheduling the set of uplink resources for the UE, the downlink control information indicating to the UE to pre-schedule the set of uplink resources for the UE according to a selected pre-scheduling type in response to the downlink control information, avoiding restarting an inactivity timer, a retransmission timer, or both, where an expiration of the inactivity timer, the retransmission timer, or both, is determined relative to a start of the inactivity timer, the retransmission timer, or both, in response to transmitting the first scheduling grant.

22. The method of claim 21, further comprising: scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generating the downlink control information message based at least in part on using the pre-scheduling type, the downlink control information message including an indication that the downlink control information message is associated with the pre-scheduling type.

23. The method of claim 21, further comprising: scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generating the downlink control information message based at least in part on using the pre-scheduling type, wherein transmitting the downlink control information includes transmitting the downlink control information message using a time slot index, a symbol index, or a resource block index of a control channel or a shared channel that is associated with the pre-scheduling type.

24. The method of claim 21, further comprising: transmitting radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency, or any combination thereof, for receiving control information associated with the pre-scheduling type.

25. The method of claim 21, further comprising: transmitting radio resource control information indicating a recurring uplink resource location configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource location, wherein transmitting the downlink control information includes: transmitting medium access control information indicating that one or more of the recurring uplink resource locations includes the set of uplink resources.

26. The method of claim 21, further comprising: determining the pre-scheduling type from a plurality of scheduling types, the plurality of scheduling types including: a first pre-scheduling type that uses the downlink control information to dynamically schedule the set of uplink resources in anticipation of the one or more requests for uplink resources; a second pre-scheduling type that uses the downlink control information to pre-schedule the set of uplink resources in anticipation of the one or more requests for uplink resources; and a third pre-scheduling type that uses the downlink control information to pre-schedule the set of uplink resources in anticipation of the one or more requests for uplink resources and to dynamically schedule the set of uplink resources in anticipation of the one or more requests for uplink resources. a second pre-scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses medium access control information triggering to dynamically schedule the set of uplink resources using one or more of the recurring uplink resource locations indicated by the second pre-scheduling type in anticipation of the one or more requests for uplink resources; a third scheduling type that uses downlink control information to dynamically schedule the set of uplink resources after receiving a request for uplink resources; and a fourth scheduling type that uses radio resource control information to statically indicate recurring uplink resource locations and uses downlink control information triggering to semi-statically schedule the set of uplink resources in the recurring uplink resource locations indicated by the fourth scheduling type.

27. The method of claim 21, wherein, the downlink control information is transmitted based at least in part on a discontinuous reception cycle configured for the UE.

28. An apparatus for wireless communication at a user equipment (UE), comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; in response to receiving the first scheduling grant, start an inactivity timer, a retransmission timer, or both; receive, in a downlink control information message, downlink control information that pre-schedules a set of uplink resources for the UE prior to the UE requesting uplink resources; in response to the downlink control information pre-scheduling the set of uplink resources for the UE according to a pre-scheduling type, refrain from restarting the inactivity timer, the retransmission timer, or both, wherein an expiration of the inactivity timer, the retransmission timer, or both, is determined relative to the start of the inactivity timer, the retransmission timer, or both, in response to receiving the first scheduling grant; and communicate using the set of uplink resources based at least in part on the downlink control information being associated with the pre-scheduling type.

29. The apparatus of claim 28, wherein, the instructions are further executable by the processor to cause the apparatus to: decode the downlink control information message; and determine that the pre-scheduling type is associated with the downlink control information based at least in part on an indicator included in the decoded downlink control information message.

30. The apparatus of claim 28, wherein, the instructions are further executable by the processor to cause the apparatus to: identify an index of a slot, symbol, or resource block for a control channel or a shared channel in which to receive the downlink control information message or perform an uplink transmission scheduled by the downlink control information message; and determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the index of the slot, the symbol, or the resource block.

31. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: receive radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the pre-scheduling type; and determine that the pre-scheduling type is associated with the downlink control information message based at least in part on the configuration and a location of the downlink control information message in a control channel or a location of a shared channel.

32. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: determine a scheduling type of the downlink control information or an uplink transmission; and determine whether to start the inactivity timer based at least in part on the determined scheduling type.

33. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: identify a discontinuous reception on interval; determine that the downlink control information is received in a first portion of the discontinuous reception on interval; and avoid starting or restarting the inactivity timer based at least in part on receiving the downlink control information in the first portion of the discontinuous reception on interval.

34. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: identify a discontinuous reception on interval; determine that the downlink control information is received in a second portion of the discontinuous reception on interval; and start or restart the inactivity timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on interval.

35. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: avoid starting the retransmission timer after receiving the downlink control information based at least in part on an indicator included in the downlink control information.

36. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: avoid starting the retransmission timer after receiving the downlink control information based at least in part on a radio resource control configuration.

37. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: identify a discontinuous reception on interval; determine that the downlink control information is received in a first portion of the discontinuous reception on interval; and avoid starting or restarting the retransmission timer based at least in part on receiving the downlink control information in the first portion of the discontinuous reception on interval.

38. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: identify a discontinuous reception on interval; determine that the downlink control information is received in a second portion of the discontinuous reception on interval; and start or restart the retransmission timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on interval.

39. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: avoid transmitting the request for uplink resources based at least in part on the set of uplink resources being scheduled by the downlink control information.

40. The apparatus of claim 39, wherein, The instructions can further be executable by the processor to cause the apparatus to: determine a first duration associated with transmitting the request for uplink resources and being scheduled the set of requested uplink resources; determine a second duration until the set of uplink resources will be scheduled by the downlink control information; and avoid transmitting the request for uplink resources based at least in part on the second duration being less than the first duration.

41. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: determine a duration until a second set of uplink resources will be scheduled by a second downlink control information of the pre-scheduling type; and avoid transmitting a request for uplink resources based at least in part on the duration being less than a threshold.

42. The device of claim 41, wherein, The threshold is based at least in part on a second duration associated with transmitting the request for uplink resources and being scheduled the requested uplink resources.

43. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: receive radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof, for receiving control information associated with the pre-scheduling type; determine a timing for being scheduled uplink resources in response to a transmitted scheduling request; and determine whether to transmit a scheduling request based at least in part on the timing and the configuration for the pre-scheduling type.

44. The apparatus of claim 28, wherein, The instructions can further be executable by the processor to cause the apparatus to: receive radio resource control information indicating a recurring uplink resource position configured for the UE and the pre-scheduling type being associated with the recurring uplink resource position, wherein receiving the downlink control information comprises receiving medium access control information indicating one or more of the recurring uplink resource position includes the set of uplink resources.

45. An apparatus for wireless communication at a network device, comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmit one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; select a pre-scheduling type for scheduling uplink resources for a user equipment (UE), the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE; and transmitting downlink control information in a downlink control information message prior to receiving, from the UE, a request for uplink resources, the downlink control information pre-scheduling the set of uplink resources for the UE, the downlink control information indicating to the UE to pre-schedule the set of uplink resources for the UE according to a selected pre-scheduling type in response to the downlink control information, refraining from restarting an inactivity timer, a retransmission timer, or both, where an expiration of the inactivity timer, the retransmission timer, or both, is determined relative to a start of the inactivity timer, the retransmission timer, or both, in response to transmitting the first scheduling grant.

46. The device of claim 45, wherein, The instructions can further be executable by the processor to cause the apparatus to: schedule the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generate the downlink control information message based at least in part on using the pre-scheduling type, the downlink control information message including an indication that the downlink control information message is associated with the pre-scheduling type.

47. The device of claim 45, wherein, The instructions can further be executable by the processor to cause the apparatus to: schedule the set of uplink resources using the pre-scheduling type based at least in part on the selection; and generate the downlink control information message based at least in part on using the pre-scheduling type, where transmitting the downlink control information includes transmitting the downlink control information message using a time slot index, a symbol index, or a resource block index of a control channel or a shared channel that is associated with the pre-scheduling type.

48. The device of claim 45, wherein, The instructions can further be executable by the processor to cause the apparatus to: transmit radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency, or any combination thereof, for receiving control information associated with the pre-scheduling type.

49. The device of claim 45, wherein, The instructions can further be executable by the processor to cause the apparatus to: transmit radio resource control information indicating a recurring uplink resource location configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource location, where transmitting the downlink control information includes transmitting medium access control information indicating that one or more of the recurring uplink resource locations include the set of uplink resources.

50. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; means for starting, in response to receiving the first scheduling grant, an inactivity timer, a retransmission timer, or both; means for receiving downlink control information in a downlink control information message prior to the UE requesting uplink resources, the downlink control information pre-scheduling a set of uplink resources for the UE; means for pre-scheduling the set of uplink resources for the UE according to a pre-scheduling type in response to the downlink control information, wherein expiration of the inactivity timer, the retransmission timer, or both, is determined relative to starting of the inactivity timer, the retransmission timer, or both, in response to receiving the first scheduling grant; and means for communicating using the set of uplink resources based at least in part on the downlink control information being associated with the pre-scheduling type.

51. The device of claim 50, wherein, the control information being received in a downlink control information message, the apparatus further comprising: means for decoding the downlink control information message; and means for determining that the pre-scheduling type is associated with the downlink control information based at least in part on an indicator included in the decoded downlink control information message.

52. The device of claim 50, wherein, the control information being received in a downlink control information message, the apparatus further comprising: means for identifying an index of a slot, symbol, or resource block for a control channel or shared channel in which the downlink control information message is received or an uplink transmission scheduled by the downlink control information message is performed; and means for determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the index of the slot, the symbol, or the resource block.

53. The device of claim 50, wherein, the control information being received in a downlink control information message, the apparatus further comprising: means for receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration comprising a periodicity, an offset, a frequency location, or any combination thereof, for receiving control information associated with the pre-scheduling type; and means for determining that the pre-scheduling type is associated with the downlink control information message based at least in part on the configuration and a location of the downlink control information message in a control channel or a location of a shared channel.

54. The apparatus of claim 50, further comprising: means for determining a scheduling type of the downlink control information or a scheduling type of an uplink transmission; and means for determining whether to start the inactivity timer based at least in part on the determined scheduling type.

55. The apparatus of claim 50, further comprising: means for identifying a discontinuous reception on interval; means for determining that the downlink control information is received in a first portion of the discontinuous reception on interval; and means for refraining from starting or restarting the inactivity timer based at least in part on the downlink control information being received in the first portion of the discontinuous reception on interval.

56. The apparatus of claim 50, further comprising: means for identifying a discontinuous reception on duration interval; means for determining that the downlink control information is received in a second portion of the discontinuous reception on duration interval; and means for starting or restarting the inactivity timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on duration interval.

57. The apparatus of claim 50, further comprising: means for refraining from starting the retransmission timer after receiving the downlink control information based at least in part on an indicator included in the downlink control information.

58. The apparatus of claim 50, further comprising: means for refraining from starting the retransmission timer after receiving the downlink control information based at least in part on a radio resource control configuration.

59. The apparatus of claim 50, further comprising: means for identifying a discontinuous reception on duration interval; means for determining that the downlink control information is received in a first portion of the discontinuous reception on duration interval; and means for refraining from starting or restarting the retransmission timer based at least in part on receiving the downlink control information in the first portion of the discontinuous reception on duration interval.

60. The apparatus of claim 50, further comprising: means for identifying a discontinuous reception on duration interval; means for determining that the downlink control information is received in a second portion of the discontinuous reception on duration interval; and means for starting or restarting the retransmission timer based at least in part on receiving the downlink control information in the second portion of the discontinuous reception on duration interval.

61. The apparatus of claim 50, further comprising: means for refraining from transmitting a request for uplink resources based at least in part on the set of uplink resources being scheduled by the downlink control information.

62. The apparatus of claim 61, further comprising: means for determining a first duration associated with transmitting the request for uplink resources and being scheduled the requested uplink resources; means for determining a second duration until the set of uplink resources will be scheduled by the downlink control information; and means for refraining from transmitting the request for uplink resources based at least in part on the second duration being less than the first duration.

63. The apparatus of claim 50, further comprising: means for determining a duration until a second set of uplink resources will be scheduled by a second downlink control information of the pre-scheduling type; and means for refraining from transmitting a request for uplink resources based at least in part on the duration being less than a threshold.

64. The apparatus of claim 50, further comprising: means for receiving radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency location, or any combination thereof for receiving control information associated with the pre-scheduling type; means for determining a timing for which uplink resources are scheduled in response to a transmitted scheduling request; and means for determining whether to transmit a scheduling request based at least in part on the timing and the configuration for the pre-scheduling type.

65. The apparatus of claim 50, further comprising: means for receiving radio resource control information indicating a recurring uplink resource position configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource position, wherein receiving the downlink control information comprises receiving medium access control information indicating that one or more of the recurring uplink resource positions include the set of uplink resources.

66. An apparatus for wireless communication at a network device, comprising: means for transmitting one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; means for selecting a pre-scheduling type for scheduling uplink resources for a user equipment (UE), the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE; and means for transmitting downlink control information in a downlink control information message prior to receiving a request for uplink resources from the UE, the downlink control information pre-scheduling the set of uplink resources for the UE, the downlink control information indicating to the UE that the set of uplink resources for the UE are pre-scheduled according to the selected pre-scheduling type in response to the downlink control information, avoiding restarting an inactivity timer, a retransmission timer, or both, wherein an expiration of the inactivity timer, the retransmission timer, or both, is determined relative to a start of the inactivity timer, the retransmission timer, or both, in response to transmitting the first scheduling grant.

67. The apparatus of claim 66, further comprising: means for scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and means for generating the downlink control information message based at least in part on using the pre-scheduling type, the downlink control information message including an indication that the downlink control information message is associated with the pre-scheduling type.

68. The apparatus of claim 66, further comprising: means for scheduling the set of uplink resources using the pre-scheduling type based at least in part on the selection; and means for generating the downlink control information message based at least in part on using the pre-scheduling type, wherein transmitting the downlink control information comprises transmitting the downlink control information message using a time slot index, a symbol index, or a resource block index of a control channel or a shared channel associated with the pre-scheduling type.

69. The apparatus of claim 66, further comprising: means for transmitting radio resource control information indicating a configuration for the pre-scheduling type, the configuration including a periodicity, an offset, a frequency, or any combination thereof for receiving control information associated with the pre-scheduling type.

70. The apparatus of claim 66, further comprising: means for transmitting radio resource control information indicating a recurring uplink resource position configured for the UE and that the pre-scheduling type is associated with the recurring uplink resource position, wherein transmitting the downlink control information comprises transmitting medium access control information indicating that one or more of the recurring uplink resource positions include the set of uplink resources.

71. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: receive one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; start an inactivity timer, a retransmission timer, or both, in response to receiving the first scheduling grant; receive, in a downlink control information message, downlink control information pre-scheduling a set of uplink resources for the UE prior to the UE requesting uplink resources; avoid restarting the inactivity timer, the retransmission timer, or both, in response to the downlink control information pre-scheduling the set of uplink resources for the UE according to a pre-scheduling type, wherein an expiration of the inactivity timer, the retransmission timer, or both, is determined with respect to the start of the inactivity timer, the retransmission timer, or both, in response to receiving the first scheduling grant; and communicate using the set of uplink resources based at least in part on the downlink control information being associated with the pre-scheduling type.

72. A non-transitory computer-readable medium storing code for wireless communication at a network device, the code comprising instructions executable by a processor to: transmit one or more messages including a first scheduling grant corresponding to a semi-static scheduling type or a dynamic scheduling type; select a pre-scheduling type for scheduling uplink resources for a user equipment (UE), the pre-scheduling type for pre-scheduling a set of uplink resources for the UE prior to receiving one or more requests for uplink resources from the UE; and transmitting downlink control information in a downlink control information message prior to receiving a request for uplink resources from the UE, the downlink control information pre-scheduling the set of uplink resources for the UE, the downlink control information indicating to the UE to pre-schedule the set of uplink resources for the UE according to a selected pre-scheduling type in response to the downlink control information, avoiding restarting an inactivity timer, a retransmission timer, or both, wherein, an expiration of the inactivity timer, the retransmission timer, or both, is determined with respect to the start of the inactivity timer, the retransmission timer, or both, in response to transmitting the first scheduling grant.

Images