Pre-configured 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, by Phuyal et al., entitled "Preconfigured Uplink Resource Techniques in Wireless Communications," each of which has been assigned to the assignee of this 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, including voice, video, packet data, messaging, and broadcast. These systems may support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE) systems, 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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may sometimes be referred to as user equipment (UEs).

[0004] In some cases, a UE may have only a relatively small amount of data to be transmitted periodically. For example, a UE may be associated with a sensor that periodically provides readings to network nodes. In some cases, to obtain uplink resources for uplink transmission, a UE may send a request for uplink data resources (for example, a buffer status report (BSR) indicating that the UE has data to transmit may be provided to the base station), receive uplink permission in response to the request, and then transmit uplink data in accordance with the uplink permission. If the UE has only a relatively small amount of data to transmit, such a procedure consumes a significant amount of overhead compared to the amount of data being transmitted. Efficient techniques for allocating uplink resources to UEs for "grant-free" uplink transmissions (i.e., not requiring multi-step communication just to obtain uplink permission each time) can enable more efficient network operation through such uplink resource allocation and reduced overhead associated with such uplink transmissions. [Overview of the project] [Means for solving the problem]

[0005] The techniques described relate to improved methods, systems, devices, and apparatus for supporting preconfigured uplink resources (PURs) in wireless communications. The various techniques described involve communicating that support for PURs is available at a base station and allocating PUR resources to a user equipment (UE) based on a request from the UE. The UE may receive an indication that the base station supports PURs, such as through a system information block (SIB), decide to request a PUR, and send a PUR request message to the base station. The PUR response from the base station may indicate a PUR allocation for the UE that can be used for uplink transmission.

[0006] In some cases, the base station may provide a PUR allocation different from the requested PUR configuration provided by the UE in the time of the PUR request. The UE may determine that the different PUR configuration is insufficient for it and may send a PUR configuration failure to the base station. In some cases, a transmission from the base station to the UE indicating a 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 by the base station to send a 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. As an addition or alternative, a PUR request from the UE requesting a PUR configuration or PUR reconfiguration may provide an indication of the number of instances of the requested PUR authorization. Such a PUR request may indicate a PUR release request by indicating the number of instances of the PUR authorization as 0. In addition or alternatively, the base station may determine that the requested PUR configuration or PUR reconfiguration is not available to the UE and send a PUR rejection notice to the UE. The rejection notice may also indicate, in the case of a PUR reconfiguration request, how the UE will handle the existing PUR configuration (for example, whether to release the existing PUR configuration or to retain the existing PUR configuration).

[0007] A method for wireless communication at a UE is described. The method may include: the base station deciding to support a pre-configured uplink resource for a grant-free uplink transmission from the UE; the base station sending a pre-configured uplink resource request message to the base station based on the decision to support the pre-configured uplink resource; the base station receiving a pre-configured uplink resource configuration from the base station in response to the pre-configured uplink resource request message, identifying the pre-configured uplink resource allocated to the UE; the base station receiving an uplink resource for a response message to be transmitted from the UE; and the base station sending a pre-configured uplink resource configuration response message to the base station using the uplink resource for the response message.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: decide that the base station will support a pre-configured uplink resource for grant-free uplink transmissions from the UE; send a pre-configured uplink resource request message to the base station based on the decision that the base station will support the pre-configured uplink resource; receive a pre-configured uplink resource configuration from the base station in response to the pre-configured uplink resource request message, identifying the pre-configured uplink resource allocated to the UE; receive an uplink resource for a response message to be sent from the UE; and send a pre-configured uplink resource configuration response message to the base station using the uplink resource for the response message.

[0009] Another device for wireless communication at a UE is described. The device may include means for determining that a base station will support a pre-configured uplink resource for grant-free uplink transmissions from the UE; transmitting a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource; receiving a pre-configured uplink resource configuration from the base station in response to the pre-configured uplink resource request message, identifying the pre-configured uplink resource allocated to the UE; receiving uplink resources for a response message to be transmitted from the UE; and transmitting a pre-configured uplink resource configuration response message to the base station using the uplink resources for the response message.

[0010] A non-temporary, computer-readable medium for storing code for wireless communications at a UE is described. The code may include instructions executable by a processor for: determining that a base station will support a pre-configured uplink resource for a grant-free uplink transmission from the UE; sending a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource; receiving a pre-configured uplink resource configuration from the base station in response to the pre-configured uplink resource request message, identifying the pre-configured uplink resource allocated to the UE; receiving an uplink resource for a response message to be sent from the UE; and sending a pre-configured uplink resource configuration response message to the base station using the uplink resource for the response message.

[0011] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the pre-configured uplink resource configuration may be provided as a delta configuration showing a difference over the UE's previous pre-configured uplink resource configuration. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the pre-configured uplink resource configuration may be provided as a delta configuration showing a difference over the current configuration used by the UE. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the pre-configured uplink resource configuration may be provided as a delta configuration showing a difference over the default pre-configured uplink resource configuration.

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

[0013] Some examples of the methods, apparatus, and non-transient computer-readable media described herein may further include operations, features, means, or instructions for determining, based on a pre-configured uplink resource (PUR) configuration from a base station, a set of control channel resources to be monitored for uplink permission, where uplink permission indicates an uplink resource for sending a PUR configuration response message to the base station. In some examples of the methods, apparatus, and non-transient computer-readable media described herein, the pre-configured 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, apparatus, and non-transient computer-readable media described herein, sending a pre-configured uplink resource configuration response message may be performed when the UE is in idle mode or in connected mode with a base station.

[0014] A method for wireless communication at the UE is described. The method may include determining an early data transmission configuration for the early data transmission procedure for transmitting UE payload data in an uplink message of the early data transmission procedure. In some cases, the uplink message may include a pre-configured uplink resource request message indicating the requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration. The method may further include transmitting an uplink message of the early data transmission procedure and receiving a message from the base station in a downlink message of the early data transmission procedure indicating the configuration, reconfiguration, or release of a pre-configured uplink resource configuration.

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

[0016] Another device for wireless communications in a UE is described. The device 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 a message from a base station in the downlink message for the early data transmission procedure indicating the configuration, reconfiguration, or release of a pre-configured uplink resource configuration.

[0017] A non-temporary, computer-readable medium for storing code for wireless communications in a UE is described. The code may include instructions executable by a processor 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 a message from a base station in the downlink message for the early data transmission procedure indicating the configuration, reconfiguration, or release of a pre-configured uplink resource configuration.

[0018] Some examples of methods, apparatus, and non-temporary computer-readable media described herein involve formatting a pre-configured uplink resource request message to be transmitted in an uplink message of an early data transmission procedure, which may further include operations, features, means, or instructions for the pre-configured uplink resource request message to indicate a requested configuration, reconfiguration, or release of a pre-configured uplink resource configuration, and for transmitting the pre-configured uplink resource request message in an uplink message of an early data transmission procedure.

[0019] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining, based on pre-configured uplink resource (PUR) configuration messages from a base station, a set of control channel resources to be monitored for uplink permission, where uplink permission refers to an uplink resource for sending a PUR configuration response message to a base station.

[0020] In some examples of the methods, apparatus, and non-temporary 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, apparatus, and non-temporary computer-readable media described herein, the Pre-configured Uplink Resource (PUR) configuration message from the base station is received within the Early Data Transmission (EDT) downlink message 4, which provides an RRC connection release message or an RRC Early Data Complete message. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the PUR configuration is provided as a delta configuration that shows a difference over the UE's previous PUR configuration. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the PUR configuration is provided as a delta configuration that shows a difference over the default PUR configuration or a difference over the configuration used in the UE. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the EDT message 4 explicitly or implicitly provides one or more of the following: an indication that the UE will use a previous PUR configuration, 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.

[0021] Some examples of methods, apparatus, and non-temporary 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 in response to a pre-configured uplink resource (PUR) configuration message, using the uplink resource for a response message from the UE. Some examples of methods, apparatus, and non-temporary 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 a broadcast system information transmission from a base station indicating that PUR may not be supported. Some examples of methods, apparatus, and non-temporary 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 the PUR configuration based on the PUR release message.

[0022] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for formatting a pre-configured uplink resource request message indicating the number of instances of pre-configured uplink resource authorizations requested by a UE to be transmitted to a base station, wherein the number of instances of pre-configured uplink resource (PUR) authorizations provides an indication of an explicit number of PUR authorizations or an infinite number of PUR authorizations.

[0023] A method of wireless communication at a UE is described. The method involves the base station deciding to support a pre-configured uplink resource in response to a grant-free uplink transmission from the UE, and the base station sending a pre-configured uplink resource request message to the base station based on the decision to support the pre-configured uplink resource, which may include the number of instances of pre-configured uplink resource permission requested by the UE, and receiving a pre-configured uplink resource configuration from the base station.

[0024] A device for wireless communication in a UE is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to decide that a base station will support a pre-configured uplink resource for grant-free uplink transmissions from the UE, and to send a pre-configured uplink resource request message to the base station based on the decision that the base station will support the pre-configured uplink resource, wherein the pre-configured uplink resource request message includes the number of instances of pre-configured uplink resource permission requested by the UE, and to receive a pre-configured uplink resource configuration from the base station.

[0025] Another device for wireless communication at a UE is described. The device involves a base station deciding to support a pre-configured uplink resource for a grant-free uplink transmission from the UE, and transmitting a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource, wherein the pre-configured uplink resource request message includes the number of instances of pre-configured uplink resource permission requested by the UE, and means for receiving a pre-configured uplink resource configuration from the base station.

[0026] A non - transient computer - readable medium storing code for wireless communication in a UE is described. The code causes a processor to determine that a base station supports pre - configured uplink resources for grant - free uplink transmission from the UE, and to transmit a pre - configured uplink resource request message to the base station based on the determination that the base station supports pre - configured uplink resources, where the pre - configured uplink resource request message includes the number of instances of pre - configured uplink resource grants requested by the UE, and to receive a pre - configured 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 - transient computer - readable media described herein, the number of instances of pre - configured 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 - transient computer - readable media described herein, the number of instances of pre - configured 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 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 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 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 transmission from a base station indicating that preconfigured uplink resources (PURs) may not be supported and releasing the PUR configuration.

[0030] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured uplink resource request message may be transmitted to the base station within an uplink message of an Early Data Transmission (EDT) procedure. Some examples of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for formatting an uplink resource request message so that it is 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, apparatus, and non-temporary computer-readable media described herein, an uplink resource request message is transmitted within a message 3 (MSG3) transmission of the EDT procedure. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a message from the base station indicating a UE's pre-configured uplink resource is received within an Early Data Transmission (EDT) downlink message 4 providing an RRC connection release message or an RRC early data completion message. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a message from the base station explicitly or implicitly provides one or more of the following: an indication that the UE will use a previous pre-configured uplink resource (PUR) configuration, a confirmation of the previous PUR configuration, an indication that the previous PUR configuration should be deconfigured and released, a new resource for a new PUR configuration, or any combination thereof.

[0032] A method for wireless communication in a UE is described. The method involves receiving a radio resource configuration connection release message or a radio resource configuration early data completion message from a base station that provides a pre-configured uplink resource configuration, wherein the pre-configured uplink resource configuration indicates the number of instances of pre-configured uplink resource permission for the UE, and transmitting one or more uplink communications to the base station based on the pre-configured uplink resource configuration.

[0033] A device for wireless communications in a UE is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the device to receive a radio resource configuration connection release message or a radio resource configuration early data completion message from a base station, where the pre-configured uplink resource configuration indicates the number of instances of pre-configured uplink resource permission for the UE, and to transmit one or more uplink communications to the base station based on the pre-configured uplink resource configuration.

[0034] Another device for wireless communications at a UE is described. The device receives from a base station a radio resource configuration connection release message or a radio resource configuration early data completion message that provides a pre-configured uplink resource configuration, which may include means for indicating the number of instances of pre-configured uplink resource permission for the UE and for transmitting one or more uplink communications to the base station based on the pre-configured uplink resource configuration.

[0035] A non-temporary, computer-readable medium for storing code for wireless communications in a UE is described. The code includes receiving a radio resource configuration connection release message or a radio resource configuration early data completion message from a base station that provides a pre-configured uplink resource configuration, which may include instructions executable by a processor to indicate the number of instances of pre-configured uplink resource permission for the UE and to transmit one or more uplink communications to the base station based on the pre-configured uplink resource configuration.

