Techniques for requesting uplink transmission resources for maximum permitted exposure reporting

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may identify a maximum permitted exposure (MPE) event associated with a beam; determine that physical uplink control channel (PUCCH) resources for transmitting a scheduling request are unavailable based at least in part on identifying the MPE event associated with the beam; and initiate a physical random access channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable. Numerous other aspects are provided.

Description

[0001] public domain

[0002] Aspects of the present disclosure generally relate to techniques and apparatus for wireless communications and techniques for requesting uplink transmission resources for maximum permitted exposure reporting.

[0003] Related technical description

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless communication network may include several base stations (BSs) capable of supporting communications for several user equipment (UEs). User equipment (UEs) may communicate with the base stations (BSs) via downlinks and uplinks. The downlink (or forward link) refers to the communication link from the BS to the UE, while the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, 5G Node B, and so on.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies.

[0007] Overview

[0008] In some aspects, a wireless communication method performed by a UE may include: identifying a maximum permitted exposure (MPE) event associated with a beam; determining that a physical uplink control channel (PUCCH) resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; and initiating a physical random access channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUCCH resource is unavailable.

[0009] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a physical uplink shared channel transmission.

[0010] In some aspects, initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

[0011] In some aspects, the method includes determining that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or the additional MPE event being associated with an additional beam associated with the additional PUCCH resources, and initiating the PRACH procedure based at least in part on determining that the additional PUCCH resources are unavailable.

[0012] In some aspects, the PRACH procedure comprises one of: contention-based PRACH, contention-free PRACH, or two-step PRACH.

[0013] In some aspects, the method includes selecting a PRACH type from one or more candidate PRACH types, and the one or more candidate PRACH types include one or more of: a contention-based PRACH type, a contention-free PRACH type, or a two-step PRACH type.

[0014] In some aspects, selecting the PRACH type includes: selecting a contention-free PRACH type if the contention-free PRACH type is available; selecting a two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; and selecting a contention-based PRACH type if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

[0015] In some aspects, initiating the PRACH procedure includes transmitting a message 1 of a contention-based PRACH procedure or a contention-free PRACH procedure.

[0016] In some aspects, the method includes receiving an uplink grant to transmit the uplink message.

[0017] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0018] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0019] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0020] In some aspects, the method includes transmitting the uplink message.

[0021] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0022] In some aspects, a wireless communication method performed by a UE may include: identifying an MPE event associated with a beam; determining that a physical uplink shared channel (PUSCH) resource for transmitting an uplink message is unavailable based at least in part on identifying the MPE event associated with the beam; and initiating a reporting procedure, wherein initiating the reporting procedure includes: initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUSCH resource is unavailable, or transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource.

[0023] In some aspects, the method includes determining not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

[0024] In some aspects, the method includes determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

[0025] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a PUSCH transmission.

[0026] In some aspects, the method includes transmitting the uplink message.

[0027] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0028] In some aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0029] In some aspects, transmitting the scheduling request via the MPE-specific PUCCH resource includes transmitting the scheduling request via the MPE-specific PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

[0030] In some aspects, the method includes receiving an uplink grant to transmit the uplink message.

[0031] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0032] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0033] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0034] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the at least one processor may be configured to: identify an MPE event associated with a beam; determine that PUCCH resources for transmitting a scheduling request are unavailable based at least in part on identifying the MPE event associated with the beam; and initiate a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable.

[0035] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a physical uplink shared channel transmission.

[0036] In some aspects, initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

[0037] In some aspects, the one or more processors may be configured to determine that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or the additional MPE event being associated with the additional beam associated with the additional PUCCH resources, and to initiate the PRACH procedure based at least in part on determining that the additional PUCCH resources are unavailable.

[0038] In some aspects, the PRACH procedure comprises one of: contention-based PRACH, contention-free PRACH, or two-step PRACH.

[0039] In some aspects, the one or more processors may be configured to select a PRACH type from one or more candidate PRACH types, and the one or more candidate PRACH types include one or more of: a contention-based PRACH type, a contention-free PRACH type, or a two-step PRACH type.

[0040] In some aspects, selecting the PRACH type includes: selecting a contention-free PRACH type if the contention-free PRACH type is available; selecting a two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; and selecting a contention-based PRACH type if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

[0041] In some aspects, initiating the PRACH procedure includes transmitting a message 1 of a contention-based PRACH procedure or a contention-free PRACH procedure.

[0042] In some aspects, the one or more processors may be configured to receive an uplink grant to transmit the uplink message.

[0043] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0044] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0045] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0046] In some aspects, the one or more processors may be configured to transmit the uplink message.

[0047] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0048] In some aspects, a UE for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the at least one processor may be configured to: identify an MPE event associated with a beam; determine that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying the MPE event associated with the beam; and initiate a reporting procedure, wherein initiating the reporting procedure includes: initiating a PRACH procedure for transmitting the uplink message based at least in part on determining that the PUSCH resources are unavailable, or transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource.

[0049] In some aspects, the one or more processors may be configured to determine not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

[0050] In some aspects, the one or more processors may be configured to determine not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

[0051] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a PUSCH transmission.

[0052] In some aspects, the one or more processors may be configured to transmit the uplink message.

[0053] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0054] In some aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0055] In some aspects, transmitting the scheduling request via the MPE-specific PUCCH resource includes transmitting the scheduling request via the MPE-specific PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

[0056] In some aspects, the one or more processors may be configured to receive an uplink grant to transmit the uplink message.

[0057] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0058] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0059] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0060] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to identify an MPE event associated with a beam; determine that PUCCH resources for transmitting a scheduling request are unavailable based at least in part on identifying the MPE event associated with the beam; and initiate a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable.

[0061] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a physical uplink shared channel transmission.

[0062] In some aspects, initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

[0063] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to: determine that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or the additional MPE event being associated with the additional beam associated with the additional PUCCH resources, and initiate the PRACH procedure based at least in part on determining that the additional PUCCH resources are unavailable.

[0064] In some aspects, the PRACH procedure comprises one of: contention-based PRACH, contention-free PRACH, or two-step PRACH.

[0065] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to: select a PRACH type from one or more candidate PRACH types, and the one or more candidate PRACH types include one or more of the following: a contention-based PRACH type, a contention-free PRACH type, or a two-step PRACH type.

[0066] In some aspects, selecting the PRACH type includes: selecting a contention-free PRACH type if the contention-free PRACH type is available; selecting a two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; and selecting a contention-based PRACH type if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

[0067] In some aspects, initiating the PRACH procedure includes transmitting a message 1 of a contention-based PRACH procedure or a contention-free PRACH procedure.

[0068] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to: receive an uplink grant to transmit the uplink message.

[0069] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0070] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0071] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0072] In some aspects, the one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: transmit the uplink message.

