Candidate cell configuration update requested by the ue

Abstract

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

Description

[0001] Related applications

[0002] This application claims priority to U.S. Provisional Patent Application Serial No. 63 / 599,702, filed November 16, 2023, entitled “UE REQUESTED CANDIDATE CELLCONFIGURATION UPDATE,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications and techniques for updating user equipment requests for candidate cell configuration. Background Technology

[0004] A radio access network (RAN) has multiple cells, each containing at least one network element. Each cell can be associated with a network entity, radio unit, transmit-receive point (TRP) of the network entity, base station, component carrier, etc. To utilize the RAN to communicate with other devices or other network entities, a user equipment (UE) connects to the network element of the cell. The cell with the network element connected to the UE is called the "serving cell." If the communication quality within the serving cell becomes insufficient, or if another cell can provide better communication quality, there may be other cells adjacent to or near the serving cell that the UE can connect to. The network element can configure the UE to have information about some or all of these other cells, which may be referred to as "candidate cells," "target cells," "non-serving cells," "neighboring cells," etc.

[0005] The UE may be able to support Layer 1 / 2 (L1 / L2) triggered mobility (LTM) (also known as lower-layer triggered mobility). In LTM, the UE monitors candidate cells by periodically measuring reference signals received from them and reporting such measurements to network entities in the serving cell. LTM allows the UE and network entities to provide seamless handover between different cells when necessary and can reduce higher-layer (e.g., Layer 3) message exchange and reconfiguration. In some aspects where cells are associated with component carriers, handover to a different cell may involve switching from one carrier to another in the frequency domain. The LTM process can reduce latency and packet loss, resulting in a better user experience. In some aspects, the UE can perform conditional LTM cell handover. In this case, the UE can be configured to detect one or more specific conditions based on LTM cell reference signal measurements. If the conditions are met, the UE autonomously sends an uplink (UL) transmission to the target cell to initiate the cell handover. 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 to the UE information indicating the target cell to which the UE applies for the cell handover or a cell handover command configured for the target cell. The network entity operating the candidate LTM cell is configured to periodically monitor the reserved resources to detect whether the UE has performed a cell handover to the candidate LTM cell. Summary of the Invention

[0006] The systems, methods, and apparatuses disclosed herein each have several innovative aspects, none of which individually are solely responsible for the desired properties disclosed herein.

[0007] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a user equipment (UE). The method includes: the UE receiving a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters from a network entity. The method further includes: the UE selecting one or more candidate cell monitoring parameters from the plurality of candidate cell monitoring parameters for modification based on conditions of the UE. The method also includes: the UE transmitting a request to the network entity to update one or more candidate cell monitoring parameters from the plurality of candidate cell monitoring parameters.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a network entity. The method includes: the network entity transmitting a candidate cell monitoring configuration to a UE, 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 of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented as a device or system. In some implementations, a device includes a communication unit and a processing system. The processing system is configured to control the communication unit to implement any of the methods described in this document.

[0010] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Attached Figure Description

[0011] It should be noted that the relative dimensions in the following figures may not be drawn to scale. The same reference numerals and names in the various figures indicate the same elements. To facilitate identification of the discussion of any particular element or action, one or more of the most significant digits in the reference numerals refer to the figure number in which that element was first introduced.

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

[0013] Figure 1B This is a diagram illustrating an example radio system following a change in the candidate cell monitoring configuration requested by the UE.

[0014] Figure 2 This is a sequence diagram illustrating an example operation of the communication process for changing the candidate cell monitoring configuration requested by the UE.

[0015] Figure 3A This is a sequence diagram showing the configuration update after receiving the update confirmation.

[0016] Figure 3B This is a sequence diagram showing the configuration update after a predetermined time has elapsed following the update request.

[0017] Figure 3CThis is a timing diagram showing the configuration update after a predetermined number of update requests have been transmitted.

[0018] Figure 3D This is a timing diagram showing the configuration update after a predetermined number of update requests have been transmitted within the update interval.

[0019] Figure 4 This is a flowchart illustrating an example UE operation that demonstrates a method for changing the candidate cell monitoring configuration requested by the UE.

[0020] Figure 5 This is a flowchart illustrating an example network entity operation for a method of changing the candidate cell monitoring configuration requested by a UE.

[0021] Figure 6 This is a block diagram illustrating example user assistance information data for changes in candidate cell monitoring configuration requested by the UE.

[0022] Figure 7 This is a block diagram illustrating example Media Access Control (MAC) control element (CE) data for a change in the candidate cell monitoring configuration requested by the UE.

[0023] Figure 8 This is a block diagram showing an example configuration of network entities and UEs. Detailed Implementation

[0024] For the purpose of describing the innovative aspects of this disclosure, the following description relates to certain implementations. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some examples in this disclosure are based on wireless communications according to 3GPP wireless standards such as the 4th generation (4G) Long Term Evolution (LTE) standard and the 5th generation (5G) New Radio (NR) standard. However, the described implementations can be implemented in any apparatus, system, or network capable of transmitting and receiving radio frequency signals or other known signals according to any of the wireless communication standards (including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.15, or 802.16 wireless standards) for transmission within wireless, cellular, or Internet of Things (IoT) networks such as systems utilizing 3G, 4G, 5G, 6th generation (6G), WiFi, or future radio technologies.

[0025] A radio access network (RAN) has multiple cells, each of which includes at least one network element. Each cell can be associated with a network entity, a network entity's transmit-receive point (TRP), radio unit, base station, component carrier, etc. To utilize the RAN to communicate with other devices or other network entities, a user equipment (UE) connects to the network element of a cell. The cell with a network element connected to the UE is called the "serving cell." If the communication quality within the serving cell becomes insufficient, or if another cell can provide better communication quality, there may be other cells adjacent to or near the serving cell with which the UE can establish a connection. The network element can configure the UE to have information about some or all of these other cells, which are called "candidate cells," "target cells," "non-serving cells," "neighboring cells," etc.

[0026] The UE may be able to support Layer 1 / 2 (L1 / L2) triggered mobility (LTM) (also known as lower-layer triggered mobility). In LTM, the UE monitors candidate cells by periodically measuring reference signals received from them and reporting such measurements to network entities in the serving cell. LTM allows the UE and network entities to provide seamless handover between different cells when necessary and can reduce higher-layer (e.g., Layer 3) message exchange and reconfiguration. In some aspects where cells are associated with component carriers, handover to a different cell may involve switching from one carrier to another in the frequency domain. The LTM process can reduce latency and packet loss, resulting in a better user experience. In some aspects, the UE can perform conditional LTM cell handover. In this case, the UE can be configured to detect one or more specific conditions based on LTM cell reference signal measurements. If the conditions are met, the UE autonomously sends an uplink (UL) transmission to the target cell to initiate the cell handover. 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 to the UE information indicating the target cell to which the UE applies for the cell handover or a cell handover command configured for the target cell. The network entity operating the candidate LTM cell is configured to periodically monitor reserved resources to detect whether the UE has performed a cell handover to the candidate LTM cell. Although some examples in this disclosure are based on LTM technology, these concepts can be applied to other types of mobility or cell monitoring procedures.

[0027] For both the UE and the network entity, monitoring candidate cells requires additional resources and consumes more power. This can occur when the UE needs to reduce power consumption, for example, due to low battery or overheating. In such cases, it may be advantageous for the UE to reduce the overhead associated with monitoring candidate cells or to request the network entity to update the candidate cell monitoring configuration based on the UE resources used for candidate cell monitoring.

[0028] This disclosure provides systems, methods, and apparatus for enabling a UE to request updates to a candidate cell monitoring configuration. The UE can request an update based on conditions indicating that candidate cell monitoring resources should be reduced. Such conditions include low battery power, overheating, or a change in the UE's location. In various implementations, among other examples, the UE can also request modifications to the number of candidate cells monitored by the UE, modifications to the number of reference signals associated with candidate cells, or periodic modifications to the monitoring. In some aspects, the UE can receive updates to the candidate cell monitoring configuration from a network entity in response to a request. In some aspects, the UE can autonomously update the candidate cell monitoring configuration after a predetermined time period following the requested update. Additionally, in some implementations, the network entity operating the serving cell can notify the network entity operating the candidate cells of these updates, thereby allowing the network entity operating the candidate cells to release resources associated with providing reference signals to the UE.

[0029] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. When the UE's battery level is low, the UE can reduce power consumption associated with candidate cell monitoring. Furthermore, the UE can reduce the likelihood of overheating caused by processing associated with candidate cell monitoring. Moreover, when the UE is also reducing resources associated with candidate cell monitoring, the network entity operating the candidate cell can reduce resources associated with providing UE-specific reference signals to the UE. For example, the network entity operating the candidate cell can release resources associated with transmitting UE-specific reference signals used by the UE for LTM monitoring. Furthermore, the network entity operating the candidate cell can release resources reserved for detecting uplink transmissions indicating cell handover from the UE.

[0030] Figure 1A This is an illustration of an example wireless communication system 100 including a user equipment (UE) communicating with network entities in the serving cell, wherein the UE is configured to have a candidate cell monitoring configuration. Figure 1AIn the example shown, the wireless communication system 100 includes cells 126A to 126G and various network elements such as network entities 120A and 120B, radio units (RUs) 121A to 121D, and UEs 110A and 110B. Cells (e.g., any of cells 126A to 126G) may be associated with network entities such as base stations, radio units, TRPs, or carrier aggregation components. Cells 126A to 126G may include various types of cells, including macro cells for higher-power network entities and / or small cells for lower-power network entities. Small cells may include femtocells, picocells, microcells, and the like.

