Maximum allowed exposure reporting configuration in carrier aggregation and dual connectivity

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send an uplink message on an uplink channel associated with a special cell (Spcell) to trigger a maximum permitted exposure (MPE) report based at least in part on a maximum permitted exposure (MPE) event. The UE may send an MPE medium access control (MAC) control element (MAC‑CE) to report the MPE event, wherein the MPE MAC‑CE is sent on a physical uplink shared channel associated with the Spcell or a supplementary cell. Numerous other aspects are provided.

Description

Technical Field

[0001]

[0003] Aspects of the present disclosure generally relate to wireless communications, and more particularly, to techniques and apparatus for providing maximum permitted exposure (MPE) reporting configuration in carrier aggregation and dual connectivity. Background Art

[0002] Wireless communication systems have been 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 that support 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), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), 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).

[0003] A wireless communication network may include multiple base stations (BSs), which can support communication for multiple user equipment (UEs). User equipment (UEs) can communicate with a base station (BS) 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, transmission reception point (TRP), new radio (NR) BS, 5G Node B, and so on.

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate on a city-wide, national-wide, regional-wide, and even global scale. New Radio (NR), also known as 5G, is an enhancement to the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, fully utilizing new spectrum, using orthogonal frequency division multiplexing (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. However, as the demand for mobile broadband access continues to increase, there is a need to further improve LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the Invention

[0005] In some aspects, a method of wireless communication performed by a UE may include: sending an uplink message on an uplink channel associated with a special cell (Spcell) to trigger an MPE report based at least in part on a maximum permitted exposure (MPE) event; and sending an MPE medium access control (MAC) control element (MAC-CE) to report the MPE event, wherein the MPE MAC-CE is sent on a physical uplink shared channel (PUSCH) associated with the Spcell or a secondary cell (Scell).

[0006] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: send an uplink message on an uplink channel associated with an SPcell to trigger an MPE report based at least in part on an MPE event; and send an MPE MAC-CE to report the MPE event, wherein the MPE MAC-CE is sent on a PUSCH associated with the SPcell or Scell.

[0007] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to perform the following operations: based at least in part on an MPE event, sending an uplink message on an uplink channel associated with an SPcell to trigger an MPE report; and sending an MPE MAC-CE to report the MPE event, wherein the MPE MAC-CE is sent on a PUSCH associated with the SPcell or Scell.

[0008] In some aspects, an apparatus for wireless communication may include: a unit for sending an uplink message on an uplink channel associated with an Spcell to trigger an MPE report based at least in part on an MPE event; and a unit for sending an MPE MAC-CE to report the MPE event, wherein the MPE MAC-CE is sent on a PUSCH associated with the Spcell or Scell.

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

[0010] In order to better understand the following specific embodiments, the features and technical advantages of the examples according to the present disclosure have been summarized to a considerable extent above. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of performing the present disclosure. These equivalent constructions do not depart from the scope of protection of the appended claims. When considering the following specific embodiments in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (about their organization and method of operation), as well as the associated advantages, will be better understood. Each of these drawings is provided for illustration and description purposes only and is not intended to be used as a limitation to the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to understand the above-described features of the present disclosure in detail, the present application provides a more detailed description with reference to some aspects of the above brief summary, some of which are illustrated in the accompanying drawings. However, it should be noted that since the description of the present invention allows for other equally effective aspects, these drawings only depict certain typical aspects of the present disclosure and should not be considered to limit the scope of protection of the present invention. The same reference numerals in different figures may identify the same or similar elements.

[0012] Figure 1is a block diagram conceptually illustrating an example of a wireless communication network according to various aspects of the present disclosure.

[0013] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.

[0014] Figure 3 is a diagram illustrating one or more examples of communications involving maximum permissible exposure (MPE) events, according to various aspects of the present disclosure.

[0015] Figures 4A-4B is a diagram illustrating one or more examples of providing MPE reporting configurations in carrier aggregation and dual connectivity according to various aspects of the present disclosure.

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

[0017] Figure 6 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.

[0018] Figure 7 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. DETAILED DESCRIPTION

[0019] 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 a variety of different forms, which should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, providing these aspects is only to make the present disclosure thorough and complete, and will fully convey the scope of protection of the present disclosure to those of ordinary skill in the art. Based on the teachings of this article, it should be understood by those of ordinary skill in the art that the scope of protection of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, a device or method can be implemented using any number of aspects set forth herein. In addition, the scope of protection of the present disclosure is intended to cover such a device or method, which can be implemented by using other structures, functions, or structures and functions of the various aspects of the disclosure set forth herein, or structures and functions of the various aspects of the disclosure set forth herein that are different from those set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more components of the present invention.

[0020] Some aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and depicted 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 any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0021] It should be noted that although various aspects are described herein using terms generally associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may also be applicable to communication systems based on other generations (e.g., 5G and subsequent versions including NR technology).

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

[0023] 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., a radius of several kilometers), which allows unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area, which allows unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home), which allows restricted access to 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 1In the example shown, BS 110a may be a macro BS for macrocell 102a, BS 110b may be a pico BS for picocell 102b, and BS 110c may be a femto BS for femtocell 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.

[0024] In some aspects, the cells need not 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 be interconnected 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 (e.g., direct physical connections or virtual networks) using any suitable transport network.

[0025] 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, 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.

[0026] 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 higher 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).

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

[0028] 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / 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 device or video device or a satellite radio device), an in-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.