[0036] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the number of instances of a PUR authorization provides an indication of an explicit number of PUR authorizations or an infinite number of PUR authorizations. Some examples of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for sending a PUR request message to a base station based on the base station's decision to support a pre-configured uplink resource before it is received, wherein the pre-configured uplink resource request message includes the number of instances of a pre-configured uplink resource authorization requested by the UE.

[0037] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the PUR request message is transmitted to the base station within the uplink message of the EDT procedure. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the uplink resource request message may be transmitted within the MSG3 transmission of the EDT procedure. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the pre-configured uplink resource configuration is provided as a delta configuration that represents a difference over the UE's previous pre-configured uplink resource configuration, a difference over the default pre-configured uplink resource configuration, or a difference over the configuration used in the UE.

[0038] A method of wireless communication at a UE is described. The method may include: the base station deciding to support a pre-configured uplink resource in response to a grant-free uplink transmission from the UE; the base station sending a pre-configured uplink resource request message to the base station based on the decision to support the pre-configured uplink resource; and the base station receiving a pre-configured uplink resource response message from the base station in response to the pre-configured uplink resource request message, indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0039] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to decide that a base station will support a pre-configured uplink resource for a grant-free uplink transmission from the UE, to send a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource, and to receive a pre-configured uplink resource response message from the base station in response to the pre-configured uplink resource request message, indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0040] Another apparatus for wireless communications at a UE is described. The apparatus may include means for a base station to decide whether to support a pre-configured uplink resource for a grant-free uplink transmission from the UE, for the base station to send a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource, and for the base station to receive a pre-configured uplink resource response message from the base station in response to the pre-configured uplink resource request message, indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0041] A non-temporary, computer-readable medium for storing code for wireless communications in a UE is described. The code may include instructions executable by a processor to: determine that a base station will support a pre-configured uplink resource for a grant-free uplink transmission from the UE; send a pre-configured uplink resource request message to the base station based on the base station's decision to support the pre-configured uplink resource; and receive a pre-configured uplink resource response message from the base station in response to the pre-configured uplink resource request message, indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0042] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is requested, where a PUR response message indicates that the previous PUR configuration will be released by the UE. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is requested, where a PUR response message indicates that the previous PUR configuration will be maintained by the UE.

[0043] A method for wireless communication at a base station is described. The method may include: the base station transmitting an indication that it supports a pre-configured uplink resource in response to a grant-free uplink transmission; receiving a pre-configured uplink resource request message from the UE; transmitting a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message, identifying the pre-configured uplink resource allocated to the UE; transmitting an uplink resource to the UE for a response message from the UE; and receiving a pre-configured uplink resource configuration response from the UE via the uplink resource for the response message.

[0044] A device for wireless communication at a base station is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. Instructions may be executable by the processor to cause the device to transmit an indication that the base station supports a pre-configured uplink resource for grant-free uplink transmissions, to receive a pre-configured uplink resource request message from the UE, to send a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message, to send an uplink resource to the UE for a response message from the UE, and to receive a pre-configured uplink resource configuration response from the UE via the uplink resource for the response message.

[0045] Another device for wireless communication at a base station is described. The device may include means for transmitting an indication that the base station supports a pre-configured uplink resource for a grant-free uplink transmission; receiving a pre-configured uplink resource request message from the UE; transmitting a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message, identifying a pre-configured uplink resource allocated to the UE; transmitting an uplink resource to the UE for a response message from the UE; and receiving a pre-configured uplink resource configuration response from the UE via the uplink resource for the response message.

[0046] A non-temporary, computer-readable medium for storing code for wireless communications at a base station is described. The code may include instructions executable by a processor for: transmitting an indication that the base station supports a pre-configured uplink resource for a grant-free uplink transmission; receiving a pre-configured uplink resource request message from a UE; transmitting a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message, identifying a pre-configured uplink resource allocated to the UE; transmitting an uplink resource to the UE for a response message from the UE; and receiving a pre-configured uplink resource configuration response from the UE via the uplink resource for the response message.

[0047] In some examples of the methods, apparatus, and non-transient computer-readable media described herein, the pre-configured uplink resource configuration may be provided as a delta configuration showing a difference over the UE's previous pre-configured uplink resource configuration, the current configuration used by the UE, or the default pre-configured uplink resource configuration. In some examples of the methods, apparatus, and non-transient computer-readable media described herein, the uplink resources for the response message may be provided in an explicit indication from the base station having the pre-configured uplink resource configuration. In some examples of the methods, apparatus, and non-transient 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, apparatus, and non-transient computer-readable media described herein, a pre-configured uplink resource configuration failure indication may be transmitted when the UE is in idle mode or in connection mode with the base station.

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

[0049] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory. 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 sending a pre-configured uplink resource request message, wherein the early data transmission configuration provides uplink transmission of UE payload data in the uplink message of the early data transmission procedure, and to receive a pre-configured uplink resource request message from the UE in the uplink message of the early data transmission procedure, wherein the pre-configured uplink resource request message indicates the requested configuration, reconfiguration, or release of the pre-configured uplink resource configuration, and to send a pre-configured uplink resource configuration message to the UE in response to the pre-configured uplink resource request message, wherein the pre-configured uplink resource configuration indicates the uplink resource for the response message from the UE.

[0050] Another device for wireless communication at a base station is described. The device may include means for determining an early data transmission configuration for an early data transmission procedure available for transmitting a pre-configured uplink resource request message, wherein the early data transmission configuration provides uplink transmission of UE payload data in the uplink message of the early data transmission procedure; receiving a pre-configured uplink resource request message from the UE in the uplink message of the early data transmission procedure, wherein the pre-configured uplink resource request message indicates the requested configuration, reconfiguration, or release of the 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, wherein the pre-configured uplink resource configuration indicates the uplink resource for the response message from the UE.

[0051] A non-temporary computer-readable medium for storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to determine an early data transmission configuration for an early data transmission procedure available for sending a pre-configured uplink resource request message, wherein the early data transmission configuration provides uplink transmission of UE payload data in the uplink message of the early data transmission procedure; receive a pre-configured uplink resource request message from the UE in the uplink message of the early data transmission procedure, wherein the pre-configured uplink resource request message indicates the requested configuration, reconfiguration, or release of the pre-configured uplink resource configuration; and send a pre-configured uplink resource configuration message to the UE in response to the pre-configured uplink resource request message, wherein the pre-configured uplink resource configuration indicates the uplink resource for a response message from the UE.

[0052] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication that an uplink message of an early data transmission procedure is available for a pre-configured uplink resource request message. In some examples of methods, apparatus, and non-temporary computer-readable media described herein, the indication may be transmitted within a system information block broadcast from a base station.

[0053] In some examples of the methods, apparatus, and non-temporary 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 used in the UE. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, operations, features, means, or instructions for receiving an indication of a successful PUR configuration or a PUR configuration failure in response to a pre-configured uplink resource (PUR) configuration message, using an uplink resource for a response message from the UE.

[0054] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured 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, apparatus, and non-temporary computer-readable media described herein, the EDT Early Data Completion message explicitly or implicitly provides one or more of the following: an indication that the UE will use a previous PUR configuration, confirmation of the previous PUR configuration, an indication that the previous PUR configuration should be deconfigured and released, a new resource for the new PUR configuration, or any combination thereof. In some examples of the methods, apparatus, and non-temporary 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 methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting a broadcast system information transmission indicating that PUR is not supported and that the UE will release the PUR configuration. Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining that the UE's PUR configuration will be reconfigured or released, sending a page message to the UE, receiving a random access request message from the UE in response to the page message, and transmitting an indication in response to the random access request message that the PUR configuration should be reconfigured or released.

[0056] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, 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. Some examples of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for sending a pre-configured uplink resource (PUR) release message to the UE and for deconfiguring the PUR configuration based on the PUR release message. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the PUR release message may be sent while the UE is in connected mode or in an EDT random access response message, where the PUR release message is a radio resource control (RRC) PUR reconfiguration message.

[0057] A method for wireless communication at a base station is described. The method includes the base station sending an indication that it supports a pre-configured uplink resource in response to a grant-free uplink transmission, and receiving a pre-configured uplink resource request message from the UE, which may include the number of instances of pre-configured uplink resource permission requested by the UE, and the base station sending a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message.

[0058] A device for wireless communication at a base station is described. The device may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to transmit an indication that the base station supports a pre-configured uplink resource for grant-free uplink transmissions, and to receive a pre-configured uplink resource request message from the UE, wherein the pre-configured uplink resource request message includes the number of instances of pre-configured uplink resource permission requested by the UE, and to transmit a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message.

[0059] Another device for wireless communication at a base station is described. The device includes means for transmitting an indication that the base station supports a pre-configured uplink resource in response to a grant-free uplink transmission, and for receiving a pre-configured uplink resource request message from the UE, wherein the pre-configured uplink resource request message includes the number of instances of pre-configured uplink resource permission requested by the UE, and for transmitting a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message.

[0060] A non-temporary, computer-readable medium for storing code for wireless communication at a base station is described. The code includes instructions that the base station transmits an indication that it supports a pre-configured uplink resource in response to a grant-free uplink transmission, and instructions that the base station receives a pre-configured uplink resource request message from a UE, the pre-configured uplink resource request message including the number of instances of pre-configured uplink resource permission requested by the UE, and instructions that the base station transmits a pre-configured uplink resource configuration to the UE in response to the pre-configured uplink resource request message.

[0061] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the number of instances of a pre-configured uplink resource authorization provides an indication of an explicit or indeterminate number of PUR authorizations. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a number of instances that is 0 indicates that a pre-configured uplink resource configuration will be released. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the number of instances of a pre-configured uplink resource (PUR) authorization requested by the UE indicates that a one-shot PUR configuration is requested or a multi-shot PUR configuration is requested.

[0062] A method of wireless communication at a base station is described. The method may include the base station sending an indication that it supports a pre-configured uplink resource in response to a grant-free uplink transmission, receiving a pre-configured uplink resource request message from the UE, and sending a pre-configured uplink resource response message to the UE in response to the pre-configured uplink resource request message, indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0063] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, 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 a pre-configured uplink resource for a grant-free uplink transmission, to receive a pre-configured uplink resource request message from the UE, and to send a pre-configured uplink resource response message to the UE in response to the pre-configured uplink resource request message indicating that the pre-configured uplink resource request message is rejected, where the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

[0064] Another device for wireless communication at a base station is described. The device may include means for transmitting an indication that the base station supports a pre-configured uplink resource for a grant-free uplink transmission, receiving a pre-configured uplink resource request message from the UE, and transmitting a pre-configured uplink resource response message to the UE in response to the pre-configured uplink resource request message indicating that the pre-configured uplink resource request message is rejected, wherein the pre-configured uplink resource response message indicates how the UE will proceed based on the rejected pre-configured uplink resource request message.

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

[0066] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is requested, where a PUR response message indicates that the previous PUR configuration will be released by the UE. In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a pre-configured uplink resource (PUR) request message indicates that a reconfiguration of a previous PUR configuration is requested, where a PUR response message indicates that the previous PUR configuration will be maintained by the UE. [Brief explanation of the drawing]

[0067] [Figure 1] This figure shows an example of a system for wireless communications that supports pre-configured uplink resource (PUR) techniques in wireless communications, according to aspects of this disclosure. [Figure 2] This figure shows an example of a part of a wireless communication system that supports the PUR technique in wireless communication according to the aspects of this disclosure. [Figure 3] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 4] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 5] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 6] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 7] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 8] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 9] This figure shows an example of a process flow supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 10] This is a block diagram of a device supporting the PUR technique in wireless communications according to the embodiments of this disclosure. [Figure 11] This is a block diagram of a device supporting the PUR technique in wireless communications according to the embodiments of this disclosure. [Figure 12] This is a block diagram of a communication manager supporting the PUR technique in wireless communication according to the aspects of this disclosure. [Figure 13] This is a diagram of a system including a device that supports the PUR technique in wireless communications, according to an aspect of this disclosure. [Figure 14] This is a block diagram of a device supporting the PUR technique in wireless communications according to the embodiments of this disclosure. [Figure 15] This is a block diagram of a device supporting the PUR technique in wireless communications according to the embodiments of this disclosure. [Figure 16] This is a block diagram of a communication manager supporting the PUR technique in wireless communication according to the aspects of this disclosure. [Figure 17]This is a diagram of a system including a device that supports the PUR technique in wireless communications, according to an aspect of this disclosure. [Figure 18] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 19] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 20] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 21] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 22] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 23] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 24] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 25] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 26] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 27] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 28] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Figure 29] This flowchart shows a method for supporting the PUR technique in wireless communications according to the aspects of this disclosure. [Modes for carrying out the invention]