[0031] Network entities such as base stations can operate multiple cells. In some traditional deployments, a base station can operate three (3) cells, but other numbers of cells can be deployed at the base station. A primary cell group (MCG) may include the primary cell (PCell) of an eNodeB (eNB, also known as an evolved Node B) and zero or more secondary cells (Scells). A secondary cell group (SCG) may include the primary SCG cell (PSCell) of a gNodeB (gNB) and zero or more secondary cells (SCells). Once an SCG is added to a Radio Resource Control (RRC) configuration, the UE can be in non-standalone (NSA) operating mode. Either a cell within an MCG or an SCG may be referred to as the currently 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.

[0032] Network entities can support carrier aggregation. Carrier aggregation can provide greater network throughput by using multiple frequencies to transmit and receive data in the frequency domain. Each frequency can be referred to as a component carrier. Data transmitted over multiple component carriers (CCs) can be aggregated and delivered to the target device. The first component carrier is associated with the PCell and is used to establish access to the network entity and server, serving as the primary component carrier. Subsequent component carriers are associated with the SCell.

[0033] exist Figure 1A In the example shown, UE 110B has established a connection via radio unit 121B via a component carrier associated with PCell 122. Furthermore, UE 110B can communicate with radio unit 121B using an additional component carrier associated with SCell 123. In this disclosure, PCell and SCell are considered cells, and the techniques described herein can be applied to PCell and SCell.

[0034] exist Figure 1AIn the example shown, UE 110A has established a connection with network entity 120A in cell 126A and is communicating wirelessly with network entity 120A. UE 110A can communicate directly or via one or more TRPs (TRPs). Figure 1A (Not shown in the image) communicates with network entity 120A. A cell associated with a network entity with which the UE has already established a connection can be called a "serving cell". Therefore, in Figure 1A In the example shown, cell 126A can be referred to as the serving cell for UE 110A because UE 110A has already established a connection with network entity 120A in cell 126A.

