Codebook adjustment or beam switching based on internal interference of UE sensors or interfaces

Abstract

The UE may determine the use of a sensor or interface of the UE; and in response, may adjust at least one of beam selection, transmit power, operation mode, or carrier aggregation for the UE. The base station may receive an indication from the UE that a carrier configured for the UE has an impact on the performance of the sensor or interface of the UE. The base station may adjust the configuration of the carrier or adjust the uplink grant for the carrier in response to receiving the indication from the UE.

Description

[0001] Priority claim

[0002] This patent application claims the benefit of and priority to application No. 16 / 661,853, filed on October 23, 2019, entitled “CODEBOOK ADJUSTMENT OR BEAMSWITCHING BASED ON INTERNAL INTERFERENCE TO A SENSOR OR INTERACE OF A UE,” which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference in its entirety. background Technical Field

[0004] The present disclosure relates generally to communication systems, and more particularly to wireless communications involving user equipment (UE). Background Art

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies 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.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR 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 can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0008] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define 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 a more detailed description that will be presented later.

[0009] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus determines usage of a sensor or interface of the UE. In response to determining usage of the sensor or interface, the apparatus adjusts at least one of beam selection, transmit power, operation mode, or carrier aggregation for the UE.

[0010] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The apparatus configures a UE for carrier aggregation. The apparatus receives an indication from the UE that a carrier configured for the UE has an impact on the performance of a sensor or interface of the UE. The apparatus adjusts the configuration of the carrier or adjusts an uplink grant for the carrier in response to receiving the indication from the UE.

[0011] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and access network in accordance with various aspects presented herein.

[0013] Figure 2A , 2B , 2C, and 2D are diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

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

[0015] Figure 4A is a diagram illustrating an example of internal interference of components of a UE in accordance with various aspects presented herein.

[0016] Figure 4BAn example of image degradation of a camera image due to internal interference of components of a UE in accordance with various aspects presented herein is illustrated.

[0017] Figure 5 is an example communication flow between a UE and a base station according to various aspects presented herein.

[0018] Figure 6 is a flow chart of a wireless communication method according to various aspects presented herein.

[0019] Figure 7 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus according to various aspects presented herein.

[0020] Figure 8 is a diagram illustrating an example of a hardware implementation for a device employing a processing system in accordance with various aspects presented herein.

[0021] Fig. 9 is a flow chart of a wireless communication method according to various aspects presented herein.

[0022] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus according to various aspects presented herein.

[0023] Fig.11 is a diagram illustrating an example of a hardware implementation for a device employing a processing system in accordance with various aspects presented herein. DETAILED DESCRIPTION

[0024] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0025] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be 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 may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0026] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including 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, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0027] Accordingly, in one or more example embodiments, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, the computer program may include a computer executable to implement all steps of the method, function, or other element associated method described throughout the present disclosure. Each function may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store instructions or data structures in the form of computer executable code that can be accessed by a computer.

[0028] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0029] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0030] Base stations 102 may communicate wirelessly with UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also known as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also known as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be over one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth for each carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The 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 to DL compared to UL). The 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 carrier may be referred to as a secondary cell (SCell).

[0031] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The 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). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0032] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0033] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0034] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gB node (gNB), or another type of base station. Some base stations 180 (such as gNBs) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UEs 104. When a gNB operates in mmW or near mmW frequencies, the gNB may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. A mmW base station, such as base station 180, may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0035] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0036] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0037] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0038] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0039] Refer again Figure 1In some aspects, the UE 104 may include an adjustment component 198 configured to determine the use of a sensor or interface of the UE, and in response, adjust at least one of beam selection, transmit power, operating mode, or carrier aggregation for the UE. In some aspects, additionally or alternatively, the UE 104 may include an adjustment component 198 or other device to determine the use of a sensor or interface of the UE, and in response, send an indication to a base station (such as base station 120 / 180) indicating that the carrier used by the UE for carrier aggregation has an impact on the sensor or interface of the UE. As an example, the indication is sent in at least one of a UE assistance information message or an inter-device coexistence message. Optionally, the UE (such as UE 104) is configured to receive an adjusted configuration for the carrier or a reduced uplink grant for the carrier in response to the indication sent to the base station. In some aspects, the base station 102 / 180 may include a carrier aggregation adjustment component 199 configured to: receive an indication from the UE 104 that a carrier configured for the UE has an impact on the performance of a sensor or interface of the UE, and adjust the configuration of the carrier or adjust the uplink grant for the carrier in response to receiving the indication from the UE. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0040] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , 2CIn the example provided, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0041] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 with 14 symbols per slot and parameter design μ=0 with 1 slot per subframe is provided. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

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

[0043] like Figure 2A As illustrated in FIG, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as Rx for one specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0044] Figure 2B An example of various DL channels within a subframe of an explanation frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth, as well as the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0045] As in Figure 2CAs illustrated in FIG, some REs carry DM-RSs for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. Although not shown, the UE may transmit a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0046] Figure 2D An example of various UL channels within a subframe of an illustration frame. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0047] Figure 33 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 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 broadcasting 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 of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with 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 through HARQ, priority handling, and logical channel prioritization.

[0048] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including 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 (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0049] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a 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 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). 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 signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

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

[0051] Similar to the functionality described in conjunction 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 delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0052] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding 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 separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0053] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0054] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The 199 combines all aspects.

[0056] As combined Figure 1 As described, UE 104 may transmit and receive communications with base station 180 using beamformed signals from base station 180. As an example, narrow beam directions may be used for mmW communications. Beams may be formed using multiple antenna elements that receive inputs from phase shifters and amplifiers to form desired beams. A codebook may be used to determine the amplitude and phase for each antenna element. In one example, a beam may be selected based on selecting or switching between different beam steering vectors. In some examples, the beam steering vector may include different scaling factors for the corresponding amplitudes assigned to these antenna elements. Beams may be selected or switched based on beam training. Beam switching may be based on external sensors (such as proximity sensors or thermal sensors) to limit human exposure to radio frequency (RF) radiation from wireless devices and / or for thermal mitigation. Additionally or alternatively, beam switching may be based on the mobility of the UE, for example, based on inputs from accelerometers, gyroscopes, and magnetometers that may indicate rotation of the UE or linear motion of the UE. RF beam switching may be performed so that a radio frequency integrated circuit (RFIC) may be stable within 100-200ns (e.g., within the CP window of a symbol). In some implementations, components of the UE that adjust the beam or phase may include circuits including dedicated hardware and / or signal processors to perform beam switching using digital baseband signal processing. In addition, mixed signal circuits for converting digital signals to analog signals may be applied, as well as RF mixers for further converting baseband signals to radio frequency. The exact implementation of the UE components (respectively) in hardware / software, baseband / RF splitting, and / or digital / analog splitting may depend on the specific application and design constraints imposed on the overall system.