[0068] Various aspects of this disclosure provide improved methods, systems, devices, and apparatus for signaling and configuring pre-configured uplink resources (PURs). The various techniques described communicate that a PUR resource is available at a base station, for example, by transmitting a System Information Block (SIB) indicating support for the PUR. A UE may receive an indication of support for the PUR and decide to request the PUR resource from the base station (for example, based on uplink data to be transmitted to the base station). The UE may, in some cases, send a PUR request message requesting the PUR resource. A base station may receive a PUR request message and decide whether to allocate the PUR resource to the UE. If the base station decides to allocate the PUR resource to the UE, it may send a PUR response with a PUR allocation to the UE, or if the base station decides that the PUR resource is not available for allocation to the UE, it may send a PUR rejection message to the UE.

[0069] In some cases, a base station may provide a PUR allocation different from the PUR configuration requested by the UE. Note that the various examples in this disclosure illustrate techniques for requesting or configuring a PUR configuration. Such techniques may also be used when reconfiguring an existing PUR configuration is requested or configured, and both PUR configurations and PUR reconfigurations may be simply referred to herein as “PUR configurations.” If a base station provides a PUR allocation different from the requested PUR configuration, the UE may determine that the different PUR configuration is insufficient for the UE and transmit a PUR configuration failure. A PUR configuration failure may indicate that the UE is releasing the PUR configuration, and the base station may reallocate the configured PUR for other purposes. In some cases, a base station-to-UE transmission indicating a PUR configuration may provide an uplink resource indication, which may be used by the UE to transmit a PUR configuration failure indication or a PUR configuration completion indication. In some cases, an uplink resource indication may be an explicit indication of uplink permission, provided with the PUR configuration. As an addition or alternative, the UE may monitor for and request one or more downlink control channel (e.g., physical downlink control channel (PDCCH)) transmissions during a window to obtain uplink permission for a PUR failure or PUR configuration complete indication. In some cases, the UE may send a PUR failure or PUR configuration complete message while in connected mode (e.g., radio resource control (RRC) connected mode) or idle mode (e.g., RRC idle mode). If the UE is in idle mode, the PUR failure or PUR configuration complete message may be sent upon the first occurrence of the configured PUR.

[0070] In some cases, the UE may decide that the random access procedure for establishing a connection with the base station is configured to allow early data transmission (EDT) as part of the random access procedure. Such an EDT random access procedure may allow the UE to transmit a data payload as part of the random access procedure, which may reduce overhead and allow for the transmission of relatively small amounts of data. In some cases, the EDT random access procedure may be used by the UE to transmit a PUR request and by the base station to transmit a PUR configuration to the UE. In such cases, various embodiments of the EDT random access procedure may include transmissions providing PUR request and configuration information to be communicated between the base station and the UE.

[0071] In some cases, a PUR request from a UE requesting a PUR configuration or PUR reconfiguration may provide an indication of the number of instances of the requested PUR authorization. In such cases, the UE may indicate a value for the number of such PUR authorizations requested, an indeterminate number of PUR authorizations being requested (i.e., such authorizations continuing indefinitely), or zero PUR authorizations being requested and the PUR configuration being 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 also send a PUR rejection indication to the UE that indicates 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 retain the existing PUR configuration. In some cases, the indication from the base station may be an explicit indication provided along with the PUR rejection indication.

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

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

[0074] Figure 1 shows an example of a wireless communication system 100 supporting PUR techniques in wireless communication according to aspects of this 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-high reliability (e.g., mission-critical) communication, low-latency communication, or communication with low-cost, low-complexity devices.

[0075] Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. The base station 105 described herein may include, or may be referred to by, several other preferred terms, transceiver base station, radio base station, access point, radio transceiver, node B, enode B (eNB), next-generation node B or giganode B (any of which may be called gNB), home node B, home enode B, or several other preferred terms. The wireless communication system 100 may include different types of base stations 105 (e.g., macro base stations or small cell base stations). UE 115 described herein may communicate with various types of base stations 105 and network equipment, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

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

[0077] The geographical coverage area 110 for base station 105 may be divided into sectors that constitute a portion of the geographical coverage area 110, 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, base station 105 may be mobile and therefore may provide communication coverage to a moving geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies may overlap, and overlapping geographical coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105. The wireless communication system 100 may include, for example, heterogeneous LTE / LTE-A / LTE-A Pro networks or NR networks in which different types of base stations 105 provide coverage to various geographical coverage areas 110.