[0035] Despite Figure 1A While shown as a smartphone, UEs such as UE 110A and / or UE 110B can be implemented as any suitable computing or electronic device, such as mobile communication devices, modems, cellular phones, gaming devices, navigation devices, media devices, laptops, desktop computers, tablets, smart appliances, vehicle-based communication systems, Internet of Things (IoT) devices (e.g., sensor nodes, controller / actuator nodes, combinations thereof), etc. UE 110A can use a wireless link ( Figure 1A (Not shown) to communicate with network entity 120A, these radio links can be implemented as any suitable type of radio link. A radio link may include one or more radio links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or a combination of communication protocols or standards (such as 3GPP LTE, 5G NR, etc.). Multiple radio links can be aggregated in carrier aggregation to provide higher data rates for UE 110.

[0036] As examples, network entities such as network entities 120A and 120B can be base stations, Evolved Universal Terrestrial Radio Access Network Node Bs (E-UTRAN Node Bs), Evolved Node Bs (eNodeBs, eNBs), Next Generation Node Bs (gNodeBs, gNBs), ng-eNBs, access points, radio heads, etc. Network entities can be implemented in macro cells, micro cells, small cells, pico cells, etc., or any combination thereof. Network entities (e.g., network entities 120A or 120B) can be configured to use Multiple-Input Multiple-Output (MIMO) communication to exchange radio signals with UE 110.

[0037] Network entities (e.g., network entity 120A and network entity 120B) use one or more applicable radio access technologies (RATs) specified by one or more communication protocols or standards to support wireless communication with one or more UEs (such as UE 110A and 110B) via radio frequency (RF) signaling. Network entities may employ any of a variety of RATs, such as operating as a Node B (or Base Transceiver Station (BTS)) for a Universal Mobile Telecommunications System (UMTS) RAT (also known as "3G"), operating as an eNB for a 3GPP LTE RAT, operating as a 5G Node B ("gNB") for a 3GPP 5G NR RAT, and similar.

[0038] Network entities 120A and 120B, as well as radio units 121A to 121D, can be part of a RAN, such as an evolved universal terrestrial radio access network, E-UTRAN, 5G NR RAN, or NR RAN. Network entities 120A and 120B can be connected to the core network ( Figure 1A (Not shown in the diagram). For example, when connected to a 5G core network, network entities 120A and 120B can connect to the core network via the NG2 interface for control plane signaling and use the NG3 interface for user plane data communication. When connected to an evolved packet core (EPC) network, network entities 120A and 120B can use the Si interface for control plane signaling and user plane data communication. Network entities 120A and 120B can communicate via the Xn interface using the Xn Application Protocol (XnAP) or via the X2 interface using the X2 Application Protocol (X2AP) to exchange user plane and control plane data. UEs (e.g., UE 110A and / or 110B) can connect to one or more wide area networks (WANs) or other packet data networks (PDNs), such as the Internet, via the core network.

[0039] In some respects, the functionality of network entities, and therefore the hardware components, can be distributed across multiple network nodes or devices, and can be distributed in a manner used to perform the functions described herein. As an example, the functionality of network entity 120 can be distributed across radio units (RUs) (e.g., any of radio units 121A to 121D), distributed units (DUs), or central units (CUs).

[0040] Communication between the network entity and the UE utilizes an uplink (UL) transmission path for RF transmission from the UE to the network entity and a downlink (DL) transmission path for RF transmission from the network entity to the UE. For example, ... Figure 1AAs shown, UE 110A uses UL transmission path 114 for RF transmission from UE 110A to network entity 120A, and uses DL transmission path 112 for RF transmission from network entity 120A to UE 110A. In the context of UL transmission path 114, UE 110A acts as a data transmitter and network entity 120A acts as a data receiver, while in the context of DL transmission path 112, network entity 120A acts as a data transmitter and UE 110A acts as a data receiver. UL transmission path 114 and DL transmission path 112 can utilize multiple communication channels for signal transmission. These multiple channels can each have different purposes.

[0041] 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 transmitting user data (such as voice data, video data, or text message data) from a UE (e.g., UE 110A and / or 110B) to a network entity (e.g., network entity 120A and / or 120B). Additionally, the PUSCH can be used to transmit control information (e.g., uplink control information (UCI)). The PUSCH can be shared by multiple UEs. The PUCCH is used to transmit control information (e.g., UCI) from the UE to the network, such as channel quality feedback, scheduling requests, and responses. The PRACH is used for random access in the uplink direction, enabling the UE to access the system.

[0042] DL transmission path 112 may include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Broadcast Channel (PBCH), or Paging Channel. The PDSCH is used for the transmission of user data from network entities to the UE. The PDSCH can be shared by multiple UEs. Similar to the PUSCH, the data can be any type of information, such as voice data, video data, or text message data. The Paging Channel is used to notify the UE of incoming traffic from a network entity for that UE.

[0043] exist Figure 1AIn the example shown, UE 110A may be able to support LTM. In this example, network entity 120A has provided UE 110A with a candidate cell monitoring configuration for use in LTM. This configuration specifies that UE 110A can monitor and measure reference signals (RS) for network entities associated with cells 126B to 126E, and report such measurements to network entity 120A in serving cell 126A. In this configuration, cells 126B to 126E can be referred to as “active candidate cells” because UE 110A is actively monitoring RS for cells 126B to 126E, and these cells are candidates to become “target cells” in LTM handover. In this example, cells 126F and 126G can be referred to as “inactive candidate cells” or “deactivated candidate cells” because UE 110A is not actively monitoring RS from these cells for LTM purposes.

[0044] UE 110A can be configured to detect one or more specific conditions based on RS measurements. If the conditions are met, the UE can autonomously initiate an LTM procedure and send an uplink (UL) transmission to network entity 120A to initiate cell handover. For example, UE 110A can detect that the communication quality between UE 110A and network entity 120A has degraded and can achieve better communication quality by switching to radio unit 121C communicating with cell 126D. UE 110A can report the RS measurements to network entity 120A, and in response, network entity 120A can transmit a cell handover command to UE 110A indicating information about the target cell 126D.

[0045] exist Figure 1A In the example shown, UE 110A has detected a condition instructing UE 110A to reduce resources associated with monitoring RS used for LTM. For example, UE 110's battery level may be below a threshold level, UE 110A's temperature may rise above a threshold level, or UE 110A may have changed location. In response to detecting this condition, UE 110 can 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 candidate cells that UE 110A will no longer monitor for the LTM process. In some aspects, the request 128 may identify resources to be reduced, such as resources associated with candidate cells that will no longer be monitored.

[0046] Figure 1B This is a diagram illustrating an example wireless communication system 100 after a change in the candidate cell monitoring configuration requested by the UE. Figure 1B continue Figure 1AThe example shown is in [the image]. Figure 1B In the example shown, UE 110A has transmitted a request to stop monitoring resources associated with candidate cell 126E. In some aspects, network entity 120A transmits an updated candidate cell monitoring configuration specifying cells 126B to 126D as candidate cells for LTM. Cell 126E is not designated as a candidate cell in the updated configuration, and UE 110A no longer monitors RS from cell 126E. Therefore, cell 126E can be changed from an "active candidate cell" to a "deactivated candidate cell" or an "inactive candidate cell." The UE can release the resources associated with monitoring RS from cell 126E.

[0047] exist Figure 1A and Figure 1B In the example shown, network entity 120B is a network entity associated with cell 126E. In some aspects, network entity 120A transmits a message to network entity 120B instructing network entity 120B that it may release resources associated with UE-specific RSs intended for use by UE 110A during LTM procedures. A potential technical advantage of releasing such resources is that network entity 120B can provide the released resources for other purposes, thereby potentially increasing the throughput and / or efficiency of the network entity.

[0048] Note that updates to the candidate cell monitoring configuration can reduce or increase resource usage on the UE and the network. For example, if the UE's battery level is low or the UE is experiencing a thermal issue, the UE can request an update to the candidate cell monitoring configuration to reduce the number of candidate cells being monitored, reduce the number of monitored RSs, reduce monitoring periodicity, and / or reduce reporting periodicity. On the other hand, if the UE's battery condition improves (i.e., the UE is plugged into a charger) or the thermal issue decreases, the UE can 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 of monitored RSs, increase monitoring periodicity, and / or increase reporting periodicity.

[0049] Compared to existing systems, the disclosed technology can improve power consumption in the UE. For example, when conditions on the UE make such reduction desirable, such as when the UE's battery is low or when the UE is at risk of overheating, the UE can initiate a request to update the candidate cell monitoring configuration to reduce power consumption associated with candidate cell monitoring. The UE does not need to wait for network entities to update the candidate cell monitoring configuration.

[0050] Figure 2 , Figures 3A to 3D and Figure 4Figure 9, along with the accompanying description, illustrates various techniques and aspects of a UE requesting a candidate cell configuration update. In some of the examples below, the operation can be described as utilizing RRC signaling. Unless otherwise specified, RRC signaling can instruct an RRC reconfiguration message from a network entity to the UE, or a System Information Block (SIB).

[0051] Figure 2 This is a sequence diagram 200 illustrating an example operation of the communication process for changing the candidate cell monitoring configuration requested by the UE. Although not shown for clarity, it is possible to implement... Figure 2 The various responses to the messages shown in the diagram ensure reliable operation of candidate cell monitoring configuration updates requested by the UE. (Regarding...) Figure 2 In the example discussed, network entity 120A is associated with the serving cell, and network entities 120B and 120X are associated with candidate cells for LTM handover.

[0052] At operation 201, UE 110A may transmit or report UE capabilities to network entity 120A to support a candidate cell monitoring configuration update requested by the UE. In some aspects, UE 110A may transmit UE capability information to network entity 120A during the initial communication session establishment process between UE 110A and network entity 120A. After establishing a communication session with network entity 120A, network entity 120A may be referred to as the "serving cell network entity". UE capability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rate, and network protocols. Additionally, UE 110A may report to network entity 120A UE capabilities indicating whether the UE supports a candidate cell monitoring configuration update requested by the UE.

[0053] exist Figure 2 In the example, UE 110A can transmit UE capability information to network entity 120A. In some implementations, the network entity can receive UE capability information from the core network (e.g., from the core network's Access and Mobility Management Function (AMF)). In some other implementations, the network entity can receive UE capabilities from another network entity (e.g., a gNB or eNB).

[0054] At operation 202, network entity 120A may configure UE 110A based on the UE capability information received at operation 201, in response to the candidate cell configuration update requested by the UE. In some aspects, network entity 120 may do so via RRC signaling (e.g., RRCReconfigurationThe network entity 120 may configure UE 110 using a 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 (e.g., for use during LTM procedures). In some aspects, the candidate cell monitoring configuration may also include monitoring periodicity, an indication of one or more rules to be used to update the candidate cell monitoring configuration, a first time period in which the UE should subsequently update the candidate cell monitoring configuration autonomously, and / or a second time period in which the UE will update the candidate cell monitoring configuration after receiving confirmation from the network entity of the request to update the candidate cell monitoring configuration.

[0055] At operation 204, network entities 120B and 120X can transmit RS to UE 110A for use during LTM handover. UE 110A can measure RS to determine whether LTM handover is desired. In some aspects, RS may include a Synchronization Signal Block (SSB). In other aspects, RS may include a Channel State Information Reference Signal (CSI-RS).

[0056] At operation 206, UE 110A may provide a candidate cell RS measurement report to 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 L1 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 about the candidate cell and / or RS, and a cell identifier (ID) and / or RS ID corresponding to the reported candidate cell or RS. The channel metrics may be one or more of the following: L1 or Layer 3 (L3) Reference Signal Received Power (RSRP), Signal-to-Interference-plus-Noise Ratio (SINR), Reference Signal Received Quality (RSRQ), and the like.

[0057] At operation 208, UE 110A selects configuration update. UE 110A may select configuration update in response to UE 110A detecting a condition of the UE. In some aspects, this condition may include detecting that the battery level exceeds a power threshold. For example, the battery level may have dropped below a predetermined or configurable level. In some aspects, this condition may include detecting that the temperature of UE 110A has exceeded a threshold. For example, UE 110A may detect that the temperature of UE 110A or its components has increased to exceed a threshold, which may cause damage to UE 110A or its components. In some aspects, this condition may be a change in the location of UE 110A within the cell. For example, UE 110A may have moved within the serving cell to a location farther away from one or more of the active candidate cells.

[0058] In some respects, the update may be the output of a machine learning model that uses the history of RS measurements, the conditions of UE 110A, and / or UE location as input. In some respects, historical information may be collected by UE 110A. In some other respects, historical information may be provided to UE 110A by the network. In some further respects, historical information may be provided to UE 110A by a third-party service (e.g., UE vendor or other third party). Similarly, the machine learning model may be provided by the network, mobile network operator, or a third party.

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

[0060] UE 110A can transmit indications of requested updates to network entity 120A in various ways. In some aspects, UE 110A can transmit indications of requested updates in RRC signaling. In others, UE 110A can use a UL Media Access Control (MAC) element (CE) to transmit indications of requested updates. In still others, UE 110A can transmit indications of requested updates in uplink control information (UCI) via PUCCH or PUSCH.

[0061] An example implementation of UE 110 transmitting an indication of a requested update in RRC signaling will now be described. In some aspects, UE 110A transmits RRC signaling to network entity 120A, where the RRC includes User Assistance Information (UAI) that includes an indication of a requested update to the candidate cell monitoring configuration. The type of UAI 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 UE 110A for LTM purposes. In some aspects, the UAI may include an updated list of RSs to be monitored by UE 110A for LTM purposes.

[0062] 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 an update to the candidate cell monitoring configuration can be selected based on predefined or configurable rules, where both UE 110A and network entity 120A apply the same rules to update the candidate cell monitoring configuration. For example, the rule could specify that UE 110A will no longer monitor the candidate cell or RS with the lowest RSRP in the most recent candidate cell RS measurement report provided at operation 206.

[0063] An example implementation in which UE 110A uses UL MAC CE to transmit an indication of a requested update will now be described. In some aspects, UE 110A may transmit a scheduling request to the network entity associated with the serving cell (network entity 120A in this example). Network entity 120A may transmit UL authorization for the PUSCH in response to the scheduling request. In some aspects, the UE may send a request to update the candidate cell monitoring configuration in MAC CE via authorized PUSCH resources.

[0064] In some other respects, UE 110A can transmit either a contention-free RACH or a contention-based RACH. The Type 1 random access procedure can also be referred to as a 4-step RACH procedure. A Type 1 random access procedure involves a protocol comprising up to four messages (referred to as Msg1, Msg2, Msg3, and Msg4). To initiate a Type 1 random access procedure, the UE transmits a random access preamble in the first message (Msg1) via PRACH. The network entity responds to Msg1 by transmitting a second message (Msg2) via PDSCH. Msg2 is also referred to as the Random Access Response (RAR). In some cases, Msg2 indicates the scheduled resources (in the PUSCH) available for the UE to use for the transmission of the third message (Msg3). When applicable, the UE transmits Msg3 via the PUSCH resources authorized in Msg2. In response to Msg3, the network entity transmits the fourth message (Msg4). Msg4 is also referred to as the contention-resolved transmission (Msg4). Note that Msg3 and Msg4 may not be necessary. For example, the UE may include a small data transmission with a random access preamble in Msg1, and the network entity may include a response in Msg2 without granting authorization for uplink resources for Msg3.

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

[0066] In some respects, the RACH transmission for a UE requesting an update of the candidate cell monitoring configuration may have a preamble identifying the RACH as initiating the 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 respects, the UE may transmit the request to update the candidate cell monitoring configuration in a subsequent UL transmission. For example, for a 2-step RACH procedure, the UE may transmit the request in the PUSCH transmission of MsgA, or for a 4-step RACH procedure, the UE may transmit the request in Msg3.

[0067] In some aspects, the UE can be configured to have multiple LTM configurations associated with multiple LTM configuration IDs. A MACCE can include one or more LTM configuration IDs identifying a specific candidate cell monitoring configuration to be updated. A MAC CE can have one or more MAC CE types that can be used to indicate a request to update a candidate cell monitoring configuration. In some aspects, a single MAC CE type can be defined to indicate that the MAC CE contains a request to update the candidate cell monitoring configuration. The UE 110A uses various fields within the MAC CE to indicate the specific type of update being requested and the updated value. For example, a single MAC CE type can indicate a request to update a candidate cell monitoring configuration. Fields within the MAC CE indicate whether the request is for cell deactivation or activation, RS activation or deactivation, and / or a request for periodic updates to RS monitoring. Other fields within the MAC CE provide indicators for the values ​​associated with the requested update, such as the candidate cell ID for cell activation or deactivation, an indicator indicating which RSs will be activated or deactivated, and / or an indicator indicating the periodicity of the update. The following is about... Figure 7 Describe further details about the sample MAC CE.

[0068] In some other respects, a MAC CE can be one of several types, where each MAC CE type indicates the type of update being requested, and the fields of the MAC CE indicate the updated value for the requested type. Different types of MAC CEs can be defined for different request purposes. For example, a first MAC CE type can indicate cell activation or deactivation. A second MAC CE type can indicate a request for RS activation or deactivation. A third MAC CE type can be defined to indicate a request to update the RS monitoring periodicity. Each of the different MAC CE types associated with a request to update the candidate cell monitoring configuration can use a different MAC CE subheader. In some respects, each type of request is defined by a different Logical Channel ID (LCID) in the subheader.

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

[0070] In some respects, the UE can indicate a request to deactivate a candidate cell by transmitting an L1 report in a UCI indicating that the measurements of all RSs associated with the candidate cell are outside the effective range. In other respects, the UE can indicate a request to deactivate a cell by transmitting an L1 report including a UCI indicating that the measurements of all RSs associated with the candidate cell are below a predetermined or configurable threshold.

[0071] In some other aspects, the UE 110A can use L1 reports to update the candidate cell monitoring configuration based on trigger conditions. For example, in some cases, the trigger condition may be sending L1 reports with values ​​indicating that the RS or candidate cell measurement is outside the valid range a predetermined or configurable number of times. In some other cases, the trigger condition may be sending L1 reports with values ​​indicating that the RS or candidate cell measurement is outside the valid range a predetermined or configurable number of times within a predefined or configurable time interval. In some aspects, when the trigger condition occurs, the UE can initiate a contention-free RACH procedure. The L1 report may be sent in the PUSCH of MsgA in a 2-step RACH procedure or in Msg3 in a 4-step RACH procedure.

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

[0073] In some aspects, the acknowledgment message can be an acknowledgment (ACK) indicating that network entity 120A has received and / or accepted the request to update the candidate cell monitoring configuration. In an implementation where the request is transmitted from UE 110A to network entity 120A via MAC CE or via RRC signaling, the ACK can be associated with a UL authorization provided by network entity 120A to UE 110A via PDCCH. In some aspects, the UL authorization can indicate the same Hybrid Automatic Repeat Request (HARQ) procedure ID as the PUSCH carrying the request transmitted from UE 110A. In some aspects, the acknowledgment message can indicate that the network entity agrees to the update of the candidate cell monitoring configuration. The acknowledgment message can be transmitted via an ACK indicating the updated candidate cell monitoring configuration. RRCReconfiguration Messages, MAC CE, or downlink control information (DCI) are transmitted from network entity 120A to UE110A.

[0074] At operation 214, the network entity may transmit the updated candidate cell configuration to the 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 to UE 110A for LTM procedures regarding the deactivated candidate cell. For example, the network entity may release resources previously used to transmit RS (e.g., RS to be used for the LTM procedure) to UE 110A. Furthermore, network entity 120B may release resources associated with monitoring UL transmissions from UE 110A associated with LTM handover to network entity 120B, since such handover will not occur while the cell is deactivated.

[0075] At operation 216, UE 110A and network entities 120A and 120B can implement the updated candidate cell monitoring configuration. In some respects, UE 110A can do this after sending a request to update the candidate cell monitoring configuration at operation 210. X The UE 110A updates the candidate cell monitoring configuration via milliseconds. In some respects, the UE 110A can proactively update its configuration based on the requested configuration update.

[0076] In some other aspects, UE 110A can update the candidate cell monitoring configuration based on trigger conditions. For example, in some cases, the trigger condition may be sending reports a predetermined or configurable number of times at operation 206. In some other cases, the trigger condition may be sending reports a predetermined or configurable number of times within a predetermined or configurable time interval at operation 206. In some aspects, the UE can update the candidate cell monitoring configuration based on trigger conditions after they are detected. X ms updates candidate cell monitoring configuration.

[0077] In some other respects, the UE can, after receiving confirmation or response to the request for updated candidate cell monitoring configuration transmitted at operation 210, Y ms updates candidate cell monitoring configuration.

[0078] Figures 3A to 3D This includes an example timing diagram showing the relative timing of various operations performed during a UE request to update the candidate cell monitoring configuration. The timing diagram may not be drawn to scale, and the durations between the various operations may differ from those shown in the diagram.

[0079] Figure 3A This is a sequence diagram illustrating the configuration update after receiving the update confirmation. Figure 3AIn the example timing diagram 300 shown, UE 110A receives a series of RS 302A, 302B, and 302C at times t0, t1, and t2, respectively, and calculates the measurements of the received RS for use in determining whether to perform LTM handover. At time t3, UE 110A detects a change in UE conditions. For example, UE 110A may detect that the battery level is below a threshold, the thermal measurement is above a threshold, or the UE's location has changed. In response to detecting the change in conditions, UE 110A selects a candidate cell monitoring configuration update at operation 208. For example, UE 110A can select a candidate cell for deactivation, a reference signal for deactivation, or monitor periodic changes. At time t4, UE 110A transmits a request 304 to network entity 120A to update the candidate cell monitoring configuration. At time t5, UE 110A receives an acknowledgment 306 confirming that network entity 120A has received the request. At time t6, the updated candidate cell monitoring configuration is implemented and becomes effective by UE 110A 216.

[0080] Figure 3B This is a sequence diagram showing the configuration update after a predetermined time has elapsed following the update request. (and...) Figure 3A The example timing diagram 300 is the same, in Figure 3B In the example timing diagram 310 shown, UE 110A receives a series of RS 302A, 302B, and 302C at times t0, t1, and t2, respectively, and calculates the measurements of the received RS for use in determining whether to perform an LTM handover. At time t3, UE 110A detects a change in UE conditions. For example, UE 110A may detect that the battery level is below a threshold, the thermal measurement is above a threshold, or the UE's location has changed. In response to detecting the change in conditions, UE 110A selects a candidate cell monitoring configuration update at operation 208. For example, UE 110A can select a candidate cell for deactivation, a reference signal for deactivation, or monitor periodic changes. At time t4, UE 110A transmits a request 304 to network entity 120A to update the candidate cell monitoring configuration. Time t4 is the start of a predetermined or configurable time interval 312 during which UE 110A waits for the candidate cell monitoring configuration update. At time t5, the predetermined interval ends, and UE 110A implements 216 updated candidate cell monitoring configurations.

[0081] Figure 3C This is a timing diagram illustrating configuration updates after a predetermined number of update requests have been transmitted. Figure 3A Example timing diagram 300 and Figure 3B Similar to the example timing diagram 310, in Figure 3CIn the example timing diagram 320 shown, UE 110A receives a series of RS 302A, 302B, and 302C at times t0, t1, and t2, respectively, and calculates the measurements of the received RS for use in determining whether to perform an LTM handover. At time t3, UE 110A detects a change in UE conditions. For example, UE 110A may detect that the battery level is below a threshold, the thermal measurement is above a threshold, or the UE's location has changed. In response to detecting the change in conditions, UE 110A selects a candidate cell monitoring configuration update at operation 208. For example, UE 110A can select a candidate cell for deactivation, a reference signal for deactivation, or monitor periodic changes. From time t4 to t6, UE 110A transmits a series of requests 304A to 304N to network entity 120A to update the candidate cell monitoring configuration. After the Nth consecutive update request, at time t7, UE 110A implements 216 the updated candidate cell monitoring configuration. As discussed above, the value of N can be a predefined or configurable value.

[0082] Figure 3D This is a timing diagram illustrating a configuration update after a predetermined number of update requests have been transmitted within the update interval. Figure 3A , Figure 3B and Figure 3C The corresponding example timing diagrams 300, 310, and 320 are the same, in Figure 3D In the example timing diagram 330 shown, UE 110A receives a series of RS 302A, 302B, and 302C at times t0, t1, and t2, respectively, and calculates the measurements of the received RS for use in determining whether to perform an LTM handover. At time t3, UE 110A detects a change in UE conditions. For example, UE 110A may detect that the battery level is below a threshold, the thermal measurement is above a threshold, or the UE's location has changed. In response to detecting the change in conditions, UE 110A selects a candidate cell monitoring configuration update at operation 208. For example, UE 110A can select a candidate cell for deactivation, a reference signal for deactivation, or monitor periodic changes. Time t4 marks the beginning of the update interval 312 that spans through time t8. From time t5 to t7, UE 110A transmits a series of requests 304A to 304M to network entity 120A to update the candidate cell monitoring configuration. After M update requests have been sent during update interval 332, UE 110A implements 216 updated candidate cell monitoring configurations. As discussed above, the value of M and the size of update interval 332 can be predetermined or configurable values.

[0083] Figure 4This is a flowchart illustrating an example UE operation for a method of changing the candidate cell monitoring configuration requested by the UE. The example operation of method 400 can be, for example, performed by... Figure 1A , Figure 1B , Figure 2 and / or Figures 3A to 3D It is executed using UE 110A.

[0084] At box 401, and as mentioned above... Figure 2 As described in Operation 201, the UE can transmit or report UE capabilities that support a candidate cell monitoring configuration update requested by the UE to the serving cell network entity. In some aspects, the UE can transmit UE capability information to the network entity during the initial communication session establishment process between the UE and the network entity. UE capability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rate, and network protocols. UE 110A can report UE capability information to network entity 120A indicating whether the UE supports a candidate cell monitoring configuration update requested by the UE.

[0085] At box 402, and as mentioned above... Figure 2 As described in operation 202, the UE can receive a configuration for a candidate cell monitoring configuration update requested by the UE from the serving cell network entity. In some aspects, this 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 (e.g., for use during LTM procedures). In some aspects, the candidate cell monitoring configuration may also include monitoring periodicity, an indication of one or more rules to be used to update the candidate cell monitoring configuration, a first time period in which the UE should subsequently update the candidate cell monitoring configuration autonomously, and / or a second time period in which the UE will update the candidate cell monitoring configuration after receiving confirmation from the network entity of the request to update the candidate cell monitoring configuration.

[0086] At box 404, and as mentioned above... Figure 2 As described in Operation 204, the UE can receive RS from various network entities in different cells for use in the LTM handover process. The UE can measure the RS to determine whether the LTM handover is desired.

[0087] At box 406, and as mentioned above... Figure 2 As described in Operation 206, the UE can provide candidate cell RS measurement reports to the serving cell network entity. In some aspects, candidate cell RS measurement reports can be provided in L1 signaling. For example, the reports can be provided in PUCCH or PUSCH.

[0088] At box 408, and as mentioned above... Figure 2As described in operation 208, UE 110A selects a configuration update. In response to the UE detecting a condition for itself, the UE may select a configuration update. In some aspects, this condition may include detecting that the battery level exceeds a power threshold. For example, the battery level may have dropped below a predetermined or configurable level. In some aspects, the condition may include detecting that the UE's temperature has exceeded a threshold. For example, the UE may detect that the temperature of the UE or its components has increased to exceed a threshold, potentially causing damage to the UE or its components. In some aspects, the condition may be a change in the UE's location within the cell. For example, the UE may have moved within the serving cell to a location further away from one or more of the active candidate cells. In some aspects, the condition may be the output of a machine learning model that uses historical measurements of RS and / or the conditions of UE 110A as input.

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

[0090] At box 412, and as mentioned above... Figure 2 As described in operation 212, the UE may optionally receive from the serving cell network entity an acknowledgment message confirming the request to update the candidate cell monitoring configuration. In some aspects, the acknowledgment message may be an ACK indicating that the serving cell network entity has received and / or accepted the request to update the candidate cell monitoring configuration. In some aspects, the acknowledgment message may indicate that the network entity agrees to the update of the candidate cell monitoring configuration.

[0091] At box 416, as mentioned above... Figure 2 As described in operation 216, the UE can implement the updated candidate cell monitoring configuration. In some aspects, the UE can do this after sending a request to update the candidate cell monitoring configuration at operation 210. X The UE 110A updates the candidate cell monitoring configuration via milliseconds. In some respects, the UE 110A can proactively update its configuration based on the requested configuration update.

[0092] Figure 5 This is a flowchart illustrating an example network entity operation for a method of changing the candidate cell monitoring configuration requested by a UE. The operation of method 500 can be performed by... Figure 1A, Figure 1B , Figure 2 and / or Figures 3A to 3D Execution of network entity 120A.

[0093] At box 501, and as mentioned above... Figure 2 As described in Operation 201, a network entity can receive reports of UE capabilities that support a candidate cell monitoring configuration update requested by the UE. In some aspects, the network entity can receive capability information from the UE during the initial communication session establishment process between the UE and the network entity. UE capability information may include supported frequency bands, radio access technologies, maximum transmission power, maximum data rate, and network protocols. UE capability information can indicate whether the UE supports the candidate cell monitoring configuration update requested by the UE.

[0094] At box 502, and as mentioned above... Figure 2 As described in operation 202, a network entity may transmit a configuration to a UE for a candidate cell monitoring configuration update requested by the UE. In some aspects, this 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 (e.g., for use during LTM procedures). In some aspects, the candidate cell monitoring configuration may also include monitoring periodicity, an indication of one or more rules to be used for updating the candidate cell monitoring configuration, a first time period in which the UE should subsequently update the candidate cell monitoring configuration autonomously, and / or a second time period in which the UE will update the candidate cell monitoring configuration after receiving confirmation from the network entity of the request to update the candidate cell monitoring configuration.

[0095] At box 506, and as mentioned above... Figure 2 As described in Operation 206, network entities can receive candidate cell RS measurement reports from the UE. In some aspects, candidate cell RS measurement reports can be provided in L1 signaling. For example, the reports can be provided in PUCCH or PUSCH.

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

[0097] At box 512, and as mentioned above... Figure 2As described in operation 212, the network entity may optionally transmit an acknowledgment message to the UE confirming the request to update the candidate cell monitoring configuration. In some aspects, the acknowledgment message may be an ACK indicating that the network entity has received and / or accepted the request to update the candidate cell monitoring configuration. In other aspects, the acknowledgment message may indicate that the network entity agrees to the update of the candidate cell monitoring configuration.

[0098] At box 514, and as mentioned above... Figure 2 As described in operation 214, a network entity can transmit the updated candidate cell configuration to a candidate cell network entity affected by the updated candidate cell monitoring configuration. For example, in the case of a candidate cell being deactivated, the deactivated candidate cell network entity can release resources previously dedicated to the UE for the LTM procedure. For example, the candidate cell network entity can release resources used to transmit RS (e.g., RS to be used for the LTM procedure) to the UE. Furthermore, the candidate cell network entity can release resources associated with monitoring UL transmissions from the UE associated with LTM handover to the candidate cell network entity, since such handover will not occur when the cell is deactivated.

[0099] At box 516, and as mentioned above... Figure 2 As described in Operation 216, network entities can implement updated candidate cell monitoring configurations.

[0100] Figure 6 This is a block diagram illustrating example User Assistance Information (UAI) data 602 for a change in the candidate cell monitoring configuration requested by the UE. In some aspects, UAI data 602 may include one or more of the following: 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 reporting periodicity 612.

[0101] The candidate cell list 604 can specify an updated list of candidate cells to be monitored. The updated list can contain fewer or more candidate cells than the current candidate cell monitoring configuration. In some aspects, the candidate cell list 604 can specify an updated list of candidate cell IDs to be monitored. In other aspects, the candidate cell list 604 can specify an updated list of candidate cell indices.

[0102] The candidate cell RS list 606 can specify an updated list of RSs to be monitored. The updated list can contain fewer or more RSs than the current candidate cell monitoring configuration. In some aspects, the candidate cell RS list 606 can specify an updated list of RS indices. For example, the updated list of RS indices can include updated lists of SSB indices or CSI-RS indices.

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

[0104] The number of monitored RSs 609 can specify an update to the number of candidate cell RSs that the UE can monitor. In some aspects, the number of monitored RSs 609 can be associated with the maximum number of monitored RSs on each candidate cell or all candidate cells. In other aspects, the number of monitored RSs 609 can be associated with the minimum number of monitored RSs on each candidate cell or all candidate cells.

[0105] The monitoring periodicity 610 can specify the update of the monitoring periodicity for the monitored RS or candidate cell. In some aspects, the monitoring periodicity 610 can be associated with the maximum periodicity of the monitored RS or candidate cell. In other aspects, the monitoring periodicity 610 can be associated with the minimum periodicity of the monitored RS or candidate cell.

[0106] Reporting periodicity 612 can specify the update of the reporting periodicity for candidate cell RS measurements used in the LTM process. In some aspects, reporting periodicity 612 can be associated with the maximum reporting periodicity for candidate cell RS measurements. In other aspects, reporting periodicity 612 can be associated with the minimum reporting periodicity for candidate cell RS measurements.

[0107] Figure 7 This is a block diagram illustrating example MAC CE data 702 for changes in the candidate cell monitoring configuration requested by the UE. In some aspects, MAC CE data 702 includes one or more of the following: LTM configuration ID 704, indicator 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 reporting periodicity 714.

[0108] LTM configuration ID 704 identifies the candidate cell monitoring configuration to be updated.

[0109] The candidate cell list 708 specifies a list of candidate cells that can be monitored. This list can contain both active and inactive candidate cells. An updated list can contain fewer or more candidate cells than the current candidate cell monitoring configuration. In some aspects, the candidate cell list 708 can specify an updated list of candidate cell IDs to be monitored. In other aspects, the candidate cell list 708 can specify an updated list of candidate cell indices.

[0110] The candidate cell RS list 709 specifies a list of candidate cell RSs that can be monitored. The list can include active and inactive RSs. An updated list can contain fewer or more RSs than the current candidate cell monitoring configuration. In some aspects, the candidate cell RS list 709 can specify an updated list of RS indices. For example, an updated list of RS indices can include updated lists of SSB indices or CSI-RS indices.

[0111] Indicator 706 may include a cell activation / deactivation indicator and an RS activation / deactivation indicator. The indicator may be a bit field, where the position of a bit in the bit field corresponds to the position of a candidate cell in candidate cell list 708 or the position of an RS in candidate cell RS list 709. The value of the bit indicates whether the corresponding cell or RS is active or inactive.

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

[0113] The number of monitored RSs 711 can specify an update to the number of candidate cell RSs that the UE can monitor. In some aspects, the number of monitored RSs 711 can be associated with the maximum number of monitored RSs on each candidate cell or all candidate cells. In other aspects, the number of monitored RSs 711 can be associated with the minimum number of monitored RSs on each candidate cell or all candidate cells.

[0114] The monitoring periodicity 712 can specify the update of the monitoring periodicity for the monitored RS or candidate cell. In some aspects, the monitoring periodicity 712 can be associated with the maximum periodicity of the monitored RS or candidate cell. In other aspects, the monitoring periodicity 712 can be associated with the minimum periodicity of the monitored RS or candidate cell.

[0115] The reporting periodicity 714 can specify the update of the reporting periodicity for candidate cell RS measurements used in the LTM process. In some aspects, the reporting periodicity 714 can be associated with the maximum reporting periodicity for candidate cell RS measurements. In other aspects, the reporting periodicity 714 can be associated with the minimum reporting periodicity for candidate cell RS measurements.

[0116] Depending on the type of update being performed, not all fields may be available. For example, if MACCE is used to activate or deactivate candidate cells to be monitored, fields related to RS are not used. In such cases, unused fields can be filled with reserved bit sequences.

[0117] Figure 8 This is a block diagram illustrating an example configuration of network entity 120 and UE 110. Network entity 120 can be any implementation of network entities 120A and 120B. Note that the depicted hardware configuration represents the processing and communication components related to the candidate cell configuration update requested by the UE. Certain components that are well understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, etc., may be omitted from the depicted hardware configuration.

[0118] UE 110 includes an antenna 802, a radio frequency front-end (RF front-end) 804, and a communication interface for communication with network entity 120, one or more TRPs, and / or one or more radio units (e.g., Figure 1A and Figure 1B Radio frequency transceivers (e.g., LTE transceiver 806 and 5G NR transceiver 808) that communicate with radio units 121A to 121D.

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

[0120] The antenna 802 of UE 110 may include an array of multiple antennas that can be tuned to one or more frequency bands associated with a corresponding RAT. The antenna 802 and RF front-end 804 can be tuned to and / or are capable of being tuned 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 antenna 802, RF front-end 804, LTE transceiver 806, and / or 5G NR transceiver 808 can be configured to support communication with network entity 120, one or more TRPs, or one or more radio units (e.g., Figure 1A and Figure 1B Beamforming for the transmission and reception of communications by radio units 121A to 121D. By way of example and not limitation, antenna 802 and RF front end 804 can be implemented for operation in sub-gigahertz bands, sub-6 GHz bands and / or above 6 GHz bands as defined by 3GPP LTE and 5G NR communication standards.

[0121] UE 110 also includes a processor 814 and a computer-readable storage medium (CRM) 816. The processor 814 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs) and the like. For illustration purposes, the processor 814 may include an application processor (AP) used by UE 110 to execute an operating system and various user-level software applications, and one or more processors utilized by a modem or baseband processor of the RF front end 804.

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

[0123] 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 (Real Cell Registries) for monitoring active candidate cells. In some aspects, candidate cell monitoring configuration 819 may also include monitoring periodicity, indications of one or more rules to be used to update the candidate cell monitoring configuration, a first time period in which the UE should subsequently update the candidate cell monitoring configuration autonomously, and / or a second time period in which the UE will update the candidate cell monitoring configuration after receiving confirmation from a network entity of a request to update the candidate cell monitoring configuration.

[0124] CRM 816 also includes a communication controller 822. Alternatively or additionally, the communication controller 822 may be implemented, in whole or in part, as a hardware logic or circuitry system integrated or separate from other components of the UE 110. In some aspects, the communication 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 candidate cell configuration updates requested by the UE.

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

[0126] Turn to the hardware configuration of network entity 120, note that although Figure 8 The implementation of network entity 120 is shown as a single network node (e.g., a 5G NR node B or "gNB"), but the functionality of network entity 120 and therefore its hardware components can alternatively be distributed across multiple network nodes or devices, and can be distributed in a manner used to perform the functions described herein. As an example, the functionality (and hardware components) of network entity 120 can be distributed across radio units (RUs), distributed units (DUs), or central units (CUs).

[0127] Network entity 120 includes an antenna 852, a radio frequency front-end (RF front-end) 854, one or more LTE transceivers 856 and / or one or more 5G NR transceivers 858 for communicating with UE 110. The RF front-end 854 of network entity 120 can couple or connect the LTE transceivers 856 and 5G NR transceivers 858 to the antenna 852 to facilitate various types of wireless communication. Similar to RF front-end 804, 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 one or more RF signals (e.g., RF signals from UE 110) and preprocesses the one or more RF signals to generate data from the RF signals, which is provided as input to processes and / or applications performed on network entity 120. Such preprocessing may include, for example, power amplification, conversion of band signaling to baseband signaling, initial analog-to-digital conversion, and the like.

[0128] The antenna 852 of network entity 120 can be configured individually and / or configured as one or more arrays of multiple antennas. The antenna 852 and RF front-end 854 can be tuned to and / or are capable of being tuned to one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 856 and / or the 5G NR transceiver 858. Additionally, the antenna 852, RF front-end 854, LTE transceiver 856, and / or 5G NR transceiver 858 can be configured to support beamforming, such as massive MIMO, for transmission and reception of communications with UE 110.

[0129] Network entity 120 also includes a processor 860 and a computer-readable storage medium (CRM) 862. The processor 860 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs). For illustration, the processor 860 may include an application processor (AP) used by network entity 120 to execute an operating system and various user-level software applications, and one or more processors used by a modem or baseband processor of the RF front-end 854 to implement communication with the UE 110.

[0130] CRM 862 may include any suitable memory or storage device that can be used to store device data of network entity 120, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory. Device data may include data 864, which includes network scheduling data, radio resource management data, beamforming codebooks, software application configuration information, UE transmitter power level and / or TRP configuration data, and the like.

[0131] 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, candidate cell monitoring configuration 819 may also include one or more of the following: monitoring periodicity, indication of one or more rules to be used to update the candidate cell monitoring configuration, a first time period in which the UE should subsequently update the candidate cell monitoring configuration autonomously, and / or a second time period in which the UE will update the candidate cell monitoring configuration after receiving confirmation from a network entity of a request to update the candidate cell monitoring configuration.

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

[0133] CRM 862 also includes an RF resource manager 865. In some aspects, the RF resource manager 865 of network entity 120 is implemented to perform various functions associated with allocating physical access (e.g., resource blocks) or communication resources for the air interface of network entity 120. The air interface of network entity 120 can be partitioned or divided into various units (e.g., frames, subframes, or time slots) of one or more of bandwidth, time, symbol, or spatial layers. For example, within the framework of the 5G NR protocol, the RF resource manager 865 can allocate bandwidth and access time intervals within resource blocks, wherein each resource block can be wholly or partially allocated to one or more channels for communication with UE 110. Channels can include one or more of PRACH, PUCCH, PUSCH, PDCCH, PDSCH, PBCH, or paging channels. A resource block can include multiple subcarriers, each subcarrier spanning a portion of the frequency domain of the resource block. Subcarriers can be further divided into resource elements or Orthogonal Frequency Division Multiplexing (OFDM) symbols, each resource element or OFDM symbol spanning a portion of the time domain of the subcarrier. Therefore, a resource block comprises multiple OFDM symbols, which can be grouped into subcarriers together with other OFDM symbols having a common frequency bandwidth. In some aspects, OFDM symbols can be Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) symbols. In other aspects, OFDM symbols can be Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) symbols.

[0134] CRM 862 further includes a network entity manager 866. Alternatively or additionally, the network entity manager 866 may be implemented, wholly or partially, as a hardware logic or circuit system 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 transceiver 856 and the 5G NR transceiver 858 for communication with the UE 110, TRP, and radio unit (e.g., via the fronthaul interface 867). Figure 1A and Figure 1B It communicates with radio units 121A to 121D, as well as with the core network.

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

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

[0137] Figure 1A , Figure 1B , Figure 2 , Figures 3A to 3D and Figure 4 Figure 9 and the operations described herein are examples intended to aid in understanding exemplary implementations and should not be used to limit potential implementations or the scope of the claims. Some implementations may include additional operations, fewer operations, operations in parallel or different orders, and several different operations. Alternatively, or in addition to the other examples described herein, the examples also include any combination of the following implementation options (listed as clauses for reference).

[0138] Clause 1. A method for wireless communication performed 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 from the plurality of candidate cell monitoring parameters for modification based on conditions of the UE; and transmitting to the network entity a request to update the one or more candidate cell monitoring parameters from the candidate cell monitoring parameters.

[0139] Clause 2. The method of Clause 1 further comprises: detecting the conditions of the UE, wherein the conditions include at least one of the following: a battery level below a first threshold level, a change in battery state, a change in the location of the UE, or a heat level above a second threshold level; and transmitting the request based on the conditions.

[0140] Clause 3. The method as described in any one of Clauses 1 or 2 further comprises: detecting the condition based on the output of a machine learning model that uses historical information as input.

[0141] Clause 4. The method as described in Clause 3, wherein the historical information includes at least one of the following: first historical information collected by the UE; second historical information received from the network entity; or third historical information obtained from the application service provider.

[0142] Clause 5. The method as described in any one of Clauses 3 or 4, wherein 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.

[0143] Clause 6. The method of any one of Clauses 1 to 5, wherein the one or more candidate cell monitoring parameters include at least one of the following: the candidate cells being monitored; the number of candidate cells being monitored; the monitored reference signals associated with one or more first candidate cells; the number of monitored reference signals associated with one or more second candidate cells; the monitoring periodicity associated with one or more third candidate cells; or the reporting periodicity associated with one or more fourth candidate cells.

[0144] Clause 7. The method of any one of Clauses 1 to 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 Layer 2 triggered mobility (LTM) candidate cells.

[0145] Clause 8. The method of any one of Clauses 1 to 7, wherein selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on rules or machine learning models.

[0146] Clause 9. The method as described in Clause 8, wherein the UE selects the one or more candidate cell monitoring parameters based on the same rules as the network entity.

[0147] Clause 10. The method of any one of Clauses 1 to 9, wherein 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.

[0148] Clause 11. The method of any one of Clauses 1 to 10, wherein transmitting the request to update the candidate cell monitoring configuration includes transmitting the request in at least one of: Radio Resource Control (RRC) messages, User Assistance Information (UAI), Uplink (UL) Media Access Control (MAC) Control Element (CE), or Uplink Control Information (UCI).

[0149] Clause 12. The method of Clause 11 further includes: transmitting a scheduling request to the network entity; and receiving a UL authorization from the network entity in response to the scheduling request, wherein transmitting the request for updating includes transmitting the UL MAC CE based on the UL authorization.

[0150] Clause 13. The method as described in Clause 11, wherein transmitting the request for updating comprises 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 comprising both the random access preamble and the random access request.

[0151] Clause 14. The method of any one of Clauses 11 to 13, wherein the UL MAC CE includes a first request type indicating that the candidate cell monitoring configuration should be updated.

[0152] Clause 15. The method of any one of Clauses 11 to 14, wherein the UL MAC CE comprises at least one of the following: 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.

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

[0154] Clause 17. The method as described in Clause 16, wherein the type of update to the candidate cell monitoring configuration indicates at least one of the following: candidate cell activation; candidate cell deactivation; reference signal (RS) activation; RS deactivation; RS monitoring is updated periodically; or the report is updated periodically.

[0155] Clause 18. The method as described in any one of Clauses 16 or 17, wherein the MAC CE sub-header is based on the second request type of the ULMAC CE.

[0156] Clause 19. The method as described in Clause 18, wherein the Logical Channel ID (LCID) of the MAC CE sub-header is based on the second request type of the UL MAC CE.

[0157] Clause 20. The method of Clause 11 further includes receiving a plurality of reference signals associated with the candidate cell monitoring configuration, wherein the UCI includes a Layer 1 (L1) measurement report based on the plurality of reference signals.

[0158] Clause 21. The method as described in Clause 20, wherein a predetermined value for the reference signal (RS) in the L1 measurement report indicates a request to activate the RS.

[0159] Clause 22. The method as described in Clause 21, wherein the predetermined value includes an out-of-range indicator for the measurement associated with the RS.

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

[0161] Clause 24. The method as described in Clause 20, wherein each RS of the candidate cell has an indicator indicating that the measurement is below a threshold and indicating a request to activate the candidate cell.

[0162] Clause 25. The method of any one of Clauses 1 to 24 further comprises at least one of the following: updating the candidate cell monitoring configuration after a first predetermined time period has elapsed since the transmission of the request; updating the candidate cell monitoring configuration multiple times consecutively after a second predetermined time period has elapsed since the transmission of the request; updating the candidate cell monitoring configuration a predetermined number of times within a time interval after a third predetermined time period has elapsed since the transmission of the request; or updating the candidate cell monitoring configuration after a fourth predetermined time period has elapsed since receiving a response to the request to update the candidate cell monitoring configuration.

[0163] Clause 26. The method of any one of Clauses 1 to 25 further comprises: 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 monitoring parameters of the one or more candidate cells based on the one or more reference signals.

[0164] Clause 27. A method for wireless communication by a first network entity, comprising: transmitting a candidate cell monitoring configuration to a user equipment (UE), the candidate cell monitoring configuration specifying one or more candidate cells; receiving from the UE a request to update one or more candidate cell monitoring parameters of the candidate cell monitoring configuration; and transmitting an indicator to a second network entity operating at least one 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 comprises: transmitting to the UE a response to the request to update the monitoring parameters of the one or more candidate cells.

[0166] Clause 29. The method of Clause 28, wherein the request to update the monitoring parameters of the one or more candidate cells is included in the Physical Uplink Shared Channel (PUSCH), and the method further comprises: transmitting to the UE an uplink (UL) grant having the same Hybrid Automatic Repeat Request (HARQ) Procedure Identifier (ID) as the PUSCH.

[0167] Clause 30. The method as described in Clause 28, wherein transmitting the response comprises transmitting at least one of the following: 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 as described in Clause 27, wherein the indicator indicating the modification of the resources includes an indicator for releasing resources reserved for cell handover for the UE.

[0169] Clause 32. A user equipment (UE) comprising: a radio transceiver; at least one processor; and instructions for a communication controller, the instructions, when executed by the at least one processor, configuring the UE to receive, via the radio transceiver, a candidate cell monitoring configuration having a plurality of candidate cell monitoring parameters from a network entity; Based on the UE's conditions, select one or more candidate cell monitoring parameters from the plurality of candidate cell monitoring parameters for modification; and transmit a request to the network entity via the radio transceiver to update the one or more candidate cell monitoring parameters from the candidate cell monitoring parameters.

[0170] Clause 33. The UE as described in Clause 32, wherein the instructions further include instructions for configuring the UE to: detect the conditions of the UE, wherein the conditions include at least one of: a battery level below a first threshold level, a change in battery state, a change in the location of the UE, or a heat level above a second threshold level; and transmit the request based on the conditions.

[0171] Clause 34. The UE as described in any one of Clauses 32 or 33, wherein the instructions further include instructions for configuring the UE to detect the condition based on the output of a machine learning model that uses historical information as input.

[0172] Clause 35. The UE as described in Clause 34, wherein the historical information includes at least one of: first historical information collected by the UE; second historical information received from the network entity; or third historical information obtained from the application service provider.

[0173] Clause 36. The UE as described in any one of Clauses 34 or 35, wherein the instructions for configuring the UE to select the one or more candidate cell monitoring parameters include instructions for configuring the UE to select the one or more candidate cell monitoring parameters based on the output of the machine learning model.

[0174] Clause 37. The UE as described in any one of Clauses 32 to 36, wherein the one or more candidate cell monitoring parameters include at least one of the following: monitored candidate cells; the number of monitored candidate cells; monitored reference signals associated with one or more first candidate cells; the number of monitored reference signals associated with one or more second candidate cells; monitoring periodicity associated with one or more third candidate cells; or reporting periodicity associated with one or more fourth candidate cells.

[0175] Clause 38. The UE as described in any one of Clauses 32 to 37, wherein the candidate cell monitoring configuration is associated with at least one of the following: one or more non-serving cells; one or more deactivated cells; or one or more Layer 1 or Layer 2 triggered mobility (LTM) candidate cells.

[0176] Clause 39. The UE as described in any one of Clauses 32 to 38, wherein the instructions for configuring the UE to select the one or more candidate cell monitoring parameters include instructions for configuring the UE to select the one or more candidate cell monitoring parameters based on rules or a machine learning model.

[0177] Clause 40. The UE as described in Clause 39, wherein the UE selects the one or more candidate cell monitoring parameters based on the same rules as the network entity.

[0178] Clause 41. The UE as described in any one of Clauses 32 to 40, wherein the instructions for configuring the UE to select the one or more candidate cell monitoring parameters include instructions for configuring the UE to select 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.

[0179] Clause 42. The UE as described in any one of Clauses 32 to 41, wherein the instruction for configuring the UE to transmit the request to update the candidate cell monitoring configuration includes instructions for configuring the UE to transmit the request in at least one of: Radio Resource Control (RRC) messages, User Assistance Information (UAI), Uplink (UL) Media Access Control (MAC) Control Element (CE), or Uplink Control Information (UCI).

[0180] Clause 43. The UE as described in Clause 42, wherein the instructions further include instructions for configuring the UE to: transmit a scheduling request to the network entity; and receive a UL grant from the network entity in response to the scheduling request, wherein transmitting the request for updating includes transmitting the UL MAC CE via the UL grant.

[0181] Clause 44. The UE as described in Clause 42, wherein the instruction for transmitting the request for update includes an instruction for transmitting the request for update 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 including both the random access preamble and the random access request.

[0182] Clause 45. The UE as described in any one of Clauses 42 to 44, wherein the UL MAC CE includes a first request type indicating that the candidate cell monitoring configuration should be updated.

[0183] Clause 46. The UE as described in any one of Clauses 42 to 45, wherein the UL MAC CE includes at least one of the following: 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.

[0184] Clause 47. The UE as described in any one of Clauses 32 to 46, wherein the UL MAC CE includes a second request type indicating the type of update to the candidate cell monitoring configuration.

[0185] Clause 48. The UE as described in Clause 47, wherein the type of update to the candidate cell monitoring configuration indicates at least one of the following: candidate cell activation; candidate cell deactivation; reference signal (RS) activation; RS deactivation; or RS monitoring periodic update; or reporting periodic update.

[0186] Clause 49. The UE as described in any one of Clauses 47 or 48, wherein the MAC CE sub-header is based on the second request type of the ULMAC CE.

[0187] Clause 50. The UE as described in Clause 49, wherein the Logical Channel ID (LCID) of the MAC CE sub-header is based on the second request type of the UL MAC CE.

[0188] Clause 51. The UE as described in Clause 42, wherein the instructions further include instructions for configuring the UE to receive a plurality of reference signals associated with the candidate cell monitoring configuration, wherein the UCI includes a Layer 1 (L1) measurement report based on the plurality of reference signals.

[0189] Clause 52. The UE as described in Clause 51, wherein a predetermined value for the reference signal (RS) in the L1 measurement report indicates a request to activate the RS.

[0190] Clause 53. The UE as described in Clause 52, wherein the predetermined value includes an out-of-range indicator for measurements associated with the RS.

[0191] Clause 54. The UE as described in Clause 53, wherein the out-of-range indicator for the measurement associated with each RS of the candidate cell indicates a request to activate the candidate cell.

[0192] Clause 55. The UE as described in Clause 51, wherein each RS of the candidate cell has an indicator indicating that the measurement is below a threshold and indicating a request to activate the candidate cell.

[0193] Clause 56. The UE as described in any one of Clauses 32 to 55, wherein the instructions further include instructions for configuring the UE to perform at least one of the following operations: updating the candidate cell monitoring configuration after a first predetermined time period has elapsed since the request was transmitted; updating the candidate cell monitoring configuration multiple times consecutively after a second predetermined time period has elapsed since the request was transmitted; updating the candidate cell monitoring configuration a predetermined number of times within a time interval after a third predetermined time period has elapsed since the request was transmitted; or updating the candidate cell monitoring configuration after a fourth predetermined time period has elapsed since a response to the request to update the candidate cell monitoring configuration was received.

[0194] Clause 57. The UE as described in any one of Clauses 32 to 56, wherein the instructions further include instructions for configuring the UE to: receive one or more reference signals from one or more candidate cells associated with the candidate cell monitoring configuration; and calculate one or more modifications to the monitoring parameters of the one or more candidate cells based on the one or more reference signals.

[0195] Clause 58. A first network entity comprising: a radio transceiver; at least one processor; and instructions for a communication controller, the instructions, when executed by the at least one processor, configuring the first network entity to: transmit a candidate cell monitoring configuration to a user equipment (UE), the candidate cell monitoring 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 of the one or more candidate cells, the indicator indicating modification of resources associated with the one or more candidate cell monitoring parameters.

[0196] Clause 59. The first network entity as described in Clause 58, wherein the instructions further include instructions for configuring the first network entity to transmit to the UE a response to the request to update the monitoring parameters of the one or more candidate cells.

[0197] Clause 60. The first network entity as described in Clause 59, wherein the request to update the monitoring parameters of the one or more candidate cells is included in the Physical Uplink Shared Channel (PUSCH), and the instructions further include instructions for configuring the first network entity to: transmit an uplink (UL) grant to the UE having the same Hybrid Automatic Repeat Request (HARQ) Procedure Identifier (ID) as the PUSCH.

[0198] Clause 61. The first network entity as described in Clause 59, wherein the instructions for configuring the first network entity to transmit the response include instructions for configuring 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.

[0199] Clause 62. An apparatus comprising: a communication controller; and a processing system configured to control the communication controller to implement any of the methods described in Clauses 1 to 31.

[0200] It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X or Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and Y". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "B only". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "A+B" or "B+A".

[0201] It should be noted that some or all of the aforementioned or following implementations may be combined or combined to form a new or another implementation.

[0202] It should be noted that the foregoing or following techniques can be used to solve at least (but not limited to) the problems or scenarios mentioned in this disclosure.

[0203] The following additional considerations apply to the foregoing and the following discussion.

[0204] It should be noted that any two or more of the foregoing or following paragraphs, (sub)bullets, points, actions or claims described in each method / technique / implementation may be logically, reasonably and appropriately combined to form a particular method.

[0205] It should be noted that any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the foregoing or following techniques / implementations / concepts may be implemented independently and separately to form a particular method. Dependencies such as “based on,” “more specifically,” “wherein,” etc., in the techniques / implementations / concepts mentioned in this disclosure are merely one possible implementation that does not limit the particular method.

[0206] Certain techniques described in this disclosure are included as logic or multiple components or modules. A module can be a software module (such as code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system or logic (such as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) permanently configured to perform certain operations. A hardware module may also include programmable logic or circuit systems temporarily configured by software to perform certain operations (e.g., contained within a general-purpose processor or other programmable processor). The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0207] As used herein, the terms “component” and “module” are intended to be broadly interpreted 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 interpreted as meaning “at least partially based on”.

[0208] This article describes several aspects in conjunction with thresholds. As used in this article, meeting a threshold can mean that the value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.

[0209] As used herein, the phrase “at least one of” or “one or more of” in the list of references refers to any combination of these items, including a single member. For example, “at least one of the following: a, b, or c” is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

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

[0211] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in connection with the implementations disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed herein and their structural equivalents. The interchangeability of hardware, firmware, and software has been generally described in terms of functionality, and has been illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and design constraints imposed on the system as a whole.

[0212] Hardware and data processing apparatuses for implementing the various illustrative components, logic, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices (PLDs), discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, specific processes, operations, and methods can be performed by a circuit system specific to a given function.

[0213] As described above, in some aspects, implementations of the subject matter described herein can be implemented as software. For example, the various functions of the components disclosed herein, or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein, can be implemented as one or more modules of one or more computer programs. Such computer programs may include non-transitory processor-executable instructions or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or control of, a data processing apparatus including the apparatus 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 can 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 technology may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

[0214] As used herein, the terms “user device,” “user equipment” (e.g., UE 110), “wireless communication device,” “mobile communication device,” “communication device,” or “mobile device” refer to any or all of the following: cellular phone, smartphone, portable computing device, personal or mobile multimedia player, laptop computer, tablet computer, smartbook, Internet of Things (IoT) device, handheld computer, wireless email receiver, cellular phone with multimedia Internet support, wireless game controller, display subsystem, driver assistance system, vehicle controller, vehicle system controller, vehicle communication system, infotainment system, vehicle telematics system or subsystem, vehicle display system or subsystem, vehicle data controller, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device (such as a smartwatch), wireless hotspot, femtocell, broadband router, or other type of router, as well as similar electronic devices including programmable processors and memories configured to perform the operations described herein. Furthermore, in some cases, the user device may be embedded in electronic systems such as a vehicle’s main unit or an advanced driver assistance system (ADAS). Furthermore, mobile internet devices (MIDs). Depending on the type, a user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0215] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are given the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0216] Furthermore, the various features described in this specification in the context of individual implementations can also be implemented in combination within a single implementation. Conversely, the various features described in the context of a single implementation can also be implemented individually or in any suitable sub-combination in multiple implementations. Thus, although features may be described above as functioning in a particular combination and even initially claimed in this way, in some cases one or more features from the claimed combination can be removed from the combination, and the claimed combination may involve sub-combinations or variations of sub-combinations.