[0029] Some UEs may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, and the like that are capable of communicating with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) 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 in a housing that houses components of UE 120 (e.g., a processor component, a memory component, and the like). In some aspects, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, and the like.

[0030] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can 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 can be deployed.

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

[0032] As indicated above, Figure 1 Provided as an example. Other examples can be referenced Figure 1 The examples described are different.

[0033] Figure 2 A block diagram shows a design 200 of base station 110 and UE 120, which may be Figure 1 One of the base stations in Figure 1 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.

[0034] At base station 110, transmit processor 220 may receive data intended 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., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols (if any) and provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. In accordance with various aspects described in further detail below, position coding may be utilized to generate synchronization signals to convey additional information.

[0035] 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 (if 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.

[0036] On the uplink, at UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280, and process the data and control information. 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 back to the base station 110. At the base station 110, uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0037] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the may perform one or more techniques associated with providing maximum permitted exposure (MPE) reporting configuration in carrier aggregation and dual connectivity, as described in further 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 of the Figure 5 The operations of process 500 and / or other processing as described herein. Memory 242 and memory 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, when the one or more instructions are executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, conversion, interpretation, etc.), they may perform or direct, for example, Figure 5 The process 500 and / or other processing operations described herein may include executing instructions, converting instructions, compiling instructions, interpreting instructions, etc. The scheduler 246 may schedule UEs for downlink and / or uplink data transmission.

[0038] In some aspects, the UE 120 may include: means for sending an uplink message on an uplink channel associated with a special cell (Spcell) to trigger an MPE report based at least in part on an MPE event; means for sending an MPE medium access control (MAC) control element (MAC-CE) to report the MPE event, wherein the MPE MAC-CE is sent on a physical uplink shared channel (PUSCH) associated with the Spcell or a supplementary cell (Scell), etc. In some aspects, these means may include combining Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and so forth.

[0039] As indicated above, Figure 2 Provided as an example. Other examples can be referenced Figure 2 The examples described are different.

[0040] Figure 3 FIG. 1 is a diagram illustrating one or more examples 300 of communications involving MPE events, according to various aspects of the present disclosure. Figure 3As shown in , the UE and the base station can communicate via one or more beams, and the communication via the beam may take multiple different paths to reach the receiver. In some cases, the beam can be a millimeter wave (mmWave) beam for communication in the mmWave band. When transmitting in the mmWave band, the transmitter can use a higher antenna gain than when transmitting in a band below 6 gigahertz (GHz). Therefore, the effective isotropic radiated power (EIRP) of mmWave communication can be higher than that of communication below 6 GHz, which represents the radiated power in a specific direction (e.g., the direction of the beam).

[0041] Because UEs emit radio frequency (RF) waves, microwaves, and / or other radiation, some regulatory agencies have imposed limits on the peak EIRP that can be directed toward a human body (e.g., to improve safety). These limits, sometimes referred to as MPE constraints, MPE limits, etc., may impose restrictions on various operations that a UE may perform. For example, RF radiation typically increases when a UE is transmitting, and may further increase if the UE is performing frequent transmissions, high-power transmissions, etc. Therefore, because frequent and / or high-power transmissions may result in significant RF radiation, regulatory agencies (e.g., the Federal Communications Commission (FCC) in the United States) provide information related to acceptable RF radiation exposure when a UE communicates on an uplink, downlink, sidelink, etc.

[0042] For example, Figure 3 As shown in FIG, and by reference numeral 310, the UE may communicate with the base station using an uplink beam and / or a downlink beam. In some cases, the uplink beam used by the UE may not be directed toward a human body and thus may not be affected by the MPE condition.

[0043] like Figure 3As further shown in the figure, and by reference numeral 320, the uplink beam used by the UE to send uplink communications may become affected by an MPE condition. For example, when an MPE event occurs, the uplink beam may be affected by the MPE condition. The MPE event may be, for example, a human body or body part 325 that obstructs the uplink beam (e.g., the beam used by the UE to send uplink transmissions may be directed towards the human body or body part 325). That is, the human body or body part 325 may block or obstruct communications to and / or from the antenna subarray of the UE, or may otherwise be located near the antenna subarray. In this case, the downlink beam may be suitable for use by the UE to communicate with the base station, but when the uplink beam is subject to the MPE condition, the uplink beam may not be allowed to be used. For example, the downlink beam may not be subject to MPE constraints because the EIRP level of the base station's transmission may drop when the transmission reaches the UE and / or body part 325. However, uplink beams are subject to MPE conditions because the EIRP level of the UE's transmissions may exceed the allowed EIRP level due to the close proximity of the UE and the body part 325. In this case, the UE and / or the base station may use a first beam for uplink communication and a second beam for downlink communication, where the first beam (e.g., an uplink transmit beam used by the UE or an uplink receive beam used by the base station) does not form a reciprocal beam pair with the second beam (e.g., a downlink receive beam used by the UE or a downlink transmit beam used by the base station).

