UE requested candidate cell configuration update

Abstract

Methods, systems, and devices perform user requested updates of a candidate cell monitoring configuration. A user equipment (UE) (110A) receives, from a network entity (120A), a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters. The UE selects one or more candidate cell monitoring parameters of a plurality of candidate cell monitoring parameters for modification based on a condition of the UE. The UE transmits, to the network entity, a request (128) to update the one or more of the candidate cell monitoring parameters.

Description

UE REQUESTED CANDIDATE CELL CONFIGURATION UPDATERELATED APPLICATION[1] This application claims the priority benefit of U.S. Provisional Patent Application Serial No. 63 / 599,702, filed November 16, 2023, and entitled “UE REQUESTED CANDIDATE CELL CONFIGURATION UPDATE. " the entire contents of which is hereby incorporated by reference herein.TECHNICAL FIELD[2] Aspects of the present disclosure relate generally to wireless communication and techniques for user equipment requested update of a candidate cell configuration.BACKGROUND[3] A radio access network (RAN) has multiple cells where each cell includes at least one network element. Each cell may be associated with a network entity, a radio unit, a transmission reception point (TRP) of a network entity, a base station, a component carrier, or the like. In order to utilize the RAN to communicate with other devices or other network entities, the user equipment (UE) connects to a network element of a cell. The cell having the network element connected to the UE is referred to as a “serving cell.” There may be other cells adjacent to. or near to, the serving cell that the UE may establish a connection with if the communication quality within the serving cell becomes inadequate or if another cell can provide better communication quality. The network element may configure the UE with information regarding some or all of these other cells, which may be referred to as “candidate cells.” “target cells,” non-serving cells,” “neighbor cells,” or the like.[4] The UE may be capable of layer 1 / 2 (L1 / L2) triggered mobility (LTM) (also referred to as lower layer triggered mobility). In LTM, the UE monitors candidate cells by periodically measuring reference signals received from the candidate cells and reports such measurements to the network entity in the serving cell. LTM allows the UE and network entity to provide seamless switching between different cells when necessary, and may reduce higher layer (e.g., layer 3) message exchange and reconfiguration. In some aspects where the cell is associated with a component carrier, the switch to a different cell may involve a switch from one carrier to another carrier in the frequency domain. LTM procedures can reduce latency and packet loss, leading to a better user experience. In some aspects, the UE may perform a conditional LTM cell switch. In this case, the UE may be configured to detect a certain condition or conditions based on the LTM cell reference signal measurements. If thecondition(s) are met, the UE autonomously sends an uplink (UL) transmission to the target cell to initialize the cell switch. In some aspects, the UE reports the LTM cell reference signal measurements to the network entity of the serving cell, and in response, the network entity may transmit a cell switch command to the UE indicating information of the target cell or the target cell configuration which the UE applies for the cell switch. A network entity operating a candidate LTM cell is configured to periodically monitor reserved resources to detect whether the UE has performed a cell switch to the candidate LTM cell.BRIEF SUMMARY[5] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.[6] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communications by a user equipment (UE). The method includes the UE receiving, from a network entity, a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters. The method includes the UE selecting one or more candidate cell monitoring parameters of the plurality of candidate cell monitoring parameters for modification based on a condition of the UE. The method includes the UE transmitting, to the network entity, a request to update the one or more of the candidate cell monitoring parameters.[7] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communications by a network entity. The method includes the network entity transmitting, to a UE, a candidate cell monitoring configuration, the candidate cell monitoring configuration specifying one or more candidate cells. The method includes the network entity receiving, from the UE, a request to update one or more candidate cell monitoring parameters of the candidate cell monitoring configuration. The method includes the network entity transmitting an indicator to a second network entity operating at least one candidate cell of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.[8] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus or system. In some implementations, an apparatus includes a communication unit and a processing system. The processing system is configured to control the communication unit to implement any one of the methods described in this document.[9] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Note that the relative dimensions of the following figures may not be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0011] Figure 1A is a diagram illustrating an example wireless system including a user equipment (UE) communicating with a network entity in a serving cell where the UE is configured with a candidate cell monitoring configuration.

[0012] Figure IB is a diagram illustrating the example wireless system after a UE requested change in the candidate cell monitoring configuration.

[0013] Figure 2 is a sequence diagram illustrating example operations of a communications process for UE requested change in a candidate cell monitoring configuration.

[0014] Figure 3A is a timing diagram illustrating a configuration update after receiving an update confirmation.

[0015] Figure 3B is a timing diagram illustrating a configuration update after a predetermined time has elapsed following an update request.

[0016] Figure 3C is a timing diagram illustrating a configuration update after a predetermined number of update requests have been transmitted.

[0017] Figure 3D is a timing diagram illustrating a configuration update after a predetermined number of update requests have been transmitted within an update interval.

[0018] Figure 4 is a flow chart diagram illustrating example UE operations of a method for UE requested change in a candidate cell monitoring configuration.

[0019] Figure 5 is a flow chart diagram illustrating example network entity7operations of a method for UE requested change in a candidate cell monitoring configuration.

[0020] Figure 6 is a block diagram illustrating example user assistance information data for UE requested change in a candidate cell monitoring configuration.

[0021] Figure 7 is a block diagram illustrating example medium access control (MAC) control element (CE) data for UE requested change in a candidate cell monitoring configuration.

[0022] Figure 8 is a block diagram illustrating example configurations of a network entity and UE.DETAILED DESCRIPTION

[0023] The following description is directed to certain implementations for the purpose of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless communication according to the 3rd Generation Partnership Project (3GPP) wireless standards, such as the 4th generation (4G) Long Term Evolution (LTE) and 5thgeneration (5G) New Radio (NR) standards. However, the described implementations can be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 , 802.15, or 802.16 wireless standards, or other known signals that are used to communicate within a wireless, cellular, or internet of things (loT) network, such as a system utilizing 3G, 4G, 5G, 6thgeneration (6G), WiFi, or future radio technology.

[0024] A radio access network (RAN) has multiple cells where each cell includes at least one network element. Each cell may be associated with a network entity, a transmission reception point (TRP) of a network entity, a radio unit, a base station, a component carrier, or the like. In order to utilize the RAN to communicate with other devices or other network entities, the user equipment (UE) connects to a network element of a cell. The cell having the network element connected to the UE is referred to as a “serving cell.” There may be other cells adjacent to, or near to, the serving cell with which the UE may establish a connection if the communication quality within the serving cell becomes inadequate or if another cell can provide better communication quality. The network element may configure the UE with information regarding some or all of these other cells, which are referred to as “candidate cells,” “target cells,” “non-serving cells,” “neighbor cells,” or the like.

[0025] The UE may be capable of layer 1 / 2 (L1 / L2) triggered mobility' (LTM) (also referred to as lower layer triggered mobility). In LTM, the UE monitors candidate cells by periodically measuring reference signals received from the candidate cells and reports such measurements to the network entity in the serving cell. LTM allows the UE and netw ork entity to provide seamless switching between different cells when necessary, and may reduce higher layer (e.g., layer 3) message exchange and reconfiguration. In some aspects where the cell is associated with a component carrier, the switch to a different cell may involve a switch from one carrier to another carrier in the frequency domain. LTM procedures can reduce latency and packet loss, leading to a better user experience. In some aspects, the UE may perform aconditional LTM cell switch. In this case, the UE may be configured to detect a certain condition or conditions based on the LTM cell reference signal measurements. If the condition(s) are met, the UE autonomously sends an uplink (UL) transmission to the target cell to initialize the cell switch. In some aspects, the UE reports the LTM cell reference signal measurements to the network entity of the serving cell, and in response, the network entity maytransmit a cell switch command to the UE indicating information of the target cell or the target cell configuration which the UE applies for the cell switch. A network entity operating a candidate LTM cell is configured to periodically monitor reserved resources to detect whether the UE has performed a cell switch to the candidate LTM cell. Although some examples of this disclosure are based on LTM technology, the concepts can be applied to other types of mobility or cell monitoring procedures.

[0026] Monitoring candidate cells requires additional resources and consumes more power, both for the UE and for the network entity. It may be the case that the UE needs to reduce power consumption, for example due to a low battery charge or overheating. In such cases, it may be advantageous for the UE to reduce overhead associated with monitoring candidate cells or request that the network entity update the candidate cell monitoring configuration based on UE resources for candidate cell monitoring.

[0027] This disclosure provides systems, methods and apparatuses for a UE to request an update to the candidate cell monitoring configuration. The UE may request the update based on a condition indicating that candidate cell monitoring resources should be reduced. Such conditions include low- battery charge, overheating, or a change in the location of the UE. In various implementations, the UE may request a modification to the number of candidate cells monitored by the UE, a modification to the number of reference signals associated with candidate cells, or modification in the periodicity- of monitoring, among other examples. In some aspects, the UE may receive an update to the candidate cell monitoring configuration from the network entity in response to the request. In some aspects, the UE may autonomously update the candidate cell monitoring configuration after a predetermined time period following a requested update. Additionally, in some implementations, the network entity operating a serving cell can inform the network entities operating candidate cells of the updates thereby allowing the network entity- operating candidate cells to release resources associated with providing reference signals to the UE.

[0028] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. The UE can reduce power consumption associated with candidate cell monitoring when the battery level of the UE is low. Further, the UE can reduce the potential for overheating caused by processing relatedto candidate cell monitoring. Moreover, a network entity operating a candidate cell can reduce resources associated with providing UE specific reference signals to a UE when the UE is also reducing resources associated with candidate cell monitoring. For example, the network entity operating a candidate cell can release resources associated with transmitting UE specific reference signals used by the UE for ETM monitoring. Further, the network entity operating a candidate cell can release resources reserved for detecting an uplink transmission from the UE indicating a cell switch.

[0029] Figure 1A is a diagram illustrating an example wireless communication system 100 including a user equipment communicating with a network entity in a serving cell where the UE is configured with a candidate cell monitoring configuration. In the example shown in Figure 1A, wireless communication system 100 includes cells 126A-126G and various network elements such as network entities 120A and 120B, radio units (RUs) 121 A-121D, and UEs 110A and HOB. A cell (e.g., any of cells 126A-126G) may be associated with a network entity such as a base station, radio unit, TRP, or a carrier aggregation component. Cells 126A-126G may include various types of cells, including macrocells for higher-power network entities and / or small cells for lower-power network entities. Small cells may include femtocells, picocells, microcells, and the like.

[0030] A network entity such as a base station may operate multiple cells. In some traditional deployments, a base station may operate three (3) cells, but other quantities of cells may be deployed at a base station. A master cell group (MCG) may include a primary cell (PCell) and zero or more secondary cells (SCells) of an eNodeB (eNB, also referred to as an evolved node B). A secondary' cell group (SCG) may include a primary' SCG cell (PSCell) and zero or more secondary' cells (SCells) of a gNodeB (gNB). Once an SCG is added to the radio resource control (RRC) configuration, the UE may be in a non-standalone (NS A) mode of operation. Any of cells within the MCG or SCG may be referred to as a current serving cell. For dual connectivity (DC) operation, the term special cell (SpCell) refers to the PCell of the MCG or the PSCell of the SCG.