[0078] The term “cell” refers to a logical communication entity used for communication with a base station 105 (for example, via a carrier) and may relate to identifiers (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)) used to distinguish 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 communications (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term “cell” may refer to a portion (e.g., a sector) of a geographical coverage area 110 on which a logical entity operates.

[0079] UE115 may be distributed throughout the entire wireless communication system 100, and each UE115 may be fixed or mobile. UE115 may also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or several other preferred terms, where “device” may also be referred to as a unit, station, terminal, or client. UE115 may also be a personal electronic device such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, which may be implemented in various items such as appliances, vehicles, meters, etc.

[0080] Some UE115s, such as MTC devices or IoT devices, may be low-cost or low-complexity devices that can provide automated communication between machines (for example, via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with base stations 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or acquire information and relay that information to a central server or application program where that information is available, or present that information to a human interacting with the program or application. Some UE115s may be designed to collect information or enable automated machine behavior. 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 UE115s may be configured to employ power-saving operating modes, such as half-duplex communication (e.g., modes that support unidirectional communication via transmit or receive, but not simultaneous transmit and receive). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for the UE115 include entering a power-saving "deep sleep" mode when not engaged in active communication, or operating via a limited bandwidth (e.g., according to narrowband communication). In some cases, the UE115 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 (for example, using a peer-to-peer (P2P) protocol or a device-to-device (D2D) protocol). One or more of the groups of UE115s utilizing D2D communication may be within the geographical coverage area 110 of base station 105. Other UE115s in such groups may be outside the geographical coverage area 110 of base station 105, or may not be able to receive transmissions from base station 105. In some cases, a group of UE115s communicating via D2D communication may utilize a one-to-many (1:M) system where each UE115 transmits to all other UE115s in the group. In some cases, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE115s without the involvement of base station 105.

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

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

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

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

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

[0088] The wireless communication system 100 may also operate in the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (for example, from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter-wave (mmW) communication between a UE 115 and a 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 the UE 115. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency domains, and the specified use of bands across these frequency domains may vary by country or regulatory body.

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

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

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

[0092] In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at 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 to communicate over logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use Hybrid Automatic Retransmission Requests (HARQ) to improve link efficiency by performing retransmissions at the MAC layer. In the control plane, the Radio Resource Control (RRC) protocol layer may establish, configure, and maintain RRC connections between the UE 115 and the base station 105 or core network 130, supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

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

[0094] The time interval in LTE or NR is, for example, T s = This can be expressed as a multiple of the basic time unit, which may refer to a sampling period of 1 / 30,720,000 seconds. The time interval of the communication resources may be organized according to wireless frames, each having a duration of 10 milliseconds (ms), where the frame duration is T f =307,200T sIt can be expressed as follows: A wireless frame can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may contain 10 subframes numbered from 0 to 9, each subframe having a duration of 1 ms. A subframe may be further divided into two slots, each having a duration of 0.5 ms, and each slot may contain 6 or 7 modulated symbol periods (for example, depending on the length of the cyclic prefix prepared for each symbol period). Except for the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the smallest scheduling unit of the wireless communication system 100, and may be called a transmit time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (for example, in a burst of shortened TTI (sTTI) or in a selected component carrier using sTTI).

[0095] In some wireless communication systems, a slot may be further divided into multiple minislots, each containing one or more symbols. In some cases, the symbols or minislots within a minislot may be the smallest unit of scheduling. Each symbol may have a duration that varies depending, for example, on the subcarrier interval or the frequency band of operation. Furthermore, some wireless communication systems may implement slot aggregation, where multiple slots or minislots 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 for supporting communication over communication link 125. For example, the carrier of communication link 125 may include a portion of the radio frequency spectrum band that is operated 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. The carrier may be associated with a predetermined frequency channel (e.g., an Advanced 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. The carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted over the carrier may consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM).

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

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

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

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

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

[0102] In some cases, UE115 and base station 105 may use PUR to help reduce signaling overhead associated with uplink transmission. In some cases, base station 105 may transmit an indication of PUR support (for example, via SIB). UE115 may receive this indication and transmit a PUR request to base station 105. The PUR response from base station 105 may indicate a PUR allocation for UE115 that can be used for uplink transmission. In some cases, base station 105 may provide a PUR allocation different from the requested PUR configuration provided by UE115 in the PUR request. UE115 may determine that the different PUR configuration is insufficient for UE115 and transmit a PUR configuration failure to base station 105. In some cases, the transmission from base station 105 to UE115 indicating a PUR configuration may provide an indication of uplink resources that can be used by UE115 to transmit a PUR configuration failure indication.

[0103] In some cases, the EDT random access procedure may be used by UE115 to send a PUR request, and may be used by base station 105 to send a PUR configuration to UE115. Additionally or alternatively, a PUR request from UE115 requesting a PUR configuration or PUR reconfiguration may provide an indication of the number of instances of the requested PUR permission. Additionally or alternatively, base station 105 may determine that the requested PUR reconfiguration is not available to UE115 and may also indicate how UE115 will handle the existing PUR configuration (e.g., whether to release the existing PUR configuration or to retain 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 an aspect 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 Figure 1. The UE 115-a may communicate with the base station 105-a within the coverage area 110-a via a downlink transmitter 205 and an uplink transmitter 210.

[0105] In some cases, base station 105-a may constitute a set of resources as a PUR that can be used for uplink transmissions of UE 115-a and other UEs that can be serviced by base station 105-a. In some cases, UE 115-a and base station 105-a may operate using MTC or NB-IoT communication, and 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, UE 115-a may be stationary or (e.g., in a factory automation deployment) mobile within a relatively small area, and therefore may have a modern timing advance (TA) to synchronize uplink transmissions to base station 105-a even when UE 115-a comes out of idle mode to send uplink transmissions.

[0106] In some cases, base station 105-a may provide a PUR indicator 215 indicating support for PUR at base station 105-a. Such an indicator may be provided, for example, in a SIB or other downlink signaling (e.g., in a synchronous signaling block (SSB), a physical broadcast channel (PBCH) transmitted with minimal residual system information (RMSI), etc.). UE 115-a may receive the PUR indicator 215 and decide that its data transmission needs will benefit from pre-configured uplink transmissions. For example, if UE 115-a has periodic uplink transmissions smaller than a transmission size threshold, UE 115-a may decide that it should request a PUR configuration from base station 105-a. Additionally or alternatively, if UE 115-a has relatively high-priority traffic (e.g., data traffic for critical systems or safety-related information), UE 115-a may decide that it should request a PUR configuration from base station 105-a. In some cases, the PUR indicator 215 may provide an indication of the data size for the relevant uplink transmission, which UE115-a may use to determine whether a PUR configuration should be requested.

[0107] UE115-a may decide to request a PUR configuration and send a PUR request 225 to base station 105-a. UE115-a may, in some cases, be in connection mode (e.g., RRC connection mode) when sending the PUR request 225 and may send the message using dynamic uplink authorization (e.g., uplink resources allocated by base station 105-a and indicated to UE115-a in downlink control information (DCI)) or in pre-configured authorization (e.g., semi-persistent scheduling (SPS) authorization previously provided to UE115-a). In some cases, UE115-a may be in idle mode (e.g., RRC idle mode) and, if base station 105-a supports EDT, may use EDT to send the PUR request 225. Furthermore, in some cases, UE115-a may have an existing PUR allocation and may use a previously configured PUR authorization to send a PUR request 225 requesting the reconfiguration of the existing PUR allocation.

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

[0109] Figure 3 shows an example of a process flow 300 supporting a PUR technique in wireless communications according to aspects of this disclosure. In some examples, the process flow 300 may implement an embodiment of a wireless communications system 100 or 200. In this example, the process flow 300 includes UE115-b and base station 105-b, which may be examples of corresponding devices described with reference to Figures 1 and 2.

[0110] In 305, base stations 105-b and UE 115-b may perform connection establishment (e.g., RRC connection establishment). Such connection establishment may be performed using connection establishment procedures established for wireless communication (e.g., using random access techniques established in LTE or NR systems).

[0111] In 310, base station 105-b may identify a PUR resource and format an SIB indicating PUR support. In some cases, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using PUR, and traffic or service priority related to PUR authorization. In some cases, the SIB may provide an index to a pre-configured mapping of PUR configurations. In some cases, base station 105-b may configure several different sets of PURs, and the SIB may be formatted to indicate multiple sets of PURs. In 315, base station 105-b may transmit an SIB having an indication of PUR support, which UE 115-b may receive.

[0112] In this example, UE115-b may be in connected mode, and in 320, base station 105-b may grant uplink permission to UE115-b. Uplink permission may be granted, for example, based on a buffer status report (BSR) provided by UE115-b. In 325, UE115-b may format a PUR request message. A 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 reconfiguring the existing PUR configuration (for example, based on updated data traffic on UE115-b, a change in the presence of higher-priority data on UE115-b, etc.).

[0113] In 330, UE115-b may send a PUR request message. In some cases, the PUR request message may be sent using the uplink resources provided in the uplink authorization. In other cases, as will be described in more detail below, UE115-b may send the PUR request message using other uplink resources (e.g., SPS resources, EDT Random Access Procedure Send, other existing PUR resources, etc.).

[0114] In 335, base station 105-b may receive a PUR request message and determine the PUR configuration for UE 115-b. Depending on the circumstances, base station 105-b may determine the PUR configuration based on one or more of the following: QoS information provided in the PUR request, the type of PUR requested (for example, whether an acknowledged mode (AM) PUR 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] In 340, base station 105-b may send a PUR acknowledgment message to UE115-b indicating a PUR configuration for 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 for UE115-b. In some cases, the PUR configuration may be shared by several different UEs, and the PUR configuration may indicate the shared resources and provide information that can be used by UE115-b to enable base station 105-b to distinguish transmissions from UE115-b (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.).

[0116] In 345, UE115-b may identify the PUR configuration provided by base station 105-b. If the PUR configuration is a new configuration, UE115-b may configure uplink transmissions to be transmitted 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. In 350, UE115-b may optionally send a PUR configuration (or reconfiguration) complete message to 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 unsuitable for the UE (for example, due to the number of PUR permissions being less than the number required for transmissions of a particular priority). In such cases, instead of sending a configuration complete indication, UE115-b may send a PUR failure indication that allows both UE115-b and base station 105-b to release the configured resources of the PUR configuration. In some cases, the uplink resources for such indication to base station 105-a may be indicated in the PUR confirmation message (for example, in an explicit uplink grant, a window in which UE115-b will monitor for a PDCCH transmission with uplink grant, the first instance of PUR grant, etc.).

[0117] Figure 4 shows another example of a process flow 400 supporting a PUR technique in wireless communications according to an aspect of the present disclosure. In some examples, the process flow 400 may implement an aspect of a wireless communications system 100 or 200. In this example, the process flow 400 includes UE115-c and base station 105-c, which may be examples of corresponding devices described with reference to Figures 1 and 2.

[0118] In 405, the UE115-c may be in idle mode. In some cases, the UE115-c may be idle (e.g., in RRC_IDLE mode) because it has previously performed connection establishment and there is no uplink or downlink data to send.

[0119] In 410, base station 105-c may identify a PUR resource and format an SIB indicating PUR support. In some cases, as described with respect to Figure 3, the SIB may provide information on various PUR parameters, such as the amount of data that can be transmitted in an uplink transmission using the PUR resource, and traffic or service priority related to the PUR configuration. In some cases, the SIB may provide an index to a pre-configured mapping of PUR configurations. In some cases, base station 105-c may configure several different PUR configurations, and the SIB may be formatted to indicate multiple PUR configurations. In 415, base station 105-c may transmit an SIB having an indication of PUR support, which UE 115-c may receive.

[0120] In this example, UE115-c may be in idle mode, and in 420, UE115-c may be able to receive SIBs and identify that base station 105-c supports PUR. In some cases, UE115-c may be in idle mode but periodically monitor for SIBs and other downlink control transmissions, and may receive SIBs during such monitoring.

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

[0122] In 430, UE115-c may send a PUR request message. In some cases, the PUR request message may be sent using, for example, an SPS resource previously allocated to UE115-c. In other cases, UE115-c may execute a random access procedure and send a PUR request upon completion of the random access procedure (for example, in a MSG5 transmission). In yet another case, UE115-c may have an existing PUR allocation and send a PUR request using the existing PUR allocation. Furthermore, in some cases, as will be explained in more detail with respect to Figure 7, the PUR request message may be sent within an EDT random access message.

[0123] In 435, base station 105-c may receive a PUR request message and determine the PUR configuration for UE 115-c. Depending on the circumstances, base station 105-c may determine the PUR configuration based on one or more of the following: QoS information provided in the PUR request, whether an AM PUR or an UM PUR is requested, other PUR allocations to other UEs, the amount of available PUR resources, or any combination thereof.

[0124] In 440, base station 105-c may send a PUR acknowledgment message to UE115-c indicating a PUR configuration for 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, and the PUR configuration may indicate shared resources and provide information that can be used by UE115-c to enable base station 105-c to distinguish transmissions from UE115-c (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.).

[0125] In 445, UE115-c may identify the PUR configuration provided by base station 105-c. If the PUR configuration is a new configuration, UE115-c may configure uplink transmission to be transmitted 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. In 450, UE115-c may optionally send a PUR configuration (or reconfiguration) completion message (or PUR configuration failure message) to base station 105-c.

[0126] Figure 5 shows an example of a process flow 500 supporting a PUR technique in wireless communications according to an aspect of the present disclosure. In some examples, the process flow 500 may implement an aspect of a wireless communications system 100 or 200. In this example, the process flow 500 includes UE115-d and base station 105-d, which may be examples of corresponding devices described with reference to Figures 1 and 2.

[0127] In 505, UE115-d may be in idle mode. In some cases, UE115-d may be idle because it has previously performed connection establishment and there is no uplink or downlink data to transmit. In 510, base station 105-d may identify EDT support and PUR resources and format an 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 Figures 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, and traffic or service priority related to the PUR configuration. In some cases, the SIB may provide an index to a pre-configured mapping of PUR configurations. In some cases, base station 105-d may configure several different PUR configurations, and the SIB may be formatted to indicate multiple PUR configurations. In 515, base station 105-d may transmit an SIB having a PUR support indication, which UE 115-d may receive.

[0128] In this example, UE115-d may be in idle mode, and in 520, UE115-d may be able to receive SIBs and identify that base station 105-d supports EDT and PUR. In some cases, UE115-d may be in idle mode but periodically monitor for SIBs and other downlink control transmissions, and may receive SIBs during such monitoring.

[0129] In 525, UE115-d may identify uplink data for PUR and 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, UE115-d may have an existing PUR configuration, and the PUR request may be for the reconfiguration of the existing PUR configuration (for example, based on updated data traffic in UE115-d, a change in the presence of higher-priority data in UE115-d, etc.).

[0130] In 530, UE115-d may send a PUR request message (for example, after the EDT). In some cases, UE115-d may send a random access request, and may provide a PUR request within the EDT related to the random access procedure, in accordance with established techniques for sending the EDT, as will be described in more detail with respect to Figure 7.

[0131] In 535, base station 105-d may receive a PUR request message and determine a PUR configuration for UE 115-d. Depending on the circumstances, base station 105-d may determine the PUR configuration based on one or more of the following: QoS information provided in the PUR request, whether AM PUR or UM PUR is requested, other PUR configurations for other UEs, the amount of available PUR resources, or any combination thereof.

[0132] In 540, base station 105-d may send a PUR acknowledgment message to UE115-d indicating a PUR configuration for UE115-d. In some cases, the PUR configuration may be a new configuration for UE115-d. In other cases, the PUR configuration may be a reconfigured existing PUR configuration for UE115-d. In some cases, the PUR configuration may be shared by multiple different UEs, and the PUR configuration may indicate shared resources and provide information that can be used by UE115-d to enable base station 105-d to identify transmissions from UE115-d (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.).

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

[0134] As shown above, in some cases, the base station may determine that a PUR configuration corresponding to a received PUR request is not available, and the base station may provide a different PUR configuration for use by the UE (for example, one with fewer PUR permissions available for uplink transmissions from the UE). In such cases, the UE may determine whether the different PUR configuration is sufficient to meet the UE's needs. If the different PUR configuration is not suitable for properly servicing the data related to the requested PUR configuration, the UE may send a PUR configuration failure message to the base station in response to the receipt of the different PUR configuration. Figure 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 supporting a PUR technique in wireless communications according to aspects of this disclosure. In some examples, the process flow 600 may implement an embodiment of a wireless communications system 100 or 200. In this example, the process flow 600 includes a UE 115-e and a base station 105-e, which may be examples of the corresponding devices described with reference to Figures 1 and 2.

[0136] In 605, base station 105-e and UE 115-e may each determine that the PUR conditions are satisfied. Such a determination may be made as described in the various examples herein, such as base station 105-e establishing a PUR configuration and providing the UE with an indication of it (for example, in an SIB), and UE 115-e, upon receiving such an indication, may decide to request a PUR configuration.

[0137] In 610, the UE may identify an uplink resource for sending a PUR request message. In some cases, the uplink resource may be provided within an uplink authorization associated with the UE115-e in connected mode. In other cases, the UE115-e in connected or idle mode may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.).

[0138] In 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, UE115-e may have existing PUR allocations, and the PUR request may be for the reconfiguration of existing PUR allocations (for example, based on updated data traffic in UE115-e, a change in the presence of higher-priority data in UE115-e, etc.). In 620, UE115-e may send a PUR request message, which base station 105-e may receive.

[0139] In 625, base station 105-e may determine that the requested PUR allocation for UE115-e is unavailable. Depending on the circumstances, base station 105-e may determine that the PUR allocation is unavailable based on one or more of the following: the amount of PUR authorization 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. Base station 105-e may identify different PUR configurations available for UE115-e.

[0140] In 630, base station 105-e may send a PUR response message to UE115-e indicating a different PUR configuration allocated for UE115-e. In 635, UE115-e may determine that the PUR configuration provided by base station 105-e is insufficient for UE115-e's uplink transmissions. For example, UE115-e may have uplink data that should be transmitted at a set periodicity (e.g., sensor data that should be transmitted once every 30 seconds), and the PUR configuration provided by base station 105-e may provide PUR grants at a less periodicity than set (e.g., one PUR grant every 60 seconds). Thus, in this example, based on 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 required or cannot be applied due to other configurations that conflict with the PUR configuration.

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

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

[0143] In other cases, UE115-e may be in idle mode, and uplink permission may be provided after the PUR response message so that UE115-e can send a PUR configuration failure from idle mode. In some cases, uplink permission may be provided in the PUR configuration or PUR response message itself. Additional or alternative, UE115-e may monitor PDCCH during several windows following the PUR response message to obtain uplink permission for use when sending a PUR configuration failure message (or PUR configuration acknowledgment message) while in idle mode. In further cases, additional or alternative, a procedure may be provided in 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 acknowledgment message) while in idle mode.

[0144] As shown with respect to Figure 5, in some cases, an EDT procedure may be used to exchange PUR requests and configuration messages. Figure 7 shows an example of a process flow 700 supporting the PUR technique in EDT according to aspects of this disclosure. In some examples, the process flow 700 may implement an embodiment of a wireless communication system 100 or 200. In this example, the process flow 700 includes UE115-f and base station 105-f, which may be examples of the corresponding devices described with reference to Figures 1 and 2.

[0145] In 705, UE115-f may be in idle mode. In some cases, UE115-f may be idle because it has previously performed connection establishment and there is no uplink or downlink data to transmit. In 710, base station 105-f may identify EDT support and PUR resources and format an SIB indicating PUR support and EDT support. In some cases, base station 105-f may determine whether UE115-f is allowed to use EDT to request PUR configuration / reconfiguration / release. 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 Figures 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, and traffic or service priority related to PUR configuration. In some cases, the SIB may provide an index to a pre-configured mapping of PUR configurations. In some cases, base station 105-f may configure several different PUR configurations, and the SIB may be formatted to indicate multiple PUR configurations. In 715, base station 105-f may transmit an SIB having indications of PUR support and EDT support, which UE 115-f may receive.

[0146] In this example, UE115-f may be in idle mode, and in 720, UE115-f may be able to receive SIBs and identify that base station 105-f supports EDT and PUR. In some cases, UE115-f may be in idle mode but periodically monitor for SIBs and other downlink control transmissions, and may receive SIBs during such monitoring.

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

[0148] In 740, UE115-f may 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-f may have an existing PUR configuration, and the PUR request may be for reconfiguring the existing PUR configuration or releasing the existing PUR configuration (for example, based on updated data traffic in UE115-f, a change in the presence of higher-priority data in UE115-f, etc.).

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

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

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

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

[0153] Furthermore, as shown in Figure 7, base station 105-f may transmit an EDT MSG4 with 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, a delta configuration may be used to configure or reconfigure the PUR for signaling efficiency. Such a delta configuration only needs to provide parameters that are modified from a previous PUR configuration or from the default PUR configuration relative to the current configuration of UE115-f, and any missing parameters are assumed to have either a default value or an unchanged value from the current UE value (e.g., EARFCN).

[0155] As illustrated, in some cases, EDT MSG4 may provide an RRC early data completion message (for example, to CP-EDT). In some cases, such a message may implicitly or explicitly indicate that UE115-f may perform one or more of the following actions with respect to PUR resources: continue using an already allocated random access MSG1 data resource (i.e., an existing PUR configuration), verify whether an already allocated PUR configuration is valid or invalid, deconfigure or release an already allocated PUR configuration, allocate a new Msg1 data resource, or any combination thereof. In some cases, an explicit indication for PUR release may be provided in a Boolean flag to indicate the release of a PUR resource; if no such flag is present, the previously configured PUR is considered to still be valid when UE115-f returns to idle mode. In some cases, the Boolean flag may be included in an RRC connection release message or an RRC connection resume message. In some cases, base station 105-f may indicate that PUR support is turned off for all UEs when making a call by providing an SIB indication that PUR is not supported, in which case UE 115-f (and other UEs that may receive the SIB) may release any PUR configuration.

[0156] As an addition or alternative, base station 105-f may decide that the PUR configuration of UE115-f will be reconfigured. For example, base station 105-f may decide that resources allocated to a PUR will 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, which 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 UE115-f in idle mode to trigger UE115-f to establish an RRC connection, and once UE115-f is in 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, which is used by base station 105-f to indicate to UE115-f that a configured PUR should be released.

[0157] Furthermore, in some cases, when UE115-f sends a PUR request message, one or more items of supporting information may be provided, such as the UE's coverage enhancement (CE) level or traffic-related information. Such traffic-related information may include, for example, traffic periodicity (or traffic arrival pattern), traffic probability (i.e., whether the UE will always transmit or not have data), traffic-related delay tolerance, packet size to be transmitted, or any combination thereof, one or more of these. Additional or alternative, in some cases, UE115-f may also provide a PUR configuration or reconfiguration request message, a requested number of PUR permission occurrences. In some cases, the number of occurrences may be indicated as one for requesting a one-shot PUR, or 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 indeterminate to request that the PUR permission remains indefinitely valid until one criterion for PUR release is met. In some cases, the number of occurrences may be provided within an information element in the PUR request. In some cases, the number of occurrences may be indicated as none in order to require the PUR resource to remain indefinitely active until one of the criteria for PUR release is met. Similarly, in some cases, the number of occurrences may be indicated as 0 in order to request the release of a PUR resource, thereby avoiding the need for a separate PUR release request message, particularly 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 PUR permission. As an addition or alternative, UE115-f may indicate a PUR reconfiguration failure, as described with respect to Figure 8, which may indicate that the PUR configuration is being released.

[0158] Figure 8 shows an example of a process flow 800 supporting a PUR technique in wireless communications according to aspects of the present disclosure. In some examples, process flow 800 may implement an embodiment of wireless communications system 100 or 200. In this example, process flow 800 includes a UE 115-g and a base station 105-g, which may be examples of the corresponding devices described with reference to Figures 1 and 2. In this example, the EDT procedure may again be used to exchange PUR request and configuration messages, as in Figure 7, but if the PUR configuration provided by base station 105-g is insufficient for UE 115-g, UE 115-g will indicate a PUR configuration failure.

[0159] In this example, at 805, UE115-g may be in idle mode. In some cases, UE115-g may be idle because it has previously performed connection establishment and there is no uplink or downlink data to transmit. At 810, base station 105-g may identify EDT support and PUR resources and format an SIB indicating PUR support and EDT support. At 815, base station 105-g may transmit an SIB having indications of PUR support and EDT support, which UE115-g may receive.

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

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

[0162] In 840, the UE115-g may 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, the UE115-g may have an existing PUR configuration, and the PUR request may be for the reconfiguration of the existing PUR configuration or the release of the existing PUR configuration (for example, based on updated data traffic in the UE115-g, a change in the presence of higher-priority data in the UE115-g, etc.).

[0163] At 845, UE115-g may send a PUR request message using EDT MSG3. At 850, base station 105-g may receive the PUR request message and determine a PUR configuration for UE115-g. In this example, at 850, base station 105-g may determine that the requested PUR configuration is unavailable and determine a different PUR configuration for UE115-g.

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

[0165] In 860, UE115-g may identify different PUR configurations provided by base station 105-g and may determine that the different PUR configurations are inadequate (for example, based on fewer PUR authorizations than required for uplink data transmission). In 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 again use MO EDT process 870 to communicate PUR requests and PUR responses. Furthermore, additional uplink transmissions may be provided to indicate PUR configuration failures, and uplink resources for uplink transmissions may be identified as described herein, as relating to Figure 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. The UE's actions after receiving such a rejection message may be based on one or more implicit or explicit indications related to the rejection message. Figure 9 shows an example of a process flow 900 supporting a PUR technique in which a PUR rejection message is sent to the UE, according to aspects of this disclosure. In some examples, the process flow 900 may implement an embodiment of a wireless communication system 100 or 200. In this example, the process flow 900 includes a UE 115-h and a base station 105-h, which may be examples of the corresponding devices described with reference to Figures 1 and 2.

[0167] In 905, base station 105-h and UE 115-h may each decide that the PUR conditions are satisfied. Such a decision may be made as described in the various examples herein, such as base station 105-h establishing a PUR configuration and providing the UE with an indication of it (for example, in an SIB), and UE 115-h, upon receiving such an indication, may decide to request a PUR configuration.

[0168] In 910, the UE may identify an uplink resource for sending a PUR request message. In some cases, the uplink resource may be provided within an uplink authorization associated with the UE115-h in connected mode. In other cases, the UE115-h in connected or idle mode may identify other uplink resources (e.g., SPS resources, EDT transmissions, other existing PUR resources, etc.).

[0169] At 915, 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, UE115-h may have existing PUR allocations, and the PUR request may be for the reconfiguration of existing PUR allocations (for example, based on updated data traffic at UE115-h, a change in the presence of higher-priority data at UE115-h, etc.). At 920, UE115-h may send a PUR request message, which base station 105-h may receive.

[0170] In 925, base station 105-h may determine that the requested PUR allocation for UE 115-h is unavailable. Depending on the circumstances, base station 105-h may determine that the PUR allocation is unavailable based on one or more of the following: the amount of PUR authorization 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. Base station 105-h may identify different PUR configurations available for UE 115-h.

[0171] In 930, if an existing PUR configuration exists, base station 105-h may decide whether to retain or release the existing PUR configuration of UE115-h. In 935, base station 105-h may send a PUR rejection message to UE115-h that may provide an indication of how UE115-h should handle the existing PUR configuration if such an existing PUR configuration exists. If there is no existing PUR, UE115-h may fall back 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 retained or released. In some cases, if UE115-h does not receive a response message from base station 105-h, UE115-h may consider the PUR request to be rejected and may use default rules for existing PUR configurations, if any. In some cases, a PUR rejection message may include an explicit indication of how to handle an existing PUR configuration. For example, base station 105-h may indicate to UE 115-h that the PUR request will be rejected and the configured PUR will be released, or that the PUR request will be rejected and the configured PUR will be maintained. Such explicit indications can give base station 105-h extended flexibility to determine and explicitly indicate UE 115-h's behavior based on various conditions at base station 105-h that led to the PUR rejection message.

[0172] Figure 10 shows a block diagram 1000 of a device 1005 supporting a PUR technique in wireless communication according to an aspect of this disclosure. Device 1005 may be an example of an embodiment of UE 115 as described herein. Device 1005 may include a receiver 1010, a communications manager 1015, and a transmitter 1020. Device 1005 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0173] Receiver 1010 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 PUR techniques in wireless communication). The information may be passed to other components of device 1005. Receiver 1010 may be an example of an embodiment of transceiver 1320, which will be described with reference to Figure 13. Receiver 1010 may utilize a single antenna or a set of antennas.