[0073] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0074] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to identify an MPE event associated with a beam; determine that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying the MPE event associated with the beam; and initiate a reporting procedure, wherein initiating the reporting procedure includes: initiating a PRACH procedure for transmitting the uplink message based at least in part on determining that the PUSCH resources are unavailable, or transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource.

[0075] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to determine not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

[0076] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to: determine not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

[0077] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a PUSCH transmission.

[0078] In some aspects, the one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: transmit the uplink message.

[0079] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0080] In some aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0081] In some aspects, transmitting the scheduling request via the MPE-specific PUCCH resource includes transmitting the scheduling request via the MPE-specific PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

[0082] In some aspects, the one or more instructions, when executed by one or more processors of the UE, may cause the one or more processors to: receive an uplink grant to transmit the uplink message.

[0083] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0084] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0085] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0086] In some aspects, an apparatus for wireless communication may include: a device for identifying an MPE event associated with a beam; a device for determining that PUCCH resources for transmitting a scheduling request are unavailable based at least in part on identifying the MPE event associated with the beam; and a device for initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable.

[0087] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a physical uplink shared channel transmission.

[0088] In some aspects, initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

[0089] In some aspects, the apparatus may include means for determining that additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or an additional MPE event being associated with an additional beam associated with the additional PUCCH resource, and initiating the PRACH procedure based at least in part on determining that the additional PUCCH resources are unavailable.

[0090] In some aspects, the PRACH procedure comprises one of: contention-based PRACH, contention-free PRACH, or two-step PRACH.

[0091] In some aspects, the apparatus may include means for selecting a PRACH type from one or more candidate PRACH types, and the one or more candidate PRACH types may include one or more of a contention-based PRACH type, a contention-free PRACH type, or a two-step PRACH type.

[0092] In some aspects, selecting the PRACH type includes: selecting a contention-free PRACH type if the contention-free PRACH type is available; selecting a two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; and selecting a contention-based PRACH type if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

[0093] In some aspects, initiating the PRACH procedure includes transmitting a message 1 of a contention-based PRACH procedure or a contention-free PRACH procedure.

[0094] In some aspects, the apparatus may include means for receiving an uplink grant to transmit the uplink message.

[0095] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0096] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0097] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0098] In some aspects, the apparatus may include means for transmitting the uplink message.

[0099] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0100] In some aspects, an apparatus for wireless communication may include: a device for identifying an MPE event associated with a beam; a device for determining that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying the MPE event associated with the beam; and a device for initiating a reporting procedure, wherein initiating the reporting procedure includes: a device for initiating a PRACH procedure for transmitting the uplink message based at least in part on determining that the PUSCH resources are unavailable, or a device for transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource.

[0101] In some aspects, the apparatus may include means for determining not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

[0102] In some aspects, the apparatus may include means for determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

[0103] In some aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a PUSCH transmission.

[0104] In some aspects, the apparatus may include means for transmitting the uplink message.

[0105] In some aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0106] In some aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0107] In some aspects, transmitting the scheduling request via the MPE-specific PUCCH resource includes transmitting the scheduling request via the MPE-specific PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

[0108] In some aspects, the apparatus may include means for receiving an uplink grant to transmit the uplink message.

[0109] In some aspects, the uplink grant is an MPE-specific uplink grant.

[0110] In some aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resources associated with the MPE event.

[0111] In some aspects, the uplink grant indicates a new beam to be used to transmit the uplink message.

[0112] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described herein with reference to and as illustrated in the accompanying figures and description.

[0113] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The concepts and specific examples disclosed can be readily used as a basis for modifying or designing other structures for implementing the same purposes as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, as well as the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures is provided for illustration and description purposes and is not intended to define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] In order to understand in detail the features of the present disclosure set forth above, a more particular description of the content briefly summarized above may be obtained with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0116] Figure 1 is a diagram illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0117] Figure 2is a diagram illustrating an example of a base station and a UE in communication in a wireless communication network according to various aspects of the present disclosure.

[0118] Figure 3 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0119] Figure 4 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0120] Figure 5 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0121] Figure 6 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0122] Figure 7 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0123] Figure 8 is a diagram illustrating an example of identifying MPE events associated with beams according to various aspects of the present disclosure.

[0124] Figure 9 is a diagram illustrating example processes performed, for example, by a UE, according to various aspects of the present disclosure.

[0125] Figure 10 is a diagram illustrating example processes performed, for example, by a UE, according to various aspects of the present disclosure.

[0126] Figure 11 is a diagram illustrating example processes performed, for example, by a UE, according to various aspects of the present disclosure.

[0127] Figure 12 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus according to various aspects of the present disclosure.

[0128] Detailed description

[0129] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and they will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently of any other aspect of the present disclosure or implemented in combination. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using a supplement to the various aspects of the present disclosure set forth herein or other other structures, functionality, or structure and functionality. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

[0130] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0131] It should be noted that although various aspects may be described herein using terminology generally associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applicable in communication systems based on other generations, such as 5G and later generations, including NR technology.

[0132] Figure 1 1 is a diagram illustrating a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include several BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0133] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in FIG, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "TRP," "AP," "Node B," "5G NB," and "cell" may be used interchangeably herein.

[0134] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0135] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in , relay station 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, relay base station, relay, or the like.

[0136] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0137] The network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. These BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0138] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0139] Some UEs may be considered machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and the like, which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as a processor component, a memory component, and the like.

[0140] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0141] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this scenario, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0142] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 Examples described.

[0143] Figure 2 A block diagram shows a design 200 of a base station 110 and a UE 120, which may be Figure 1 One for each base station and one for each UE in . Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0144] At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)). A transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in greater detail below, position coding may be utilized to generate synchronization signals to convey additional information.

[0145] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0146] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from the controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Network controller 130 may include communication unit 294, controller / processor 290, and memory 292.

[0147] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component(s) of the base station 110 may perform one or more operations associated with the techniques for requesting uplink transmission resources for maximum permitted exposure (MPE) reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) may perform or direct e.g. Figure 9 The process of 900 Figure 10 The process of 1000 Figure 11 1100, and / or operations of other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120, may perform or direct, for example, Figure 9 The process of 900 Figure 10 The process of 1000 Figure 11 The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0148] In some aspects, the UE 120 may include: means for identifying an MPE event associated with a beam; means for determining that a PUCCH resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; means for initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resource is unavailable; and the like. In some aspects, such means may include in conjunction with Figure 2 One or more components of the UE 120 are depicted, such as the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0149] In some aspects, the UE 120 may include: means for identifying an MPE event associated with a beam; means for determining that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying the MPE event associated with the beam; means for initiating a reporting procedure, wherein initiating the reporting procedure includes: initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or transmitting a scheduling request to transmit an uplink message via an MPE-dedicated PUCCH resource; etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of the UE 120 are depicted, such as the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and the like.

[0150] As indicated above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 Examples described.

