Preconfigured uplink resource techniques in wireless communications

Abstract

To provide methods, systems, and devices for wireless communications that support preconfigured uplink resources (PUR) in wireless communications.SOLUTION: In a wireless communication system, a base station 105-a may communicate a PUR display 215 indicating that support for PUR is available, and may allocate a PUR allocation 220 to a user equipment (UE) 115-a based on requests 225 from the UE. The UE 115-a may transmit UL data 230 using the allocated PUR allocation.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] Cross-reference This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 873,836, filed Jul. 12, 2019, and U.S. Patent Application No. 16 / 926,164, filed Jul. 10, 2020, both entitled “Preconfigured Uplink Resource Techniques in Wireless Communications,” each of which is assigned to the assignee of the present application.

[0002] The following generally relates to wireless communications and, more particularly, to preconfigured uplink resource techniques in wireless communications.

Background Art

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

[0004] In some cases, the UE may have only a relatively small amount of data to be transmitted periodically. For example, the UE may be associated with a sensor that is to periodically provide readings to the network node. In some cases, to obtain uplink resources for uplink transmission, the UE may send a request for uplink data resources (e.g., a buffer status report (BSR) indicating that the UE has data to be transmitted may be provided to the base station), may receive an uplink grant in response to the request, and may then transmit uplink data according to the uplink grant. When the UE has only a relatively small amount of data to be transmitted, such procedures consume a significant amount of overhead compared to the amount of data transmitted. Efficient techniques (i.e., techniques that do not require multi-step communication just to obtain an uplink grant each time) for allocating uplink resources to the UE for "grant-free" uplink transmission may enable more efficient network operation through such allocation of uplink resources and reduced overhead associated with such uplink transmission. Summary of the Invention Means for Solving the Problems

[0005] The techniques described relate to improved methods, systems, devices, and apparatuses that support preconfigured uplink resources (PURs) in wireless communication. The various techniques described communicate that support for PURs is available at a base station and allocate PUR resources to a user equipment (UE) based on requests from the UE. The UE may receive an indication that the base station supports PURs, such as via a system information block (SIB), may determine that it should request a PUR, and may send a PUR request message to the base station. A PUR response from the base station may indicate a PUR allocation for the UE that may be used for uplink transmission.

[0006] In some cases, the base station may provide a PUR allocation that is different from the requested PUR configuration provided by the UE upon a PUR request. The UE may determine that the different PUR configuration is not sufficient for the UE and may send 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 uplink resources that can be used by the UE to send a PUR configuration failure indication. In some cases, an early data transmission (EDT) random access procedure may be used by the UE to send a PUR request and may be used by the base station to send the PUR configuration to the UE. In such cases, the PUR request message may be sent together with a random access message as part of the EDT random access procedure. Additionally or alternatively, a PUR request from the UE requesting a PUR configuration or a 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 of the PUR grant as 0. Additionally or alternatively, the base station may determine that the requested PUR configuration or PUR reconfiguration is not available to the UE and may send a PUR rejection indication to the UE. The rejection indication may also indicate, in the case of a PUR reconfiguration request, how the UE is to handle the existing PUR configuration (e.g., whether to release the existing PUR configuration or whether to maintain the existing PUR configuration).

[0007] A method of wireless communication in a UE is described. The method includes determining by a base station to support preconfigured uplink resources for grant-free uplink transmission 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, receiving from the base station a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, 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 for the response message.

[0008] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine by a base station to support preconfigured uplink resources for grant-free uplink transmission 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, receive from the base station a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, 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 for the response message.

[0009] Another apparatus for wireless communication in a UE is described. The apparatus includes means 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 the determination that the base station supports preconfigured uplink resources, receiving from the base station a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, 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 for the response message.

[0010] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code includes instructions executable by a processor 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 the determination that the base station supports preconfigured uplink resources, receive from the base station a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, receive an uplink resource 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 resource for the response message.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference over a previous preconfigured uplink resource configuration of the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference over a current configuration being used by the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration may be provided as a delta configuration indicating a difference over a default preconfigured uplink resource configuration.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, uplink resources for a response message may be provided within an explicit indication having a preconfigured uplink resource configuration from a base station. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, uplink resources for a response message may be included within a first instance of a preconfigured uplink resource allocated to the UE.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein determine a set of control channel resources to be monitored for an uplink grant based on a preconfigured uplink resource (PUR) configuration from a base station, and may further include operations, features, means, or instructions for monitoring a 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. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource (PUR) configuration response message to the base station indicates whether the PUR configuration was successful or 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 connection mode with the base station.

[0014] A method of wireless communication at a UE is described. The method may include determining an early data transmission configuration for an early data transmission procedure for transmitting UE payload data in an uplink message of the early data transmission procedure. Optionally, 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 an uplink message of the early data transmission procedure and receiving, from the base station, in a downlink message of the early data transmission procedure, a message indicating a configuration or reconfiguration or release of a preconfigured uplink resource configuration.

[0015] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine an early data transmission configuration for an early data transmission procedure, transmit an uplink message for the early data transmission procedure, and receive, from a base station, in a downlink message for the early data transmission procedure, a message indicating configuration or reconfiguration or release of a preconfigured uplink resource configuration.

[0016] Another apparatus for wireless communication in a UE is described. The apparatus may include means for determining an early data transmission configuration for an early data transmission procedure, transmitting an uplink message for the early data transmission procedure, and receiving, from a base station, in a downlink message for the early data transmission procedure, a message indicating configuration or reconfiguration or release of a preconfigured uplink resource configuration.

[0017] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code may include instructions executable by a processor to cause the processor to determine an early data transmission configuration for an early data transmission procedure, transmit an uplink message for the early data transmission procedure, and receive, from a base station, in a downlink message for the early data transmission procedure, a message indicating configuration or reconfiguration or release of a preconfigured uplink resource configuration.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein format a preconfigured uplink resource request message to be sent in an uplink message of an early data transmission procedure, where the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration, and may further include operations, features, means, or instructions for sending the preconfigured uplink resource request message in an uplink message of an early data transmission procedure.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein determine a set of control channel resources to be monitored for uplink grant based on a preconfigured uplink resource (PUR) configuration message from a base station, and may further include operations, features, means, or instructions for monitoring the set of control channel resources for uplink grant, where the uplink grant indicates uplink resources for sending a PUR configuration response message to the base station.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink message of the early data transmission procedure is transmitted within the transmission of message 3 (MSG3) of the early data transmission procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the preconfigured uplink resource (PUR) configuration message from the base station is received within the early data transmission (EDT) downlink message 4 that provides an RRC connection release message or an RRC early data completion message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the PUR configuration is provided as a delta configuration indicating the difference over the UE's previous PUR configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the PUR configuration is provided as a delta configuration indicating the difference over the default PUR configuration or indicating the difference over the configuration being used in the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the EDT message 4 explicitly or implicitly provides one or more of an indication that the UE is to use the previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration is to be deconfigured and released, new resources for the new PUR configuration, or any combination thereof.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication of a successful PUR configuration or a PUR configuration failure, using uplink resources for response messages from a UE, in response to a 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, means, or instructions for determining that a PUR configuration is to be deconfigured and releasing the PUR configuration, based on receiving broadcast system information transmission from a base station indicating that PUR may not be supported. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a PUR release message from a base station and deconfiguring a PUR configuration based on the PUR release message.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for formatting a preconfigured uplink resource request message indicating the number of instances of preconfigured uplink resource grants requested by a UE to be transmitted to a base station, where 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.

[0023] A method of wireless communication in a UE is described. The method includes determining, by a base station, to support preconfigured uplink resources for grant-free uplink transmission from the UE, and transmitting, based on the determination that the base station supports preconfigured uplink resources, a preconfigured uplink resource request message to the base station, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE, and may further include receiving a preconfigured uplink resource configuration from the base station.

[0024] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine, by a base station, to support preconfigured uplink resources for grant-free uplink transmission from the UE, and transmit, based on the determination that the base station supports preconfigured uplink resources, a preconfigured uplink resource request message to the base station, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE, and may further include receiving a preconfigured uplink resource configuration from the base station.

[0025] Another apparatus for wireless communication in a UE is described. The apparatus may include means for determining, by a base station, to support preconfigured uplink resources for grant-free uplink transmission from the UE, and transmitting, based on the determination that the base station supports preconfigured uplink resources, a preconfigured uplink resource request message to the base station, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE, and may further include receiving a preconfigured uplink resource configuration from the base station.

[0026] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code causes a base station to determine to support preconfigured uplink resources for grant-free uplink transmission from the UE, and to transmit a preconfigured uplink resource request message to the base station based on the determination 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 to receive a preconfigured uplink resource configuration from the base station, and may include instructions executable by a processor for doing so.

[0027] 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 a UE indicates that a one-shot PUR configuration is requested, or that a multi-shot PUR configuration is requested.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration is provided as a delta configuration that indicates a difference from a UE's previous preconfigured uplink resource configuration. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration is provided as a delta configuration that indicates a difference from a default preconfigured uplink resource configuration or a difference from 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, means, or instructions for transmitting a PUR reconfiguration failure indication to a base station and releasing the PUR configuration after receiving a preconfigured uplink resource (PUR) configuration.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining a set of control channel resources to monitor for an uplink grant based on a message from a base station and for monitoring the set of control channel resources for an 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, means, or instructions for determining that a PUR configuration may be deconfigured based on receiving broadcast system information from the base station indicating that preconfigured uplink resources (PURs) may not be supported and for releasing the PUR configuration.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a pre-configured uplink resource request message may be transmitted to a base station within an uplink message of an early data transmission (EDT) procedure. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for formatting an uplink resource request message to be transmitted within an uplink message of an EDT procedure, where the uplink resource request message indicates a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an uplink resource request message is transmitted during a message 3 (MSG3) transmission of an EDT procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a message from a base station indicating a pre-configured uplink resource of a UE is received within an early data transmission (EDT) downlink message 4 that provides an RRC connection release message or an RRC early data completion message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a message from a base station explicitly or implicitly provides one or more of an indication that the UE is to use a previous pre-configured uplink resource (PUR) configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration is to be deconfigured and released, a new resource for a new PUR configuration, or any combination thereof.

[0032] A method of wireless communication in a UE is described. The method includes receiving, from a base station, a radio resource configuration connection release message or a radio resource configuration early data completion message that provides a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration indicates the 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.

[0033] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions 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 early data completion message that provides a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration indicates the 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.

[0034] Another apparatus for wireless communication in a UE is described. The apparatus includes means for receiving, from a base station, a radio resource configuration connection release message or a radio resource configuration early data completion message that provides a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration indicates the 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.

[0035] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code is to receive from a base station a radio resource configuration connection release message or a radio resource configuration early data completion message that provides a preconfigured uplink resource configuration, where the preconfigured uplink resource configuration indicates the number of instances of a preconfigured uplink resource grant for the UE and to transmit one or more uplink communications to the base station based on the preconfigured uplink resource configuration, and may include instructions executable by a processor.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of instances of a PUR grant 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 transmitting a PUR request message to a base station based on a determination that the base station supports preconfigured uplink resources before reception, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE.

[0037] 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 an 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 during MSG3 transmission of an 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 that indicates a difference from the UE's previous preconfigured uplink resource configuration, a difference from a default preconfigured uplink resource configuration, or a difference from the configuration being used in the UE.

[0038] A method of wireless communication in a UE is described. The method may include the base station determining to support preconfigured uplink resources for grant-free uplink transmission 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, a preconfigured uplink resource response message from the base station indicating that the preconfigured uplink resource request message is rejected, where the preconfigured uplink resource response message indicates how the UE will proceed based on the rejected preconfigured uplink resource request message.

[0039] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine that the 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 the determination that the base station supports preconfigured uplink resources, and receive, in response to the preconfigured uplink resource request message, a preconfigured uplink resource response message from the base station indicating that the preconfigured uplink resource request message is rejected, where the preconfigured uplink resource response message indicates how the UE will proceed based on the rejected preconfigured uplink resource request message.

[0040] Another apparatus for wireless communication in a UE is described. The apparatus may include means 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 the determination that the base station supports preconfigured uplink resources, and receiving, in response to the preconfigured uplink resource request message, a preconfigured uplink resource response message from the base station indicating that the preconfigured uplink resource request message has been rejected, where the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message.

[0041] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. 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 the determination that the base station supports preconfigured uplink resources, and receiving, in response to the preconfigured uplink resource request message, a preconfigured uplink resource response message from the base station indicating that the preconfigured uplink resource request message has been rejected, where the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message.

[0042] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is required, where a 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, a preconfigured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is required, where a PUR response message indicates that the previous PUR configuration is to be maintained by the UE.

[0043] A method of wireless communication at a base station is described. 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, transmitting to the UE a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, transmitting uplink resources to the UE for a response message, and receiving a preconfigured uplink resource configuration response from the UE via the uplink resources for the response message.

[0044] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions 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, in response to the preconfigured uplink resource request message, transmit a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE to the UE, transmit uplink resources to the UE for a response message from the UE, and receive a preconfigured uplink resource configuration response from the UE via the uplink resources for the response message.

[0045] Another apparatus for wireless communication at a base station is described. 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, in response to the preconfigured uplink resource request message, transmitting a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE to the UE, transmitting uplink resources to the UE for a response message from the UE, and receiving a preconfigured uplink resource configuration response from the UE via the uplink resources for the response message.

[0046] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to cause the base station 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, transmit to the UE a preconfigured uplink resource configuration identifying the preconfigured uplink resources allocated to the UE in response to the preconfigured uplink resource request message, transmit uplink resources to the UE for a response message from the UE, and receive a preconfigured uplink resource configuration response from the UE via the uplink resources for the response message.

[0047] 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 from 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 for the response message may be provided in an explicit indication having 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 for the response message may be provided in a control channel transmission from the base station among a set of control channel resources to be monitored by the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource configuration failure indication may be transmitted when the UE is in an idle mode or in a connected mode with the base station.

