Preconfigured uplink resource techniques in wireless communications

Abstract

This invention describes apparatus and methods for wireless communication that support pre-configured uplink resources (PURs) in wireless communication. A base station can communicate the availability of PUR support and can allocate PUR resources to a user equipment (UE) based on a request from the UE. The UE can determine to request a PUR, such as by receiving an indication from the base station that it supports a PUR via a System Information Block (SIB), and transmit a PUR request message to the base station. A PUR response from the base station can indicate the configuration or reconfiguration of the PUR allocation for the UE that can be used for uplink transmission, or the release of the PUR allocation.

Description

Techniques for Preconfigured Uplink Resources in Wireless Communication The following generally relates to wireless communication and, more specifically, to techniques for preconfigured uplink resources in a wireless communication system. Wireless communication systems have been widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, Advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as New Radio (NR) systems. These systems may 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 Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each of which simultaneously supports the communication of multiple communication devices that may otherwise be referred to as user equipment (UE). In some cases, a UE may have a relatively small amount of data to transmit periodically. For example, a UE may be associated with a sensor that is used to provide readings to a network node on a periodic basis. In some cases, in order to obtain uplink resources for an uplink transmission, a UE may transmit a request for uplink data resources (e.g., a buffer status report (BSR) indicating that the UE has data to transmit may be provided to the base station), receive an uplink grant in response to the request, and then transmit uplink data according to the uplink grant. In cases where the UE has a relatively small amount of data to transmit, such procedures consume a large amount of overhead relative to the amount of data transmitted. Efficient techniques for allocating uplink resources to a UE for "grant-free" uplink transmission (i.e., obtaining an uplink grant without having to perform multiple-step communication each time) may allow for more efficient network operation by allocating such uplink resources and reduced overhead associated with such uplink transmissions. The described techniques relate to improved methods, systems, devices, and apparatuses for supporting preconfigured uplink resources (PUR) in a wireless communication system. The various techniques described provide for communicating that support for PUR is available at a base station and allocating PUR resources to a UE based on a request from the user equipment (UE). The UE may receive an indication that the base station supports PUR, such as via a system information block (SIB), determine to request PUR, and transmit a PUR request message to the base station. The PUR response from the base station may indicate the PUR allocation for the UE that is available for uplink transmission. In some cases, the base station may provide a PUR allocation that is different from the requested PUR configuration provided by the UE in the PUR request. The UE may determine that the different PUR configuration is insufficient for the UE and may transmit a PUR configuration failure to the base station. In some cases, the transmission from the base station to the UE indicating the PUR configuration may provide an indication of the uplink resources that can be used by the UE to transmit the PUR configuration failure indication. In some cases, an early data transmission (EDT) random access procedure may be used to transmit the PUR request from the UE and may be used by the base station to transmit the PUR configuration to the UE. In such cases, the PUR request message may be transmitted as a random access message as part of the EDT random access procedure. Additionally or alternatively, the PUR request from the UE for a PUR configuration or PUR reconfiguration may provide an indication of the number of instances of the requested PUR grant. Such a PUR request may indicate a PUR release request by indicating the number of instances or PUR grants as zero. Additionally or alternatively, the base station may determine that the requested PUR configuration or PUR reconfiguration is not available for the UE and may transmit a PUR rejection indication to the UE. In the case of a PUR reconfiguration request, the rejection indication may also indicate to the UE how to handle the existing PUR configuration (e.g., whether to release the existing PUR configuration or maintain the existing PUR configuration). Describes a method for wireless communication at a UE. The method may include: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports the preconfigured uplink resources; receiving, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; receiving uplink resources for a response message to be transmitted from the UE; and transmitting a preconfigured uplink resource configuration response message to the base station using the uplink resources of the response message. Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmit a preconfigured uplink resource request message to the base station based on determining that the base station supports the preconfigured uplink resources; receive, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; receive uplink resources for a response message to be transmitted from the UE; and transmit a preconfigured uplink resource configuration response message to the base station using the uplink resources of the response message. Describe another device for wireless communication at a UE. The device may include components for: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports the preconfigured uplink resources; receiving, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; receiving an uplink resource for a response message to be transmitted from the UE; and transmitting a preconfigured uplink resource configuration response message to the base station using the uplink resource of the response message. Describe a non-transitory computer-readable medium that stores code for wireless communication at a UE. The code may include instructions executable by a processor for: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports the preconfigured uplink resources; receiving, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; receiving an uplink resource for a response message to be transmitted from the UE; and transmitting a preconfigured uplink resource configuration response message to the base station using the uplink resource of the response message. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference relative to a previous preconfigured uplink resource configuration of the UE. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference relative to a current configuration being used by the UE. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference relative to a default preconfigured uplink resource configuration. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the uplink resource of the response message may be provided in an explicit indication with the preconfigured uplink resource configuration from the base station. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the uplink resource of the response message may be included in a first entry of the preconfigured uplink resources allocated to the UE. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: determining a set of control channel resources for monitoring an uplink grant based on the preconfigured uplink resource (PUR) configuration from the base station; and monitoring the set of control channel resources for the uplink grant, where the uplink grant indicates the uplink resources for transmitting the PUR configuration response message to the base station. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource (PUR) configuration response message to the base station indicates that the PUR configuration has succeeded or has failed. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the preconfigured uplink resource configuration response message may be performed when the UE is in the idle mode or in a mode connected to the base station. Describes a method for wireless communication at a UE. The method may include determining a data early transmission configuration of a data early transmission procedure for transmitting UE payload data in an uplink message of the data early transmission procedure. In some cases, the uplink message may include a preconfigured uplink resource request message indicating a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration. The method may further include transmitting the uplink message of the data early transmission procedure and receiving, in a downlink message of the data early transmission procedure, a message from the base station indicating a configuration, reconfiguration, or release of a preconfigured uplink resource configuration. Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine a data early transmission configuration of a data early transmission procedure; transmit an uplink message of the data early transmission procedure; and receive, in a downlink message of the data early transmission procedure, a message from the base station indicating a configuration, reconfiguration, or release of a preconfigured uplink resource configuration. Describes another apparatus for wireless communication at a UE. The apparatus may include components for: determining a data early transmission configuration of a data early transmission procedure; transmitting an uplink message of the data early transmission procedure; and receiving, in a downlink message of the data early transmission procedure, a message from the base station indicating a configuration, reconfiguration, or release of a preconfigured uplink resource configuration. Describe a non - transitory computer - readable medium that stores code for wireless communication at a UE. The code may include instructions executable by a processor for: determining a data early transmission configuration of a data early transmission procedure; transmitting an uplink message of the data early transmission procedure; and receiving, in a downlink message of the data early transmission procedure from the base station, a message indicating a configuration or re - configuration or release of a pre - configured uplink resource configuration. Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may further include operations, features, components, or instructions for: formatting a pre - configured uplink resource request message to be transmitted in the uplink message of the data early transmission procedure, where the pre - configured uplink resource request message indicates a requested configuration, re - configuration, or release of a pre - configured uplink resource configuration; and transmitting the pre - configured uplink resource request message in the uplink message of the data early transmission procedure. Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may further include operations, features, components, or instructions for: determining a set of control channel resources for monitoring an uplink grant based on the pre - configured uplink resource (PUR) configuration message from the base station; and monitoring the set of control channel resources for the uplink grant, where the uplink grant indicates an uplink resource for transmitting a PUR configuration response message to the base station. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the uplink message of the data early transmission procedure is transmitted in the transmission of the third message (MSG3) of the data early transmission procedure. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the pre - configured uplink resource (PUR) configuration message from the base station is received in a fourth data early transmission (EDT) downlink message providing an RRC connection release message or an RRC data early completion message. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the PUR configuration is provided as a differential configuration indicating a difference relative to a previous PUR configuration of the UE. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the PUR configuration is provided as a differential configuration indicating a difference relative to a default PUR configuration or indicating a difference relative to a configuration being used at the UE. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the fourth EDT message explicitly or implicitly provides one or more of the following: an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication for de - configuring and releasing the previous PUR configuration, new resources of a new PUR configuration, or any combination thereof. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: indicating a successful PUR configuration or a PUR configuration failure of an uplink resource transmission using a response message from the UE in response to the preconfigured uplink resource (PUR) configuration message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: determining to deconfigure the PUR configuration based on receiving broadcast system information transmission indicating that the PUR may not be supported from the base station; and releasing the PUR configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: receiving a PUR release message from the base station; and deconfiguring the PUR configuration based on the PUR release message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: formatting a preconfigured uplink resource request message indicating the number of instances of preconfigured uplink resource grants requested by the UE to be transmitted to the base station, wherein the number of instances of the preconfigured uplink resource (PUR) grant provides an explicit number of PUR grants or an indication of an infinite number of PUR grants. Describes a method for wireless communication at a UE. The method may include: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports preconfigured uplink resources, wherein the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and receiving a preconfigured uplink resource configuration from the base station. Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmit a preconfigured uplink resource request message to the base station based on determining that the base station supports preconfigured uplink resources, wherein the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and receive a preconfigured uplink resource configuration from the base station. Describe another apparatus for wireless communication at a UE. The apparatus may include components for: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports preconfigured uplink resources, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and receiving a preconfigured uplink resource configuration from the base station. Describe a non-transitory computer-readable medium that stores code for wireless communication at a UE. The code may include instructions executable by a processor for: determining that a base station supports preconfigured uplink resources for grant-free uplink transmission from the UE; transmitting a preconfigured uplink resource request message to the base station based on determining that the base station supports preconfigured uplink resources, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and receiving a preconfigured uplink resource configuration from the base station. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of instances of preconfigured uplink resource (PUR) grants provides an explicit number of PUR grants or an indication of an infinite number of PUR grants. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of instances of preconfigured uplink resource (PUR) grants requested by the UE indicates a request for a one-shot PUR configuration or a request for a multi-shot PUR configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference relative to a previous preconfigured uplink resource configuration of the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference relative to a default preconfigured uplink resource configuration or indicating a difference relative to a configuration being used at the UE. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: transmitting a PUR reconfiguration failure indication to the base station after receiving the preconfigured uplink resource configuration; and releasing the PUR configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: determining a set of control channel resources for monitoring an uplink grant based on the message from the base station; and monitoring the set of control channel resources for the uplink grant, where the uplink grant indicates uplink resources for transmitting a preconfigured uplink resource configuration response message to the base station. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: determining that a preconfigured uplink resource (PUR) configuration may be deconfigured based on receiving broadcast system information transmission indicating that the PUR may not be supported from the base station; and releasing the PUR configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource request message may be transmitted to the base station in an uplink message of a data early transmission (EDT) procedure. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: formatting the uplink resource request message to be transmitted in the uplink message of the EDT procedure, where the uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink resource request message is transmitted in a transmission of a third message (MSG3) of the EDT procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the message from the base station indicating the UE's preconfigured uplink resources is received in a fourth data early transmission (EDT) downlink message providing an RRC connection release message or an RRC data early completion message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the message from the base station explicitly or implicitly provides one or more of the following: an indication that the UE is to use a previous preconfigured uplink resource (PUR) configuration, a confirmation of the previous PUR configuration, an indication to deconfigure and release the previous PUR configuration, new resources for a new PUR configuration, or any combination thereof. A method for wireless communication at a UE is described. The method may include: receiving, from a base station, a radio resource configuration connection release message or a radio resource configuration data early completion message providing a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration indicates a number of instances of a preconfigured uplink resource grant for the UE; and transmitting one or more uplink communications to the base station based on the preconfigured uplink resource configuration. Describe an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive from a base station a radio resource configuration connection release message or a radio resource configuration data early completion message providing a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration indicates a number of instances of preconfigured uplink resource grants for the UE; and transmit one or more uplink communications to the base station based on the preconfigured uplink resource configuration. Describe another apparatus for wireless communication at a UE. The apparatus may include means for: receiving from a base station a radio resource configuration connection release message or a radio resource configuration data early completion message providing a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration indicates a number of instances of preconfigured uplink resource grants for the UE; and transmitting one or more uplink communications to the base station based on the preconfigured uplink resource configuration. Describe a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor for: receiving from a base station a radio resource configuration connection release message or a radio resource configuration data early completion message providing a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration indicates a number of instances of preconfigured uplink resource grants for the UE; and transmitting one or more uplink communications to the base station based on the preconfigured uplink resource configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of instances of PUR grants provides an explicit number of PUR grants or an indication of an infinite number of PUR grants. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for: prior to the receiving, transmitting a PUR request message to the base station based on a determination that the base station supports preconfigured uplink resources, wherein the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the PUR request message is transmitted to the base station in an uplink message of the EDT procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink resource request message may be transmitted in the MSG3 transmission of the EDT procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference relative to a previous preconfigured uplink resource configuration of the UE, indicating a difference relative to a default preconfigured uplink resource configuration, or indicating a difference relative to a configuration being used at the UE. Describes a method for wireless communication at a UE. The method may include: determining that a base station supports preconfigured uplink resources for grant-free uplink transmissions from the UE; transmitting a preconfigured uplink resource request message to the base station based on the determination that the base station supports preconfigured uplink resources; and receiving, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine that a base station supports preconfigured uplink resources for grant-free uplink transmissions from the UE; transmit a preconfigured uplink resource request message to the base station based on the determination that the base station supports preconfigured uplink resources; and receive, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describes another apparatus for wireless communication at a UE. The apparatus may include means for: determining that a base station supports preconfigured uplink resources for grant-free uplink transmissions from the UE; transmitting a preconfigured uplink resource request message to the base station based on the determination that the base station supports preconfigured uplink resources; and receiving, in response to the preconfigured uplink resource request message from the base station, a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describe a non - transitory computer - readable medium that stores code for wireless communication at a UE. The code can include instructions executable by a processor for: determining that a base station supports pre - configured uplink resources for grant - free uplink transmission from the UE; transmitting a pre - configured uplink resource request message to the base station based on determining that the base station supports pre - configured uplink resources; and in response to receiving from the base station a pre - configured uplink resource response message indicating that the pre - configured uplink resource request message is rejected, and wherein the pre - configured uplink resource response message indicates how the UE is to proceed based on the rejected pre - configured uplink resource request message. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the pre - configured uplink resource (PUR) request message indicates a request for re - configuration of a previous PUR configuration, and wherein the PUR response message indicates that the previous PUR configuration is to be released by the UE. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the pre - configured uplink resource (PUR) request message indicates a request for re - configuration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be maintained by the UE. Describe a method for wireless communication at a base station. The method can include: transmitting an indication that the base station supports pre - configured uplink resources for grant - free uplink transmission; receiving a pre - configured uplink resource request message from a UE; transmitting, in response to the pre - configured uplink resource request message, a pre - configured uplink resource configuration identifying the pre - configured uplink resources allocated to the UE to the UE; transmitting an uplink resource to the UE in response to a response message from the UE; and receiving a pre - configured uplink resource configuration response from the UE via the uplink resource of the response message. Describe an apparatus for wireless communication at a base station. The apparatus can include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to: transmit an indication that the base station supports pre - configured uplink resources for grant - free uplink transmission; receive a pre - configured uplink resource request message from a UE; transmit, in response to the pre - configured uplink resource request message, a pre - configured uplink resource configuration identifying the pre - configured uplink resources allocated to the UE to the UE; transmit an uplink resource to the UE in response to a response message from the UE; and receive a pre - configured uplink resource configuration response from the UE via the uplink resource of the response message. Describe another apparatus for wireless communication at a base station. The apparatus may include components for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE; in response to the preconfigured uplink resource request message, transmitting to the UE a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; transmitting uplink resources to the UE in response to a response message from the UE; and receiving, from the UE via the uplink resources of the response message, a preconfigured uplink resource configuration response. Describe a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE; in response to the preconfigured uplink resource request message, transmitting to the UE a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE; transmitting uplink resources to the UE in response to a response message from the UE; and receiving, from the UE via the uplink resources of the response message, a preconfigured uplink resource configuration response. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference relative to a previous preconfigured uplink resource configuration of the UE, a current configuration being used by the UE, or a default preconfigured uplink resource configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink resources of the response message may be provided in an explicit indication of the preconfigured uplink resource configuration from the base station. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink resources of the response message may be provided in a set of control channel resources monitored by the UE in a control channel transmission from the base station. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource configuration failure indication may be transmitted when the UE is in an idle mode or in a mode connected to the base station. Describe a method for wireless communication at a base station. The method may include: determining a data early transmission configuration for a data early transmission procedure available for transmitting a preconfigured uplink resource request message, wherein the data early transmission configuration provides for uplink transmission of UE payload data in an uplink message of the data early transmission procedure; receiving, from a UE, the preconfigured uplink resource request message in the uplink message of the data early transmission procedure, wherein the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration; and in response to the preconfigured uplink resource configuration, transmitting a preconfigured uplink resource configuration message to the UE, wherein the preconfigured uplink resource configuration indicates an uplink resource for a response message from the UE. Describe a device for wireless communication at a base station. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: determine a data early transmission configuration for a data early transmission procedure available for transmitting the preconfigured uplink resource request message, wherein the data early transmission configuration provides for uplink transmission of UE payload data in an uplink message of the data early transmission procedure; receive, from a UE, the preconfigured uplink resource request message in the uplink message of the data early transmission procedure, wherein the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration; and in response to the preconfigured uplink resource configuration, transmit a preconfigured uplink resource configuration message to the UE, wherein the preconfigured uplink resource configuration indicates an uplink resource for a response message from the UE. Describe another device for wireless communication at a base station. The device may include means for: determining a data early transmission configuration for a data early transmission procedure available for transmitting the preconfigured uplink resource request message, wherein the data early transmission configuration provides for uplink transmission of UE payload data in an uplink message of the data early transmission procedure; receiving, from a UE, the preconfigured uplink resource request message in the uplink message of the data early transmission procedure, wherein the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration; and in response to the preconfigured uplink resource configuration, transmitting a preconfigured uplink resource configuration message to the UE, wherein the preconfigured uplink resource configuration indicates an uplink resource for a response message from the UE. Describe a non - transitory computer - readable medium that stores code for wireless communication at a base station. The code may include instructions executable by a processor for: determining a data pre - transmission configuration of a data pre - transmission procedure for transmitting a pre - configured uplink resource request message, where the data pre - transmission configuration provides for uplink transmission of UE payload data in an uplink message of the data pre - transmission procedure; receiving from a UE a pre - configured uplink resource request message in the uplink message of the data pre - transmission procedure, where the pre - configured uplink resource request message indicates a requested configuration, re - configuration, or release of a pre - configured uplink resource configuration; and in response to the pre - configured uplink resource configuration, transmitting a pre - configured uplink resource configuration message to the UE, where the pre - configured uplink resource configuration indicates an uplink resource for a response message from the UE. Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may further include operations, features, components, or instructions for: transmitting an indication that the uplink message of the data pre - transmission procedure is available for the pre - configured uplink resource request message. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the indication may be transmitted in a system information block broadcast from the base station. In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the PUR configuration may be provided as a delta configuration indicating a difference relative to a previous PUR configuration of the UE, indicating a difference relative to a default PUR configuration, or indicating a difference relative to a configuration being used at the UE. Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may further include operations, features, components, or instructions for: in response to the pre - configured uplink resource configuration message, receiving an indication of successful PUR configuration or PUR configuration failure using the uplink resource of the response message from the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource (PUR) configuration may be provided in an early data transmission (EDT) data early completion message indicating the PUR resources of the UE's configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the EDT data early completion message explicitly or implicitly provides one or more of the following: an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication for deconfiguring and releasing the previous PUR configuration, new resources of a new PUR configuration, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication for deconfiguring and releasing the previous PUR configuration includes a Boolean flag in the EDT data early completion message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: transmitting broadcast system information indicating that PUR is not supported and that the UE is to release the PUR configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: determining to reconfigure or release the PUR configuration of the UE; transmitting a paging message to the UE; receiving a random access request message from the UE in response to the paging message; and transmitting an indication for reconfiguring or releasing the PUR configuration in response to the random access message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication for reconfiguring the PUR configuration indicates a new PUR configuration for the UE to use or indicates that the UE is to release the PUR configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: transmitting a preconfigured uplink resource (PUR) release message to the UE; and deconfiguring the PUR configuration based on the PUR release message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the PUR release message may be transmitted when the UE is in the connected mode or in an EDT random access response message, and wherein the PUR release message is a radio resource control (RRC) PUR reconfiguration message. Describes a method for wireless communication at a base station. The method may include: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE, wherein the preconfigured uplink resource request message includes an example number of preconfigured uplink resource grants requested by the UE; and transmitting a preconfigured uplink resource configuration to the UE in response to the preconfigured uplink resource request message. Describe a device for wireless communication at a base station. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: transmit an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receive a preconfigured uplink resource request message from a UE, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and in response to the preconfigured uplink resource request message, transmit a preconfigured uplink resource configuration to the UE. Describe another device for wireless communication at a base station. The device may include means for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and in response to the preconfigured uplink resource request message, transmitting a preconfigured uplink resource configuration to the UE. Describe a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE; and in response to the preconfigured uplink resource request message, transmitting a preconfigured uplink resource configuration to the UE. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the number of instances of preconfigured uplink resource grants provides an explicit number of PUR grants or an indication of an indefinite number of PUR grants. In some examples of the methods, devices, and non-transitory computer-readable media described herein, a number of zero instances indicates that the preconfigured uplink resource configuration is to be released. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the number of instances of preconfigured uplink resource (PUR) grants requested by the UE indicates a request for a single-trigger PUR configuration or a request for a multi-trigger PUR configuration. Describe a method for wireless communication at a base station. The method may include: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE; and in response to the preconfigured uplink resource request message, transmitting to the UE a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describe an apparatus for wireless communication at a base station. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receive a preconfigured uplink resource request message from a UE; and in response to the preconfigured uplink resource request message, transmit to the UE a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describe another apparatus for wireless communication at a base station. The apparatus may include means for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE; and in response to the preconfigured uplink resource request message, transmitting to the UE a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. Describe a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor for: transmitting an indication that the base station supports preconfigured uplink resources for grant-free uplink transmission; receiving a preconfigured uplink resource request message from a UE; and in response to the preconfigured uplink resource request message, transmitting to the UE a preconfigured uplink resource response message indicating that the preconfigured uplink resource request message is rejected, and wherein the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource (PUR) request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the previous PUR configuration is to be released by the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource (PUR) request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be maintained by the UE. Cross-reference This patent application claims priority to U.S. patent application Ser. No. 16 / 926,164, filed Jul. 10, 2020, by Phuyal et al., entitled “Preconfigured Uplink Resource Techniques in Wireless Communications,” and U.S. Provisional Patent Application No. 62 / 873,836, filed Jul. 12, 2019, by Phuyal et al., entitled “Preconfigured Uplink Resource Techniques in Wireless Communications,” which are hereby assigned to the assignee of the present application and which are hereby incorporated by reference in their entireties. Aspects of the present invention provide improved methods, systems, devices, and apparatuses for supporting signaling and configuration related to preconfigured uplink resources (PURs). The various techniques described provide for conveying that PUR resources are available at a base station, such as by indicating transmission of a system information block (SIB) that supports PURs. A UE may receive an indication of support for PURs and may determine to request PUR resources from the base station (e.g., based on uplink data to be transmitted to the base station). In some cases, the UE may transmit a PUR request message requesting PUR resources. The base station may receive the PUR request message and determine whether to allocate PUR resources to the UE. The base station may transmit a PUR response with a PUR allocation to the UE in the case where the base station determines to allocate PUR resources to the UE, or may transmit a PUR rejection message to the UE in the case where the base station determines that no PUR resources are available for allocation to the UE. In some cases, the base station may provide a PUR allocation different from the requested PUR configuration from the UE. It should be noted that the various examples of the present invention discuss techniques for requesting or configuring PUR configurations. Such techniques may also be used when reconfiguring an existing PUR configuration, and both the PUR configuration and the PUR reconfiguration may be simply referred to herein as "PUR configuration". In the case where the base station provides a PUR allocation different from the requested PUR configuration, the UE may determine that the different PUR configuration is insufficient for the UE and may transmit a PUR configuration failure. The PUR configuration failure may indicate that the UE will release the PUR configuration, and the base station may reallocate the PUR of the configuration for other purposes. In some cases, the transmission from the base station to the UE indicating the PUR configuration may provide an uplink resource indication that can be used by the UE to transmit a PUR configuration failure indication or can be used by the UE to transmit a PUR configuration completion indication. In some cases, the indication of the uplink resource may be an explicit indication of an uplink grant for the provided PUR configuration. Additionally or alternatively, the UE may monitor one or more downlink control channel (e.g., Physical Downlink Control Channel (PDCCH)) transmissions during certain window periods to obtain an uplink grant for a PUR failure or PUR configuration completion indication. In some cases, the UE may transmit a PUR failure or PUR configuration completion message when in the connected mode (e.g., Radio Resource Control (RRC) connected mode) or when in the idle (e.g., RRC idle) mode. In the case where the UE is in the idle mode, the PUR failure or PUR configuration completion message may be transmitted when the configured PUR first appears. In some cases, the UE may determine that the random access procedure for establishing a connection with the base station is configured to allow early data transmission (EDT) as part of the random access procedure. Such an EDT random access procedure may allow the UE to transmit a data payload as part of the random access procedure, which can reduce overhead and allow the transmission of a relatively small amount of data. In some cases, the EDT random access procedure can be used to transmit a PUR request from the UE and can be used by the base station to transmit a PUR configuration to the UE. In some cases, various aspects of the EDT random access procedure may include providing a transmission for the PUR request and configuration information to be sent between the base station and the UE. In some cases, a PUR request for a PUR configuration or a PUR reconfiguration by a UE may provide an indication of the number of instances of the PUR grant requested. In such cases, the UE may indicate the value of the number of such PUR grants requested, may indicate that an indefinite number of PUR grants are requested (i.e., such grants are to continue indefinitely), or may indicate that zero PUR grants are requested and that the PUR configuration is to be released. Additionally or alternatively, in some cases, the base station may determine that the requested PUR reconfiguration is not available to the UE and may transmit to the UE a PUR rejection indication that may also indicate how the UE is to handle the existing PUR configuration. In some cases, the base station may indicate that the UE is to release the existing PUR configuration. In other cases, the base station may indicate that the UE is to maintain the existing PUR configuration. In some cases, the indication from the base station may be an explicit indication of the provided PUR rejection indication. Such techniques may allow for single-message data transmission from a UE. Such single-message transmission may have reduced overhead relative to other techniques for uplink transmission of relatively small amounts of data, such as techniques that employ a four-step uplink random access procedure to allow for data transmission in a fifth message (MSG5), or EDT random access techniques that provide for data transmission in a third message (MSG3). In the case of using legacy random access procedures or EDT procedures, such techniques still rely on a grant from the base station before a UE in an idle mode can transmit uplink data. As discussed herein, single-message uplink transmission from a UE in an idle mode and having an up-to-date timing advance (TA) can be supported, with further reduced overhead relative to random access or EDT techniques. Such reduced overhead can enhance transmission efficiency and reduce power consumption. In some cases, UEs (e.g., enhanced machine type communication (eMTC) UEs or narrowband Internet of Things (NB-IoT) UEs) that have relatively small amounts of data to transmit at certain intervals while maintaining an up-to-date (i.e., having an up-to-date TA) may benefit from the reduced signaling overhead of the techniques discussed herein. Aspects of the present invention are initially described in the context of a wireless communication system. Then, several exemplary processing procedure flows for signal transfer between a UE and a base station to configure and use PUR resources are discussed. Aspects of the present invention are further illustrated and described with reference to device diagrams, system diagrams, and flowcharts related to PUR in radio communication. Figure 1 illustrates an example of a wireless communication system 100 that supports PUR technology in wireless communication according to various aspects of the present invention. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices. The base station 105 may wirelessly communicate with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB, or a giga NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or some other suitable term. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein may be capable of communicating with various types of base stations 105 and network devices including macro eNBs, small cell eNBs, gNBs, relay base stations, etc. Each base station 105 may be associated with a specific geographical coverage area 110 that supports communication with respective UEs 115. Each base station 105 may provide communication coverage for the respective geographical coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105 or a downlink transmission from the base station 105 to the UE 115. The downlink transmission may also be referred to as a forward link transmission, and the uplink transmission may also be referred to as a reverse link transmission. The geographical coverage area 110 of the base station 105 can be divided into sectors that form a part of the geographical coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells or various combinations thereof. In some instances, the base station 105 can be mobile and thus provide communication coverage for a mobile geographical coverage area 110. In some instances, different geographical coverage areas 110 associated with different technologies can overlap, and the overlapping geographical coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network, where different types of base stations 105 provide coverage for respective geographical coverage areas 110. The term "cell" refers to a logical communication entity used to communicate with the base station 105 (e.g., via a carrier wave) and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) used to distinguish adjacent cells operating via the same carrier wave or different carrier waves. In some instances, a carrier wave can support multiple cells, and different cells can be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), etc.) that can provide access for different types of devices. In some cases, the term "cell" can refer to a part of the geographical coverage area 110 (e.g., a sector) over which the logical entity operates. UEs 115 can be dispersed throughout the wireless communication system 100, and each UE 115 can be fixed or mobile. A UE 115 can also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a user device or some other suitable term, where a "device" can also be referred to as a unit, a station, a terminal, or a client. A UE 115 can also be 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 instances, a UE 115 can also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, etc., which can be implemented in various items such as appliances, vehicles, meters, etc. Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide for automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some instances, M2M communication or MTC may include communication from devices integrated with sensors or meters to measure or capture information and relay the information to a central server or application, which may utilize the information or present the information to a person interacting with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, health monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security detection, physical access control, and transaction-based business charging. Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication by transmitting or receiving but not simultaneously transmitting and receiving). In some instances, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving "deep sleep" mode when not participating in active communication or operating on a limited bandwidth (e.g., according to narrowband communication). In some cases, UEs 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for such functions. In some cases, UEs 115 may also be capable of communicating directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs in a group of UEs 115 that utilize D2D communication may be within the geographical coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographical coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, each group of UEs 115 that communicate via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some cases, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication occurs between UEs 115 without involving the base station 105. Base station 105 can communicate with the core network 130 and with each other. For example, base station 105 can interface with core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) via a backhaul link 134 (e.g., via X2, Xn, or other interfaces). Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC), which can include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with the EPC. User IP packets can be transmitted via the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be connected to the network operator IP service. The operator IP service can include access to the Internet, one or more enterprise intranets, IP multimedia subsystem (IMS), or packet switched (PS) streaming services. At least some of the network devices such as base station 105 can include sub-components such as access network entities, which can be instances of access node controllers (ANC). Each access network entity can communicate with UE 115 via several other access network transmission entities, which can be referred to as radio device heads, intelligent radio device heads, or transmission / reception points (TRP). In some configurations, the various functions of each access network entity or base station 105 can be distributed across various network devices (e.g., radio device heads and access network controllers) or combined into a single network device (e.g., base station 105). Wireless communication 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 of 300 MHz to 3 GHz is called the ultra-high frequency (UHF) region or the decimeter band because the wavelength ranges from approximately one decimeter to one meter. UHF waves can be blocked or redirected by buildings and environmental features. However, the waves can penetrate structures sufficiently to enable macro cells to serve UEs 115 located indoors. Compared to the transmission of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, the transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km). The wireless communication system 100 may also operate in the super high frequency (SHF) region using a frequency band of 3 GHz to 30 GHz, also known as the centimeter band. The SHF region includes frequency bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which can be opportunistically used by devices that may be able to tolerate interference from other users. The wireless communication system 100 may also operate in the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the individual devices may even be smaller and closer spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, compared to SHF or UHF transmissions, the propagation of EHF transmissions may suffer even greater atmospheric attenuation and shorter distances. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across such frequency regions may vary by country or regulatory authority. In some cases, the wireless communication system 100 may utilize both licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 may employ licensed-assisted access (LAA), long term evolution-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz ISM band. When operating in an unlicensed radio spectrum band, wireless devices such as the base station 105 and the UE 115 may employ a listen-before-talk (LBT) procedure to ensure that the channel is idle before transmitting data. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration in combination with a component carrier operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum may include downlink transmissions, uplink transmissions, sidelink transmissions, or a combination of such transmissions. Duplexing in the unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both. In some examples, base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication system 100 may use a transmission scheme between a transmission device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmission device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication can utilize multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (this can be referred to as spatial multiplexing). The multiple signals can be transmitted, for example, by the transmission device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as an individual spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) with multiple spatial layers transmitted to the same receiving device and multi-user MIMO (MU-MIMO) with multiple spatial layers transmitted to multiple devices. 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 transmission device or a receiving device (e.g., base station 105 or UE 115) to shape or control an antenna beam (e.g., a transmit beam or a receive beam) along the spatial path between the transmission device and the receiving device. Beamforming can be achieved by combining the signals transmitted by the antenna elements of an antenna array such that signals propagating in a specific direction relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted by the antenna elements can include the transmission device or the receiving device applying certain amplitude and phase offsets to the signals carried by each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a specific direction (e.g., relative to the antenna array of the transmission device or the receiving device or relative to some other direction). In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, the communication at the carrier or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer may perform prioritization and multiplex logical channels into transport channels. The MAC layer may also use Hybrid Automatic Repeat reQuest (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of the RRC connection between the UE 115 and the base station 105 or the core network 130 supporting the user plane data over a radio bearer. At the physical layer, the transport channels may be mapped to physical channels. In some cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood of successful reception of the data. HARQ feedback is a technique that increases the likelihood of correctly receiving data over the communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat reQuest (ARQ)). In poor radio conditions (e.g., signal-to-noise ratio conditions), HARQ may improve the throughput at the MAC layer. In some cases, a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback for data received in a previous symbol within a particular slot during that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval. The time intervals in LTE or NR may be expressed as multiples of a basic time unit, which may refer to, for example, the sampling period T s = 1 / 30,720,000 seconds. The time intervals of the communication resources may be organized according to radio frames with a duration of 10 milliseconds (ms) each, where the frame period may be expressed as T f = 307,200 T sA radio frame can be identified by a system frame number (SFN) in the range of 0 to 1023. Each frame may include 10 sub-frames numbered from 0 to 9, and the duration of each sub-frame can be 1 ms. The sub-frame can be further divided into 2 time slots each with a duration of 0.5 ms, and each time slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). Except for the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, the sub-frame may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 may be shorter than the sub-frame or may be dynamically selected (e.g., in the pulse of a shortened TTI (sTTI) or in the selected component carrier using sTTI). In some wireless communication systems, a time slot can be further divided into multiple mini-slots containing one or more symbols. In some examples, the symbol or mini-slot of the mini-slot can be the smallest scheduling unit. For example, the duration of each symbol can vary according to the subcarrier spacing or the operating frequency band. Additionally, some wireless communication systems can implement time slot aggregation, where multiple time slots or mini-slots are aggregated together and used for communication between the UE 115 and the base station 105. The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication via the communication link 125. For example, the carrier of the communication link 125 may include a portion of the radio frequency spectrum band that operates according to the physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. The carrier may be associated with a predefined channel (e.g., the evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be positioned according to the channel raster for discovery by the UE 115. The carrier can be a downlink or an uplink (e.g., in the FDD mode) or can be configured to carry downlink and uplink communications (e.g., in the TDD mode). In some instances, the signal waveform transmitted by the carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). For different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR), the organizational structure of a carrier may be different. For example, communication carried by a carrier may be organized according to a TTI or a time slot, and each of these TTIs or time slots may include user data and control information or signaling for supporting the decoding of the user data. A carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling for coordinating the operation of the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information transmitted in a physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or a common search space and one or more UE-specific control regions or UE-specific search spaces). A carrier may be associated with a specific bandwidth of the radio spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of several predefined bandwidths of a carrier of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 may be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or RBs) within the carrier (e.g., "in-band" deployment of the narrowband protocol type). In a system adopting MCM technology, a resource element may consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are negatively correlated. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate of the UE 115. In a MIMO system, the wireless communication resources may refer to a combination of radio spectrum resources, time resources, and space resources (e.g., spatial layers), and using multiple spatial layers may further increase the data rate of communicating with the UE 115. Devices (e.g., base station 105 or UE 115) of the wireless communication system 100 may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configured to support communication on one of a set of carrier bandwidths. In some instances, the wireless communication system 100 may include base stations 105 and / or UEs 115 that support simultaneous communication via carriers associated with more than one different carrier bandwidth. In some cases, the UE 115 and the base station 105 may use PUR to help reduce signaling overhead associated with uplink transmissions. In some cases, the base station 105 may transmit a PUR support indication (e.g., via SIB). The UE 115 may receive the indication and transmit a PUR request to the base station 105. The PUR response from the base station 105 may indicate to the UE 115 the PUR allocation available for uplink transmission. In some cases, the base station 105 may provide a PUR allocation in the PUR request that is different from the requested PUR configuration provided by the UE 115. The UE 115 may determine that the different PUR configuration is not sufficient for the UE 115 and may transmit a PUR configuration failure to the base station 105. In some cases, the transmission from the base station 105 to the UE 115 indicating the PUR configuration may provide an uplink resource indication that may be used by the UE 115 to transmit a PUR configuration failure indication. In some cases, the EDT random access procedure may be used to transmit the PUR request from the UE 115 and may be used by the base station 105 to transmit the PUR configuration to the UE 115. Additionally or alternatively, the PUR request by the UE 115 for a PUR configuration or PUR reconfiguration may provide an indication of the number of instances of the requested PUR grant. Additionally or alternatively, the base station 105 may determine that the requested PUR reconfiguration is not available for the UE 115 and may transmit a PUR rejection indication to the UE 115 that may also indicate how the UE 115 is to handle the existing PUR configuration (e.g., whether to release the existing PUR configuration or maintain the existing PUR configuration). Figure 2 illustrates an example of a wireless communication system 200 that supports PUR techniques in wireless communication in accordance with various aspects of the present invention. In some instances, the wireless communication system 200 may implement aspects of the wireless communication system 100. In some instances, the wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be examples of corresponding devices as described with reference to FIG. 1. The UE 115-a may communicate with the base station 105-a within the coverage area 110-a via downlink transmissions 205 and uplink transmissions 210. In some cases, the base station 105-a may configure a resource set as a PUR available for uplink transmission of the UE 115-a and other UEs served by the base station 105-a. In some cases, the UE 115-a and the base station 105-a may operate using eMTC communication or NB-IoT communication, and the UE 115-a may have periodic transmissions of a relatively small amount of data (such as data associated with sensor readings or device status). In some cases, the UE 115-a may be stationary or may move within a relatively small area (e.g., in a factory automation deployment), and may thus still have an up-to-date timing advance (TA) for synchronizing to the uplink transmission of the base station 105-a even when the UE 115-a exits the idle mode to send an uplink transmission. In some cases, the base station 105-a may provide a PUR indication 215 indicating support for PUR at the base station 105-a. Such an indication may be provided, for example, in the SIB or other downlink signaling (e.g., in the physical broadcast channel (PBCH) transmitted with a synchronization signal block (SSB), remaining minimum system information (RMSI), etc.). The UE 115-a may receive the PUR indication 215 and determine that the data transmission requirements at the UE 115-a would benefit from preconfigured uplink transmission. For example, if the UE 115-a has a periodic uplink transmission with a size less than a transmission size threshold, the UE 115-a may determine to request a PUR configuration from the base station 105-a. Additionally or alternatively, if the UE 115-a has relatively high-priority traffic (e.g., data traffic of critical system or security-related information), the UE 115-a may determine to request a PUR configuration from the base station 105-a. In some cases, the PUR indication 215 may provide an indication of the data size of the associated uplink transmission available to the UE 115-a for determining whether to request a PUR configuration. UE 115-a can determine the PUR configuration requested and can transmit a PUR request 225 to the base station 105-a. In some cases, UE 115-a may be in the connected mode (e.g., in the RRC connected mode) when it sends the PUR request 225 and can use a dynamic uplink grant (e.g., uplink resources allocated by the base station 105-a in the downlink control information (DCI) and indicated to UE 115-a) or transmit the message in a pre-configured grant (e.g., a semi-persistent scheduling (SPS) grant previously provided to UE 115-a). In some cases, UE 115-a may be in the idle mode (e.g., RRC idle mode) and use EDT to send the PUR request 225 if the base station 105-a supports EDT. Additionally, in some cases, UE 115-a may have an existing PUR allocation and can use a previously configured PUR grant to send a PUR request 225 for reconfiguration of the existing PUR allocation. The base station 105-a can receive the PUR request 225 and determine the PUR configuration or reconfiguration of UE 115-a, which can be transmitted to UE 115-a in the PUR allocation 220. In some cases, the base station 105-a can determine that sufficient PUR resources are not available for the request from UE 115-a (e.g., because other UEs have higher-priority data using PUR) and can transmit a PUR rejection message, which can indicate whether to maintain or release the existing PUR configuration if there is an existing PUR configuration. When receiving a PUR rejection message indicating the release of the existing PUR configuration or when there is no existing PUR configuration, UE 115-a can fallback to a legacy uplink technology (e.g., a legacy random access procedure or an EDT random access procedure). In some cases, UE 115-a can optionally confirm the receipt of the PUR allocation 220 (or rejection). In the case of configuring or reconfiguring UE 115-a with the PUR allocation, UE 115-a can then transmit uplink data 230 using the resources indicated in the PUR configuration. In this way, UE 115-a can be in the idle mode (e.g., RRC idle mode) and can transmit uplink data in a single uplink transmission (e.g., similar to a random access MSG1 transmission) without receiving a separate uplink grant using the PUR allocation. In some cases, UE 115-a can determine to request a PUR configuration based on, for example, the traffic pattern of the uplink data (e.g., packet size, interval rate, etc.), QOS requirements, or a combination thereof. Figure 3 illustrates an example of a processing procedure flow 300 that supports the PUR technology in wireless communication according to various aspects of the present invention. In some examples, the processing procedure flow 300 may implement various aspects of the wireless communication system 100 or 200. In this example, the processing procedure flow 300 includes a UE 115-b and a base station 105-b, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2. At 305, the base station 105-b and the UE 115-b may perform connection establishment (e.g., RRC connection establishment). Such connection establishment may be performed using a connection establishment procedure established for wireless communication (e.g., using a random access technology established in an LTE system or an NR system). At 310, the base station 105-b may identify PUR resources and format a system information block (SIB) indicating PUR support. In some cases, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using PUR, the traffic or service priority associated with a PUR grant, etc. In some cases, the SIB may provide an index to a preconfigured mapping to a PUR configuration. In some cases, the base station 105-b may configure several different PUR sets, and the SIB may be formatted to indicate the multiple PUR sets. At 315, the base station 105-b may transmit the SIB with a PUR support indication, and the UE 115-b may receive the SIB with a PUR support indication. In this example, the UE 115-b may be in a connected mode, and at 320, the base station 105-b may provide an uplink grant to the UE 115-b. For example, the uplink grant may be provided based on a buffer status report (BSR) provided by the UE 115-b. At 325, the UE 115-b may format a PUR request message. For example, the PUR request message may request a new PUR configuration. In some cases, the UE 115-b may have an existing PUR configuration, and the PUR request may be for a reconfiguration of the existing PUR configuration (e.g., based on changes in updated data traffic at the UE 115-b, the presence of higher-priority data at the UE 115-b, etc.). At 330, the UE 115-b may transmit the PUR request message. In some cases, the uplink resources provided in the uplink grant may be used to transmit the PUR request message. In other cases, as discussed in more detail below, the UE 115-b may use other uplink resources (e.g., semi-persistent scheduling (SPS) resources, enhanced dedicated transmission (EDT) random access procedure transmissions, other existing PUR resources, etc.) to transmit the PUR request message. At 335, the base station 105-b can receive a PUR request message and determine the PUR configuration of the UE 115-b. In some cases, the base station 105-b can determine the PUR configuration based on one or more of the following: QoS information provided in the PUR request, the type of PUR requested (e.g., whether it is a request for an acknowledged mode (AM) or unacknowledged mode (UM) PUR), other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof. At 340, the base station 105-b can transmit a PUR confirmation message indicating the PUR configuration of the UE 115-b to the UE 115-b. In some cases, the PUR configuration can provide a new PUR allocation for the UE 115-b. In other cases, the PUR configuration can be a reconfigured allocation of an existing PUR configuration of the UE 115-b. In some cases, the PUR configuration can be shared by multiple different UEs, and the PUR configuration can indicate shared resources and provide information that can be used by the UE 115-b to allow the base station 105-b to distinguish transmissions from the UE 115-b (e.g., a preamble to be provided for uplink transmission, a spreading sequence to be applied to the uplink transmission, a cyclic shift to be applied to the sequence, etc.). At 345, the UE 115-b can identify the PUR configuration provided by the base station 105-b. In the case where the PUR configuration is a new configuration, the UE 115-b can configure the uplink transmission to use the allocated PUR resource configuration for transmission. In the case where the PUR configuration is a reconfiguration of an existing PUR configuration, the UE 115-b can reconfigure the PUR configuration according to the new PUR configuration. At 350, the UE 115-b can transmit a PUR configuration (or reconfiguration) completion message to the base station 105-b as appropriate. In some cases, as discussed in more detail below, the UE 115-b can determine that the received PUR configuration is not suitable for the UE (e.g., because the amount of the PUR grant is lower than the amount required for transmissions of a particular priority, etc.). In such cases, the UE 115-b can transmit a PUR failure indication that can allow both the UE 115-b and the base station 105-b to release the configured resources of the PUR configuration, rather than transmitting a configuration completion indication. In some cases, such uplink resources for indication to the base station 105-a can be indicated in the PUR confirmation message (e.g., in an explicit uplink grant, a window in which the UE 115-b is to monitor PDCCH transmissions using the uplink grant, the first instance of the PUR grant, etc.). Figure 4 illustrates another example of a processing procedure flow 400 that supports PUR technology in wireless communication according to various aspects of the present invention. In some examples, the processing procedure flow 400 may implement various aspects of the wireless communication system 100 or 200. In this example, the processing procedure flow 400 includes a UE 115-c and a base station 105-c, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2. At 405, the UE 115-c may be in the idle mode. In some cases, the UE 115-c may have previously performed connection establishment and may be idle due to a lack of uplink data or downlink data to be transmitted (e.g., in the RRC_IDLE mode). At 410, the base station 105-c may identify PUR resources and format a system information block (SIB) indicating PUR support. In some cases, as discussed with respect to FIG. 3, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using the PUR resources, the traffic or service priority associated with the PUR configuration, etc. In some cases, the SIB may provide an index to a pre-configured mapping to the PUR configuration. In some cases, the base station 105-c may configure several different PUR configurations, and the SIB may be formatted to indicate the multiple PUR configurations. At 415, the base station 105-c may transmit the SIB with a PUR support indication, and the UE 115-c may receive the SIB with a PUR support indication. In this example, the UE 115-c may be in the idle mode, and at 420, the UE 115-c may receive the SIB and identify that the base station 105-c supports PUR. In some cases, the UE 115-c may periodically monitor the SIB and other downlink control transmissions while in the idle mode and may receive the SIB during such monitoring. At 425, the UE 115-c may identify uplink data for PUR and format a PUR request message. For example, the PUR request message may request a new PUR configuration. In some cases, the UE 115-c may have an existing PUR configuration, and the PUR request may be for a reconfiguration of the existing PUR configuration (e.g., based on changes in updated data traffic at the UE 115-c, the presence of higher-priority data at the UE 115-c, etc.). At 430, UE 115-c may transmit a PUR request message. In some cases, SPS resources previously allocated to UE 115-c, for example, may be used to transmit the PUR request message. In other cases, UE 115-c may perform a random access procedure and transmit a PUR request upon completion of the random access procedure (e.g., in a MSG5 transmission). In still other cases, UE 115-c may have an existing PUR allocation and may use the existing PUR allocation to transmit the PUR request. Additionally, in some cases, as discussed in more detail with respect to FIG. 7, the PUR request message may be transmitted in an EDT random access message. At 435, base station 105-c may receive the PUR request message and determine the PUR configuration for UE 115-c. In some cases, base station 105-c may determine the PUR configuration based on one or more of the following: QoS information provided in the PUR request, whether an AM or UM PUR is requested, other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof. At 440, base station 105-c may transmit a PUR confirmation message indicating the PUR configuration for UE 115-c to UE 115-c. In some cases, the PUR configuration may be a new configuration for UE 115-c. In other cases, the PUR configuration may be a reconfigured configuration of an existing PUR configuration for UE 115-c. In some cases, the PUR configuration may be shared by multiple different UEs, and the PUR configuration may indicate shared resources and provide information (e.g., a preamble to be provided for uplink transmission, a spreading sequence to be applied to the uplink transmission, a cyclic shift to be applied to the sequence, etc.) that may be used by UE 115-c to allow base station 105-c to distinguish transmissions from UE 115-c. At 445, UE 115-c may identify the PUR configuration provided by base station 105-c. In the case where the PUR configuration is a new configuration, UE 115-c may configure uplink transmissions to use the PUR configuration for transmission. In the case where the PUR configuration is a reconfiguration of an existing PUR configuration, UE 115-c may reconfigure the PUR configuration according to the new PUR configuration. At 450, UE 115-c may transmit a PUR configuration (or reconfiguration) completion message (or a PUR configuration failure message) to base station 105-c as appropriate. Figure 5 illustrates an example of a processing procedure flow 500 that supports PUR techniques in wireless communication according to aspects of the present invention. In some examples, the processing procedure flow 500 may implement aspects of wireless communication systems 100 or 200. In this example, the processing procedure flow 500 includes UE 115-d and base station 105-d, which may be examples of corresponding devices described with reference to FIGS. 1 and 2. At 505, UE 115-d may be in an idle mode. In some cases, UE 115-d may have previously performed connection establishment and may be idle due to a lack of uplink data or downlink data to transmit. At 510, base station 105-d may identify EDT support and PUR resources and format a system information block (SIB) indicating PUR support and EDT support. In some cases, the base station may use a separate SIB to indicate PUR support and EDT support. In some cases, as discussed with respect to FIGS. 3 and 4, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using PUR resources, the traffic or service priority associated with the PUR configuration, and the like. In some cases, the SIB may provide an index to a pre-configured mapping to the PUR configuration. In some cases, base station 105-d may configure several different PUR configurations, and the SIB may be formatted to indicate the multiple PUR configurations. At 515, base station 105-d may transmit the SIB with the PUR support indication, and UE 115-d may receive the SIB with the PUR support indication. In this example, UE 115-d may be in an idle mode, and at 520, UE 115-d may receive one or more SIBs and identify that base station 105-d supports EDT and PUR. In some cases, UE 115-d may periodically monitor SIBs and other downlink control transmissions while in the idle mode and may receive one or more SIBs during such monitoring. At 525, UE 115-d may identify the uplink data for PUR and format a PUR request message for transmission in EDT. For example, the PUR request message may request a new PUR configuration. In some cases, UE 115-d may have an existing PUR configuration, and the PUR request may be for a reconfiguration of the existing PUR configuration (e.g., based on changes in updated data traffic at UE 115-d, the presence of higher-priority data at UE 115-d, etc.). At 530, UE 115-d may transmit the PUR request message (e.g., after EDT). In some cases, according to techniques for establishing the transmission of EDT as will be discussed in more detail with respect to FIG. 7, UE 115-d may transmit a random access request and provide the PUR request in the EDT associated with the random access procedure. At 535, base station 105-d may receive the PUR request message and determine the PUR configuration for UE 115-d. In some cases, base station 105-d may determine the PUR configuration based on one or more of the following: the QoS information provided in the PUR request, whether the request is for AM or UM PUR, the other PUR configurations for other UEs, the amount of available PUR resources, or any combination thereof. At 540, base station 105-d may transmit to UE 115-d a PUR confirmation message indicating the PUR configuration of UE 115-d. In some cases, the PUR configuration may be a new configuration for UE 115-d. In other cases, the PUR configuration may be a reconfigured existing PUR configuration for UE 115-d. In some cases, the PUR configuration may be shared by multiple different UEs, and the PUR configuration may indicate shared resources and provide information (e.g., a preamble to be provided for uplink transmission, a spreading sequence to be applied to the uplink transmission, a cyclic shift to be applied to the sequence, etc.) that can be used by UE 115-d to allow base station 105-d to identify transmissions from UE 115-d. At 545, UE 115-d may identify the PUR configuration provided by base station 105-d. In the case where the PUR configuration is a new configuration, UE 115-d may configure the uplink transmission to use the PUR configuration for transmission. In the case where the PUR configuration is a reconfiguration of an existing PUR configuration, UE 115-d may reconfigure the PUR configuration according to the new PUR configuration. At 550, UE 115-d may optionally transmit to base station 105-d a PUR configuration (or reconfiguration) completion message (or a configuration failure message). As indicated above, in some cases, the base station may determine that the PUR configuration corresponding to the received PUR request is not available, and the base station may provide a different PUR configuration for the UE (e.g., where fewer PUR grants are available for uplink transmissions from the UE) to use. In such cases, the UE may determine whether the different PUR configuration is sufficient to meet the UE's needs. In the case where the different PUR configuration is not sufficient to correctly serve the data associated with the requested PUR configuration, in response to receiving the different PUR configuration, the UE may transmit a PUR configuration failure message to the base station. FIG. 6 illustrates an example of a procedure flow in which the UE may provide such a PUR configuration failure message. Figure 6 illustrates an example of a procedure flow 600 supporting PUR techniques in wireless communication according to aspects of the present invention. In some examples, the procedure flow 600 may implement aspects of wireless communication system 100 or 200. In this example, the procedure flow 600 includes UE 115-e and base station 105-e, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2. At 605, base station 105-e and UE 115-e may each determine that the PUR condition is satisfied. Such determination may be made as discussed in various examples herein, such as based on base station 105-a establishing one or more PUR configurations and providing an indication thereof to the UE (e.g., in an SIB), and UE 115-e may receive the indication to determine the requested PUR configuration. At 610, the UE may identify uplink resources for transmitting a PUR request message. In some cases, the uplink resources may be provided in an uplink grant associated with the connected mode UE 115-e. In other cases, the connected mode or idle mode UE 115-e may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.). At 615, the UE may format the PUR request message. For example, the PUR request message may request a new configuration of PUR resources. In some cases, the UE 115-e may have an existing PUR allocation, and the PUR request may be for a reconfiguration of the existing PUR allocation (e.g., based on updated data traffic at the UE 115-e, changes due to the presence of higher priority data at the UE 115-e, etc.). At 620, the UE 115-e may transmit the PUR request message, and the base station 105-e may receive the PUR request message. At 625, the base station 105-e may determine that the requested PUR allocation for the UE 115-e is not available. In some cases, the base station 105-e may determine that the PUR allocation is not available based on one or more of the following: the amount of PUR grants in the requested PUR configuration, the QoS information provided in the PUR request, whether an AM or UM PUR is requested, other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof. The base station 105-e may identify different PUR configurations available to the UE 115-e. At 630, the base station 105-e may transmit a PUR response message to the UE 115-e indicating the different PUR configurations that have been allocated for the UE 115-e. At 635, the UE 115-e may determine that the PUR configuration provided by the base station 105-e is not sufficient for the uplink transmission of the UE 115-e. For example, the UE 115-e may have uplink data to transmit at a set period (e.g., sensor data to be transmitted every 30 seconds), and the PUR configuration provided by the base station 105-e may provide PUR grants less frequently than the set period (e.g., one PUR grant every 60 seconds). Thus, in this example, based on the insufficient uplink grants in the PUR configuration, the UE 115-e may determine that the PUR configuration is not sufficient. In other examples, the UE 115-e may determine that the PUR configuration is no longer needed or cannot be applied due to other configurations conflicting with the PUR configuration. At 640, UE 115-e may transmit a PUR configuration failure indication to base station 105-e. In some cases, UE 115-e and base station 105-e may release the PUR configuration based on the PUR configuration failure indication. Such a release may allow base station 105-e to reallocate associated uplink resources to one or more other UEs and use network resources more efficiently. In some cases, when UE 115-e is in the connected mode, providing a dedicated grant may be after the PUR response message of UE 115-e to be able to send this message of the PUR configuration failure message. In some cases, the uplink dedicated grant may be provided in the PUR configuration or in the PUR response message itself. Additionally or alternatively, UE 115-e may monitor the PDCCH during a window period after the PUR response message to obtain a UL grant for use when transmitting a PUR configuration failure message (or a PUR configuration confirmation message). In some cases, UE 115-e may be in the idle mode, and the uplink grant may be provided after the PUR response message of UE 115-e to be able to send a PUR configuration failure from the idle mode. In some cases, the uplink grant may be provided in the PUR configuration or in the PUR response message itself. Additionally or alternatively, UE 115-e may monitor the PDCCH during a window period after the PUR response message to obtain an uplink grant for use when transmitting a PUR configuration failure message (or a PUR configuration confirmation message) when in the idle mode. In another case, additionally or alternatively, a procedure may be defined in which, when in the idle mode, UE is expected to use the first occurrence of a new (or reconfigured) PUR to transmit a PUR configuration failure message (or a PUR configuration confirmation message). As indicated with respect to FIG. 5, in some cases, the EDT procedure may be used to exchange PUR requests and configuration messages. FIG. 7 illustrates an example of a processing procedure flow 700 that supports PUR techniques in EDT according to aspects of the present invention. In some examples, the processing procedure flow 700 may implement aspects of wireless communication system 100 or 200. In this example, the processing procedure flow 700 includes UE 115-f and base station 105-f, and the UE and the base station may be examples of the corresponding devices described with reference to FIGS. 1 and 2. At 705, UE 115-f may be in an idle mode. In some cases, UE 115-f may have previously performed connection establishment and may be idle due to a lack of uplink data or downlink data to transmit. At 710, base station 105-f may identify EDT support and PUR resources and format a system information block (SIB) indicating PUR support and EDT support. In some cases, base station 105-f may determine whether to allow UE 115-f to use EDT to request PUR configuration / reconfiguration / release. In some cases, the base station may use a separate SIB to indicate PUR support and EDT support. In some cases, as discussed with respect to FIGS. 3 and 4, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using PUR resources, the traffic or service priority associated with the PUR configuration, etc. In some cases, the SIB may provide an index to a preconfigured mapping to the PUR configuration. In some cases, base station 105-f may configure several different PUR configurations, and the SIB may be formatted to indicate the multiple PUR configurations. At 715, base station 105-f may transmit the SIB with PUR support and EDT support indications, and UE 115-f may receive the SIB with PUR support and EDT support indications. In this example, UE 115-f may be in an idle mode, and at 720, UE 115-f may receive one or more SIBs and identify that base station 105-f supports EDT and PUR. In some cases, UE 115-f may periodically monitor SIBs and other downlink control transmissions while in the idle mode and may receive one or more SIBs during such monitoring. At 725, UE 115-f may identify uplink data for PUR and initiate an EDT procedure. At 730, according to the EDT procedure, UE 115-f may transmit a first EDT message (EDT MSG1) that may include a random access channel (RACH) preamble. Base station 105-f may receive the EDT message and transmit a random access response including EDT MSG2. For example, the random access response may include an identifier associated with UE 115-f and a resource allocation (e.g., resource block allocation) for subsequent EDT messages and a modulation and coding scheme (MCS). At 740, UE 115-f may format a PUR request message to be transmitted in the EDT. For example, the PUR request message may request a new PUR configuration. In some cases, UE 115-f may have an existing PUR configuration, and the PUR request may be for reconfiguration of the existing PUR configuration or release of the existing PUR configuration (e.g., based on changes in updated data traffic at UE 115-f, the presence of higher priority data at UE 115-f, etc.). At 745, the UE 115-f may use an EDT MSG3 to transmit a PUR request message. At 750, the base station 105-f may receive the PUR request message and determine the PUR configuration of the UE 115-f. In some cases, the base station 105-f may determine the PUR configuration based on one or more of the following: the requested PUR configuration, the QoS information provided in the PUR request, whether an AM or UM PUR is requested, the other PUR configurations to other UEs, the amount of available PUR resources, or any combination thereof. At 755, the base station 105-f may transmit a PUR response in an EDT MSG4. The PUR response may indicate the PUR configuration of the UE 115-f. In some cases, the PUR configuration may be a new configuration for the UE 115-f. In other cases, the PUR configuration may be a reconfigured existing PUR configuration of the UE 115-f. In some cases, the PUR configuration may be shared by multiple different UEs, and the PUR configuration may indicate shared resources and provide information (e.g., a preamble to be provided for uplink transmission, a spreading sequence to be applied to the uplink transmission, a cyclic shift to be applied to the sequence, etc.) that can be used by the UE 115-f to allow the base station 105-f to identify transmissions from the UE 115-f. At 760, the UE 115-f may identify the PUR configuration provided by the base station 105-f. In the case where the PUR configuration is a new configuration, the UE 115-f may configure the uplink transmission to use the PUR configuration for transmission. In the case where the PUR configuration is a reconfiguration of an existing PUR configuration, the UE 115-f may reconfigure the PUR configuration according to the new PUR configuration. At 765, the UE 115-f may transmit a PUR configuration (or reconfiguration) completion message to the base station 105-f as appropriate. Thus, in this example, UE 115-f and base station 105-f can use the Mobile Originated (MO) EDT procedure 770 to transmit PUR requests and PUR responses. In other cases, as depicted in FIG. 5, PUR requests and PUR responses can be exchanged after the EDT procedure. In some cases, UE 115-f can use the Control Plane CIoT EPS Optimization based EDT (CP-EDT) procedure from the idle mode. In other cases, UE 115-f can use the User Plane CIoT EPS Optimization based EDT (UP-EDT) from the idle mode. In some cases, the EDT RRC messages (e.g., RRCEarlyDataRequest for CP-EDT, RRCConnectionResumeRequest for UP-EDT) can be extended to include PUR configuration, reconfiguration, or release information elements. For example, such information elements can be appended or concatenated with other RRC information elements. In one example, the establishmentCause can be used to indicate that the EDT MSG3 includes a PUR configuration, reconfiguration, or release request. For CP-EDT, if there is no uplink payload (user data), the dedicatedInfoNAS can be empty, and the uplink payload can indicate that the message is a PUR request. In other cases, separate RRC messages can be included in the EDT MSG3 transmission, one for EDT and one for the PUR request message (i.e., the PUR configuration / reconfiguration / release request message). Additionally, as indicated in FIG. 7, base station 105-f can transmit EDT MSG4 with a PUR response. The PUR response can include a PUR configuration, reconfiguration, or release message as a response. In some cases, the EDT MSG4 can be an RRC data early completion or an RRC connection release with a suspension indication. In some cases, such RRC messages can be extended to include a PUR configuration / reconfiguration or release indication. In other cases, separate RRC messages can be included in the EDT MSG4, i.e., one RRC message for EDT and one RRC message providing the PUR configuration / reconfiguration or release message. In some cases, for signaling efficiency, delta configuration can be used to configure or reconfigure PUR. Such delta configuration can only provide the parameters for the change of the current configuration of UE 115-f from the previous PUR configuration or from the default PUR configuration, and any non-existent parameters are assumed to have default values or invariant values from the current UE values (e.g., EARFCN). As indicated, in some cases, the EDT MSG4 may provide (e.g., for CP-EDT) an RRC data early completion message. In some cases, such a message may contain an implicit or explicit indication that, regarding the PUR resources, UE 115-f may perform one or more of the following: continue to use the allocated random access MSG1 data resources that have been (previously) allocated (i.e., the existing PUR configuration), confirm the validity or invalidity of the PUR configuration that has been (previously) allocated, de-configure or release the PUR configuration that has been (previously) allocated, allocate new Msg1 data resources, or any combination thereof. In some cases, an explicit indication for PUR release may be provided in a boolean flag to indicate the release of the PUR resources, and in the absence of such a flag, when UE 115-f returns to the idle mode, the PUR of the previous configuration is considered to still be valid. In some cases, the boolean flag may be included in the RRC connection release message or the RRC connection resume message. In some cases, the base station 105-f may indicate that PUR is not supported by providing an SIB indication to call for indicating that PUR support is turned off for all UEs, in which case UE 115-f (and other UEs that can receive the SIB) may release any PUR configuration. Additionally or alternatively, the base station 105-f may determine that the PUR configuration of UE 115-f is to be reconfigured. For example, the base station 105-f may determine that the resources allocated to the PUR are to be reallocated to another PUR configuration (e.g., a higher priority PUR configuration). In such cases, the base station 105-f may initiate a PUR reconfiguration or release indication that may be provided in an EDT downlink message (e.g., EDT MSG2 or EDT MSG4). For example, the base station 105-f may transmit a paging to UE 115-f in the idle mode to trigger UE 115-f to establish an RRC connection, and once UE 115-f is in the connected mode, the base station 105-f may provide a release indication or a release command message or a reconfiguration of the PUR. In some cases, an explicit PUR release message may be provided by the base station 105-f to indicate to UE 115-f that the configured PUR should be released. In addition, in some cases, when the UE 115-f transmits a PUR request message, one or more items of auxiliary information may be provided, such as the UE's coverage enhancement (CE) level or traffic-related information. Such traffic-related information may include, for example, one or more of the following: traffic period (or traffic arrival pattern), traffic probability (i.e., whether the UE will always transmit data or sometimes have no data), delay tolerance associated with the traffic, packet size to be transmitted, or any combination thereof. Additionally or alternatively, in some cases, the UE 115-f may also provide a PUR configuration or reconfiguration request message, the number of PUR grants requested to occur. In some cases, the number of occurrences may be indicated as one to request a single-trigger PUR, or another number greater than one to request that number of multi-trigger PURs. In other cases, the number of occurrences may be indicated as infinite or indefinite to request that the PUR grant be valid indefinitely until a PUR release criterion is met. In some cases, the number of occurrences may be provided in an information element in the PUR request. In some cases, the number of occurrences may be indicated as non-existent to request that the PUR resources be valid indefinitely until one of the PUR release criteria is met. Similarly, in some cases, the number of occurrences may be indicated as zero to request the release of PUR resources, which may obviate the need for a separate PUR release request message dedicated to requesting the release. In such cases, one or more other fields in the PUR request message may be optional, such that when the release of the PUR is requested by indicating a request for zero occurrences of the PUR grant, the UE 115-f does not need to include other parameters. Additionally or alternatively, the UE 115-f may indicate a PUR reconfiguration failure as discussed with respect to FIG. 8, which PUR reconfiguration failure may indicate the release of the PUR configuration. Figure 8 illustrates an example of a processing procedure flow 800 that supports PUR technology in wireless communication according to various aspects of the present invention. In some examples, the processing procedure flow 800 may implement aspects of the wireless communication system 100 or 200. In this example, the processing procedure flow 800 includes a UE 115-g and a base station 105-g, which UE and base station may be examples of the corresponding devices described with reference to FIGS. 1 and 2. In this example, similar to in FIG. 7, the EDT procedure may be used again to exchange PUR request and configuration messages, but if the PUR configuration provided by the base station 105-h is not sufficient for the UE 115-f, the UE 115-g indicates a PUR configuration failure. In this example, at 805, UE 115-g may be in the idle mode. In some cases, UE 115-g may have previously performed connection establishment and may be idle due to lack of uplink data or downlink data to transmit. At 810, base station 105-g may identify EDT support and PUR resources and format a system information block (SIB) indicating PUR support and EDT support. At 815, base station 105-g may transmit the SIB with PUR support and EDT support indication, and UE 115-g may receive the SIB with PUR support and EDT support indication. In this example, UE 115-g may again be in the idle mode, and at 820, UE 115-g may receive one or more SIBs and identify that base station 105-g supports EDT and PUR. In some cases, UE 115-g may periodically monitor SIBs and other downlink control transmissions while in the idle mode and may receive one or more SIBs during such monitoring. At 825, UE 115-g may identify uplink data for PUR and initiate the EDT procedure. At 830, according to the EDT procedure, UE 115-g may transmit a first EDT message (EDT MSG1) that may include a random access preamble. At 835, base station 105-g may receive the EDT message and transmit a random access response including EDT MSG2. For example, the random access response may include an identifier associated with UE 115-g and a resource allocation (e.g., resource block allocation) for subsequent EDT messages and a modulation and coding scheme (MCS). At 840, UE 115-g may format a PUR request message to be transmitted in the EDT. For example, the PUR request message may request a new PUR configuration. In some cases, UE 115-g may have an existing PUR configuration, and the PUR request may be for a reconfiguration of the existing PUR configuration or a release of the existing PUR configuration (e.g., based on changes in updated data traffic at UE 115-g, the presence of higher priority data at UE 115-g, etc.). At 845, UE 115-g may use EDT MSG3 to transmit the PUR request message. At 850, base station 105-g may receive the PUR request message and determine the PUR configuration of UE 115-g. In this example, at 850, base station 105-g may determine that the requested PUR configuration is not available and may determine a different PUR configuration for UE 115-g. At 855, the base station 105-g may transmit a PUR response in the EDT MSG4. The PUR response may indicate different PUR configurations of the UE 115-g. In some cases, the PUR configuration may be a new configuration of the UE 115-g. In other cases, the PUR configuration may be a reconfigured existing PUR configuration of the UE 115-g. At 860, the UE 115-g may identify the different PUR configurations provided by the base station 105-g and determine that the different PUR configurations are insufficient (e.g., based on fewer PUR grants than required for uplink data transmission). At 865, the UE 115-g may transmit a PUR configuration (or reconfiguration) failure message to the base station 105-g. Thus, in this example, the UE 115-g and the base station 105-g may again use the MO EDT procedure 870 to send a PUR request and a PUR response. Additionally, an additional uplink transmission indicating a PUR configuration failure may be provided, where the uplink resources of the uplink transmission may be identified as discussed herein with respect to FIG. 6. In some cases, if the base station determines that the requested PUR configuration is unavailable, the base station may transmit a PUR rejection message to the UE instead of a PUR configuration or reconfiguration message. UE operations after receiving such a rejection message may be based on one or more implicit or explicit indications associated with the rejection message. FIG. 9 illustrates an example of a processing procedure flow 900 of a PUR technique that supports transmitting a PUR rejection message to a UE according to various aspects of the present invention. In some examples, the processing procedure flow 900 may implement various aspects of the wireless communication system 100 or 200. In this example, the processing procedure flow 900 includes a UE 115-h and a base station 105-h, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2. At 905, the base station 105-h and the UE 115-h may each determine that the PUR condition is satisfied. Such a determination may be made as discussed herein in various examples, such as based on the base station 105-h establishing one or more PUR configurations and providing an indication thereof to the UE (e.g., in the SIB), and the UE 115-h may receive the indication to determine the requested PUR configuration. At 910, the UE may identify uplink resources for transmitting a PUR request message. In some cases, the uplink resources may be provided in an uplink grant associated with the connected mode UE 115-h. In other cases, the connected mode or idle mode UE 115-h may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.). At 915, the UE may format a PUR request message. For example, the PUR request message may request a new configuration of PUR resources. In some cases, the UE 115-h may have an existing PUR allocation, and the PUR request may be for a reconfiguration of the existing PUR allocation (e.g., based on changes in updated data traffic at the UE 115-h, the presence of higher-priority data at the UE 115-h, etc.). At 920, the UE 115-h may transmit the PUR request message, and the base station 105-h may receive the PUR request message. At 925, the base station 105-h may determine that the requested PUR allocation for the UE 115-h is not available. In some cases, the base station 105-h may determine that the PUR allocation is not available based on one or more of the following: the amount of PUR grants in the requested PUR configuration, the QoS information provided in the PUR request, whether an AM or UM PUR is requested, other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof. The base station 105-h may identify different PUR configurations available to the UE 115-h. At 930, in the case of an existing PUR configuration, the base station 105-h may determine whether to maintain or release the existing PUR configuration of the UE 115-h. At 935, the base station 105-h may transmit a PUR rejection message to the UE 115-h, which may provide an indication for the UE 115-h to handle such an existing PUR configuration in the case of an existing PUR configuration. In the absence of an existing PUR, the UE 115-h may fallback to other techniques for uplink data transmission (e.g., scheduling request transmission, EDT procedure, random access technique, SPS transmission, etc.). In the case of an existing PUR configuration, one or more predefined rules may be provided to indicate whether to continue or release the existing PUR configuration. In some cases, if the UE 115-h does not receive a response message from the base station 105-h, the UE 115-h may assume that the PUR request is rejected and may use the predefined rules of the existing PUR configuration (if any). In some cases, the PUR rejection message may include an explicit indication for handling the existing PUR configuration. For example, the base station 105-h may indicate to the UE 115-h to reject the PUR request and release the PUR of the configuration, or reject the PUR request and maintain the PUR of the configuration. Based on the various situations for generating the PUR rejection message at the base station 105-h, such explicit indications may provide enhanced flexibility to the base station 105-h to determine and explicitly indicate the behavior of the UE 115-h. Figure FIG. 1000 is a block diagram of a device 1005 that supports PUR technology in wireless communication in accordance with various aspects of the present invention. The device 1005 may be an example of aspects of the UE 115 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses). The receiver 1010 may receive information associated with various information channels (e.g., control channels, data channels, information related to PUR technology in wireless communication, etc.) such as packets, user data, or control information. The information may be passed to other components of the device 1005. The receiver 1010 may be an example of aspects of the transceiver 1320 described with reference to FIG. 13. The receiver 1010 may utilize a single antenna or an antenna array. In some cases, the communication manager 1015 may determine that a base station supports PUR for grant-free uplink transmissions from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR, receive a PUR configuration identifying the PUR allocated to the UE from the base station in response to the PUR request message; receive an uplink resource for a response message to be transmitted from the UE; and transmit a PUR configuration response message to the base station using the uplink resource for the response message. In some cases, the communication manager 1015 may also determine an EDT configuration of an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure; format a PUR request message to be transmitted in the uplink message of the EDT procedure, where the PUR request message may indicate a requested configuration, reconfiguration, or release of the PUR configuration; transmit the PUR request message in the uplink message of the EDT procedure; and receive a PUR configuration message from the base station in response to the uplink message. In some cases, the communication manager 1015 may also communicate with the base station according to a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration provides for grant-free uplink transmission from the UE to the base station; receive a preconfigured uplink resource release message from the base station indicating that the UE is to deconfigure the preconfigured uplink resource configuration; and deconfigure the preconfigured uplink resource configuration at least in part based on the preconfigured uplink resource release message. In some cases, the communication manager 1015 may also determine that a base station supports PUR for grant-free uplink transmissions from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR, where the PUR request message includes an example number of PUR grants requested by the UE; and receive a PUR configuration from the base station in response to the PUR request message. In some cases, the communication manager 1015 may also determine that the base station supports PUR for grant-free uplink transmissions from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR; and in response to receiving from the base station a PUR response message indicating rejection of the PUR request message, and wherein the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein. The communication manager 1015 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1015 or its sub-components may be performed by a general-purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present invention. The communication manager 1015 or its sub-components may be physically located in various locations, including distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some instances, according to various aspects of the present invention, the communication manager 1015 or its sub-components may be separate and distinct components. In some instances, according to various aspects of the present invention, the communication manager 1015 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in the present invention, or combinations thereof. The transmitter 1020 may transmit signals generated by other components of the device 1005. In some instances, the transmitter 1020 may be used in conjunction with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1320 described with reference to FIG. 13. The transmitter 1020 may utilize a single antenna or an antenna array. Figure 11 shows a block diagram 1100 of a device 1105 that supports PUR techniques in wireless communication according to various aspects of the present invention. The device 1105 may be an example of aspects of the device 1005 or the UE 115 described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1145. The device 1105 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses). The receiver 1110 can receive information associated with various information channels, such as packets, user data, or control information (e.g., control channels, data channels, and information related to PUR technology in wireless communication, etc.). The information can be transmitted to other components of the device 1105. The receiver 1110 can be an example of various aspects of the transceiver 1320 described with reference to FIG. 13. The receiver 1110 can utilize a single antenna or an antenna array. The communication manager 1115 can be an example of various aspects of the communication manager 1015 described herein. The communication manager 1115 can include a PUR determination component 1120, a PUR request manager 1125, a PUR configuration manager 1130, a PUR transmission manager 1135, and an EDT random access manager 1140. The communication manager 1115 can be an example of various aspects of the communication manager 1310 described herein. The PUR determination component 1120 can determine whether the base station supports PUR for grant-free uplink transmission from the UE. The PUR request manager 1125 can transmit a PUR request message to the base station based on the determination that the base station supports PUR. The PUR configuration manager 1130 can receive a PUR configuration identifying the PUR allocated to the UE from the base station in response to the PUR request message. The PUR transmission manager 1135 can receive the uplink resources for the response message to be transmitted from the UE and transmit a PUR configuration response message to the base station using the uplink resources of the response message. The EDT random access manager 1140 can determine the EDT configuration of the EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in the uplink message of the EDT procedure. The PUR request manager 1125 can format a PUR request message to be transmitted in the uplink message of the EDT procedure, where the PUR request message indicates the requested configuration, reconfiguration, or release of the PUR configuration; and transmit the PUR request message in the uplink message of the EDT procedure. The PUR configuration manager 1130 can receive a PUR configuration message from the base station in response to the PUR request message. The PUR determination component 1120 can determine whether the base station supports PUR for grant-free uplink transmission from the UE. The PUR request manager 1125 can transmit a PUR request message to the base station based on the determination that the base station supports PUR, where the PUR request message includes the number of instances of the PUR grant requested by the UE. The PUR configuration manager 1130 can receive a PUR configuration from the base station in response to the PUR request message. The PUR determination component 1120 can determine that the base station supports PUR for grant-free uplink transmissions from the UE. The PUR request manager 1125 can transmit a PUR request message to the base station based on determining that the base station supports PUR. The PUR configuration manager 1130 can receive a PUR response message from the base station indicating rejection of the PUR request message in response to the PUR request message, and wherein the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The transmitter 1145 can transmit signals generated by other components of the device 1105. In some instances, the transmitter 1145 can be used in conjunction with the receiver 1110 in a transceiver module. For example, the transmitter 1145 can be an example of aspects of the transceiver 1320 described with reference to FIG. 13. The transmitter 1145 can utilize a single antenna or an antenna array. Figure 12 shows a block diagram 1200 of a communication manager 1205 that supports PUR techniques in wireless communications according to aspects of the present invention. The communication manager 1205 can be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 can include a PUR determination component 1210, a PUR request manager 1215, a PUR configuration manager 1220, a PUR transmission manager 1225, an EDT random access manager 1230, a PUR response manager 1235, a paging manager 1240, an RRC manager 1245, and a PUR grant manager 1250. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses). The PUR determination component 1210 can determine that the base station supports PUR for grant-free uplink transmissions from the UE. The PUR request manager 1215 can transmit a PUR request message to the base station based on determining that the base station supports PUR. In some instances, the PUR request manager 1215 can format the PUR request message to be transmitted in an EDT procedure uplink message, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration. In some instances, the PUR request manager 1215 can transmit the PUR request message in an EDT procedure uplink message. In some instances, the PUR request manager 1215 can transmit a PUR request message to the base station based on determining that the base station supports PUR, wherein the PUR request message includes the number of instances of PUR grants requested by the UE. In some instances, the PUR request manager 1215 can transmit a PUR request message to the base station based on determining that the base station supports PUR. The PUR configuration manager 1220 may receive, in response to a PUR request message, a PUR configuration identifying the PUR allocated to the UE from the base station. In some instances, the PUR configuration manager 1220 may receive a PUR configuration message from the base station in response to a PUR request message. In some instances, the PUR configuration manager 1220 may receive, in response to a PUR request message, a PUR response message from the base station indicating rejection of the PUR request message, and wherein the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. In some instances, the PUR configuration manager 1220 may determine a set of control channel resources for monitoring uplink grants based on the PUR configuration from the base station. In some instances, the PUR configuration manager 1220 may monitor the set of control channel resources for an uplink grant, wherein the uplink grant indicates an uplink resource for transmitting a PUR configuration response message to the base station. In some instances, the PUR configuration manager 1220 may determine to deconfigure the PUR configuration based on receiving broadcast system information transmission from the base station indicating that the PUR is not supported. In some instances, the PUR configuration manager 1220 may release the PUR configuration. In some instances, the PUR configuration manager 1220 may receive an indication from the base station for reconfiguring the PUR configuration. In some instances, the PUR configuration manager 1220 may receive an indication from the base station in a random access response message in response to the transmission of a random access request message of the UE. In some instances, the PUR configuration manager 1220 may receive a PUR release message from the base station. In some instances, the PUR configuration manager 1220 may deconfigure the PUR configuration based on the PUR release message. In some instances, the PUR configuration manager 1220 may determine to release the previous PUR configuration. In some instances, the PUR configuration manager 1220 may transmit an indication of zero instances of PUR grants in the PUR request message. In some instances, the PUR configuration manager 1220 may transmit a PUR reconfiguration failure indication to the base station after receiving the PUR configuration. In some instances, the PUR configuration manager 1220 may release the PUR configuration. In some cases, the PUR configuration is provided as a delta configuration indicating the difference relative to a previous PUR configuration of the UE. In some cases, the PUR configuration is provided as a delta configuration indicating the difference relative to the current configuration being used by the UE. In some cases, the PUR configuration is provided as a delta configuration indicating the difference relative to a default PUR configuration. In some cases, uplink resources for a response message are provided in an explicit indication of a PUR configuration from a base station. In some cases, a PUR configuration message from the base station is received in an EDT downlink message. In some cases, a PUR configuration is provided in an EDT data advance completion message indicating PUR resources for the configuration of the UE. In some cases, the EDT data advance completion message explicitly or implicitly provides one or more of the following: an indication that the UE is to use a previous PUR configuration, a confirmation of a previous PUR configuration, an indication for deconfiguring and releasing a previous PUR configuration, new resources for a new PUR configuration, or any combination thereof. In some cases, the indication for deconfiguring and releasing a previous PUR configuration includes a boolean flag in the EDT data advance completion message. In some cases, a PUR request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be released by the UE. In some cases, a PUR request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be maintained by the UE. The PUR transmission manager 1225 may receive uplink resources for a response message to be transmitted from the UE. In some instances, the PUR transmission manager 1225 may use the uplink resources of the response message to transmit a PUR configuration response message to the base station. In some cases, the uplink resources of the response message are included in a first instance of a PUR allocated to the UE. In some cases, the transmission of the PUR configuration response message is performed when the UE is in an idle mode or in a mode connected to the base station. The EDT random access manager 1230 may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure. In some instances, the EDT random access manager 1230 may receive an indication from the base station that uplink messages of the EDT procedure are available for transmitting a PUR request message. In some cases, the indication from the base station is provided in a system information block broadcast from the base station. In some cases, the PUR request message is transmitted in a transmission of a third message (MSG3) of the EDT procedure. In some cases, the PUR request message is provided in one or more information elements of an RRC message of the EDT procedure. In some cases, the cause for establishment in the RRC message indicates that the random access message includes a PUR request. In some cases, the RRC message includes an uplink payload data indication, and wherein a predetermined value of the uplink payload data indication indicates that the random access message includes a PUR request. In some cases, the RRC message of the EDT procedure includes a first RRC message for a connection associated with the EDT procedure and a second RRC message associated with the PUR request. The PUR response manager 1235 can use the uplink resources of the response message from the UE to transmit an indication of successful PUR configuration or PUR configuration failure in response to the PUR configuration message. The paging manager 1240 can receive a paging message from the base station. In some instances, the paging manager 1240 can transmit a random access request message to the base station in response to the paging message, and wherein receiving an indication for reconfiguring the PUR configuration is in response to the random access request message. In some cases, the indication for reconfiguring the PUR configuration indicates a new PUR configuration to be used by the UE or indicates that the UE is to release the PUR configuration. The RRC manager 1245 can manage RRC signaling between the UE and the base station. In some cases, the UE receives a PUR release message while in the connected mode or in an EDT random access message, and wherein the PUR release message is an RRC PUR reconfiguration message. The PUR grant manager 1250 can receive a PUR grant and identify the number of instances of the PUR grant to be requested for a PUR configuration. In some cases, the number of instances of the PUR grant provides an explicit number of PUR grants or an indication of an indefinite number of PUR grants. In some cases, the absence of the PUR grant request field in the PUR request message or a predetermined value in the PUR grant request field indicates an indefinite number of PUR grants. In some cases, the number of instances of the PUR grant requested by the UE indicates a single-trigger PUR configuration request or a multi-trigger PUR configuration request. Figure 13 shows an illustration of a system 1300 including a device 1305 that supports PUR technology in wireless communication according to aspects of the present invention. The device 1305 can be an instance of the device 1005, the device 1105, or the UE 115 as described herein or include components of the device or UE. The device 1305 can include components for two-way voice and data communication, the components including components for transmitting and receiving communication, including a communication manager 1310, an I / O controller 1315, a transceiver 1320, an antenna 1325, a memory 1330, and a processor 1340. These components can communicate electronically via one or more buses (e.g., bus 1345). The communication manager 1310 can determine that the base station supports PUR for grant-free uplink transmission from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR; receive a PUR configuration identifying the PUR allocated to the UE from the base station in response to the PUR request message; receive the uplink resources for the response message to be transmitted from the UE; and transmit a PUR configuration response message to the base station using the uplink resources of the response message. The communication manager 1310 may also determine the EDT configuration of the EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in the uplink message of the EDT procedure; format the PUR request message to be transmitted in the uplink message of the EDT procedure, where the PUR request message indicates the requested configuration, reconfiguration, or release of the PUR configuration; transmit the PUR request message in the uplink message of the EDT procedure; and receive a PUR configuration message from the base station in response to the PUR request message. The communication manager 1310 may also communicate with the base station according to a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration provides for grant-free uplink transmission from the UE to the base station; receive a preconfigured uplink resource release message from the base station indicating that the UE is to deconfigure the preconfigured uplink resource configuration; and at least partially deconfigure the preconfigured uplink resource configuration based on the preconfigured uplink resource release message. The communication manager 1310 may also determine that the base station supports PUR for grant-free uplink transmission from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR, where the PUR request message includes the number of instances of the PUR grant requested by the UE; and receive a PUR configuration from the base station in response to the PUR request message. The communication manager 1310 may also determine that the base station supports PUR for grant-free uplink transmission from the UE; transmit a PUR request message to the base station based on the determination that the base station supports PUR; and receive a PUR response message from the base station in response to the PUR request message indicating rejection of the PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The I / O controller 1315 may manage the input and output signals of the device 1305. The I / O controller 1315 may also manage peripheral devices not integrated into the device 1305. In some cases, the I / O controller 1315 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1315 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, the I / O controller 1315 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1315 may be implemented as part of a processor. In some cases, the user may interact with the device 1305 via the I / O controller 1315 or via hardware components controlled by the I / O controller 1315. The transceiver 1320 can perform two-way communication via one or more antennas, wired links, or wireless links as described above. For example, the transceiver 1320 can represent a wireless transceiver and can perform two-way communication with another wireless transceiver. The transceiver 1320 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission and to demodulate packets received from the antenna. In some cases, the wireless device can include a single antenna 1325. However, in some cases, the device can have more than one antenna 1325, and the more than one antenna can simultaneously transmit or receive multiple wireless transmissions. The memory 1330 can include RAM and ROM. The memory 1330 can store computer-readable, computer-executable program code 1335 that includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, among other things, the memory 1330 can contain a BIOS that can control basic hardware or software operations such as interactions with peripheral components or devices. The processor 1340 can include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1340 can be configured to operate a memory array using a memory controller. In other cases, the 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 that support PUR technology in wireless communication). The code 1335 can include instructions for implementing aspects of the present invention, including instructions for supporting wireless communication. The code 1335 can be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code 1335 may not be directly executable by the processor 1340, but rather can cause a computer (e.g., when compiled and executed) to perform the functions described herein. Figure 14 shows a block diagram 1400 of a device 1405 that supports PUR technology in wireless communication according to aspects of the present invention. The device 1405 can be an example of aspects of the base station 105 as described herein. The device 1405 can include a receiver 1410, a communication manager 1415, and a transmitter 1420. The device 1405 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses). The receiver 1410 can receive information associated with various information channels, such as packets, user data, or control information (e.g., control channels, data channels, and information related to PUR technology in wireless communication, etc.). The information can be transmitted to other components of the device 1405. The receiver 1410 can be an example of aspects of the transceiver 1720 described with reference to FIG. 17. The receiver 1410 can utilize a single antenna or an antenna array. The communication manager 1415 can transmit an indication from the base station to support PUR for grant-free uplink transmission; transmit to the UE a PUR configuration identifying the PUR allocated to the UE in response to a PUR request message; receive a PUR request message from the UE; and receive a PUR configuration response from the UE via the uplink resource of the response message. The communication manager 1415 can also determine an EDT configuration for an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure; receive a PUR request message from the UE in the uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration; and transmit a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates the uplink resource of the response message from the UE. The communication manager 1415 can also transmit an indication from the base station to support PUR for grant-free uplink transmission; transmit a PUR configuration to the UE in response to a PUR request message; and receive a PUR request message from the UE, where the PUR request message includes an example of the number of PUR grants requested by the UE. The communication manager 1415 can also transmit an indication from the base station to support PUR for grant-free uplink transmission; transmit a PUR response message to the UE in response to a PUR request message, indicating a rejection of the PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message; and receive a PUR request message from the UE. The communication manager 1415 can be an example of aspects of the communication manager 1710 described herein. The communication manager 1415 or its sub-components can be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1415 or its sub-components can be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), 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 invention. The communication manager 1415 or its sub-components may be physically located at various locations, including distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some instances, according to various aspects of the present invention, the communication manager 1415 or its sub-components may be separate and distinct components. In some instances, according to various aspects of the present invention, the communication manager 1415 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in the present invention, or combinations thereof. The transmitter 1420 may transmit signals generated by other components of the device 1405. In some instances, the transmitter 1420 may be used in conjunction with the receiver 1410 in a transceiver module. For example, the transmitter 1420 may be an example of aspects of the transceiver 1720 described with reference to FIG. 17. The transmitter 1420 may utilize a single antenna or an antenna array. Figure 15 shows a block diagram 1500 of a device 1505 that supports PUR technology in wireless communication according to various aspects of the present invention. The device 1505 may be an example of aspects of the device 1405 or the base station 105 described herein. The device 1505 may include a receiver 1510, a communication manager 1515, and a transmitter 1540. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses). The receiver 1510 may receive information associated with various information channels (e.g., control channels, data channels, and information related to PUR technology in wireless communication, such as packets, user data, or control information). The information may be passed to other components of the device 1505. The receiver 1510 may be an example of aspects of the transceiver 1720 described with reference to FIG. 17. The receiver 1510 may utilize a single antenna or an antenna array. The communication manager 1515 may be an example of aspects of the communication manager 1415 described herein. The communication manager 1515 may include a PUR configuration manager 1520, a PUR request manager 1525, a PUR response manager 1530, and an EDT random access manager 1535. The communication manager 1515 may be an example of aspects of the communication manager 1710 described herein. The PUR configuration manager 1520 may transmit an indication that the base station supports PUR for grant-free uplink transmission and transmit a PUR configuration identifying the PUR allocated to the UE to the UE in response to a PUR request message. The PUR request manager 1525 may receive a PUR request message from the UE. The PUR response manager 1530 may receive a PUR configuration response from the UE via uplink resources in a response message. The EDT random access manager 1535 can determine the EDT configuration of the EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in the uplink message of the EDT procedure. The PUR request manager 1525 can receive a PUR request message from the UE in the uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration. The PUR configuration manager 1520 can transmit a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates the uplink resources for the response message from the UE. The PUR configuration manager 1520 can transmit an indication of the base station supporting PUR for grant-free uplink transmission and transmit a PUR configuration to the UE in response to the PUR request message. The PUR request manager 1525 can receive a PUR request message from the UE, where the PUR request message includes the number of instances of PUR grants requested by the UE. The PUR configuration manager 1520 can transmit an indication of the base station supporting PUR for grant-free uplink transmission and transmit a PUR response message indicating rejection of the PUR request message to the UE in response to the PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The PUR request manager 1525 can receive a PUR request message from the UE. The transmitter 1540 can transmit signals generated by other components of the device 1505. In some instances, the transmitter 1540 can be used in conjunction with the receiver 1510 in the transceiver module. For example, the transmitter 1540 can be an example of aspects of the transceiver 1720 described with reference to FIG. 17. The transmitter 1540 can utilize a single antenna or an antenna array. Figure 16 shows a block diagram 1600 of a communication manager 1605 that supports PUR techniques in wireless communication according to aspects of the present invention. The communication manager 1605 can be an example of aspects of the communication manager 1415, communication manager 1515, or communication manager 1710 described herein. The communication manager 1605 can include a PUR configuration manager 1610, a PUR request manager 1615, a PUR response manager 1620, an EDT random access manager 1625, a paging manager 1630, and a PUR grant manager 1635. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses). The PUR configuration manager 1610 may transmit an indication to the base station to support PUR for grant-free uplink transmission. In some instances, the PUR configuration manager 1610 may transmit to the UE a PUR configuration identifying the PUR allocated to the UE in response to a PUR request message. In some instances, the PUR configuration manager 1610 may transmit a PUR configuration message to the UE in response to a PUR request message, where the PUR configuration indicates the uplink resources for the response message from the UE. In some instances, the PUR configuration manager 1610 may transmit an indication to the base station to support PUR for grant-free uplink transmission. In some instances, the PUR configuration manager 1610 may transmit a PUR configuration to the UE in response to a PUR request message. In some instances, the PUR configuration manager 1610 may transmit a PUR response message to the UE in response to a PUR request message, indicating rejection of the PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. In some instances, the PUR configuration manager 1610 may receive an indication of successful PUR configuration or PUR configuration failure using the uplink resources of the response message from the UE in response to a PUR configuration message. In some instances, the PUR configuration manager 1610 may transmit a broadcast system information transmission indicating that PUR is not supported and that the UE is to release the PUR configuration. In some instances, the PUR configuration manager 1610 may transmit a PUR release message to the UE. In some instances, the PUR configuration manager 1610 may de-configure the PUR configuration based on the PUR release message. In some cases, the PUR configuration is provided as a delta configuration indicating the difference relative to the UE's previous PUR configuration, the current configuration being used by the UE, or the default PUR configuration. In some cases, the uplink resources for the response message are provided in an explicit indication of the PUR configuration from the base station. In some cases, the uplink resources for the response message are provided in a set of control channel resources monitored by the UE in a control channel transmission from the base station. In some cases, a PUR configuration failure indication is transmitted when the UE is in the idle mode or in a mode connected to the base station. In some cases, the PUR configuration is provided as a delta configuration indicating the difference relative to the UE's previous PUR configuration, indicating the difference relative to the default PUR configuration, or indicating the difference relative to the configuration being used at the UE. In some cases, the PUR configuration is provided in an EDT data early completion message for the PUR resources indicating the configuration of the UE. In some cases, the EDT data early completion message explicitly or implicitly provides one or more of the following: an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication for deconfiguring and releasing the previous PUR configuration, new resources for a new PUR configuration, or any combination thereof. In some cases, the indication for deconfiguring and releasing the previous PUR configuration includes a boolean flag in the EDT data early completion message. In some cases, the PUR release message is transmitted when the UE is in the connected mode or in an EDT random access response message, and wherein the PUR release message is an RRC PUR reconfiguration message. In some cases, the PUR request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be released by the UE. In some cases, the PUR request message indicates a request for reconfiguration of a previous PUR configuration, and wherein the PUR response message indicates that the PUR configuration is to be maintained by the UE. The PUR request manager 1615 may receive a PUR request message from the UE. In some instances, the PUR request manager 1615 may receive a PUR request message from the UE in an EDT procedure uplink message, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. In some instances, the PUR request manager 1615 may receive a PUR request message from the UE, wherein the PUR request message includes the number of instances of PUR grants requested by the UE. In some instances, the PUR request manager 1615 may receive a PUR request message from the UE. The PUR response manager 1620 may receive a PUR configuration response from the UE via an uplink resource of a response message. The EDT random access manager 1625 may determine an EDT configuration for the EDT procedure, wherein the EDT configuration provides for uplink transmission of UE payload data in an EDT procedure uplink message. In some instances, the EDT random access manager 1625 may transmit an indication that an EDT procedure uplink message is available for a PUR request message. In some cases, the indication is transmitted in a system information block broadcast from the base station. The paging manager 1630 may determine to reconfigure or release the PUR configuration of the UE. In some instances, the paging manager 1630 may transmit a paging message to the UE. In some instances, the paging manager 1630 may receive a random access request message from the UE in response to the paging message. In some instances, the paging manager 1630 may transmit an indication for reconfiguring or releasing the PUR configuration in response to the random access request message. In some cases, the indication for reconfiguring the PUR configuration indicates a new PUR configuration for the UE to use or indicates that the UE is to release the PUR configuration. The PUR grant manager 1635 can identify the PUR grants for the UE PUR configuration. In some cases, the number of instances of the PUR grant provides an explicit number of PUR grants or an indication of an indefinite number of PUR grants. In some cases, a number of zero instances indicates that the PUR configuration is to be released. In some cases, the number of instances of the PUR grant requested by the UE indicates a single-trigger PUR configuration request or a multi-trigger PUR configuration request. Figure 17 shows an illustration of a system 1700 including a device 1705 that supports PUR technology in wireless communication according to various aspects of the present invention. The device 1705 can be an example of the device 1405, the device 1505, or the base station 105 as described herein or include components of the device or the UE. The device 1705 can include components for two-way voice and data communication, the components including components for transmitting and receiving communication, including a communication manager 1710, a network communication manager 1715, a transceiver 1720, an antenna 1725, a memory 1730, a processor 1740, and an inter-station communication manager 1745. These components can communicate electronically via one or more buses (e.g., bus 1750). The communication manager 1710 can transmit an indication that the base station supports PUR for grant-free uplink transmission; transmit to the UE a PUR configuration identifying the PUR allocated to the UE in response to a PUR request message; receive a PUR request message from the UE; and receive a PUR configuration response from the UE via the uplink resources of the response message. The communication manager 1710 can also determine an EDT configuration for an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure; receive a PUR request message from the UE in the uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration; and transmit a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates the uplink resources of the response message from the UE. The communication manager 1710 can also transmit an indication that the base station supports PUR for grant-free uplink transmission; transmit a PUR configuration to the UE in response to a PUR request message; and receive a PUR request message from the UE, where the PUR request message includes the number of instances of the PUR grant requested by the UE. The communication manager 1710 can also transmit an indication that the base station supports PUR for grant-free uplink transmission; transmit a PUR response message to the UE in response to a PUR request message indicating a rejected PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message; and receive a PUR request message from the UE. The network communication manager 1715 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1715 can manage the delivery of data communication of client devices (such as one or more UEs 115). The transceiver 1720 can perform two-way communication via one or more antennas, wired links, or wireless links as described above. For example, the transceiver 1720 can represent a wireless transceiver and can perform two-way communication with another wireless transceiver. The transceiver 1720 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission and to demodulate the packets received from the antenna. In some cases, the wireless device can include a single antenna 1725. However, in some cases, the device can have more than one antenna 1725, and the more than one antenna can simultaneously transmit or receive multiple wireless transmissions. The memory 1730 can include RAM, ROM, or a combination thereof. The memory 1730 can store computer-readable program code 1735, which includes instructions that, when executed by a processor (e.g., processor 1740), cause the device to perform various functions described herein. In some cases, among other things, the memory 1730 can contain BIOS, which can control basic hardware or software operations such as interaction with peripheral components or devices. The processor 1740 can include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1740 can be configured to operate a memory array using a memory controller. In some cases, the memory controller can be integrated into the processor 1740. The processor 1740 can be configured to execute computer-readable instructions stored in a memory (e.g., memory 1730) to cause the device 1705 to perform various functions (e.g., functions or tasks supporting PUR technology in wireless communication). The inter-station communication manager 1745 can manage communication with other base stations 105 and can include a controller or scheduler for cooperating with other base stations 105 to control communication with the UEs 115. For example, the inter-station communication manager 1745 can coordinate the scheduling of transmissions to the UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some instances, the inter-station communication manager 1745 can provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between the base stations 105. Code 1735 may include instructions for implementing aspects of the present invention, including instructions for supporting wireless communication. Code 1735 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, Code 1735 may not be directly executable by the processor 1740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. Figure 18 shows a flowchart of a method 1800 for illustrating PUR technology in supporting wireless communication according to aspects of the present invention. Operations of method 1800 may be implemented by a UE 115 or its components as described herein. For example, operations of method 1800 may be performed by a communication manager as described with reference to FIGS. 10 to 13. In some instances, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 1805, the UE may determine whether the base station supports PUR for grant-free uplink transmissions from the UE. The operation at 1805 may be performed according to the methods described herein. In some instances, aspects of the operation at 1805 may be performed by a PUR determination component as described with reference to FIGS. 10 to 13. At 1810, the UE may transmit a PUR request message to the base station based on the determination that the base station supports PUR. The operation at 1810 may be performed according to the methods described herein. In some instances, aspects of the operation at 1810 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13. At 1815, the UE may receive, in response to the PUR request message, a PUR configuration identifying the PUR allocated to the UE from the base station. The operation at 1815 may be performed according to the methods described herein. In some instances, aspects of the operation at 1815 may be performed by a PUR configuration manager as described with reference to FIGS. 10 to 13. At 1820, the UE may receive an uplink resource for a response message to be transmitted from the UE. The operation at 1820 may be performed according to the methods described herein. In some instances, aspects of the operation at 1820 may be performed by a PUR transmission manager as described with reference to FIGS. 10 to 13. At 1825, the UE may transmit a PUR configuration response message to the base station using the uplink resource for the response message. The operation at 1825 may be performed according to the methods described herein. In some instances, aspects of the operation at 1825 may be performed by a PUR transmission manager as described with reference to FIGS. 10 to 13. Figure FIG. 19 illustrates a flowchart of a method 1900 for supporting PUR technology in wireless communication in accordance with various aspects of the present invention. Operations of method 1900 may be implemented by a UE 115 or components thereof as described herein. For example, operations of method 1900 may be performed by a communication manager as described with reference to FIGS. 10 through 13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 1905, the UE may determine whether the base station supports PUR for grant-free uplink transmissions from the UE. The operation at 1905 may be performed according to the methods described herein. In some instances, aspects of the operation at 1905 may be performed by a PUR determination component as described with reference to FIGS. 10 through 13. At 1910, the UE may transmit a PUR request message to the base station based on determining that the base station supports PUR. The operation at 1910 may be performed according to the methods described herein. In some instances, aspects of the operation at 1910 may be performed by a PUR request manager as described with reference to FIGS. 10 through 13. At 1915, the UE may receive a PUR configuration identifying the PUR assigned to the UE from the base station in response to the PUR request message. The operation at 1915 may be performed according to the methods described herein. In some instances, aspects of the operation at 1915 may be performed by a PUR configuration manager as described with reference to FIGS. 10 through 13. At 1920, the UE may determine a set of control channel resources for monitoring uplink grants based on the PUR configuration from the base station. The operation at 1920 may be performed according to the methods described herein. In some instances, aspects of the operation at 1920 may be performed by a PUR configuration manager as described with reference to FIGS. 10 through 13. At 1925, the UE may monitor the set of control channel resources for an uplink grant, where the uplink grant indicates uplink resources for transmitting a PUR configuration response message to the base station. The operation at 1925 may be performed according to the methods described herein. In some instances, aspects of the operation at 1925 may be performed by a PUR configuration manager as described with reference to FIGS. 10 through 13. At 1930, the UE may receive uplink resources for the response message to be transmitted from the UE. The operation at 1930 may be performed according to the methods described herein. In some instances, aspects of the operation at 1930 may be performed by a PUR transmission manager as described with reference to FIGS. 10 through 13. At 1935, the UE may transmit a PUR configuration response message to the base station using the uplink resources of the response message. The operation of 1935 may be performed according to the methods described herein. In some instances, aspects of the operation of 1935 may be performed by a PUR transmission manager as described with reference to FIGS. 10 to 13. Figure 20 shows a flowchart of a method 2000 for supporting PUR technology in wireless communication according to aspects of the present invention. The operations of method 2000 may be implemented by a UE 115 or its components as described herein. For example, the operations of method 2000 may be performed by a communication manager as described with reference to FIGS. 10 to 13. In some instances, the UE may execute an instruction set for controlling the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2005, the UE may determine an EDT configuration of an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure. The operation of 2005 may be performed according to the methods described herein. In some instances, aspects of the operation of 2005 may be performed by an EDT random access manager as described with reference to FIGS. 10 to 13. Optionally, at 2010, the UE may format a PUR request message to be transmitted in an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2010 may be performed according to the methods described herein. In some instances, aspects of the operation of 2010 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13. At 2015, the UE may transmit an uplink message of the EDT procedure. In some cases, the uplink message may include a PUR request message indicating a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2015 may be performed according to the methods described herein. In some instances, aspects of the operation of 2015 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13. At 2020, the UE may receive a PUR configuration message from the base station in response to the uplink message. The operation of 2020 may be performed according to the methods described herein. In some instances, aspects of the operation of 2020 may be performed by a PUR configuration manager as described with reference to FIGS. 10 to 13. Figure FIG. 21 shows a flowchart of a method 2100 for supporting PUR technology in wireless communication according to various aspects of the present invention. Operations of method 2100 may be implemented by a UE 115 or components thereof as described herein. For example, operations of method 2100 may be performed by a communication manager as described with reference to FIGS. 10-13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2105, the UE may determine an EDT configuration of an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure. The operation of 2105 may be performed according to the methods described herein. In some instances, aspects of the operation of 2105 may be performed by an EDT random access manager as described with reference to FIGS. 10-13. At 2110, the UE may format a PUR request message to be transmitted in an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2110 may be performed according to the methods described herein. In some instances, aspects of the operation of 2110 may be performed by a PUR request manager as described with reference to FIGS. 10-13. At 2115, the UE may transmit the PUR request message in an uplink message of the EDT procedure. The operation of 2115 may be performed according to the methods described herein. In some instances, aspects of the operation of 2115 may be performed by a PUR request manager as described with reference to FIGS. 10-13. At 2120, the UE may receive a PUR configuration message from a base station in response to the PUR request message. The operation of 2120 may be performed according to the methods described herein. In some instances, aspects of the operation of 2120 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13. At 2125, the UE may transmit an indication of successful PUR configuration or PUR configuration failure using uplink resources of a response message from the UE in response to the PUR configuration message. The operation of 2125 may be performed according to the methods described herein. In some instances, aspects of the operation of 2125 may be performed by a PUR response manager as described with reference to FIGS. 10-13. FIG FIG. 22 illustrates a flowchart of a method 2200 for supporting PUR technology in wireless communication in accordance with various aspects of the present invention. Operations of method 2200 may be implemented by UE 115 or its components as described herein. For example, operations of method 2200 may be performed by a communication manager as described with reference to FIGS. 10 through 13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2205, the UE may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure. The operation of 2205 may be performed according to the methods described herein. In some instances, aspects of the operation of 2205 may be performed by an EDT random access manager as described with reference to FIGS. 10 through 13. At 2210, the UE may format a PUR request message to be transmitted in an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2210 may be performed according to the methods described herein. In some instances, aspects of the operation of 2210 may be performed by a PUR request manager as described with reference to FIGS. 10 through 13. At 2215, the UE may transmit the PUR request message in an uplink message of the EDT procedure. The operation of 2215 may be performed according to the methods described herein. In some instances, aspects of the operation of 2215 may be performed by a PUR request manager as described with reference to FIGS. 10 through 13. At 2220, the UE may receive a PUR configuration message from a base station in response to the PUR request message. The operation of 2220 may be performed according to the methods described herein. In some instances, aspects of the operation of 2220 may be performed by a PUR configuration manager as described with reference to FIGS. 10 through 13. FIG 23 illustrates a flowchart of a method 2300 for supporting PUR technology in wireless communication in accordance with various aspects of the present invention. Operations of method 2300 may be implemented by UE 115 or its components as described herein. For example, operations of method 2300 may be performed by a communication manager as described with reference to FIGS. 10 through 13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2305, the UE may determine the EDT configuration of the EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in the uplink message of the EDT procedure. The operation of 2305 may be performed according to the methods described herein. In some examples, aspects of the operation of 2305 may be performed by the EDT random access manager as described with reference to FIGS. 10 to 13. At 2310, the UE may format a PUR request message to be transmitted in the uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration. The operation of 2310 may be performed according to the methods described herein. In some examples, aspects of the operation of 2310 may be performed by the PUR request manager as described with reference to FIGS. 10 to 13. At 2315, the UE may transmit the PUR request message in the uplink message of the EDT procedure. The operation of 2315 may be performed according to the methods described herein. In some examples, aspects of the operation of 2315 may be performed by the PUR request manager as described with reference to FIGS. 10 to 13. At 2320, the UE may receive a PUR configuration message from the base station in response to the PUR request message. The operation of 2320 may be performed according to the methods described herein. In some examples, aspects of the operation of 2320 may be performed by the PUR configuration manager as described with reference to FIGS. 10 to 13. At 2325, the UE may receive a paging message from the base station. The operation of 2325 may be performed according to the methods described herein. In some examples, aspects of the operation of 2325 may be performed by the paging manager as described with reference to FIGS. 10 to 13. At 2330, the UE may transmit a random access request message to the base station in response to the paging message. The operation of 2330 may be performed according to the methods described herein. In some examples, aspects of the operation of 2330 may be performed by the paging manager as described with reference to FIGS. 10 to 13. At 2335, the UE may receive an indication for reconfiguring the PUR configuration from the base station. The operation of 2335 may be performed according to the methods described herein. In some examples, aspects of the operation of 2335 may be performed by the PUR configuration manager as described with reference to FIGS. 10 to 13. Figure FIG. 24 shows a flowchart of a method 2400 for supporting PUR technology in wireless communication in accordance with various aspects of the present invention. The operations of method 2400 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 2400 may be performed by a communication manager as described with reference to FIGS. 10 through 13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2405, the UE may determine whether the base station supports PUR for grant-free uplink transmissions from the UE. The operation of 2405 may be performed according to the methods described herein. In some instances, aspects of the operation of 2405 may be performed by a PUR determination component as described with reference to FIGS. 10 through 13. At 2410, based on determining that the base station supports PUR, the UE may transmit a PUR request message to the base station, where the PUR request message includes the number of instances of PUR grants requested by the UE. The operation of 2410 may be performed according to the methods described herein. In some instances, aspects of the operation of 2410 may be performed by a PUR request manager as described with reference to FIGS. 10 through 13. At 2415, the UE may receive a PUR configuration from the base station. The operation of 2415 may be performed according to the methods described herein. In some instances, aspects of the operation of 2415 may be performed by a PUR configuration manager as described with reference to FIGS. 10 through 13. In some cases, the PUR configuration may be based on the number of instances of PUR grants requested by the UE. FIG 25 shows a flowchart of a method 2500 for supporting PUR technology in wireless communication in accordance with various aspects of the present invention. The operations of method 2500 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 2500 may be performed by a communication manager as described with reference to FIGS. 10 through 13. In some instances, the UE may execute an instruction set for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below. At 2505, the UE may determine whether the base station supports PUR for grant-free uplink transmissions from the UE. The operation of 2505 may be performed according to the methods described herein. In some instances, aspects of the operation of 2505 may be performed by a PUR determination component as described with reference to FIGS. 10 through 13. At 2510, the UE may transmit a PUR request message to the base station based on determining that the base station supports PUR. The operation of 2510 may be performed according to the methods described herein. In some examples, aspects of the operation of 2510 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13. At 2515, the UE may receive, in response to the PUR request message, a PUR response message from the base station indicating rejection of the PUR request message, and wherein the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The operation of 2515 may be performed according to the methods described herein. In some examples, aspects of the operation of 2515 may be performed by a PUR configuration manager as described with reference to FIGS. 10 to 13. Figure 26 shows a flowchart of a method 2600 for supporting PUR techniques in wireless communication in accordance with aspects of the present invention. The operations of method 2600 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of method 2600 may be performed by a communication manager as described with reference to FIGS. 14 to 17. In some examples, the base station may execute an instruction set for controlling functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below. At 2605, the base station may transmit an indication that the base station supports PUR for grant-free uplink transmissions. The operation of 2605 may be performed according to the methods described herein. In some examples, aspects of the operation of 2605 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. At 2610, the base station may receive a PUR request message from the UE. The operation of 2610 may be performed according to the methods described herein. In some examples, aspects of the operation of 2610 may be performed by a PUR request manager as described with reference to FIGS. 14 to 17. At 2615, the base station may transmit, in response to the PUR request message, a PUR configuration identifying the PUR allocated to the UE to the UE. The operation of 2615 may be performed according to the methods described herein. In some examples, aspects of the operation of 2615 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. At 2620, the base station may receive a PUR configuration response from the UE via the uplink resources of the response message. The operation of 2620 may be performed according to the methods described herein. In some examples, aspects of the operation of 2620 may be performed by a PUR response manager as described with reference to FIGS. 14 to 17. At 2625, the base station may transmit uplink resources to the UE in response to a response message from the UE. The operation of 2625 may be performed according to the methods described herein. In some examples, aspects of the operation of 2625 may be performed by an undefined as described with reference to FIGS. 14 through 17. Figure 27 shows a flowchart of a method 2700 for supporting PUR techniques in wireless communication according to aspects of the present invention. The operations of method 2700 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of method 2700 may be performed by a communication manager as described with reference to FIGS. 14 through 17. In some examples, the base station may execute an instruction set for controlling functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below. At 2705, the base station may determine an EDT configuration of an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure. The operation of 2705 may be performed according to the methods described herein. In some examples, aspects of the operation of 2705 may be performed by an EDT random access manager as described with reference to FIGS. 14 through 17. At 2710, the base station may receive a PUR request message from the UE in an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2710 may be performed according to the methods described herein. In some examples, aspects of the operation of 2710 may be performed by a PUR request manager as described with reference to FIGS. 14 through 17. At 2715, the base station may transmit a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates uplink resources for a response message from the UE. The operation of 2715 may be performed according to the methods described herein. In some examples, aspects of the operation of 2715 may be performed by a PUR configuration manager as described with reference to FIGS. 14 through 17. Figure 28 shows a flowchart of a method 2800 for supporting PUR techniques in wireless communication according to aspects of the present invention. The operations of method 2800 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of method 2800 may be performed by a communication manager as described with reference to FIGS. 14 through 17. In some examples, the base station may execute an instruction set for controlling functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below. At 2805, the base station may transmit an indication that the base station supports PUR for grant-free uplink transmission. The operation of 2805 may be performed according to the methods described herein. In some instances, aspects of the operation of 2805 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. At 2810, the base station may receive a PUR request message from the UE, where the PUR request message includes the number of instances of PUR grants requested by the UE. The operation of 2810 may be performed according to the methods described herein. In some instances, aspects of the operation of 2810 may be performed by a PUR request manager as described with reference to FIGS. 14 to 17. At 2815, the base station may transmit a PUR configuration to the UE in response to the PUR request message. The operation of 2815 may be performed according to the methods described herein. In some instances, aspects of the operation of 2815 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. Figure 29 shows a flowchart of a method 2900 for illustrating support for PUR techniques in wireless communication according to aspects of the present invention. The operations of method 2900 may be implemented by the base station 105 or its components as described herein. For example, the operations of method 2900 may be performed by a communication manager as described with reference to FIGS. 14 to 17. In some instances, the base station may execute an instruction set for controlling functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below. At 2905, the base station may transmit an indication that the base station supports PUR for grant-free uplink transmission. The operation of 2905 may be performed according to the methods described herein. In some instances, aspects of the operation of 2905 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. At 2910, the base station may receive a PUR request message from the UE. The operation of 2910 may be performed according to the methods described herein. In some instances, aspects of the operation of 2910 may be performed by a PUR request manager as described with reference to FIGS. 14 to 17. At 2915, the base station may transmit a PUR response message indicating rejection of the PUR request message to the UE in response to the PUR request message, and where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message. The operation of 2915 may be performed according to the methods described herein. In some instances, aspects of the operation of 2915 may be performed by a PUR configuration manager as described with reference to FIGS. 14 to 17. Note that the methods described herein describe possible embodiments, and the operations or steps may be reconfigured or otherwise modified, and other embodiments are possible. Additionally, aspects of two or more of the methods herein may be combined. The techniques described herein can be used in various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 encompasses standards such as IS-2000, IS-95, and IS-856. The IS-2000 release is often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems may implement radio technologies such as Global System for Mobile Communications (GSM), etc. OFDMA systems may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization named the "3rd Generation Partnership Project (3GPP)". CDMA2000 and UMB are described in documents from an organization named the "3rd Generation Partnership Project 2 (3GPP2)". The techniques described herein can be used in the systems and radio technologies mentioned above and other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of illustration, or the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are applicable to applications other than LTE, LTE-A, LTE-A Pro, or NR applications. Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access for UEs subscribed to services with the network provider. Compared with macro cells, small cells may be associated with low-power base stations, and small cells may operate in the same or different frequency bands (e.g., with usage rights, without usage rights, etc.) as macro cells. According to various examples, small cells may include pico cells, femto cells, and micro cells. A pico cell, for example, may cover a small geographical area and may allow unrestricted access for UEs subscribed to services with the network provider. A femto cell may also cover a small geographical area (e.g., a home) and may provide restricted access for UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in the home, etc.). The eNB of a macro cell may be referred to as a macro eNB. The eNB of a small cell may be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communication using one or more component carriers. The wireless communication systems described herein may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation. Any of a variety of different technologies and techniques may be used to represent the information and signals described herein. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof. The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, DSP, ASIC, 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 may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). 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 a computer-readable medium or transmitted by a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present invention and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations. 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. Non-transitory storage media can be any available media that can be accessed by a general purpose computer or a special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a general purpose computer or a special purpose computer or a general purpose processor or a special purpose processor. Also, any connection is properly termed a computer-readable media. For example, if 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 media. As used herein, disk or disc includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks usually magnetically reproduce data, while discs optically reproduce data with lasers. Combinations of the above are also included within the scope of computer-readable media. As used herein (including in the claims), the "or" used in a list of items (e.g., a list of items ending with phrases such as "at least one of..." or "one or more of...") indicates an inclusive list, such that a list of at least one of A, B, or C, for example, 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" should not be construed as referring to a closed set of conditions. For example, an illustrative step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present invention. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on." In the accompanying drawings, like components or features may have the same reference numeral. Additionally, various components of the same type may be distinguished by using a dash after the reference numeral and a second identifier that differentiates among like components. If only the first reference numeral is used in the specification, the description applies to any one of the like components having the same first reference numeral, regardless of the second reference numeral or any subsequent reference numerals. The description set forth herein describes exemplary configurations in conjunction with the accompanying drawings and does not represent all examples that may be implemented within the scope of the claims or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "better than other examples." For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples. The present description is provided to enable a person skilled in the art to make or use the invention. Various modifications to the invention will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the invention. Thus, the invention is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. 100: Wireless communication system 105: Base station 105-a: Base station 105-b: Base station 105-c: Base station 105-d: Base station 105-e: Base station 105-f: Base station 105-g: Base station 105-h: Base station 110: Geographic coverage area 110-a: Coverage area 115: User equipment (UE) 115-a: User equipment (UE) 115-b: User equipment (UE) 115-c: User equipment (UE) 115-d: User equipment (UE) 115-e: User equipment (UE) 115-f: User equipment (UE) 115-g: User equipment (UE) 115-h: User equipment (UE) 125: Communication link 130: Core network 132: Backhaul link 134: Backhaul link 200: Wireless communication system 205: Downlink transmission 210: Uplink transmission 215: Preconfigured uplink resource (PUR) indication 220: Preconfigured uplink resource (PUR) allocation 225: Preconfigured uplink resource (PUR) request 230: Uplink data 300: Processing procedure flow 305: Step 310: Step 315: Step 320: Step 325: Step 330: Step 335: Step 340: Step 345: Step 350: Step 400: Processing procedure flow 405: Step 410: Step 415: Step 420: Step 425: Step 430: Step 435: Step 440: Step 445: Step 450: Step 500: Processing procedure flow 505: Step 510: Step 515: Step 520: Step 525: Step 530: Step 535: Step 540: Step 545: Step 550: Step 600: Processing procedure flow 605: Step 610: Step 615: Step 620: Step 625: Step 630: Step 635: Step 640: Step 700: Processing procedure flow 705: Step 710: Step 715: Step 720: Step 725: Step 730: Step 735: Step 740: Step 745: Step 750: Step 755: Step 760: Step 765: Step 770: Mobile-originated (MO) data early transmission (EDT) procedure 800: Processing procedure flow 805: Step 810: Step 815: Step 820: Step 825: Step 830: Step 835: Step 840: Step 845: Step 850: Step 855: Step 860: Step 865: Step 870: Mobile-originated (MO) data early transmission (EDT) procedure 900: Processing procedure flow 905: Step 910: Step915: Step 920: Step 925: Step 930: Step 935: Step 1000: Block Diagram 1005: Device 1010: Receiver 1015: Communication Manager 1020: Transmitter 1100: Block Diagram 1105: Device 1110: Receiver 1115: Communication Manager 1120: Preconfigured Uplink Resource (PUR) Determination Component 1125: Preconfigured Uplink Resource (PUR) Request Manager 1130: Preconfigured Uplink Resource (PUR) Configuration Manager 1135: Preconfigured Uplink Resource (PUR) Transmission Manager 1140: Early Data Transmission (EDT) Random Access Manager 1145: Transmitter 1200: Block Diagram 1205: Communication Manager 1210: Preconfigured Uplink Resource (PUR) Determination Component 1215: Preconfigured Uplink Resource (PUR) Request Manager 1220: Preconfigured Uplink Resource (PUR) Configuration Manager 1225: Preconfigured Uplink Resource (PUR) Transmission Manager 1230: Early Data Transmission (EDT) Random Access Manager 1235: Preconfigured Uplink Resource (PUR) Response Manager 1240: Paging Manager 1245: Radio Resource Control (RRC) Manager 1250: Preconfigured Uplink Resource (PUR) Grant Manager 1300: System 1305: Device 1310: Communication Manager 1315: Input / Output (I / O) Controller 1320: Transceiver 1325: Antenna 1330: Memory 1335: Code 1340: Processor 1345: Bus 1400: Block Diagram 1405: Device 1410: Receiver 1415: Communication Manager 1420: Transmitter 1500: Block Diagram 1505: Device 1510: Receiver 1515: Communication Manager 1520: Preconfigured Uplink Resource (PUR) Configuration Manager 1525: Preconfigured Uplink Resource (PUR) Request Manager 1530: Preconfigured Uplink Resource (PUR) Response Manager 1535: Early Data Transmission (EDT) Random Access Manager 1540: Transmitter 1600: Block Diagram 1605: Communication Manager 1610: Preconfigured Uplink Resource (PUR) Configuration Manager 1615: Preconfigured Uplink Resource (PUR) Request Manager 1620: Preconfigured Uplink Resource (PUR) Response Manager 1625: Early Data Transmission (EDT) Random Access Manager 1630: Paging Manager 1635: Preconfigured Uplink Resource (PUR) Grant Manager 1700: System 1705: Device 1710: Communication Manager 1715: Network Communication Manager 1720: Transceiver 1725: Antenna 1730: Memory 1735: Code1740: Processor 1745: Inter-station communication manager 1750: Bus 1800: Method 1805: Step 1810: Step 1815: Step 1820: Step 1825: Step 1900: Method 1905: Step 1910: Step 1915: Step 1920: Step 1925: Step 1930: Step 1935: Step 2000: Method 2005: Step 2010: Step 2015: Step 2020: Step 2100: Method 2105: Step 2110: Step 2115: Step 2120: Step 2125: Step 2200: Method 2205: Step 2210: Step 2215: Step 2220: Step 2300: Method 2305: Step 2310: Step 2315: Step 2320: Step 2325: Step 2330: Step 2335: Step 2400: Method 2405: Step 2410: Step 2415: Step 2500: Method 2505: Step 2510: Step 2515: Step 2600: Method 2605: Step 2610: Step 2615: Step 2620: Step 2625: Step 2700: Method 2705: Step 2710: Step 2715: Step 2800: Method 2805: Step 2810: Step 2815: Step 2900: Method 2905: Step 2910: Step 2915: Step FIG. 1 illustrates an example of a system for wireless communication that supports preconfigured uplink resource (PUR) techniques in wireless communication according to various aspects of the present invention. FIG. 2 illustrates an example of a portion of a wireless communication system that supports PUR techniques in wireless communication according to various aspects of the present invention. FIGS. 3 through 9 illustrate examples of processing procedures that support PUR techniques in wireless communication according to various aspects of the present invention. FIGS. 10 and 11 show block diagrams of devices that support PUR techniques in wireless communication according to various aspects of the present invention. FIG. 12 shows a block diagram of a communication manager that supports PUR techniques in wireless communication according to various aspects of the present invention. FIG. 13 shows a diagram of a system that includes a device that supports PUR techniques in wireless communication according to various aspects of the present invention. FIGS. 14 and 15 show block diagrams of devices that support PUR techniques in wireless communication according to various aspects of the present invention. FIG. 16 shows a block diagram of a communication manager that supports PUR techniques in wireless communication according to various aspects of the present invention. FIG. 17 shows a diagram of a system including a device supporting PUR technology in wireless communication according to various aspects of the present invention. FIGS. 18 to 29 show flowcharts illustrating methods of supporting PUR technology in wireless communication according to various aspects of the present invention. 105-a: Base station 110-a: Coverage area 115-a: User equipment (UE) 200: Wireless communication system 205: Downlink transmission 210: Uplink transmission 215: Preconfigured uplink resource (PUR) indication 220: Preconfigured uplink resource (PUR) allocation 225: Preconfigured uplink resource (PUR) request 230: Uplink data

