Maximum allowable exposure detection and mitigation with user equipment association with objects

Abstract

The network node may obtain a first location of an object associated with a user equipment (UE) based on a reflection of the received sensing signal. The UE may transmit the communication beam to the network node. The network node may obtain at least one of an indication of a second location of the UE or a beam direction of the communication beam. The network node may configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, a maximum allowable exposure (MPE) threshold, and the first location. The network node may send a configuration of the set of communication MPE attributes to the UE. The UE may receive the configuration of a set of communication MPE attributes.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application Serial No. 18 / 069,927, filed on December 21, 2022, entitled "MAXIMUM PERMISSIBLE EXPOSURE DETECTION AND MITIGATION UTILIZING USER EQUIPMENT TO OBJECT ASSOCIATIONS", which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to communication systems, and more particularly to systems for detecting and mitigating the maximum permissible exposure (MPE) levels of wireless devices. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology that is capable of supporting communication with multiple users by sharing available system resources. 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, and time - division synchronous code - division multiple access (TD - SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] The following presents a simplified overview of one or more aspects to provide a basic understanding of these aspects. This Summary is not an extensive overview of all contemplated aspects. It neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may include a user equipment (UE). The device may send a communication beam to a network node. The device may receive a configuration of a set of communication MPE attributes associated with the UE based on a maximum permissible exposure (MPE) threshold, the communication beam, and a location of an object associated with the UE.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and a device are provided. The device may include a network node. The device may obtain a first location of an object associated with the UE based on a reflection of a received sensing signal. The device may obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. The device may configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, the MPE threshold, and the first location.

[0009] To achieve the foregoing and related purposes, one or more aspects may include the features that are fully described hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame in accordance with various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe in accordance with various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame in accordance with various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe in accordance with various aspects of the present disclosure.

[0015] Figure 3Is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 Is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0017] Figure 5 Is a diagram illustrating an example of sensing based on measurements of sensed signals reflected from a target object according to various aspects of the present disclosure.

[0018] Figure 6 Is a diagram illustrating an example of a wireless communication system having multiple wireless devices, multiple objects, and multiple regions of interest according to various aspects of the present disclosure.

[0019] Figure 7 Is a communication flowchart illustrating an example of a UE and a network node according to various aspects of the present disclosure, the UE and the network node being configured to detect and mitigate MPE from the UE by leveraging a UE-object association between the UE and one or more objects.

[0020] Figure 8 Is a flowchart of a method of wireless communication.

[0021] Figure 9 Is a flowchart of a method of wireless communication.

[0022] Figure 10 Is a flowchart of a method of wireless communication.

[0023] Figure 11 Is a diagram illustrating an example of a hardware implementation for an example device and / or network entity.

[0024] Figure 12 Is a diagram illustrating an example of a hardware implementation for an example network entity.

[0025] Figure 13 Is a diagram illustrating an example of a hardware implementation for an example network entity. Detailed Description

[0026] The detailed description set forth below in connection with the appended drawings is a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] Certain aspects of a telecommunications system are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description, and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

[0028] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, processes, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0029] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded on a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. For example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] While aspects, embodiments, and / or use cases are described by way of some examples in this application, additional or different aspects, embodiments, and use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be embodied via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies herein. In some practical settings, devices incorporating the aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0031] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0032] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may consider the converged characteristics of base station functionality. For example, a split base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via respective fronthaul links. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

[0035] Each of these units (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0036] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially based on a functional split (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least in part based on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time aspects and non-real-time aspects of the control plane communication and user plane communication with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0039] The SMO framework 105 may be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources may be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0040] The non-RT RIC 115 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB to the near-RT RIC 125.

[0041] In some embodiments, to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or from network functions at the SMO framework 105 or at the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0042] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0043] Certain UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in an unlicensed spectrum such as 5 GHz. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0045] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0046] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0047] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used in this article, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used in this article, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0048] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 102 / UE 104. The transmission and reception directions of base station 102 may be the same or may not be the same. The transmission and reception directions of UE 104 may be the same or may not be the same.

[0049] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, a convergent (monolithic) base station with a baseband unit (BBU) (including CU and DU) and RU, or as a decomposed base station including one or more of CU, DU, and / or RU. A set of base stations including decomposed base stations and / or convergent base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0050] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that processes signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally speaking, one or more location servers 168 may include one or more location / locationing servers, which may include one or more of the GMLC 165, the LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. The signal measurement may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / location systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-round-trip time (multi-RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL arrival angle (UL-AoA) positioning), and / or one or more of other systems / signals / sensors).

[0051] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term "UE" may also apply to one or more companion devices, such as in a device constellation. One or more of these devices may access the network jointly and / or access the network individually.

[0052] Referring again to Figure 1 , in certain aspects, the UE 104 may have an MPE mitigation component 198, which may be configured to send a communication beam to a network node. The MPE mitigation component 198 may be configured to receive a configuration of a set of communication MPE attributes associated with the UE based on a maximum permissible exposure (MPE) threshold, the communication beam, and the location of an object associated with the UE. In certain aspects, the base station 102 may have an MPE detection component 199, which may be configured to obtain a first location of an object associated with the UE based on the reflection of a received sensing signal. The MPE detection component 199 may be configured to obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. The MPE detection component 199 may be configured to configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, the MPE threshold, and the first location. Although the following description may focus on the association between the UE and a target object that can be sensed using a wireless device, the concepts described herein may apply to any wireless device that can be associated with a target object, such as a network node or a roadside unit (RSU). Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0053] Figure 2A is a diagram 200 illustrating an example of a first subframe within the 5G NR frame structure. Figure 2BFIG. 230 is an illustration example of DL channels within a 5G NR subframe. Figure 2C FIG. 250 is an illustration example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is an illustration example of UL channels within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplexing (FDD) (wherein for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL), or can be Time Division Duplexing (TDD) (wherein for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2C the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all - DL and all - UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by the received Slot Format Indicator (SFI) (configured dynamically via Downlink Control Information (DCI) or semi - statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0054] Figures 2A to 2D An example of the frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more time slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each time slot can include 14 or 12 symbols, depending on whether the Cyclic Prefix (CP) is normal or extended. For normal CP, each time slot can include 14 symbols, and for extended CP, each time slot can include 12 symbols. The symbols on the DL can be Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP - OFDM) symbols. The symbols on the UL can be CP - OFDM symbols (for high - throughput scenarios) or Discrete Fourier Transform (DFT) - spread OFDM (DFT - s - OFDM) symbols (for power - constrained scenarios; limited to single - stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the Sub - Carrier Spacing (SCS) (see Table 1). The symbol length / duration can be scaled using 1 / SCS.

[0055]

[0056] Table 1: Parameter sets, SCS, and CP

[0057] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 µ slots / subframe. The subcarrier spacing can be equal to , where is parameter sets 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example of normal CP with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0058] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] As Figure 2A illustrated, some of the REs in the RE carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) (designated as R for a specific configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0060] Figure 2BIllustrates examples of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes six Resource Element Groups (REGs), and each REG includes 12 consecutive Resource Elements (REs) in the OFDM symbols of an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the Physical Cell Identifier (PCI). Based on this PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0061] As Figure 2C Illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0062] Figure 2DIllustrates examples of various UL channels within a subframe of a frame. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0063] Figure 3 Is a block diagram of communication between a base station 310 and a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0064] The transmit (Tx) processor 316 and the receive (Rx) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The Tx processor 316 handles the mapping to the signal constellation based on various modulation schemes such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0065] At the UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the receive (Rx) processor 356. The Tx processor 368 and the Rx processor 356 implement layer 1 functionality associated with various signal processing functions. The Rx processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by the Rx processor 356. The Rx processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 functionality and layer 2 functionality.

[0066] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0067] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between the logical channel and the transport channel, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0068] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the Tx processor 368 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the Tx processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0069] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives signals via its respective antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the Rx processor 370.

[0070] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0071] At least one of Tx processor 368, Rx processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 MPE mitigation component 198.

[0072] At least one of Tx processor 316, Rx processor 370, and controller / processor 375 may be configured to perform aspects associated with Figure 1 MPE detection component 199.