[0048] A method of wireless communication at a base station is described. The method comprises determining an early data transmission configuration for an early data transmission procedure available for transmitting a preconfigured uplink resource request message, where the early data transmission configuration provides for uplink transmission of UE payload data in an uplink message of the early data transmission procedure; receiving, in an uplink message of the early data transmission procedure, a preconfigured uplink resource request message from the UE, where the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration; and transmitting a preconfigured uplink resource configuration message to the UE in response to the preconfigured uplink resource request message, where the preconfigured uplink resource configuration indicates an uplink resource for a response message from the UE.

[0049] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine an early data transmission configuration for an early data transmission procedure available for transmitting a preconfigured uplink resource request message, where the early data transmission configuration provides for uplink transmission of UE payload data in an uplink message of the early data transmission procedure; receive, in an uplink message of the early data transmission procedure, a preconfigured uplink resource request message from the UE, where the preconfigured uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration; and transmit a preconfigured uplink resource configuration message to the UE in response to the preconfigured uplink resource request message, where the preconfigured uplink resource configuration indicates an uplink resource for a response message from the UE.

[0050] Another apparatus for wireless communication in a base station is described. The apparatus is for determining an early data transmission configuration for an early data transmission procedure available for transmitting a pre-configured uplink resource request message, where the early data transmission configuration provides for uplink transmission of UE payload data in an uplink message of the early data transmission procedure, and receiving a pre-configured uplink resource request message from the UE in an uplink message of the early data transmission procedure, where the pre-configured uplink resource request message indicates a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration, and transmitting a pre-configured uplink resource configuration message to the UE in response to the pre-configured uplink resource request message, where the pre-configured uplink resource configuration indicates an uplink resource for a response message from the UE, and may include means for performing the foregoing.

[0051] A non-transitory computer-readable medium storing code for wireless communication in a base station is described. The code is for determining an early data transmission configuration for an early data transmission procedure available for transmitting a pre-configured uplink resource request message, where the early data transmission configuration provides for uplink transmission of UE payload data in an uplink message of the early data transmission procedure, and receiving a pre-configured uplink resource request message from the UE in an uplink message of the early data transmission procedure, where the pre-configured uplink resource request message indicates a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration, and transmitting a pre-configured uplink resource configuration message to the UE in response to the pre-configured uplink resource request message, where the pre-configured uplink resource configuration indicates an uplink resource for a response message from the UE, and may include instructions executable by a processor for performing the foregoing.

[0052] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication that uplink messages of an early data transmission procedure are available for a preconfigured 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 a base station.

[0053] 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 that indicates a difference over a previous PUR configuration of the UE, a difference over a default PUR configuration, or a difference over a configuration being used in the UE. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an indication of a successful PUR configuration or a PUR configuration failure, using uplink resources for a response message from a UE, in response to a preconfigured uplink resource (PUR) configuration message.

[0054] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a preconfigured uplink resource (PUR) configuration may be provided in an early data transmission (EDT) early data completion message indicating the configured PUR resources of the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the EDT early data completion message explicitly or implicitly provides one or more of an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration should be deconfigured and released, new resources for 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 that the previous PUR configuration should be deconfigured and released includes a boolean flag in the EDT early data completion message.

[0055] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, 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, means, or instructions for determining that the PUR configuration of the UE is to be reconfigured or released, 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 that the PUR configuration should be reconfigured or released in response to the random access request message.

[0056] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication to reconfigure a PUR configuration indicates a new PUR configuration to be used by a UE or 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, means, or instructions for sending a preconfigured uplink resource (PUR) release message to a UE and deconfiguring a 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 sent while the UE is in a connected mode or within an EDT random access response message, where the PUR release message is a radio resource control (RRC) PUR reconfiguration message.

[0057] A method of wireless communication at a base station is described. 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, where the preconfigured uplink resource request message includes the number of instances 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.

[0058] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions 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, where the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE, and transmit a preconfigured uplink resource configuration to the UE in response to the preconfigured uplink resource request message.

[0059] Another apparatus for wireless communication at a base station is described. 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, where the preconfigured uplink resource request message includes the number of instances 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.

[0060] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to cause the base station 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 transmit a preconfigured uplink resource configuration to the UE in response to the preconfigured uplink resource request message.

[0061] In some examples of the methods, apparatuses, 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, apparatuses, and non-transitory computer-readable media described herein, a number of instances that is zero indicates that the preconfigured uplink resource configuration is to be released. 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 a UE indicates that a one-shot PUR configuration is requested or that a multi-shot PUR configuration is requested.

[0062] A method of wireless communication at a base station is described. 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 transmitting, in response to the preconfigured uplink resource request message, a preconfigured uplink resource response message to the UE indicating that the preconfigured uplink resource request message is rejected, where the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message.

[0063] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions 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 has been rejected, where the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message.

[0064] Another apparatus for wireless communication at a base station is described. 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 has been rejected, where the preconfigured uplink resource response message indicates how the UE is to proceed based on the rejected preconfigured uplink resource request message.

[0065] A non - transitory computer - readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor 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, and in response to the pre - configured uplink resource request message, transmit to the UE a pre - configured uplink resource response message indicating that the pre - configured uplink resource request message is rejected, where the pre - configured uplink resource response message indicates how the UE is to proceed based on the rejected pre - configured uplink resource request message.

[0066] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, a pre - configured uplink resource (PUR) request message indicates that a re - configuration of a previous PUR configuration is requested, where 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, a pre - configured uplink resource (PUR) request message indicates that a re - configuration of a previous PUR configuration is requested, where the PUR response message indicates that the previous PUR configuration is to be maintained by the UE.

Brief Description of the Drawings

[0067]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

DETAILED DESCRIPTION OF THE INVENTION

[0068] Various aspects of the present disclosure provide improved methods, systems, devices, and apparatuses that support signaling and configuration related to preconfigured uplink resources (PURs). The various techniques described communicate that PUR resources are available at a base station, such as via transmission of a system information block (SIB) indicating support for 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). The UE may, in some cases, transmit a PUR request message requesting PUR resources. The base station may receive the PUR request message and may determine whether to allocate PUR resources to the UE. The base station may transmit a PUR response with a PUR allocation to the UE if the base station determines that it should allocate PUR resources to the UE, or may transmit a PUR rejection message to the UE if the base station determines that PUR resources are not available for allocation to the UE.

[0069] In some cases, the base station may provide a PUR allocation different from the requested PUR configuration from the UE. Note that various examples of the present disclosure describe techniques by which a PUR configuration is requested or configured. Such techniques may also be used when a reconfiguration of an existing PUR configuration is requested or configured, and both the PUR configuration and the PUR reconfiguration may be simply referred to as "PUR configuration" herein. When the base station provides a PUR allocation different from the requested PUR configuration, the UE may determine that the different PUR configuration is not sufficient for the UE and may transmit a PUR configuration failure. The PUR configuration failure may indicate that the UE releases the PUR configuration, and the base station may reallocate the configured PUR for other purposes. In some cases, the transmission from the base station to the UE indicating the PUR configuration may provide an indication of uplink resources 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 uplink resources may be an explicit indication of uplink grant provided together with the PUR configuration. Additionally or alternatively, the UE may monitor one or more downlink control channels (e.g., a physical downlink control channel (PDCCH)) transmissions in several windows to obtain an uplink grant for the PUR failure or PUR configuration completion indication. In some cases, the UE may transmit a PUR failure or PUR configuration completion message while in a connected mode (e.g., a radio resource control (RRC) connected mode) or while in an idle (e.g., RRC idle) mode. When the UE is in the idle mode, the PUR failure or PUR configuration completion message may be transmitted upon the first occurrence of the configured PUR.

[0070] In some cases, the UE may determine that the random access procedure for establishing a connection with the base station is configured to enable 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 enable the transmission of a relatively small amount of data. In some cases, the EDT random access procedure may be used to transmit a PUR request from the UE and may be used by the base station to transmit a PUR configuration to the UE. In such cases, various aspects of the EDT random access procedure may include transmissions that provide PUR requests and configuration information to be communicated between the base station and the UE.

[0071] In some cases, a PUR request from the UE requesting a PUR configuration or reconfiguration may provide an indication of the number of instances of the requested PUR permission. In such cases, the UE may indicate the value of the number of such PUR permissions requested, may indicate that an indefinite number of PUR permissions are requested (i.e., that such permissions will continue indefinitely), or may indicate that zero PUR permissions are requested and that the PUR configuration will 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 send the UE a PUR rejection indication that may also indicate how the UE will handle the existing PUR configuration. In some cases, the base station may indicate that the UE will release the existing PUR configuration. In other cases, the base station may indicate that the UE will maintain the existing PUR configuration. In some cases, the indication from the base station may be an explicit indication provided together with the PUR rejection indication.

[0072] Such techniques may enable single message data transmission from a UE. Such single message transmission may employ a four-step uplink random access procedure that enables data transmission within a fifth message (MSG5), or may have reduced overhead for uplink transmission of relatively small amounts of data compared to other techniques such as an EDT random access technique that performs data transmission within a third message (MSG3). In cases where a legacy random access procedure or EDT procedure is used, such techniques still rely on permission from the base station before a UE in idle mode can transmit uplink data. Single message uplink transmission from a UE in idle mode with the latest timing advance (TA) as described herein, having even further reduced overhead compared to random access or EDT techniques, may be supported. Such reduced overhead may extend transmission efficiency and reduce power consumption. In some cases, a UE that remains stationary (i.e., has the latest TA) and has only a relatively small amount of data to transmit at some intervals (e.g., an extended machine type communication (eMTC) UE, or a narrowband Internet of Things (NB-IoT) UE) may benefit from the reduced signaling overhead of the techniques described herein.

[0073] Aspects of the present disclosure are first described in the context of a wireless communication system. Next, several exemplary process flows are described for signaling between a UE and a base station for configuring and using PUR resources. Aspects of the present disclosure are further illustrated by, and described with reference to, apparatus diagrams, system diagrams, and flowcharts relating to PUR techniques in wireless communications.

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

[0075] 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 a transceiver base station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B or giga Node B (any of which may be referred to as a gNB), a home Node B, a home eNB, or some other suitable term, or may be referred to as such by those skilled in the art. The wireless communication system 100 may include different types of base stations 105 (e.g., macro base stations or small cell base stations). The UE 115 described herein may be able to communicate with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like.

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

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

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

[0079] UEs 115 may be distributed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. UEs 115 may be referred to by terms such as mobile devices, wireless devices, remote devices, handheld devices, or subscriber devices, where the "device" may also be referred to as a unit, station, terminal, or client. UEs 115 may also be personal electronic devices such as cellular phones, personal digital assistants (PDAs), tablet computers, laptop computers, or personal computers. In some examples, UEs 115 may also refer to wireless local loop (WLL) stations, Internet of Things (IoT) devices, any Internet of Everything (IoE) devices, or MTC devices, etc., which may be implemented in various articles such as appliances, vehicles, meters, etc.

[0080] Some UEs 115, such as MTC devices or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that enable devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from a device that incorporates sensors or meters to measure or acquire information and relay that information to a central server or application program that can utilize the information, or present the information to a human who can interact with the program or application. Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

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

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

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

[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC), which may 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 may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for the UE 115 served by the base station 105 associated with the EPC. User IP packets may be transferred through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation as well as other functions. The P-GW may be connected to a network operator IP service. The operator IP service may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched (PS) streaming service.

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

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

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

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

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

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

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

[0092] In some cases, the wireless communication system 100 may be a packet-based network operating according to a hierarchical protocol stack. In the user plane, communication in the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The media access control (MAC) layer may perform priority handling and multiplexing of logical channels onto transport channels. The MAC layer may also use hybrid automatic repeat request (HARQ) to perform retransmissions in the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may establish, configure, and maintain an RRC connection between the UE 115 and the base station 105 or the core network 130 that supports radio bearers for user plane data. In the physical layer, transport channels may be mapped to physical channels.

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

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

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

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

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

[0098] 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, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, 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 common search space and one or more UE-specific control regions or UE-specific search spaces).

[0099] A carrier may be associated with a particular bandwidth of the radio frequency spectrum. In some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) for a carrier of a particular radio access technology. In some examples, each served UE 115 may be configured to operate over a portion or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using a narrowband protocol type associated with a 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).

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

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

[0102] In some cases, the UE 115 and the base station 105 may use PUR to help reduce the signaling overhead associated with uplink transmission. In some cases, the base station 105 may transmit an indication of PUR support (e.g., via an SIB). The UE 115 may receive the indication and may send a PUR request to the base station 105. The PUR response from the base station 105 may indicate a PUR allocation for the UE 115 that can be used for uplink transmission. In some cases, the base station 105 may provide a PUR allocation that is different from the requested PUR configuration provided by the UE 115 in the PUR request. The UE 115 may determine that the different PUR configuration is not sufficient for the UE 115 and may send 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 indication of the uplink resources that can be used by the UE 115 to send a PUR configuration failure indication.

[0103] In some cases, the EDT random access procedure may be used for the UE 115 to send a PUR request and may be used by the base station 105 to send a PUR configuration to the UE 115. Additionally or alternatively, a PUR request from the UE 115 requesting a PUR configuration or a 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 send a PUR rejection indication to the UE 115 indicating how the UE 115 should handle the existing PUR configuration (e.g., whether to release the existing PUR configuration or maintain the existing PUR configuration).

[0104] Figure 2 shows an example of a wireless communication system 200 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. In some examples, 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 a coverage area 110-a via a downlink transmission 205 and an uplink transmission 210.

[0105] In some cases, the base station 105-a may configure a set of resources as PUR that may be used for uplink transmissions of the UE 115-a and other UEs that may be served by the base station 105-a. In some cases, the UE 115-a and the base station 105-a may operate using MTC or NB-IoT communication, and the UE 115-a may have periodic transmissions of relatively small amounts of data, such as sensor readings or data related to 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 thus may have an up-to-date timing advance (TA) to synchronize the uplink transmission to the base station 105-a even when the UE 115-a exits the idle mode to send an uplink transmission.