[0031] A network entity may support carrier aggregation. Carrier aggregation can provide greater network throughput by transmitting and receiving data using multiple frequencies in a frequency domain. Each frequency' may' be referred to as a component carrier. Data transmitted over multiple component carriers (CCs) may be aggregated and delivered to the target device. A first component carrier is associated with a PCell and is used for establishing access to a network entity and servers as a main component carrier. Subsequent component carriers are associated with SCells.

[0032] In the example shown in Figure 1 A, UE 11 OB has established a connection via radio unit 121B via a component carrier associated with PCell 122. Furthen UE HOB may communicate with radio unit 121 B using an additional component carrier associated with SCell 123. In this disclosure, PCells and SCells are considered cells, and the techniques described herein may be applied to PCells and SCells.

[0033] In the example shown in FIG. 1 A, the UE 110A has established a connection with network entity 120A in cell 126A and wirelessly communicates with the network entity 120A. The UE 110A may communicate directly with the network entity 120A or via one or more TRPs (not shown in FIG. 1A). A cell associated with a netw ork entity with which a UE has established a connection may be referred to as a “serving cell.” Thus, in the example shown in Figure 1 A, cell 126 A may be referred to as the serving cell for UE 110A because UE 110A has established a connection with network entity 120A in cell 126A.

[0034] Although illustrated as a smartphone in Figure 1 A, a UE such as UEs 110A and / or 11 OB may be implemented as any suitable computing or electronic device, such as a mobile communication device, a modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, an Intemet-of-things (IoT) device (e.g., sensor node, controller / actuator node, combination thereof), and the like. UE 110A may communicate with network entity 120 A using wireless links (not shown in FIG. 1A). which may be implemented as any suitable type of wireless link. The w ireless links may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3GPP LTE, 5G NR, and so forth. Multiple wireless links may be aggregated in a carrier aggregation to provide a higher data rate for the UE 110.

[0035] As examples, a network entity such as network entities 120 A and 120B may be a base station, an Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, ng-eNB, access point, radio head or the like. A network entity may be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof. A network entity (e.g., network entities 120 A or 120B) may be configured to use multiple-input and multiple-output (MIMO) communication to exchange wireless signals w ith UE 110.

[0036] A network entity (e.g., network entity 120A and network entity 120B) supports wireless communication with one or more UEs, such as UEs 110A and HOB, via radio frequency (RF) signaling using one or more applicable radio access technologies (RATs) as specified by one or more communications protocols or standards. The network entity mayemploy any of a variety of RATs. such as operating as a NodeB (or base transceiver station (BTS)) for a Universal Mobile Telecommunications System (UMTS) RAT (also known as “3G”), operating as an eNB for a 3 GPP LTE RAT, operating as a 5G node B C'gNB”) for a 3GPP 5G NR RAT, and the like.

[0037] The network entities 120A and 120B, and radio units 121A-121D may be part of a RAN, for example, an Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN, or NR RAN. The network entities 120A and 120B may be connected to a core network (not shown in Figure 1A). For example, the network entities 120A and 120B may connect to the core network through an NG2 interface for control-plane signaling and use an NG3 interface for user-plane data communications when connecting to a 5G core net ork. The network entities 120A and 120B may use an Si interface for control-plane signaling and userplane data communications when connecting to an evolved packet core (EPC) network. The network entities 120A and 120B may communicate using an Xn application protocol (XnAP) through an Xn interface or using an X2 application protocol (X2AP) through an X2 interface to exchange user-plane and control-plane data. A UE (e.g., UEs 110A and / or HOB) may connect, via the core network, to one or more wide area networks (WANs) or other packet data networks (PDNs), such as the Internet.

[0038] In some aspects, the functionality, and thus the hardw are components, of a network entity may be distributed across multiple network nodes or devices and may be distributed in a manner to perform the functions described herein. As one example, the functionality of network entity 120 may be distributed across a radio unit (RU) (e.g., any of radio units 121 A- 121D), a distributed unit (DU), or a central unit (CU).

[0039] Communications between a network entity and a UE utilize an uplink (UL) transmission path for transmission path for RF transmissions from the UE to the network entity and a downlink (DL) transmission path for RF transmissions from the network entity to the UE. For example, as shown in Figure 1A, the UE 110A utilizes UL transmission path 114 for RF transmissions from the UE 110A to the network entity 120A and DL transmission path 112 for RF transmissions from the network entity 120A to the UE 110A. In the context of the UL transmission path 114, the UE 1 10A serves as the data sending device and the network entity 120A serves as the data receiving device, whereas in the context of the DL transmission path 112, the netw ork entity7120A serves as the data sending device and the UE 110A sen es as the data receiving device. UL transmission path 114 and DL transmission path 112 may utilize multiple communications channels for signal transmission. The multiple channels may each have different purposes.

[0040] UL transmission path 114 may include a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH). and a physical random access channel (PRACH). The PUSCH is used for the transmission of user data, such as voice data, video data, or text message data from the UE (e.g., UEs 110A and / or HOB) to the network entity (e.g., network entities 120A and / or 120B). Additionally, the PUSCH may be used to transmit control information (e.g., uplink control information (UCI)). The PUSCH may be shared by multiple UEs. The PUCCH is used for transmitting control information (e.g., UCI) from the UE to the network, such as channel quality feedback, scheduling requests, and acknowledgments. The PRACH is used for random access in the uplink direction, enabling the UE to access the system.

[0041] DL transmission path 112 may include one or more of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical broadcast channel (PBCH), or a paging channel. The PDSCH is used for transmission of user data from the network entity to the UE. The PDSCH may be shared by multiple UEs. As with the PUSCH, the data may be any type of information, such as voice data, video data, or text message data. The paging channel is used to notify a UE that there is incoming traffic for it from a network entity.

[0042] In the example shown in Figure 1 A, the UE 110A may be capable of LTM. In this example, network entity 120 A has provided a candidate cell monitoring configuration to the UE 110 A for use in LTM. The configuration specifies that UE 110A may monitor and measure reference signals (RSs) for network entities associated with cells 126B-126E and report such measurements to the netw ork entity 120 A in the serving cell 126A. In this configuration, cells 126B-126E may be referred to as “active candidate cells'’ because UE 110A is actively monitoring RSs for cells 126B-126E, and these cells are candidates to become a “target cell” in an LTM switch. In this example, cells 126F and 126G may be referred to as “inactive candidate cells” or “deactivated candidate cells” because the UE 110A is not actively monitoring RSs from these cells for LTM purposes.

[0043] The UE 110A may be configured to detect a certain condition or conditions based on the RS measurements. If the condition(s) are met, the UE autonomously may initiate LTM procedures and send an uplink (UL) transmission to the network entity 120A to initialize a cell switch. For example, UE 110A may detect that communication quality between the UE 110A and the network entity 120A has deteriorated, and that better communication quality can be achieved by switching to communicating with radio unit 121C of cell 126D. The UE 110A may report the RS measurements to the network entity 120 A, and in response, the networkentity 120 A may transmit a cell switch command to the UE 110A indicating information of the target cell 126D.

[0044] In the example shown in Figure 1A, the UE 110A has detected a condition indicating the UE 110A is to reduce resources associated with monitoring RSs used for LTM. For example, the battery level of the UE 110 may be lower than a threshold level, the temperature of the UE 110A may rise above a threshold level, or the UE 110A may have changed locations. In response to detecting the condition, the UE 110 may transmit a request 128 to update the candidate cell monitoring configuration to reduce resources associated with LTM. In some aspects, the request 128 to update the candidate cell monitoring configuration may identify the candidate cell that the UE 110A will no longer monitor for LTM procedures. In some aspects, the request 128 may identify the resources to be reduced, e.g., resources associated with a candidate cell that will no longer be monitored.

[0045] Figure IB is a diagram illustrating the example wireless communication system 100 after a UE requested change in the candidate cell monitoring configuration. Figure IB continues the example shown in Figure 1A. In the example shown in Figure IB, the UE 110A has transmitted a request to stop monitoring resources associated with candidate cell 126E. In some aspects, the network entity 120A transmits an updated candidate cell monitoring configuration that specifies that cells 126B-126D are now candidate cells for LTM. Cell 126E is not specified as a candidate cell in the updated configuration and the UE 110A no longer monitors RSs from cell 126E. Thus, cell 126E may change from an ‘"active candidate celf’ to a “deactivated candidate cell" or “inactive candidate cell.’’ The UE may release resources associated with monitoring RSs from cell 126E.

[0046] In the example shown in Figures 1A and IB, network entity 120B is the network entity that is associated with cell 126E. In some aspects, network entity 120A transmits a message to network entity 120B indicating the network entity 120B can release resources associated with providing UE specific RSs intended for use by UE 110A in LTM procedures. A potential technical advantage of releasing such resources is that the network entity7120B can provide the released resources for other uses, thereby potentially increasing throughput and / or efficiency of the network entity.

[0047] It is noted that updates to the candidate cell monitoring configuration can either decrease or increase resource usage on the UE and network. For example, if the UE battery level is low or the UE is experiencing thermal issues, the UE may request an update to the candidate cell monitoring configuration to reduce the number of candidate cells being monitored, reduce the number of RSs being monitored, reduce the periodicity of monitoring, and / or reduce the reporting periodicity. On the other hand, if the condition of the UE battery improves (i.e., the UE is plugged into a charger) or the thermal issues are reduced, the UE may request an update to the candidate cell monitoring configuration to increase the number of candidate cells being monitored (including reactivating previously deactivated candidate cells), increase the number or RSs being monitored, increase the monitoring periodicity, and / or increase the reporting periodicity.

[0048] The disclosed techniques may improve power consumption in UEs when compared to existing systems. For example, the UE can initiate a request to update a candidate cell monitoring configuration to reduce power consumption associated with candidate cell monitoring when conditions on the UE make such a reduction desirable, for example, when the battery charge of the UE is low or when the UE is at risk of overheating. The UE need not wait for the network entity to update the candidate cell monitoring configuration.

[0049] Figures 2, 3 A-3D, and 4-9 along with the accompanying description below describe various techniques and aspects for UE requested candidate cell configuration updates. In some examples that follow, the operations may be described as utilizing RRC signaling. Unless specified otherwise, RRC signaling may indicate a RRC reconfiguration message from the network entity to the UE, or a system information block (SIB).

[0050] Figure 2 is a sequence diagram 200 illustrating example operations of a communications process for UE requested change in a candidate cell monitoring configuration. Although not illustrated for the sake of illustration clarity, various acknowledgements for messages illustrated in Figure 2 may be implemented to ensure reliable operations for UE requested candidate cell monitoring configuration updates. In the example discussed with respect to Figure 2, network entity 120A is associated with a serving cell, and network entities 120B and 120X are associated with candidate cells for LTM switching.