[0217] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or requiring all shown operations to be performed to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of a flowchart or table. However, other operations not depicted may be incorporated into the schematically shown example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any shown operations. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the implementations described above should not be construed 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 appended claims. In some cases, the actions set forth in the claims may be performed in a different order and still achieve the desired result.

[0218] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or modifications and variations can be derived from practice of these aspects. Although aspects of this disclosure have been described with reference to various examples, any combination of aspects from any example is also within the scope of this disclosure. The examples in this disclosure are provided for illustrative purposes only.

Claims

1. A method for wireless communication performed by a user equipment (UE) (110A), comprising: Receive (202) a candidate cell monitoring configuration with multiple candidate cell monitoring parameters from network entity (120A); Based on the conditions of the UE, select (208) one or more candidate cell monitoring parameters from the plurality of candidate cell monitoring parameters for modification; as well as Transmit (210) a request to the network entity to update one or more candidate cell monitoring parameters in the candidate cell monitoring parameters.

2. The method of claim 1, further comprising: The condition for detecting the UE includes at least one of the following: The battery level is below the first threshold level; Changes in battery status; The change in the position of the UE; or The heat level is above the second threshold level; and The transmission of the request is based on the conditions stated above.

3. The method as described in any one of claims 1 or 2, wherein, The one or more candidate cell monitoring parameters include at least one of the following: The candidate cells being monitored; The number of candidate cells monitored; Monitored reference signals associated with one or more first candidate cells; The number of monitored reference signals associated with one or more second candidate cells; Monitoring periodicity associated with one or more third candidate cells; or Reporting periodicity associated with one or more fourth candidate cells.