[0106] In some cases, base station 105-a may provide a PUR indication 215 indicating support for PUR at 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 together with the synchronization signal block (SSB), the remaining minimum system information (RMSI), etc.). UE115-a may receive the PUR indication 215 and may determine that the data transmission needs at UE115-a will benefit from pre-configured uplink transmissions. For example, if UE115-a has periodic uplink transmissions that are smaller than the transmission size threshold, UE115-a may determine that it should request a PUR configuration from base station 105-a. Additionally or alternatively, if UE115-a has traffic with a relatively high priority (e.g., data traffic for critical systems or safety-related information), UE115-a may determine that it should request a PUR configuration from base station 105-a. In some cases, the PUR indication 215 may provide an indication of the data size for the relevant uplink transmissions that UE115-a can use to determine whether to request a PUR configuration.

[0107] UE 115-a may determine that a PUR configuration should be requested and may send a PUR request 225 to the base station 105-a. UE 115-a may, in some cases, be in a connected mode (e.g., RRC connected mode) when sending the PUR request 225 and may use a dynamic uplink grant (e.g., an uplink resource allocated by the base station 105-a and indicated to UE 115-a in downlink control information (DCI)) or send a message within a preconfigured grant (e.g., a semi-persistent scheduling (SPS) grant previously provided to UE 115-a). In some cases, UE 115-a may be in an idle mode (e.g., RRC idle mode) and, if the base station 105-a supports EDT, may use EDT to send the PUR request 225. Further, in some cases, UE 115-a may have an existing PUR allocation and may use a previously configured PUR grant to send a PUR request 225 that requests reconfiguration of the existing PUR allocation.

[0108] The base station 105-a may receive the PUR request 225, may determine a PUR configuration or a PUR reconfiguration for the UE 115-a, and the PUR configuration or the PUR reconfiguration may be transmitted to the UE 115-a within the PUR allocation 220. In some cases, the base station 105-a may determine that sufficient PUR resources are not available for the request from the UE 115-a (e.g., due to other UEs having higher priority data using the PUR), and may transmit a PUR rejection message that may indicate whether the existing PUR configuration should be maintained or released if an existing PUR configuration exists. When the UE 115-a receives a PUR rejection message indicating that the existing PUR configuration should be released, or if no existing PUR configuration exists, it may fallback to a legacy uplink technique (e.g., a legacy random access procedure, or an EDT random access procedure). In some cases, the UE 115-a may optionally acknowledge the receipt of the PUR allocation 220 (or rejection). When the UE 115-a is configured or reconfigured using the PUR allocation, the UE 115-a may then transmit the uplink data 230 using the resources indicated in the PUR configuration. In that way, the UE 115-a may be in the idle mode (e.g., RRC idle mode) and transmit the uplink data in a single uplink transmission (similar to a random access MSG1 transmission) without receiving a separate uplink grant using the PUR allocation. In some cases, the UE 115-a may determine that a PUR configuration should be requested, for example, based on the uplink data traffic pattern (e.g., packet size, arrival rate, etc.), QoS requirements, or a combination thereof.

[0109] Figure 3 shows an example of a process flow 300 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. In some examples, the process flow 300 may implement aspects of the wireless communication system 100 or 200. In this example, the process flow 300 may include the UE 115-b and the base station 105-b, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2.

[0110] 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 technique established in an LTE or NR system).

[0111] 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 uplink transmissions using PUR, traffic or service priorities related to PUR grants. In some cases, the SIB may provide an index to a pre-configured mapping of PUR configurations. In some cases, the base station 105-b may configure several different sets of PUR, and the SIB may be formatted to indicate multiple sets of PUR. At 315, the base station 105-b may transmit an SIB having an indication of PUR support, which the UE 115-b may receive.

[0112] In this example, UE115-b may be in a connected mode, and at 320, base station 105-b may provide an uplink grant to UE115-b. The uplink grant may be provided, for example, based on a buffer status report (BSR) provided by UE115-b. At 325, UE115-b may format a PUR request message. The PUR request message may, for example, request a new PUR configuration. In some cases, UE115-b may have an existing PUR configuration, and the PUR request may be for reconfiguration of the existing PUR configuration (e.g., based on updated data traffic at UE115-b, a change in the presence of higher priority data at UE115-b, etc.).

[0113] At 330, UE115-b may transmit the PUR request message. In some cases, the PUR request message may be transmitted using the uplink resources provided in the uplink grant. In other cases, as described in more detail below, UE115-b may use other uplink resources (e.g., SPS resources, EDT random access procedure transmissions, other existing PUR resources, etc.) to transmit the PUR request message.

[0114] At 335, base station 105-b may receive the PUR request message and may determine a PUR configuration for UE115-b. In some cases, base station 105-b may determine the PUR configuration based on one or more of the QOS information provided in the PUR request, the type of PUR requested (e.g., whether an acknowledged mode (AM) PUR is requested or an unacknowledged mode (UM) PUR is requested), other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof.