[0073] Figure 4 FIG. 400 is a diagram illustrating an example of UE positioning based on reference signal measurements. UE 404 may transmit UL-SRS 412 at time T SRS_Tx and receive a downlink positioning reference signal (PRS) (DL-PRS) 410 at time T PRS_Rx . TRP 406 may receive UL-SRS 412 at time T SRS_Rx and transmit DL-PRS 410 at time T PRS_Tx . UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine RTT 414 based on ||T SRS_Rx – T PRS_Tx | – |T SRS_Tx – T PRS_Rx ||. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements of downlink signals received from multiple TRPs 402, 406 and measured by UE 404 (i.e., |T SRS_Tx – T PRS_Rx |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), as well as measured TRP Rx-Tx time difference measurements of uplink signals transmitted from UE 404 at multiple TRPs 402, 406 (i.e., |T SRS_Rx – T PRS_Tx|) and UL-SRS-RSRP. The UE 404 uses the assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and the DL-PRS-RSRP of the received signal), and the TRP 402, 406 use the assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the location of the UE 404. Other methods for determining the RTT are possible, such as using DL-TDOA and / or UL-TDOA measurements.

[0074] DL-AoD positioning can utilize the measured DL-PRS-RSRP of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL-PRS-RSRP of the received signal, and the resulting measurement, together with the azimuth of departure (A-AoD), zenith angle of departure (Z-AoD), and other configuration information, is used to position the UE 404 relative to the adjacent TRPs 402, 406.

[0075] DL-TDOA positioning can utilize the DL reference signal time difference (RSTD) (and DL-PRS-RSRP) of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL RSTD (and DL-PRS-RSRP) of the received signal, and the resulting measurement, together with other configuration information, is used to position the UE 404 relative to the adjacent TRPs 402, 406.

[0076] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and UL-SRS-RSRP) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRP 402, 406 use the assistance data received from the positioning server to measure the UL-RTOA (and UL-SRS-RSRP) of the received signal, and the resulting measurement, together with other configuration information, is used to estimate the location of the UE 404.

[0077] UL-AoA positioning can utilize the measured azimuth of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRP 402, 406 use the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurement, together with other configuration information, is used to estimate the location of the UE 404.

[0078] Additional positioning methods can be used to estimate the location of UE 404, such as UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various techniques can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0079] Figure 5FIG. 500 is a diagram illustrating examples of sensing based on measurements of sensed signals. In one aspect, a wireless device 502 may perform monostatic sensing, where the wireless device 502 may transmit a set 512 of sensed signals at a target object 503, the target object 503 may reflect the set 512 of sensed signals as a reflected set 516 of sensed signals at the wireless device 502, and the wireless device 502 may measure the reflected set 516 of sensed signals from the target object 503. In another aspect, the wireless device 502 and the wireless device 504 may perform bistatic sensing, where the wireless device 502 may transmit a set 512 of sensed signals at a target object 503, the target object 503 may reflect the set 512 of sensed signals as a reflected set 514 of sensed signals at the wireless device 504, and the wireless device 504 may measure the reflected set 514 of sensed signals from the target object 503. In another aspect, the wireless device 502 and the wireless device 506 may perform multi-static sensing, where in addition to the wireless device 502 using monostatic sensing to measure the reflected set 516 of sensed signals from the target object 503, the wireless device 506 may also transmit a set 518 of sensed signals at the target object 503, the target object 503 may reflect the set 518 of sensed signals as a reflected set 520 of sensed signals at the wireless device 502, and the wireless device 502 may measure the reflected set 520 of sensed signals from the target object 503. In another aspect, the wireless device 502, the wireless device 504, and the wireless device 508 may perform multi-static sensing, where in addition to the wireless device 504 using bistatic sensing to measure the reflected set 514 of sensed signals from the target object 503, the wireless device 508 may also transmit a set 522 of sensed signals at the target object 503, the target object 503 may reflect the set 522 of sensed signals as a reflected set 524 of sensed signals at the wireless device 504, and the wireless device 504 may measure the reflected set 524 of sensed signals from the target object 503. Each wireless device may be any wireless device configured to transmit or receive wireless signals, such as a UE, a network node, a TRP, or a base station. For example, the wireless device 502 may be a network node configured to transmit the set 512 of sensed signals at the target object 503 and measure the reflected set 516 of sensed signals from the target object 503. As another example, the wireless device 502 may be a network node configured to transmit the set 512 of sensed signals at the target object 503, and the wireless device 504 may be a UE configured to measure the reflected set 514 of sensed signals from the target object 503.

[0080] Wireless device 502 may perform one or more sensing measurements on the reflected set 516 of the sensing signals and / or the reflected set 520 of the sensing signals. In one aspect, wireless device 502 may calculate the distance or range between wireless device 502 and target object 503 based on the round-trip time (RTT) between when wireless device 502 transmits the set 512 of sensing signals and when wireless device 502 receives the reflected set 516 of the sensing signals. In one aspect, wireless device 502 may calculate the distance or range traveled by the set 518 of sensing signals and the reflected set 520 of the sensing signals based on the time between when wireless device 506 transmits the set 518 of sensing signals and when wireless device 502 receives the reflected set 520 of the sensing signals. In one aspect, wireless device 502 may calculate the position of target object 503 based on multiple range or distance measurements, such as via triangulation using the known locations of wireless devices 502 and 506 and the calculated range or distance measurements. In one aspect, wireless device 502 may calculate the speed of target object 503 based on a first calculated position of target object 503 and a second calculated position of target object 503, the first calculated position being based on the reflected set 516 of the sensing signals and / or the reflected set 520 of the sensing signals measured at a first time, and the second calculated position being based on the reflected set 516 of the sensing signals and / or the reflected set 520 of the sensing signals measured at a second time. In one aspect, wireless device 502 may calculate the AoA of the reflected set 516 of the sensing signals and / or the AoD of the set 512 of the sensing signals based on multiple ports for transmitting the set 512 of sensing signals and multiple ports for receiving the reflected set 516 of the sensing signals. In one aspect, wireless device 502 may calculate the AoA of the reflected set 520 of the sensing signals and / or the AoD of the set 518 of the sensing signals based on multiple ports for transmitting the set 518 of sensing signals and multiple ports for receiving the reflected set 520 of the sensing signals.

[0081] Similarly, the wireless device 504 may perform one or more sensing measurements on the reflected set 514 of the sensing signals and / or the reflected set 524 of the sensing signals. In one aspect, the wireless device 504 may calculate the distance or range traveled by the set 512 of the sensing signals and the reflected set 514 of the sensing signals based on the time between when the wireless device 502 transmits the set 512 of the sensing signals and when the wireless device 504 receives the reflected set 514 of the sensing signals. In one aspect, the wireless device 504 may calculate the distance or range traveled by the set 522 of the sensing signals and the reflected set 524 of the sensing signals based on the time between when the wireless device 508 transmits the set 522 of the sensing signals and when the wireless device 504 receives the reflected set 524 of the sensing signals. In one aspect, the wireless device 504 may calculate the location of the target object 503 based on multiple range or distance measurements, such as via triangulation using the known locations of the wireless devices 502, 504, and 508 and the calculated range or distance measurements. In one aspect, the wireless device 504 may calculate the speed of the target object 503 based on a first calculated location of the target object 503 and a second calculated location of the target object 503, the first calculated location being based on the reflected set 514 of the sensing signals and / or the reflected set 524 of the sensing signals measured at a first time, and the second calculated location being based on the reflected set 514 of the sensing signals and / or the reflected set 524 of the sensing signals measured at a second time. In one aspect, the wireless device 504 may calculate the AoA of the reflected set 514 of the sensing signals and / or the AoD of the set 512 of the sensing signals based on multiple ports that transmit the set 512 of the sensing signals and multiple ports that receive the reflected set 514 of the sensing signals. In one aspect, the wireless device 504 may calculate the AoA of the reflected set 524 of the sensing signals and / or the AoD of the set 522 of the sensing signals based on multiple ports that transmit the set 522 of the sensing signals and multiple ports that receive the reflected set 524 of the sensing signals. To perform Doppler estimation or velocity estimation of a target object (such as the target object 503 in Figure 5 ), or a UE (such as the UE 104 in Figure 1 ), the receiver wireless node may be configured to measure the reflected set of the sensing signals at multiple time points.

[0082] In some aspects, a wireless device may use the measured sensing signals to generate a location profile of a target object 503. The location profile may include multiple attributes of the target object 503 related to its location, such as the position of the target object, the size of the target object, the shape of the target object, the orientation of the target object, the rate of the target object, the speed of the target object, the acceleration of the target object, the Doppler effect of the target object, the gait of the target object, the routine of the target object, the gesture of the target object, the posture of the target object, the micro-Doppler profile of the target object, or the radar cross section (RCS) of the target object. The wireless device may also measure non-RF wireless signals, such as measuring a temperature signal using a temperature sensor, measuring an audio signal using an audio sensor or a microphone, or measuring a light signal using a light sensor or a camera. The gait of the target object may be determined by measuring a minimum threshold number of periodic sequences of the foot movements of an animal target object. The routine of the target object may be determined by measuring a minimum threshold number of periodic sequences of the movements of a dynamic target object. The gesture of the target object may be determined by measuring the movement of a dynamic target object and comparing the movement with a known gesture library. Such a gesture library may include human activities, such as keystrokes on a surface or sign language gestures. The micro-Doppler profile of the target object may include a breathing rate based on the expansion and contraction of the chest of a human target object, a heart rate based on an audio signal from the heart of a human target object, or a rotational rate based on the rate of the fan blades of a mobile target object.