[0044] For example, Figure 3 As further shown in FIG. 3 and by reference numeral 330, the UE may transmit uplink communications using a beam different from the uplink transmit beam affected by the MPE condition. For example, the UE may transmit uplink communications using an uplink transmit beam included in another cluster that is different from the uplink transmit beam affected by the MPE condition. Figure 3As shown in , the UE can use a beam directed towards the object 335, which provides a path to the base station that is not blocked by the body part 325. In this way, even if the base station uses a reciprocal beam to communicate with the UE, the UE can select a non-reciprocal beam (e.g., an uplink transmit beam and a downlink receive beam in different clusters) to communicate with the base station, which enables the UE to meet the MPE constraint. However, in some cases, switching the uplink transmit beam to meet the MPE constraint may result in uplink coverage loss. In addition, in some cases, MPE conditions may occur on multiple (possibly all) uplink transmit beams from the UE's antenna panel, and therefore the uplink coverage loss due to MPE constraints may need to be mitigated on a per-panel basis to meet regulatory requirements. This may create challenges in certain communication scenarios such as carrier aggregation or dual connectivity, where the UE may be configured to communicate with the base station using different cells. For example, the UE may need to report an MPE event detected on a specific cell, but the MPE constraint may prevent the UE from sending an MPE report on the cell where the MPE event was detected. In addition, in the case where the UE is configured to adopt inter-band carrier aggregation (for example, the configured component carriers include the 28 GHz band and the 39 GHz or 60 GHz band), the total MPE across different bands needs to meet the MPE constraint.

[0045] Some aspects described herein relate to techniques and apparatus for providing MPE reporting configurations in carrier aggregation and / or dual connectivity communication scenarios. For example, a UE may determine (e.g., using ultrasound, using broadband and / or narrowband ranging techniques, etc.) that an uplink beam associated with a particular cell is experiencing an MPE event, and may send an MPE communication to a base station to provide an indication of the MPE event. For example, the UE may send an uplink communication to trigger an MPE report via a physical random access channel (PRACH) process, a scheduling request process, etc., based at least in part on the cell on which the MPE condition is detected, and the UE may further send an MPE medium access control (MAC) control element (MAC-CE) on a physical uplink shared channel (PUSCH) to report the MPE event. In addition, when one or more conditions are met, the UE may cancel or stop the triggered MPE report. In this way, the UE may be enabled to report an MPE event in carrier aggregation and / or dual connectivity communication scenarios, where the MPE event may occur in different cells with different configurations.

[0046] As indicated above, Figure 3 Provided as an example. Other examples can be referenced Figure 3 The examples described are different.

[0047] Figures 4A-4BFIG. 4 is a diagram illustrating one or more examples 400A, 400B of MPE reporting configurations in carrier aggregation and dual connectivity according to various aspects of the present disclosure. Figures 4A-4B As shown in FIG, , UE 120 can communicate with base station 110 in a wireless network (e.g., wireless network 100). In addition, as described herein, UE 120 and base station 110 can communicate with each other using uplink beams associated with a primary cell (Pcell), one or more secondary cells (Scells), etc., according to a carrier aggregation configuration, a dual connectivity configuration, etc.

[0048] For example, carrier aggregation may generally enable two or more component carriers (sometimes referred to as carriers) to be combined (e.g., into a single channel) to enhance data capacity for a UE 120. Generally, component carriers may be combined in the same or different frequency bands, in the same or different frequency ranges, and so forth. Additionally or alternatively, contiguous or non-contiguous component carriers may be combined. In some aspects, a base station 110 may configure carrier aggregation for a UE 120 in an intra-band contiguous mode, where the aggregated component carriers are contiguous with each other and in the same frequency band. Additionally or alternatively, carrier aggregation may be configured in an intra-band non-contiguous mode, where the aggregated component carriers are in the same frequency band and non-contiguous with each other. Additionally or alternatively, carrier aggregation may be configured in an inter-band non-contiguous mode, where the aggregated component carriers are non-contiguous with each other and in different frequency bands. In carrier aggregation, a UE 120 may be configured with a cell group that includes up to sixteen (16) different cells. For example, a cell group generally includes one Pcell and up to fifteen (15) Scells. In addition, in some cases, one of the Scells may be associated with a physical uplink control channel (PUCCH) configuration (e.g., to offload some PUCCH traffic from the Pcell), which may be referred to as a secondary PUCCH Scell. In other words, in carrier aggregation operation, a UE may be configured with a cell group comprising up to 16 component carriers, wherein the cell group comprises up to two PUCCH cell groups (e.g., a primary PUCCH cell group and an optional secondary PUCCH cell group). Typically, each PUCCH cell group has a special cell (Spcell), which may refer to a specific cell in the PUCCH cell group that is associated with the PUCCH configuration. For example, a primary PUCCH cell group or a secondary PUCCH cell group may include a group of cells whose PUCCH signaling is associated with a PUCCH on a primary PUCCH cell or a secondary PUCCH Scell, respectively. A special cell (Spcell) may be a primary PUCCH cell (Pcell) in a primary PUCCH cell group or a secondary PUCCH Scell in a secondary PUCCH cell group. Thus, in some aspects, the cell groups in carrier aggregation operation may include one or two special cells (Spcells), where these Spcells may be cells in each PUCCH cell group having a PUCCH configuration shared between the cell groups in the respective PUCCH cell groups (for example, the Pcell may be a Spcell in the primary PUCCH cell group, and the secondary PUCCH Scell associated with the PUCCH configuration may be a Spcell in the secondary PUCCH cell group for offloading PUCCH services from the Pcell in the primary PUCCH cell group).