[0115] At 340, the base station 105-b may send a PUR confirmation message indicating the PUR configuration for UE115-b to UE115-b. In some cases, the PUR configuration may provide a new allocation of PUR for UE115-b. In other cases, the PUR configuration may be a reconfigured allocation of an existing PUR configuration of UE115-b. In some cases, the PUR configuration may be shared by multiple different UEs, the PUR configuration may indicate the shared resources, and information (e.g., a preamble to be provided with the 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 UE115-b to enable the base station 105-b to distinguish transmissions from UE115-b may be provided.

[0116] At 345, UE115-b may identify the PUR configuration provided by the base station 105-b. If the PUR configuration is a new configuration, UE115-b may configure the uplink transmission to be sent using the allocated PUR resources. If the PUR configuration is a reconfiguration of an existing PUR configuration, UE115-b may reconfigure the PUR configuration according to the new PUR configuration. At 350, UE115-b may optionally send a PUR configuration (or reconfiguration) completion message to the base station 105-b. In some cases, as will be described in more detail below, UE115-b may determine that the received PUR configuration is not suitable for the UE (e.g., due to the number of PUR grants being less than the number required for a particular priority transmission, etc.). In such a case, instead of sending a configuration completion indication, UE115-b may send a PUR failure indication that may enable both UE115-b and the base station 105-b to release the configured resources of the PUR configuration. In some cases, the uplink resources for such an indication to the base station 105-a may be indicated in the PUR confirmation message (e.g., in an explicit uplink grant, a window during which UE115-b is to monitor for a PDCCH transmission with an uplink grant, the first instance of a PUR grant, etc.).

[0117] Figure 4 shows another example of a process flow 400 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. In some examples, the process flow 400 may implement aspects of the wireless communication system 100 or 200. In this example, the process flow 400 may include the UE 115-c and the base station 105-c, which are examples of corresponding devices described with reference to FIGS. 1 and 2.

[0118] 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 (e.g., in the RRC_IDLE mode) due to the absence of uplink data or downlink data to be transmitted.

[0119] At 410, the base station 105-c may identify PUR resources and may format a system information block (SIB) indicating PUR support. In some cases, as described 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 PUR resources, traffic or service priorities related to the PUR configuration. In some cases, the SIB may provide an index to a preconfigured mapping of 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 multiple PUR configurations. At 415, the base station 105-c may transmit a SIB having an indication of PUR support, which the UE 115-c may receive.

[0120] In this example, the UE 115-c may be in the idle mode. At 420, the UE 115-c may receive the SIB and may identify that the base station 105-c supports PUR. In some cases, the UE 115-c may periodically monitor for the SIB and other downlink control transmissions while in the idle mode and may receive the SIB during such monitoring.

[0121] At 425, UE 115-c may identify uplink data for PUR and may format a PUR request message. The PUR request message may, for example, request a new PUR configuration. In some cases, UE 115-c may have an existing PUR configuration and the PUR request may be for reconfiguration of the existing PUR configuration (e.g., based on updated data traffic at UE 115-c, a change in the presence of higher priority data at UE 115-c, etc.).

[0122] At 430, UE 115-c may send the PUR request message. In some cases, the PUR request message may be sent, for example, using SPS resources previously allocated to UE 115-c. In other cases, UE 115-c may perform a random access procedure and send the PUR request upon completion of the random access procedure (e.g., within MSG5 transmission). In still other cases, UE 115-c may have an existing PUR allocation and may send the PUR request using the existing PUR allocation. Further, in some cases, as described in more detail with respect to FIG. 7, the PUR request message may be sent within an EDT random access message.

[0123] At 435, base station 105-c may receive the PUR request message and may determine a 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 QOS information provided in the PUR request, whether AM PUR is requested or UM PUR is requested, other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof.

[0124] At 440, the base station 105-c may send a PUR confirmation message indicating the PUR configuration for UE115-c to UE115-c. In some cases, the PUR configuration may be a new configuration for UE115-c. In other cases, the PUR configuration may be a reconfigured configuration of an existing PUR of UE115-c. In some cases, the PUR configuration may be shared by multiple different UEs, the PUR configuration may indicate shared resources, and information (e.g., a preamble to be provided with an 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 UE115-c to enable the base station 105-c to distinguish transmissions from UE115-c may be provided.

[0125] At 445, UE115-c may identify the PUR configuration provided by the base station 105-c. If the PUR configuration is a new configuration, UE115-c may configure uplink transmissions to be sent using the PUR configuration. If the PUR configuration is a reconfiguration of an existing PUR configuration, UE115-c may reconfigure the PUR configuration according to the new PUR configuration. At 450, UE115-c may optionally send a PUR configuration (or reconfiguration) completion message (or a PUR configuration failure message) to the base station 105-c.

[0126] FIG. 5 shows an example of a process flow 500 that supports PUR techniques in wireless communication according to an aspect of the present disclosure. In some examples, the process flow 500 may implement aspects of the wireless communication system 100 or 200. In this example, the process flow 500 may include UE115-d and base station 105-d, which may be examples of corresponding devices described with reference to FIGS. 1 and 2.

[0127] At 505, UE 115-d may be in the idle mode. In some cases, UE 115-d may have previously performed connection establishment and may be idle due to there being no uplink or downlink data to be transmitted. At 510, base station 105-d may identify EDT support and PUR resources and may format a system information block (SIB) indicating PUR support and EDT support. In some cases, the base station may use separate SIBs to indicate PUR support and EDT support. In some cases, as described 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, traffic or service priorities related to the PUR configuration. In some cases, the SIB may provide an index to a pre-configured mapping of the PUR configuration. In some cases, base station 105-d may configure several different PUR configurations and the SIB may be formatted to indicate multiple PUR configurations. At 515, base station 105-d may transmit a SIB having an indication of PUR support, which UE 115-d may receive.

[0128] In this example, UE 115-d may be in the idle mode. At 520, UE 115-d may receive the SIB and may identify that base station 105-d supports EDT and PUR. In some cases, UE 115-d may periodically monitor for the SIB and other downlink control transmissions while in the idle mode and may receive the SIB during such monitoring.

[0129] At 525, UE115-d may identify uplink data for PUR and format a PUR request message to be sent within the EDT. The PUR request message may, for example, request a new PUR configuration. In some cases, UE115-d may have an existing PUR configuration and the PUR request may be for reconfiguration of the existing PUR configuration (e.g., based on updated data traffic at UE115-d, a change in the presence of higher priority data at UE115-d, etc.).

[0130] At 530, UE115-d may send a PUR request message (e.g., after the EDT). In some cases, UE115-d may send a random access request and provide the PUR request within the EDT related to the random access procedure according to an established technique for sending the EDT, as described in more detail with respect to FIG. 7.

[0131] At 535, base station 105-d may receive the PUR request message and determine a PUR configuration for UE115-d. In some cases, base station 105-d may determine the PUR configuration based on one or more of the QOS information provided in the PUR request, whether AM PUR is requested or UM PUR is requested, other PUR configurations for other UEs, the amount of available PUR resources, or any combination thereof.

[0132] At 540, the base station 105-d may send a PUR confirmation message indicating a PUR configuration for the UE 115-d to the UE 115-d. In some cases, the PUR configuration may be a new configuration for the UE 115-d. In other cases, the PUR configuration may be a reconfigured existing PUR configuration for the UE 115-d. In some cases, the PUR configuration may be shared by a plurality of different UEs, the PUR configuration may indicate shared resources, and information (e.g., a preamble to be provided with an 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-d to enable the base station 105-d to identify transmissions from the UE 115-d may be provided.

[0133] At 545, the UE 115-d may identify the PUR configuration provided by the base station 105-d. If the PUR configuration is a new configuration, the UE 115-d may configure the uplink transmission to be transmitted using the PUR configuration. If the PUR configuration is a reconfiguration of an existing PUR configuration, the UE 115-d may reconfigure the PUR configuration according to the new PUR configuration. At 550, the UE 115-d may optionally send a PUR configuration (or reconfiguration) completion message (or configuration failure message) to the base station 105-d.

[0134] As shown 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 use by the UE (e.g., having fewer PUR permissions available for uplink transmissions from the UE). In such a case, the UE may determine whether the different PUR configuration is sufficient to meet the UE's needs. If the different PUR configuration is not appropriate for properly servicing the data associated with the requested PUR configuration, the UE may send a PUR configuration failure message to the base station in response to receiving the different PUR configuration. FIG. 6 shows an example of a process flow in which the UE may provide such a PUR configuration failure message.

[0135] Figure 6 shows an example of a process flow 600 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. In some examples, the process flow 600 may implement aspects of the wireless communication system 100 or 200. In this example, the process flow 600 may include the UE115-e and the base station 105-e, which are examples of corresponding devices described with reference to FIGS. 1 and 2.

[0136] At 605, the base station 105-e and the UE115-e may each determine that the PUR condition is satisfied. Such a determination may be made as described in various examples herein, based on, for example, the base station 105-e establishing a PUR configuration and providing its indication to the UE (e.g., in the SIB), and the UE115-e may receive such an indication and determine that a PUR configuration should be requested.

[0137] At 610, the UE may identify uplink resources for transmitting a PUR request message. In some cases, uplink resources may be provided among the uplink grants related to the connected-mode UE115-e. In other cases, the connected-mode or idle-mode UE115-e may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.).

[0138] At 615, the UE may format a PUR request message. The PUR request message may, for example, request a new configuration of PUR resources. In some cases, the UE115-e may have an existing PUR allocation, and the PUR request may be for reconfiguration of the existing PUR allocation (e.g., based on updated data traffic at the UE115-e, a change in the presence of higher-priority data at the UE115-e, etc.). At 620, the UE115-e may transmit the PUR request message, and the base station 105-e may receive it.

[0139] At 625, the base station 105-e may determine that the requested PUR allocation for UE115-e is unavailable. In some cases, the base station 105-e may determine that the PUR allocation is unavailable based on one or more of the amount of PUR grants in the requested PUR configuration, the QOS information provided in the PUR request, whether AM PUR is requested 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 for UE115-e.

[0140] At 630, the base station 105-e may send a PUR response message indicating the different PUR configurations allocated for UE115-e to UE115-e. At 635, UE115-e may determine that the PUR configuration provided by the base station 105-e is insufficient for the uplink transmission of UE115-e. For example, UE115-e may have uplink data to be transmitted at a set periodicity (e.g., sensor data to be transmitted once every 30 seconds), and the PUR configuration provided by the base station 105-e may provide PUR grants with a lower periodicity than set (e.g., one PUR grant every 60 seconds). Thus, in this example, based on the insufficient uplink grants in the PUR configuration, UE115-e may determine that the PUR configuration is insufficient. In other examples, UE115-e may determine that the PUR configuration is no longer needed or cannot be applied due to other configurations that conflict with the PUR configuration.

[0141] At 640, UE115-e may send a PUR configuration failure indication to the base station 105-e. In some cases, UE115-e and the base station 105-e may release the PUR configuration based on the PUR configuration failure indication. Such release may enable the base station 105-e to reallocate one or more of the associated uplink resources to one or more other UEs and use network resources more efficiently.

[0142] In some cases, when UE115-e is in the connected mode, a dedicated grant may be provided after the PUR response message so that UE115-e can send a PUR configuration failure message. In some cases, an uplink dedicated grant may be provided within the PUR configuration or within the PUR response message itself. Additionally or alternatively, UE115-e may monitor the PDCCH during some windows following the PUR response message to obtain a UL grant for use when sending a PUR configuration failure message (or PUR configuration confirmation message).

[0143] In other cases, UE115-e may be in the idle mode, and an uplink grant may be provided after the PUR response message so that UE115-e can send a PUR configuration failure from the idle mode. In some cases, an uplink grant may be provided within the PUR configuration or within the PUR response message itself. Additionally or alternatively, UE115-e may monitor the PDCCH during some windows following the PUR response message to obtain an uplink grant for use when sending a PUR configuration failure message (or PUR configuration confirmation message) while in the idle mode. In a further example, additionally or alternatively, a procedure may be defined by which the UE is expected to use the first occurrence of a newly configured (or reconfigured) PUR for sending a PUR configuration failure message (or PUR configuration confirmation message) while in the idle mode.

[0144] As shown with respect to FIG. 5, in some cases, an EDT procedure may be used to exchange PUR request and configuration messages. FIG. 7 shows an example of a process flow 700 that supports PUR techniques in EDT according to an aspect of the present disclosure. In some examples, process flow 700 may implement aspects of wireless communication system 100 or 200. In this example, process flow 700 may include UE115-f and base station 105-f, which may be examples of corresponding devices described with reference to FIGS. 1 and 2.

[0145] At 705, UE 115-f may be in the idle mode. In some cases, UE 115-f may have previously performed connection establishment and may be idle due to there being no uplink or downlink data to be transmitted. At 710, base station 105-f may identify EDT support and PUR resources and may format a system information block (SIB) indicating PUR support and EDT support. In some cases, base station 105-f may determine whether UE 115-f is allowed 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 described 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 during uplink transmission using PUR resources, traffic or service priorities related to PUR configuration. In some cases, the SIB may provide an index to a preconfigured mapping of PUR configuration. In some cases, base station 105-f may configure several different PUR configurations and the SIB may be formatted to indicate multiple PUR configurations. At 715, base station 105-f may transmit a SIB having an indication of PUR support and EDT support, and UE 115-f may receive it.

[0146] In this example, UE 115-f may be in the idle mode. At 720, UE 115-f may receive the SIB and may identify that base station 105-f supports EDT and PUR. In some cases, UE 115-f may periodically monitor for the SIB and other downlink control transmissions while in the idle mode and may receive the SIB during such monitoring.

[0147] At 725, UE115-f may identify uplink data for PUR and may initiate an EDT procedure. At 730, UE115-f may transmit a first EDT message (EDT MSG1) that may include a random access channel (RACH) preamble according to the EDT procedure. The base station 105-f may receive the EDT message and may transmit a random access response including EDT MSG2. For example, the random access response may include an identifier related to UE115-f, as well as a resource allocation (e.g., resource block allocation) and a modulation and coding scheme (MCS) for subsequent EDT messages.

[0148] At 740, UE115-f may format a PUR request message for transmission within the EDT. The PUR request message may, for example, request a new PUR configuration. In some cases, UE115-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 updated data traffic at UE115-f, a change in the presence of higher priority data at UE115-f, etc.).

[0149] At 745, UE115-f may transmit the PUR request message using EDT MSG3. At 750, the base station 105-f may receive the PUR request message and may determine a PUR configuration for UE115-f. In some cases, the base station 105-f may determine the PUR configuration based on one or more of the requested PUR configuration, QoS information provided in the PUR request, whether AM PUR is requested or UM PUR is requested, other PUR configurations for other UEs, the amount of available PUR resources, or any combination thereof.

[0150] At 755, the base station 105-f may transmit a PUR response in the EDT MSG4. The PUR response may indicate a PUR configuration for the UE115-f. In some cases, the PUR configuration may be a new configuration for the UE115-f. In other cases, the PUR configuration may be a reconfigured existing PUR configuration for the UE115-f. In some cases, the PUR configuration may be shared by multiple different UEs, the PUR configuration may indicate shared resources, and information (e.g., a preamble to be provided with the 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 UE115-f to enable the base station 105-f to identify transmissions from the UE115-f may be provided.

[0151] At 760, the UE115-f may identify the PUR configuration provided by the base station 105-f. If the PUR configuration is a new configuration, the UE115-f may configure uplink transmissions to be sent using the PUR configuration. If the PUR configuration is a reconfiguration of an existing PUR configuration, the UE115-f may reconfigure the PUR configuration according to the new PUR configuration. At 765, the UE115-f may optionally transmit a PUR configuration (or reconfiguration) completion message to the base station 105-f.

[0152] Therefore, in this example, UE115-f and base station 105-f may use a mobile originated (MO) EDT process 770 to communicate PUR requests and PUR responses. In other cases, such as those shown in FIG. 5, PUR requests and PUR responses may be exchanged after an EDT procedure. In some cases, UE115-f may use a control plane CIoT EPS optimization based EDT (CP-EDT) procedure from the idle mode. In other cases, UE115-f may use a user plane CIoT EPS optimization based EDT (UP-EDT) from the idle mode. In some cases, an EDT RRC message (e.g., RRCEarlyDataRequest for CP-EDT and RRCConnectionResumeRequest for UP-EDT) may be extended to include a PUR configuration, reconfiguration, or release request information element. Such information elements may be added or concatenated to other RRC information elements, for example. In one example, establishmentCause may be used to indicate that EDT MSG3 includes a PUR configuration, reconfiguration, or release request. For CP-EDT, when there is no uplink payload (user data), dedicatedInfoNAS may be empty, which may indicate that the message is a PUR request. In other cases, a separate RRC message may be included within the EDT MSG3 transmission, i.e., an RRC message for EDT and an RRC message for the PUR request message (i.e., PUR configuration / reconfiguration / release request message).

[0153] Furthermore, as shown in FIG. 7, the base station 105-f may transmit an EDT MSG4 having a PUR response. The PUR response may include a PUR configuration, reconfiguration, or release message as a response. In some cases, the EDT MSG4 may be an RRC early data completion or RRC connection release with an interruption indication. In some cases, such an RRC message may be extended to include a PUR configuration / reconfiguration or release indication. In other cases, separate RRC messages, i.e., one RRC message for the EDT and one RRC message providing a PUR configuration / reconfiguration or release message, may be included in the EDT MSG4.

[0154] In some cases, for signaling efficiency, a delta configuration may be used to configure or reconfigure the PUR. Such a delta configuration may only provide parameters that are changed from a previous PUR configuration or from a default PUR configuration with respect to the current configuration of the UE115-f, and any parameter that does not exist is assumed to have either a default value or an unchanged value from the current UE value (e.g., EARFCN).

[0155] As shown in the illustration, in some cases, EDT MSG4 may provide an RRC early data completion message (e.g., for CP-EDT). In some cases, such a message may implicitly or explicitly indicate that UE115-f may continue to use an already (previously) allocated allocated random access MSG1 data resource with respect to the PUR resource (i.e., an existing PUR configuration), confirm the validity or invalidity of an already (previously) allocated PUR configuration, deconfigure or release an already (previously) allocated PUR configuration, allocate a new Msg1 data resource, or perform one or more of 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 resource. In the absence of such a flag, when UE115-f returns to the idle mode, the previously configured PUR 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, base station 105-f may indicate that PUR support is turned off for all UEs during a call by providing an SIB indication that PUR is not supported. In that case, UE115-f (and other UEs that can receive the SIB) may release any PUR configuration.

[0156] Additionally or alternatively, base station 105-f may determine that the PUR configuration of UE 115-f is to be reconfigured. For example, base station 105-f may determine that the resources allocated to the PUR are to be reallocated to another PUR configuration (e.g., a PUR configuration with a higher priority). In such a case, 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, base station 105-f may send a page to UE 115-f in idle mode to trigger UE 115-f to establish an RRC connection, and when UE 115-f enters the connected mode, base station 105-f may provide a PUR release indication or release command message or reconfiguration. In some cases, an explicit PUR release message may be provided by base station 105-f to indicate to UE 115-f that the configured PUR is to be released.

[0157] Furthermore, in some cases, when UE115-f sends a PUR request message, one or more items of assistance information, such as the UE's coverage enhancement (CE) level, or traffic-related information, may be provided. Such traffic-related information may include, for example, one or more of traffic periodicity (or traffic arrival pattern), traffic probability (i.e., whether the UE always transmits or may have no data), traffic-related delay tolerance, packet size to be transmitted, or any combination thereof. Additionally or alternatively, in some cases, UE115-f may also provide a PUR configuration or reconfiguration request message, the required number of PUR grant occurrences. In some cases, the number of occurrences may be indicated as one time for requesting a one-shot PUR, or as another number greater than one for requesting that number of multi-shot PURs. In other cases, the number of occurrences may be indicated as infinite or indefinite to require that the PUR grant be indefinitely valid until one of the criteria for PUR release is met. In some cases, the number of occurrences may be provided within the information elements in the PUR request. In some cases, the number of occurrences may be indicated as non-existent to require that the PUR resource be indefinitely valid until one of the criteria for PUR release is met. Similarly, in some cases, for the purpose of requesting the release of the PUR resource, the number of occurrences may be indicated as zero, which may avoid having a separate PUR release request message, especially for the purpose of requesting release. In such cases, one or more other fields in the PUR request message may be optional so that UE115-f does not need to include other parameters when requesting PUR release by indicating a request for zero occurrences of the PUR grant. Additionally or alternatively, UE115-f may indicate a PUR reconfiguration failure as described with respect to FIG. 8, which may indicate that the PUR configuration has been released.

[0158] FIG. 8 shows an example of a process flow 800 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. In some examples, the process flow 800 may implement aspects of the wireless communication system 100 or 200. In this example, the process flow 800 may include the UE115-g and the base station 105-g, which are examples of corresponding devices described with reference to FIGS. 1 and 2. In this example, the EDT procedure may be reused to exchange PUR requests and configuration messages as in FIG. 7, but if the PUR configuration provided by the base station 105-g is insufficient for the UE115-g, the UE115-g indicates a PUR configuration failure.

[0159] In this example, at 805, the UE115-g may be in the idle mode. In some cases, the UE115-g may have previously performed connection establishment and may be idle due to no uplink data or downlink data to be transmitted. At 810, the base station 105-g may identify EDT support and PUR resources and may format a system information block (SIB) indicating the PUR support and the EDT support. At 815, the base station 105-g may transmit an SIB having an indication of the PUR support and the EDT support, which the UE115-g may receive.

[0160] In this example, the UE115-g may again be in the idle mode. At 820, the UE115-g may receive the SIB and may identify that the base station 105-g supports EDT and PUR. In some cases, the UE115-g may periodically monitor for the SIB and other downlink control transmissions while in the idle mode and may receive the SIB during such monitoring.

[0161] At 825, UE 115-g may identify uplink data for PUR and may initiate an EDT procedure. At 830, UE 115-g may transmit a first EDT message (EDT MSG1) that may include a RACH preamble according to the EDT procedure. The base station 105-g may receive the EDT message and, at 835, may transmit a random access response that includes EDT MSG2. For example, the random access response may include an identifier associated with UE 115-g, as well as a resource allocation (e.g., resource block allocation) and a modulation and coding scheme (MCS) for subsequent EDT messages.

[0162] At 840, UE 115-g may format a PUR request message to be transmitted within the EDT. The PUR request message may, for example, request a new PUR configuration. In some cases, UE 115-g 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 updated data traffic at UE 115-g, a change in the presence of higher priority data at UE 115-g, etc.).

[0163] At 845, UE 115-g may transmit the PUR request message using EDT MSG3. At 850, the base station 105-g may receive the PUR request message and may determine a PUR configuration for UE 115-g. In this example, at 850, the 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.

[0164] At 855, the base station 105-g may transmit a PUR response within EDT MSG4. The PUR response may indicate a different PUR configuration for UE 115-g. In some cases, the PUR configuration may be a new configuration for UE 115-g. In other cases, the PUR configuration may be a reconfigured existing PUR configuration for UE 115-g.

[0165] At 860, UE115-g may identify different PUR configurations provided by base station 105-g and may determine that a different PUR configuration is insufficient (e.g., based on fewer PUR grants than are required for uplink data transmission). At 865, UE115-g may send a PUR configuration (or reconfiguration) failure message to base station 105-g. Thus, in this example, UE115-g and base station 105-g may reuse MO EDT process 870 to communicate PUR requests and PUR responses. Additionally, an additional uplink transmission may be provided to indicate a PUR configuration failure, and the uplink resources for the uplink transmission may be identified as described herein, as with respect to FIG. 6.

[0166] In some cases, if the base station determines that the requested PUR configuration is unavailable, the base station may send a PUR rejection message to the UE instead of a PUR configuration or reconfiguration message. UE operation after receiving such a rejection message may be based on one or more implicit or explicit indications associated with the rejection message. FIG. 9 shows an example of a process flow 900 that supports PUR techniques in which a PUR rejection message is sent to a UE, according to an aspect of the present disclosure. In some examples, process flow 900 may implement aspects of wireless communication system 100 or 200. In this example, process flow 900 may include UE115-h and base station 105-h, which may be examples of corresponding devices described with reference to FIGS. 1 and 2.

[0167] At 905, base station 105-h and UE115-h may each determine that the PUR conditions are satisfied. Such determination may be made as described in various examples herein, such as based on the base station 105-h establishing a PUR configuration and providing those indications to the UE (e.g., in an SIB), and UE115-h may receive such indications and determine that a PUR configuration should be requested.

[0168] At 910, the UE may identify an uplink resource for transmitting the PUR request message. In some cases, an uplink resource may be provided among the uplink grants related to the connected-mode UE115-h. In other cases, the connected-mode or idle-mode UE115-h may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.).