[0051] At operation 201, the UE 110A may transmit or report to network entity 120A the UE’s capability(s) for supporting UE requested candidate cell monitoring configuration updates. In some aspects, UE 110A may transmit UE capability information to the network entity 120A during an initial communication session setup process between the UE 110A and the network entity 120A. After establishing a communication session with network entity 120 A, the network entity' 120 A may be referred to as a “serving cell network entity.” The UEcapability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rates, and network protocols. Additionally, the UE 1 10A may report UE capability to the network entity 120 A indicating whether the UE supports UE requested candidate cell monitoring configuration updates.

[0052] In the example of Figure 2, the UE 110A may transmit UE capability information to network entity 120A. In some implementations, the network entity may receive the UE capability information from a core network (e.g., from an access and mobility management function (AMF) of the core network). In some other implementations, the network entity may receive the UE capability from another network entity (e.g., a gNB or eNB).

[0053] At operation 202, the network entity 120A may, depending on the UE capability information received at operation 201. configure the UE 110A for UE requested candidate cell configuration updates. In some aspects, the network entity 120 may configure the UE 1 10 via RRC signaling, for example, RRCReconfiguration message. In some aspects, the network entity 120 may provide one or more of the following parameters: a set of active candidate cells, and / or a set of RSs to be used for monitoring active candidate cells, for example, for use in LTM procedures. In some aspects, the candidate cell monitoring configuration may also include a monitoring periodicity, an indication of one or more rules to use for updating a candidate cell monitoring configuration, a first time period after which the UE should autonomously update the candidate cell monitoring configuration, and / or a second time period after which the UE will update the candidate cell monitoring configuration after receipt from the network entity of a confirmation of a request to update the candidate cell monitoring configuration.

[0054] At operation 204. the network entities 120B and 120X may transmit RSs to the UE 110A for use in LTM switching procedures. The UE 110A may measure the RSs to determine if an LTM switch is desirable. In some aspects, the RSs may include synchronization signal blocks (SSBs). In some other aspects, the RSs may include channel state information reference signals (CSI-RSs).

[0055] At operation 206, the UE 110A may provide a candidate cell RS measurement report to the network entity 120A. The candidate cell RS measurement report may be based on the RRC configuration described in operation 202. In some aspects, the candidate cell RS measurement report may be provided in LI signaling. For example, the report may be provided in a PUCCH transmission. In some other examples, the report may be provided in a PUSCH transmission. In some aspects, the candidate cell RS measurement report may include one or more channel metrics regarding a candidate cell and / or RS, and a cell identifier (ID) and / or RS ID corresponding to the reported candidate cell or RS. The channel metric may be one or moreof an LI or layer 3 (L3) reference signal received power (RSRP), signal -to-interference-plus- noise ratio (SINR). reference signal received quality' (RSRQ). and the like.

[0056] At operation 208, the UE 1 10A selects a configuration update. The UE 1 10A may select a configuration update in response to the UE 110A detecting a condition of the UE. In some aspects, the condition may include detecting a battery' level crossing a charge threshold value. For example, the battery charge level may have decreased below a predetermined or configurable level. In some aspects, the condition may include detecting that a temperature of the UE 110A has crossed a threshold value. For example, the UE 110A may detect that the temperature of the UE 110A or a component of the UE 110A has increased beyond a threshold where damage to the UE 110A or component of the UE 110A may occur. In some aspects, the condition may be a change in the location of the UE 110A within the cell. For example, the UE 1 10A may have moved within the serving cell to a location that is further from one or more of the active candidate cells.

[0057] In some aspects, the updates may be an output of a machine learning model that uses a history’ of measurements RSs, conditions of the UE 110 A, and / or UE location as input. In some aspects, the history information may be collected by the UE 110A. In some other aspects, the history' information may be provided to the UE 110A by the network. In some further aspects, the history information may be provided to the UE 110 by a third party' service, for example, the UE vendor or other third party. Similarly, the machine learning model may be provided by the network, a mobile network operator, or a third party.

[0058] At operation 210, the UE 110A may transmit an indication of a requested update to the candidate cell monitoring configuration to the network entity’ 120A. In some aspects, the requested update may be to deactivate one or more activated candidate cells such that the UE 110A will no longer monitor RSs from the deactivated candidate cells. In some aspects, the requested update may be to reduce the number of RSs for active candidate cells such that the UE 110A will monitor fewer RSs from the indicated active candidate cells. In some aspects, the requested update may be to modify aperiodicity of candidate cell RS measurement reports.

[0059] The UE 110A may transmit the indication of the requested update to the network entity 120A in various ways. In some aspects, the UE 110A may transmit the indication of the requested update in RRC signaling. In some other aspects, the UE 110A may' transmit the indication of the requested update using an UL medium access control (MAC) control element (CE). In some other aspects, the UE 110A may transmit the indication of the requested update in uplink control information (UCI) via a PUCCH or PUSCH transmission.

[0060] Example implementations where the UE 1 10 transmits the indication of the requested update in RRC signaling will now' be described. In some aspects, the UE 110Atransmits RRC signaling to the network entity 120A where the RRC includes user assistance information (UAI) that includes an indication of the requested update to the candidate cell monitoring configuration. A UAI type included in the UAI may specify that the UAI contains a requested update to the candidate cell monitoring configuration. In some aspects, the UAI may include an updated list identifying one or more cells to be monitored by the UE 110A for LTM purposes. In some aspects, the UAI may include an updated list of RSs to be monitored by the UE 110A for LTM purposes.

[0061] In some aspects, the UAI may include an updated number of candidate cells or RSs that the UE can monitor. The candidate cells or RSs to be monitored after the update to the candidate cell monitoring configuration may be selected based on a predefined or configurable rule, where the same rule is applied by both the UE 110A and the network entity 120A to update the candidate cell monitoring configuration. For example, the rule may specify that the UE 110A will no longer monitor candidate cells or RSs having the lowest RSRP in the most recent candidate cell RS measurement report provided at operation 206.

[0062] Example implementations where the UE 110 transmits the indication of the requested update using an UL MAC CE will now be described. In some aspects, the UE 110A may transmit a scheduling request to the network entity associated with the serving cell, in this example, network entity7120A. The network entity7120A may transmit a UL grant for PUSCH in response to the scheduling request. In some aspects, the UE may send the request to update the candidate cell monitoring configuration in a MAC CE via the granted PUSCH resource.

[0063] In some other aspects, the UE 110A may transmit a contention-free RACH or contention-based RACH. A Type-1 random access procedure also may be referred to as a 4- step RACH procedure. The Type-1 random access procedure includes a protocol of up to four messages (referred to as Msgl, Msg2, Msg3, and Msg4). To begin the Type-1 random access procedure, a UE transmits a random access preamble in a first message (Msgl) via a PRACH. The network entity responds to the Msgl by transmitting a second message (Msg2) via a PDSCH. The Msg2 is also referred to as a random access response (RAR). In some instances, the Msg2 indicates scheduled resources (in a PUSCH) for the UE to use for transmission of a third message (Msg3). When applicable, the UE transmits the Msg3 via the PUSCH resources granted in Msg2. In response to the Msg3, the network entity transmits a fourth message (Msg4). The Msg4 is also referred to as a contention resolution transmission (Msg4). It is noted that the Msg3 and the Msg4 might not be needed. For example, the UE can include a small data transmission with the random access preamble in the Msgl and the network entity can include a response in the Msg2 without providing a grant for uplink resources for the Msg3.

[0064] A Type-2 random access procedure can also be referred to as a 2-step RACH procedure. In the 2-step RACH procedure, the UE can transmit the random access preamble followed by a PUSCH in a first message (referred to as Message A or MsgA). The network entity responds to the MsgA by transmitting a second message (referred to as Message B or MsgB) via a PDSCH. One way to describe the 2-step RACH is that the MsgA is a combination of the Msgl and Msg3 in a first transmission and the MsgB is a combination of the Msg2 and Msg4 in a second transmission.

[0065] In some aspects, the RACH transmission for a UE initiated request to update a candidate cell monitoring configuration may have a preamble identifying the RACH as initiating a request to update the candidate cell monitoring configuration. That is, one or more preambles may be reserved to initiate the request to update the candidate cell monitoring configuration. In other aspects, the UE may send the request to update the candidate cell monitoring configuration in a subsequent UL transmission. For example, the UE may transmit the request in the PUSCH transmission of MsgA for the 2-step RACH procedure or in Msg3 for the 4-step RACH procedure.

[0066] In some aspects, the UE may be configured with a plurality of LTM configurations associated with a plurality of LTM configuration IDs. The MAC CE may include one or more LTM configuration IDs that identifies the specific candidate cell monitoring configuration(s) to be updated. The MAC CE may have one or more MAC CE types that may be used to indicate a request to update a candidate cell monitoring configuration. In some aspects, a single MAC CE type may be defined that indicates that the MAC CE contains a request to update the candidate cell monitoring configuration. The UE 11 OA uses various fields within the MAC CE to indicate the specific types of updates being requested and the updated values. For example, a single MAC CE type may indicate a request to update a candidate cell monitoring configuration. Fields within the MAC CE indicate whether the request is a request for cell deactivation or activation, RS activation or deactivation, and / or an update to the RS monitoring periodicity. Other fields within the MAC CE provide indicators for the values associated with the requested update, e.g., the candidate cell ID for cell activation or deactivation, indicators indicating which RSs are to be activated or deactivated, and / or an indicator indicating an updated periodicity’. Further details on an example MAC CE are described below- with respect to Figure 7.

[0067] In some other aspects, the MAC CE may be one of multiple types, where each MAC CE type indicates the type of update being requested and fields with the MAC CE indicate the updated value for the request type. Different types of MAC CEs may be defined for different request purposes. For example, a first MAC CE type may indicate cell activation ordeactivation. A second MAC CE type may indicate a request for RS activation or deactivation. A third MAC CE type may be defined that indicates a request to update RS monitoring periodicity. Each of the different MAC CE types associated with requests for candidate cell monitoring configuration updates may use different MA CE subheaders. In some aspects, each type of request is defined by a different logical channel ID (LCID) in the subheader.

[0068] Example implementations where the UE 110 transmits the indication of the requested update in UCI in an LI report will now be described. In some aspects, the UE reports a “special” or “reserved” value for an RS or candidate cell that indicates that the RS or candidate cell is to be deactivated. For example, the UE 110A may transmit an LI report with UCI indicating that the RSRP or SINR for the RS or candidate cell is outside of a valid range for the RSRP or SINR to indicate a request for deactivation of the indicated RS or candidate.