[0057] The antenna elements of the UE used to generate beamformed signals can radiate interference that causes internal interference of various components of the UE. For example, some antenna elements can cause interference to the camera or the Mobile Industry Processor Interface (MIPI) lines that carry camera data from the camera sensor to the Image Signal Processor (ISP). This interference from the antenna elements can cause image degradation and can affect images in both still and video modes. Figure 4A An example UE 401 is illustrated that includes a camera 402 connected to a motherboard 406 via a flexible printed circuit (FPC) 404. The FPC 404 may include a mobile industry processor interface (MIPI) line that carries camera data from a camera sensor (e.g., camera 402) to an image signal processor (ISP) 414. The UE 401 may include multiple components (such as RF chips 408 and 410) that select beams and / or phase shifts for transmissions from the UE. Although only two RF chips are illustrated, the UE may include any number of components that select beams and / or phase shifts for transmissions from antennas of the UE. Using at least some of the components of the UE 401 may affect camera performance. For example, Figure 4A The RF chip 408 is illustrated as causing radiation interference 403 to the FPC 404 that carries data from the camera 402 to the ISP 414. The UE 401 includes multiple antenna panels 412a, 412b, 412c, 412d. Each antenna panel may include multiple antenna elements 416, as illustrated with respect to antenna panels 412a and 412d. The number of antenna elements that enables the UE to communicate in different spatial directions may result in placing at least one antenna element in a position that may cause interference to a sensor or interface of the UE. In one example, the UE may include more than 60 antenna elements. In order to place more than 60 antenna elements within the UE, some antenna elements may be located near a sensor or interface. Similarly, the use of focused beams / focused radiation may cause additional interference to specific sensors or interfaces. Therefore, the use of some antenna panels, some antenna elements and / or some transceivers may cause internal interference to a sensor or interface of the UE. Figure 4A The example in illustratively illustrates that antenna elements 416a and 416b may cause interference 407 to camera 402 or a MIPI line (eg, which may include FPC 404).

[0058] Figure 4BAn example of a camera image 422 at a display of a UE 420 is illustrated, which has artifacts 424 in the camera image 422 caused by internal interference from some antenna elements. The effect may be more pronounced for UEs that include multiple camera assemblies or have pop-up cameras. A pop-up camera may include a camera that is physically raised or moved relative to the body of the UE to expose the camera or lens for taking pictures. The degradation of the image may be improved at higher transmit powers used by the UE. The degradation of the image may be improved when a narrower beam or a more focused radiation pattern is used by the UE.

[0059] To address potential impacts on a sensor or interface of a UE due to internal interference, the UE may determine when the sensor or interface is active, and in response, may perform actions to limit performance impacts caused by the internal interference. In some examples, the UE may determine when a camera is active, and may take actions to limit internal interference to the camera.

[0060] Examples of reducing the impact on camera performance can be applied to various situations. There may be multiple situations where the UE's camera and modem will be concurrently active. For example, beamforming using a particular beam may affect camera performance for video conferencing using a camera for real-time video and an antenna for streaming real-time video using mmW. For virtual reality (VR) / extended reality (XR) applications that use cameras and use beamformed transmissions (e.g., based on mmW or 5G NR) to communicate high-speed data, camera performance may be affected. In another example, when connected to a 5G NR network or using beam-transmitted communications, camera performance may be affected for drone applications that use cameras for still images or videos. In another example, camera performance may be affected when recording or taking pictures while using a data network (such as a 5G NR data network, a data network using beamforming, etc.).

[0061] For mmW communications, the codebook may include information for the UE to communicate with the base station in a specific spatial direction. For example, the entries of the codebook may be associated with steering vectors, one steering vector for each beam, wherein each steering vector includes a phase shift and / or a signal scaling factor for each antenna element. The numbering of the entries in the codebook may form a code to identify each beam. The entries of the codebook may be associated with unidirectional or multidirectional beams, extending the lobes of the transmitted signal energy toward more than one direction. Different entries of the codebook may include beams facing the same direction, but are distinguished by narrower or wider beams (e.g., by changing the width of the lobe). Therefore, a wider beam can use a reduced number of activated antenna elements. The codebook may include a set of transceivers and a set of antenna elements that should be used to communicate in one or more spatial directions. The codebook may indicate the direction(s) that the UE can form, as well as the set of transceivers and the set of antenna elements that should be activated for each beam to communicate using a specific spatial angle. In some examples, the codebook may include a subset of entries associated with beams pointing in the same or similar directions. For example, a subset may include, for example, a wider parent beam using a limited set of transceivers and antenna elements, and a number of further beams that refine the parent beam using antenna elements and transceiver sets that are more or less restricted than the parent beam to form narrower lobes or reduce side lobes.

[0062] In some aspects, beam switching and / or codebook pruning may be used to avoid or prohibit the use of specific beams from a codebook. In some examples, the use of certain antenna elements, beams that may affect sensors or interfaces of the UE may be avoided or prohibited in the codebook. As an example, beam switching and / or codebook pruning may be used to limit interference to sensors or interfaces (e.g., MIPI that carries camera data). With beam switching, different beams of the codebook may be selected to limit interference. With codebook pruning, codebook entries that may affect sensors / interfaces may be removed, avoided, or disabled. When sensors and / or interfaces associated with a camera are in use, codebook pruning may be applied or the use of certain beams may be restricted. When the sensor / interface is not in use, the restriction may be removed or the pruned beam may be restored.

[0063] Figure 5 An example communication flow 500 between a UE 502 and a base station 504 including various aspects described herein is illustrated. Optional aspects are illustrated with dashed lines. At 503, the UE may detect that a particular sensor or interface of the UE 502 is active, e.g., being used. In response, at 505, the UE 502 may apply codebook pruning to remove codebook entries that may affect the sensor / interface.

[0064] The example of limiting internal interference to camera performance is merely to illustrate the concept of adjusting UE operation to avoid internal interference to components of UE 502. Various aspects may be applied to other sensors or interfaces of UE 502 that may cause internal interference.