[0169] At 915, the UE may format the PUR request message. The PUR request message may, for example, request a new configuration of PUR resources. In some cases, the UE115-h may have an existing PUR allocation, and the PUR request may be for reconfiguration of the existing PUR allocation (e.g., based on updated data traffic at the UE115-h, a change in the presence of higher-priority data at the UE115-h, etc.). At 920, the UE115-h may send the PUR request message, and the base station 105-h may receive it.

[0170] At 925, the base station 105-h may determine that the requested PUR allocation for the UE115-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 amount of PUR grants in the requested PUR configuration, the QoS information provided in the PUR request, whether AM PUR 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 for the UE115-h.

[0171] At 930, the base station 105-h may determine whether to retain or release the existing PUR configuration of the UE115-h if an existing PUR configuration exists. At 935, the base station 105-h may send a PUR rejection message to the UE115-h that may provide an indication regarding the handling of the existing PUR configuration of the UE115-h if such an existing PUR configuration exists. If there is no existing PUR, the UE115-h may fallback to other techniques for uplink data transmission (e.g., scheduling request transmission, EDT procedure, random access technique, SPS transmission, etc.). If an existing PUR configuration exists, one or more default rules may be provided indicating that the existing PUR configuration will be continued or released. In some cases, if the UE115-h does not receive a response message from the base station 105-h, the UE115-h may consider the PUR request to be rejected and may use the default rules for the existing PUR configuration if it exists. In some cases, the PUR rejection message may include an explicit indication regarding the handling of the existing PUR configuration. For example, the base station 105-h may indicate to the UE115-h that the PUR request is rejected and that the configured PUR will be released, or that the PUR request is rejected and the configured PUR will be maintained. Such an explicit indication may provide the base station 105-h with extended flexibility to determine and explicitly indicate UE115-h behavior based on various conditions at the base station 105-h that resulted in the PUR rejection message.

[0172] Figure 10 shows a block diagram 1000 of a device 1005 that supports PUR techniques in wireless communication, according to an aspect of the present disclosure. The device 1005 may be an example of an aspect of the UE115 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).

[0173] The receiver 1010 can receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to the PUR technique in wireless communication). The information may be passed to other components of the device 1005. The receiver 1010 may be an example of the aspect of the transceiver 1320 described with reference to FIG. 13. The receiver 1010 may utilize a single antenna or a set of antennas.

[0174] In some cases, the communication manager 1015 may determine that the base station supports PUR for grant-free uplink transmission from the UE, may send a PUR request message to the base station based on the determination that the base station supports PUR, may receive a PUR configuration identifying the PUR allocated to the UE from the base station in response to the PUR request message, may receive an uplink resource for the response message to be sent from the UE, and may send a PUR configuration response message to the base station using the uplink resource for the response message.

[0175] In some cases, the communication manager 1015 may also determine an EDT configuration for the EDT procedure, where the EDT configuration provides for the uplink transmission of UE payload data in the uplink message of the EDT procedure, formats the PUR request message to be sent 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, sends the PUR request message in the uplink message of the EDT procedure, and receives a PUR configuration message from the base station in response to the uplink message.

[0176] In some cases, the communication manager 1015 may also communicate with the base station according to a pre-configured uplink resource configuration, where the pre-configured uplink resource configuration provides grant-free uplink transmission from the UE to the base station, receives from the base station a pre-configured uplink resource release message indicating that the UE will deconfigure the pre-configured uplink resource configuration, and deconfigure the pre-configured uplink resource configuration at least partially based on the pre-configured uplink resource release message.

[0177] In some cases, the communication manager 1015 may also determine that the base station supports PUR for grant-free uplink transmission from the UE, and send 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 PUR permission requested by the UE, and receive a PUR configuration from the base station in response to the PUR request message.

[0178] In some cases, the communication manager 1015 may also determine that the base station supports PUR for grant-free uplink transmission from the UE, send a PUR request message to the base station based on the determination that the base station supports PUR, and receive from the base station a PUR response message indicating that the PUR request message is rejected, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message. The communication manager 1015 may be an example of the aspects of the communication manager 1310 described herein.

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

[0180] The communication manager 1015 or its sub-components can be physically located in various locations, including being distributed such that portions of the functionality are implemented in different physical locations by one or more physical components. In some examples, the communication manager 1015 or its sub-components can be separate and distinct components according to various aspects of this disclosure. In some examples, the communication manager 1015 or its sub-components can 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 this disclosure, or combinations thereof according to various aspects of this disclosure.

[0181] The transmitter 1020 can transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 can be placed together with the receiver 1010 within a transceiver module. For example, the transmitter 1020 can be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The transmitter 1020 can utilize a single antenna or a set of antennas.

[0182] FIG. 11 shows a block diagram 1100 of a device 1105 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. The device 1105 may be an example of the device 1005 or an aspect of the UE 115 as 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 each other (e.g., via one or more buses).

[0183] The receiver 1110 may receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to the PUR technique in wireless communication). The information may be passed to other components of the device 1105. The receiver 1110 may be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The receiver 1110 may utilize a single antenna or a set of antennas.

[0184] The communication manager 1115 may be an example of an aspect of the communication manager 1015 as described herein. The communication manager 1115 may include a PUR decision 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 may be an example of an aspect of the communication manager 1310 described herein.

[0185] The PUR decision component 1120 may determine that the base station supports PUR for grant-free uplink transmission from the UE. The PUR request manager 1125 may transmit a PUR request message to the base station based on the decision that the base station supports PUR. The PUR configuration manager 1130 may receive, in response to the PUR request message, a PUR configuration from the base station that identifies the PUR allocated to the UE. The PUR transmission manager 1135 may receive uplink resources for the response message to be transmitted from the UE, and may transmit a PUR configuration response message to the base station using the uplink resources for the response message.

[0186] The EDT random access manager 1140 may determine an EDT configuration for 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 may format the 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, and may transmit the PUR request message in the uplink message of the EDT procedure. The PUR configuration manager 1130 may receive a PUR configuration message from the base station in response to the PUR request message.

[0187] The PUR decision component 1120 may determine that the base station supports PUR for grant-free uplink transmission from the UE. The PUR request manager 1125 may transmit a PUR request message to the base station based on the decision that the base station supports PUR, where the PUR request message includes the number of instances of PUR permission requested by the UE. The PUR configuration manager 1130 may receive a PUR configuration from the base station in response to the PUR request message.

[0188] The PUR decision component 1120 may determine that the base station supports PUR for grant-free uplink transmission from the UE. The PUR request manager 1125 may send a PUR request message to the base station based on the decision that the base station supports PUR. The PUR configuration manager 1130 may receive, in response to the PUR request message, a PUR response message from the base station indicating that the PUR request message is rejected, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message.

[0189] The transmitter 1145 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1145 may be placed together with the receiver 1110 in a transceiver module. For example, the transmitter 1145 may be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The transmitter 1145 may utilize a single antenna or a set of antennas.

[0190] FIG. 12 shows a block diagram 1200 of a communication manager 1205 that supports PUR techniques in wireless communication, according to an aspect of the present disclosure. The communication manager 1205 may be an example of an aspect of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 may include a PUR decision 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 permission manager 1250. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0191] The PUR decision component 1210 may determine that the base station supports PUR for grant-free uplink transmission from the UE.

[0192] The PUR request manager 1215 may send a PUR request message to the base station based on the decision that the base station supports PUR. In some examples, the PUR request manager 1215 may format the PUR request message to be sent within the uplink message of the EDT procedure, where the PUR request message indicates the requested configuration, reconfiguration, or release of the PUR configuration. In some examples, the PUR request manager 1215 may send the PUR request message within the uplink message of the EDT procedure.

[0193] In some examples, the PUR request manager 1215 may send a PUR request message to the base station based on the decision that the base station supports PUR, where the PUR request message includes the number of instances of PUR permission requested by the UE. In some examples, the PUR request manager 1215 may send a PUR request message to the base station based on the decision that the base station supports PUR.

[0194] The PUR configuration manager 1220 may receive from the base station a PUR configuration that identifies the PUR allocated to the UE in response to the PUR request message. In some examples, the PUR configuration manager 1220 may receive a PUR configuration message from the base station in response to the PUR request message.

[0195] In some examples, the PUR configuration manager 1220 may receive from the base station a PUR response message indicating that the PUR request message has been rejected in response to the PUR request message, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message.

[0196] In some examples, the PUR configuration manager 1220 may determine a set of control channel resources to monitor for an uplink grant based on the PUR configuration from the base station. In some examples, the PUR configuration manager 1220 may monitor a 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.

[0197] In some examples, the PUR configuration manager 1220 may determine that the PUR configuration is to be deconfigured based on receiving broadcast system information transmission from the base station indicating that PUR is not supported. In some examples, the PUR configuration manager 1220 may release the PUR configuration.

[0198] In some examples, the PUR configuration manager 1220 may receive an indication from the base station that the PUR configuration is to be reconfigured. In some examples, the PUR configuration manager 1220 may receive, in a random access response message, an indication transmitted in response to a random access request message of the UE from the base station.

[0199] In some examples, the PUR configuration manager 1220 may receive a PUR release message from the base station. In some examples, the PUR configuration manager 1220 may deconfigure the PUR configuration based on the PUR release message. In some examples, the PUR configuration manager 1220 may determine that a previous PUR configuration is to be released.

[0200] In some examples, the PUR configuration manager 1220 may transmit an indication of zero instances of PUR grants in the PUR request message.

[0201] In some examples, after receiving the PUR configuration, the PUR configuration manager 1220 may transmit a PUR reconfiguration failure indication to the base station. In some examples, the PUR configuration manager 1220 may release the PUR configuration.

[0202] In some cases, the PUR configuration is provided as a delta configuration indicating the difference from the UE's previous PUR configuration. In some cases, the PUR configuration is provided as a delta configuration indicating the difference from the current configuration being used by the UE. In some cases, the PUR configuration is provided as a delta configuration indicating the difference from the default PUR configuration.

[0203] In some cases, the uplink resources for the response message are provided in an explicit indication with the PUR configuration from the base station. In some cases, the PUR configuration message from the base station is received in the EDT downlink message. In some cases, the PUR configuration is provided in the EDT early data completion message indicating the configured PUR resources of the UE. In some cases, the EDT early data completion message explicitly or implicitly provides one or more of an indication that the UE is to use the previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration is to be deconfigured and released, new resources for the new PUR configuration, or any combination thereof. In some cases, the indication that the previous PUR configuration is to be deconfigured and released includes a boolean flag in the EDT early data completion message.

[0204] In some cases, the PUR request message indicates that reconfiguration of the previous PUR configuration is requested, where the PUR response message indicates that the previous PUR configuration is to be released by the UE. In some cases, the PUR request message indicates that reconfiguration of the previous PUR configuration is requested, where the PUR response message indicates that the previous PUR configuration is to be maintained by the UE.

[0205] The PUR transmission manager 1225 may receive an uplink resource for a response message to be transmitted from the UE. In some examples, the PUR transmission manager 1225 may use the uplink resource for the response message to transmit a PUR configuration response message to the base station. In some cases, the uplink resource for the response message is included in the first instance of PUR allocated to the UE. In some cases, transmitting the PUR configuration response message is performed when the UE is in the idle mode or in the connected mode with the base station.

[0206] 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 examples, the EDT random access manager 1230 may receive an indication from the base station that an uplink message of the EDT procedure is 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 message 3 (MSG3) transmission 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 establishment cause in the RRC message indicates that the random access message contains a PUR request. In some cases, the RRC message includes an indication of uplink payload data, where a predetermined value of the indication of uplink payload data indicates that the random access message contains a PUR request. In some cases, the RRC message of the EDT procedure includes a concatenated first RRC message related to the EDT procedure and a second RRC message related to the PUR request.

[0207] The PUR response manager 1235 can respond to a PUR configuration message and transmit an indication of a successful PUR configuration or a PUR configuration failure using an uplink resource for a response message from the UE.

[0208] The paging manager 1240 can receive a paging message from the base station. In some examples, the paging manager 1240 can transmit a random access request message to the base station in response to the paging message, where receiving an indication that the PUR configuration should be reconfigured responds to the random access request message. In some cases, the indication that the PUR configuration should be reconfigured indicates a new PUR configuration to be used by the UE or that the UE will release the PUR configuration.

[0209] 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 connected mode or in an EDT random access message, where the PUR release message is an RRC PUR reconfiguration message.

[0210] The PUR permission manager 1250 can receive a PUR permission and can identify the number of instances of PUR permission that should be requested for a PUR configuration. In some cases, the number of instances of PUR permission provides an indication of an explicit number of PUR permissions or an indefinite number of PUR permissions. In some cases, the indefinite number of PUR permissions is indicated by the absence of a PUR permission request field in the PUR request message or by a predetermined value in the PUR permission request field. In some cases, the number of instances of PUR permission requested by the UE indicates that a one-shot PUR configuration is requested or that a multi-shot PUR configuration is requested.

