Patent Application
20230035400
Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for wireless networks. These TSs describe aspects related to mobility and power control for operation within such networks.
The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, and techniques in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B).
The following is a glossary of terms that may be used in this disclosure.
The term “circuitry” as used herein refers to, is part of, or includes hardware components that are configured to provide the described functionality. The hardware components may include an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an application-specific integrated circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), or a digital signal processor (DSP). In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer to an application processor, baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.
The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, and network interface cards.
The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities that may allow a user to access network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, or workload units. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware elements. A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio-frequency carrier,” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.
The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, or a virtualized network function.
The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.
For descriptions of embodiments herein, the access node 108 may provide a serving cell with which the UE 104 is initially communicatively coupled and the access node 112 may provide a target cell. The UE 104 and access nodes 108/112 may cooperate to handover the communication session of the UE 104 from the serving cell to the target cell.
In some embodiments, the access node 112 may be a neighbor base station that provides coverage for an adjacent geographical location. In this embodiment, the access node 112 may provide a neighbor cell that operates independently and distinctly from the serving cell.
In some embodiments, the access node 108 may be one of a plurality of access nodes that provides service to the UE 104 through a dual connectivity (DC) operation. The access nodes may be coupled with each other via an X2 interface over an ideal or non-ideal backhaul. The access nodes may include a master node (MN) to provide a control plane connection to a core network. The MN may be associated with the group of serving cells referred to as a master cell group (MCG). The access nodes may further include a secondary node (SN) that may not have a control plane connection to the core network. The SN may be used to provide additional resources to the UE 104. The SN may be associated with a group of serving cells referred to as a secondary cell group (SCG). In these embodiments, the access node 108 may represent a first SN that provides a primary cell of the SCG (PSCell) and the access node 112 may represent a second SN. The handover may then involve the UE 104 transitioning the PSCell from the first SN to the second SN.
In some embodiments, the network may utilize a conditional handover (CHO) or conditional PSCell change (CPC) to improve mobility robustness and reliability. This may involve the access node 108 configuring the UE 104 with handover assistance information with respect to one or more candidate cells, and providing the one or more candidate cells with information about the UE 104. The UE 104 may then monitor link qualities for various handover conditions and, if detected, perform a handover to a target cell selected from the candidate cells without requiring a handover command from the access node 108. The serving cell may not be notified when the execution conditions are met and the UE 104 may directly execute the handover toward the target cell.
The Federal Communications Commission (FCC) and other regulatory bodies define limits on human body exposure to electromagnetic fields (EMF) in wireless communication systems. In NR frequency range 2 (FR2), which corresponds to frequency ranges 24,250 MHz-52,600 MHz, maximum permitted exposure (MPE) is defined as an averaged power measured over surface area in free space. The MPE is measured in units of milliwatts per square centimeter (mW/cm2) within a period of time (one second per FCC).
3GPP TSs indicates that if the transmit power in an uplink reaches the MPE limit, the UE is to reduce its transmit power. This may be done by directly reducing a power level used in the uplink transmissions, or reducing a duty cycle to reduce an average uplink transmit power. The UE 104 may directly reduce its power level by a power management maximum power reduction (P-MPR) value and may inform the network that the power level was reduced. To reduce the duty cycle, the network may adjust the uplink scheduling in order to reduce the average transmit power over a given time unit.
When operating in the higher frequency ranges, for example, FR2 and above, the UE 104 may engage in beamforming by focusing the transmit beams in a direction toward a receiving access node. To ensure the selected direction (and power) of the uplink transmit beam is suitable and complies with the MPE regulations, the UE 104 may perform a body proximity sensing (BPS) operation to detect the presence of a nearby body. A BPS operation may include transmitting a low-power sensing signal and using a receiver of the UE 104 to measure reflections of the sensing signal to determine human body proximity. If the UE 104 detects body 116 in the direction of the access node 108 that is providing the serving cell, the UE 104 may need to reduce its uplink transmit power based on MPE limits. This may compromise the quality of the uplink transmissions.
Embodiments of the present disclosure describe leveraging the pre-configuration performed for the CHO/CPC in order to handover to a target cell in the event the uplink transmit power of the UE 104 is reduced due to BPS/MPE. In some embodiments, the handover to the target cell may occur even though the handover conditions related to CHO/CPC are not met.
The UE 104 may perform measurements based on the measurement configurations in the measurement control 204 and provide results of the measurements to the access node 108 in one or more measurement reports 208.
Based on the measurement reports 208, the access node 108 may select one or more candidate access nodes (including access node 112) for potentially receiving a handover. The access node 108 may transmit/receive various handover (HO) preparation messages with the candidate access nodes. The HO preparation messages 212 may include a message transmitted from the access node 108 to the access node 112 that includes a context of the UE 104. The context may include UE state information, security information, UE capability information, and identity of a UE-associated logical connection over an Si interface between the UE 104 and the access node 108.
The signaling diagram 200 may further include the access node 108 transmitting HO assistance information 216 to the UE 104. The HO assistance information may be transmitted in a radio resource control (RRC) message such as an RRC reconfiguration message. The HO assistance information may be configuration information corresponding to the one or more candidate cells selected by the access node. This may include identities or frequencies of the one or more candidate cells. The HO assistance information may further include execution conditions generated by the access node 108. The execution conditions may define the circumstances in which the UE 104 may perform the CHO/CPC.
The execution conditions may include A3 or A5 events. An A3 event may refer to the serving cell being a number of decibels (dB) worse than a target cell. An A5 event may refer to the serving cell being worse than a first threshold and the target cell being better than a second threshold. The signal metrics for measuring the serving/target cell may be one or more of reference signal receive power (RSRP), reference signal receive quality (RSRQ), or signal-to-interference-and-noise ratio (SINR). The thresholds/number of decibels may be configured by the HO assistance information 216, another configuration message, or predefined by a 3GPP TS.
At 220, the UE 104 may detect an MPE/BPS event. For example, the UE 104 may determine that an uplink transmit power exceeds the MPE limit or the UE 104 may sense a body in proximity of the UE 104. This may result in the UE 104 needing to reduce its uplink transmit power.
Based on the detection of the MPE/BPS event at 220, the UE 104 may proceed to connect to the target cell at 224. To do so, the UE 104 detaches from the access node 104, applies the stored corresponding configuration for the target cell, synchronizes to the target cell, and completes the RRC handover procedure by sending an RRC Reconfiguration Complete message to the access node 112. The UE 104 may release stored CHO configurations after successful completion of RRC handover procedure.
The connection to the target cell at 224 may be done even though the execution conditions for CHO/CPC (for example, A3/A5) are not met. Thus, based on the detected MPE/BPS event at 220, the UE 104 may perform an early CHO/CPC. An “early CHO/CPC,” as used herein, may refer to performing a handover/PSCell change even though the configured execution conditions for CHO/CPC are not satisfied. The early CHO/CPC may be based on MPE/BPS.
In some embodiments, a number of early execution conditions may be configured for early CHO/CPC. The early execution conditions may be based on signaling conditions in the serving or target cell. For example, the UE 104 may perform the early CHO/CPC in the event a ratio between the reduced uplink transmit power to the serving cell (due to MPE limits) and an available uplink transmit power to the target cell is less than a predetermined threshold; the reduced uplink transmit power to the serving cell is less than an available uplink transmit power to the target cell by a predetermined threshold; or the reduced uplink transmit power is less than a first predetermined threshold and the available uplink transmit power to the target cell is greater than a second threshold. While the above early execution conditions refer to uplink transmit powers to the serving/target cells, similar conditions may be based on other factors that may be impacted by a reduced uplink transmit power including, for example, uplink throughput or downlink throughput.
In some embodiments, the UE 104 may inform the serving cell or the target cell that the reason for early CHO/CPC is due to MPE mitigation or BPS. The target cell may be informed of the reason for early CHO/CPC by adding an indication in an IE of the RRC reconfiguration complete message. Additionally or alternatively, the serving cell may be informed of the reason for early CHO/CPC by the MPE media access control (MAC)-control element (CE) signal transmitted by the UE 104 with the indication.
The operation flow/algorithmic structure 300 may include, at 304, receiving configuration information for one or more candidate cells. The configuration information may be received in an RRC message such as an RRC reconfiguration message. In some embodiments, the configuration information may include cell identifiers of the candidate cells that are to be considered for a CHO/CPC. The candidate cells may have been identified by a serving cell based on measurements performed by the UE on neighbor cells consistent with the measurement configurations
The operation flow/algorithmic structure 300 may further include, at 308, identifying execution conditions for CHO/CPC. In some embodiments, the execution conditions may be A3 or A5 events. In some embodiments, the thresholds corresponding to the execution conditions may be included in the RRC message that identifies the plurality of candidate cells.
The operation flow/algorithmic structure 300 may further include, at 312, detecting a trigger to reduce uplink transmit power based on an MPE limit. The trigger may be based on an uplink transmit power exceeding the MPE limit. In some embodiments, an MPE limit may be set based on an assumed body proximity. In additional/alternative embodiments, one or more MPE limits may correspond to conditions in which a body is or is not detected to be proximate to the UE. For example, a first MPE limit may be defined for use when no body is detected and a second, lower, MPE limit may be defined for use when a body is detected. In some embodiments, the second MPE limit may be restricted to a direction in which the body is detected, while the first MPE limit may correspond to a direction in which a body is not detected. Thus, in some situations, the UE's detection of a body may cause the UE to reduce its uplink transmit power in order to comply with a lower MPE limit.
The operation flow/algorithmic structure 300 may further include, at 316, initiating a handover to a target cell of the candidate cells based on detecting the trigger without the execution conditions being met. The reduction of uplink transmit power required in the serving cell may compromise uplink or downlink throughput with the serving cell. However, it may be possible to associate with one of the candidate cells without having to reduce an uplink transmit power or reducing the uplink transmit power by a smaller amount than that required in the serving cell. This may be the case when the UE is capable of performing uplink beamforming and directional MPE provides a higher MPE limit in directions not towards a detected body.
The UE may identify the target cell from the list of candidate cells provided in the RRC message based on signaling conditions associated with the target cell. The signaling conditions may include available uplink transmit power, uplink transmit beam, uplink signaling quality, or downlink signal quality.
In some embodiments, the UE may initiate a handover to the identified target cell based on early CHO/CPC execution conditions. These conditions may be configured along with, or separate from, the CHO/CPC execution conditions. The early CHO/CPC execution conditions may be based on a level by which the uplink transmit power is to be reduced in the serving cell in order to comply with the MPE limit. For example, signaling conditions of the serving cell (based on the reduced uplink transmit power) may be compared with signaling conditions of the target cell. This comparison may serve as a basis for initiating the early handover.
Initiating the handover may include starting synchronization with the target cell. Once the UE starts the synchronization with the target cell, the UE may no longer monitor the source cell.
The operation flow/algorithmic structure 400 may include, at 404, receiving configuration information for one or more candidate cells. Similar to that described above, the configuration information may be received in an RRC message and may include cell identifiers of the candidate cells that are to be considered for a CHO/CPC. The candidate cells may have been identified by the serving cell based on measurements performed by the UE on neighbor cells consistent with measurement configurations.
The operation flow/algorithmic structure 400 may further include, at 408, identifying execution conditions for CHO/CPC. In some embodiments, the execution conditions may be A3 or A5 events. In some embodiments, the thresholds corresponding to the execution conditions may be included in the RRC message that identifies the candidate cells.
The operation flow/algorithmic structure 400 may further include, at 412, detecting a body proximity based on a BPS operation. The BPS operation may involve transmitting a BPS signal and monitoring for reception of the BPS signal as reflected off of a nearby body. If the reflected signal is greater than a predetermined threshold, the BPS operation may indicate that a body is in proximity to the UE.
If the UE includes more than one antenna panel or is otherwise capable of performing uplink beamforming, the UE may be capable of transmitting uplink signals in a direction away from the detected body. In some embodiments, the UE may perform a directional BPS operation in which beamformed BPS signals are transmitted during the BPS operation. This may allow the UE to determine uplink signals may be transmitted in a direction not towards the detected body.
The operation flow/algorithmic structure 400 may further include, at 416, initiating a handover to a target cell of the candidate cells based on detecting the trigger without the execution conditions of the CHO/CPC being met.
In some embodiments, the UE may identify the target cell from the list of candidate cells based on a direction of the target cell. For example, the UE may perform receive beam sweeping while measuring reference signals from the candidate cells. This may allow the UE to determine an approximate direction of the various candidate cells. The candidate cell in the direction away from the detected body may be identified as the target cell.
Detecting the target cell from the candidate cells and determining whether early CHO/CPC conditions are met may be based on signaling conditions in the serving and target cells similar to that described above with respect to
In some embodiments, upon detecting a proximate body, the UE may determine an adjusted serving cell throughput based on various available exposure mitigation techniques. For example, to mitigate exposure sufficient to comply with the MPE limit, the UE may reduce an absolute uplink transmit power, reduce an average uplink transmit power by reducing an uplink duty cycle, or change an uplink transmit beam. While these techniques may cause the UE to comply with the MPE limit, they will also likely reduce UL/DL throughput with the serving cell. In some embodiments, the reduced throughput may be compared to the predetermined threshold or to a corresponding throughput of the target cell. This comparison may serve as a basis for initiating the handover at 416.
The operation flow/algorithmic structure 500 may include, at 504, transmitting measurement configurations to a UE. The measurement configurations may configure measurements on neighbor cells with respect to the UE. These measurement configurations may include inter-frequency measurement objects (MOs), intra-frequency MOs, inter-radio access technology (RAT) MOs, or intra-RAT MOs. The measurements may be configured to be performed within or outside of measurement gaps.
The operation flow/algorithmic structure 500 may further include, at 508, identifying candidates cells for CHO/CPC. The candidate cells may be identified based on results of measurements performed and reported by the UE. The base station may provide the candidate cells with the UE context to facilitate CHO/CPC.
The operation flow/algorithmic structure 500 may further include, at 512, configuring the UE with first execution conditions for CHO/CPC and second execution conditions for early CHO/CPC. The first execution conditions may be A3/A5 conditions for a standard CHO/CPC. The second execution conditions may be based on BPS or MPE limit.
Similar to that discussed elsewhere herein, the second execution conditions may be based on signaling conditions in the serving cell (upon reduction of uplink transmit power to comply with MPE limit) and in the target cell.
The UE 600 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, or actuators), video surveillance/monitoring devices (for example, cameras or video cameras), wearable devices (for example, a smart watch), or Internet-of-things devices.
The UE 600 may include processors 604, RF interface circuitry 608, memory/storage 612, user interface 616, sensors 620, driver circuitry 622, power management integrated circuit (PMIC) 624, antenna structure 626, and battery 628. The components of the UE 600 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of
The components of the UE 600 may be coupled with various other components over one or more interconnects 632, which may represent any type of interface, input/output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
The processors 604 may include processor circuitry such as, for example, baseband processor circuitry (BB) 604A, central processor unit circuitry (CPU) 604B, and graphics processor unit circuitry (GPU) 604C. The processors 604 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 612 to cause the UE 600 to perform operations as described herein.
In some embodiments, the baseband processor circuitry 604A may access a communication protocol stack 636 in the memory/storage 612 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 604A may access the communication protocol stack to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some embodiments, the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 608.
The baseband processor circuitry 604A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
The memory/storage 612 may include one or more non-transitory, computer-readable media that include instructions (for example, communication protocol stack 636) that may be executed by one or more of the processors 604 to cause the UE 600 to perform various operations described herein. The memory/storage 612 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 600. In some embodiments, some of the memory/storage 612 may be located on the processors 604 themselves (for example, L1 and L2 cache), while other memory/storage 612 is external to the processors 604 but accessible thereto via a memory interface. The memory/storage 612 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.
The RF interface circuitry 608 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 600 to communicate with other devices over a radio access network. The RF interface circuitry 608 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.
In the receive path, the RFEM may receive a radiated signal from an air interface via antenna structure 626 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 604.
In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 626.
In various embodiments, the RF interface circuitry 608 may be configured to transmit/receive signals in a manner compatible with NR access technologies.
The antenna 626 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 626 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 626 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 626 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
The user interface circuitry 616 includes various input/output (I/O) devices designed to enable user interaction with the UE 600. The user interface 616 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.)), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 600.
The sensors 620 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other like audio capture devices.
The driver circuitry 622 may include software and hardware elements that operate to control particular devices that are embedded in the UE 600, attached to the UE 1100, or otherwise communicatively coupled with the UE 600. The driver circuitry 622 may include individual drivers allowing other components to interact with or control various input/output (I/O) devices that may be present within, or connected to, the UE 600. For example, driver circuitry 622 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensor circuitry 620 and control and allow access to sensor circuitry 620, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, and audio drivers to control and allow access to one or more audio devices.
The PMIC 624 may manage power provided to various components of the UE 600. In particular, with respect to the processors 604, the PMIC 624 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
A battery 628 may power the UE 600, although in some examples the UE 600 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 628 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 628 may be a typical lead-acid automotive battery.
The base station 700 may be similar to and substantially interchangeable with base station 78 of
The base station 700 may include processors 704, RF interface circuitry 708, core network (CN) interface circuitry 712, memory/storage circuitry 716, and antenna structure 726.
The components of the base station 700 may be coupled with various other components over one or more interconnects 728.
The processors 704, RF interface circuitry 708, memory/storage circuitry 716 (including communication protocol stack 710), antenna structure 726, and interconnects 728 may be similar to like-named elements shown and described with respect to
The CN interface circuitry 712 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to/from the base station 700 via a fiber optic or wireless backhaul. The CN interface circuitry 712 may include one or more dedicated processors or
FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 712 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
In some embodiments, the base station 700 may be coupled with transmit receive points (TRPs) using the antenna structure 726, CN interface circuitry, or other interface circuitry.
It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
In the following sections, further exemplary embodiments are provided.
Example 1 includes a method of operating a user equipment (UE), the method comprising: receiving, from a serving cell, configuration information for one or more candidate cells; identifying one or more execution conditions for conditional handover (CHO) or conditional primary secondary cell (PSCell) change (CPC) with respect to the one or more candidate cells; detecting a trigger to reduce an uplink transmit power in the serving cell based on a maximum power exposure (MPE) limit; and initiating a handover to a target cell of the one or more candidate cells based on detecting the trigger without the one or more execution conditions being met.
Example 2 includes the method of example 1, further comprising: determining the uplink transmit power is to be reduced from a first level to a second level to comply with the MPE limit; and performing the handover to the target cell based on the second level.
Example 3 includes the method of example 1 or 2, further comprising: determining signaling conditions in the target cell; and performing the handover to the target cell based further on the signal conditions.
Example 4 includes the method of example 3, wherein determining signaling conditions comprises: determining an available uplink transmit power to the target cell or a signal quality of a downlink signal of the target cell.
Example 5 includes the method of example 1, further comprising: calculating throughput with respect to the serving cell or the target cell; and preforming the handover based on the throughput.
Example 6 includes the method of example 1, wherein detecting the trigger comprises: sensing a body proximity.
Example 7 includes the method of example 1, wherein the target cell is a neighbor cell or a primary cell of a secondary cell group.
Example 8 includes the method of example 1, further comprising: identifying the target cell from the one or more candidate cells based on a measurement of the target cell.
Example 9 includes the method of example 1, further comprising: transmitting, to the target cell, a radio resource control (RRC) message that includes an indication that initiating the handover was done without the one or more execution conditions being met; or transmitting, to the serving cell, a media access control (MAC) control element (CE) that includes an indication that initiating the handover was done without the one or more execution conditions being met.
Example 10 includes a method of operating a user equipment (UE), the method comprising: receiving, from a serving cell, configuration information for a target cell; identifying one or more execution conditions for conditional handover (CHO) or conditional primary secondary cell (PSCell) change (CPC) to the target cell; detecting a proximate body based on a body proximity sensing (BPS) operation; and initiating a handover to the target cell based on detecting the proximate body without the one or more execution conditions being met.
Example 11 includes the method of example 10, further comprising: comparing an adjusted serving cell throughput based on an available exposure mitigation technique to a threshold or to a target cell throughput; and initiating the handover to the target cell based on said comparing of the adjusted serving cell throughput to the threshold or to the target cell throughput.
Example 12 includes the method of example 11, wherein the available exposure mitigation technique comprises: reducing an uplink transmit power; reducing an average uplink transmit power by reducing an uplink duty cycle; or changing an uplink transmit beam.
Example 13 includes the method of example 11, wherein the available exposure mitigation technique is to reduce directional exposure based on a maximum permissible exposure limit.
Example 14 includes the method of example 10, further comprising: determining signaling conditions in the target cell; and performing the handover to the target cell based further on the signal conditions.
Example 15 includes the method of example 10, wherein the target cell is a neighbor cell or a primary cell of a secondary cell group.
Example 16 includes the method of example 10, further comprising: receiving configuration information for a plurality of candidate cells; and identifying the target cell from the plurality of candidate cells based on a measurement of the target cell.
Example 17 includes the method of example 10, further comprising: transmitting, to the target cell, a radio resource control (RRC) message that includes an indication that initiating the handover was done without the one or more execution conditions being met; or transmitting, to the serving cell, a media access control (MAC) control element (CE) that includes an indication that initiating the handover was done without the one or more execution conditions being met.
Example 18 includes the method of example 10, wherein initiating the handover comprises: initiating a synchronization with the target cell.
Example 19 includes a method of operating a base station, the method comprising: transmitting, to a user equipment (UE), measurement configurations with respect to one or more neighbor cells; identifying at least one candidate cell from the one or more neighbor cells based on measurement reports received from the UE; and transmitting, to the UE, information to configure first execution conditions for conditional handover (CHO) or conditional primary secondary cell change (CPC) to a target cell of the at least one candidate cell, and to configure second execution conditions for an early CHO or an early CPC based on body positioning sensing or a maximum permissible exposure (MPE) limit.
Example 20 includes the method of example 19, further comprising: receiving, from the UE, a media access control (MAC) control element (CE) that includes an indication that the UE is to handover to the target cell without the first execution conditions being met.
Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 23 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 24 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
Example 26 may include a signal as described in or related to any of examples 1-20, or portions or parts thereof.
Example 27 may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 28 may include a signal encoded with data as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
Example 32 may include a signal in a wireless network as shown and described herein.
Example 33 may include a method of communicating in a wireless network as shown and described herein.
Example 34 may include a system for providing wireless communication as shown and described herein.
Example 35 may include a device for providing wireless communication as shown and described herein.
Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
This application claims the benefit of U.S. Provisional Patent Application No. 63/227,931, filed on Jul. 30, 2021, which is herein incorporated by reference in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 63227931 | Jul 2021 | US |