[0065] The codebook may include a field for each beam that identifies whether the beam affects a specific sensor or interface of the UE 502. The antenna element design along with the radiation pattern and classification of the antenna (such as dipole or patch type) may be used to identify beams that may have an impact on a specific sensor or interface of the UE. Based on the circuit board design (e.g., the distance of the antenna array and components that control the antenna array from the sensor / interface), antenna elements that may cause glitches or noise to the sensor / interface and degrade the performance of the sensor / interface may be identified. For example, antenna elements that may cause interference to the camera MIPI lines, resulting in degraded camera performance, may be identified.

[0066] In some examples, UE 502 may perform a characterization process to determine beams that affect a sensor / interface, as illustrated at 501. The UE may turn on a sensor or interface and perform a beam sweeping procedure across different beams that may be used by the UE. The UE may perform the beam sweeping procedure using different transmit powers. The UE may determine the interference caused to the sensor / interface for different beams or for different transmit power levels. The UE may then identify beams that have a threshold impact on the operation of the sensor / interface. For example, the UE may turn on a camera application and may determine the amount of image noise or image degradation caused by a potential beam set. The UE may perform measurements on the beams using different transmit power amounts. The UE may then identify beams or transmit power amounts that cause a specific amount of noise to the camera image. The threshold may be a threshold stored at the UE.

[0067] As an example, the codebook may include a camera and / or sensor / interface impact field that indicates whether the beam affects the performance of a camera or other sensor / interface at the UE 502. The field may be in the form of a bit mask. The indication may include a true / false indication of whether the beam affects the camera. For example, a "true" indication may be included for any beam that uses one or more antenna elements or phase shift components that affect camera operation (e.g., affects the camera MIPI line). The UE 502 may use this additional information in the codebook to determine which beams may cause noise and artifacts to the camera operation.

[0068] When the camera and / or sensor / interface is in use, the UE 502 may prune the codebook to avoid using the beam(s) indicated as affecting the camera, as illustrated at 505. For example, a codebook manager (CBM) at the UE 502 may output a candidate beam list (CBL) that does not include beams indicated in the codebook as having an impact on the sensor or interface. When use of the sensor / interface is terminated (e.g., the camera application is closed), the pruned beams may be restored and a more comprehensive CBL may be used to select beams for the UE 502.

[0069] The codebook may indicate the power level at which the beam begins to affect the sensor / interface, rather than just indicating in a true / false manner whether the beam affects the sensor / interface. For example, for a given beam in the codebook, only a specific power level may be used on the beam when the sensor or interface is in use. In addition to weights used for phase shifters to create beams, the codebook may also include indications of power levels that can be used for beams in situations where a camera or other sensor / interface is used. In this example, the UE 502 may prune the codebook based not only on the use of the sensor / interface, but also on the current transmit power of the UE 502 to avoid selecting beams that would otherwise affect the sensor / interface at the current transmit power. Beams that do not affect the camera and / or sensor / interface at the current transmit power may be included in the CBL for the UE.

[0070] In another example, as a supplement or replacement for the above, restrictions outside the codebook field can be used to avoid using antenna elements, antenna panels or beams that affect a specific sensor / interface of UE502 when the specific sensor / interface is being used. In this example, as illustrated at 507, when a sensor / interface (e.g., a camera) is being used, UE 502 can avoid or exclude a set including one or more antenna elements / antenna panels / beams. For example, UE 502 can only use antenna elements or antenna panels that are not prohibited when the sensor / interface is being used. UE 502 can perform beam switching without using prohibited antenna elements / antenna panels / beams by querying replacement / adjacent beams of the current beam. This approach can be applied without changing the codebook. UE 502 can limit the use of antenna elements / antenna panels / beams when the affected sensor / interface is being used, and can select antenna elements / antenna panels / beams without restriction when the sensor / interface is not in use.

[0071] Rather than codebook pruning or avoiding selection of antenna elements / antenna panels / beams, when a particular sensor / interface is in use, the UE 502 may perform other adjustments when using beams that affect the sensor / interface. The UE may limit the transmit power (e.g., maximum transmit power TRPmax) and / or effective isotropic radiated power (EIRPmax), as illustrated at 509. The UE 502 may limit the maximum transmit power and / or effective isotropic radiated power to a level below that causes an impact on the sensor / interface. For example, a power may be determined above which radiated interference to the MIPIPHY line causes artifacts in the camera image. When the camera is in use, the UE 502 may limit the transmit power (e.g., TRPmax and / or EIRPmax) to a power level below the determined power level to avoid internal interference to the MIPI PHY line. When the camera is not in use, the UE 502 may use a transmit power higher than the determined power level.

[0072] When a sensor / interface is being used and a beam, antenna element, and / or antenna panel that may affect the performance of the sensor / interface is being used, the UE 502 may fall back to a wider beam, as illustrated at 510. For example, the UE may switch to a parent beam that is wider than the current beam that affects the sensor / interface. The wider beam may limit interference to the sensor / interface. For example, the wider beam may limit internal interference to the MIPIPHY lines and may avoid causing artifacts in the camera image.

[0073] When the sensor / interface is being used, the UE 502 may switch to a different radio access technology (RAT) (e.g., from a first RAT to a second RAT), as illustrated at 511. The switch may be based on the sensor / interface being used, and the beams, antenna elements, and / or antenna panels that may affect the performance of the sensor / interface being used. For example, the UE 502 may change from operating using a mmW-based RAT to operating using a sub-6 RAT or other RAT. In some examples, the UE 502 may switch mode preferences during camera operation and fall back to a sub-6 RAT or a different RAT. The switch may also be based on whether the second RAT to which the switch is to be performed can meet the wireless communication needs of the UE. Once the sensor / interface is no longer used, the UE may switch back to using the first RAT, such as a mmW-based RAT or an original RAT. In some examples, the UE may send a request to a base station (such as, base station 504) or an indication that the UE may switch from a first RAT to a different second RAT. As an example, the request is sent in at least one of a UE assistance information message, an inter-device coexistence message, a radio resource control (RRC) message, or any other suitable message. In response, the base station initiates a corresponding inter-RAT handover and sends a corresponding message to the UE. Upon receiving the message including the inter-RAT handover indication, the UE performs the indicated handover to the target second RAT (e.g., based on a related handover protocol). The UE may further notify the network when the sensor / interface is no longer in use. To this end, the UE sends a corresponding message, using the second RAT to request or indicate that the UE can switch to the first RAT. In one example, the UE may indicate its ability to switch to the first RAT. In response, the base station may initiate an inter-RAT handover from the second RAT to the first RAT. The UE may receive a corresponding message that causes the UE to perform a handover from the second RAT to the first RAT (e.g., based on a related handover protocol).