[0151] Figure 3 is a diagram illustrating an example 300 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure.

[0152] As in Figure 3 In the figure and as shown by reference numeral 310, the UE and the base station can communicate using directional beams. In some wireless networks, the UE can communicate with the base station by using directional beamforming to boost the transmit power in one or more specific directions associated with one or more beams. By concentrating the transmit power in one or more beams, the output energy associated with transmissions using the one or more beams can be higher than the output energy when the UE performs omnidirectional transmissions for those transmissions. This may increase the range of the transmission, but may also result in the energy density of the transmission meeting (e.g., exceeding) an MPE value, which defines the highest energy density allowed for close exposure to the human body. The MPE value may be defined via radio resource control (RRC) configuration, for example, to comply with standards and / or regulations. The standards and / or regulations may have different limits for different frequency bandwidths. For example, the limits (e.g., corresponding to the MPE values) may be lower for millimeter wave (mmWave) than for sub-6 wave transmissions.

[0153] As indicated by reference numeral 320, the UE may identify an MPE event. The UE may identify an MPE event based, at least in part, on detecting a portion of a human body and / or other organic material within a path of an uplink beam at a close distance to the UE. Based, at least in part, on detecting the portion of a human body in a direction for which a beam with an energy density that satisfies MPE would be used for transmission, the UE may reduce the transmit power of one or more antennas associated with the beam. However, by reducing the transmit power of one or more antennas associated with the beam, the transmission may have insufficient power for the base station to receive the transmission. This may result in a beam failure.

[0154] As shown by reference numeral 330, the UE may continue to communicate with the base station by using a new beam for uplink communication. The new beam may be in a different direction than the beam associated with the MPE event. In some discussions below, an MPE event may be referred to as an uplink beam failure.

[0155] As indicated above, Figure 3 are provided as examples. Other examples may differ from those described in Figure 3 Examples described.

[0156] Figure 4 is a diagram illustrating an example 400 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure.

[0157] As in Figure 4 In the embodiment and indicated by reference numeral 410, a UE may identify an MPE event. The UE may identify the MPE event based at least in part on detecting a portion of a human body or other organic object at a close distance to the UE within a path of a current beam resource (e.g., a PUSCH). The UE may further identify the MPE event based at least in part on determining that reducing transmit power of one or more antennas to comply with an MPE metric may result in a transmission using the current beam resource not having sufficient power for the transmission to be received by a base station.

[0158] As indicated by reference numeral 420, the UE may transmit a scheduling request (SR) to the base station. The UE may transmit the SR to the base station using uplink resources (e.g., PUCCH). The transmit beam associated with the PUCCH resource may be preconfigured by higher layer signaling (such as RRC or media access control element (MAC-CE) signaling). The uplink resource may be associated with a beam different from the current beam associated with the MPE event. However, if the beam associated with the uplink resource is also affected by the MPE event, the uplink resource may be unavailable.

[0159] As indicated by reference numeral 430, the UE may receive an uplink grant from the base station. The UE may receive the uplink grant based at least in part on the base station receiving the SR. In other words, if the uplink resource is not associated with a beam associated with an MPE event, the UE may receive the uplink grant. The uplink grant may identify uplink resources for the UE to use to transmit an uplink message.

[0160] As indicated by reference numeral 440, the UE may transmit an uplink message via the uplink resource. For example, the UE may transmit a report of an MPE event, a report for an uplink beam failure event, a report for a beam failure recovery event, and the like.

[0161] As indicated above, Figure 4 are provided as examples. Other examples may differ from those described in Figure 4 Examples described.

[0162] The UE may attempt to transmit an SR via an uplink resource even if the uplink resource is associated with a beam associated with an MPE event. Regardless of whether the uplink resource is associated with an MPE event, attempting to transmit an SR via the uplink resource may consume computational, communication, and / or network resources for the base station and the UE to determine that power used to transmit the SR using the uplink resource is insufficient for the base station to receive a transmission and to recover from unreceived transmissions. Furthermore, a delay based at least in part on waiting to attempt to transmit an SR via the uplink resource before attempting another procedure for requesting resources may result in synchronization errors between the UE and the base station.

[0163] In some aspects described herein, a UE (e.g., UE 120) may identify an MPE event associated with a beam and determine whether uplink resources (e.g., PUCCH resources) are available for transmitting a scheduling request. In some aspects, the UE may determine whether the uplink resources are available based at least in part on identifying the MPE event associated with the beam. Based at least in part on determining that the uplink resources are not available, the UE may determine whether another uplink resource associated with a scheduling request is available. In some aspects, the UE may skip one or more scheduling opportunities for one or more uplink resources (e.g., one or more uplink resources associated with one or more beams associated with the MPE event). Based at least in part on skipping one or more opportunities for transmitting a scheduling request, the UE may instead initiate a PRACH procedure to request an uplink grant. The transmit beam associated with the PRACH procedure may not be preconfigured and may be determined by the UE. For example, the UE may initiate a PRACH procedure to request an uplink grant for transmitting a MAC-CE-based report for an MPE event and / or a beam failure recovery event. In this way, the UE may save computational, communication, and / or network resources that may have been used to first attempt to transmit the SR using uplink resources associated with the beam associated with the MPE event.

[0164] Figure 5 is a diagram illustrating an example 500 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure. Figure 5 As shown in FIG, a UE (e.g., UE 120) may communicate with a base station (e.g., base station 110) to request uplink resources for transmitting an uplink message (e.g., a report of an MPE event). The UE and the base station may be part of a wireless network (e.g., wireless network 100).

[0165] As indicated by reference numeral 510, the UE may identify an MPE event and / or determine that PUSCH resources are unavailable. In some aspects, the UE may determine that the MPE event is associated with one or more beams through which the UE communicates with the base station. In some aspects, the UE may determine that one or more uplink resources (e.g., one or more PUSCH resources) are unavailable based at least in part on the MPE event. For example, a beam failure of one or more beams through which the UE communicates with the base station may be based at least in part on the MPE event. In some aspects, one or more resources may be unavailable based at least in part on their association with the one or more beams determined to be in beam failure.

[0166] As indicated by reference numeral 520, the UE may determine that PUCCH resources are unavailable. In some aspects, the UE may determine that the PUCCH resources are associated with resources requested for transmitting uplink messages associated with PUSCH (e.g., reporting of MPE events, beam failure recovery events, etc.). In some aspects, the UE may determine that one or more additional PUCCH resources for transmitting a scheduling request are unavailable (e.g., based at least in part on the MPE event). In some aspects, the UE may determine that no PUCCH resources, and / or other uplink resources, are available to transmit an SR request for resources for transmitting uplink messages.

[0167] In some aspects, the UE may determine not to transmit (e.g., determine to skip transmitting) an SR via a PUCCH resource associated with a PUSCH based at least in part on identifying an MPE event. In some aspects, the UE may determine not to transmit an SR via a PUCCH resource associated with beam failure recovery based at least in part on identifying an MPE event. In other words, the UE may determine not to transmit an SR via an unavailable PUCCH resource based at least in part on identifying an MPE event.