[0083] A network node or a UE configured to perform measurements on a reflected set of sensing signals may be configured to send a sensing signal report to a sensing server (e.g., LMF), which coordinates multiple wireless nodes to perform sensing on the target object. Performing sensing on a target object (such as target object 503) may be regarded as a consumer-grade radar with advanced detection capabilities (such as sensing both the location and temperature of the target object). Configuring a network node to sense such attributes of a target object may be used for contactless interaction or even device-free interaction with a device or a system. The network node may use one or more RF signals as sensing signals, thereby allowing a wireless system to utilize the same signals to perform both communication and sensing. For example, in a 3GPP NR wireless system, the network node may use millimeter wave (mmWave) RF signals in the frequency range specified by FR2 (24.25 GHz to 52.6 GHz), FR2x (52.6 GHz to 71 GHz), or FR4 (71 GHz to 114.25 GHz) to perform accurate range or distance detection of the target object.

[0084] In some aspects, a network node may be configured to detect and monitor an association or relationship between a UE and an object that can be sensed by a wireless device. For example, a human object may hold the UE or may wear a container that includes the UE, such as clothing or a bag. A human may carry a smart phone UE, may wear a smart watch UE, may wear a head-mounted display (HMD) UE, or may wear a backpack or carry a business bag that includes a laptop computer UE. As another example, a transportation object may have a UE mounted on the surface of the transportation. The transportation may be a car, a drone, or an automated guided vehicle (AGV). The transportation may have an infotainment system UE or an electronic control unit (ECU) UE mounted in the transportation.

[0085] When the object is associated with the UE, the network node may sense the object and the object may act as a proxy for the UE, or the network node may communicate with the UE and the UE may act as a proxy for the target object. This allows the network node to track and manage both the UE and the object by communicating with the UE without sensing the object, or by sensing the object without communicating with the UE, thereby reducing overhead. The network node may be configured to make such an association permanent or temporary. The network node may use one or more sensing schemes to sense one or more attributes of the object.