[0174] In some cases, the communications manager 1015 may decide that the base station will support PUR for grant-free uplink transmissions from the UE, send a PUR request message to the base station based on the decision that the base station will support PUR, receive a PUR configuration from the base station in response to the PUR request message that identifies the PUR allocated to the UE, receive uplink resources for a response message to be sent from the UE, and send a PUR configuration response message to the base station using the uplink resources for the response message.

[0175] In some cases, the communications manager 1015 may also determine an EDT configuration for an EDT procedure, wherein the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure, and format a PUR request message to be transmitted in an uplink message of the EDT procedure, wherein the PUR request message may indicate a requested configuration, reconfiguration, or release of a PUR configuration, and transmit the PUR request message in an uplink message of the EDT procedure, and receive a PUR configuration message from the base station in response to the uplink message.

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

[0177] In some cases, the communications manager 1015 may also decide that the base station will support PUR for grant-free uplink transmissions from the UE, and send a PUR request message to the base station based on the decision that the base station will support PUR, wherein the PUR request message includes the number of instances of PUR authorization 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 communications manager 1015 may also decide that the base station will support PUR for a grant-free uplink transmission from the UE, send a PUR request message to the base station based on the base station's decision to support PUR, and receive a PUR response message from the base station in response to the 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. The communications manager 1015 may be an example of an embodiment of the communications manager 1310 described herein.

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

[0180] The communication manager 1015 or its subordinate components may be physically located in various locations, including distributed so that parts of its functionality are implemented in different physical locations by one or more physical components. In some examples, the communication manager 1015 or its subordinate components may be separate and different components according to various aspects of this disclosure. In some examples, the communication manager 1015 or its subordinate components may be combined with one or more other hardware components, including, but not limited to, input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof according to various aspects of this disclosure.

[0181] Transmitter 1020 can transmit signals generated by other components of device 1005. In some examples, transmitter 1020 may be located together with receiver 1010 in a transceiver module. For example, transmitter 1020 may be an example of an embodiment of transceiver 1320, which is described with reference to Figure 13. Transmitter 1020 may utilize a single antenna or a set of antennas.

[0182] Figure 11 shows a block diagram 1100 of a device 1105 supporting a PUR technique in wireless communication according to an aspect of this disclosure. Device 1105 may be an example of an aspect of device 1005 or UE 115 as described herein. Device 1105 may include a receiver 1110, a communications manager 1115, and a transmitter 1145. Device 1105 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0183] 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 PUR techniques in wireless communication). The information may be passed to other components of device 1105. Receiver 1110 may be an example of an embodiment of transceiver 1320, which will be described with reference to Figure 13. Receiver 1110 may utilize a single antenna or a set of antennas.

[0184] Communication manager 1115 may be an example of an embodiment of communication manager 1015 as described herein. Communication manager 1115 may include a PUR determination component 1120, a PUR request manager 1125, a PUR configuration manager 1130, a PUR transmission manager 1135, and an EDT random access manager 1140. Communication manager 1115 may be an example of an embodiment of communication manager 1310 as described herein.

[0185] The PUR determination component 1120 may determine that the base station will support PUR for grant-free uplink transmissions 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 a PUR configuration from the base station in response to the PUR request message, identifying the PUR assigned to the UE. The PUR transmission manager 1135 may receive uplink resources for a response message to be sent from the UE and may use the uplink resources for the response message to send a PUR configuration response message to the base station.

[0186] The EDT Random Access Manager 1140 may determine an EDT configuration for an 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 a PUR Request message to be transmitted in the uplink message of the EDT procedure, where the PUR Request message indicates a requested configuration, reconfiguration, or release of a PUR configuration, and may transmit a 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 a PUR Request message.

[0187] The PUR decision component 1120 may decide that the base station will support PUR for grant-free uplink transmissions 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, 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 decide that the base station will support PUR for grant-free uplink transmissions 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. In response to the PUR request message, the PUR configuration manager 1130 may receive 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] Transmitter 1145 can transmit signals generated by other components of device 1105. In some examples, transmitter 1145 may be located together with receiver 1110 in a transceiver module. For example, transmitter 1145 may be an example of an embodiment of transceiver 1320, which will be described with reference to Figure 13. Transmitter 1145 may utilize a single antenna or a set of antennas.