[0168] As indicated by reference numeral 530, the UE may initiate a PRACH procedure. In some aspects, the UE may determine to initiate a PRACH procedure based at least in part on determining that PUCCH resources for transmitting the SR are unavailable. In some aspects, the UE may determine to initiate a PRACH procedure based at least in part on determining that one or more additional PUCCH resources are unavailable. In some aspects, the UE may ignore one or more SR opportunities for one or more PUCCH resources (e.g., one or more SR-PUCCHs) and trigger a PRACH procedure without waiting to determine whether the SR is received by the base station.

[0169] In some aspects, the PRACH procedure may include contention-based PRACH, contention-free PRACH, or two-step PRACH. In some aspects, the UE may select a PRACH type for the PRACH procedure. For example, the UE may select a PRACH type from one or more candidate PRACH types, such as contention-based PRACH, contention-free PRACH, or two-step PRACH. In some aspects, if the contention-free PRACH type is available, the UE may select the contention-free PRACH type. If the contention-free PRACH type is not available, the UE may select the two-step PRACH type if the two-step PRACH type is available. If the contention-free PRACH type is not available and the two-step PRACH type is not available, the UE may select the contention-based PRACH type if the contention-based PRACH type is available.

[0170] In some aspects, initiating a PRACH procedure may include transmitting a message 1 for a contention-based PRACH procedure or a contention-free PRACH procedure. In some aspects, initiating a PRACH procedure may include transmitting a message A for a 2-step PRACH procedure.

[0171] In some aspects, the UE may initiate a PRACH procedure by transmitting Message 1 or Message A via a new beam that is different from the beam associated with the PUSCH and / or PUCCH associated with the MPE event. In some aspects, the UE may determine that the new beam does not have an MPE event, another MPE event, and / or a beam failure event. In other words, the transmission using the new beam may have sufficient power to be received by the base station.

[0172] As indicated by reference numeral 540, the UE may receive an uplink grant from the base station for scheduling one or more uplink resources to transmit an uplink message. In some aspects, the UE may receive the uplink grant via current downlink resources associated with a current beam (e.g., a beam associated with a PUCCH and / or an MPE event). In some aspects, the UE may receive the uplink grant within a downlink control information (DCI) message. In some aspects, the uplink grant may be an MPE-specific uplink grant.

[0173] In some aspects, the uplink grant may indicate a new beam to be used to transmit the uplink message.In some aspects, the uplink grant may indicate that the UE will transmit the uplink message using the same beam as the beam through which the UE initiated the PRACH procedure.

[0174] As indicated by reference numeral 550, the UE may transmit an uplink message. In some aspects, the uplink message may include a report of an MPE event, a beam failure report, a PUSCH transmission, etc. In some aspects, the uplink message may include a MAC-CE report for an MPE event, a beam failure recovery event, etc. In some aspects, the UE may transmit the uplink message via a new beam. In some aspects, the new beam may be the same beam used to initiate the PRACH procedure. In some aspects, the new beam may be the beam indicated in the uplink grant.

[0175] By skipping transmitting the SR using uplink resources associated with the beam associated with the MPE event and instead initiating a PRACH process, the UE can save computing, communication, and / or network resources that would otherwise be used to transmit the SR without sufficient power to be received by the base station.

[0176] As indicated above, Figure 5 are provided as examples. Other examples may differ from those described in Figure 5 Examples described.

[0177] Figure 6 is a diagram illustrating an example 600 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure. Figure 6 As shown in FIG, a UE (e.g., UE 120) may communicate with a base station (e.g., base station 110) to request uplink resources for transmitting an uplink message (e.g., a report of an MPE event). The UE and the base station may be part of a wireless network (e.g., wireless network 100).

[0178] As in Figure 6 In the embodiment and indicated by reference numeral 610, the UE may identify an MPE event associated with one or more beams and / or determine that PUSCH resources are unavailable. The PUSCH resources may be associated with at least one of the one or more beams associated with the MPE event.

[0179] As indicated by reference numeral 620, the UE may determine that PUCCH resources are available. In some aspects, the PUCCH resources may be associated with a beam that is different from the one or more beams associated with the MPE event. In some aspects, the UE may determine whether to transmit the SR via the PUCCH resources or to initiate a PRACH procedure based at least in part on whether the one or more PUCCH resources are available (e.g., associated with the one or more beams associated with the MPE event). In some aspects, the UE initiates a PRACH procedure only if the UE does not have PUCCH resources available to request resources for transmitting an uplink message (e.g., a MAC-CE report for an MPE event). In other words, the UE may determine whether to initiate a PRACH procedure or to transmit the SR via uplink resources associated with the current beam.

[0180] The UE may transmit the SR as indicated by reference numeral 630. In some aspects, the SR does not include information indicating the message type of the uplink message. In some aspects, the SR may not indicate that an MPE event has occurred or that one or more beams are associated with an MPE event.

[0181] The UE may receive an uplink grant from the base station, as indicated by reference numeral 640. In some aspects, the UE may receive the uplink grant via downlink resources (e.g., a physical downlink control channel (PDCCH)) associated with a current beam (such as a beam associated with an MPE event or a beam not associated with an MPE event).

[0182] The UE may transmit an uplink message, as indicated by reference numeral 650. In some aspects, the UE may transmit the uplink message using the same beam used to transmit the SR for the uplink message. In some aspects, the UE may transmit the uplink message based at least in part on the beam and / or uplink resource identified by the uplink grant.

[0183] By determining whether the UE has uplink resources available to transmit an SR before determining to initiate a PRACH procedure, the UE may save computational, communication, and / or network resources that may otherwise have been used to perform the PRACH procedure.

[0184] As indicated above, Figure 6 are provided as examples. Other examples may differ from those described in Figure 6 Examples described.

[0185] Figure 7 is a diagram illustrating an example 700 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure. Figure 7As shown in FIG, a UE (e.g., UE 120) may communicate with a base station (e.g., base station 110) to request uplink resources for transmitting an uplink message (e.g., a report of an MPE event). The UE and the base station may be part of a wireless network (e.g., wireless network 100).

[0186] As in Figure 7 In the embodiment and indicated by reference numeral 710, the UE may identify an MPE event associated with one or more beams and / or determine that PUSCH resources are unavailable. The PUSCH resources may be associated with at least one of the one or more beams associated with the MPE event.

[0187] As indicated by reference numeral 720, the UE may determine that the first PUCCH resource is unavailable and the second PUCCH resource is available. In some aspects, the first PUCCH resource may be associated with a PUSCH resource (e.g., the first PUCCH resource may be configured for use by the UE to transmit an SR to request resource grant for reporting an MPE event). In some aspects, the first PUCCH resource may be associated with a beam associated with the MPE event, while the second PUCCH resource may be associated with another beam not associated with the MPE event.