[0086] In some aspects, a network node may detect the radar cross section (RCS) of an object, the micro-Doppler profile of the object, the location of the object, or the temperature of the object. Such attributes may then be associated with a UE associated with the object. In one aspect, the network node may perform sensing of the object to assist in beam management (BM) for the associated UE, or to assist in maximum permissible exposure (MPE) detection and / or mitigation for the associated UE. In some aspects, the network node may perform positioning with the UE (e.g., LTE positioning or NR positioning), may perform sensing of the UE (e.g., if the UE is made of a material that reflects the sensing signal better than the object), or may communicate more with the UE (e.g., receive reports from the UE's magnetometer or accelerometer) to determine the attributes of the UE. Such attributes may then be associated with the object associated with the UE. In some aspects, a set of UEs may be associated with a set of objects, and the network node may communicate with one of the UEs or may sense one of the objects / UEs to track the entire aggregated set of devices (UEs and objects). In some aspects, the network node may track a lost object or a lost UE by determining when the association between the UE and the object is broken (e.g., the UE and the object are separated by a minimum threshold distance). In some aspects, UE-object association may be used to enhance public safety by using a system that tracks fewer UEs and / or objects in an area of interest. In some aspects, UE-object association may be used to track the health of an object (e.g., an elderly patient wearing or holding a UE), and send an alert to the UE if the monitored vital signs enter a dangerous threshold range, or trigger communication between the UE and an emergency device if the monitored vital signs enter a dangerous threshold range.

[0087] The wireless device may be configured to send a request that associates a potential associated user equipment (PAUE) with an object associated with an area of interest. A network node may receive the request and send a query to a network node set and a PAUE set to determine the capabilities of the network node set and the PAUE set, respectively. The network node may then select a subset of the network node set and a subset of the PAUE set as potential devices available for creating an association between the UE and the object. The network node may select the subsets based on the capabilities of the network nodes and the PAUEs (e.g., the ability of the network nodes to sense objects within the area of interest, the ability of the PAUEs to maintain an association with the objects). The network node may be configured to send a set of data collection schedules to the subset of the network nodes and the subset of the PAUEs to obtain a first set of attributes associated with the UE and a second set of attributes associated with the objects associated with the area of interest. The subset of the PAUEs may include the UE. The network node may receive the first set of attributes and the second set of attributes from the subset of the network nodes and the subset of the UEs based on the set of data collection schedules. The network node may send the association of the UE with the object based on the first set of attributes and the second set of attributes. The wireless device may receive the association of the UE with the object associated with the area of interest based on the request.

[0088] Figure 6FIG. 600 is a diagram illustrating an example of a wireless communication system having an area of interest 610, an area of interest 630, and an area of interest 650. Each of the areas of interest may be associated with a set of network nodes and a set of UEs. For example, area of interest 610 may be associated with RSU 602, TRP 604, UE 612, and UE 614. Area of interest 630 may be associated with TRP 604, TRP 606, UE 636, UE 632, and UE 634. Area of interest 650 may be associated with TRP 606, UE 652, and UE 654. The associated network nodes and / or the associated UEs may be considered wireless devices configured to sense an object within area of interest 610 using single-site sensing or bistatic sensing. For example, each of RSU 602, TRP 604, UE 612, and / or UE 614 may be configured to sense one or both of object 622 or object 624 within area of interest 610. Each of TRP 604, TRP 606, UE 636, UE 632, and UE 634 may be configured to sense one or both of object 642 or object 644 within area of interest 630. Each of TRP 606, UE 652, and UE 654 may be configured to sense one or each of object 662, object 664, object 666, or object 668 within area of interest 650. The wireless devices may use single-site sensing to send a sensing signal to an object and measure the reflected sensing signal from the object, or may cooperate with each other to send a sensing signal to the object, which may then be measured by another wireless device to measure the reflected sensing signal from the object. The wireless devices may indicate what type of sensors the sensing wireless devices may use to collect data from a target object, such as an RF antenna, a LIDAR sensor, a SONAR sensor, a vision camera, a thermal camera, or an audio microphone. A wireless device located closer to an object may be configured to measure an attribute of the object with higher accuracy than a wireless device located farther away from the object. For example, UE 612 may be configured to generate a micro-Doppler profile of object 622 (e.g., measure a person's heartbeat or measure a person's breathing rate), while RSU 602 may not be able to measure such an attribute of object 622 with such high accuracy because UE 612 is physically closer to object 622. As another example, RSU 602 may be configured to detect a gesture or gait of object 622 (e.g., determine whether object 622 is waving or kicking, or determine whether object 622 is bouncing or jumping), but TRP 604 may not be able to measure such an attribute of object 622 with such high accuracy because RSU 602 is physically closer to object 622 than TRP 604.In some aspects, a wireless device or network node may be configured to calculate the accuracy of the wireless device based on at least one of its distance from an object, the strength of a sensor that receives a reflected sensing signal, or the strength of a sensing signal transmitted to the object.

[0089] In addition to performing sensing, a UE in an area of interest may be configured to report attributes associated with the UE. In some aspects, the UE may be configured to report beam and channel state information (CSI) reference signal (CSI-RS) measurements, radio resource management (RRM) measurements, or sounding reference signal (SRS) transmission measurements. Such measurements may be used to indicate which UEs have the strongest or most reliable beam connections to a network node, and the beam directions for positioning measurements. On the other hand, the UE may be configured to report positioning reference signal (PRS) measurements, SRS positioning measurements, or measurements using other sensors (e.g., barometers, GNSS devices, inertial measurement units (IMUs)). Such measurements may be used to indicate the location of the UE and / or movement information of the UE.

[0090] A network node may be able to construct an association between a UE and an object based on attributes associated with the object collected by using sensing and based on attributes associated with the UE collected by communicating with the UE or by using sensing. For example, the network node may associate UE 612 with object 622 by determining that the location of UE 612 is within a threshold distance of object 622 and / or by determining that the shape profile of object 622 indicates that object 622 is holding UE 612. As another example, the network node may associate UE 614 with object 626 by determining that object 626 has a shape profile indicating that UE 614 is mounted on object 626. As another example, the network node may associate both UE 632 and UE 634 with object 642 by determining that both UE 632 and UE 634 are within a threshold distance of object 642. As another example, the network node may associate UE 652 with objects 662, 664, and 666 by determining that UE 652 is within a threshold distance of objects 662, 664, and 666 for a period of time while objects 662, 664, and 666 are moving. On the other hand, if there is no UE within a threshold distance of object 624, the network node may not associate object 624 with a UE. When the network node associates a set of UEs with a set of objects, the network node may use the attributes of one of the associated UEs or objects to derive the attributes of other associated UEs or objects. For example, if the network node associates object 642 with UE 632 and UE 634, the network node may perform a location on UE 632 to derive the locations of object 642 and UE 634, or may perform sensing on object 642 to derive the locations of UE 632 and UE 634. Similarly, if the network node associates UE 652 with objects (objects 662, 664, and 666), the network node may perform sensing on object 664 to derive the locations of UE 652, objects 662, and 666, or may perform a location on UE 652 to derive the locations of objects 662, 664, and 666. Thus, the network node may be able to track the location or movement of a UE by tracking the location of an object and vice versa, and may be able to track the locations or movements of multiple UEs and / or multiple objects by tracking the location or movement of a single UE or a single object.

[0091] Figure 7Communication flow chart 700 exemplifies an example of UE 702 and network node 704, which are configured to detect and mitigate MPE from UE 702 by leveraging the UE-object association between UE 702 and a set of objects 706. If UE 702 is used to detect MPE without network node 704, UE 702 may not be able to detect the presence of potential MPE victims such as humans outside the threshold range of UE 702. Network node 704 may be able to use sensing to detect a greater number of potential MPE victims regarding UE 702.

[0092] UE 702 and network node 704 may be configured to communicate with each other via a set of transmissions 708. UE 702 may send an MPE detection request 710 to network node 704. Network node 704 may receive MPE detection request 710. MPE detection request 710 may also include the location, orientation, Tx beam direction, or Tx power selection of UE 702. MPE detection request 710 may be sent via the following messages including MPE detection request 710: Radio Resource Control (RRC) message, UE assistance information message, Long-Term Evolution (LTE) Positioning Protocol (LPP) message, Medium Access Control (MAC) control element (MAC-CE), Uplink Control Information (UCI) message, Physical Uplink Control Channel (PUCCH) message, or Physical Random Access Channel (PRACH) message.

[0093] In response, at 712, network node 704 may obtain the UE-object association. Network node 704 may obtain the UE-object association in various ways. In one aspect, network node 704 may receive the UE-object association from another network node (such as the LMF or sensing server that associates UE 702 with the set of objects). In another aspect, network node 704 may perform single-site beam sensing to determine the location of the set of objects 706 within the region of interest around UE 702 (e.g., within 1 meter or within 10 meters), and may communicate with UE 702 or perform sensing on UE 702 to determine the location of UE 702, and may associate UE 702 with the set of objects 706 based on the location of each object in the retrieved set of objects 706 and the location of UE 702.

[0094] In one aspect, network node 704 may send a set 714 of sensing signals to a set 706 of objects. The set 706 of objects may reflect the set 714 of sensing signals to network node 704 as a set 716 of reflected sensing signals. At 718, network node 704 may perform sensing on the set 716 of reflected sensing signals. In another aspect, network node 704 may perform bistatic beam sensing with another wireless device to determine the location of the set 706 of objects, and may communicate with or perform sensing on UE 702 to determine the location of UE 702, and may associate UE 702 with the set 706 of objects based on the retrieved locations of the set 706 of objects and UE 702. In some aspects, network node 704 may search for other wireless devices around UE 702 to determine whether additional sensing signals from the other wireless devices can be used to sense human objects in the set 706 of objects near UE 702. For example, network node 704 may identify a wireless device around UE 702 that can send sensing signals capable of centimeter-level accuracy (e.g., a TRP or another UE other than UE 702), or may use another sensor capable of centimeter-level accuracy to receive signals (e.g., using the camera or LIDAR sensor of UE 702 or another UE other than UE 702 to view the objects, and the other UE may view the area around UE 702). Network node 704 may limit its search for wireless devices based on the maximum allowable power used around the human object, antenna gain, array gain, relative location between the transmitting wireless device and UE 702, carrier frequency of the wireless device, or MPE government regulations. Network node 704 may select wireless devices for bistatic sensing based on the MPE profiles of human objects specific to those wireless devices (e.g., the MPE profile of a TRP or the MPE profile of the panel type used at the base station).

[0095] In another aspect, UE 702 may perform monostatic or bistatic sensing on the set 706 of objects, and may send a sensing report to network node 704 that includes the set 706 of objects (e.g., all objects within 1 or 2 meters of UE 702). For example, UE may send a set 720 of sensing signals to the set 706 of objects. The set 706 of objects may reflect the set 720 of sensing signals to UE 702 as a set 722 of reflected sensing signals. At 724, UE 702 may perform sensing on the set 722 of reflected sensing signals. UE 702 may send a sensing report 726 to network node 704. Network node 704 may receive the sensing report 726 from UE 702. In some aspects, UE 702 may send a UE-object association using an MPE detection request 710. The MPE detection request 710 may contain a UE-object association profile associated with UE 702.

[0096] The network node 704 or the UE 702 may filter out objects that are not potential MPE victims. For example, the network node 704 may filter out objects that do not have human attributes (e.g., objects with a specific size, RCS, temperature, micro-Doppler signature (e.g., due to breathing or heartbeat), movement pattern (e.g., speed, gait, routine)), and the network node 704 may use these human attributes to detect whether an object is a potential MPE victim. The network node 704 may build an association between the UE 702 and a set 706 of objects.

[0097] At 728, the network node 704 may configure a set 730 of MPE attributes based on the UE 702 and the set 706 of objects. In some aspects, the network node 704 may identify the set 706 of objects by type, e.g., classifying each of the objects in the set 706 as an inanimate object, a machine, an animal, or a human. At least one of these types may be associated with an MPE profile. In some aspects, the inanimate object type may not be associated with an MPE profile, but the human type may be associated with an MPE profile. The MPE profile may be a profile of the maximum threshold of radio waves to which an object may be exposed, such as the maximum threshold of RF waves to which an object may be exposed. The network node 704 may identify the set 706 of objects by type to filter out objects with an associated MPE profile, such that the network node 704 configures MPE attributes for objects with an associated MPE profile.

[0098] In some aspects, the network node 704 may associate human objects with size characteristics, radar cross section (RCS) characteristics, temperature characteristics, micro-Doppler characteristics, and / or movement pattern characteristics. For example, the size characteristics of a human object may be between one foot and seven feet tall, and between half a foot and three feet wide. In another example, the RCS characteristics of a human object may be between 0.5m 2 to 2m 2 . In another example, the temperature characteristics of a human object may be between 80°F - 110°F. The temperature of an object may be determined by a temperature sensor at the UE 702. In another example, the micro-Doppler signature of a human object may be a breathing pattern or a heartbeat pattern detected using a micro-Doppler radar signal. In another example, the movement pattern of a human object may be a walking motion, a jumping motion, a speed less than 15 mph, a gait, or a routine, such as drinking water or using a mobile phone device. If at least one, at least two, or at least three or more human characteristics are detected from the set 706 of objects, the network node 704 may determine that the set 706 of objects is human.

[0099] In some aspects, if the set of objects 706 is determined to be human, the network node 704 can estimate the minimum distance between the surface of the UE 702 and the set of objects 706. For example, the network node 704 can determine that the UE 702 is in the hand of the set of objects 706, in which case the network node 704 can estimate that human tissue exists on the surface of the UE 702. In another example, the network node 704 can determine that the UE 702 is in the backpack of the set of objects 706, in which case the network node 704 can estimate that the human tissue is at least 5 cm away from the surface of the UE 702. By estimating the distance between the human tissue and the UE 702, if the set of objects 706 is human, the network node 704 can more accurately calculate the upper limit of the MPE metric and attributes for sending / receiving signals from / to the UE 702 without exceeding the safe MPE value of the set of objects 706.

[0100] In some aspects, the network node 704 can search for any object in the set of objects 706 around the UE 702 based on the sensing performed at 718 and / or the sensing report 726 received from the UE 702, and the object can be a human within a threshold distance (such as a range of 1 meter). The network node 704 can determine each human object within the threshold distance of the UE 702 as a potential victim of the MPE from the UE 702. In some aspects, the network node 704 can associate the human object closest to the UE 702 as the associated object for UE-object association.

[0101] In some aspects, the network node 704 may estimate the tightness of the association between the UE 702 and each object in the set 706 of objects that has a type associated with the MPE profile. The tightness metric may be a function of the following: the reliability of the sensed object (e.g., link quality, RCS of the object, sensing resolution), the estimated distance between the UE 702 and the center of the object, the estimated distance between the UE 702 and the organization of the object (e.g., if the object is holding the UE 702 or if the UE 702 is inside a container worn by the object), the Tx beam direction of the UE 702 relative to the object, or the movement pattern / direction of the object relative to the UE 702 (e.g., if the object is moving towards or away from the UE 702). The tightness metric may be used to adjust the value of the MPE attribute. For example, a high tightness metric may be used for the UE 702 estimated to be held by a human object, which may be associated with a low MPE attribute (e.g., the maximum power for the transmit beam), and a low tightness metric may be used for the UE 702 estimated to be moving away from the human object, which may be associated with a relatively high MPE attribute. The network node 704 may use the default MPE profile of the human object and adjust the value of one or more MPE attributes of the MPE profile based on the tightness metric. In some aspects, the network node 704 may be configured to periodically perform sensing on one or more objects in the set 706 of objects associated with the MPE profile to update the tightness metric. In some aspects, the network node 704 may be configured to increase the periodicity (time between sensing) in response to a decrease in the value of the tightness metric and decrease the periodicity in response to an increase in the value of the tightness metric.

[0102] In one aspect, the network node 704 may detect how far each potential MPE victim is from the UE 702 and set the maximum Tx power of the UE 702 based on that distance. The set 730 of MPE attributes may be referred to as the configuration of the MPE attributes because the set 730 of MPE attributes may be used by the UE 702 to determine the upper or lower threshold to comply with when communicating with the network node 704 via the set 734 of transmissions. The network node 704 may send the set 730 of MPE attributes to the UE 702. The UE 702 may receive the set 730 of MPE attributes from the network node 704. The network node 704 may send the set 730 of MPE attributes in a system information message, RRC signaling, MAC-CE, and / or DCI (PDCCH). At 732, the UE 702 may configure the set 734 of transmissions with the network node 704 based on the set 730 of MPE attributes. Then, the UE 702 may communicate with the network node 704 via the set 734 of transmissions based on the set 730 of MPE attributes.

[0103] The set 730 of MPE attributes may include at least one of the following: (a) the location of an object associated with the UE 702, (b) the minimum distance between the object and the UE 702, (c) a proposed modification attribute of the Tx beam of the UE 702, (d) a proposed power back-off attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power. The communication beam may include at least one of a first indication of the location of the UE or a second indication of the beam direction of the communication beam. The location of the object may be reported as an absolute location (e.g., coordinates), or may be reported relative to the location of the UE 702, such as the estimated minimum distance of the object from the UE 702. The UE 702 may be configured to change its Tx beam based on the set 730 of MPE attributes, for example, by ensuring that the power used for the Tx beam remains below the proposed Tx power, by adopting the proposed duty cycle, or by applying the proposed power back-off.

[0104] Figure 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE404, UE 612, UE 614, UE 632, UE 634, UE 636, UE 652, UE 654, UE 702; wireless device 502, wireless device 504, wireless device 506, wireless device 508; apparatus 1104). At 902, the UE may send a communication beam to a network node. For example, 802 may be performed by Figure 7 the UE 702 in, which may communicate with the network node 704 via the set of transmissions 708, and the set of transmissions may include the transmission of the communication beam. Additionally, 802 may be performed by Figure 1 、 Figure 3 or Figure 11 the component 198 in.