[0211] FIG. 13 shows a diagram of a system 1300 that includes a device 1305 that supports the PUR technique in wireless communication. The device 1305 may be an example of, or may include, the components of the device 1005, the device 1105, or the UE 115 as described herein. The device 1305 may include components for transmitting and receiving communication, including components for two-way voice and data 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 may communicate electronically via one or more buses (e.g., bus 1345).

[0212] The communication manager 1310 may determine that the base station supports PUR for grant-free uplink transmission from the UE, may send a PUR request message to the base station based on the determination that the base station supports PUR, may receive a PUR configuration from the base station that identifies the PUR allocated to the UE in response to the PUR request message, may receive an uplink resource for a response message to be transmitted from the UE, and may send a PUR configuration response message to the base station using the uplink resource for the response message.

[0213] The communication manager 1310 may 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, formats 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 the PUR configuration, transmits the PUR request message in an uplink message of the EDT procedure, and receives a PUR configuration message from the base station in response to the PUR request message.

[0214] The communication manager 1310 may also communicate with the base station according to a pre-configured uplink resource configuration, where the pre-configured uplink resource configuration provides grant-free uplink transmission from the UE to the base station, receives from the base station a pre-configured uplink resource release message indicating that the UE will release the pre-configured uplink resource configuration, and release the pre-configured uplink resource configuration at least partially based on the pre-configured uplink resource release message.

[0215] The communication manager 1310 may also determine that the base station supports PUR for grant-free uplink transmission from the UE, and 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 PUR permission requested by the UE, and receive a PUR configuration from the base station in response to the PUR request message.

[0216] 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 from the base station a PUR response message indicating that the PUR request message is rejected, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message.

[0217] The I / O controller 1315 can manage input and output signals for the device 1305. The I / O controller 1315 can also manage peripheral devices not integrated within 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 (registered trademark), ANDROID (registered trademark), MS-DOS (registered trademark), MS-WINDOWS (registered trademark), OS / 2 (registered trademark), UNIX (registered trademark), LINUX (registered trademark), or another known operating system. In other cases, the I / O controller 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, a user may interact with the device 1305 via the I / O controller 1315 or via hardware components controlled by the I / O controller 1315.

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

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

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

[0221] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated within the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause the device 1305 to perform various functions (e.g., functions or tasks that support PUR techniques in wireless communication).

[0222] Code 1335 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1335 may 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 may cause a computer to perform functions described herein (e.g., when compiled and executed).

[0223] FIG. 14 shows a block diagram 1400 of a device 1405 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. The device 1405 may be an example of an aspect of the base station 105 as described herein. The device 1405 may include a receiver 1410, a communication manager 1415, and a transmitter 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0224] The receiver 1410 may receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to the PUR technique in wireless communication). The information may be passed to other components of the device 1405. The receiver 1410 may be an example of an aspect of the transceiver 1720 described with reference to FIG. 17. The receiver 1410 may utilize a single antenna or a set of antennas.

[0225] The communication manager 1415 may transmit an indication that the base station supports PUR for grant-free uplink transmission, may transmit a PUR configuration that identifies the PUR allocated to the UE to the UE in response to a PUR request message, may receive a PUR request message from the UE, and may receive a PUR configuration response from the UE via an uplink resource for the response message.

[0226] The communication manager 1415 may also determine an EDT configuration for the EDT procedure, where the EDT configuration provides for the uplink transmission of UE payload data in the uplink message of the EDT procedure, and receives 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 transmits a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates an uplink resource for a response message from the UE.

[0227] The communication manager 1415 may also send an indication that the base station supports PUR for grant-free uplink transmission, may send a PUR configuration to the UE in response to a PUR request message, and 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.

[0228] The communication manager 1415 may also send an indication that the base station supports PUR for grant-free uplink transmission, and in response to a PUR request message, send a PUR response message to the UE indicating that the PUR request message has been rejected, 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 may be an example of the aspects of the communication manager 1710 described herein.

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

[0230] The communication manager 1415 or its sub-components may be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations by one or more physical components. In some examples, the communication manager 1415 or its sub-components may be separate and distinct components according to various aspects of this disclosure. In some examples, 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 this disclosure, or combinations thereof according to various aspects of this disclosure.

[0231] The transmitter 1420 may transmit signals generated by other components of the device 1405. In some examples, the transmitter 1420 may be placed together with the receiver 1410 within a transceiver module. For example, the transmitter 1420 may be an example of an aspect of the transceiver 1720 described with reference to FIG. 17. The transmitter 1420 may utilize a single antenna or a set of antennas.

[0232] Figure 15 shows a block diagram 1500 of a device 1505 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. The device 1505 may be an example of the device 1405 or an aspect of the base station 105 as 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).

[0233] The receiver 1510 may receive information such as packets, user data, or control information related to various information channels (e.g., control channels, data channels, and information related to the PUR technique in wireless communication). The information may be passed to other components of the device 1505. The receiver 1510 may be an example of an aspect of the transceiver 1720 described with reference to FIG. 17. The receiver 1510 may utilize a single antenna or a set of antennas.

[0234] The communication manager 1515 may be an example of an aspect of the communication manager 1415 as 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 an aspect of the communication manager 1710 described herein.

[0235] The PUR configuration manager 1520 may transmit an indication that the base station supports PUR for grant-free uplink transmission, and may transmit a PUR configuration that identifies 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 an uplink resource for the response message.

[0236] The EDT random access manager 1535 may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for the uplink transmission of UE payload data in an uplink message of the EDT procedure. The PUR request manager 1525 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 PUR configuration manager 1520 may transmit a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates an uplink resource for a response message from the UE.

[0237] The PUR configuration manager 1520 may transmit an indication that the base station supports PUR for grant-free uplink transmission and may transmit a PUR configuration to the UE in response to the PUR request message. The PUR request manager 1525 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.

[0238] The PUR configuration manager 1520 may transmit an indication that the base station supports PUR for grant-free uplink transmission and may transmit a PUR response message to the UE in response to the PUR request message, where the PUR response message indicates that the PUR request message has been rejected and indicates how the UE is to proceed based on the rejected PUR request message. The PUR request manager 1525 may receive a PUR request message from the UE.

[0239] The transmitter 1540 may transmit signals generated by other components of the device 1505. In some examples, the transmitter 1540 may be co-located with the receiver 1510 within a transceiver module. For example, the transmitter 1540 may be an example of an aspect of the transceiver 1720 described with reference to FIG. 17. The transmitter 1540 may utilize a single antenna or a set of antennas.

[0240] FIG. 16 shows a block diagram 1600 of a communication manager 1605 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. The communication manager 1605 may be an example of an aspect of the communication manager 1415, the communication manager 1515, or the communication manager 1710 described herein. The communication manager 1605 may 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 permission manager 1635. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0241] The PUR configuration manager 1610 may transmit an indication that the base station supports PUR for grant-free uplink transmission. In some examples, the PUR configuration manager 1610 may transmit a PUR configuration identifying the PUR allocated to the UE to the UE in response to a PUR request message. In some examples, 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 uplink resources for a response message from the UE. In some examples, the PUR configuration manager 1610 may transmit an indication that the base station supports PUR for grant-free uplink transmission. In some examples, the PUR configuration manager 1610 may transmit a PUR configuration to the UE in response to a PUR request message.

[0242] In some examples, the PUR configuration manager 1610 may send a PUR response message to the UE in response to a PUR request message, indicating that the PUR request message is rejected, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message. In some examples, the PUR configuration manager 1610 may receive an indication of a successful PUR configuration or a PUR configuration failure using an uplink resource for a response message from the UE in response to a PUR configuration message. In some examples, the PUR configuration manager 1610 may send broadcast system information transmission indicating that PUR is not supported and that the UE will release the PUR configuration.

[0243] In some examples, the PUR configuration manager 1610 may send a PUR release message to the UE. In some examples, the PUR configuration manager 1610 may deconfigure the PUR configuration based on the PUR release message.

[0244] In some cases, the PUR configuration is provided as a delta configuration indicating the difference over the UE's previous PUR configuration, the current configuration used by the UE, or the default PUR configuration. In some cases, the uplink resource for the response message is provided in an explicit indication of the PUR configuration from the base station. In some cases, the uplink resource for the response message is provided in a control channel transmission from the base station within a set of control channel resources to be monitored by the UE. In some cases, the PUR configuration failure indication is sent when the UE is in idle mode or in a connected mode with the base station. In some cases, the PUR configuration is provided as a delta configuration indicating the difference over the UE's previous PUR configuration, the difference over the default PUR configuration, or the difference over the configuration used in the UE.

[0245] In some cases, the PUR configuration is provided in the EDT early data completion message indicating the configured PUR resources of the UE. In some cases, the EDT early data completion message explicitly or implicitly provides an indication that the UE will use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration should be deconfigured and released, new resources for a new PUR configuration, or any combination thereof. In some cases, the indication that the previous PUR configuration should be deconfigured and released includes a boolean flag in the EDT early data completion message. In some cases, the PUR release message is sent while the UE is in the connected mode or in the EDT random access response message, where the PUR release message is an RRC PUR reconfiguration message. In some cases, the PUR request message indicates that a reconfiguration of a previous PUR configuration is requested, where the PUR response message indicates that the previous PUR configuration will be released by the UE. In some cases, the PUR request message indicates that a reconfiguration of a previous PUR configuration is requested, where the PUR response message indicates that the previous PUR configuration will be maintained by the UE.

[0246] The PUR request manager 1615 may receive a PUR request message from the UE. In some examples, the PUR request manager 1615 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. In some examples, the PUR request manager 1615 may receive a PUR request message from the UE, where the PUR request message includes the number of instances of PUR permission requested by the UE. In some examples, the PUR request manager 1615 may receive a PUR request message from the UE.

[0247] The PUR response manager 1620 may receive a PUR configuration response from the UE via an uplink resource for the response message.

[0248] The EDT random access manager 1625 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 examples, the EDT random access manager 1625 may send an indication that an uplink message of the EDT procedure is available for a PUR request message. In some cases, the indication is sent in a system information block broadcast from the base station.

[0249] The paging manager 1630 may determine that the PUR configuration of the UE is to be reconfigured or released. In some examples, the paging manager 1630 may send a page message to the UE. In some examples, the paging manager 1630 may receive a random access request message from the UE in response to the page message. In some examples, the paging manager 1630 may send an indication that the PUR configuration is to be reconfigured or released in response to the random access request message. In some cases, the indication that the PUR configuration is to be reconfigured indicates a new PUR configuration to be used by the UE or indicates that the UE is to release the PUR configuration.

[0250] The PUR grant manager 1635 may identify a PUR grant for the UE PUR configuration. In some cases, the number of instances of the PUR grant provides an indication of the explicit number of PUR grants or an indefinite number of PUR grants. In some cases, a number of instances that is zero 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 that a one-shot PUR configuration is requested or that a multi-shot PUR configuration is requested.

[0251] FIG. 17 shows a diagram of a system 1700 including a device 1705 that supports the PUR technique in wireless communication according to an aspect of the present disclosure. The device 1705 may be an example of or include components of the device 1405, the device 1505, or the base station 105 as described herein. The device 1705 may include components for transmitting and receiving communication, including components for two-way voice and data 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 may communicate electronically via one or more buses (e.g., bus 1750).

[0252] The communication manager 1710 may send an indication that the base station supports PUR for grant-free uplink transmission, send a PUR configuration identifying the PUR allocated to the UE 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 an uplink resource for the response message.

[0253] The communication manager 1710 may also determine an EDT configuration for the 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 an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration, and send a PUR configuration message to the UE in response to the PUR request message, where the PUR configuration indicates an uplink resource for a response message from the UE.

[0254] The communication manager 1710 may also send an indication that the base station supports PUR for grant-free uplink transmission, may send a PUR configuration to the UE in response to a PUR request message, and 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.

[0255] The communication manager 1710 may also send an indication that the base station supports PUR for grant-free uplink transmission and, in response to a PUR request message, send a PUR response message to the UE indicating that the PUR request message has been rejected, where the PUR response message indicates how the UE is to proceed based on the rejected PUR request message, and may receive a PUR request message from the UE.

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

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

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

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

[0260] Processor 1740 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, individual gate or transistor logic component, individual hardware component, or any combination thereof). In some cases, processor 1740 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated within processor 1740. Processor 1740 may 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 that support PUR techniques in wireless communication).

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

[0262] Code 1735 may include instructions for implementing aspects of the present disclosure, 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 Processor 1740, but may cause a computer to perform the functions described herein (e.g., when compiled and executed).

[0263] FIG. 18 shows a flowchart illustrating a method 1800 for supporting the PUR technique in wireless communication according to an aspect of the present disclosure. The operations of method 1800 may be performed by UE 115 or its components as described herein. For example, the operations of method 1800 may be executed by a communication manager as described with reference to FIGS. 10-13. In some examples, the UE may execute a set of instructions for controlling the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0264] At 1805, the UE may determine that the base station supports PUR for grant-free uplink transmission from the UE. The operation of 1805 may be performed according to the method described herein. In some examples, the aspect of the operation of 1805 may be performed by a PUR determination component as described with reference to FIGS. 10-13.

[0265] 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 of 1810 may be performed according to the method described herein. In some examples, the aspect of the operation of 1810 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0266] In 1815, the UE may receive, in response to a PUR request message, a PUR configuration from the base station that identifies the PUR allocated to the UE. The operation of 1815 may be performed according to the methods described herein. In some examples, aspects of the operation of 1815 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13.

[0267] In 1820, the UE may receive uplink resources for a response message to be transmitted from the UE. The operation of 1820 may be performed according to the methods described herein. In some examples, aspects of the operation of 1820 may be performed by a PUR transmission manager as described with reference to FIGS. 10-13.

[0268] In 1825, the UE may use the uplink resources for the response message to transmit a PUR configuration response message to the base station. The operation of 1825 may be performed according to the methods described herein. In some examples, aspects of the operation of 1825 may be performed by a PUR transmission manager as described with reference to FIGS. 10-13.

[0269] FIG. 19 shows a flowchart illustrating a method 1900 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 1900 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1900 may be performed by a communication manager as described with reference to FIGS. 10-13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0270] In 1905, the UE may determine that the base station supports PUR for grant-free uplink transmission from the UE. The operation of 1905 may be performed according to the methods described herein. In some examples, the aspects of the operation of 1905 may be performed by the PUR determination component as described with reference to FIGS. 10-13.