[0188] As indicated by reference numeral 730, the UE may ignore the SR opportunity for the first PUCCH. The UE may determine to ignore (e.g., skip) the SR opportunity for the first PUCCH based at least in part on determining, based at least in part on the MPE event, that the transmit power of one or more antennas associated with a beam associated with the first PUCCH resource may be insufficient for the base station to receive the transmitted SR via the first PUCCH resource. In some aspects, the first PUCCH resource may be associated with a PUSCH resource, a beam failure recovery procedure, and the like.

[0189] As indicated by reference numeral 740, the UE may transmit an SR via a second PUCCH resource. The SR may indicate that the UE requests resources for transmitting an uplink message (e.g., a MAC-CE report for an MPE event). In some aspects, the UE may transmit the SR using the current beam configured for the second PUCCH resource.

[0190] As indicated by reference numeral 750, the UE may receive an uplink grant from the base station. In some aspects, the uplink grant may be included in a DCI message. In some aspects, the UE may receive the uplink grant via a beam associated with the first PUCCH resource, a beam associated with the second PUCCH resource, or another beam.

[0191] In some aspects, the uplink grant may indicate a new beam to be used to transmit the uplink message.In some aspects, the uplink grant may indicate that the UE is to transmit the uplink message using the same beam as the beam associated with the second PUCCH.

[0192] As indicated by reference numeral 760, the UE may transmit an uplink message. In some aspects, the UE may transmit the uplink message using the same beam (e.g., a beam associated with a second PUCCH) used to transmit the SR for the uplink message. In some aspects, the UE may transmit the uplink message based at least in part on the beam and / or uplink resource identified by the uplink grant.

[0193] By determining whether different uplink resources (e.g., uplink resources not associated with PUSCH resources) are available for transmitting the SR before determining to initiate a PRACH procedure, the UE may save computational, communication, and / or network resources that may otherwise have been used to perform the PRACH procedure.

[0194] As indicated above, Figure 7 are provided as examples. Other examples may differ from those described in Figure 7 Examples described.

[0195] Figure 8 is a diagram illustrating an example 800 of identifying MPE events associated with a beam in accordance with various aspects of the present disclosure. Figure 8 As shown in FIG, a UE (e.g., UE 120) may communicate with a base station (e.g., base station 110) to request uplink resources for transmitting an uplink message (e.g., a report of an MPE event). The UE and the base station may be part of a wireless network (e.g., wireless network 100).

[0196] As in Figure 8 In the embodiment and indicated by reference numeral 810, the UE may identify an MPE event associated with one or more beams and / or determine that PUSCH resources are unavailable. The PUSCH resources may be associated with at least one of the one or more beams associated with the MPE event.

[0197] As indicated by reference numeral 820, the UE may determine that PUCCH is available. In some aspects, the PUCCH resources may include MPE-specific PUCCH SR opportunities (e.g., dedicated SR-PUCCH). In some aspects, the PUCCH resources may be associated with beams that are not associated with MPE events and / or PUSCH. For example, the transmit beam associated with the PUCCH resources may be determined by the UE rather than configured by the base station.

[0198] As indicated by reference numeral 830, the UE may receive a first uplink grant. In some aspects, the first uplink grant may be based at least in part on an SR transmitted by the UE prior to detecting the MPE event. The first uplink grant may be associated (e.g., by the UE) with a first uplink message that does not include a report for the MPE event. In some aspects, the first uplink grant may be associated with a beam associated with the MPE event.

[0199] As indicated by reference numeral 840, the UE may transmit the SR via MPE-dedicated resources (e.g., uplink resources dedicated to receiving requests for uplink grants for reporting MPE events, beam failure recovery events, etc.). In some aspects, the UE may transmit the SR via a beam different from the beam of the PUSCH resources.

[0200] In some aspects, the UE may have available PUSCH resources (e.g., based at least in part on receiving a first uplink grant) and may determine not to transmit a report for an MPE event via the PUSCH resources. Instead, the UE may transmit a new SR or initiate a PRACH procedure (e.g., as described herein). In some aspects, the UE may determine not to transmit a report for an MPE event via the PUSCH resources based at least in part on PUSCH resources associated with a beam associated with the MPE event, availability of MPE-dedicated resources, etc.

[0201] As indicated by reference numeral 850, the UE may receive a second uplink grant based at least in part on the new SR. In some aspects, the UE may receive a second uplink grant from the base station for scheduling one or more uplink resources to transmit a second uplink message including a report for the MPE event. In some aspects, the UE may receive the second uplink grant using downlink resources associated with a beam associated with the MPE event. In some aspects, the UE may receive the second uplink grant using downlink resources associated with a beam not associated with the MPE event.

[0202] The UE may transmit a first uplink message using uplink resources associated with the first uplink grant (e.g., using an associated beam), as indicated by reference numeral 860. In some aspects, the UE may determine to transmit the first uplink message based at least in part on a determination that the beam associated with the uplink resources is not associated with an MPE event.

[0203] As indicated by reference numeral 870, the UE may transmit a second uplink message. In some aspects, the UE may transmit the second uplink message using uplink resources (e.g., and associated beam) indicated in the second uplink grant. In some aspects, the UE may transmit the second uplink message using uplink resources associated with the beam used by the UE to transmit the SR.

[0204] By skipping using uplink resources associated with a beam that may be associated with an MPE event to transmit a report for an MPE event, and instead transmitting the SR via MPE-dedicated resources, the UE can save computing, communication, and / or network resources that could otherwise be used to attempt to transmit a report for the MPE event via uplink resources and recover from a base station that never received the report for the MPE event.

[0205] As indicated above, Figure 8 are provided as examples. Other examples may differ from those described in Figure 8 Examples described.

[0206] Figure 9 is a diagram illustrating an example process 900 , performed, for example, by user equipment, in accordance with various aspects of the present disclosure.

[0207] The UE may identify an uplink message for transmission, as indicated by reference numeral 910. For example, the uplink message may include a MAC-CE report for an MPE event, a beam failure recovery event, and the like.

[0208] As indicated by reference numeral 920, the UE may determine whether an MPE event is detected on an SR-like uplink resource. For example, the UE may detect an MPE event and determine whether the SR-like uplink resource is associated with a beam associated with the MPE event.

[0209] As indicated by reference numeral 930, the UE may trigger SR-like PUCCH resources based at least in part on determining that no MPE event is detected on SR-like uplink resources (eg, uplink resources that may be used to request an uplink grant).

[0210] As indicated by reference numeral 940, based at least in part on determining that an MPE event is detected on the SR-like uplink resources, the UE may trigger a PRACH procedure (e.g., as described herein).

[0211] As indicated above, Figure 9 are provided as examples. Other examples may differ from those described in Figure 9 Examples described.