[0074] Wireless communication using (or some) specific beams with mmW carriers may also degrade the performance of sensors or interfaces at UE 502. When the sensor / interface is being used, UE 502 may make adjustments to the wireless communication using a specific carrier, as illustrated at 512. For example, if a carrier may affect the performance of the sensor / interface of UE 502 and the sensor / interface is being actively used, UE 502 may drop the carrier when operating in carrier aggregation. The carrier may be identified or known by UE 502 as affecting the performance of the sensor / interface. For example, when a camera is being used at UE 502, UE 502 may drop the mmW carrier that causes radiated interference to the MIPIPHY line. When the camera is being used, the UE may use a different carrier, such as a sub-6 carrier, an LTE carrier, and / or an alternative mmW carrier whose beam does not cause radiated interference to the MIPIPHY line, etc. Therefore, adjusting the carrier at 512 may further include selecting a new carrier. When the sensor / interface is no longer being used, the UE may send an additional notification to the network. This notification may inform the network that there are additional RATs, beams, or carriers available for communication with the UE.

[0075] UE 502 may provide an indication 513 to the base station about carriers configured for UE 502 that cause internal interference to a sensor or interface of UE 502. As an example, UE 502 may send the indication in a UE assistance information message, an inter-device coexistence message, etc. The indication 513 from UE 502 may indicate that UE 502 seeks assistance from the network to assist in resolving the internal interference issue. The network (e.g., base station 504) may respond by adjusting the carrier configuration of UE 502 to change from the indicated mmW carrier, changing the configured state of the indicated mmW carrier, or reducing UL grants for the indicated mmW carrier. Figure 5 The base station 504 is illustrated sending an adjusted configuration 515 and an adjusted uplink grant 517 in response to an indication 513 from the UE 502. For example, the network may respond by not providing any additional uplink grants for the indicated mmW carrier, thereby silencing transmissions that may affect the sensor / carrier. The network may respond by providing a grant for discontinuous transmissions for the UE 502. The UE may send a notification to the network when the sensor / interface is no longer being used. The network may adjust the configured state of the carrier, may stop silencing transmissions for the carrier, or may send a grant for transmissions that are not discontinuous in response to a notification from the UE that the sensor / interface is no longer being used.

[0076] As another example, rather than adjusting / dropping a carrier, the UE 502 may send an indication to the base station (e.g., in UE assistance information, or an inter-device coexistence (IDC) message) that may indicate a particular carrier. The base station may respond by changing the carrier to a particular state or by refraining from providing uplink grants for the carrier, thereby muting the effect that transmissions on the particular carrier would otherwise have on the camera at the UE 502. The UE 502 may notify the base station when a carrier is available.

[0077] UE 502 may transmit communications 519 to base station 504 based on the adjustments applied at any of 505 , 507 , 509 , 510 , 511 , 512 , 515 , and / or 517 .

[0078] Figure 6 600 is a flow chart of a wireless communication method. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 502, 1050; device 702 / 702'; processing system 814, which may include memory 360 and may be the entire UE 350 or a component of the UE 350 (such as TX processor 368, RX processor 356 and / or controller / processor 359)). The method may help improve the operation of the UE by making adjustments based on internal interference caused by sensors and / or interfaces of the UE.

[0079] As illustrated at 601, the UE may perform a characterization process for a sensor or interface to identify beams or transmit power levels that have an impact on the sensor or interface of the UE. The UE may turn on the sensor or interface and perform a beam sweeping procedure for a set of beams that may be used by the UE for communication. The UE may perform beam sweeping using different transmit power levels. The UE may measure the impact on the performance of the sensor or interface and may identify one or more beams and / or transmit power levels that have an impact on the sensor or interface. The UE may use a threshold for the impact and may identify a beam and / or transmit power level that has a threshold impact on the performance of the sensor or interface. The UE may then exclude selection of one or more beams when the sensor or interface is being used (e.g., in response to determining use of the sensor or interface), or may limit the transmit power to less than the transmit power level.

[0080] At 602, the UE determines whether a particular sensor or interface is being used at the UE. If the UE does not determine that a sensor / interface is being used, then at 604, the UE may continue to operate normally without applying adjustments or restrictions. The sensor may include a camera, such as in conjunction with a Figure 4A The interface may include MIPI lines that carry camera data from the camera sensor to the ISP, such as in conjunction with Figure 4AIn other examples, the sensor may include a thermal sensor. The determination may be performed, for example, by a determination component 708 of the device 702.

[0081] In response to determining the use of the sensor or interface, the UE adjusts at least one of beam selection, transmit power, operation mode, or performance of carrier aggregation for the UE. The adjustment can be performed, for example, by the adjustment component 710 of the device 702.

[0082] For example, at 608, the UE may adjust beam selection by limiting the candidate beam list to avoid beams indicated in the codebook as having an impact on the sensor or interface in response to determining the use of the sensor or interface. The adjustment may be performed, for example, by the beam selection component 718 of the device 702. As illustrated at 616, the UE may select a beam based on the CBL. The CBL may have pruned entries based on a field indicating whether the entry causes an impact (e.g., internal interference) on the sensor or interface that has been determined to be in use. The codebook may include a field for one or more beams indicating whether one or more beams in the codebook have an impact on the sensor or interface. In response to determining at 602 that the sensor or interface is not in use, the UE, for example, at 604, does not limit the candidate beam list to avoid beams indicated in the codebook as having an impact on the sensor or interface. Therefore, the UE utilizes a candidate beam list that does include beams indicated in the codebook as having an impact on the sensor or interface.

[0083] The codebook may include a field for one or more beams, which indicates, for one or more beams in the codebook, a power level at which the corresponding beam has an effect on the sensor or interface. As illustrated at 606, the UE may determine the current transmit power of the UE and may limit the CBL based on the current transmit power. The determination of the transmit power may be performed, for example, by a transmit power component 722 of the device 702. For example, a codebook entry may indicate the power that causes the effect on the sensor / interface. In the case where the current transmit power is equal to or higher than the power level indicated for the codebook entry, the codebook entry may be pruned from the CBL. In the case where the current transmit power is lower than the indicated power level, the entry may be included in the CBL. As illustrated by the dotted line between 608 and 610, the UE may perform an adjustment to the beam selection at 608 and perform an adjustment to the transmit power at 610.