[0049] In dual connectivity (e.g., Multi-RAT Dual Connectivity (MR-DC), E-UTRA-NR Dual Connectivity (EN-DC), etc.), UE 120 may be configured with two cell groups to enable UE 120 to be connected to multiple cells simultaneously. For example, UE 120 may be configured with a primary cell group that includes a PCell and optionally one or more Scells. Additionally, in some aspects, UE 120 may be configured with a secondary cell group that includes a primary secondary cell (PScell) or a secondary primary cell (SPcell), and optionally one or more additional secondary cells (e.g., in addition to the Scells in the primary cell group). In this case, the term Pcell may refer to a cell belonging to a primary cell group on which UE 120 performs an initial connection establishment procedure or becomes a Pcell through a handover procedure, the term PScell or SPcell may refer to a cell in a secondary cell group on which UE 120 performs random access when a secondary cell group is configured for the UE (e.g., in dual connectivity operation), and the term Scell may refer to an additional cell belonging to the primary cell group or the secondary cell group and configured by base station 110 to provide additional bandwidth to UE 120. Furthermore, in a manner similar to that described above, the terms special cell and SPcell in dual connectivity refer to a cell associated with a PUCCH configuration, which may be a Pcell in the primary cell group or a PScell (or SPcell) in the secondary cell group.

[0050] In some aspects, as described herein, the UE 120 may employ different MPE reporting procedures depending on whether the MPE event is detected on a Spcell, an Scell, a PScell, an SPcell, etc. Furthermore, in some aspects, the UE 120 may cancel MPE reporting that is triggered at least in part based on an MPE event when one or more conditions are met (e.g., when parameters used by the UE 120 and the base station 110 for communication have changed such that continued reporting of the MPE event is no longer necessary). For example, in some aspects, Figure 4A 4 shows an example of an MPE reporting procedure that may be employed when UE 120 detects an MPE event on a Spcell. Figure 4B An example 400B of an MPE reporting procedure that may be employed when a UE 120 detects an MPE event on an Scell, PScell, SPcell, etc. is shown. Figure 4A and Figure 4B Both show that when one or more conditions are met, UE 120 may cancel the triggered MPE report.

[0051] like Figure 4AAs shown in FIG4 and by reference numeral 410, a UE 120 may detect an MPE event associated with an uplink transmit beam that the UE 120 uses to communicate with a base station on a special cell (Spcell). For example, as described above, the MPE event may be detected based at least in part on a human body, a body part blocking the beam, being located near an antenna subarray, and the like. Thus, in some aspects, the UE 120 may detect (e.g., using ultrasound, using wideband and / or narrowband ranging techniques, and the like) whether an antenna subarray of the UE 120 is near and / or blocked by a human body or body part, whether a directional beam of the UE 120 is directed toward and / or blocked by a human body or body part, and the like. Thus, when the UE 120 detects an MPE event on the Spcell, the UE 120 may determine that the uplink transmit beam or one or more component carriers associated with the uplink transmit beam is subject to an MPE condition, such that the UE 120 is not permitted to use the uplink transmit beam or the component carriers associated with the uplink transmit beam. In other words, due to the MPE event, the UE 120 may be subject to transmission limitations (eg, limitations on antenna gain, limitations on transmit power, etc.) on the Spcell due to the MPE event.

[0052] like Figure 4A As further shown in FIG4 and by reference numeral 412, the UE 120 may initiate a physical random access channel (PRACH) procedure on the Spcell to trigger an MPE report based at least in part on detecting an MPE event on the Spcell. For example, in some aspects, the UE 120 may transmit a PRACH preamble (e.g., in msg1 of a four-step RACH procedure, msgA preamble of a two-step RACH procedure, etc.) to the base station 110 to initiate the PRACH procedure, and the UE 120 may subsequently transmit an MPE MAC-CE to the base station 110 to report the MPE event in a PUSCH communication (e.g., in msg3 of a four-step RACH procedure, msgA payload of a two-step RACH procedure, etc.). In addition, in the case of a four-step RACH procedure, the UE 120 may receive a random access response (RAR) message from the base station 110 as a reply to the PRACH preamble transmission, the RAR message scheduling the PUSCH in which the UE 120 transmits the MPE MAC-CE. In some aspects, the MPE MAC-CE may indicate to the base station 110 information related to the MPE event (eg, cell identifier, bandwidth portion identifier, etc.).

[0053] In some aspects, when the UE 120 transmits a PRACH preamble to initiate a PRACH process and thereby trigger an MPE report, the UE 120 may switch to a different bandwidth portion on the Spcell configured with PRACH resources (e.g., because the UE 120 may be restricted from transmitting using the bandwidth portion in which the MPE event was detected). For example, in some aspects, the Spcell may be configured with multiple bandwidth portions, one or more of which may be configured with PRACH resources (e.g., a PRACH preamble, a RACH opportunity (RO), etc.). Thus, as described herein, the UE 120 may detect an MPE event on a first bandwidth portion associated with the Spcell, and the UE 120 may perform an uplink transmission of a PRACH preamble to trigger an MPE report on a second bandwidth portion associated with the Spcell configured with PRACH resources. For example, in some aspects, the UE 120 may perform an uplink transmission of a PRACH preamble using a bandwidth portion on a primary uplink carrier configured with PRACH resources, a bandwidth portion on a supplemental uplink carrier configured with PRACH resources, and so on. Additionally or alternatively, UE 120 may perform uplink transmission of a PRACH preamble using a portion of bandwidth on an uplink carrier associated with an MPE event, which may correspond to a primary uplink carrier or a supplementary uplink carrier. Additionally or alternatively, UE 120 may perform uplink transmission of a PRACH preamble using a portion of bandwidth on an uplink carrier associated with a low frequency band (e.g., relative to other uplink carriers configured for UE 120) because the low frequency band may have a lower MPE impact. For example, in some cases, the low frequency band may correspond to a supplementary uplink carrier, which may be configured in the low frequency band to extend coverage.