[0271] In 1910, the UE may send a PUR request message to the base station based on the determination that the base station supports PUR. The operation of 1910 may be performed according to the methods described herein. In some examples, the aspects of the operation of 1910 may be performed by the PUR request manager as described with reference to FIGS. 10-13.

[0272] In 1915, the UE may receive from the base station a PUR configuration that identifies the PUR allocated to the UE in response to the PUR request message. The operation of 1915 may be performed according to the methods described herein. In some examples, the aspects of the operation of 1915 may be performed by the PUR configuration manager as described with reference to FIGS. 10-13.

[0273] In 1920, the UE may determine a set of control channel resources to monitor for seeking uplink grants based on the PUR configuration from the base station. The operation of 1920 may be performed according to the methods described herein. In some examples, the aspects of the operation of 1920 may be performed by the PUR configuration manager as described with reference to FIGS. 10-13.

[0274] In 1925, the UE may monitor a set of control channel resources for seeking uplink grants, where the uplink grant indicates uplink resources for transmitting a PUR configuration response message to the base station. The operation of 1925 may be performed according to the methods described herein. In some examples, the aspects of the operation of 1925 may be performed by the PUR configuration manager as described with reference to FIGS. 10-13.

[0275] In 1930, the UE may receive an uplink resource for a response message to be transmitted from the UE. The operation of 1930 may be performed according to the methods described herein. In some examples, aspects of the operation of 1930 may be performed by a PUR transmission manager as described with reference to FIGS. 10-13.

[0276] In 1935, the UE may transmit a PUR configuration response message to the base station using the uplink resource for the response message. The operation of 1935 may be performed according to the methods described herein. In some examples, aspects of the operation of 1935 may be performed by a PUR transmission manager as described with reference to FIGS. 10-13.

[0277] FIG. 20 shows a flowchart illustrating a method 2000 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2000 may be implemented by 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-13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0278] In 2005, 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 2005 may be performed according to the methods described herein. In some examples, aspects of the operation of 2005 may be performed by an EDT random access manager as described with reference to FIGS. 10-13.

[0279] Optionally, in 2010, the UE may format a PUR request message to be sent in an uplink message of an EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operations in 2010 may be performed according to the methods described herein. In some examples, aspects of the operations in 2010 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0280] In 2015, the UE may send an uplink message of an EDT procedure. Optionally, the uplink message may include a PUR request message indicating a requested configuration, reconfiguration, or release of a PUR configuration. The operations in 2015 may be performed according to the methods described herein. In some examples, aspects of the operations in 2015 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0281] In 2020, the UE may receive a PUR configuration message from a base station in response to an uplink message. The operations in 2020 may be performed according to the methods described herein. In some examples, aspects of the operations in 2020 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13.

[0282] FIG. 21 shows a flowchart illustrating a method 2100 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2100 may be implemented by UE 115 or components thereof as described herein. For example, the operations of method 2100 may be performed by a communication manager as described with reference to FIGS. 10-13. In some examples, the UE may execute a set of instructions for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0283] At 2105, 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 2105 may be performed according to the methods described herein. In some examples, aspects of the operation of 2105 may be performed by an EDT random access manager as described with reference to FIGS. 10-13.

[0284] At 2110, the UE may format a PUR request message to be sent 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 examples, aspects of the operation of 2110 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0285] At 2115, the UE may send a 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 examples, aspects of the operation of 2115 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0286] At 2120, the UE may receive a PUR configuration message from a base station in response to a PUR request message. The operation of 2120 may be performed according to the methods described herein. In some examples, aspects of the operation of 2120 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13.

[0287] At 2125, the UE may, in response to the PUR configuration message, use an uplink resource for the response message from the UE to send an indication of a successful PUR configuration or a PUR configuration failure. The operation of 2125 may be performed according to the methods described herein. In some examples, aspects of the operation of 2125 may be performed by a PUR response manager as described with reference to FIGS. 10-13.

[0288] FIG. 22 shows a flowchart illustrating a method 2200 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2200 may be performed by UE 115 or its components as described herein. For example, the operations of method 2200 may be performed by a communication manager as described with reference to FIGS. 10-13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0289] At 2205, the UE may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for the 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 examples, aspects of the operation of 2205 may be performed by an EDT random access manager as described with reference to FIGS. 10-13.

[0290] At 2210, the UE may format a PUR request message to be sent 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 examples, aspects of the operation of 2210 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0291] At 2215, the UE may send a 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 examples, the manner of operation of 2215 may be performed by a PUR request manager as described with reference to FIGS. 10-13.

[0292] At 2220, the UE may receive a PUR configuration message from the base station in response to the PUR request message. The operation of 2220 may be performed according to the methods described herein. In some examples, the manner of operation of 2220 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13.

[0293] FIG. 23 shows a flowchart illustrating a method 2300 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2300 may be performed by UE 115 or its components as described herein. For example, the operations of method 2300 may be performed by a communication manager as described with reference to FIGS. 10-13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0294] At 2305, the UE may determine an EDT configuration for the 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 2305 may be performed according to the methods described herein. In some examples, the manner of operation of 2305 may be performed by an EDT random access manager as described with reference to FIGS. 10-13.

[0295] At 2310, the UE may format a PUR request message to be sent in an uplink message of an EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2310 may be performed according to the methods described herein. In some examples, the operation mode of 2310 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13.

[0296] At 2315, the UE may send a PUR request message in an uplink message of an EDT procedure. The operation of 2315 may be performed according to the methods described herein. In some examples, the operation mode of 2315 may be performed by a PUR request manager as described with reference to FIGS. 10 to 13.

[0297] At 2320, the UE may receive a PUR configuration message from the base station in response to a PUR request message. The operation of 2320 may be performed according to the methods described herein. In some examples, the operation mode of 2320 may be performed by a PUR configuration manager as described with reference to FIGS. 10 to 13.

[0298] 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, the operation mode of 2325 may be performed by a paging manager as described with reference to FIGS. 10 to 13.

[0299] At 2330, the UE may send a random access request message to the base station in response to a paging message. The operation of 2330 may be performed according to the methods described herein. In some examples, the operation mode of 2330 may be performed by a paging manager as described with reference to FIGS. 10 to 13.

[0300] At 2335, the UE may receive an indication from the base station that the PUR configuration should be reconfigured. The operations of 2335 may be performed according to the methods described herein. In some examples, aspects of the operations of 2335 may be performed by a PUR configuration manager as described with reference to FIGS. 10 - 13.

[0301] FIG. 24 shows a flowchart illustrating a method 2400 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2400 may be implemented by the UE 115 or its components as described herein. For example, the operations of method 2400 may be performed by a communication manager as described with reference to FIGS. 10 - 13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0302] At 2405, the UE may determine that the base station supports PUR for grant - free uplink transmissions from the UE. The operations of 2405 may be performed according to the methods described herein. In some examples, aspects of the operations of 2405 may be performed by a PUR decision component as described with reference to FIGS. 10 - 13.

[0303] At 2410, the UE may 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 PUR grants requested by the UE. The operations of 2410 may be performed according to the methods described herein. In some examples, aspects of the operations of 2410 may be performed by a PUR request manager as described with reference to FIGS. 10 - 13.

[0304] At 2415, the UE may receive the PUR configuration from the base station. The operations of 2415 may be performed according to the methods described herein. In some examples, aspects of the operations of 2415 may be performed by a PUR configuration manager as described with reference to FIGS. 10 - 13. In some cases, the PUR configuration may be based on the number of instances of PUR grants requested by the UE.

[0305] FIG. 25 shows a flowchart depicting a method 2500 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2500 may be implemented by UE 115 or its components as described herein. For example, the operations of method 2500 may be performed by a communication manager as described with reference to FIGS. 10 - 13. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0306] At 2505, the UE may determine that the base station supports PUR for grant - free uplink transmissions from the UE. The operations of 2505 may be performed according to the methods described herein. In some examples, aspects of the operations of 2505 may be performed by a PUR decision component as described with reference to FIGS. 10 - 13.

[0307] At 2510, the UE may transmit a PUR request message to the base station based on the determination that the base station supports PUR. The operations of 2510 may be performed according to the methods described herein. In some examples, aspects of the operations of 2510 may be performed by a PUR request manager as described with reference to FIGS. 10 - 13.

[0308] At 2515, the UE may receive, in response to a PUR request message, a PUR response message from the base station indicating that the PUR request message is rejected, where the PUR response message indicates how the UE will proceed based on the rejected PUR request message. The operation of 2515 may be performed according to the methods described herein. In some examples, the manner of operation of 2515 may be performed by a PUR configuration manager as described with reference to FIGS. 10-13.

[0309] FIG. 26 shows a flowchart depicting a method 2600 for supporting PUR techniques in wireless communication according to aspects of the present disclosure. The operations of method 2600 may be implemented by base station 105 or its components as described herein. For example, the operations of method 2600 may be performed by a communication manager as described with reference to FIGS. 14-17. In some examples, the base station may execute a set of instructions for controlling the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

[0310] At 2605, the base station may transmit an indication that the base station supports PUR for grant-free uplink transmission. The operation of 2605 may be performed according to the methods described herein. In some examples, the manner of operation of 2605 may be performed by a PUR configuration manager as described with reference to FIGS. 14-17.

[0311] 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, the manner of operation of 2610 may be performed by a PUR request manager as described with reference to FIGS. 14-17.

[0312] At 2615, the base station may transmit to the UE a PUR configuration that identifies the PUR allocated to the UE in response to the PUR request message. The operations of 2615 may be performed according to the methods described herein. In some examples, aspects of the operations of 2615 may be performed by a PUR configuration manager as described with reference to FIGS. 14-17.

[0313] At 2620, the base station may receive a PUR configuration response from the UE via an uplink resource for the response message. The operations of 2620 may be performed according to the methods described herein. In some examples, aspects of the operations of 2620 may be performed by a PUR response manager as described with reference to FIGS. 14-17.

[0314] At 2625, the base station may transmit an uplink resource to the UE for the response message from the UE. The operations of 2625 may be performed according to the methods described herein. In some examples, aspects of the operations of 2625 may be performed by an undefined as described with reference to FIGS. 14-17.

[0315] FIG. 27 shows a flowchart illustrating a method 2700 for supporting PUR techniques in wireless communication according to aspects of the present disclosure. The operations of method 2700 may be implemented by 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-17. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

[0316] At 2705, the base station may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for the 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-17.

[0317] At 2710, the base station may receive a PUR request message from a 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-17.

[0318] 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-17.

[0319] FIG. 28 shows a flowchart illustrating a method 2800 for supporting a PUR technique in wireless communication according to an aspect of the present disclosure. The operations of method 2800 may be performed by 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-17. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

[0320] At 2805, the base station may transmit an indication that the base station supports PUR for grant-free uplink transmission. The operations of 2805 may be performed according to the methods described herein. In some examples, aspects of the operations of 2805 may be performed by a PUR configuration manager as described with reference to FIGS. 14 - 17.

[0321] At 2810, the base station may receive a PUR request message from a UE, where the PUR request message includes the number of instances of PUR grants requested by the UE. The operations of 2810 may be performed according to the methods described herein. In some examples, aspects of the operations of 2810 may be performed by a PUR request manager as described with reference to FIGS. 14 - 17.

[0322] At 2815, the base station may transmit a PUR configuration to the UE in response to the PUR request message. The operations of 2815 may be performed according to the methods described herein. In some examples, aspects of the operations of 2815 may be performed by a PUR configuration manager as described with reference to FIGS. 14 - 17.

[0323] FIG. 29 shows a flowchart illustrating a method 2900 for supporting PUR techniques in wireless communication according to an aspect of the present disclosure. The operations of method 2900 may be implemented by 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 - 17. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

[0324] 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 examples, the manner of operation of 2905 may be performed by a PUR configuration manager as described with reference to FIGS. 14-17.

[0325] At 2910, the base station may receive a PUR request message from a UE. The operation of 2910 may be performed according to the methods described herein. In some examples, the manner of operation of 2910 may be performed by a PUR request manager as described with reference to FIGS. 14-17.

[0326] At 2915, in response to the PUR request message, the base station may send a PUR response message to the UE indicating that the PUR request message is rejected, 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 examples, the manner of operation of 2915 may be performed by a PUR configuration manager as described with reference to FIGS. 14-17.

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

[0328] The techniques described herein can be used for various wireless communication systems such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. CDMA systems can implement wireless technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). CDMA2000 can cover the IS-2000 standard, IS-95 standard, and IS-856 standard. The IS-2000 release is often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA (registered trademark)) and other variants of CDMA. TDMA systems can implement wireless technologies such as the Global System for Mobile Communications (GSM).

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

[0330] Macro cells generally cover a relatively large geographical area (e.g., several kilometers in radius) and may enable unrestricted access by UEs subscribed to the network provider's service. Small cells are often associated with low-power base stations compared to macro cells, and small cells may operate in the same or a different frequency band than macro cells (e.g., licensed frequency band, unlicensed frequency band, etc.). Small cells may include, according to various examples, picocells, femtocells, and microcells. Picocells may cover, for example, a small geographical area and may enable unrestricted access by UEs subscribed to the network provider's service. Femtocells may also cover a small geographical area (e.g., a home) and may provide restricted access by UEs associated with the femtocell (e.g., UEs within a closed subscriber group (CSG), UEs for users within a home, etc.). The eNB for macro cells may sometimes be called a macro eNB. The eNB for small cells may sometimes be called 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.

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

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

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

[0334] The functions described in this specification may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementation forms are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described in this specification may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located at various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0335] A computer-readable medium includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. The non-transitory storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, 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 and disc include CD, laser disc, optical disc, DVD, floppy disk, and Blu-ray disc, where disk typically magnetically reproduces data and disc optically reproduces data using a laser. Combinations of the above are also included within the scope of computer-readable media.

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

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

[0338] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not represent all examples that may be implemented or fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples". The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques 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 examples being described.

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

Explanation of Reference Numerals