[0084] In examples where the sensor includes a camera or the interface includes a MIPI line that carries camera data to the ISP, the impact on the sensor or interface may include image degradation for the camera of the UE. The image degradation may be caused by radiated interference from at least one antenna element of the UE interfering with the MIPI line that carries camera data from the camera sensor to the ISP.

[0085] As illustrated at 618, the UE may adjust beam selection in response to determining the use of the sensor or interface by avoiding selecting a beam associated with at least one of the antenna elements, antenna panels, or beams identified as having an impact on the sensor or interface. At 618, the UE may select a beam in a manner that avoids a beam associated with at least one of the antenna elements, antenna panels, or beams identified as having an impact on the sensor or interface. The UE may select a replacement beam for the current beam, wherein the replacement beam is selected from a beam set that does not include a beam associated with at least one of the antenna elements, antenna panels, or beams identified as having an impact on the sensor or interface. As illustrated at 620, the UE adjusts beam selection in response to determining the use of the sensor or interface by switching to a wider beam or a parent beam of the current beam.

[0086] As illustrated at 610, the UE may adjust the transmit power of the UE based on determining (at 602) the use of a sensor or interface. The transmit power may be adjusted, for example, by a power component 702 of a device 712. The UE may adjust the transmit power when the sensor or interface is used and when a beam having an impact on the sensor or interface is selected. The maximum transmit power or maximum effective isotropic radiated power of the UE may be limited below a level at which the beam causes an impact on the sensor or interface.

[0087] As illustrated at 612, the UE may adjust an operating mode of the UE in response to determining the use of the sensor or interface. The operating mode may be adjusted, for example, by a mode component 714 of the device 702. For example, the UE may change from operating based on one RAT to operating based on a different RAT, as illustrated at 622. The first RAT may use beams, while the second RAT may communicate without using beamforming. As an example, the UE may switch from using mmW communications to using a sub-6 RAT, an LTE RAT, etc.

[0088] As illustrated at 614, the UE may adjust the execution of carrier aggregation in response to determining the use of the sensor or interface by adjusting the communication on the carrier identified as having an impact on the sensor or interface. The adjustment of the carrier aggregation may be performed, for example, by the carrier aggregation component 716 of the device 702. For example, at 624, the UE may discard the carrier identified as having an impact on the sensor or interface. The UE may discard the carrier in an autonomous manner. The UE may adjust or reduce the communication used for the carrier. At 626, the UE may select a replacement carrier for carrier aggregation. The replacement carrier may be based on a different RAT than the carrier identified as having an impact on the sensor or interface. The carrier may include a different mmW carrier that does not cause internal interference to the sensor / interface being used. As illustrated at 628, the UE may send an indication to the base station that the carrier used by the UE for carrier aggregation has an impact on the sensor or interface of the UE. The indication may be sent in at least one of a UE assistance information message or an inter-device coexistence message. At 630, the UE may receive an adjusted configuration for the carrier or a reduced uplink grant for the carrier in response to the indication sent to the base station. The adjusted configuration may include a configuration for a different carrier. The reduced uplink grant may not include an additional grant for the indicated carrier. The reduced uplink grant may include a grant for discontinuous transmission on the indicated carrier.

[0089] As illustrated at 632, the UE may transmit a communication to the base station based on the adjustment applied in conjunction with any of 608, 610, 612, and / or 614. The communication may be transmitted by the transmitting component 706 of the device 702, for example.

[0090] Figure 7700 is a conceptual data flow diagram illustrating the data flow between different devices / components in an example device 702. The device 702 can be a UE or a component of a UE. The device 702 includes a receiving component 704, which is configured to receive downlink communications from a base station 750. The device 702 includes a transmitting component 706, which is configured to transmit uplink communications to the base station 750. The device 702 may include a determining component 708, which is configured to determine the use of a sensor or interface of the UE, for example, the use of a sensor / interface component 720. The device 702 may include an adjusting component 710, which is configured to adjust at least one of beam selection, transmit power, operation mode, or carrier aggregation for the UE in response to determining the use of the sensor or interface. The adjusting component 710 may include a beam selection component 718, which is configured to adjust the beam selection in response to determining the use of the sensor or interface. The beam selection component 718 may limit the candidate beam list to avoid beams indicated in the codebook as having an impact on the sensor or interface. The beam selection component 718 may avoid selecting a beam associated with at least one of an antenna element, an antenna panel, or a beam that is identified as having an impact on a sensor or an interface. The beam selection component 718 may select a replacement beam for the current beam, wherein the replacement beam is selected from a beam set that does not include a beam associated with at least one of an antenna element, an antenna panel, or a beam that is identified as having an impact on a sensor or an interface. The beam selection component 718 may switch to a wider beam or a parent beam of the current beam. The adjustment component 710 may include a power component 712 configured to adjust the transmit power of the UE based on determining the use of the sensor or interface. The adjustment component 710 may include a mode component 714 configured to adjust the operating mode of the UE by changing from an operation based on a radio access technology (RAT) using a beam to an operation based on a different RAT in response to determining the use of the sensor or interface. The device may include a transmit power component 722 configured to determine the current transmit power of the UE. Adjusting component 710 may include a carrier aggregation component 716 configured to adjust performance of carrier aggregation by adjusting communications on carriers identified as having an impact on the sensor or interface in response to determining usage of the sensor or interface. Carrier aggregation component 716 may select an alternative carrier for carrier aggregation, e.g., via transmitting component 706. Carrier aggregation component 716 may send an indication to a base station indicating that a carrier used by the UE for carrier aggregation has an impact on the sensor or interface of the UE, and may receive, e.g., via receiving component 704, an adjusted configuration for the carrier or a reduced uplink grant for the carrier in response to the indication sent to the base station.