[0190] Figure 12 shows a block diagram 1200 of a communications manager 1205 supporting the PUR technique in wireless communications according to an aspect of this disclosure. The communications manager 1205 may be an example of an aspect of communications manager 1015, communications manager 1115, or communications manager 1310 as described herein. The communications manager 1205 may include a PUR determination component 1210, a PUR request manager 1215, a PUR configuration manager 1220, a PUR transmit manager 1225, an EDT random access manager 1230, a PUR response manager 1235, a paging manager 1240, an RRC manager 1245, and a PUR authorization manager 1250. Each of these modules may communicate with one another directly or indirectly (for example, via one or more buses).

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

[0192] The PUR request manager 1215 may send a PUR request message to the base station based on the base station's decision to support PUR. In some examples, the PUR request manager 1215 may format the PUR request message to be sent within an uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of the PUR configuration. In some examples, the PUR request manager 1215 may send the PUR request message within an 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 a decision that the base station supports PUR, where the PUR request message includes the number of instances of PUR authorization requested by the UE.

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

[0195] In some examples, the PUR configuration manager 1220 may, in response to a PUR request message, receive 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.

[0196] In some examples, the PUR configuration manager 1220 may determine, based on the PUR configuration from the base station, a set of control channel resources to monitor for uplink permission. In some examples, the PUR configuration manager 1220 may monitor a set of control channel resources for uplink permission, where uplink permission refers to an uplink resource for sending a PUR configuration response message to the base station.

[0197] In some cases, the PUR configuration manager 1220 may decide to deconfigure the PUR configuration based on receiving a broadcast system information transmission from the base station indicating that PUR is not supported. In some cases, the PUR configuration manager 1220 may release the PUR configuration.

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

[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 decide that the previous PUR configuration will be released.

[0200] In some cases, the PUR configuration manager 1220 may send an indication of zero instances of PUR permission in the PUR request message.

[0201] In some examples, the PUR configuration manager 1220 may send a PUR reconfiguration failure indication to the base station after receiving the PUR configuration. 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 showing a difference over the UE's previous PUR configuration. In some cases, the PUR configuration is provided as a delta configuration showing a difference over the current configuration used by the UE. In some cases, the PUR configuration is provided as a delta configuration showing a difference over the default PUR configuration.

[0203] In some cases, uplink resources for response messages are provided in an explicit indication from the base station that the PUR configuration is present. In some cases, the PUR configuration message from the base station is received in an EDT downlink message. In some cases, the PUR configuration is provided in an EDT early data completion message indicating the configured PUR resources of the UE. In some cases, an EDT early data completion message explicitly or implicitly provides one or more of the following: an indication that the UE will use a previous PUR configuration, confirmation of a 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.

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

[0205] The PUR transmission manager 1225 may receive uplink resources for a response message to be sent from the UE. In some examples, the PUR transmission manager 1225 may use the uplink resources for the response message to send a PUR configuration response message to the base station. In some cases, the uplink resources for the response message are included in the first instance of the PUR allocated to the UE. In some cases, sending a PUR configuration response message is performed when the UE is in idle mode or in 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 uplink transmission of UE payload data in the uplink message of the EDT procedure. In some examples, the EDT Random Access Manager 1230 may receive an indication from the base station that the 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 the RRC message of the EDT procedure. In some cases, the established 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 may, in response to a PUR configuration message, use the uplink resources for the response message from the UE to send an indication of a successful PUR configuration or a PUR configuration failure.

[0208] The paging manager 1240 may receive page messages from the base station. In some cases, the paging manager 1240 may send a random access request message to the base station in response to a page message, where receiving an indication that the PUR configuration should be reconfigured is a response 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 within an EDT random access message, where the PUR release message is an RRC PUR reconfiguration message.

[0210] The PUR authorization manager 1250 may receive PUR authorizations and identify the number of instances of PUR authorizations that should be requested to request a PUR configuration. In some cases, the number of instances of PUR authorizations may be an explicit number of PUR authorizations or an indeterminate number of PUR authorizations. In some cases, an indeterminate number of PUR authorizations may be indicated by the absence of a PUR authorization request field in the PUR request message or by a predetermined value in the PUR authorization request field. In some cases, the number of instances of PUR authorizations requested by the UE may indicate whether a one-shot PUR configuration or a multi-shot PUR configuration is requested.

[0211] Figure 13 shows a diagram of a system 1300 including a device 1305 that supports the PUR technique in wireless communication according to an aspect of this disclosure. Device 1305 may be, or include, an example of a component of device 1005, device 1105, or UE 115 as described herein. Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communications 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 (for example, bus 1345).

[0212] The communications manager 1310 may decide that the base station will support PUR for grant-free uplink transmissions from the UE, may send a PUR request message to the base station based on the decision that the base station will support PUR, may receive a PUR configuration from the base station in response to the PUR request message that identifies the PUR allocated to the UE, may receive uplink resources for a response message to be sent from the UE, and may send a PUR configuration response message to the base station using the uplink resources for the response message.

[0213] The communications manager 1310 also determines an EDT configuration for an EDT procedure, wherein the EDT configuration provides for uplink transmission of UE payload data in an uplink message of the EDT procedure, and formats a PUR request message to be transmitted in an uplink message of the EDT procedure, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration, and may transmit the PUR request message in an uplink message of the EDT procedure, and receive a PUR configuration message from the base station in response to the PUR request message.

[0214] The communications manager 1310 may also communicate with the base station in accordance with a pre-configured uplink resource configuration, wherein the pre-configured uplink resource configuration provides grant-free uplink transmission from the UE to the base station, receives a pre-configured uplink resource release message from the base station indicating that the UE will deconfigure the pre-configured uplink resource configuration, and deconfigures the pre-configured uplink resource configuration at least in part based on the pre-configured uplink resource release message.

[0215] The communications manager 1310 may also decide that the base station will support PUR for grant-free uplink transmissions from the UE, and send a PUR request message to the base station based on the decision that the base station will support PUR, wherein the PUR request message includes the number of instances of PUR authorization requested by the UE, and receive a PUR configuration from the base station in response to the PUR request message.

[0216] The communications manager 1310 may also decide that the base station will support PUR for a grant-free uplink transmission from the UE, send a PUR request message to the base station based on the decision that the base station will support PUR, and receive a PUR response message from the base station in response to the 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.

[0217] The I / O controller 1315 may manage input and output signals for device 1305. The I / O controller 1315 may also manage peripherals not integrated into device 1305. In some cases, the I / O controller 1315 may represent physical connections or ports to external peripherals. In some cases, the I / O controller 1315 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, the I / O controller 1315 may represent, or interact with, a modem, keyboard, mouse, touchscreen, 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 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 bidirectionally 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 bidirectionally 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 that may be capable of transmitting or receiving multiple wireless transmissions simultaneously.

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

[0221] The processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting PUR techniques in wireless communication).

[0222] Code 1335 may include instructions for carrying out aspects of this disclosure, including instructions for supporting wireless communication. Code 1335 may be stored in a non-temporary computer-readable medium, such as system memory or other types of memory. In some cases, Code 1335 may not be directly executable by processor 1340, but may cause the computer to perform the functions described herein (for example, when compiled and executed).

[0223] Figure 14 shows a block diagram 1400 of a device 1405 supporting a PUR technique in wireless communication according to an aspect of this disclosure. Device 1405 may be an example of an embodiment of a base station 105 as described herein. Device 1405 may include a receiver 1410, a communications manager 1415, and a transmitter 1420. Device 1405 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0224] 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 PUR techniques in wireless communication). The information may be passed to other components of device 1405. Receiver 1410 may be an example of an embodiment of transceiver 1720, as described with reference to Figure 17. Receiver 1410 may utilize a single antenna or a set of antennas.

[0225] The communications manager 1415 may send an indication that the base station supports PUR for grant-free uplink transmissions, may send a PUR configuration 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 response messages.

[0226] The communications manager 1415 also determines an EDT configuration for an EDT procedure, wherein the EDT configuration provides uplink transmission of UE payload data in an uplink message for the EDT procedure; receives a PUR request message from the UE in an uplink message for the EDT procedure, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration; and sends a PUR configuration message to the UE in response to the PUR request message, wherein the PUR configuration may indicate an uplink resource for a response message from the UE.

[0227] The communications manager 1415 may also transmit an indication that the base station supports PUR for grant-free uplink transmissions, transmit a PUR configuration to the UE in response to a PUR request message, and receive a PUR request message from the UE, which includes the number of instances of PUR authorization requested by the UE.

[0228] The communication manager 1415 may also transmit an indication that the base station supports PUR for grant-free uplink transmissions, and in response to a PUR request message, transmit a PUR response message to the UE indicating that the PUR request message is rejected, wherein the PUR response message may indicate how the UE will proceed based on the rejected PUR request message, and may also receive a PUR request message from the UE. The communication manager 1415 may be an example of an embodiment of the communication manager 1710 described herein.

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

[0230] The communication manager 1415 or its subordinate components may be physically located in various locations, including distributed so that parts of its functionality are implemented in different physical locations by one or more physical components. In some examples, the communication manager 1415 or its subordinate components may be separate and different components according to various aspects of this disclosure. In some examples, the communication manager 1415 or its subordinate components may be combined with one or more other hardware components, including, but not limited to, input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof according to various aspects of this disclosure.

[0231] Transmitter 1420 may transmit signals generated by other components of device 1405. In some examples, transmitter 1420 may be located together with receiver 1410 in a transceiver module. For example, transmitter 1420 may be an example of an embodiment of transceiver 1720, which is described with reference to Figure 17. Transmitter 1420 may utilize a single antenna or a set of antennas.

[0232] Figure 15 shows a block diagram 1500 of a device 1505 supporting a PUR technique in wireless communication according to an aspect of this disclosure. Device 1505 may be an example of an aspect of device 1405 or a base station 105 as described herein. Device 1505 may include a receiver 1510, a communications manager 1515, and a transmitter 1540. Device 1505 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0233] 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 PUR techniques in wireless communication). The information may be passed to other components of device 1505. Receiver 1510 may be an example of an embodiment of transceiver 1720, as described with reference to Figure 17. Receiver 1510 may utilize a single antenna or a set of antennas.

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

[0235] The PUR configuration manager 1520 may send an indication that the base station supports PUR for grant-free uplink transmissions, and may send a PUR configuration to the UE in response to a PUR request message, identifying the PUR allocated to the UE. 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 a response message.

[0236] The EDT Random Access Manager 1535 may determine an EDT configuration for an EDT procedure, where the EDT configuration provides for uplink transmission of UE payload data in the uplink message of the EDT procedure. The PUR Request Manager 1525 may receive a PUR Request message from the UE in the uplink message of the EDT procedure, where the PUR Request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The PUR Configuration Manager 1520 may send a PUR Configuration message to the UE in response to a 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 send an indication that the base station supports PUR for grant-free uplink transmissions and may send a PUR configuration to the UE in response to a PUR request message. The PUR request manager 1525 may receive a PUR request message from the UE, which includes the number of instances of PUR authorization requested by the UE.

[0238] The PUR configuration manager 1520 may send an indication that the base station supports PUR for grant-free uplink transmissions, and in response to a PUR request message, 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 will 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 device 1505. In some examples, the transmitter 1540 may be located together with the receiver 1510 in a transceiver module. For example, the transmitter 1540 may be an example of an embodiment of the transceiver 1720, which is described with reference to Figure 17. The transmitter 1540 may utilize a single antenna or a set of antennas.

[0240] Figure 16 shows a block diagram 1600 of a communications manager 1605 supporting the PUR technique in wireless communications according to an aspect of this disclosure. The communications manager 1605 may be an example of an aspect of the communications manager 1415, communications manager 1515, or communications manager 1710 described herein. The communications 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 authorization manager 1635. Each of these modules may communicate with one another directly or indirectly (for example, via one or more buses).

[0241] The PUR configuration manager 1610 may send an indication that the base station supports PUR for grant-free uplink transmissions. In some examples, the PUR configuration manager 1610 may, in response to a PUR request message, send a PUR configuration to the UE that identifies the PUR allocated to the UE. In some examples, the PUR configuration manager 1610 may, in response to a PUR request message, send a PUR configuration message to the UE, where the PUR configuration indicates the uplink resources for the response message from the UE. In some examples, the PUR configuration manager 1610 may send an indication that the base station supports PUR for grant-free uplink transmissions. In some examples, the PUR configuration manager 1610 may, in response to a PUR request message, send a PUR configuration to the UE.