[0212] Figure 10 is a diagram illustrating an example process 1000, performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120, etc.) performs operations associated with techniques for requesting uplink transmission resources for MPE reporting.

[0213] like Figure 10 As shown in , in some aspects, process 1000 may include identifying an MPE event associated with a beam (block 1010). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may identify an MPE event associated with a beam, as described above.

[0214] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include determining that PUCCH resources for transmitting a scheduling request are unavailable based at least in part on identifying an MPE event associated with the beam (block 1020). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may determine that PUCCH resources for transmitting a scheduling request are unavailable based at least in part on identifying an MPE event associated with the beam, as described above.

[0215] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable (block 1030). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may initiate a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable, as described above.

[0216] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0217] In a first aspect, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a physical uplink shared channel transmission.

[0218] In a second aspect, alone or in combination with the first aspect, initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

[0219] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes determining that the additional PUCCH resource for transmitting the scheduling request is unavailable based at least in part on the MPE event or the additional MPE event being associated with the additional beam associated with the additional PUCCH resource, and initiating the PRACH procedure based at least in part on determining that the additional PUCCH resource is unavailable.

[0220] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PRACH procedure comprises one of: contention-based PRACH, contention-free PRACH, or two-step PRACH.

[0221] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1000 includes selecting a PRACH type from one or more candidate PRACH types, and the one or more candidate PRACH types include one or more of the following: a contention-based PRACH type, a contention-free PRACH type, or a two-step PRACH type.

[0222] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, selecting the PRACH type includes: selecting a contention-free PRACH type when the contention-free PRACH type is available; selecting a two-step PRACH type when the contention-free PRACH type is not available and the two-step PRACH type is available; and selecting a contention-based PRACH type when the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

[0223] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, initiating the PRACH procedure includes transmitting a message 1 of a contention-based PRACH procedure or a contention-free PRACH procedure.

[0224] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1000 includes receiving an uplink grant to transmit the uplink message.

[0225] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the uplink grant is an MPE-specific uplink grant.

[0226] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resource associated with the MPE event.

[0227] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the uplink grant indicates a new beam to be used for transmitting the uplink message.

[0228] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 1000 includes transmitting the uplink message.

[0229] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0230] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0231] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 1000. Additionally or alternatively, two or more blocks of process 1000 may be executed in parallel.

[0232] Figure 11 is a diagram illustrating an example process 1100, performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120, etc.) performs operations associated with techniques for requesting uplink transmission resources for MPE reporting.

[0233] like Figure 11 As shown in , in some aspects, process 1100 may include identifying an MPE event associated with a beam (block 1110). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may identify an MPE event associated with a beam, as described above.

[0234] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include determining that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying an MPE event associated with the beam (block 1120). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may determine that PUSCH resources for transmitting an uplink message are unavailable based at least in part on identifying an MPE event associated with the beam, as described above.

[0235] like Figure 11As further shown in FIG, in some aspects, process 1100 may include initiating a reporting procedure, the initiating the reporting procedure comprising initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource (block 1130). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may initiate a reporting procedure, the initiating the reporting procedure comprising initiating a PRACH procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or transmitting a scheduling request to transmit the uplink message via an MPE-dedicated PUCCH resource, as described above.

[0236] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0237] In a first aspect, process 1100 includes determining not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

[0238] In a second aspect, alone or in combination with the first aspect, process 1100 includes determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

[0239] In a third aspect, alone or in combination with one or more of the first and second aspects, the uplink message comprises one or more of: a report of the MPE event, a beam failure report, or a PUSCH transmission.

[0240] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 includes transmitting the uplink message.

[0241] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, transmitting the uplink message includes transmitting the uplink message via a new beam.

[0242] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the new beam is the same beam used to initiate the PRACH procedure or transmit the scheduling request for the uplink message.

[0243] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, transmitting the scheduling request via the MPE dedicated PUCCH resource includes: transmitting the scheduling request via the MPE dedicated PUCCH resource via an additional beam, which is different from the beam of the PUSCH resource.

[0244] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1100 includes receiving an uplink grant to transmit the uplink message.

[0245] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the uplink grant is an MPE-specific uplink grant.

[0246] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving the uplink grant comprises receiving the uplink grant via a beam of the PUCCH resource associated with the MPE event.

[0247] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the uplink grant indicates a new beam to be used for transmitting the uplink message.

[0248] although Figure 11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Figure 11 1100. Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0249] Figure 12 12 is a conceptual data flow diagram 1200 illustrating the flow of data between different components in an example apparatus 1202. Apparatus 1202 can be a UE (e.g., UE 120). In some aspects, apparatus 1202 includes a receiving component 1204, an identifying component 1206, a determining component 1208, an initiating component 1210, and / or a transmitting component 1212.

[0250] In some aspects, the apparatus may utilize a receiving component 1204 and a transmitting component 1212 to communicate with a base station via one or more beams. The UE may utilize an identifying component 1206 to identify an MPE event associated with a beam. For example, the identifying component 1206 may determine that an uplink beam failure event based on MPE has occurred. The determining component 1208 may determine whether PUCCH resources for transmitting an SR are available. The initiating component 1210 may initiate a PRACH procedure for transmitting an uplink message (e.g., a MAC-CE report for an MPE event).

[0251] The apparatus may include executing Figure 9 The aforementioned process 900, Figure 10 The aforementioned process 1000, Figure 11 The aforementioned process 1100 and other additional components of each box of the algorithm. Figure 9 The aforementioned process 900, Figure 10 The aforementioned process 1000, Figure 11 Each block in the aforementioned process 1100, etc., may be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0252] Figure 12 The number and arrangement of components shown in the FIG are provided as examples. In practice, there may be Figure 12 Components may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. Figure 12 Two or more components shown in may be implemented in a single component, or Figure 12 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 12 A set of components (e.g., one or more components) shown in FIG may perform the operations described as being performed by Figure 12 One or more functions performed by another group of components shown in FIG.

[0253] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0254] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0255] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0256] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Thus, the operation and behavior of these systems and / or methods are described herein without reference to specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods based, at least in part, on the description herein.

[0257] Although specific feature combinations are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of the various aspects includes that each dependent claim is combined with each other claim in this group of claims. The phrase quoting "at least one of" a list of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other arrangement of a, b and c).

[0258] The elements, actions or instructions used herein should not be interpreted as critical or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more items and can be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, non-related items, a combination of related items and non-related items, etc.) and can be used interchangeably with "one or more". Where it is intended that there is only one item, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "having", "containing", "comprising" etc. are intended to be open terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink control channel (PUCCH) resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; as well as A physical random access channel (PRACH) procedure for transmitting an uplink message is initiated based at least in part on determining that the PUCCH resources are unavailable.

2. The method of claim 1 , wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

3. The method of claim 1 , wherein initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