[0091] The apparatus may include executing Figure 5 and 6 The additional components of the blocks of the algorithm in the preceding flowchart. Thus, Figure 5 and 6The blocks in the aforementioned flow charts may be performed by components, and the device may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0092] Figure 8 800 is a diagram illustrating an example of a hardware implementation of a device 702' employing a processing system 814. The processing system 814 may be implemented with a bus architecture generally represented by a bus 824. Depending on the specific application of the processing system 814 and the overall design constraints, the bus 824 may include any number of interconnecting buses and bridges. The bus 824 links together various circuits, including one or more processors and / or hardware components (represented by the processor 804, components 704, 706, 708, 710, 712, 714, 716, 718, 720, 722, and computer readable medium / memory 806). The bus 824 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0093] The processing system 814 may be coupled to the transceiver 810. The transceiver 810 is coupled to one or more antennas 820. The transceiver 810 provides a means for communicating with various other devices via a transmission medium. The transceiver 810 receives signals from the one or more antennas 820, extracts information from the received signals, and provides the extracted information to the processing system 814 (specifically, the receiving component 704). In addition, the transceiver 810 receives information from the processing system 814 (specifically, the transmitting component 706) and generates signals to be applied to the one or more antennas 820 based on the received information. The processing system 814 includes a processor 804 coupled to a computer-readable medium / memory 806. The processor 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 806. The software, when executed by the processor 804, causes the processing system 814 to perform the various functions described above for any particular device. The computer-readable medium / memory 806 may also be used to store data manipulated by the processor 804 when executing the software. The processing system 814 further includes at least one of the components 704, 706, 708, 710, 712, 714, 716, 718, 720, 722. These components may be software components running in the processor 804, software components resident / stored in the computer-readable medium / memory 806, one or more hardware components coupled to the processor 804, or some combination thereof. The processing system 814 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 814 may be the entire UE (e.g., see Figure 3 of 350).

[0094] In one configuration, the device 702 / 702' for wireless communication includes a device for determining the use of a sensor or interface of a UE. The device may include a device for adjusting at least one of the beam selection, transmit power, operation mode, or carrier aggregation execution for the UE in response to determining the use of the sensor or interface. The device may include a device for adjusting the beam selection in response to determining the use of the sensor or interface. The device for adjusting the beam selection may limit the candidate beam list to avoid beams indicated in the codebook as having an impact on the sensor or interface. The device for adjusting the beam selection may avoid selecting a beam associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or interface. The device for adjusting the beam selection may select a replacement beam for the current beam, wherein the replacement beam is selected from a beam set that does not include a beam associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or interface. The device for adjusting the beam selection may switch to a wider beam or a parent beam of the current beam. The device may include a device for determining the current transmit power of the UE. The apparatus may include means for adjusting the transmit power of the UE based on determining the use of a sensor or interface. The apparatus may include means for adjusting the operating mode of the UE by changing from an operation based on a radio access technology (RAT) using a beam to an operation based on a different RAT in response to determining the use of the sensor or interface. The apparatus may include means for adjusting the execution of carrier aggregation by adjusting the communication on a carrier identified as having an impact on the sensor or interface in response to determining the use of the sensor or interface. The means for adjusting the execution of carrier aggregation may select an alternative carrier for carrier aggregation. The means for adjusting the execution of carrier aggregation may send an indication to a base station indicating that the carrier used by the UE for carrier aggregation has an impact on the sensor or interface of the UE, and may receive an adjusted configuration for the carrier or a reduced uplink grant for the carrier in response to the indication sent to the base station. The aforementioned means may be one or more of the aforementioned components of the apparatus 702 and / or the processing system 814 of the apparatus 702' configured to perform the functions recited by the aforementioned means. As described above, the processing system 814 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0095] Fig. 9900 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 504, 750; device 1002 / 1002'; processing system 1114, which may include memory 376 and may be the entire base station 310 or a component of the base station 310 (such as TX processor 316, RX processor 370 and / or controller / processor 375)). The method may help improve the operation of a UE by adjusting the configuration / grant for carrier aggregation based on internal interference experienced at the UE.

[0096] At 902, the base station configures the UE for carrier aggregation.For example, the carrier aggregation component 1008 of the device 1002 can configure the UE 1050 for carrier aggregation.

[0097] At 904, the base station receives an indication from the UE that the carrier configured for the UE has an impact on the performance of a sensor or interface of the UE. The indication may be received from the UE in a UE assistance information message. The indication may be received from the UE in an inter-device coexistence message. Figure 4B As described, one of the carriers configured for the UE may cause a certain degree of internal interference at the UE. For example, the sensor may include a camera. Using the camera for communication may cause the camera's image to be degraded. In another example, the interface may include a MIPI line, for example, to carry camera data from a camera sensor to an ISP. The indication may be received, for example, by an indication component 1004 of the device 1002 via a receiving component 1004.

[0098] At 906, the base station may adjust the configuration of the carrier in response to receiving the indication from the UE. For example, the base station may change the configured state of the carrier in response to receiving the indication from the UE. For example, the adjustment component 1012 of the device 1002 may perform an adjustment to the configuration of the carrier, or set the carrier (e.g., a secondary carrier, SCell) to a deactivated state.

[0099] Alternatively or additionally, at 908, the base station may adjust the uplink grant(s) for the carrier in response to receiving the indication from the UE. For example, the base station may reduce the uplink grant for the carrier in response to receiving the indication from the UE. For example, uplink grant component 1014 of device 1002 may perform the adjustment of the uplink grant(s) for the carrier.

[0100] Fig.101000 is a conceptual data flow diagram illustrating data flow between different devices / components in an example device 1002. The device can be a base station or a component of a base station. The device 1002 can include a receiving component 1004 configured to receive uplink transmissions from a UE 1050. The device 1002 can include a transmitting component 1006 configured to transmit downlink communications to the UE 1050. The device 1002 can include configuring the UE 1050 for carrier aggregation (e.g., as in conjunction with Fig. 9 The device 1002 may include an indication component 1010 configured to receive an indication from the UE 1050 that the carrier configured for the UE 1050 has an impact on the performance of the sensor or interface of the UE 1050, for example, as described in conjunction with Fig. 9 The device may include an adjustment component 1012, which is configured to adjust the configuration of the carrier in response to receiving the indication from the UE 1050, for example, as combined with Fig. 9 The device may include an uplink grant component 1014, which is configured to adjust the uplink grant (s) for the carrier in response to receiving the indication from the UE 1050, for example, as combined with Fig. 9 As described in 908.

[0101] Device 1002 may include executing Figure 5 and 9 The additional components of the blocks of the algorithm in the preceding flowchart. Thus, Figure 5 and 9 The blocks in the aforementioned flow charts may be performed by components, and the device 1002 may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0102] Fig.111 is a diagram 1100 illustrating an example of a hardware implementation of a device 1002' employing a processing system 1114. Device 1002' may correspond to device 1002. Processing system 1114 may be implemented with a bus architecture generally represented by bus 1124. Bus 1124 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of processing system 1114. Bus 1124 links various circuits together, including one or more processors and / or hardware components (represented by processor 1104, components 1004, 1006, 1008, 1010, 1012, 1014, and computer readable medium / memory 1106). Bus 1124 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0103] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other devices over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, the transmitting component 1006) and generates signals to be applied to the one or more antennas 1120 based on the received information. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described above for any particular device. The computer-readable medium / memory 1106 may also be used to store data manipulated by the processor 1104 when executing software. The processing system 1114 further includes at least one of the components 1004, 1006, 1008, 1010, 1012, 1014. These components may be software components running in the processor 1104, software components resident / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 may be a component of the base station 310 and may include the memory 376 and / or at least one of the following: the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1114 may be the entire base station (e.g., see Figure 3 310).