[0242] In some examples, the PUR configuration manager 1610 may, in response to a PUR request message, 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 will proceed based on the rejected PUR request message. In some examples, the PUR configuration manager 1610 may, in response to a PUR configuration message, use the uplink resources for the response message from the UE to receive an indication of a successful PUR configuration or a PUR configuration failure. In some examples, the PUR configuration manager 1610 may send a broadcast system information transmission indicating that PUR is not supported and that the UE will release the PUR configuration.

[0243] In some cases, the PUR configuration manager 1610 may send a PUR release message to the UE. In some cases, 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 that shows a difference over the UE's previous PUR configuration, the current configuration used by the UE, or the default PUR configuration. In some cases, uplink resources for response messages are provided in an explicit indication of the PUR configuration from the base station. In some cases, uplink resources for response messages are 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 cases, a PUR configuration failure indication is sent when the UE is in idle mode or connected mode with the base station. In some cases, the PUR configuration is provided as a delta configuration that shows a difference over the UE's previous PUR configuration, a difference over the default PUR configuration, or a difference over the configuration used in the UE.

[0245] In some cases, the PUR configuration is provided in an 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 the following: 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, a PUR Release message is sent while the UE is in connected mode or in an EDT Random Access Response message, where the PUR Release message is an RRC PUR Reconfiguration message. In some cases, a PUR Request message indicates that the 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, a PUR Request message indicates that the 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 PUR request messages from the UE. In some examples, the PUR request manager 1615 may receive PUR request messages from the UE within an uplink message of an 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 PUR request messages from the UE, where the PUR request message includes the number of instances of PUR authorization requested by the UE. In some examples, the PUR request manager 1615 may receive PUR request messages from the UE.

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

[0248] The EDT Random Access Manager 1625 may determine an EDT configuration for an EDT procedure, where the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure. In some examples, the EDT Random Access Manager 1625 may send an indication that the uplink message of the EDT procedure is available for a PUR request message. In some cases, this indication is sent in a system information block broadcast from the base station.

[0249] The paging manager 1630 may determine that the UE's PUR configuration will 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 should be reconfigured or released in response 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 indicates that the UE will release the PUR configuration.

[0250] The PUR authorization manager 1635 may identify PUR authorizations for UE PUR configurations. In some cases, the number of instances of a PUR authorization provides an indication of an explicit number of PUR authorizations or an indeterminate number of PUR authorizations. In some cases, a number of instances that is 0 indicates that the PUR configuration will be released. In some cases, the number of instances of a PUR authorization requested by the UE indicates that a one-shot PUR configuration is requested or a multi-shot PUR configuration is requested.

[0251] Figure 17 shows a diagram of a system 1700 including a device 1705 that supports the PUR technique in wireless communications according to an aspect of the present disclosure. Device 1705 may be, or include, device 1405, device 1505, or an example of a component of a base station 105 as described herein. Device 1705 may include components for bidirectional voice and data communications, including components for transmitting and receiving communications, including a communications manager 1710, a network communications manager 1715, a transceiver 1720, an antenna 1725, a memory 1730, a processor 1740, and an inter-station communications manager 1745. These components may communicate electronically via one or more buses (e.g., bus 1750).

[0252] The communications manager 1710 may send an indication that the base station supports PUR for grant-free uplink transmissions, may send a PUR configuration 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 response messages.

[0253] The communications manager 1710 also determines an EDT configuration for an EDT procedure, wherein the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure; receives a PUR request message from the UE in the uplink message of the EDT procedure, wherein the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration; and sends a PUR configuration message to the UE in response to the PUR request message, wherein the PUR configuration may indicate an uplink resource for a response message from the UE.

[0254] The communications manager 1710 may also send an indication that the base station supports PUR for grant-free uplink transmissions, send a PUR configuration to the UE in response to a PUR request message, and receive a PUR request message from the UE, which includes the number of instances of PUR permission requested by the UE.

[0255] The communications manager 1710 may also transmit an indication that the base station supports PUR for grant-free uplink transmissions, and in response to a PUR request message, transmit a PUR response message to the UE indicating that the PUR request message is rejected, wherein the PUR response message indicates how the UE will proceed based on the rejected PUR request message, and receive a PUR request message from the UE.

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

[0257] The transceiver 1720 can 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 can 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 that may be capable of transmitting or receiving multiple wireless transmissions simultaneously.

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

[0260] The processor 1740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1740 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1740. The processor 1740 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1730) to cause device 1705 to perform various functions (e.g., functions or tasks supporting PUR techniques in wireless communication).

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

[0262] Code 1735 may include instructions for carrying out aspects of this disclosure, including instructions for supporting wireless communication. Code 1735 may be stored in a non-temporary 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 the computer to perform the functions described herein (for example, when compiled and executed).

[0263] Figure 18 shows a flowchart illustrating method 1800 supporting the PUR technique in wireless communications according to aspects of this disclosure. The operation of method 1800 may be carried out by a UE 115 or its components as described herein. For example, the operation of method 1800 may be carried out by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0264] In 1805, the UE may decide that the base station will support PUR for grant-free uplink transmissions from the UE. The operation of 1805 may be performed according to the methods described herein. In some examples, the operation of 1805 may be performed by PUR decision components as described with reference to Figures 10 to 13.

[0265] In 1810, the UE may send a PUR request message to the base station based on the decision that the base station supports PUR. The operation of 1810 may be performed according to the methods described herein. In some examples, the operation of 1810 may be performed by a PUR request manager as described with reference to Figures 10 to 13.

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

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

[0268] In 1825, the UE may use uplink resources for the response message to send 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, the operation of 1825 may be performed by a PUR transmission manager as described with reference to Figures 10 to 13.

[0269] Figure 19 shows a flowchart illustrating method 1900 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 1900 may be performed by a UE 115 or its components as described herein. For example, the operation of method 1900 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0270] In 1905, the UE may decide that the base station will support PUR for grant-free uplink transmissions from the UE. The operation of 1905 may be performed according to the methods described herein. In some examples, the operation of 1905 may be performed by PUR decision components as described with reference to Figures 10 to 13.

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

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

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

[0274] In 1925, the UE may monitor a set of control channel resources for uplink permission, where uplink permission indicates an uplink resource for sending 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 operation of 1925 may be performed by a PUR configuration manager as described with reference to Figures 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 method described herein. In some examples, the aspects of the operation of 1930 may be performed by a PUR transmission manager as described while referring 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 method described herein. In some examples, the aspects of the operation of 1935 may be performed by a PUR transmission manager as described while referring to FIGS. 10-13.

[0277] FIG. 20 shows a flowchart showing 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 while referring 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 the 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 the uplink transmission of UE payload data in an uplink message of the EDT procedure. The operation of 2005 may be performed according to the method described herein. In some examples, the aspects of the operation of 2005 may be performed by an EDT random access manager as described while referring to FIGS. 10-13.

[0279] Optionally, in 2010, the UE may format a PUR request message to be sent within 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 2010 may be performed according to the methods described herein. In some examples, the operation of 2010 may be performed by a PUR request manager as described with reference to Figures 10-13.

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

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

[0282] Figure 21 shows a flowchart illustrating a method 2100 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 2100 may be performed by a UE 115 or its components as described herein. For example, the operation of method 2100 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0283] In 2105, the UE may determine an EDT configuration for the EDT procedure, where the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure. The operation of 2105 may be performed according to the methods described herein. In some examples, the operation of 2105 may be performed by an EDT random access manager, as described with reference to Figures 10-13.

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

[0285] In 2115, the UE may send a PUR request message within the uplink message of the EDT procedure. The operation of 2115 may be performed according to the methods described herein. In some examples, the operation of 2115 may be performed by a PUR request manager as described with reference to Figures 10 to 13.

[0286] In 2120, the UE may receive a PUR configuration message from the 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, the operation of 2120 may be performed by a PUR configuration manager, as described with reference to Figures 10 to 13.

[0287] In 2125, the UE may, in response to a PUR configuration message, use the uplink resources 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, the operation of 2125 may be performed by a PUR response manager as described with reference to Figures 10 to 13.

[0288] Figure 22 shows a flowchart illustrating method 2200 supporting the PUR technique in wireless communications according to aspects of this disclosure. The operation of method 2200 may be performed by a UE 115 or its components as described herein. For example, the operation of method 2200 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0289] In 2205, the UE may determine an EDT configuration for an EDT procedure, where the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure. The operation of 2205 may be performed according to the methods described herein. In some examples, the operation of 2205 may be performed by an EDT random access manager, as described with reference to Figures 10-13.

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

[0291] In 2215, the UE may send a PUR request message within the uplink message of the EDT procedure. The operation of 2215 may be performed according to the methods described herein. In some examples, the operation of 2215 may be performed by a PUR request manager as described with reference to Figures 10 to 13.

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

[0293] Figure 23 shows a flowchart illustrating a method 2300 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 2300 may be performed by a UE 115 or its components as described herein. For example, the operation of method 2300 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0294] In 2305, the UE may determine an EDT configuration for an EDT procedure, where the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure. The operation of 2305 may be performed according to the methods described herein. In some examples, the operation of 2305 may be performed by an EDT random access manager, as described with reference to Figures 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 manner of operation of 2310 may be performed by a PUR request manager as described while referring 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 manner of operation of 2315 may be performed by a PUR request manager as described while referring to FIGS. 10 to 13.

[0297] At 2320, the UE may receive a PUR configuration message from a 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 manner of operation of 2320 may be performed by a PUR configuration manager as described while referring to FIGS. 10 to 13.

[0298] At 2325, the UE may receive a paging message from a base station. The operation of 2325 may be performed according to the methods described herein. In some examples, the manner of operation of 2325 may be performed by a paging manager as described while referring to FIGS. 10 to 13.

[0299] At 2330, the UE may send a random access request message to a 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 manner of operation of 2330 may be performed by a paging manager as described while referring to FIGS. 10 to 13.

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

[0301] Figure 24 shows a flowchart illustrating method 2400 supporting the PUR technique in wireless communications according to aspects of this disclosure. The operation of method 2400 may be performed by a UE 115 or its components as described herein. For example, the operation of method 2400 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0302] In 2405, the UE may decide that the base station will support PUR for grant-free uplink transmissions from the UE. The operation of 2405 may be performed according to the methods described herein. In some examples, the operation of 2405 may be performed by PUR determination components as described with reference to Figures 10 to 13.

[0303] In 2410, the UE may send a PUR request message to the base station based on its decision that the base station supports PUR, where the PUR request message includes the number of instances of PUR authorization requested by the UE. The operation of 2410 may be performed according to the methods described herein. In some examples, the operation of 2410 may be performed by a PUR request manager as described with reference to Figures 10 to 13.

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

[0305] Figure 25 shows a flowchart illustrating Method 2500, which supports the PUR technique in wireless communications, according to aspects of this disclosure. The operation of Method 2500 may be performed by a UE 115 or its components as described herein. For example, the operation of Method 2500 may be performed by a communications manager as described with reference to Figures 10 to 13. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. In addition or alternatively, the UE may perform aspects of the functions described below using dedicated hardware.

[0306] In 2505, the UE may decide that the base station will support PUR for grant-free uplink transmissions from the UE. The operation of 2505 may be performed according to the methods described herein. In some examples, the operation of 2505 may be performed by PUR decision components as described with reference to Figures 10 to 13.

[0307] In 2510, the UE may send a PUR request message to the base station based on the decision that the base station supports PUR. The operation of 2510 may be performed according to the methods described herein. In some examples, the operation of 2510 may be performed by a PUR request manager as described with reference to Figures 10 to 13.

[0308] In 2515, the UE may, in response to a PUR request message, receive 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 operation of 2515 may be performed by a PUR configuration manager, as described with reference to Figures 10 to 13.

[0309] Figure 26 shows a flowchart illustrating a method 2600 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 2600 may be carried out by a base station 105 or its components as described herein. For example, the operation of method 2600 may be carried out by a communications manager as described with reference to Figures 14 to 17. In some examples, the base station may execute a set of instructions to control the base station's functional elements to perform the functions described below. In addition or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

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

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

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

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

[0314] In 2625, the base station may send uplink resources to the UE for a response message from the UE. The operation of 2625 may be performed according to the methods described herein. In some examples, the mode of operation of 2625 may be performed by undefined means, as described with reference to Figures 14-17.

[0315] Figure 27 shows a flowchart illustrating a method 2700 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 2700 may be performed by a base station 105 or its components as described herein. For example, the operation of method 2700 may be performed by a communications manager as described with reference to Figures 14 to 17. In some examples, the base station may execute a set of instructions to control the base station's functional elements to perform the functions described below. In addition or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