[0054] In some aspects, when an MPE event is detected on an Spcell, the UE 120 may further select a specific bandwidth portion and / or cell to send an MPE MAC-CE for reporting the MPE event. For example, in some aspects, the UE 120 may send the MPE MAC-CE on a PUSCH associated with the same bandwidth portion and / or cell used to send the PRACH preamble. Additionally or alternatively, the UE 120 may send the MPE MAC-CE on a PUSCH associated with any bandwidth portion and / or cell in the same cell group as the Spcell (e.g., a carrier aggregation cell group, a primary cell group under dual connectivity when the Spcell is a PCell, a secondary cell group under dual connectivity when the Spcell is a PScell, etc.).

[0055] like Figure 4BAs shown in FIG4 and by reference numeral 420, UE 120 may communicate with base station 110 on an Scell, SPcell, etc. For example, in some aspects, base station 110 may transmit one or more physical downlink control channel (PDCCH) communications including downlink control information (DCI) to schedule one or more physical downlink shared channel (PDSCH) communications to be sent to UE 120. Furthermore, in some aspects, base station 110 may transmit one or more PDCCH communications including DCI to schedule PUSCH communications for UE 120.

[0056] like Figure 4B As further shown in FIG4 and by reference numeral 422, UE 120 may detect an MPE event associated with an uplink transmit beam (e.g., an uplink transmit beam used to transmit a PUSCH) used by UE 120 to communicate with a base station on an Scell, SPcell, etc. For example, as described above, the MPE event may be detected based at least in part on a human body, a body part blocking the beam, being located near an antenna subarray, etc. Thus, when UE 120 detects an MPE event on an Scell, SPcell, etc., UE 120 may determine that UE 120 is not permitted to transmit using the uplink transmit beam or a component carrier associated with the uplink transmit beam. In other words, UE 120 may be subject to transmission restrictions on the Scell, SPcell, etc. due to the MPE event.

[0057] like Figure 4B As further shown in FIG. 4 and by reference numeral 424, UE 120 may initiate a scheduling request procedure to trigger an MPE report based at least in part on detecting an MPE event on an Scell, SPcell, or the like. For example, Figure 4B As shown in , UE 120 may send a scheduling request to base station 110 on a PUCCH associated with an Scell, and base station 110 may subsequently send a PDCCH including DCI to schedule a PUSCH for UE 120. Accordingly, UE 120 may send an MPE MAC-CE to the base station to report an MPE event in a PUSCH communication. For example, in some aspects, an MPE MAC-CE for reporting an MPE event on an Scell or SPcell may be sent on a PUSCH associated with any Scell or SPcell in the same cell group or a different cell group than the Scell or SPcell associated with the MPE event (which may be excluded from available PUSCH options due to transmission restrictions imposed by the MPE event).

[0058] like Figure 4A and Figure 4B As further shown in FIG, and by reference numeral 430, the UE 120 may cancel an MPE report when one or more conditions are met. For example, in some aspects, the UE 120 may cancel an MPE report that has been triggered for a cell (e.g., a Spcell, a Scell, a SPcell, etc.) based at least in part on sending an MPE MAC-CE reporting an MPE event. Additionally or alternatively, the UE 120 may cancel an MPE report triggered for a cell based at least in part on receiving a DCI scheduling a new PUSCH with the same Hybrid Automatic Repeat Request (HARQ) identifier as the PUSCH used to send the MPE MAC-CE. For example, as described above, the MPE MAC-CE is typically sent on a PUSCH associated with a Spcell or Scell, and in some cases, the PUSCH may not be associated with any ACK and / or NACK information. Thus, after the UE 120 sends the MPE MAC-CE, the UE 120 may wait until receiving a DCI scheduling another new PUSCH communication. In this case, the DCI scheduling the next new PUSCH communication may indicate the same HARQ identifier as the PUSCH used to transmit the MPE MAC-CE, indicating that the base station 110 successfully received the MPE MAC-CE, so that the UE 120 can cancel the MPE report. Additionally or alternatively, the UE 120 can cancel the MPE triggered for the cell based at least in part on receiving a DCI scrambled by a special radio network temporary identifier (RNTI) on a control resource set (CORESET). For example, in some aspects, the DCI may schedule an uplink grant after a scheduling request is sent from the UE 120 to the base station 110, and the DCI may be scrambled by a special RNTI and / or may be sent on a special CORESET to confirm the MPE MAC-CE. In this case, the DCI may similarly indicate that the base station 110 successfully received the MPE MAC-CE, so that the UE 120 can cancel the MPE report. Additionally or alternatively, UE 120 may suppress MPE reporting triggered for a particular serving cell based at least in part on DCI, radio resource control (RRC) signaling, and / or other signaling that causes UE 120 to switch bandwidth portions on the corresponding serving cell.

[0059] In some aspects, when MPE reporting is triggered for an Scell and / or PScell, the UE 120 may cancel MPE reporting for the Scell and / or PScell based at least in part on information received from the base station 110 indicating that the Scell and / or PScell has been deactivated, removed, and / or transitioned to a dormant state. For example, when an Scell and / or PScell has been deactivated, removed, and / or transitioned to a dormant state, the UE 120 no longer communicates via the deactivated, removed, and / or dormant cell and, therefore, may cancel MPE reporting for the corresponding serving cell. Additionally or alternatively, the UE 120 may cancel MPE reporting for the Scell, PScell, SPcell, etc. based at least in part on a MAC reset affecting the corresponding serving cell.