[0105] At 804, the UE may receive a configuration of a set of communication MPE attributes associated with the UE based on an MPE threshold, the communication beam, and the location of an object associated with the UE. For example, 804 may be performed by Figure 7 the UE 702 in, which may receive the set 730 of MPE attributes associated with the UE 702 based on the MPE threshold of the network node 704 (e.g., from an MPE profile), the set of transmissions 708 (which may form a baseline of how much power the UE 702 is currently using to send communication signals), and the location of the set 706 of objects associated with the UE 702 determined according to the sensing report 726 and / or the sensing performed at 718. Additionally, 804 may be performed by Figure 1 、 Figure 3 or Figure 11 the component 198 in.

[0106] Figure 9 is a flowchart 900 of a method for wireless communication. This method can be performed by a UE (e.g., UE 104, UE 350, UE 404, UE 612, UE 614, UE 632, UE 634, UE 636, UE 652, UE 654, UE 702; wireless device 502, wireless device 504, wireless device 506, wireless device 508; apparatus 1104). At 902, the UE can transmit sensing beams. For example, 902 can be performed by Figure 7 UE 702 in Figure 1 , which can transmit a set 720 of sensing signals at a set 706 of objects. Additionally, 902 can be performed by Figure 3 or Figure 11 component 198 in

[0107] At 904, the UE can receive reflections of the sensing beams from objects associated with the UE. For example, 904 can be performed by Figure 7 UE 702 in Figure 1 , which can receive a set 722 of reflected sensing signals from a set 706 of objects associated with UE 702. Additionally, 904 can be performed by Figure 3 or Figure 1 component 198 in

[0108] At 906, the UE can measure the reflections of the received sensing beams. For example, 906 can be performed by Figure 7 UE 702 in Figure 1 , which, when performing sensing on the set 722 of reflected sensing signals, can measure the reflections of the received set 722 of reflected sensing signals at 724. Additionally, 906 can be performed by Figure 3 or Figure 11 component 198 in

[0109] At 908, the UE can calculate the locations of the objects associated with the UE based on the measured reflections of the received sensing beams. For example, 908 can be performed by Figure 7 UE 702 in Figure 1 , which can calculate the location of each object in the set 706 of objects at 724 based on the measured reflections of the received set 722 of reflected sensing signals, or calculate only the locations of the objects associated with UE 702. Additionally, 908 can be performed by Figure 3 or Figure 11 component 198 in

[0110] At 910, the UE may calculate at least one of size, temperature, micro-Doppler signature, or movement pattern based on the reflections of the received sensing beams, where the communication beam may include an indication of the likelihood that an object is human based on at least one of the calculated size, temperature, micro-Doppler signature, or movement pattern. For example, 910 may be performed by Figure 7 the UE 702 in Figure 1 , Figure 3 or Figure 11 , which may calculate at least one of size, temperature, micro-Doppler signature, or movement pattern based on the set 722 of reflected sensing signals at 724. The sensing report 726 may include an indication of the likelihood that an object in the set 706 of objects is human based on at least one of the calculated size, temperature, micro-Doppler signature, or movement pattern. Additionally, 910 may be performed by

[0111] In 912, the UE may send a communication beam to a network node. For example, 912 may be performed by Figure 7 the UE 702 in Figure 1 , Figure 3 or Figure 11 , which may communicate with the network node 704 via the set 708 of transmissions, which includes the transmission of the communication beam. The UE 702 may also send the sensing report 726 to the network node 704. Additionally, 912 may be performed by

[0112] In 914, the UE may receive a configuration of a set of communication MPE attributes associated with the UE based on an MPE threshold, the communication beam, and the location of the object associated with the UE. The communication beam may include an indication of the calculated location of the object associated with the UE. For example, 914 may be performed by Figure 7 the UE 702 in Figure 1 , Figure 3 or Figure 11 , which may receive the set 730 of MPE attributes associated with the UE 702 based on the MPE threshold of the network node 704, the set 708 of transmissions, and the location of the set 706 of objects associated with the UE 702 determined according to the sensing report 726. The sensing report 726 may include an indication of the calculated location of the object associated with the UE. Additionally, 914 may be performed by

[0113] In 916, the UE may send a request to the network node to perform MPE detection on the UE. For example, 916 may be performed by Figure 7 the UE702 in Figure 1 , Figure 3or Figure 11 Component 198 in

[0114] At 918, the UE may receive configuration based on a request to perform MPE detection. For example, 918 may be performed by the UE 702 in Figure 7 which may receive MPE attributes 730 based on an MPE detection request 710 to perform MPE detection. Additionally, 918 may be performed by Component 198 in Figure 1 、 Figure 3 or Figure 11 Component 198 in

[0115] Figure 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; TRP 402, TRP 406, TRP 604, TRP 606; wireless device 502, wireless device 504, wireless device 506, wireless device 508; RSU 602; network node 704; network entity 1102, network entity 1202, network entity 1360). At 1002, the network node may obtain a first location of an object associated with the UE based on a reflection of a received sensing signal. For example, 1002 may be performed by the network node 704 in Figure 7 which may obtain a first location of a set of objects 706 associated with the UE 702 at 712 based on a set 716 of reflected sensing signals. Additionally, 1002 may be performed by Component 199 in Figure 1 、 Figure 3 、 Figure 11 or Figure 12 Component 199 in

[0116] At 1004, the network node may obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. For example, 1004 may be performed by the network node 704 in Figure 7 which may obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. Additionally, 1004 may be performed by Component 199 in Figure 1 、 Figure 3 、 Figure 11 or Figure 12 Component 199 in