[0069] In some aspects, the UE may indicate a request for deactivating a candidate cell by transmitting an LI report in UCI that indicates measurements of all of the RSs associated with the candidate cell are outside of a valid range. In some other aspects, the UE may indicate a request for deactivating a cell by transmitting an LI report including UCI that indicates measurements of all of the RSs associated with the candidate cell are below a predetermined or configurable threshold.

[0070] In some other aspects, the UE 110A may update the candidate cell monitoring configuration using an LI report based on a trigger condition. For example, in some instances, the trigger condition may be sending the LI report with values indicating an RS or candidate cell measurements are outside of a valid range a predetermined or configurable number of times. In some other instances, the trigger condition may be sending the LI report with values indicating an RS or candidate cell measurements are outside of a valid range a predetermined or configurable number of times within a predefined or configurable time interval. In some aspects, when the triggering condition occurs, the UE may initiate a contention-free RACH process. The LI report may be sent in the PUSCH of MsgA of the 2-step RACH procedure or in Msg3 of the 4-step RACH procedure.

[0071] At operation 212. the network entity 120A may optionally transmit a confirmation message to the UE 110A confirming the request to update the candidate cell monitoring configuration received from the UE 110A at operation 210. In some aspects the network entity 120A may confirm the same update to the candidate cell monitoring configuration as requested by the UE 110 A. In some other aspects, the network entity 120 A may respond with a different candidate cell monitoring configuration than was requested by the UE 110 A.

[0072] In some aspects, the confirmation message may be an acknowledgement (ACK) of the request to update the candidate cell monitoring configuration to indicate that the networkentity 120A has received and / or accepted the request. In implementations where the request was transmitted from the UE 110A to the network entity 120A via a MAC CE or via RRC signaling, the ACK may be associated with an UL grant provided to the UE 110A by the network entity 120A via PDCCH. In some aspects, the UL grant may indicate the same hybrid automatic repeat request (HARQ) process ID as that of the PUSCH that carried the request transmitted from the UE 110A. In some aspects, the confirmation message may indicate that the network entity agrees to the update of the candidate cell monitoring configuration. The confirmation message may be transmitted from the network entity 120A to the UE 110A via an RRCReconfiguration message, a MAC CE, or a downlink control information (DCI) that indicates the updated candidate cell monitoring configuration.

[0073] At operation 214, the network entity may transmit an updated candidate cell configuration to candidate cell network entity 120B. The updated candidate cell configuration may indicate to the candidate cell network entity 120B that the associated candidate cell has been deactivated, and that it can release resources previously dedicated for use by the UE 110A for LTM procedures with respect to the deactivated candidate cell. For example, the network entity may release resources that were used for transmitting RSs specifically to the UE 110A, for example, RSs to be used for LTM procedures. Further, the network entity 120B may release resources associated with monitoring for an UL transmission from the UE 110A associated with an LTM switch to the network entity 120B because such a switch will not occur while the cell is deactivated.

[0074] At operation 216, the UE 1 10A and network entities 120A and 120B may implement the updated candidate cell monitoring configuration. In some aspects the UE 11 OA may update the candidate cell monitoring configuration X ms after sending the request to update the candidate cell monitoring configuration at operation 210. In some aspects, the UE 1 10A may update the configuration autonomously based on the requested configuration updates.

[0075] In some other aspects, the UE 110A may update the candidate cell monitoring configuration based on a trigger condition. For example, in some instances, the trigger condition may be sending the report at operation 206 a predetermined or configurable number of times. In some other instances, the trigger condition may be sending the report at operation 206 a predetermined or configurable number of times w ithin a predetermined or configurable time interval. In some aspects, the UE may update the candidate cell monitoring configuration X ms after the trigger condition is detected.

[0076] In some other aspects, the UE may update the candidate cell monitoring configuration Y ms after receiving a confirmation or acknowledgement of the request to update the candidate cell monitoring configuration transmitted at operation 210.

[0077] Figures 3A-3D include example timing diagrams illustrating relative timings of various operations performed during a UE requested update to a candidate cell monitoring configuration. The timing diagrams may not be drawn to scale, and the time durations between the various operations may differ from that shown in the Figures.

[0078] Figure 3A is a timing diagram illustrating a configuration update after receiving an update confirmation. In the example timing diagram 300 shown in Figure 3 A, the UE 110A receives a series of RSs 302A, 302B, and 302C at times to, ti, and t2. respectively, and calculates measurements of the received RSs for use in determining if an LTM switch is to be performed. At time ts, the UE 1 10A detects a change in the condition of the UE. For example, the UE 110 A may detect a batten- charge level below a threshold value, a thermal measurement above a threshold value, or a change in the location of the UE. In response to detecting the change in condition, the UE 110, at operation 208, selects a candidate cell monitoring configuration update. For example, the UE 110A may select a candidate cell for deactivation, a reference signal for deactivation, or a change in the monitoring periodicity. At time t4, The UE 110A transmits a request 304 to update the candidate cell monitoring configuration to the network entity 120 A. At time F. The UE 110A receives a confirmation 306 confirming that the network entity 120A has received the request. At time t6. the updated candidate cell monitoring configuration is implemented 216 by the UE 110A and takes effect.

[0079] Figure 3B is a timing diagram illustrating a configuration update after a predetermined time has elapsed following an update request. Like the example timing diagram 300 of Figure 3A. in the example timing diagram 310 shown in Figure 3B. the UE 110A receives a series of RSs 302A, 302B, and 302C at times to, ti, and t2, respectively, and calculates measurements of the received RSs for use in determining if an LTM switch is to be performed. At time t3, the UE 110A detects a change in the condition of the UE. For example, the UE 110A may detect a battery charge level below a threshold value, athermal measurement above a threshold value, or a change in the location of the UE. In response to detecting the change in condition, the UE 110, at operation 208, selects a candidate cell monitoring configuration update. For example, the UE 110A may select a candidate cell for deactivation, a reference signal for deactivation, or a change in the monitoring periodicity. At time t4, The UE 110A transmits a request 304 to update the candidate cell monitoring configuration to the network entity 120A. Time t4 is the start of a predetermined or configurable time interval 312 during which the UE 110A waits to update the candidate cell monitoring configuration. Attime ts. the end of the predetermined inters- al occurs and the UE 110A implements 216 the updated candidate cell monitoring configuration.

[0080] Figure 3C is a timing diagram illustrating a configuration update after a predetermined number of update requests have been transmitted. Like the example timing diagram 300 of Figure 3A and the example timing diagram 310 of Figure 3B, in the example timing diagram 320 shown in Figure 3C, the UE 110A receives a series of RSs 302A, 302B, and 302C at times to, ti, and t2, respectively, and calculates measurements of the received RSs for use in determining if an LTM switch is to be performed. At time ts, the UE 110A detects a change in the condition of the UE. For example, the UE 110A may detect a battery charge level below a threshold value, a thermal measurement above a threshold value, or a change in the location of the UE. In response to detecting the change in condition, the UE 110, at operation 208, selects a candidate cell monitoring configuration update. For example, the UE 110A may select a candidate cell for deactivation, a reference signal for deactivation, or a change in the monitoring periodicity. From times t4, through te The UE 110A transmits a series of requests 304A-304N to update the candidate cell monitoring configuration to the network entity 120 A. After the Nth consecutive update request, at time t7, the UE 110A implements 216 the updated candidate cell monitoring configuration. As discussed above, the value of N may be a predetermined or configurable value.

[0081] Figure 3D is a timing diagram illustrating a configuration update after a predetermined number of update requests have been transmitted within an update interval. Like the example timing diagrams 300, 310, and 320 of Figures 3A, 3B, and 3C, respectively, in the example timing diagram 330 shown in Figure 3D, the UE 110A receives a series of RSs 302A, 302B, and 302C at times to. ti, and t2, respectively, and calculates measurements of the received RSs for use in determining if an LTM switch is to be performed. At time ts, the UE 110A detects a change in the condition of the UE. For example, the UE 110A may detect a battery charge level below a threshold value, a thermal measurement above a threshold value, or a change in the location of the UE. In response to detecting the change in condition, the UE 110, at operation 208, selects a candidate cell monitoring configuration update. For example, the UE 110A may select a candidate cell for deactivation, a reference signal for deactivation, or a change in the monitoring periodicity. Time t4 is the start of an update interval 312 that runs through time ts. From times ts, through t7, the UE 110A transmits a series of requests 304A-304M to update the candidate cell monitoring configuration to the netw ork entity 120A. After M update requests have been sent during the update interval 332, the UE 110A implements 21 the updated candidate cell monitoring configuration. As discussed above, thevalue of M and the size of the update interval 332 may be predetermined or configurable values.

[0082] Figure 4 is a flow chart diagram illustrating example UE operations of a method for UE requested change in a candidate cell monitoring configuration. The example operations of method 400 may be performed, for example, by UE 110A of Figures 1A, IB, 2, and / or 3A- 3D.

[0083] At block 401, and as described above with respect to Figure 2. operation 201, the UE may transmit or report to a serving cell network entity the UE’s capability(s) for supporting UE requested candidate cell monitoring configuration updates. In some aspects, the UE may transmit UE capability information to the network entity during an initial communication session setup process between the UE and the network entity. The UE capability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rates, and network protocols. The UE 110A may report UE capability information to the network entity 120 A indicating whether the UE supports UE requested candidate cell monitoring configuration updates.

[0084] At block 402, and as described above with respect to Figure 2, operation 202, the UE may receive, from the serving cell network entity, a configuration for UE requested candidate cell monitoring configuration updates. In some aspects, the configuration may include one or more of the following parameters: a set of active candidate cells, and / or a set of RSs to be used for monitoring active candidate cells, for example, for use in LTM procedures. In some aspects, the candidate cell monitoring configuration may also include a monitoring periodicity, an indication of one or more rules to use for updating a candidate cell monitoring configuration, a first time period after which the UE should autonomously update the candidate cell monitoring configuration, and / or a second time period after which the UE will update the candidate cell monitoring configuration after receipt from the network entity of a confirmation a request to update the candidate cell monitoring configuration.

[0085] At block 404, and as described above with respect to Figure 2, operation 204, the UE may receive RSs from various network entities in different cells for use in LTM switching procedures. The UE may measure the RSs to determine if an LTM switch is desirable.

[0086] At block 406, and as described above with respect to Figure 2, operation 206, the UE may provide a candidate cell RS measurement report to the serving cell network entity. In some aspects, the candidate cell RS measurement report may be provided in LI signaling. For example, the report may be provided in a PUCCH or PUSCH.

[0087] At block 408, and as described above with respect to Figure 2, operation 208, the UE 110 A selects a configuration update. The UE may select a configuration update in responseto the UE detecting a condition of the UE. In some aspects, the condition may include detecting a battery level crossing a charge threshold value. For example, the battery charge level may have decreased below a predetermined or configurable level. In some aspects, the condition may include detecting that a temperature of the UE has crossed a threshold value. For example, the UE may detect that the temperature of the UE or a component of the UE has increased beyond a threshold where damage to the UE or component may occur. In some aspects, the condition may be a change in the location of the UE within the cell. For example, the UE may have moved within the serving cell to a location that is further from one or more of the active candidate cells. In some aspects, the condition may be an output of a machine learning model that uses a history of measurements RSs and / or conditions of the UE 110A as input.