Claims

1. An apparatus for wireless communication at a network access entity, comprising: one or more processors; one or more memories coupled to the one or more processors; and one or more processor-readable instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to: transmit an indication that the network access entity supports preconfigured uplink resources associated with ungranted uplink transmission; receive a preconfigured uplink resource request message, wherein the preconfigured uplink resource request message includes a number of instances of preconfigured uplink resource grants requested by a user equipment (UE); and in response to the preconfigured uplink resource request message, transmit a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration includes a differential configuration indicating at least one difference relative to a configuration of the UE.

2. The apparatus of claim 1, wherein the quantity of the example of preconfigured uplink resource grant provides an indication of either a specific quantity of preconfigured uplink resource grant or an unlimited quantity of preconfigured uplink resource grant.

3. The device as requested in Request 1, wherein the quantity of the example of the pre-configured uplink resource grant requested by the UE indicates a request for a single-trigger pre-configured uplink resource configuration or a request for a multi-trigger pre-configured uplink resource configuration.

4. The device as requested in Request 1, wherein the configuration is a previously pre-configured uplink resource configuration of the UE.

5. The device as requested in item 1, wherein the configuration is a preset pre-configured uplink resource configuration.

6. The apparatus of claim 1, wherein the one or more processor-readable instructions stored in the one or more memories are further executable by the one or more processors to cause the apparatus to: receive a preconfigured uplink resource reconfiguration failure indication based on the transmission of the preconfigured uplink resource configuration.