[0060] In some aspects, when an MPE report is triggered for a Spcell, the UE 120 may cancel the MPE report for the Spcell based at least in part on the successful completion of a random access procedure initiated after the UE 120 switches bandwidth parts due to an MPE event. For example, when the UE 120 detects an MPE event on a bandwidth part associated with the Spcell, the UE 120 may be restricted from performing further transmissions on the same bandwidth part. Consequently, the UE 120 may need to switch to a different bandwidth part and perform a random access procedure over the new bandwidth part to report the MPE event. In some aspects, the UE 120 may cancel the MPE report triggered for the Spcell after the UE 120 has switched to the different bandwidth part and completed the random access procedure over the new bandwidth part. Furthermore, when the MPE event on the Spcell causes the UE 120 to switch bandwidth parts, the UE 120 may terminate any ongoing random access procedure to initiate a new random access procedure on the new bandwidth part, and the UE 120 may reset one or more preamble and power ramp counters. For example, when the UE 120 performs a random access procedure, the UE 120 may transmit a PRACH preamble using an initial transmit power, and may increment one or more preamble and power ramp counters according to a preamble power ramp step size (e.g., an incremental value indicating an amount by which the transmit power of subsequent transmissions is increased) each time the PRACH preamble is transmitted until the one or more preamble and power ramp counters reach a maximum value. Thus, when the UE 120 terminates an ongoing random access procedure to initiate a new random access procedure on a new bandwidth portion, the preamble and power ramp counters may be reset to prevent the UE 120 from prematurely reaching the maximum transmit power of the PRACH preamble.

[0061] As indicated above, provide Figures 4A-4BAs one or more examples. Other examples can be referred to Figures 4A-4B The examples described are different.

[0062] Figure 5 is a diagram illustrating an example process 500, for example, performed by a UE, in accordance with various aspects of the present disclosure. Example process 500 is an example of a UE (eg, UE 120, etc.) performing operations associated with MPE reporting configuration in carrier aggregation and dual connectivity.

[0063] like Figure 5 As shown in , in some aspects, process 500 may include: sending an uplink message on an uplink channel associated with the Spcell to trigger an MPE report based at least in part on an MPE event (block 510). For example, the UE may (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, etc.) send an uplink message on an uplink channel associated with the Spcell to trigger an MPE report based at least in part on an MPE event, as described above.

[0064] like Figure 5 As further shown in FIG5 , in some aspects, process 500 may include sending an MPE MAC-CE to report an MPE event, wherein the MPE MAC-CE is sent on a PUSCH associated with the Spcell or Scell (block 520). For example, the UE may send the MPE MAC-CE to report the MPE event (e.g., using the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, the memory 282, etc.), as described above. In some aspects, the MPE MAC-CE is sent on a PUSCH associated with the Spcell or Scell.

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

[0066] In a first aspect, the uplink message is sent to trigger a PRACH procedure on the Spcell based at least in part on detecting an MPE event on the Spcell.

[0067] In a second aspect, alone or in combination with the first aspect, the uplink message is sent on a bandwidth portion associated with the Spcell configured with PRACH resources.

[0068] In a third aspect, alone or in combination with one or more of the first and second aspects, the bandwidth portion used to send the uplink message is associated with one or more of: an uplink carrier associated with the Spcell or a supplementary uplink carrier.

[0069] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the bandwidth portion used to transmit the uplink message is associated with an uplink carrier on which the MPE event is detected.

[0070] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the bandwidth portion used to transmit the uplink message is associated with a supplementary uplink carrier in a low frequency band.

[0071] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the PUSCH used to transmit the MPE MAC-CE is associated with a bandwidth portion in which the uplink message triggering the PRACH procedure is transmitted.

[0072] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the PUSCH used to transmit the MPE MAC-CE is associated with a bandwidth portion in a cell group including the Spcell.

[0073] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the uplink message is sent to trigger a scheduling request process on the PUCCH of the Spcell based at least in part on detecting the MPE event on one or more of the Scell or SPcell.

[0074] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the Spcell or Scell associated with the PUSCH for sending the MPE MAC-CE does not include the Scell or the SPcell in which the MPE event is detected.

[0075] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 500 includes canceling the MPE reporting of a cell associated with the MPE event based at least in part on sending the MPE MAC-CE.

[0076] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 500 includes: canceling the MPE report of the cell associated with the MPE event based at least in part on receiving information scheduling a new PUSCH, wherein the new PUSCH has a HARQ identifier corresponding to the PUSCH used to send the MPE MAC-CE.

[0077] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, process 500 includes canceling the MPE report of the cell associated with the MPE event based at least in part on receiving a DCI scrambled by the RNTI on a CORESET used to confirm the MPE MAC-CE.

[0078] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 500 includes: canceling the MPE report of the Scell or PScell associated with the MPE event at least in part based on the Scell or the PScell being deactivated, removed, or transitioning to a dormant state.

[0079] In a fourteenth aspect, alone or in combination with one or more of aspects 1 to thirteen, process 500 includes canceling the MPE report of the Scell or PScell associated with the MPE event based at least in part on a MAC reset affecting a serving cell corresponding to the Scell or the PScell.

[0080] In a fifteenth aspect, alone or in combination with one or more of aspects 1 to 14, process 500 includes canceling the MPE report of the Spcell associated with the MPE event based at least in part on the successful completion of a random access procedure initiated after switching from the first bandwidth portion to the second bandwidth portion due to the MPE event.

[0081] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 500 includes canceling the MPE reporting based at least in part on receiving DCI or RRC signaling that causes switching from the first bandwidth portion to the second bandwidth portion.