[0088] At block 410, and as described above with respect to Figure 2, operation 210, the UE may transmit an indication of a requested update to the candidate cell monitoring configuration to the serving cell network entity. In some aspects, the requested update may be to deactivate one or more active candidate cells such that the UE will no longer monitor RSs from the deactivated candidate cells. In some aspects, the requested update may be to reduce the number of RSs for active candidate cells such that the UE will monitor fewer RSs from the indicated active candidate cells. In some aspects, the requested update may be to modify a periodicity of candidate cell RS measurement reports.

[0089] At block 412, and as described above with respect to Figure 2, operation 212, the UE may optionally receive a confirmation message from the serving cell network entity confirming the request to update the candidate cell monitoring configuration. In some aspects, the confirmation message may be an ACK of the request to update the candidate cell monitoring configuration to indicate that the serving cell network entity has received and / or accepted the request. In some aspects, the confirmation message may indicate that the network entity agrees to the update of the candidate cell monitoring configuration.

[0090] At block 416, and as described above with respect to Figure 2, operation 216, the UE may implement the updated candidate cell monitoring configuration. In some aspects the UE may update the candidate cell monitoring configuration X ms after sending the request to update the candidate cell monitoring configuration at operation 210. In some aspects, the UE 110A may update the configuration autonomously based on the requested configuration updates.

[0091] Figure 5 is a flow chart diagram illustrating example network entity operations of a method for UE requested change in a candidate cell monitoring configuration. The operations of method 500 may be performed by the network entity 120A of Figures 1 A, I B, 2, and / or 3A-3D.

[0092] At block 501, and as described above with respect to Figure 2, operation 201, the network entity may receive a report of the UE’s capability (s) for supporting UE requested candidate cell monitoring configuration updates. In some aspects, the network entity may receive the capability information from the UE during an initial communication session setup process between the UE and the network entity. The UE capability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rates, and network protocols. The UE capability information may indicate whether the UE supports UE requested candidate cell monitoring configuration updates.

[0093] At block 502, and as described above with respect to Figure 2, operation 202, the network entity may transmit, to the UE, a configuration for UE requested candidate cell monitoring configuration updates. In some aspects, the configuration may include one or more of the follow ing parameters: a set of active candidate cells, and / or a set of RSs to be used for monitoring active candidate cells, for example, for use in LTM procedures. In some aspects, the candidate cell monitoring configuration may also include a monitoring periodicity7, an indication of one or more rules to use for updating a candidate cell monitoring configuration, a first time period after which the UE should autonomously update the candidate cell monitoring configuration, and / or a second time period after which the UE will update the candidate cell monitoring configuration after receipt from the netw ork entity7of a confirmation a request to update the candidate cell monitoring configuration.

[0094] At block 506, and as described above with respect to Figure 2. operation 206, the network entity may receive a candidate cell RS measurement report from the UE. In some aspects, the candidate cell RS measurement report may be provided in LI signaling. For example, the report may be provided in a PUCCH or PUSCH.

[0095] At block 510, and as described above with respect to Figure 2, operation 210, the network entity may receive an indication of a requested update to the candidate cell monitoring configuration from the UE. In some aspects, the requested update may be to deactivate one or more active candidate cells such that the UE will no longer monitor RSs from the deactivated candidate cells. In some aspects, the requested update may be to reduce the number of RSs for active candidate cells such that the UE will monitor fewer RSs from the indicated active candidate cells. In some aspects, the requested update may be to modify a periodicity7of candidate cell RS measurement reports.

[0096] At block 512, and as described above with respect to Figure 2, operation 212, the network entity may optionally transmit a confirmation message to the UE confirming the request to update the candidate cell monitoring configuration. In some aspects, the confirmation message may be an ACK of the request to update the candidate cell monitoringconfiguration to indicate that the network entity has received and / or accepted the request. In some aspects, the confirmation message may indicate that the network entity agrees to the update of the candidate cell monitoring configuration.

[0097] At block 514, and as described above with respect to Figure 2, operation 214, the network entity may transmit an updated candidate cell configuration to candidate cell network entities that are affected by the updated candidate cell monitoring configuration. For example, in the case that a candidate cell is deactivated, the deactivated candidate cell network entity can release resources previously dedicated for use by the UE for LTM procedures. For example, the candidate cell network entity may release resources that were used for transmitting RSs specifically to the UE, for example, RSs to be used for LTM procedures. Further, the candidate cell network entity may release resources associated with monitoring for an UL transmission from the UE associated with an LTM switch to the candidate cell network entity because such a switch will not occur while the cell is deactivated.

[0098] At block 516, and as described above with respect to Figure 2, operation 216, the network entity may implement the updated candidate cell monitoring configuration.

[0099] Figure 6 is a block diagram illustrating example user assistance information (UAI) data 602 for a UE requested change in a candidate cell monitoring configuration. In some aspects, the UAI data 602 may include one or more of a candidate cell list 604, a candidate cell RS list 606, a number of monitored candidate cells 608, a number of monitored RSs 609, a monitoring periodicity 610, and a report periodicity 612.

[0100] Candidate cell list 604 may specify an updated list of candidate cells for monitoring. The updated list may contain fewer or more candidate cells than in the current candidate cell monitoring configuration. In some aspects, the candidate cell list 604 may specify an updated list of candidate cell IDs for monitoring. In some other aspects, the candidate cell list 604 may specify an updated list of candidate cell indexes.

[0101] Candidate cell RS list 606 may specify an updated list of RSs that are to be monitored. The updated list may contain fewer or more RSs than in the current candidate cell monitoring configuration. In some aspects, the candidate cell RS list 606 may specify an updated list of RS indexes. For example, the updated list of RS indexes may include an updated list of SSB indexes or CSI-RS indexes.

[0102] Number of monitored candidate cells 608 may specify an update to the number of candidate cells that the UE can monitor. In some aspects, the number of monitored candidate cells 608 may be associated with a maximum number of monitored candidate cells. In some other aspects, the number of monitored candidate cells 608 may be associated with a minimum number of monitored candidate cells.

[0103] Number of monitored RSs 609 may specify an update to the number of candidate cell RSs that the UE can monitor. In some aspects, the number of monitored RSs 609 may be associated with a maximum number of monitored RSs per candidate cell or across all candidate cells. In some other aspects, the number of monitored RSs 609 may be associated with a minimum number of monitored RSs per candidate cell or across all candidate cells.

[0104] Monitoring periodicity 610 may specify an update to the monitoring periodicity for monitoring RSs or candidate cells. In some aspects, the monitoring periodicity 610 may be associated with a maximum periodicity for monitoring RSs or candidate cells. In some other aspects, the monitoring periodicity 610 may be associated with a minimum periodicity7for monitoring RSs or candidate cells.

[0105] Report periodicity 612 may specify an update to the reporting periodicity for reporting candidate cell RS measurements for use in LTM procedures. In some aspects, the report periodicity 612 may be associated with a maximum report periodicity for reporting candidate cell RS measurements. In some other aspects, the report periodicity 612 may be associated with a minimum report periodicity for reporting candidate cell RS measurements.

[0106] Figure 7 is a block diagram illustrating example MAC CE data 702 for UE requested change in a candidate cell monitoring configuration. In some aspects, the MAC CE data 702 includes one or more of an LTM configuration ID 704, indicators 706, candidate cell list 708, candidate cell RS list 709, number of monitored candidate cells 710, number of monitored RSs 711, monitoring periodicity 712. and report periodicity 714.

[0107] LTM configuration ID 704 identifies the candidate cell monitoring configuration that is to be updated.

[0108] Candidate cell list 708 may specify a list of candidate cells that may be monitored. The list may contain both active and inactive candidate cells. The updated list may contain fewer or more candidate cells than in the current candidate cell monitoring configuration. In some aspects, the candidate cell list 708 may specify an updated list of candidate cell IDs for monitoring. In some other aspects, the candidate cell list 708 may specify an updated list of candidate cells indexes.

[0109] Candidate cell RS list 709 may specify a list of candidate cell RSs that may be monitored. The list may contain RSs that are active and inactive. The updated list may contain fewer or more RSs than in the current candidate cell monitoring configuration. In some aspects, the candidate cell RS list 709 may specify an updated list of RS indexes. For example, the updated list of RS indexes may include an updated list of SSB indexes or CSI-RS indexes.[HO] Indicators 706 may include cell activation / deactivation indicators and RS activation / deactivation indicators. The indicators may be bit fields, where a position of a bit inthe bit field corresponds to a position of a candidate cell in the candidate cell list 708 or a position of an RS in the candidate cell RS list 709. The value of the bit may indicate whether the corresponding cell or RS is active or inactive.[Hl] Number of monitored candidate cells 710 may specify an update to the number of candidate cells that the UE can monitor. In some aspects, the number of monitored candidate cells 710 may be associated with a maximum number of monitored candidate cells. In some other aspects, the number of monitored candidate cells 710 may be associated with a minimum number of monitored candidate cells.

[0112] Number of monitored RSs 711 may specify an update to the number of candidate cell RSs that the UE can monitor. In some aspects, the number of monitored RSs 711 may be associated with a maximum number of monitored RSs per candidate cell or across all candidate cells. In some other aspects, the number of monitored RSs 71 1 may be associated with a minimum number of monitored RSs per candidate cell or across all candidate cells.

[0113] Monitoring periodicity 712 may specify an update to the monitoring periodicity for monitoring RSs or candidate cells. In some aspects, the monitoring periodicity 712 may be associated with a maximum periodicity for monitoring RSs or candidate cells. In some other aspects, the monitoring periodicity 712 may be associated with a minimum periodicity for monitoring RSs or candidate cells.

[0114] Report periodicity 714 may specify an update to the reporting periodicity for reporting candidate cell RS measurements for use in LTM procedures. In some aspects, the report periodicity 714 may be associated with a maximum report periodicity for reporting candidate cell RS measurements. In some other aspects, the report periodicity 714 may be associated with a minimum report periodicity for reporting candidate cell RS measurements.

[0115] Not all fields may be used depending on the type of update being performed. For example, if the MAC CE is used to activate or deactivate candidate cells for monitoring, fields related to RSs are not used. In such cases, the unused fields may be filled with a reserved bit sequence.

[0116] Figure 8 is a block diagram illustrating example configurations of a network entity 120 and a UE 110. Network entity 120 may be an implementation of any network entities 120A and 120B. Note that the depicted hardware configurations represent the processing components and communication components related to UE requested candidate cell configuration updates. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like.