[0340] 100 Wireless communication system 105 Base station 110 Geographic coverage area 115 User equipment (UE) 125 Communication link 130 Core network 132, 134 Backhaul link 200 Wireless communication system 205 Downlink transmission 210 Uplink transmission 215 PUR indication 220 PUR allocation 225 PUR request 230 Uplink data 1005 Device 1010 Receiver 1015 Communication manager 1020 Transmitter 1105 Device 1110 Receiver 1115 Communication manager 1120 PUR decision component 1125 PUR request manager 1130 PUR configuration manager 1135 PUR transmission manager 1140 EDT random access manager 1145 Transmitter 1205 Communication manager 1210 PUR decision component 1215 PUR request manager 1220 PUR Configuration Manager 1225 PUR Transmission Manager 1230 EDT Random Access Manager 1235 PUR Response Manager 1240 Paging Manager 1245 RRC Manager 1250 PUR Permission Manager 1305 Device 1310 Communication Manager 1315 I / O Controller 1320 Transceiver 1325 Antenna 1330 Memory 1335 Computer Executable Code 1340 Processor 1345 Bus 1405 Device 1410 Receiver 1415 Communication Manager 1420 Transmitter 1505 Device 1510 Receiver 1515 Communication Manager 1520 PUR Configuration Manager 1525 PUR Request Manager 1530 PUR Response Manager 1535 EDT Random Access Manager 1540 Transmitter 1605 Communication Manager 1610 PUR Configuration Manager 1615 PUR Request Manager 1620 PUR Response Manager 1625 EDT Random Access Manager 1630 Paging Manager 1635 PUR Permission Manager 1705 Device 1710 Communication Manager 1715 Network Communication Manager 1720 Transceiver 1725 Antenna 1730 Memory 1735 Computer-readable code 1740 Processor 1745 Inter-station communication manager 1750 Bus

Claims

1. A method for wireless communication in a user equipment (UE), comprising: transmitting, to the base station, a preconfigured uplink resource request message based at least in part on a determination that the base station supports preconfigured uplink resources, the preconfigured uplink resource request message including the number of instances of preconfigured uplink resource grants requested by the UE; receiving, from the base station, a message indicating configuration or reconfiguration or release of the preconfigured uplink resources; and A method comprising the steps of.

2. The method of claim 1, wherein 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.

3. The method of claim 1, wherein the number of instances of preconfigured uplink resource (PUR) grants requested by the UE indicates that a one-shot PUR configuration is requested or that a multi-shot PUR configuration is requested.

4. The method of claim 1, wherein the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference from a previous preconfigured uplink resource configuration of the UE.

5. The method of claim 1, wherein the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference from a default preconfigured uplink resource configuration or a difference from a configuration being used in the UE.

6. After receiving the preconfigured uplink resource (PUR) configuration, transmitting a PUR reconfiguration failure indication to the base station; and releasing the PUR configuration. The method of claim 1, further comprising the steps of.

7. determining, based at least in part on the message from the base station, a set of control channel resources to monitor for uplink grants; and monitoring the set of control channel resources for uplink grants, wherein the uplink grants indicate uplink resources for transmitting a preconfigured uplink resource configuration response message to the base station. The method of claim 1.

8. Determining that a PUR configuration is to be deconfigured, based at least in part on receiving from the base station broadcast system information indicating that a preconfigured uplink resource (PUR) is not supported; Releasing the PUR configuration; The method according to claim 1, further comprising. **Claim 9** The method according to claim 1, wherein the preconfigured uplink resource request message is transmitted to the base station in an uplink message of an early data transmission (EDT) procedure. **Claim 10** Further comprising formatting the uplink resource request message to be transmitted in the uplink message of the EDT procedure, wherein the uplink resource request message indicates a requested configuration, reconfiguration, or release of a preconfigured uplink resource configuration. The method according to claim 9. **Claim 11** The method according to claim 9, wherein the uplink resource request message is transmitted in a transmission of message 3 (MSG3) of the EDT procedure. **Claim 12** The method according to claim 1, wherein the message from the base station indicating a configuration or reconfiguration or release of the UE's preconfigured uplink resource is received in an early data transmission (EDT) downlink message 4 that provides a radio resource control (RRC) connection release message or an RRC early data completion message. **Claim 13** The method according to claim 1, wherein the message from the base station explicitly or implicitly provides one or more of an indication that the UE is to use a previous preconfigured uplink resource (PUR) configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration is to be deconfigured and released, new resources for a new PUR configuration, or any combination thereof. **Claim 14** A method for wireless communication in a user equipment (UE), comprising: Determining an early data transmission configuration for an early data transmission procedure; Transmitting an uplink message of the early data transmission procedure to a base station; Receiving from the base station, in a downlink message of the early data transmission procedure, a message indicating a configuration or reconfiguration or release of a preconfigured uplink resource configuration. A method comprising...

15. Formatting a pre-configured uplink resource request message to be transmitted within the uplink message of the early data transmission procedure, wherein the pre-configured uplink resource request message indicates a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration; Transmitting the pre-configured uplink resource request message within the uplink message of the early data transmission procedure; The method according to claim 14, further comprising...

16. Determining a set of control channel resources to be monitored for an uplink grant, at least partially based on the pre-configured uplink resource (PUR) configuration message from the base station; Further comprising monitoring the set of control channel resources for the uplink grant, wherein the uplink grant indicates uplink resources for transmitting a PUR configuration response message to the base station; The method according to claim 14.

17. The method according to claim 14, wherein the uplink message of the early data transmission procedure is transmitted during the transmission of Message 3 (MSG3) of the early data transmission procedure.

18. The method according to claim 14, wherein the message from the base station indicating a configuration, reconfiguration, or release of a pre-configured uplink resource is received within an early data transmission (EDT) downlink message 4 that provides a radio resource control (RRC) connection release message or an RRC early data completion message.

19. The method according to claim 18, wherein the PUR configuration is provided as a delta configuration indicating a difference from a previous PUR configuration of the UE.

20. The method according to claim 18, wherein the PUR configuration is provided as a delta configuration indicating a difference from a default PUR configuration or a difference from a configuration being used in the UE.

21. The method according to claim 18, wherein the EDT message 4 explicitly or implicitly provides one or more of an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration is to be deconfigured and released, new resources for a new PUR configuration, or any combination thereof.

22. The method according to claim 14, further comprising transmitting an indication of a successful PUR configuration or a PUR configuration failure using an uplink resource for a response message from the UE in response to the preconfigured uplink resource (PUR) configuration message.

23. Determining that a PUR configuration is to be deconfigured, at least in part based on receiving broadcast system information from the base station indicating that a preconfigured uplink resource (PUR) is not supported; and Releasing the PUR configuration. The method according to claim 14, further comprising.

24. Receiving a preconfigured uplink resource (PUR) release message from the base station; and Deconfiguring the PUR configuration, at least in part based on the PUR release message. The method according to claim 14, further comprising.

25. The method according to claim 14, further comprising 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 preconfigured uplink resource (PUR) grants provides an indication of an explicit number of PUR grants or an infinite number of PUR grants.

26. A method for wireless communication in a user equipment (UE), the method comprising: Receiving, from a base station, a radio resource configuration connection release message or a radio resource configuration early data completion message providing a preconfigured uplink resource configuration, the preconfigured uplink resource configuration indicating the number of instances of preconfigured uplink resource grants for the UE; and Transmitting one or more uplink communications to the base station, at least in part based on the preconfigured uplink resource configuration. A method comprising. ​ ​

27. The method according to claim 26, wherein the number of instances of preconfigured uplink resource (PUR) grants provides an indication of an explicit number of PUR grants or an infinite number of PUR grants.

28. The method according to claim 26, further comprising transmitting a preconfigured uplink resource (PUR) request message to the base station, at least partially based on a determination that the base station supports preconfigured uplink resources before reception, wherein the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE. The method according to claim 26.

29. The method according to claim 28, wherein the PUR request message is transmitted to the base station within an uplink message of an early data transmission (EDT) procedure.

30. The method according to claim 29, wherein the uplink resource request message is transmitted during message 3 (MSG3) transmission of the EDT procedure.

31. The method according to claim 26, wherein the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference from a previous preconfigured uplink resource configuration of the UE, a difference from a default preconfigured uplink resource configuration, or a difference from a configuration used in the UE.

32. An apparatus for wireless communication in a user equipment (UE), comprising: means for transmitting a preconfigured uplink resource (PUR) request message to the base station, at least partially 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; and means for receiving a message from the base station indicating a configuration or reconfiguration or release of preconfigured uplink resources. The apparatus comprising.

33. The apparatus according to claim 32, wherein the number of instances of preconfigured uplink resource (PUR) grants provides an indication of an explicit number of PUR grants or an infinite number of PUR grants.

34. The apparatus according to claim 32, wherein the pre-configured uplink resource configuration is provided as a delta configuration indicating a difference exceeding the previous pre-configured uplink resource configuration of the UE, a difference exceeding a default pre-configured uplink resource configuration, or a difference exceeding the configuration used in the UE.

35. Means for transmitting a PUR reconfiguration failure indication to the base station after receiving the pre-configured uplink resource (PUR) configuration; Means for releasing the PUR configuration The apparatus according to claim 32, further comprising.

36. Means for determining, at least in part based on the message from the base station, a set of control channel resources to monitor for an uplink grant; Further comprising means for monitoring the set of control channel resources for an uplink grant, wherein the uplink grant indicates uplink resources for transmitting a pre-configured uplink resource configuration response message to the base station. The apparatus according to claim 32.

37. Means for determining that a PUR configuration is to be deconfigured, at least in part based on receiving broadcast system information transmission from the base station indicating that pre-configured uplink resources (PUR) are not supported; Means for releasing the PUR configuration The apparatus according to claim 32, further comprising.

38. The apparatus according to claim 32, wherein the pre-configured uplink resource request message is transmitted to the base station in an uplink message of an early data transmission (EDT) procedure.

39. Further comprising means for formatting the uplink resource request message to be transmitted in the uplink message of the EDT procedure, wherein the uplink resource request message indicates a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration. The apparatus according to claim 38.

40. The apparatus according to claim 38, wherein the uplink resource request message is transmitted in message 3 (MSG3) transmission of the EDT procedure.

41. The apparatus according to claim 32, wherein the message from the base station indicating the configuration, reconfiguration, or release of the preconfigured uplink resource is received in an early data transmission (EDT) downlink message 4 that provides a radio resource control (RRC) connection release message or an RRC early data completion message.

42. An apparatus for wireless communication in a user equipment (UE), comprising: means for determining an early data transmission configuration for an early data transmission procedure; means for transmitting an uplink message of the early data transmission procedure to a base station; means for receiving, from the base station, a message indicating the configuration, reconfiguration, or release of a preconfigured uplink resource configuration in a downlink message of the early data transmission procedure. The apparatus comprising the above.

43. means for formatting a preconfigured uplink resource request message to be transmitted in the uplink message of the early data transmission procedure, the preconfigured uplink resource request message indicating a requested configuration, reconfiguration, or release of a preconfigured uplink resource; means for transmitting the preconfigured uplink resource request message in the uplink message of the early data transmission procedure. The apparatus according to claim 42, further comprising the above.

44. means for determining, at least in part based on the preconfigured uplink resource (PUR) configuration message from the base station, a set of control channel resources to monitor for an uplink grant; means for monitoring the set of control channel resources for the uplink grant, the uplink grant indicating uplink resources for transmitting a PUR configuration response message to the base station. The apparatus according to claim 42.

45. The apparatus according to claim 42, wherein the uplink message of the early data transmission procedure is transmitted in a transmission of message 3 (MSG3) of the early data transmission procedure.

46. The apparatus according to claim 42, wherein the message from the base station indicating configuration, reconfiguration, or release of a preconfigured uplink resource is received in an early data transmission (EDT) downlink message 4 that provides a radio resource control (RRC) connection release message or an RRC early data completion message.

47. The apparatus according to claim 46, wherein the PUR configuration is provided as a delta configuration indicating a difference exceeding the UE's previous PUR configuration, a difference exceeding a default PUR configuration, or a difference exceeding the configuration used in the UE.

48. The apparatus according to claim 46, wherein the EDT message 4 explicitly or implicitly provides one or more of an indication that the UE is to use a previous PUR configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration should be deconfigured and released, new resources for a new PUR configuration, or any combination thereof.

49. Means for transmitting an indication of successful PUR configuration or PUR configuration failure using an uplink resource for a response message from the UE in response to the preconfigured uplink resource (PUR) configuration message The apparatus according to claim 42, further comprising.

50. Means for determining that the PUR configuration is to be deconfigured, based at least in part on receiving broadcast system information transmission from the base station indicating that preconfigured uplink resources (PURs) are not supported; and Means for releasing the PUR configuration The apparatus according to claim 42, further comprising.

51. Means for receiving a preconfigured uplink resource (PUR) release message from the base station; and Means for deconfiguring the PUR configuration based at least in part on the PUR release message The apparatus according to claim 42, further comprising.

52. Means 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. The apparatus according to claim 42. **Claim 53** An apparatus for wireless communication in a user equipment (UE), Means for receiving from a base station a radio resource configuration connection release message or a radio resource configuration early data completion message providing a preconfigured uplink resource configuration, wherein the preconfigured uplink resource configuration indicates the number of instances of preconfigured uplink resource grants for the UE. Means for transmitting one or more uplink communications to the base station based at least in part on the preconfigured uplink resource configuration An apparatus comprising. **Claim 54** The apparatus according to claim 53, 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. **Claim 55** Further comprising means for transmitting a preconfigured uplink resource (PUR) request message to the base station based at least in part on a determination that the base station supports preconfigured uplink resources prior to receiving, wherein the preconfigured uplink resource request message includes the number of instances of preconfigured uplink resource grants requested by the UE. The apparatus according to claim 53. **Claim 56** The apparatus according to claim 55, wherein the PUR request message is transmitted to the base station within an uplink message of an early data transmission (EDT) procedure. **Claim 57** The apparatus according to claim 53, wherein the preconfigured uplink resource configuration is provided as a delta configuration indicating a difference over a previous preconfigured uplink resource configuration of the UE, a difference over a default preconfigured uplink resource configuration, or a difference over a configuration being used in the UE.

Images