[0104] In one configuration, a device 1002 / 1002' for wireless communication includes a device for configuring a UE for carrier aggregation. The device 1002 / 1002' may include a device for receiving an indication from the UE that a carrier configured for the UE has an impact (e.g., causing internal interference to the performance of a sensor or interface of the UE). The device 1002 / 1002' may include a device for adjusting the configuration of the carrier or adjusting the uplink grants for the carrier in response to receiving the indication from the UE. The device for adjusting may reduce the uplink grants for the carrier in response to receiving the indication. The aforementioned device may be one or more of the aforementioned components of the device 1002 and / or the processing system 1114 of the device 1002' configured to perform the functions described by the aforementioned device. As described above, the processing system 1114 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0105] The following examples are merely illustrative, and aspects thereof may be combined with aspects of other embodiments or teachings described herein without limitation. Below, an overview of further examples of the present disclosure is provided:

[0106] Example 1 is a method for wireless communication at a user equipment (UE), comprising: determining the use of a sensor or interface of the UE; and adjusting at least one of beam selection, transmit power, operating mode, or carrier aggregation execution for the UE in response to determining the use of the sensor or interface.

[0107] In Example 2, the method of Example 1 further includes that the sensor includes a camera.

[0108] In Example 3, the method of Example 1 or Example 2 further includes that the interface includes a Mobile Industry Processor Interface (MIPI) line that carries camera data from the camera sensor to an image signal processor (ISP).

[0109] In Example 4, the method of any one of the preceding examples further includes, in response to determining the use of a sensor or interface, the UE adjusts the beam selection by utilizing a candidate beam list, wherein the candidate beam list does not include beams indicated in the codebook as having an impact on the sensor or interface, and the method further includes: selecting a beam based on the candidate beam list.

[0110] In Example 5, the method of Example 4 further includes determining a current transmit power of the UE, wherein the candidate beam list is limited based on the current transmit power.

[0111] In Example 6, the method of any one of the preceding examples further includes that the impact on the sensor or interface includes image degradation for a camera of the UE.

[0112] In Example 7, the method of Example 6 further includes that the image degradation is caused by radiated interference from at least one antenna element of the UE, which interferes with a Mobile Industry Processor Interface (MIPI) line that carries camera data from a camera sensor to an image signal processor (ISP).

[0113] In Example 8, the method of Example 4 further includes the codebook comprising a field for one or more beams, the field indicating whether the one or more beams in the codebook have an impact on the sensor or the interface.

[0114] In Example 9, the method of Example 4 further includes the codebook comprising a field for one or more beams, the field indicating, for the one or more beams in the codebook, a power level at which the corresponding beam has an impact on the sensor or the interface.

[0115] In Example 10, the method of Example 4 further includes, in response to determining that the sensor or the interface is not in use, the UE utilizing a candidate beam list including beams indicated in the codebook as having an impact on the sensor or the interface.

[0116] In Example 11, the method of any one of the preceding examples further includes, in response to determining the use of a sensor or interface, the UE adjusts the beam selection by excluding from selection a beam associated with at least one of the antenna elements, antenna panels, or beams identified as having an impact on the sensor or interface, the method further including: selecting a beam by excluding from selection a beam associated with at least one of the antenna elements, antenna panels, or beams identified as having an impact on the sensor or interface.

[0117] In Example 12, the method of Example 11 further includes that selecting the beam includes selecting a replacement beam for the current beam, wherein the replacement beam is selected from a beam set that does not include a beam associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or the interface.

[0118] In Example 13, the method of any of the preceding examples, further comprises the UE adjusting a transmit power of the UE based on determining usage of the sensor or interface.

[0119] In Example 14, the method of Example 13 further includes, the UE adjusting the transmit power when a sensor or an interface is used and a beam having an impact on the sensor or the interface is selected.

[0120] In Example 15, the method of Example 14, further includes that a maximum transmit power or a maximum effective isotropically radiated power of the UE is limited to a level below a level at which a beam causes an impact on a sensor or an interface.

[0121] In Example 16, the method of any of the preceding examples, further comprising the UE adjusting the beam selection by switching to a wider beam or a parent beam of the current beam in response to determining the use of the sensor or interface.

[0122] In Example 17, the method of any of the preceding examples, further includes the UE adjusting an operating mode of the UE by changing from operation based on a radio access technology (RAT) using a beam to operation based on a different RAT in response to determining usage of the sensor or interface.

[0123] In Example 18, the method of any of the preceding examples, further comprises the UE adjusting performance of carrier aggregation by adjusting communications on carriers identified as having an impact on the sensor or interface in response to determining usage of the sensor or interface.

[0124] In Example 19, the method of any of the preceding examples, further comprising the UE adjusting performance of carrier aggregation by dropping carriers identified as having an impact on the sensor or interface in response to determining usage of the sensor or interface.

[0125] In Example 20, the method of Example 19, further comprises selecting a replacement carrier for carrier aggregation.

[0126] In Example 21, the method of Example 20, further comprising the replacement carrier being based on a different radio access technology (RAT) than the carrier identified as having an impact on the sensor or the interface.

[0127] In Example 22, the method of any of the preceding examples, further includes, in response to determining usage of the sensor or interface, the UE adjusting execution of the carrier aggregation by sending an indication to the base station indicating that the carrier used by the UE for carrier aggregation has an impact on the sensor or interface of the UE.