[0117] The UE 110 includes antennas 802, a radio frequency front end (RF front end) 804, and radio-frequency transceivers (e.g., an LTE transceiver 806 and a 5G NR transceiver 808) for communicating with network entity 120, one or more TRPs, and / or one or more radio units (e.g., radio units 121A-121D of Figures 1A and IB).

[0118] The RF front end 804 includes one or more modems configured for the corresponding RAT(s) employed (for example, 3GPP 5G NR). one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs). signal processors, and the like. In the example illustrated in Figure 8, the RF front end 804 of the UE 110 may couple or connect the LTE transceiver 806, and the 5G NR transceiver 808 to the antennas 802 to facilitate various types of wireless communication. The RF front end 804 operates, in effect, as a physical (PHY) transceiver interface to conduct and process signaling between the one or more processors 814 and the antennas 802 so as to facilitate various types of wireless communication.

[0119] The antennas 802 of the UE 110 may include an array of multiple antennas that may be tuned to one or more frequency bands associated with a corresponding RAT. The antennas 802 and the RF front end 804 may be tuned to, and / or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 806, and / or the 5G NR transceiver 808. Additionally, the antennas 802, the RF front end 804, the LTE transceiver 806, and / or the 5G NR transceiver 808 may be configured to support beamforming for the transmission and reception of communications with the network entity 120, one or more TRPs, or one or more radio units (e.g., radio units 121A-121D of Figures 1A and IB). By way of example and not limitation, the antennas 802 and the RF front end 804 may be implemented for operation in sub-gigahertz bands, sub-6 GHz bands, and / or above 6 GHz bands that are defined by the 3 GPP LTE and 5G NR communication standards.

[0120] The UE 110 also includes processors) 814 and computer-readable storage media (CRM) 816. The processor(s) 814 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 814 may include an application processor (AP) utilized by the UE 1 10 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 804.

[0121] CRM 816 may include any suitable memory or storage device such as randomaccess memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory' (ROM), Flash memory, solid-state drive (SSD) or other mass-storage devices, and the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processors 814 and other components of the UE 110 to perform the various functions described herein and attributed to the UE 110. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 814 to enable user-plane communication, control-plane signaling, and user interaction with the UE 110. The data 818 stored in the CRM 816 represents, for example, user data, multimedia data, beamforming codebooks, software application configuration information, and the like.

[0122] Data 818 may include candidate cell monitoring configuration 819. Candidate cell monitoring configuration 819 may include a set of active candidate cells, and / or a set of RSs to be used for monitoring active candidate cells. In some aspects, the candidate cell monitoring configuration 819 may also include a monitoring periodicity, an indication of one or more rules to use for updating a candidate cell monitoring configuration, a first time period after which the UE should autonomously update the candidate cell monitoring configuration, and / or a second time period after which the UE will update the candidate cell monitoring configuration after receipt from the network entity of a confirmation a request to update the candidate cell monitoring configuration.

[0123] CRM 816 also includes a communications controller 822. Alternatively or additionally, the communications controller 822 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE 110. In some aspects, communications controller 822 configures the RF front end 804, the LTE transceiver 806, and / or the 5G NR transceiver 808 to implement the techniques described herein for UE requested candidate cell configuration updates.

[0124] The processor(s) 814 along with other processors of the UE 110 that are used to implement the techniques described herein may be individually or collectively referred to as “a processing system." One or more of RF front end 804, LTE transceiver 806, and 5G NR transceiver 808 may be individually or collectively referred to as a “communication unit.”

[0125] Turning to the hardw are configuration of the network entity 120, it is noted that although Figure 8 illustrates an implementation of the network entity 120 as a single network node (for example, a 5G NR Node B, or “gNB”), the functionality, and thus the hardware components, of the network entity 120 instead may be distributed across multiple netw ork nodes or devices and may be distributed in a manner to perform the functions described herein.As one example, the functionality (and hardware components) of network entity 120 may be distributed across a radio unit (RU), distributed unit (DU), or central unit (CU).

[0126] The network entity 120 includes antennas 852, a radio frequency front end (RF front end) 854, one or more LTE transceivers 856, and / or one or more 5GNR transceivers 858 for communicating with the UE 110. The RF front end 854 of the network entity7120 may couple or connect the LTE transceivers 856 and the 5G NR transceivers 858 to the antennas 852 to facilitate various types of wireless communication. Similar to RF front end 804. the RF front end 854 includes one or more modems, one or more ADCs, one or more DACs, and the like. RF front end 854 receives the one or more RF signals, for example, RF signals from UE 110, and pre-processes the one or more RF signals to generate data from the RF signals that is provided as input to processes and / or applications executing on network entity 120. This preprocessing may include, for example, power amplification, conversion of band-pass signaling to baseband signaling, initial analog-to-digital conversion, and the like.

[0127] The antennas 852 of the network entity 120 may be configured individually and / or as one or more arrays of multiple antennas. The antennas 852 and the RF front end 854 may be tuned to, and / or be tunable to, one or more frequency band defined by the 3GPP LTE and 5G NR communication standards, and implemented by the LTE transceivers 856, and / or the 5G NR transceivers 858. Additionally, the antennas 852, the RF front end 854, the LTE transceivers 856, and / or the 5G NR transceivers 858 may be configured to support beamforming, such as Massive-MIMO, for the transmission and reception of communications wi th the UE 110.

[0128] The network entity' 120 also includes processor(s) 860 and computer-readable storage media (CRM) 862. The processor(s) 860 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 860 may include an application processor (AP) utilized by the network entity 120 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 854 to enable communication with the UE 110.

[0129] CRM 862 may include any suitable memory or storage device such as randomaccess memory7(RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory' (ROM), or Flash memory' usable to store device data of the network entity 120. The device data may include data 864, which includes network scheduling data, radio resource management data, beamforming codebooks, software application configuration information, UE transmitter power levels, and / or TRP configuration data and the like.

[0130] Data 864 may further include candidate cell monitoring configuration 819. Candidate cell monitoring configuration 819 may include a set of active candidate cells, and / or a set of RSs to be used for monitoring active candidate cells. In some aspects, the candidate cell monitoring configuration 819 may also include one or more of a monitoring periodicity, an indication of one or more rules to use for updating a candidate cell monitoring configuration, a first time period after which the UE should autonomously update the candidate cell monitoring configuration, and / or a second time period after which the UE will update the candidate cell monitoring configuration after receipt from the network entity of a confirmation a request to update the candidate cell monitoring configuration.

[0131] CRM 862 additionally includes a communications controller 871. Alternately or additionally, the communications controller 871 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the network entity 120. Like communications controller 822 of UE 110, communications controller 871 configures the RF front end 854, the LTE transceiver 856, and / or the 5G NR transceiver 858 to implement the techniques described herein for UE requested candidate cell configuration updates.

[0132] CRM 862 also includes an RF resource manager 865. In some aspects, the RF resource manager 865 of the network entity 120 is implemented to perform various functions associated with allocating physical access (for example, resource blocks) or communication resources for the air interface of the network entity 120. The air interface of the network entity 120, may be partitioned or divided into various units (for example, frames, subframes, or slots) of one or more of bandwidth, time, symbols, or spatial layers. For example, within a framework of a 5GNR protocol, the RF resource manager 865 may allocate bandwidth and time intervals of access in resource blocks, each of which may be allocated in whole, or in part, to one or more channels for communicating with the UE 1 10. The channels may include one or more of a PRACH, a PUCCH, a PUSCH, a PDCCH, a PDSCH, a PBCH, or a paging channel. The resource blocks may include multiple subcarriers that each span a portion of a frequency domain of the resource blocks. The subcarriers may be further divided into resource elements, or orthogonal frequency-division multiplexing (OFDM) symbols, that each span a portion of a time domain of the subcarriers. Consequently, a resource block includes multiple OFDM symbols that may be grouped into subcarriers with other OFDM symbols having a common frequency bandwidth. In some aspects, the OFDM symbols may be Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) symbols. In some other aspects, the OFDM symbols may be Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) symbols.

[0133] CRM 862 further includes network entity manager 866. Alternately or additionally, the network entity manager 866 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the network entity 120. In at least some aspects, the network entity manager 866 configures the LTE transceivers 856 and the 5G NR transceivers 858 for communication with the UE 110, TRPs, and radio units (e.g., radio units 121A-121D of Figures 1A and IB) via fronthaul interface 867, as well as communication with a core network.

[0134] In some aspects, the network entity 120 includes an inter-network entity interface 868, such as an Xn and / or X2 interface, which the network entity manager 866 configures to exchange user-plane and control-plane data with another network entity, to manage the communication of the network entity 120 with the UE 110. The network entity 120 includes a core network interface 870 that the network entity manager 866 configures to exchange userplane and control-plane data with core network functions and entities.

[0135] The processor(s) 860 along with other processors of the network entity 120 that are used to implement the techniques described herein may be individually or collectively referred to as “a processing system.” One or more of RF front end 854, 5G NR transceiver(s) 858, fronthaul interface 867, inter-network entity interface 868, and core network interface 870 may be individually or collectively referred to as a “communication unit.”

[0136] Figures 1 A, IB, 2, 3A-3D and 4-9 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims. Some implementations might include additional operations, fewer operations, operations in parallel or in a different order, and some operations differently. Alternatively, or in addition to the other examples described herein, examples include any combination of the following implementation options (enumerated as clauses for reference).

[0137] Clause 1. A method for wireless communications by a user equipment (UE), comprising: receiving, from a network entity, a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters; selecting one or more candidate cell monitoring parameters of the plurality of candidate cell monitoring parameters for modification based on a condition of the UE; and transmitting, to the network entity, a request to update the one or more of the candidate cell monitoring parameters.

[0138] Clause 2. The method of clause 1, further comprising: detecting the condition of the UE, wherein the condition includes at least one of: a battery charge level below a firstthreshold level a change in a battery charge state, a change in a location of the UE, or a thermal level above a second threshold level; and transmitting the request based on the condition.

[0139] Clause 3. The method of any of clauses 1 or 2, further comprising: detecting the condition based on an output of a machine learning model using history' information as input.

[0140] Clause 4. The method of clause 3, wherein the history information includes at least one of: first history information collected by the UE; second history information received from the network entity; or third history information obtained from an application service provider.

[0141] Clause 5. The method of any of clauses 3 or 4, wherein the selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on the output of the machine learning model.

[0142] Clause 6. The method of any of clauses 1-5, wherein the one or more candidate cell monitoring parameters include at least one of: monitored candidate cells; a number of the monitored candidate cells; monitored reference signals associated with one or more first candidate cells; a number of the monitored reference signals associated with one or more second candidate cells; a monitoring periodicity associated with one or more third candidate cells; or a reporting periodicity' associated with one or more fourth candidate cells.

[0143] Clause 7. The method of any' of clauses 1-6, wherein the candidate cell monitoring configuration is associated with at least one of: one or more non-serving cells; one or more deactivated cells; or one or more layer 1 or 2 triggered mobility (LTM) candidate cells.