[0117] At 1006, the network node may configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location. For example, 1006 may be performed by Figure 7is executed by network node 704, which can configure a set of communication MPE attributes associated with the UE based on at least one of a second location or beam direction, an MPE threshold, and a first location. Additionally, 1006 can be executed by Figure 1 , Figure 3 , Figure 11 or Figure 12 by components 199 in.

[0118] Figure 11FIG. 1100 is a diagram illustrating an example of a hardware implementation for apparatus 1104. Apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., cellular RF transceivers). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, apparatus 1104 may further include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, apparatus 1104 may further include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power supply 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include on-chip transceivers (TRXs) (or in some cases, only a receiver (Rx)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using antenna 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or the RU associated with the network entity 1102 via the transceiver 1122 through one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each separately include computer-readable media / memory 1124', 1106'. The additional memory module 1126 may also be considered computer-readable media / memory. Each computer-readable media / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1124 / application processor 1106, causes the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software.The cellular baseband processor 1124 / application processor 1106 can be a component of the UE 350 and can include the memory 360 and / or at least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359. In one configuration, the device 1104 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the device 1104 can be the entire UE (e.g., see. Figure 3 of the UE 350) and include additional modules of the device 1104.

[0119] As discussed above, component 198 can be configured to send communication beams to a network node. Component 198 can be configured to receive a configuration of a set of communication MPE attributes associated with a UE based on an MPE threshold, a communication beam, and a location of an object associated with the UE. Component 198 can be within cellular baseband processor 1124, application processor 1106, or both cellular baseband processor 1124 and application processor 1106. Component 198 can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1104 can include various components configured for various functions. In one configuration, device 1104 (and in particular cellular baseband processor 1124 and / or application processor 1106) can include components for sending communication beams to a network node. Device 1104 can include components for receiving a configuration of a set of communication MPE attributes associated with a UE based on an MPE threshold, a communication beam, and a location of an object associated with the UE. The set of communication MPE attributes can include at least one of the following: (a) a location of an object associated with the UE, (b) a minimum distance between the object and the UE, (c) a proposed modification attribute of a Tx beam, (d) a proposed power back-off attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power. The communication beam can include at least one of a first indication of a location of the UE or a second indication of a beam direction of the communication beam. Device 1104 can include components for sending sensing beams. Device 1104 can include components for receiving reflections of sensing beams from an object associated with the UE. Device 1104 can include components for measuring reflections of the received sensing beams. Device 1104 can include components for calculating a location of an object associated with the UE based on the measured reflections of the received sensing beams. The communication beam can include the calculated location of an object associated with the UE. The communication beam can include an indication of a likelihood that the object is human based on the measured reflections of the received sensing beams. Device 1104 can include components for calculating at least one of size, temperature, micro-Doppler signature, or movement pattern based on the received reflections of the sensing beams. The indication of the likelihood that the object is human can be based on at least one of the calculated size, temperature, micro-Doppler signature, or movement pattern. The object can be not in physical contact with the UE. Device 1104 can include components for sending a request to perform MPE detection on the UE to a network node. Device 1104 can include components for receiving a configuration based on the request to perform MPE detection. The request can include a UE-object association profile associating the UE with the object. The request can include at least one of a second location of the UE, an orientation, a Tx beam direction, or a Tx power selection.The request may include an indication of the periodicity for the network node to send a configuration to the UE. Apparatus 1104 may include components for sending a request to perform MPE detection by sending an RRC message, a UE assistance information message, an LPP message, a MAC-CE, a UCI message, a PUCCH message, or a PRACH message including the request to perform MPE detection. Apparatus 1104 may include components for receiving a configuration of a set of communication MPE attributes by receiving at least one of a system information message, an RRC message, a MAC-CE, a DCI, or a PDCCH message including the configuration of the set of communication MPE attributes. The components may be component 198 of apparatus 1104 configured to perform the functions recited by the components. As described above, apparatus 1104 may include a Tx processor 368, an Rx processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the Tx processor 368, the Rx processor 356, and / or the controller / processor 359 configured to perform the functions recited by these components.

[0120] Figure 12FIG. 1200 is a diagram illustrating an example of a hardware implementation for network entity 1202. Network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. Network entity 1202 may include at least one of CU 1210, DU 1230, or RU 1240. For example, depending on the layer functionality handled by component 199, network entity 1202 may include CU 1210; both CU 1210 and DU 1230; each of CU 1210, DU 1230, and RU 1240; DU 1230; both DU 1230 and RU 1240; or RU 1240. CU 1210 may include CU processor 1212. CU processor 1212 may include on-chip memory 1212'. In some aspects, CU 1210 may also include additional memory module 1214 and communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link, such as the F1 interface. DU 1230 may include DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include additional memory module 1234 and communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include additional memory module 1244, one or more transceivers 1246, antenna 1280, and communication interface 1248. RU 1240 communicates with UE 104. On-chip memories 1212’, 1232’, 1242’ and additional memory modules 1214, 1234, 1244 may each be considered computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0121] As discussed above, component 199 may be configured to obtain a first location of an object associated with a UE based on the reflection of a received sensing signal. Component 199 may be configured to obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. Component 199 may be configured to configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location. Component 199 may be within one or more processors of one or more of CU 1210, DU 1230, and RU 1240. Component 199 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1202 may include a variety of components configured for various functions. In one configuration, network entity 1202 may include components for obtaining a first location of an object associated with a UE based on the reflection of a received sensing signal. Network entity 1202 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. Network entity 1202 may include components for configuring a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location. Network entity 1202 may include components for configuring a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location, and may include receiving, from the UE, a signal including a sensing report associated with an object associated with the UE. Network entity 1202 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by receiving, from the UE, a signal including at least one of an indication of the second location of the UE or a second beam direction of the signal. Network entity 1202 may include components for obtaining a first location of an object associated with the UE by transmitting a sensing signal. Network entity 1202 may include components for obtaining a first location of an object associated with the UE by receiving a reflection of the sensing signal from the object. Network entity 1202 may include components for obtaining a first location of an object associated with the UE, and may include measuring the reflection of the received sensing signal. Network entity 1202 may include components for calculating a likelihood that the object is human based on the measured reflection of the received sensing signal. Network entity 1202 may include components for calculating a likelihood that the object is human by calculating at least one of size, temperature, micro-Doppler signature, or movement pattern based on the reflection of the received sensing signal. The indication of the likelihood that the object is human may be based on at least one of the calculated size, temperature, micro-Doppler signature, or movement pattern.The network entity 1202 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by transmitting a positioning signal. The network entity 1202 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by receiving a response to the positioning signal from the UE. The network entity 1202 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by calculating a location of the second location of the UE or a second beam direction of the received response based on the received response. The network entity 1202 may include components for sending a set of configured communication MPE attributes associated with the UE to the UE. The network entity 1202 may include components for sending the set of configured communication MPE attributes by transmitting at least one of a system information message, an RRC message, a MAC-CE, a DCI, or a PDCCH message including the set of configured communication MPE attributes. The set of communication MPE attributes may include at least one of the following: (a) a location of an object associated with the UE, (b) a minimum distance between the object and the UE, (c) a proposed modification attribute of a Tx beam, (d) a proposed power backoff attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power. The network entity 1202 may include components for receiving a request from the UE to perform MPE detection. The network entity 1202 may include components for configuring a set of communication MPE attributes associated with the UE based on the request to perform MPE detection. The request may include a UE-object association profile associating the UE with an object. The request may include at least one of a location, an orientation, a Tx beam direction, or a Tx power selection of the UE. The request may include a periodic second indication for the network node to send the set of configured communication MPE attributes to the UE. The network entity 1202 may include components for receiving the request to perform MPE detection by receiving at least one of an RRC message, a UE assistance information message, an LPP message, a MAC-CE, a UCI message, a PUCCH message, or a PRACH message including the request to perform MPE detection. The components may be component 199 of the network entity 1202 configured to perform the functions recited by the components. As described above, the network entity 1202 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375. Thus, in one configuration, these components may be the Tx processor 316, the Rx processor 370, and / or the controller / processor 375 configured to perform the functions recited by these components.

[0122] Figure 13FIG. 1300 is a diagram illustrating an example of a hardware implementation for network entity 1360. In one example, network entity 1360 may be within core network 130. Network entity 1360 may include network processor 1312. Network processor 1312 may include on-chip memory 1312'. In some aspects, network entity 1360 may further include additional memory module 1314. Network entity 1360 communicates with CU 1302 directly (e.g., backhaul link) or indirectly (e.g., through RIC) via network interface 1380. On-chip memory 1312' and additional memory module 1314 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Processor 1312 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0123] As discussed above, component 199 may be configured to obtain a first location of an object associated with a UE based on a reflection of a received sensing signal. Component 199 may be configured to obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. Component 199 may be configured to configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location. Component 199 may be within processor 1312. Component 199 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1360 may include a variety of components configured for various functions. In one configuration, network entity 1360 may include components for obtaining a first location of an object associated with a UE based on a reflection of a received sensing signal. Network entity 1360 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. Network entity 1360 may include components for configuring a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location. Network entity 1360 may include components for configuring a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location, and may include receiving, from the UE, a signal including a sensing report associated with an object associated with the UE. Network entity 1360 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by receiving, from the UE, a signal including at least one of an indication of the second location of the UE or a second beam direction of the signal. Network entity 1360 may include components for obtaining a first location of an object associated with the UE by transmitting a sensing signal. Network entity 1360 may include components for obtaining a first location of an object associated with the UE by receiving a reflection of the sensing signal from the object. Network entity 1360 may include components for obtaining a first location of an object associated with the UE, and may include measuring a reflection of the received sensing signal. Network entity 1360 may include components for calculating a likelihood that the object is human based on the measured reflection of the received sensing signal. Network entity 1360 may include components for calculating a likelihood that the object is human by calculating at least one of a size, a temperature, a micro-Doppler signature, or a movement pattern based on a reflection of the received sensing signal. An indication of the likelihood that the object is human may be based on at least one of the calculated size, temperature, micro-Doppler signature, or movement pattern.The network entity 1360 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by transmitting a positioning signal. The network entity 1360 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by receiving a response to the positioning signal from the UE. The network entity 1360 may include components for obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE by calculating a location of the second location of the UE or a second beam direction of the received response based on the received response. The network entity 1360 may include components for transmitting a set of configured communication MPE attributes associated with the UE to the UE. The network entity 1360 may include components for transmitting the set of configured communication MPE attributes by transmitting at least one of a system information message, an RRC message, a MAC-CE, a DCI, or a PDCCH message including the set of configured communication MPE attributes. The set of communication MPE attributes may include at least one of the following: (a) a location of an object associated with the UE, (b) a minimum distance between the object and the UE, (c) a proposed modification attribute of a Tx beam, (d) a proposed power backoff attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power. The network entity 1360 may include components for receiving a request from the UE to perform MPE detection. The network entity 1360 may include components for configuring a set of communication MPE attributes associated with the UE based on the request to perform MPE detection. The request may include a UE-object association profile associating the UE with an object. The request may include at least one of a location, an orientation, a Tx beam direction, or a Tx power selection of the UE. The request may include a periodic second indication for the network node to transmit the set of configured communication MPE attributes to the UE. The network entity 1360 may include components for receiving the request to perform MPE detection by receiving at least one of an RRC message, a UE assistance information message, an LPP message, a MAC-CE, a UCI message, a PUCCH message, or a PRACH message including the request to perform MPE detection. The component may be a component 199 of the network entity 1360 configured to perform the functions recited by the component.