4. The method of claim 3, further comprising: determining that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or additional MPE events being associated with additional beams associated with the additional PUCCH resources, Wherein initiating the PRACH procedure is based at least in part on determining that the additional PUCCH resources are unavailable.

5. The method of claim 1 , wherein the PRACH procedure comprises one of: Contention-based PRACH, Contention-free PRACH, or Two-step PRACH.

6. The method of claim 1, further comprising: Selecting a PRACH type from one or more candidate PRACH types, The one or more candidate PRACH types include one or more of the following: Contention-based PRACH type, Contention-free PRACH type, or Two-step PRACH type.

7. The method of claim 6, wherein selecting the PRACH type comprises: Selecting a contention-free PRACH type if the contention-free PRACH type is available; Selecting the two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; as well as The contention-based PRACH type is selected if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

8. The method of claim 1 , wherein initiating the PRACH procedure comprises: Message 1 is transmitted for a contention-based PRACH procedure or a contention-free PRACH procedure.

9. The method of claim 1, further comprising: An uplink grant to transmit the uplink message is received.

10. The method of claim 9, wherein the uplink grant is an MPE-specific uplink grant.

11. The method of claim 9, wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

12. The method of claim 9, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

13. The method of claim 1, further comprising: The uplink message is transmitted.

14. The method of claim 13, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

15. The method of claim 14, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

16. A wireless communication method performed by a user equipment (UE), comprising: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink shared channel (PUSCH) resource for transmitting an uplink message is unavailable based at least in part on identifying the MPE event associated with the beam; as well as Initiating a reporting procedure, wherein initiating said reporting procedure comprises: initiating a physical random access channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or A scheduling request to transmit the uplink message is transmitted via an MPE dedicated physical uplink control channel PUCCH resource.

17. The method of claim 16, further comprising: A determination is made not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

18. The method of claim 16, further comprising: Determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery is based at least in part on identifying the MPE event.

19. The method of claim 16, wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

20. The method of claim 16, further comprising: The uplink message is transmitted.

21. The method of claim 20, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

22. The method of claim 21, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

23. The method of claim 16, wherein transmitting the scheduling request via the MPE-dedicated PUCCH resource comprises: A scheduling request is transmitted via the MPE-dedicated PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

24. The method of claim 16, further comprising: An uplink grant to transmit the uplink message is received.

25. The method of claim 24, wherein the uplink grant is an MPE-specific uplink grant.

26. The method of claim 24, wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

27. The method of claim 24, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

28. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory and the one or more processors being configured to: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink control channel (PUCCH) resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; as well as A physical random access channel (PRACH) procedure for transmitting an uplink message is initiated based at least in part on determining that the PUCCH resources are unavailable.

29. The UE of claim 28, wherein the uplink message comprises one or more of the following: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

30. The UE of claim 28, wherein initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

31. The UE of claim 30, wherein the one or more processors are further configured to: determining that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or additional MPE events being associated with additional beams associated with the additional PUCCH resources, Wherein initiating the PRACH procedure is based at least in part on determining that the additional PUCCH resources are unavailable.

32. The UE of claim 28, wherein the PRACH procedure comprises one of: Contention-based PRACH, Contention-free PRACH, or Two-step PRACH.

33. The UE of claim 28, wherein the one or more processors are further configured to: Selecting a PRACH type from one or more candidate PRACH types, The one or more candidate PRACH types include one or more of the following: Contention-based PRACH type, Contention-free PRACH type, or Two-step PRACH type.

34. The UE of claim 33, wherein selecting the PRACH type comprises: Selecting a contention-free PRACH type if the contention-free PRACH type is available; Selecting the two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; as well as The contention-based PRACH type is selected if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

35. The UE of claim 28, wherein initiating the PRACH procedure comprises: Message 1 is transmitted for a contention-based PRACH procedure or a contention-free PRACH procedure.

36. The UE of claim 28, wherein the one or more processors are further configured to: An uplink grant to transmit the uplink message is received.

37. The UE of claim 36, wherein the uplink grant is an MPE-specific uplink grant.

38. The UE of claim 36, wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

39. The UE of claim 36, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

40. The UE of claim 28, wherein the one or more processors are further configured to: The uplink message is transmitted.

41. The UE of claim 40, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

42. The UE of claim 41, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

43. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory and the one or more processors being configured to: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink shared channel (PUSCH) resource for transmitting an uplink message is unavailable based at least in part on identifying the MPE event associated with the beam; as well as Initiating a reporting procedure, wherein initiating said reporting procedure comprises: initiating a physical random access channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or A scheduling request to transmit the uplink message is transmitted via an MPE dedicated physical uplink control channel PUCCH resource.

44. The UE of claim 43, wherein the one or more processors are further configured to: A determination is made not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

45. The UE of claim 43, wherein the one or more processors are further configured to: Determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery is based at least in part on identifying the MPE event.

46. ​​The UE of claim 43, wherein the uplink message comprises one or more of the following: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

47. The UE of claim 43, wherein the one or more processors are further configured to: The uplink message is transmitted.

48. The UE of claim 47, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

49. The UE of claim 48, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

50. The UE of claim 43, wherein transmitting the scheduling request via the MPE-dedicated PUCCH resource comprises: A scheduling request is transmitted via the MPE-dedicated PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

51. The UE of claim 43, wherein the one or more processors are further configured to: An uplink grant to transmit the uplink message is received.

52. The UE of claim 51, wherein the uplink grant is an MPE-specific uplink grant.

53. The UE of claim 51 , wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

54. The UE of claim 51 , wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

55. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink control channel (PUCCH) resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; as well as A physical random access channel (PRACH) procedure for transmitting an uplink message is initiated based at least in part on determining that the PUCCH resources are unavailable.

56. The non-transitory computer-readable medium of claim 55, wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

57. The non-transitory computer-readable medium of claim 55, wherein initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

58. The non-transitory computer-readable medium of claim 57, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: determining that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or additional MPE events being associated with additional beams associated with the additional PUCCH resources, Wherein initiating the PRACH procedure is based at least in part on determining that the additional PUCCH resources are unavailable.

59. The non-transitory computer-readable medium of claim 55, wherein the PRACH procedure comprises one of: Contention-based PRACH, Contention-free PRACH, or Two-step PRACH.

60. The non-transitory computer-readable medium of claim 55, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: Selecting a PRACH type from one or more candidate PRACH types, The one or more candidate PRACH types include one or more of the following: Contention-based PRACH type, Contention-free PRACH type, or Two-step PRACH type.

61. The non-transitory computer-readable medium of claim 60, wherein selecting the PRACH type comprises: Selecting a contention-free PRACH type if the contention-free PRACH type is available; Selecting the two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; as well as The contention-based PRACH type is selected if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

62. The non-transitory computer-readable medium of claim 55, wherein initiating the PRACH procedure comprises: Message 1 is transmitted for a contention-based PRACH procedure or a contention-free PRACH procedure.