[0144] Clause 8. The method of any of clauses 1-7. wherein the selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on a rule or a machine learning model.

[0145] Clause 9. The method of clause 8, wherein the UE selects the one or more candidate cell monitoring parameters based on a same rule as the network entity.

[0146] Clause 10. The method of any of clauses 1 -9, wherein the selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on a reference signal received power (RSRP) associated with the one or more candidate cell monitoring parameters.

[0147] Clause 11. The method of any of clauses 1-10, wherein the transmitting the request to update the candidate cell monitoring configuration includes transmitting the request in at least one of: a radio resource control (RRC) message, a user assistant information (UAI), an uplink (UL) medium access control (MAC) control element (CE), or uplink control information (UCI).

[0148] Clause 12. The method of clause 1 1, further comprising: transmitting, to the network entity', a scheduling request; and receiving, from the network entity', an UL grantresponsive to the scheduling request, wherein the transmitting the request to update includes transmitting the UL MAC CE based on the UL grant.

[0149] Clause 13. The method of clause 1 1, wherein the transmitting the request to update includes transmitting the request via at least one of: a random access preamble on a random access channel (RACH), a random access request on a physical uplink shared channel (PUSCH), or a random access message that includes both the random access preamble and the random access request.

[0150] Clause 14. The method of any of clauses 1 1-13, wherein the UL MAC CE includes a first request type indicating the candidate cell monitoring configuration is to be updated.

[0151] Clause 15. The method of any of clauses 11-14, wherein the UL MAC CE includes at least one of: a configuration identifier (ID) identifying the candidate cell monitoring configuration being modified; one or more candidate cell IDs; one or more reference signal IDs; one or more reference signal monitoring periodicities; one or more activation indicators; or one or more deactivation indicators.

[0152] Clause 16. The method of any of clauses 11-15, wherein the UL MAC CE includes a second request type indicating a type of update to the candidate cell monitoring configuration.

[0153] Clause 17. The method of clause 16, wherein the type of update to the candidate cell monitoring configuration indicates at least one of: a candidate cell activation; a candidate cell deactivation; a reference signal (RS) activation; an RS deactivation;

[0154] an RS monitoring periodicity update; or a reporting periodicity update.

[0155] Clause 18. The method of any of clauses 16 or 17, wherein a MAC CE subheader is based on the second request type of the UL MAC CE.

[0156] Clause 19. The method of clause 18, wherein a logical channel ID (LCID) of the MAC CE subheader is based on the second request type of the UL MAC CE.

[0157] Clause 20. The method of clause 1 1, further comprising receiving a plurality' of reference signals associated with the candidate cell monitoring configuration, wherein the UCI comprises a layer 1 (LI) measurement report based on the plurality of reference signals.

[0158] Clause 21. The method of clause 20, wherein a predetermined value for a reference signal (RS) in the LI measurement report indicates a request to deactivate the RS.

[0159] Clause 22. The method of clause 21, wherein the predetermined value comprises an out-of-range indicator for a measurement associated with the RS.

[0160] Clause 23. The method of clause 22, wherein the out-of-range indicator for the measurement associated with each RS of a candidate cell indicates a request for deactivating the candidate cell.

[0161] Clause 24. The method of clause 20, wherein each RS of a candidate cell has an indicator indicating that a measurement is below a threshold value indicates a request for deactivating the candidate cell.

[0162] Clause 25. The method of any of clauses 1-24, further comprising at least one of: updating the candidate cell monitoring configuration after a first predetermined time period has elapsed after transmitting the request; updating the candidate cell monitoring configuration after a second predetermined time period has elapsed after transmitting the request a consecutive number of rimes; updating the candidate cell monitoring configuration after a third predetermined time period has elapsed after transmitting the request a predetermined number of times within a time interval; or updating the candidate cell monitoring configuration after a fourth predetermined time period has elapsed after receiving a response to the request to update the candidate cell monitoring configuration.

[0163] Clause 26. The method of any of clauses 1-25, further comprising: receiving one or more reference signals from one or more candidate cells associated with the candidate cell monitoring configuration; and calculating one or more modifications to the one or more candidate cell monitoring parameters based on the one or more reference signals.

[0164] Clause 27. A method for wireless communications by a first network entity, comprising: transmitting, to a user equipment (UE), a candidate cell monitoring configuration, the candidate cell monitoring configuration specifying one or more candidate cells; receiving, from the UE, a request to update one or more candidate cell monitonng parameters of the candidate cell monitoring configuration; and transmitting an indicator to a second network entity operating at least one candidate cell of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.

[0165] Clause 28. The method of clause 27, further comprising transmitting, to the UE, a response to the request to update the one or more candidate cell monitoring parameters.

[0166] Clause 29. The method of clause 28, wherein the request to update the one or more candidate cell monitoring parameters is included in a physical uplink shared channel (PUSCH), and the method further comprising: transmitting, to the UE, an uplink (UL) grant having a same hybrid automatic repeat request (HARQ) process identifier (ID) as the PUSCH.

[0167] Clause 30. The method of clause 28, wherein the transmitting the response includes transmitting at least one of: a radio resource control (RRC) reconfiguration message; a media access control (MAC) control element (CE); a downlink control information (DCI); or an acknowledgment message.

[0168] Clause 31. The method of clause 27, wherein the indicator indicating the modification of resources comprises an indicator to release resources reserved for the UE for cell switching.

[0169] Clause 32. A user equipment (UE) comprising: a wireless transceiver; at least one processor; and instructions for a communications controller that, when executed by the at least one processor, configure the UE to: receive, via the wireless transceiver from a network entity, a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters;

[0170] select one or more of candidate cell monitoring parameters of the plurality' of candidate cell monitoring parameters for modification based on a condition of the UE; and transmit, via the wireless transceiver to the network entity, a request to update the one or more of the candidate cell monitoring parameters.

[0171] Clause 33. The UE of clause 32, wherein the instructions further include instructions to configure the UE to: detect the condition of the UE, wherein the condition includes at least one of: a battery charge level below a first threshold level, a change in a battery charge state, a change in a location of the UE, or a thermal level above a second threshold level; and transmit the request based on the condition.

[0172] Clause 34. The UE of any of clauses 32 or 33, wherein the instructions further include instructions to configure the UE to: detect the condition based on an output of a machine learning model using history information as input.

[0173] Clause 35. The UE of clause 34, wherein the history information includes at least one of: first history' information collected by the UE; second history' information received from the network entity; or third history information obtained from an application service provider.

[0174] Clause 36. The UE of any of clauses 34 or 35, wherein the instructions to configure the UE to select the one or more candidate cell monitoring parameters include instructions to configure the UE to select the one or more candidate cell monitoring parameters based on the output of the machine learning model.

[0175] Clause 37. The UE of any of clauses 32-36, wherein the one or more candidate cell monitoring parameters include at least one of: monitored candidate cells; a number of the monitored candidate cells; monitored reference signals associated with one or more first candidate cells; a number of the monitored reference signals associated with one or more second candidate cells; a monitoring periodicity associated with one or more third candidate cells; or a reporting periodicity’ associated with one or more fourth candidate cells.

[0176] Clause 38. The UE of any of clauses 32-37, wherein the candidate cell monitoring configuration is associated with at least one of: one or more non-serving cells; one or more deactivated cells; or one or more layer 1 or 2 triggered mobility (LTM) candidate cells.

[0177] Clause 39. The UE of any of clauses 32-38, wherein the instructions to configure the UE to select the one or more candidate cell monitoring parameters include instructions to configure the UE to select the one or more candidate cell monitoring parameters based on a rule or a machine learning model.

[0178] Clause 40. The UE of clause 39, wherein the UE selects the one or more candidate cell monitoring parameters based on a same rule as the network entity.

[0179] Clause 41. The UE of any of clauses 32-40. wherein the instructions to configure the UE to select the one or more candidate cell monitoring parameters include instructions to configure the UE to select the one or more candidate cell monitoring parameters based on a reference signal received powder (RSRP) associated with the one or more candidate cell monitoring parameters.

[0180] Clause 42. The UE of any of clauses 32-41. wherein the instructions to configure the UE to transmit the request to update the candidate cell monitoring configuration include instructions to configure the UE to transmit the request in at least one of: a radio resource control (RRC) message, a user assistant information (UAI), an uplink (UL) medium access control (MAC) control element (CE), or uplink control information (UCI).

[0181] Clause 43. The UE of clause 42, wherein the instructions further include instructions to configure the UE to: transmit, to the network entity, a scheduling request; and receive, from the network entity, an UL grant responsive to the scheduling request, wherein the transmitting the request to update includes transmitting the UL MAC CE via the UL grant.

[0182] Clause 44. The UE of clause 42, wherein the instructions to transmit the request to update include instructions to transmit the request to update via at least one of: a random access preamble on a random access channel (RACK), a random access request on a physical uplink shared channel (PUSCH), or a random access message that includes both the random access preamble and the random access request.

[0183] Clause 45. The UE of any of clauses 42-44, wherein the UL MAC CE includes a first request type indicating the candidate cell monitoring configuration is to be updated.

[0184] Clause 46. The UE of any of clauses 42-45, wherein the UL MAC CE includes at least one of: a configuration identifier (ID) identifying the candidate cell monitoring configuration being modified; one or more candidate cell IDs; one or more reference signal IDs; one or more reference signal monitoring periodicities; one or more activation indicators; or one or more deactivation indicators.

[0185] Clause 47. The UE of any of clauses 32-46, wherein the UL MAC CE includes a second request type indicating a type of update to the candidate cell monitoring configuration.

[0186] Clause 48. The UE of clause 47, wherein the type of update to the candidate cell monitoring configuration indicates at least one of: a candidate cell activation; a candidate cell deactivation; a reference signal (RS) activation; an RS deactivation; or an RS monitoring periodicity update; or a reporting periodicity update.

[0187] Clause 49. The UE of any of clauses 47 or 48. wherein a MAC CE subheader is based on the second request type of the UL MAC CE.

[0188] Clause 50. The UE of clause 49, wherein a logical channel ID (LCID) of the MAC CE subheader is based on the second request type of the UL MAC CE.

[0189] Clause 51. The UE of clause 42, wherein the instructions further include instructions to configure the UE to receive a plurality of reference signals associated with the candidate cell monitoring configuration, wherein the UCI comprises a layer 1 (LI) measurement report based on the plurality of reference signals.

[0190] Clause 52. The UE of clause 51, wherein a predetermined value for a reference signal (RS) in the LI measurement report indicates a request to deactivate the RS.

[0191] Clause 53. The UE of clause 52, wherein the predetermined value comprises an out- of-range indicator for a measurement associated with the RS.

[0192] Clause 54. The UE of clause 53, wherein the out-of-range indicator for the measurement associated with each RS of a candidate cell indicates a request for deactivating the candidate cell.