[0124] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart may be rearranged. Further, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0125] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that the action will occur if the condition is met, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. shall not be used as a substitute for the word "component." Thus, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0126] As used herein, the phrase "based on" should not be construed to refer to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be construed as "at least based on A", unless specifically stated otherwise.

[0127] A device configured to "output" data (such as, a transmission, a signal, or a message) can (for example) transmit the data using a transceiver, or can transfer the data to a device that transmits the data. A device configured to "obtain" data (such as, a transmission, a signal, or a message) can, for example, receive the data using a transceiver, or can obtain the data from a device that receives the data.

[0128] The following aspects are merely illustrative and can be combined with other aspects or teachings described herein without limitation.

[0129] Aspect 1 is a method for wireless communication at a UE, where the method can include transmitting a communication beam to a network node. The method can include receiving a configuration of a set of communication MPE attributes associated with the UE based on an MPE threshold, the communication beam, and a location of an object associated with the UE.

[0130] Aspect 2 is the method according to Aspect 1, where the set of communication MPE attributes can include at least one of the following: (a) the location of the object associated with the UE, (b) the minimum distance between the object and the UE, (c) a proposed modification attribute of a Tx beam, (d) a proposed power backoff attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power.

[0131] Aspect 3 is the method according to any one of Aspects 1 or 2, where the communication beam can include at least one of a first indication of the location of the UE or a second indication of the beam direction of the communication beam.

[0132] Aspect 4 is the method according to any one of Aspects 1 to 3, where the method can include transmitting a sensing beam. The method can include receiving a reflection of the sensing beam from the object associated with the UE. The method can include measuring the received reflection of the sensing beam. The method can include calculating the location of the object associated with the UE based on the measured received reflection of the sensing beam. The communication beam can include the calculated location of the object associated with the UE.

[0133] Aspect 5 is the method according to Aspect 4, where the communication beam can include an indication of the likelihood that the object is human based on the measured received reflection of the sensing beam.

[0134] Aspect 6 is the method according to aspect 5, wherein the method may include calculating at least one of size, temperature, micro-Doppler signature, or movement pattern based on the reflection of the received sensing beam. The indication of the likelihood that the object is the human may be based on at least one of the calculated size, the temperature, the micro-Doppler signature, or the movement pattern.

[0135] Aspect 7 is the method according to aspect 6, wherein the object may not be in physical contact with the UE.

[0136] Aspect 8 is the method according to any one of aspects 1 to 7, wherein the method may include sending a request to perform MPE detection on the UE to the network node. Receiving the configuration may be based on the request to perform the MPE detection.

[0137] Aspect 9 is the method according to aspect 8, wherein the request may include a UE-object association profile associating the UE with the object.

[0138] Aspect 10 is the method according to any one of aspects 8 or 9, wherein the request may include at least one of a second location, an orientation, a Tx beam direction, or a Tx power selection of the UE.

[0139] Aspect 11 is the method according to any one of aspects 8 to 10, wherein the request may include an indication of the periodicity for the network node to send the configuration to the UE.

[0140] Aspect 12 is the method according to any one of aspects 8 to 11, wherein sending the request to perform the MPE detection may include sending an RRC message, a UE assistance information message, an LPP message, a MAC-CE, a UCI message, a PUCCH message, or a PRACH message including the request to perform the MPE detection.

[0141] Aspect 13 is the method according to any one of aspects 1 to 12, wherein receiving the configuration of the set of communication MPE attributes may include receiving at least one of a system information message, an RRC message, a MAC-CE, a DCI, or a PDCCH message including the configuration of the set of communication MPE attributes.

[0142] Aspect 14 is a method of wireless communication at a network node, wherein the method may include obtaining a first location of an object associated with a UE based on a reflection of a received sensing signal. The method may include obtaining at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE. The method may include configuring a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location.

[0143] Aspect 15 is the method according to 14, wherein configuring the set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location may include receiving, from the UE, a signal including a sensing report associated with the object associated with the UE.

[0144] Aspect 16 is the method according to any one of Aspects 14 or 15, wherein obtaining at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE may include receiving, from the UE, a signal including at least one of the indication of the second location of the UE or a second beam direction of the signal.

[0145] Aspect 17 is the method according to any one of Aspects 14 to 16, wherein obtaining the first location of the object associated with the UE may include transmitting the sensing signal. Obtaining the first location of the object associated with the UE may include receiving a reflection of the sensing signal from the object. Obtaining the first location of the object associated with the UE may include measuring the reflection of the received sensing signal.

[0146] Aspect 18 is the method according to Aspect 17, wherein the method may include calculating a likelihood that the object is a human based on the measured reflection of the received sensing signal.

[0147] Aspect 19 is the method according to any one of Aspects 14 to 18, wherein calculating the likelihood that the object is the human may include calculating at least one of size, temperature, micro-Doppler signature, or movement pattern based on the reflection of the received sensing signal. The indication of the likelihood that the object is the human may be based on at least one of the calculated size, the temperature, the micro-Doppler signature, or the movement pattern.

[0148] Aspect 20 is the method according to any one of aspects 14 to 19, wherein obtaining at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE may include transmitting a positioning signal. Obtaining at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE may include receiving a response to the positioning signal from the UE. Obtaining at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE may include calculating the location of the second location of the UE or the second beam direction of the received response based on the received response.

[0149] Aspect 21 is the method according to any one of aspects 14 to 20, wherein the method may include transmitting a set of configured communication MPE attributes associated with the UE.

[0150] Aspect 22 is the method according to aspect 21, wherein transmitting the set of configured communication MPE attributes may include transmitting at least one of a system information message, an RRC message, a MAC-CE, a DCI, or a PDCCH message including the set of configured communication MPE attributes.

[0151] Aspect 23 is the method according to any one of aspects 14 and 22, wherein the set of communication MPE attributes may include at least one of the following: (a) the location of the object associated with the UE, (b) the minimum distance between the object and the UE, (c) a proposed modification attribute of the Tx beam, (d) a proposed power back-off attribute, (e) a proposed duty cycle attribute, or (f) a proposed Tx power.