[0316] In 2705, the base station may determine an EDT configuration for the EDT procedure, where the EDT configuration provides uplink transmission of UE payload data in the uplink message of the EDT procedure. The operation of 2705 may be performed according to the methods described herein. In some examples, the operation of 2705 may be performed by an EDT random access manager, as described with reference to Figures 14-17.

[0317] In 2710, the base station may receive a PUR request message from the UE in the uplink message of the EDT procedure, where the PUR request message indicates a requested configuration, reconfiguration, or release of a PUR configuration. The operation of 2710 may be performed according to the methods described herein. In some examples, the operation of 2710 may be performed by a PUR request manager as described with reference to Figures 14-17.

[0318] In 2715, the base station may send a PUR configuration message to the UE in response to a PUR request message, where the PUR configuration indicates the uplink resources for the response message from the UE. The operation of 2715 may be performed according to the methods described herein. In some examples, the operation of 2715 may be performed by a PUR configuration manager, as described with reference to Figures 14 to 17.

[0319] Figure 28 shows a flowchart illustrating a method 2800 supporting a PUR technique in wireless communications according to an aspect of this disclosure. The operation of method 2800 may be carried out by a base station 105 or its components as described herein. For example, the operation of method 2800 may be carried out by a communications manager as described with reference to Figures 14 to 17. In some examples, the base station may execute a set of instructions to control the base station's functional elements to perform the functions described below. In addition or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

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

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

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

[0323] Figure 29 shows a flowchart illustrating method 2900 supporting the PUR technique in wireless communications according to aspects of this disclosure. The operation of method 2900 may be performed by a base station 105 or its components as described herein. For example, the operation of method 2900 may be performed by a communications manager as described with reference to Figures 14 to 17. In some examples, the base station may execute a set of instructions to control the base station's functional elements to perform the functions described below. In addition or alternatively, the base station may perform aspects of the functions described below using dedicated hardware.

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

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

[0326] In 2915, the base station may, in response to a PUR request message, 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 will 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 operation of 2915 may be performed by a PUR configuration manager, as described with reference to Figures 14-17.

[0327] It should be noted that the methods described herein represent possible implementations, that the operations and steps may be reconfigured or otherwise modified, and that other implementations are possible. Furthermore, two or more embodiments of the methods may be combined.

[0328] The techniques described herein can be used for a variety of wireless communication systems, including Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems may implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. IS-2000 releases are sometimes referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is sometimes referred to as CDMA2000 1xEV-DO, High-Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA®) and other variations of CDMA. TDMA systems may implement radio technologies such as Global System for Mobile Communications (GSM).

[0329] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Advanced UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the "Third Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "Third Generation Partnership Project II" (3GPP2). The techniques described herein may be used for the systems and radio technologies described herein as well as for other systems and radio technologies. Embodiments of LTE, LTE-A, LTE-A Pro, or NR systems may be described as examples, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used for the majority of the description; however, the techniques described herein are applicable to applications other than those of LTE, LTE-A, LTE-A Pro, or NR.

[0330] Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UEs (User Entities) subscribed to a network provider's service. Small cells may be associated with lower-power base stations compared to macrocells and may operate in the same or different frequency bands as macrocells (e.g., licensed frequency bands, unlicensed frequency bands, etc.). Small cells may include picocells, femtocells, and microcells, depending on various examples. Picocells may cover small geographical areas, for example, and can enable unrestricted access by UEs subscribed to a network provider's service. Femtocells may also cover small geographical areas (e.g., a home) and can provide restricted access by UEs associated with femtocells (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). eNBs for macrocells are sometimes called macro eNBs. eNBs for small cells are sometimes called small cell eNBs, pico eNBs, femto eNBs, or home eNBs. The eNB may support one or more cells (for example, two, three, or four) and may also support communication using one or more component carriers.

[0331] The wireless communication systems described herein may support synchronous or asynchronous operation. In synchronous operation, base stations may have similar frame timings, and transmissions from different base stations may be approximately time-synchronized. In asynchronous operation, base stations may have different frame timings, and transmissions from different base stations may not be time-synchronized. The techniques described herein may be used for either synchronous or asynchronous operation.

[0332] The information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0333] The various exemplary blocks and modules described in relation to the disclosure herein may be implemented or run using general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, 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 working with a DSP core, or any other such configuration).

[0334] The functions described herein 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 codes. Other examples and implementations fall within the scope of this disclosure and the accompanying claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.

[0335] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-temporary storage media may be any available media that can be accessed by a general-purpose computer or a dedicated computer. Examples, but not limitations, of non-temporary computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and that can be accessed by a general-purpose computer or a dedicated computer or a general-purpose processor or a dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then 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, LaserDisc®, OpticalDisc, Digital Multipurpose Disc (DVD)®, FloppyDisc, and Blu-ray® Disc, where disk typically reproduces data magnetically and disc optically using a laser. Combinations of the above are also included in the scope of computer-readable media.

[0336] When used herein, including in the claims, the “or” used in an enumeration of items (for example, an enumeration of items ending with a phrase such as “at least one of” or “one or more of”) indicates an inclusive enumeration, such as the enumeration “at least one of A, B, or C” meaning A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, the phrase “based on” as used herein should not be interpreted 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 this disclosure. In other words, the phrase “based on” as used herein should be interpreted in the same way as the phrase “at least partially based on.”

[0337] In the attached diagrams, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If 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 descriptions provided herein with respect to the accompanying drawings are illustrative and do not necessarily represent all examples that may be implemented or fall within the scope of the claims. The term “exemplary” as used herein means “acting as an example, case, or illustration,” and does not mean “preferred” or “advantageous over other examples.” Detailed descriptions include specific details to facilitate understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.

[0339] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this 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 this disclosure. Accordingly, this disclosure should be given the broadest scope that is consistent with the principles and novel features disclosed herein, and is not limited to the examples and designs described herein. [Explanation of symbols]

[0340] 100 Wireless Communication Systems 105 Base station 110 Geographic Coverage Areas 115 User Equipment (UE) 125 Communication Link 130 Core Network 132, 134 Backhaul Link 200 Wireless Communication Systems 205 Downlink transmission 210 Uplink transmission 215 PUR display 220 PUR allocation 225 PUR request 230 Uplink Data 1005 devices 1010 Receiver 1015 Communications Manager 1020 Transmitter 1105 devices 1110 Receiver 1115 Communications Manager 1120 PUR determination component 1125 PUR Request Manager 1130 PUR Configuration Manager 1135 PUR Sending Manager 1140 EDT Random Access Manager 1145 Transmitter 1205 Communications Manager 1210 PUR determination component 1215 PUR Request Manager 1220 PUR Configuration Manager 1225 PUR Sending Manager 1230 EDT Random Access Manager 1235 PUR Response Manager 1240 Paging Manager 1245 RRC Manager 1250 PUR Authorization Manager 1305 devices 1310 Communications Manager 1315 I / O Controller 1320 Transceiver 1325 Antenna 1330 memory 1335 Computer executable code 1340 processor 1345 Bus 1405 Devices 1410 Receiver 1415 Communications Manager 1420 Transmitter 1505 Device 1510 Receiver 1515 Communications Manager 1520 PUR Configuration Manager 1525 PUR Request Manager 1530 PUR Response Manager 1535 EDT Random Access Manager 1540 Transmitter 1605 Communications Manager 1610 PUR Configuration Manager 1615 PUR Request Manager 1620 PUR Response Manager 1625 EDT Random Access Manager 1630 Paging Manager 1635 PUR Authorization Manager 1705 devices 1710 Communications Manager 1715 Network Communications Manager 1720 Transceiver 1725 Antenna 1730 memory 1735 Computer-readable code 1740 Processor 1745 Inter-station communications manager 1750 Bus

Claims

1. A device for wireless communication in an access network entity, One or more processors, One or more memories coupled to the one or more processors, One or more processor-readable instructions stored in the one or more memory and The device includes, and the one or more processor-readable instructions are provided to the device, Sending a message indicating that the access network entity supports the pre-configured uplink resource (PUR) associated with grant-free uplink transmission, Receiving a PUR request message, wherein the PUR request message includes the number of instances of PUR permission from the user equipment (UE), and a number of instances that is 0 indicates that the PUR configuration will be released. Sending a PUR configuration in response to the PUR request message, wherein the PUR configuration includes a set of control channel resources for uplink authorization associated with the UE. An apparatus that can be executed by one or more processors to perform the following.

2. The apparatus according to claim 1, wherein the number of instances of the PUR authorization provides an indication of an explicit number of PUR authorizations or an indeterminate number of PUR authorizations.

3. The apparatus according to claim 1, wherein the number of instances of the PUR authorization from the UE indicates that a one-shot PUR configuration is required or a multi-shot PUR configuration is required.

4. The apparatus according to claim 1, wherein the PUR configuration is the previous PUR configuration of the UE.

5. The apparatus according to claim 1, wherein the PUR configuration is the default PUR configuration.

6. The one or more processor-readable instructions stored in the one or more memory are transmitted to the device. Based on the transmission of the PUR configuration, a PUR reconfiguration failure indication is received. The apparatus according to claim 1, further capable of being executed by one or more processors to perform the following.

7. The one or more processor-readable instructions stored in the one or more memory are transmitted to the device. To transmit a display of a delta configuration showing at least one difference beyond the configuration of the aforementioned UE. The one or more processors can further perform the following: The apparatus according to claim 1.

8. One or more processor-readable instructions stored in one or more of the memory, which can be executed by one or more processors to cause the device to receive the PUR request message, are provided to the device. The PUR request message is received within the uplink message of the early data transmission procedure. The apparatus according to claim 1, further executable by one or more processors to perform the following.

9. The PUR request message is formatted for reception in the uplink message of the Early Data Transmission Procedure. The apparatus according to claim 8, wherein the PUR request message indicates a requested PUR configuration or the release of the PUR configuration.

10. One or more processor-readable instructions stored in one or more of the memory, which can be executed by one or more processors to cause the device to receive the PUR request message, are provided to the device. The PUR request message is received during the transmission of message 3 (MSG3) of the aforementioned early data transmission procedure. The apparatus according to claim 8, further executable by one or more processors to perform the following.

11. One or more processor-readable instructions stored in one or more memories and executable by one or more processors to cause the device to transmit the PUR configuration are transmitted to the device. In an early data transmission downlink message (MSG4) that provides a wireless resource control connection release message or a wireless resource control early data completion message, the PUR configuration is transmitted. The apparatus according to claim 1, further executable by one or more processors to perform the following.

12. The aforementioned PUR configuration is either explicit or implicit, One or more indications for deconfiguring and releasing a previous or default PUR configuration, a new resource associated with a new PUR configuration for use as said PUR configuration, or a combination thereof. The apparatus according to claim 1, which provides...

13. A device for wireless communication in an access network entity, One or more processors, One or more memories coupled to the one or more processors, One or more processor-readable instructions stored in the one or more memory and The device includes, and the one or more processor-readable instructions are provided to the device, Sending a message indicating that the access network entity supports the pre-configured uplink resource (PUR) associated with grant-free uplink transmission, Receiving a PUR request message, wherein the PUR request message includes the number of instances of PUR permission from the user equipment (UE), and a number of instances that is 0 indicates that the PUR configuration will be released. Sending a PUR configuration in response to the aforementioned PUR request message, Broadcasting system information indicating that PUR is not supported An apparatus that can be executed by one or more processors to perform the following.

14. The apparatus according to claim 13, wherein the number of instances of the PUR permission provides an indication of an explicit number of PUR permissions or an indeterminate number of PUR permissions.

15. A method for wireless communication in an access network entity, The steps include sending a message indicating that the access network entity supports a pre-configured uplink resource (PUR) associated with grant-free uplink transmission, A step of receiving a PUR request message, wherein the PUR request message includes the number of instances of PUR permission from the user equipment (UE), and a number of instances that is 0 indicates that the PUR configuration will be released. A step of sending a PUR configuration in response to the PUR request message, wherein the PUR configuration includes a set of control channel resources for uplink authorization associated with the UE. Methods that include...

16. The method according to claim 15, wherein the number of instances of the PUR permission provides an indication of an explicit number of PUR permissions or an indeterminate number of PUR permissions.

17. The method according to claim 15, wherein the number of instances of the PUR authorization from the UE indicates that a one-shot PUR configuration is requested or a multi-shot PUR configuration is requested.

18. The method according to claim 15, wherein the PUR configuration is a previous PUR configuration of the UE.

Images