[0193] Clause 55. The UE of clause 51, wherein each RS of a candidate cell has an indicator indicating that a measurement is below a threshold value indicates a request for deactivating the candidate cell.

[0194] Clause 56. The UE of any of clauses 32-55, wherein the instructions further include instructions to configure the UE to perform at least one of: update the candidate cell monitoring configuration after a first predetermined time period has elapsed after transmitting the request; update the candidate cell monitoring configuration after a second predetermined time period has elapsed after transmitting the request a consecutive number of times; update the candidate cell monitoring configuration after a third predetermined time period has elapsed after transmitting the request a predetermined number of times within a time interval; or update the candidate cell monitoring configuration after a fourth predetermined time period has elapsed after receiving a response to the request to update the candidate cell monitoring configuration.

[0195] Clause 57. The UE of any of clauses 32-56, wherein the instructions further include instructions to configure the UE to: receive one or more reference signals from one or morecandidate cells associated with the candidate cell monitoring configuration; and calculate one or more modifications to the one or more candidate cell monitoring parameters based on the one or more reference signals.

[0196] Clause 58. A first network entity comprising: a wireless transceiver; at least one processor; and instructions for a communications controller that, when executed by the at least one processor, configure the first network entity to: transmit, to a user equipment (UE), a candidate cell monitoring configuration, the candidate cell monitonng configuration specifying one or more candidate cells; receive, from the UE, a request to update one or more candidate cell monitoring parameters of the candidate cell monitoring configuration; and transmit an indicator to a second network entity operating at least one candidate cell of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.

[0197] Clause 59. The first network entity of clause 58, wherein the instructions further include instructions to configure the first network entity to transmit, to the UE, a response to the request to update the one or more candidate cell monitoring parameters.

[0198] Clause 60. The first network entity’ of clause 59, wherein the request to update the one or more candidate cell monitoring parameters is included in a physical uplink shared channel (PUSCH), and the instructions further include instructions to configure the first network entity to: transmit, to the UE, an uplink (UL) grant having a same hybrid automatic repeat request (HARQ) process identifier (ID) as the PUSCH.

[0199] Clause 61. The first network entity of clause 59, wherein the instructions to configure the first network entity to transmit the response include instructions to configure the first network entity to transmit at least one of: a radio resource control (RRC) reconfiguration message; a media access control (MAC) control element (CE); a downlink control information (DCI); or an acknowledgment message.

[0200] Clause 62. An apparatus comprising: a communication controller; and a processing system configured to control the communication controller to implement any one of the methods of clauses 1-31.

[0201]

[0202] It is noted that throughout this disclosure, an expression of “X / Y” may include meaning of “X or Y”. It is noted that throughout this disclosure, an expression of “X / Y” may include meaning of “X and Y”. It is noted that throughout this disclosure, an expression of “X / Y” may include meaning of “X and / or Y”. It is noted that throughout this disclosure, an expression of “(A) B” or “B (A)” may include concept of “only B”. It is noted that throughout this disclosure, an expression of “(A) B” or “B (A)” may include concept of “A+B” or “B+A”.

[0203] It is noted that some or all of the foregoing or the following implementations can be jointly combined or formed to be a new or another one implementation.

[0204] It is noted that the foregoing or the following techniques can be used to solve at least (but not limited to) the issue(s) or scenario(s) mentioned in this disclosure.

[0205] The following additional considerations may apply to the foregoing and the following discussions.

[0206] It is noted that any two or more than two of the foregoing or the following paragraphs, (sub)-bullets, points, actions, or claims described in each method / technique / implementation may be combined logically, reasonably, and properly to form a specific method.

[0207] It is noted that any sentence, paragraph, (sub)-bullet, point, action, or claim described in each of the foregoing or the following technique(s) / implementation(s) / concept(s) may be implemented independently and separately to form a specific method. Dependency, such as “based on”, “more specifically”, “where” or etc., in technique(s) / implementation(s) / concept(s) mentioned in this disclosure is just one possible implementation which would not restrict the specific method.

[0208] Certain techniques are described in this disclosure as including logic or a number of components or modules. Modules may be software modules (such as code stored on non- transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (such as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (for example, as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (for example, configured by software) may be driven by cost and time considerations.

[0209] As used herein, the terms “component” and “module” are intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on.”

[0002] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than orequal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0211] As used herein, a phrase referring to "at least one of’ or "one or more of’ a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c. and a combination of a and b and c.

[0212] In this disclosure, the term "can" indicates a capability, or alternatively indicates a possible implementation option. The term "may" indicates a permission or a possible implementation option.

[0213] The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.

[0214] The hardware and data processing apparatus used to implement the various illustrative components, logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes, operations and methods may be performed by circuitry that is specific to a given function.

[0215] As described above, in some aspects implementations of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process oralgorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor- or computer-executable instructions encoded on one or more tangible processor- or computer- readable storage media for execution by, or to control the operation of, data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media. When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0216] As used herein, the terms “user device'’, “user equipment” (for example, UE 110), “wireless communication device”, “mobile communication device”, “communication device”, or “mobile device” refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, Intemet-of-Things (loT) devices, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, display sub-systems, driver assistance systems, vehicle controllers, vehicle system controllers, vehicle communication system, infotainment systems, vehicle telematics systems or subsystems, vehicle display systems or subsystems, vehicle data controllers, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media-streaming dongles or another personal media devices, wearable devices such as smartwatches, wireless hotspots, femtocells, broadband routers or other types of routers, and similar electronic devices which include a programmable processor and memory and circuitry configured to perform operations as described herein. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, a mobile-internet device (MID). Depending on the A pe, the user device can include one or more general-purpose processors, a computer-readable memory. a user interface, one or more netw ork interfaces, one or more sensors, etc.

[0217] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shownherein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0218] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0219] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0220] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes.

Claims

CLAIMSWhat is claimed is:

1. A method for wireless communications by a user equipment (UE) (110A), comprising: receiving (202), from a network entity (120 A), a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters; selecting (208) one or more candidate cell monitoring parameters of the plurality of candidate cell monitoring parameters for modification based on a condition of the UE; and transmitting (210), to the network entity, a request to update the one or more of the candidate cell monitoring parameters.

2. The method of claim 1 , further comprising: detecting the condition of the UE, the condition including at least one of: a battery charge level below a first threshold level. a change in a battery charge state, a change in a location of the UE, or a thermal level above a second threshold level; and wherein the transmitting the request is based on the condition.

3. The method of any of claims 1 or 2, wherein the one or more candidate cell monitoring parameters include at least one of: monitored candidate cells; a number of the monitored candidate cells; monitored reference signals associated with one or more first candidate cells; a number of the monitored reference signals associated with one or more second candidate cells; a monitoring periodicity associated with one or more third candidate cells; or a reporting periodicity associated with one or more fourth candidate cells.

4. The method of any of claims 1-3, wherein the candidate cell monitoring configuration is associated with at least one of: one or more non-serving cells; one or more deactivated cells; or one or more layer 1 or 2 triggered mobility (LTM) candidate cells.

5. The method of any of claims 1-4, wherein the selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on a rule or a machine learning model.

6. The method of any of claims 1-5, wherein the selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on a reference signal received power (RSRP) associated with the one or more candidate cell monitoring parameters.

7. The method of any of claims 1-6. wherein the transmitting the request to update the candidate cell monitoring configuration includes transmitting the request in at least one of: a radio resource control (RRC) message, a user assistance information (UAI), an uplink (UL) medium access control (MAC) control element (CE), or uplink control information (UCI).

8. The method of claim 7, further comprising: transmitting, to the network entity, a scheduling request; and receiving, from the network entity, an UL grant responsive to the scheduling request, wherein the transmitting the request to update includes transmitting the UL MAC CE based on the UL grant.

9. The method of claim 7, wherein the transmitting the request to update includes transmitting the request via at least one of: a random access preamble on a physical random access channel (PRACH), a random access request on a physical uplink shared channel (PUSCH). or a random access message that includes both the random access preamble and the random access request.

10. The method of any of claims 7-9, wherein the UL MAC CE includes at least one of: a first request type indicating the candidate cell monitoring configuration is to be updated; a second request type indicating a type of update to the candidate cell monitoring configuration; a configuration identifier (ID) identifying the candidate cell monitoring configuration being modified; one or more candidate cell IDs;one or more reference signal IDs; one or more reference signal monitoring periodicities; one or more activation indicators; or one or more deactivation indicators.

11. The method of claim 10. wherein the type of update to the candidate cell monitoring configuration indicates at least one of: a candidate cell activation; a candidate cell deactivation; a reference signal (RS) activation; an RS deactivation; an RS monitoring periodicity update; or a reporting periodicity update.

12. The method of any of claims 10 or 11, wherein a MAC CE subheader is based on the second request type of the UL MAC CE.

13. The method of claim 12, wherein a logical channel ID (LCID) of the MAC CE subheader is based on the second request type of the UL MAC CE.

14. The method of claim 7, further comprising receiving a plurality of reference signals associated with the candidate cell monitoring configuration, wherein the UCI comprises a layer 1 (LI) measurement report based on the plurality of reference signals.

15. The method of any of claims 1-14, further comprising at least one of: updating the candidate cell monitoring configuration after a first predetermined time period has elapsed after transmitting the request; updating the candidate cell monitoring configuration after a second predetermined time period has elapsed after transmitting the request a consecutive number of times; updating the candidate cell monitoring configuration after a third predetermined time period has elapsed after transmitting the request a predetermined number of times within a time interval; or updating the candidate cell monitoring configuration after a fourth predetermined time period has elapsed after receiving a response to the request to update the candidate cell monitoring configuration.

16. The method of any of claims 1-15, further comprising: receiving one or more reference signals from one or more candidate cells associated with the candidate cell monitoring configuration; and calculating one or more modifications to the one or more candidate cell monitoring parameters based on the one or more reference signals.

17. A method for wireless communications by a first network entity ( 120A), comprising: transmitting (202), to a user equipment (UE) (110A), a candidate cell monitoring configuration, the candidate cell monitoring configuration specifying one or more candidate cells; receiving (208), from the UE, a request to update one or more candidate cell monitoring parameters of the candidate cell monitoring configuration; and transmitting (214) an indicator to a second network entity (120B) operating at least one candidate cell of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.

18. The method of claim 17, further comprising transmitting (212), to the UE, a response to the request to update the one or more candidate cell monitoring parameters, wherein the response includes at least one of: a radio resource control (RRC) reconfiguration message; a media access control (MAC) control element (CE); a downlink control information (DCI); or an acknowledgment message.

19. The method of claim 17, wherein the indicator indicating the modification of resources comprises an indicator to release resources reserved for the UE for cell switching.

20. An apparatus comprising: a communication controller; and a processing system configured to control the communication controller to implement any one of the methods of claims 1-19.

Images