63. The non-transitory computer-readable medium of claim 55, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: An uplink grant to transmit the uplink message is received.

64. The non-transitory computer-readable medium of claim 63, wherein the uplink grant is an MPE-specific uplink grant.

65. The non-transitory computer-readable medium of claim 63, wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

66. The non-transitory computer-readable medium of claim 63, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

67. The non-transitory computer-readable medium of claim 55, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: The uplink message is transmitted.

68. The non-transitory computer-readable medium of claim 67, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

69. The non-transitory computer-readable medium of claim 68, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

70. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to: Identify the maximum permissible exposure (MPE) event associated with the beam; determining that a physical uplink shared channel (PUSCH) resource for transmitting an uplink message is unavailable based at least in part on identifying the MPE event associated with the beam; as well as Initiating a reporting procedure, wherein initiating said reporting procedure comprises: initiating a physical random access channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or A scheduling request to transmit the uplink message is transmitted via an MPE dedicated physical uplink control channel PUCCH resource.

71. The non-transitory computer readable medium of claim 70, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: A determination is made not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

72. The non-transitory computer readable medium of claim 70, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: Determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery is based at least in part on identifying the MPE event.

73. The non-transitory computer-readable medium of claim 70, wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

74. The non-transitory computer-readable medium of claim 70, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: The uplink message is transmitted.

75. The non-transitory computer-readable medium of claim 74, wherein transmitting the uplink message comprises: The uplink message is transmitted via the new beam.

76. The non-transitory computer-readable medium of claim 75, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

77. The non-transitory computer-readable medium of claim 70, wherein transmitting the scheduling request via the MPE-dedicated PUCCH resource comprises: A scheduling request is transmitted via the MPE-dedicated PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

78. The non-transitory computer-readable medium of claim 70, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: An uplink grant to transmit the uplink message is received.

79. The non-transitory computer-readable medium of claim 78, wherein the uplink grant is an MPE-specific uplink grant.

80. The non-transitory computer-readable medium of claim 78, wherein receiving the uplink grant comprises: The uplink grant is received via the beam of the PUCCH resources associated with the MPE event.

81. The non-transitory computer-readable medium of claim 78, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

82. A device for wireless communication, comprising: means for identifying a maximum permissible exposure (MPE) event associated with the beam; means for determining that a physical uplink control channel, PUCCH, resource for transmitting a scheduling request is unavailable based at least in part on identifying the MPE event associated with the beam; as well as Means for initiating a Physical Random Access Channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUCCH resources are unavailable.

83. The apparatus of claim 82, wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

84. The apparatus of claim 82, wherein initiating the PRACH procedure is based at least in part on determining that additional PUCCH resources for transmitting the scheduling request are unavailable.

85. The apparatus of claim 84, further comprising: means for determining that the additional PUCCH resources for transmitting the scheduling request are unavailable based at least in part on the MPE event or additional MPE events being associated with additional beams associated with the additional PUCCH resources, Wherein initiating the PRACH procedure is based at least in part on determining that the additional PUCCH resources are unavailable.

86. The apparatus of claim 82, wherein the PRACH procedure comprises one of: Contention-based PRACH, Contention-free PRACH, or Two-step PRACH.

87. The apparatus of claim 82, further comprising: means for selecting a PRACH type from one or more candidate PRACH types, The one or more candidate PRACH types include one or more of the following: Contention-based PRACH type, Contention-free PRACH type, or Two-step PRACH type.

88. The apparatus of claim 87, wherein selecting the PRACH type comprises: means for selecting a contention-free PRACH type if the contention-free PRACH type is available; means for selecting a two-step PRACH type if the contention-free PRACH type is not available and the two-step PRACH type is available; as well as Means for selecting a contention-based PRACH type if the contention-free PRACH type is not available, the two-step PRACH type is not available, and the contention-based PRACH type is available.

89. The apparatus of claim 82, wherein initiating the PRACH procedure comprises: Message 1 is transmitted for a contention-based PRACH procedure or a contention-free PRACH procedure.

90. The apparatus of claim 82, further comprising: Means for receiving an uplink grant to transmit the uplink message.

91. The apparatus of claim 90, wherein the uplink grant is an MPE-specific uplink grant.

92. The apparatus of claim 90, wherein receiving the uplink grant comprises: Means for receiving the uplink grant via the beam of the PUCCH resources associated with the MPE event.

93. The apparatus of claim 90, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

94. The apparatus of claim 82, further comprising: means for transmitting the uplink message.

95. The apparatus of claim 94, wherein transmitting the uplink message comprises: Means for transmitting the uplink message via a new beam.

96. The apparatus of claim 95, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

97. A device for wireless communication, comprising: means for identifying a maximum permissible exposure (MPE) event associated with the beam; means for determining that a physical uplink shared channel (PUSCH) resource for transmitting an uplink message is unavailable based at least in part on identifying the MPE event associated with the beam; as well as Means for initiating a reporting procedure, initiating the reporting procedure comprising: means for initiating a Physical Random Access Channel (PRACH) procedure for transmitting an uplink message based at least in part on determining that the PUSCH resources are unavailable, or Means for transmitting a scheduling request to transmit the uplink message via an MPE dedicated physical uplink control channel (PUCCH) resource.

98. The apparatus of claim 97, further comprising: Means for determining not to transmit a scheduling request via a PUCCH resource associated with the PUSCH resource based at least in part on identifying the MPE event.

99. The apparatus of claim 97, further comprising: Means for determining not to transmit a scheduling request via PUCCH resources associated with beam failure recovery based at least in part on identifying the MPE event.

100. The apparatus of claim 97, wherein the uplink message comprises one or more of: Report of the MPE incident, Beam failure report, or Physical uplink shared channel transmission.

101. The apparatus of claim 97, further comprising: means for transmitting the uplink message.

102. The apparatus of claim 101 , wherein transmitting the uplink message comprises: Means for transmitting the uplink message via a new beam.

103. The apparatus of claim 102, wherein the new beam is the same beam used to initiate the PRACH procedure or transmit a scheduling request for the uplink message.

104. The apparatus of claim 97, wherein transmitting the scheduling request via the MPE-dedicated PUCCH resource comprises: means for transmitting a scheduling request via the MPE-dedicated PUCCH resource via an additional beam, the additional beam being different from the beam of the PUSCH resource.

105. The apparatus of claim 97, further comprising: Means for receiving an uplink grant to transmit the uplink message.

106. The apparatus of claim 105, wherein the uplink grant is an MPE-specific uplink grant.

107. The apparatus of claim 105, wherein receiving the uplink grant comprises: Means for receiving the uplink grant via the beam of the PUCCH resources associated with the MPE event.

108. The apparatus of claim 105, wherein the uplink grant indicates a new beam to be used to transmit the uplink message.

Images