4. The method according to any one of claims 1 to 3, wherein, The candidate cell monitoring configuration is associated with at least one of the following: One or more non-serving cells; One or more deactivated cells; or One or more Layer 1 or Layer 2 cells trigger Mobility LTM candidate cells.

5. The method according to any one of claims 1 to 4, wherein, Selecting the one or more candidate cell monitoring parameters includes selecting the one or more candidate cell monitoring parameters based on rules or machine learning models.

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

7. The method according to any one of claims 1 to 6, wherein, The request to transmit an update of the candidate cell monitoring configuration includes transmitting the request in at least one of the following: Radio Resource Control (RRC) message, User Assistance Information (UAI), Uplink UL Media Access Control (MAC) Control Element (CE), or Uplink Control Information (UCI).

8. The method of claim 7, further comprising: Transmit a scheduling request to the network entity; as well as In response to the scheduling request, a UL authorization is received from the network entity, wherein transmitting the request for updating includes transmitting the UL MAC CE based on the UL authorization.

9. The method of claim 7, wherein, Transmitting the request for updating includes transmitting the request via at least one of the following: Random access preamble on the Physical Random Access Channel (PRACH); Random access request on the Physical Uplink Shared Channel (PUSCH); or The random access message includes both the random access preamble and the random access request.

10. The method according to any one of claims 7 to 9, wherein, The UL MAC CE includes at least one of the following: The first request type indicates that the candidate cell monitoring configuration should be updated; A second request type indicating the type of update to the candidate cell monitoring configuration; The configuration identifier ID that identifies the candidate cell monitoring configuration being modified; One or more candidate cell IDs; One or more reference signal IDs; One or more reference signals are monitored periodically; 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 the following: Candidate cells activated; Deactivate candidate cells; Reference signal RS activated; RS deactivation; RS monitoring updates periodically; or The report is updated periodically.

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