7. The apparatus of claim 1, wherein the processor-readable instructions stored in the one or more memories are further executable by the one or more processors to cause the apparatus to: transmit a set of control channel resources for an uplink grant associated with the UE, wherein the uplink grant indication is associated with an uplink resource for receiving a pre-configured uplink resource configuration response message.

8. The apparatus of claim 1, wherein the processor-readable instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to receive the preconfigured uplink resource request message are further executable by the one or more processors to cause the apparatus to: receive the preconfigured uplink resource request message in an uplink message of a data advance transmission procedure.

9. The apparatus of claim 8, wherein the preconfigured uplink resource request message is formatted for reception in the uplink message of the data advance procedure, and wherein the uplink resource request message indicates a request for preconfigured uplink resource configuration or the release of a preconfigured uplink resource configuration.

10. The apparatus of claim 8, wherein the processor-readable instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to receive the preconfigured uplink resource request message are further executable by the one or more processors to cause the apparatus to: receive the preconfigured uplink resource request message in a third message (MSG3) transmission of one of the data advance transmission procedures.

11. The apparatus of claim 1, wherein the processor-readable instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to transmit the pre-configured uplink resource configuration are further executable by the one or more processors to cause the apparatus to: transmit the pre-configured uplink resource configuration in a data advance transmission downlink message (MSG4) that provides a radio resource control connection release message or a radio resource control data advance completion message.