[0082] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 500 includes: causing switching from the first bandwidth portion to the second bandwidth portion on the Spcell based at least in part on the MPE event, terminating the ongoing random access procedure and initiating a new random access procedure.

[0083] In an eighteenth aspect, either alone or in combination with one or more of aspects one to seventeen, process 500 comprises resetting a preamble and a power ramp counter associated with the ongoing random access procedure based at least in part on initiating the new random access procedure.

[0084] Although Figure 5 Exemplary blocks of process 500 are shown, but in some aspects, similar to Figure 5 Process 500 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than described in

[0066] Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0085] Figure 6 6 is a conceptual data flow diagram illustrating the flow of data between various components in an example apparatus 602. Apparatus 602 may be a UE. In some aspects, apparatus 602 includes a receiving component 604, an MPE event detecting component 606, and / or a transmitting component 608. As shown, apparatus 602 may communicate with another apparatus 650 (e.g., a UE, a base station, or another wireless communication device) using receiving component 604 and / or transmitting component 608.

[0086] The receiving component 604 can receive one or more downlink communications from the apparatus 650. For example, the receiving component 604 can receive a random access response message, downlink control information (DCI), and / or other appropriate downlink communications that schedule a PUSCH in which the apparatus 602 will send a maximum permitted exposure (MPE) medium access control (MAC) control element (MAC-CE) to report an MPE event detected on a particular cell. Additionally or alternatively, the receiving component 604 can receive a DCI confirming the MPE MAC-CE, a DCI and / or RRC signaling that causes the apparatus 602 to switch bandwidth portions due to the reported MPE event, and / or the like. In some aspects, the receiving component 604 can include an antenna (e.g., the antenna 252), a receive processor (e.g., the receive processor 258), a controller / processor (e.g., the controller / processor 280), a transceiver, a receiver, and / or the like.

[0087] The MPE event detection component 606 can detect one or more MPE events that occur when the device 602 transmits information (e.g., on an uplink). For example, the MPE event detection component 606 can detect an MPE event based at least in part on a person, body part, etc. blocking an uplink beam, being located near an antenna subarray, etc. (e.g., using ultrasound, using wideband and / or narrowband ranging techniques, etc.). In some aspects, the MPE event detection component 606 can include a processor (e.g., the transmit processor 264, the receive processor 258, the controller / processor 280, etc.).

[0088] The transmission component 610 can send one or more uplink communications to the apparatus 650. For example, the transmission component 610 can send an uplink message on an uplink channel associated with a special cell (Spcell) to trigger an MPE report based at least in part on an MPE event, can send an MPE MAC-CE on a PUSCH associated with a Spcell or a supplementary cell (Scell) to report the MPE event, etc. In some aspects, the transmission component 610 can include an antenna (e.g., antenna 252), a transmit processor (e.g., transmit processor 264), a controller / processor (e.g., controller / processor 280), a transceiver, a transmitter, and the like.

[0089] The apparatus may include a device for performing Figure 5 An additional component of each box in the algorithm in the aforementioned process 500, etc. Figure 5 Each block in the aforementioned process 500 and the like may be performed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the stated process / algorithm, these components may be implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

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

[0091] Figure 7 7 is a diagram 700 illustrating an example of a hardware implementation for an apparatus 705 employing a processing system 710. In some aspects, the apparatus 705 may be a UE.

[0092] Processing system 710 may be implemented using a bus architecture, generally represented by bus 715. Bus 715 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of processing system 710. Bus 715 links together various circuits, including one or more processors and / or hardware components (represented by processor 720, components 604, 606, and / or 608), and computer-readable media / memory 725. Bus 715 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are not described in any further detail.

[0093] The processing system 710 can be coupled to a transceiver 730. The transceiver 730 is coupled to one or more antennas 735. The transceiver 730 provides a means for communicating with various other devices via a transmission medium. The transceiver 730 receives signals from the one or more antennas 735, extracts information from the received signals, and provides the extracted information to the processing system 710 (specifically, the receiving component 604). In addition, the transceiver 730 receives information from the processing system 710 (specifically, the transmitting component 608) and generates signals to be applied to the one or more antennas 735 based at least in part on the received information.

[0094] The processing system 710 includes a processor 720 coupled to a computer-readable medium / memory 725. The processor 720 is responsible for general processing, including executing software stored on the computer-readable medium / memory 725. When executed by the processor 720, the software causes the processing system 710 to perform the various functions described herein with respect to any particular device. The computer-readable medium / memory 725 may also be used to store data that is manipulated when the processor 720 executes the software. The processing system also includes at least one of components 604, 606, and / or 608. These components may be software components running on the processor 720, resident / stored in the computer-readable medium / memory 725, one or more hardware modules coupled to the processor 720, or some combination thereof.

[0095] In some aspects, the processing system 710 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 705 for wireless communication includes: means for transmitting an uplink message on an uplink channel associated with the Spcell to trigger an MPE report based at least in part on an MPE event; and means for transmitting an MPE MAC-CE on a PUSCH associated with the Spcell or Scell to report the MPE event. The aforementioned means may be one or more of the aforementioned components of the processing system 710 of the apparatus 602 and / or apparatus 705 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 710 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0096] As indicated above, Figure 7 Provided as an example. Other examples can be referenced Figure 7 The examples described are different.

[0097] The above disclosure provides illustration and description, but is not exhaustive, nor does it limit these aspects to the precise form disclosed. Modifications and variations can be made based on the above disclosure, or modifications and variations can be obtained from practice of these aspects.