13. The method of claim 12, wherein, The 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 includes a Layer 1 L1 measurement report based on the plurality of reference signals.

15. The method of any one of claims 1 to 14, further comprising at least one of the following: The candidate cell monitoring configuration is updated after a first predetermined time period has elapsed since the request was transmitted. The candidate cell monitoring configuration is updated multiple times consecutively after a second predetermined time period has elapsed following the transmission of the request. The candidate cell monitoring configuration is updated a predetermined number of times after a third predetermined time period has elapsed since the request was transmitted; or The candidate cell monitoring configuration is updated after a fourth predetermined time period has elapsed since the response to the request to update the candidate cell monitoring configuration was received.

16. The method of any one of claims 1 to 15, further comprising: Receive one or more reference signals from one or more candidate cells associated with the candidate cell monitoring configuration; as well as One or more modifications to the monitoring parameters of the one or more candidate cells are calculated based on the one or more reference signals.

17. A method for wireless communication by a first network entity (120A), comprising: Transmit (202) candidate cell monitoring configuration to user equipment (UE) (110A), the candidate cell monitoring configuration specifying one or more candidate cells; The UE receives (208) a request to update one or more candidate cell monitoring parameters of the candidate cell monitoring configuration; as well as A (214) indicator is transmitted to a second network entity (120B) operating at least one of the one or more candidate cells, the indicator indicating modification of resources associated with monitoring parameters of the one or more candidate cells.

18. The method of claim 17, further comprising transmitting (212) a response to the UE to the request for updating the monitoring parameters of the one or more candidate cells, wherein, The response includes at least one of the following: Radio Resource Control (RRC) reconfiguration message; Media access control (MAC) control element (CE); Downlink Control Information (DCI); or Response information.

19. The method of claim 17, wherein, The indicator indicating the modification of resources includes an indicator for releasing resources reserved for cell handover for the UE.

20. An apparatus comprising: Communication controller; as well as A processing system configured to control the communication controller to implement any of the methods described in claims 1 to 19.

Images