12. The apparatus of claim 1, wherein the pre-configured uplink resource configuration explicitly or implicitly provides one or more of the following: an instruction for deconfiguring and releasing a previous or preset pre-configured uplink resource configuration, a new resource associated with a new pre-configured uplink resource configuration to be used as that configuration, or any combination thereof.

13. The device of request item 1, wherein the quantity of example item being zero indicates that the pre-configured uplink resource configuration should be released.

14. An apparatus for wireless communication at a network access entity, comprising: one or more processors; one or more memories coupled to the one or more processors; and one or more processor-readable instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to: transmit an indication that the network access entity supports one of the preconfigured uplink resources associated with ungranted uplink transmission; receive a preconfigured uplink resource request message, wherein the preconfigured uplink resource request message includes an indication that a user equipment (UE) requests a preconfigured uplink resource grant instance or that the UE requests one of an unlimited number of preconfigured uplink resource grant instances; and transmit a preconfigured uplink resource configuration, a preconfigured uplink resource reconfiguration, or a release of one of the preconfigured uplink resource configurations, wherein the preconfigured uplink resource configuration includes a differential configuration indicating at least one difference relative to a previous preconfigured uplink resource configuration of the UE.

15. The apparatus of claim 14, wherein the previously pre-configured uplink resource configuration includes a preset pre-configured uplink resource configuration.

16. A method for wireless communication at a network access entity, comprising: transmitting an indication that the network access entity supports preconfigured uplink resources associated with ungranted uplink transmission; receiving a preconfigured uplink resource request message, wherein the preconfigured uplink resource request message includes a number of instances of preconfigured uplink resource grants requested by a user equipment (UE); and in response to the preconfigured uplink resource request message, transmitting a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration includes a differential configuration indicating at least one difference relative to a configuration of the UE.

17. The method of request item 16, wherein the quantity of the example of the preconfigured uplink resource grant provides an indication of an explicit quantity of the preconfigured uplink resource grant or an indication of an unlimited quantity of the preconfigured uplink resource grant.

18. As in request item 16, where the quantity of the example item being zero indicates that the pre-configured uplink resource configuration should be released.

19. The method of request item 16, wherein the quantity of the example of the pre-configured uplink resource grant requested by the UE indicates a request for a single-trigger pre-configured uplink resource configuration or a request for a multi-trigger pre-configured uplink resource configuration.

20. The method of request item 16, wherein the configuration is a previously pre-configured uplink resource configuration or a preset pre-configured uplink resource configuration of the UE.

Images