[0128] In Example 23, the method of Example 22, further includes sending the indication in at least one of a UE assistance information message or an inter-device coexistence message.

[0129] In Example 24, the method of Example 22, further comprises receiving an adjusted configuration for the carrier or a reduced uplink grant for the carrier in response to the indication sent to the base station.

[0130] In Example 25, the method of any of Examples 1-24 further includes performing a characterization process for a sensor or interface, comprising: turning on the sensor or interface; performing a beam sweeping procedure; and identifying one or more beams or transmit power levels that have a threshold effect on the sensor or interface, wherein the UE excludes selection of the one or more beams or limits the transmit power to below the transmit power level in response to determining usage of the sensor or interface of the UE.

[0131] Example 26 includes a system or apparatus for wireless communication at a user equipment (UE), comprising: means for performing the steps of the method of any one of Examples 1-25. As an option, the apparatus may include a memory and at least one processor coupled to the memory.

[0132] Example 27 includes an apparatus for wireless communication at a user equipment (UE), comprising one or more memories; and at least one processor coupled to the memories and configured to perform the steps of the method of any of Examples 1-25.

[0133] Example 28 is a non-transitory computer-readable medium storing computer-executable code for wireless communication at a user equipment (UE), which code, when executed by one or more processors, causes the one or more processors to perform the method of any one of Examples 1-25.

[0134] Example 29 is a method for performing wireless communications at a base station, comprising: configuring a user equipment (UE) for carrier aggregation; receiving an indication from the UE that a carrier configured for the UE has an impact on performance of a sensor or interface of the UE; and adjusting the configuration of the carrier or adjusting an uplink grant for the carrier in response to receiving the indication from the UE.

[0135] In Example 30, the method of Example 29 further includes that the sensor includes a camera.

[0136] In Example 31, the method of Example 29 or Example 30 further includes that the interface includes a Mobile Industry Processor Interface (MIPI) line that carries camera data from the camera sensor to an image signal processor (ISP).

[0137] In Example 32, the method of any one of Examples 29-31, further comprising, the indication being received in at least one of a UE assistance information message or an inter-device coexistence message.

[0138] In Example 33, the method of any one of Examples 29-32 further includes the base station changing the configured state of the carrier in response to receiving the indication from the UE.

[0139] In Example 34, the method of any one of Examples 29-33 further includes the base station reducing uplink grants for the carrier in response to receiving the indication from the UE.

[0140] Example 35 is a system or apparatus for wireless communication at a base station, comprising: means for performing the steps of the method of any one of Examples 29-34. As an option, the apparatus may include a memory and at least one processor coupled to the memory.

[0141] Example 36 is a device or apparatus for wireless communication at a base station, comprising: one or more memories; and at least one processor coupled to the memory and configured to perform the steps of the method of any one of Examples 29-34.

[0142] Example 37 is a non-transitory computer-readable medium storing computer-executable code for wireless communication at a base station, which code, when executed by one or more processors, causes the one or more processors to perform the method of any of Examples 29-34.

[0143] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0144] The previous 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 easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used in this article to represent "used as an example, instance, or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" 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 "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. 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 "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

Claims

1. A method of wireless communication at a user equipment (UE), include: determining usage of a sensor or an interface of the UE; as well as In response to determining usage of the sensor or the interface, adjusting beam selection for the UE, wherein the UE adjusts the beam selection by utilizing a candidate beam list in response to determining usage of the sensor or the interface, the candidate beam list not including beams indicated in a codebook as having an impact on the sensor or the interface; as well as A beam is selected based on the candidate beam list. The method of claim 1 , wherein the sensor comprises a camera.

3. The method of claim 1, wherein the interface comprises a Mobile Industry Processor Interface (MIPI) line that carries camera data from a camera sensor to an Image Signal Processor (ISP).

4. The method of claim 1, further comprising: include: A current transmit power of the UE is determined, wherein the candidate beam list is restricted based on the current transmit power.

5. The method of claim 1, wherein the impact on the sensor or the interface comprises image degradation for a camera of the UE.

6. The method of claim 5, wherein the image degradation is caused by radiated interference from at least one antenna element of the UE, the radiated interference interfering with a Mobile Industry Processor Interface (MIPI) line that carries camera data from a camera sensor to an Image Signal Processor (ISP).

7. The method of claim 1, wherein the codebook includes a field for one or more beams, the field indicating whether the one or more beams in the codebook have an impact on the sensor or the interface.

8. The method of claim 1, wherein the codebook comprises a field for one or more beams, the field indicating, for the one or more beams in the codebook, a power level at which the corresponding beam has an impact on the sensor or the interface.

9. The method of claim 1, wherein in response to determining that the sensor or the interface is not in use, the UE utilizes a candidate beam list including beams indicated in the codebook as having an impact on the sensor or the interface.

10. The method of claim 1, wherein the UE adjusts the beam selection in response to determining the use of the sensor or the interface by excluding from selection a beam associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or the interface, the method further include: The beam is selected by excluding from selection beams associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or the interface.

11. The method of claim 10, wherein the beam is selected include: A replacement beam for a current beam is selected, wherein the replacement beam is selected from a set of beams that does not include a beam associated with at least one of an antenna element, an antenna panel, or a beam identified as having an impact on the sensor or the interface.

12. The method of claim 1, wherein the UE adjusts the beam selection by switching to a wider beam or a parent beam of a current beam in response to determining usage of the sensor or the interface.

13. The method of claim 1, further comprising performing a characterization process for the sensor or the interface, wherein include: Turning on the sensor or the interface; executing beam sweeping procedures; as well as identifying one or more beams or transmit power levels having a threshold impact on the sensor or the interface, Wherein the UE excludes selection of the one or more beams or limits transmit power to below the transmit power level in response to determining usage of the sensor or the interface of the UE.

14. An apparatus for wireless communication at a user equipment (UE), include: Memory; as well as at least one processor coupled to the memory and configured to: determining usage of a sensor or an interface of the UE; as well as adjusting beam selection for the UE in response to determining usage of the sensor or the interface, wherein the UE adjusts the beam selection by utilizing a candidate beam list in response to determining usage of the sensor or the interface, the candidate beam list not including beams indicated in a codebook as having an impact on the sensor or the interface; as well as A beam is selected based on the candidate beam list.

Images