[0098] 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.

[0099] 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.

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

[0101] Although the combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or not disclosed in the specification. Although each dependent claim listed below can only directly depend on one claim, the disclosure of each aspect includes each dependent claim in combination with each other claim item in the claim group. A phrase referring to "at least one of" a list item refers to any combination of these items (which includes a single member). For 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 ordering of a, b, and c).

[0102] Any element, action or instruction used in this application should not be interpreted as being key or fundamental unless so clearly described. In addition, as used herein, the articles "a" and "an" are intended to include one or more, which can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more (for example, related items, unrelated items, a combination of related items and unrelated items, etc.), which can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "containing", "having", "comprising" etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise clearly stated.

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: Based at least in part on a maximum permitted exposure (MPE) event, sending an uplink message on an uplink channel associated with the special cell to trigger an MPE report; as well as sending an MPE medium access control (MAC) control element (MAC-CE) to report the MPE event, wherein the MPE MAC-CE is sent on a physical uplink shared channel (PUSCH) associated with the special cell or the secondary cell (Scell), The uplink message is sent to perform at least one of the following: triggering a physical random access channel (PRACH) process on the special cell based at least in part on detecting the MPE event on the special cell; or triggering a scheduling request process on a physical uplink control channel (PUCCH) of the special cell based at least in part on detecting the MPE event on one or more of the Scell or the secondary primary cell.

2. The method according to claim 1, wherein The uplink message is sent on a bandwidth portion associated with the special cell and configured with PRACH resources.

3. The method according to claim 2, wherein: The bandwidth portion used to transmit the uplink message is associated with one or more of an uplink carrier associated with the special cell or a supplementary uplink carrier.

4. The method according to claim 2, wherein: The portion of bandwidth used to send the uplink message is associated with the uplink carrier on which the MPE event was detected.

5. The method according to claim 2, wherein: The bandwidth portion used to transmit the uplink message is associated with a supplemental uplink carrier in a low frequency band.

6. The method according to claim 1, wherein The PUSCH used to transmit the MPE MAC-CE is associated with a bandwidth portion in which the uplink message for triggering the PRACH procedure is transmitted.

7. The method according to claim 1, wherein The PUSCH used to transmit the MPE MAC-CE is associated with a bandwidth portion in a cell group including the special cell.

8. The method according to claim 1, wherein The special cells or Scells associated with the PUSCH for transmitting the MPE MAC-CE do not include the Scell or the secondary primary cell in which the MPE event is detected.

9. The method according to claim 1, further comprising: The MPE reporting for a cell associated with the MPE event is canceled based at least in part on sending the MPE MAC-CE.

10. The method according to claim 1, further comprising: The MPE reporting for a cell associated with the MPE event is canceled based at least in part on receiving information scheduling a new PUSCH having a hybrid automatic repeat request (HARQ) identifier corresponding to the PUSCH used to transmit the MPE MAC-CE.

11. The method according to claim 1 , further comprising: The MPE report for a cell associated with the MPE event is canceled based at least in part on receiving downlink control information scrambled by a radio network temporary identifier on a control resource set used to acknowledge the MPE MAC-CE.

12. The method according to claim 1, further comprising: The MPE reporting for an Scell or a primary supplementary cell (PScell) associated with the MPE event is canceled based at least in part on the Scell or the PScell being deactivated, removed, or transitioning to a dormant state.

13. The method according to claim 1, further comprising: The MPE reporting for an Scell or a primary supplementary cell (PScell) associated with the MPE event is canceled based at least in part on a MAC reset affecting a serving cell corresponding to the Scell or the PScell.

14. The method according to claim 1, further comprising: Based at least in part on a successful completion of a random access procedure initiated after switching from a first bandwidth portion to a second bandwidth portion due to the MPE event, canceling the MPE reporting for a special cell associated with the MPE event.

15. The method according to claim 1, further comprising: The MPE reporting is canceled based at least in part on receiving downlink control information (DCI) or radio resource control (RRC) signaling that causes a switch from the first bandwidth portion to the second bandwidth portion.

16. The method according to claim 1, further comprising: Based at least in part on the MPE event causing a switch from a first bandwidth portion to a second bandwidth portion on the special cell, terminating an ongoing random access procedure and initiating a new random access procedure.

17. The method according to claim 16, further comprising: Preamble and power ramp counters associated with the ongoing random access procedure are reset based at least in part on initiating the new random access procedure.

18. A user equipment for wireless communication, comprising: Memory; as well as One or more processors operatively coupled to the memory, the memory and the one or more processors configured to perform the method according to any one of claims 1 to 17.

19. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions, when executed by one or more processors of a user device, cause the one or more processors to perform the method according to any one of claims 1 to 17.

20. An apparatus for wireless communication, comprising: means for sending an uplink message on an uplink channel associated with a special cell to trigger a maximum permitted exposure (MPE) report based at least in part on an MPE event; as well as means for sending an MPE medium access control (MAC) control element (MAC-CE) to report the MPE event, wherein the MPE MAC-CE is sent on a physical uplink shared channel associated with the special cell or the supplementary cell, The uplink message is sent to perform at least one of the following: triggering a physical random access channel (PRACH) process on the special cell based at least in part on detecting the MPE event on the special cell; or triggering a scheduling request process on a physical uplink control channel (PUCCH) of the special cell based at least in part on detecting the MPE event on one or more of the Scell or the secondary primary cell.

Images