[0152] Aspect 24 is the method according to any one of aspects 14 to 23, wherein the method may include receiving a request from the UE to perform MPE detection. Configuring the set of communication MPE attributes associated with the UE may be based on the request to perform the MPE detection.

[0153] Aspect 25 is the method according to any one of aspects 14 to 24, wherein the request may include a UE-object association profile associating the UE with the object.

[0154] Aspect 26 is the method according to any one of aspects 14 to 25, wherein the request may include at least one of the location, orientation, Tx beam direction, or Tx power selection of the UE.

[0155] Aspect 27 is the method according to any one of aspects 14 to 26, wherein the request may include a periodic second indication for the network node to send the set of configured communication MPE attributes to the UE.

[0156] Aspect 28 is the method according to any one of aspects 14 to 27, wherein receiving the request to perform the MPE detection may include receiving an RRC message, a UE assistance information message, an LPP message, a MAC-CE, a UCI message, a PUCCH message, or a PRACH message including the request to perform the MPE detection.

[0157] Aspect 29 is a device for wireless communication, the device including: a memory; and at least one processor coupled to the memory, and at least partially based on the information stored in the memory, the at least one processor is configured to implement any one of aspects 1 to 28.

[0158] Aspect 30 is the device according to aspect 29, the device further including at least one of an antenna or a transceiver coupled to the at least one processor.

[0159] Aspect 31 is a device for wireless communication, the device including components for implementing any one of aspects 1 to 28.

[0160] Aspect 32 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor is configured to: send a communication beam to a network node; and receive a configuration of a set of communication MPE attributes associated with the UE based on a maximum allowable exposure (MPE) threshold, the communication beam, and a location of an object associated with the UE.

2. The apparatus according to claim 1, wherein the set of communication MPE attributes includes at least one of the following: the location of the object associated with the UE; the minimum distance between the object and the UE; suggested modification attributes of a transmit (Tx) beam; suggested power back-off attributes; suggested duty cycle attributes; or suggested Tx power.

3. The apparatus according to claim 1, wherein the communication beam includes at least one of a first indication of the location of the UE or a second indication of the beam direction of the communication beam.

4. The apparatus according to claim 1, wherein the at least one processor is further configured to: send a sensing beam; receive a reflection of the sensing beam from the object associated with the UE; measure the received reflection of the sensing beam; and calculate the location of the object associated with the UE based on the measured received reflection of the sensing beam, wherein the communication beam includes an indication of the calculated location of the object associated with the UE.

5. The apparatus according to claim 4, wherein the communication beam includes an indication of the likelihood that the object is human based on the measured received reflection of the sensing beam.

6. The apparatus according to claim 5, wherein the at least one processor is further configured to: calculate at least one of size, temperature, micro-Doppler signature, or movement pattern based on the received reflection of the sensing beam, wherein the indication of the likelihood that the object is the human is based on at least one of the calculated size, the temperature, the micro-Doppler signature, or the movement pattern.

7. The apparatus according to claim 6, wherein the object is not in physical contact with the UE.

8. The apparatus according to claim 1, the apparatus further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: Send a request to the network node to perform MPE detection on the UE via the transceiver, where, for receiving the configuration, the at least one processor is configured to receive the configuration based on a request to perform the MPE detection.

9. The apparatus according to claim 8, wherein the request includes a UE-object association profile associating the UE with the object.

10. The apparatus according to claim 8, wherein the request includes at least one of a second location of the UE, an orientation, a transmit (Tx) beam direction, or a Tx power selection of the UE.

11. The apparatus according to claim 8, wherein the request includes an indication of the periodicity for the network node to send the configuration to the UE.

12. The apparatus according to claim 8, wherein, To send the request for performing the MPE detection, the at least one processor is configured to: Send a radio resource control (RRC) message, a UE assistance information message, a long term evolution (LTE) positioning protocol (LPP) message, a media access control (MAC) control element (MAC-CE), an uplink control information (UCI) message, a physical uplink control channel (PUCCH) message, or a physical random access channel (PRACH) message including the request for performing the MPE detection.

13. The device according to claim 1, wherein To receive the configuration of the set of communication MPE attributes, the at least one processor is configured to: Receive at least one of a system information message, a radio resource control (RRC) message, a media access control (MAC) control element (MAC-CE), a downlink control information (DCI), or a physical downlink control channel (PDCCH) message including the configuration of the set of communication MPE attributes.

14. An apparatus for wireless communication at a network node, the apparatus comprising: A memory; And At least one processor coupled to the memory and at least partially based on information stored in the memory, the at least one processor is configured to: Obtain a first location of an object associated with a user equipment (UE) based on a reflection of a received sensing signal; Obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE; And Configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, a maximum permissible exposure (MPE) threshold, and the first location.

15. The device according to claim 14, wherein To obtain the first location of the object associated with the UE, the at least one processor is configured to: Receive a signal from the UE including a sensing report associated with the object associated with the UE.

16. The apparatus according to claim 14, wherein, To obtain at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE, the at least one processor is configured to: Receive a signal from the UE including at least one of the indication of the second location of the UE or the second beam direction of the signal.

17. The apparatus according to claim 14, wherein To obtain the first location of the object associated with the UE, the at least one processor is configured to: Send the sensing signal; Receive a reflection of the sensing signal from the object; and Measure the reflection of the received sensing signal.

18. The apparatus according to claim 17, wherein the at least one processor is further configured to: Calculate a likelihood that the object is a human based on the measured reflection of the received sensing signal.

19. The apparatus according to claim 18, wherein, To calculate the likelihood that the object is the human, the at least one processor is configured to: Calculate at least one of size, temperature, micro-Doppler signature, or movement pattern based on reflections of the received sensing signal, wherein the indication of the likelihood that the object is the human is based on at least one of the calculated size, the calculated temperature, the calculated micro-Doppler signature, or the calculated movement pattern.

20. The apparatus according to claim 14, wherein, To obtain at least one of the indication of the second location of the UE or the beam direction of the beam associated with the UE, the at least one processor is configured to: Transmit a positioning signal; Receive a response to the positioning signal from the UE; and Calculate the location of the second location of the UE or the second beam direction of the received response based on the received response.

21. The apparatus according to claim 14, the apparatus further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: Transmit, via the transceiver, a set of configured communication MPE attributes associated with the UE.

22. The device according to claim 21, wherein, To transmit the set of configured communication MPE attributes, the at least one processor is configured to: Transmit at least one of a system information message, a radio resource control (RRC) message, a media access control (MAC) control element (MAC-CE), a downlink control information (DCI), or a physical downlink control channel (PDCCH) message including the set of configured communication MPE attributes.

23. The apparatus according to claim 14, wherein the set of communication MPE attributes includes at least one of the following: The location of the object associated with the UE; The minimum distance between the object and the UE; A proposed modification attribute of a transmit (Tx) beam; A proposed power backoff attribute; A proposed duty cycle attribute; or A proposed Tx power.

24. The apparatus according to claim 14, wherein the at least one processor is further configured to: Receive a request to perform MPE detection on the UE from the UE, wherein, To configure the set of communication MPE attributes associated with the UE, the at least one processor is configured to configure the set of communication MPE attributes associated with the UE based on the request to perform the MPE detection.

25. The apparatus according to claim 24, wherein the request includes a UE-object association profile associating the UE with the object.

26. The apparatus according to claim 24, wherein the request includes at least one of the location, orientation, transmit (Tx) beam direction, or Tx power selection of the UE.

27. The apparatus according to claim 24, wherein the request includes a periodic second indication for the network node to transmit the set of configured communication MPE attributes to the UE.

28. The apparatus according to claim 24, wherein, To receive the request to perform the MPE detection, the at least one processor is configured to: Receive a radio resource control (RRC) message, a UE assistance information message, a long term evolution (LTE) positioning protocol (LPP) message, a media access control (MAC) control element (MAC-CE), an uplink control information (UCI) message, a physical uplink control channel (PUCCH) message, or a physical random access channel (PRACH) message that includes the request to perform the MPE detection.

29. A method for wireless communication at a user equipment (UE), the method comprising: Transmit a communication beam to a network node; And Receive a configuration of a set of communication MPE attributes associated with the UE based on a maximum permissible exposure (MPE) threshold, the communication beam, and a location of an object associated with the UE.

30. A method for wireless communication at a network node, the method comprising: Obtain a first location of an object associated with a user equipment (UE) based on a reflection of a received sensing signal; Obtain at least one of an indication of a second location of the UE or a beam direction of a beam associated with the UE; And Configure a set of communication MPE attributes associated with the UE based on at least one of the second location or the beam direction, an MPE threshold, and the first location.

Images