Conditional switching based on network energy saving mode

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication of a network energy saving (NES) condition switching threshold. The UE may monitor one or more received signals based at least in part on the NES condition switching threshold. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 501,121, filed May 9, 2023, entitled “CONDITIONAL HANDOVERS BASED ON A NETWORK ENERGY SAVING MODE,” and U.S. Non-Provisional Patent Application No. 18 / 647,195, filed April 26, 2024, entitled “CONDITIONAL HANDOVERS BASED ON A NETWORK ENERGY SAVING MODE,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication, and specifically to techniques and apparatus for conditional switching based on network power-saving modes. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of a network power saving (NES) condition switching condition (e.g., an NES condition switching threshold). The method may include monitoring one or more received signals based at least in part on the NES condition switching threshold.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network node. This method may include sending an indication of NES condition switching conditions (e.g., an NES condition switching threshold).

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the apparatus to receive an indication of NES condition switching conditions (e.g., an NES condition switching threshold). The one or more processors may be configured to cause the apparatus to monitor one or more received signals at least in part based on the NES condition switching threshold.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the apparatus to send indications of NES condition switching conditions (e.g., NES condition switching thresholds).

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive indications of NES condition switching conditions (e.g., an NES condition switching threshold). When executed by one or more processors of the UE, the set of instructions enables the UE to monitor one or more received signals at least in part based on the NES condition switching threshold.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to send indications of NES condition switching conditions (e.g., NES condition switching thresholds).

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving an indication of an NES condition switching threshold. The apparatus may also include components for monitoring one or more received signals, at least in part based on the NES condition switching condition (e.g., the NES condition switching threshold).

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting an indication of NES condition switching conditions (e.g., an NES condition switching threshold).

[0015] The general terms include, as fully described herein with reference to the accompanying drawings and description, and illustrated in the accompanying drawings and description, methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems.

[0016] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to provide a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0017] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 4 This is a diagram illustrating an example of a switchover that follows the present disclosure.

[0023] Figure 5 This is a diagram illustrating an example of a wireless communication process between a source network node, a UE, and a target network node according to this disclosure.

[0024] Figure 6This illustrates the second target network node according to this disclosure and as per the above. Figure 5 A diagram illustrating an example of the wireless communication process between the source network node, the UE, and the target network node.

[0025] Figure 7 This is a diagram illustrating an example procedure performed by a UE according to this disclosure, for example.

[0026] Figure 8 This is a diagram illustrating an example process performed, for example, by a network node according to this disclosure.

[0027] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure.

[0028] Figure 10 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0029] Switching a network node to Network Energy Saving (NES) mode may cause one or more inefficiencies during handover. For example, as part of the switch to NES mode, the source network node may offload attached User Equipment (UE) and / or multiple UEs to other network nodes. To offload a UE, the network node may send a corresponding Radio Resource Control (RRC) reconfiguration message to each UE, which instructs the UE to perform a handover. Sending multiple RRC reconfiguration messages may delay the source network node's switch to NES mode, delay UE handover, increase the source network node's power consumption, increase the UE's power consumption, and / or reduce the UE's battery life, as described below.

[0030] Alternatively or additionally, the target network node may notify the source network node that the target network node is transitioning to NES mode, and the source network node may change one or more conditional handover conditions associated with the target network node to mitigate UE-triggered conditional handover to the target network node. However, in a similar manner to the above, the source network node sends a corresponding RRC reconfiguration message to each UE, which indicates an update to one or more conditional handover conditions associated with the target network node. Sending multiple RRC reconfiguration messages may delay UE handover, increase UE power consumption, and / or reduce UE battery life, as described below.

[0031] The various aspects described herein generally relate to conditional handover based on NES mode. More specifically, some aspects relate to reducing signaling overhead in conditional handover based at least partially on NES mode. In some aspects, the UE may receive an indication of NES conditional handover conditions, such as an NES conditional handover threshold. As described below, the NES conditional handover may differ from the UE's baseline conditional handover threshold and / or current conditional handover. Based at least partially on receiving an indication of an NES conditional handover threshold, the UE may monitor and / or evaluate one or more received signals based at least partially on the NES conditional handover threshold. For example, the UE may detect a conditional handover triggering event based at least partially on the NES conditional handover threshold, and / or the UE may perform a conditional handover to a target network node. Alternatively, the UE may not detect the occurrence of a conditional handover triggering event (e.g., based at least partially on the NES conditional handover threshold) and may subsequently avoid performing a conditional handover to a target network node.

[0032] In some aspects, network nodes may send indications of NES conditional handover conditions, such as NES conditional handover thresholds. For example, network nodes may use a mechanism different from RRC signaling to send indications of NES conditional handover, such as sending indications of NES conditional handover in Layer 1 (L1) signaling and / or Layer 2 (L2) signaling. In some aspects, the indication of an NES conditional handover threshold may be an indication of changes to existing conditional handover configurations and / or existing conditional handover thresholds. That is, the NES conditional handover threshold may indicate changes (e.g., offsets) applied to the current conditional handover threshold.

[0033] Using NES conditional handover conditions (e.g., NES conditional handover thresholds) enables the source network node to offload attached UEs and / or provide (e.g., associated with the target network node) updated conditional handover thresholds using mechanisms different from RRC signaling (e.g., RRC reconfiguration messages). Therefore, the source network node can offload attached UEs and / or mitigate UE handovers to the target network node operating in NES mode, at least in part, using fewer RRC messages and / or less RRC signaling. Reducing RRC signaling allows the source network node to reduce power consumption and / or transition to NES mode more quickly. As an example of reduced power consumption, the source network node can shrink the coverage area it provides more quickly. In some respects, reducing RRC signaling can mitigate the use of complementary RRC signaling (e.g., RRC reconfiguration complete messages) by each UE in response, reducing UE power consumption and preserving UE battery life.

[0034] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0035] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0036] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0037] Figure 1This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0038] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0039] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0040] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

[0041] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions for other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, relay, etc.

[0042] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0043] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0044] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0045] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0046] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0048] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0049] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive indications of NES condition switching conditions (e.g., NES condition switching thresholds); and monitor one or more received signals at least in part based on the NES condition switching thresholds. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send indications of NES condition switching conditions (e.g., NES condition switching thresholds). Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0053] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0054] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0055] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0056] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

[0057] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0058] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements and / or be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0059] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 4 to 10 ( ) any aspect of the methods described in the method.

[0060] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). Figures 4 to 10 ( ) any aspect of the methods described in the method.

[0061] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may perform one or more techniques associated with conditional switching based on network power saving modes, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 7 The process 700 Figure 8 The operation of process 800 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 7 The process 700 Figure 8 The operation of process 800 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0062] In some aspects, the UE (e.g., UE 120) includes components for receiving indications of NES condition switching conditions (e.g., NES condition switching thresholds); and / or components for monitoring one or more received signals at least in part based on the NES condition switching thresholds. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0063] In some aspects, a network node (e.g., network node 110) includes components for sending indications of NES condition switching conditions (e.g., NES condition switching thresholds). Components for the network node to perform the operations described herein may include one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0064] Although Figure 2The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0065] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0066] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0067] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0068] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed individually. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0069] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0070] Each unit in the clusters (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cluster, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other clusters via transmission media. In some examples, each unit in the cluster may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other clusters, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other clusters, or both.

[0071] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include RRC functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU330 for network control and signaling purposes, as needed.

[0072] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0073] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0074] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0075] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

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

[0077] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0078] Figure 4 This is a diagram illustrating example 400 of the first-to-end switching according to this disclosure.

[0079] like Figure 4As shown, the MBB (Maintain-Before-Disconnect) handover process may involve UE 405, source network node 410, target network node 415, User Plane Function (UPF) device 420, and Access and Mobility Management Function (AMF) device 425. In some examples, actions described as being performed by network nodes may be performed by multiple different network nodes. For example, configuration actions and / or core network communication actions may be performed by a first network node (e.g., CU or DU), and radio communication actions may be performed by a second network node (e.g., DU or RU). UE 405 may correspond to UE 120 as described elsewhere herein. Source network node 410 and / or target network node 415 may correspond to network node 110 as described elsewhere herein. UPF device 420 and / or AMF device 425 may correspond to network controller 130 as described elsewhere herein. UE 405 and source network node 410 may be connected via a serving cell or source cell (e.g., may have an RRC connection), and UE 405 may undergo a handover via the target cell to the target network node 415. UPF device 420 and / or AMF device 425 may be located within the core network. Source network node 410 and destination network node 415 may communicate with the core network for mobility support and user plane functions. The MBB handover process may include an enhanced MBB (eMBB) handover process.

[0080] As shown in the figure, the MBB handover process may include a handover preparation phase 430, a handover execution phase 435, and a handover completion phase 440. During the handover preparation phase 430, the UE 405 may report measurements that prepare the source network node 410 and / or the target network node 415 for handover and trigger handover execution. During the handover execution phase 435, the UE 405 may perform the handover by executing a random access procedure with the target network node 415 and establishing an RRC connection with the target network node 415. During the handover completion phase 440, the source network node 410 may forward stored communications associated with the UE 405 to the target network node 415, and the UE 405 may be released from the connection with the source network node 410.

[0081] As indicated by reference numeral 445 in the accompanying drawings, UE 405 may perform one or more measurements and may send a measurement report to source network node 410 based at least in part on performing one or more measurements (e.g., serving cell measurement and / or neighbor cell measurement). The measurement report may indicate parameters such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), and / or Signal-to-Interference-plus-Noise Ratio (SINR) parameters (e.g., for the serving cell and / or one or more neighbor cells). Source network node 410 may use the measurement report to determine whether to trigger a handover to target network node 415. For example, source network node 410 may trigger a handover from UE 405 to target network node 415 if one or more measurements meet certain conditions. In some aspects, UE 405 may perform measurements and / or generate measurement reports based at least in part on a measurement configuration received from source network node 410. For example, source network node 410 may use the measurement configuration to indicate one or more parameters associated with performing the measurement, such as any combination of frequency position, time position, and / or subcarrier offset.

[0082] As shown by reference numeral 450 in the attached figure, the source network node 410 and the target network node 415 can communicate with each other to prepare for the handover of UE 405. As part of the handover preparation, the source network node 410 can send a handover request to the target network node 415 to instruct the target network node 415 to prepare for the handover. The source network node 410 can communicate to the target network node 415 the RRC context information associated with UE 405 and / or the configuration information associated with UE 405. The target network node 415 can prepare for the handover by reserving resources for UE 405. After reserving resources, the target network node 415 can send an acknowledgment (ACK) to the source network node 410 in response to the handover request.

[0083] As shown by reference numeral 455 in the attached figure, the source network node 410 may send an RRC reconfiguration message to the UE 405. The RRC reconfiguration message may include a handover command instructing the UE 405 to perform a handover procedure from the source network node 410 to the target network node 415. The handover command may include information associated with the target network node 415, such as the assignment of a Random Access Channel (RACH) preamble for accessing the target network node 415. Reception of the RRC reconfiguration message including the handover command by the UE 405 may trigger the start of the handover execution phase 435.

[0084] As shown by reference numeral 460 in the attached figure, during the handover execution phase 435 of the MBB handover, the UE 405 can perform the handover by performing a random access procedure with the target network node 415 (e.g., including synchronization with the target network node 415) while continuing to communicate with the source network node 410. For example, when the UE 405 performs the random access procedure with the target network node 415, the UE 405 may send uplink data, uplink control information, and / or uplink reference signals (e.g., probe reference signals) to the source network node 410, and / or may receive downlink data, downlink control information, and / or downlink reference signals from the source network node 410.

[0085] As shown by reference numeral 465 in the attached figure, after successfully establishing a connection with the target network node 415 (e.g., via a random access procedure), the UE may send an RRC reconfiguration complete message to the target network node 415. The receipt of the RRC reconfiguration message by the target network node 415 may trigger the start of the handover completion phase 440.

[0086] As shown by reference numeral 470 in the accompanying drawings, the source network node 410 and the target network node 415 can communicate with each other to prepare for releasing the connection between the source network node 410 and the UE 405. In some aspects, such as after receiving an RRC reconfiguration message from the UE 405, the target network node 415 can determine that the connection between the source network node 410 and the UE 405 is to be released. In this case, the target network node 415 can send a handover connection establishment complete message to the source network node 410. The handover connection establishment complete message can cause the source network node 410 to stop sending data to the UE 405 and / or stop receiving data from the UE 405. Additionally or alternatively, the handover connection establishment complete message can cause the source network node 410 to forward communications associated with the UE 405 to the target network node 415 and / or notify the target network node 415 of the status of one or more communications with the UE 405. For example, source network node 410 may forward buffered downlink communications (e.g., downlink data) for UE 405 and / or uplink communications (e.g., uplink data) received from UE 405 to target network node 415. Additionally or alternatively, source network node 410 may notify target network node 415 of the Packet Data Convergence Protocol (PDCP) status associated with UE 405 and / or the sequence number to be used for downlink communications with UE 405.

[0087] As shown by reference numeral 475 in the attached figure, the target network node 415 may send an RRC reconfiguration message to the UE 405 to instruct the UE 405 to release the connection with the source network node 410. Upon receiving the instruction to release the connection with the source network node 410, the UE 405 may cease communication with the source network node 410. For example, the UE 405 may avoid sending uplink communication to the source network node 410 and / or may avoid monitoring downlink communication from the source network node 410.

[0088] As shown by reference numeral 480 in the attached figure, the UE may send an RRC reconfiguration complete message to the target network node 415 to indicate that the connection between the source network node 410 and the UE 405 is being released or has been released.

[0089] As shown by reference numeral 485 in the attached figure, the target network node 415, the UPF device 420, and / or the AMF device 425 can communicate to switch the user plane path of UE 405 from the source network node 410 to the target network node 415. Before the user plane path is switched, downlink communication for UE 405 can be routed to the source network node 410 via the core network. After the user plane path is switched, downlink communication for UE 405 can be routed to the target network node 415 via the core network. Upon completion of the user plane path switch, the AMF device 425 can send an end marker message to the source network node 410 to notify the completion of the user plane path switch. As shown by reference numeral 490 in the attached figure, the target network node 415 and the source network node 410 can communicate to release the source network node 410.

[0090] As part of the MBB handover process, UE 405 may maintain simultaneous connections with both the source network node 410 and the target network node 415 during a time period 495. The time period 495 may begin at the start of the handover execution phase 435 (e.g., after UE 405 receives a handover command from the source network node 410) when UE 405 performs a random access procedure with the target network node 415. The time period 495 may end when the connection between UE 405 and the source network node 410 is released (e.g., when UE 405 receives an instruction to release the source network node 410 from the target network node 415). By maintaining simultaneous connections with both the source network node 410 and the target network node 415, the handover process can be performed with zero or minimal communication interruptions, thereby reducing latency.

[0091] In some aspects, UE 405 may perform a conditional handover based at least in part on UE 405 detecting that a conditional handover condition has been met. Exemplarily, source network node 410 may indicate one or more conditional handover conditions that could trigger UE 405 to initiate a conditional handover. A first example of a conditional handover condition is an A3 threshold, which indicates that a first signal level (e.g., RSRP metric) associated with a first signal received from a neighboring network node is better by an offset (e.g., signal level offset) than a second signal level associated with a second signal received from the source network node. A second example of a conditional handover condition is an A5 threshold, which indicates that the first signal level associated with a neighboring network node has become greater than a first signal metric threshold, and the second signal level associated with the source network node has fallen below a second threshold. In some aspects, source network node 410 may indicate the conditional handover condition in RRC signaling (such as RRC signaling associated with sending an RRC reconfiguration message), as described with respect to reference numeral 455. UE 405 may trigger a conditional handover to target network node 415, at least in part based on the detection that a first example of the A3 threshold and / or conditional handover conditions has been met. Alternatively or additionally, UE 405 may trigger a conditional handover to target network node 415, at least in part based on the determination that a second example of the A5 threshold and / or conditional handover conditions has been met. Thus, the source network node may indicate the conditional handover conditions, and UE 405 may initiate a conditional handover at least in part based on the determination that the conditional handover conditions have been met.

[0092] Switching a network node to NES mode may cause one or more inefficiencies during the handover process. For example, a network node (e.g., source network node 410 and / or target network node 415) may switch to NES mode during off-peak hours (e.g., periods when the load and / or traffic supported by the network node meets smaller traffic thresholds), during maintenance procedures, and / or at least partially based on instructions from the core network. As part of the switch to NES mode, a network node may offload attached UEs to another network node. For example, the network node may send a corresponding RRC reconfiguration message to each UE, instructing the UE to perform a handover. However, sending multiple RRC reconfiguration messages may delay the network node's switch to NES mode and / or delay the UE's handover. For example, the network node may avoid sending RRC reconfiguration messages to the corresponding UEs until after the network node receives a measurement report from the corresponding UE. In some aspects, signaling each UE to send an RRC reconfiguration message may increase the network node's energy consumption. Therefore, switching to NES mode can be costly in terms of energy consumption, at least in part based on the number of RRC reconfiguration messages sent by the network node, and / or potentially costly in terms of time, at least in part based on the latency incurred by both the network node and the UE. Alternatively or additionally, the network node may switch from Discontinuous Transmit (DTX) mode and / or Discontinuous Receive (DRX) mode to acquire sufficient air interface resources to send multiple RRC reconfiguration messages, which may also increase the network node's energy consumption. Each UE can respond to RRC reconfiguration messages with an RRC reconfiguration complete message, resulting in increased UE energy consumption and reduced UE battery life.

[0093] In some respects, the target network node may (e.g., via a backhaul link) notify the source network node that the target network node is transitioning to NES mode. Based at least in part on receiving information indicating that the target network node is transitioning to NES mode, the source network node may modify one or more conditional handover conditions associated with the target network node to mitigate UE-triggered conditional handover to the target network node. For example, the source network node may change offsets and / or thresholds (e.g., A3 threshold and / or A5 threshold) to values ​​that prevent UE-triggered conditional handover. However, in a similar manner to the above, the source network node may update the offsets and / or thresholds at least in part based on sending a corresponding RRC reconfiguration message to each UE, increasing the source network node's power consumption. Alternatively or additionally, each UE may respond to the RRC reconfiguration message using an RRC reconfiguration completion message, thereby increasing UE power consumption and shortening UE battery life.

[0094] Some of the technologies and apparatus described herein provide conditional handover based on NES mode. In some aspects, the UE may receive an indication of NES conditional handover conditions, such as an NES conditional handover threshold. As described below, the NES conditional handover threshold may be associated with a conditional handover triggering event (e.g., a conditional handover condition being met), which is associated with a network node (e.g., a source network node and / or a target network node) operating in NES mode. Based at least in part on receiving an indication of the NES conditional handover threshold, the UE may monitor and / or evaluate one or more received signals based at least in part on the NES conditional handover threshold. For example, the UE may detect a conditional handover triggering event based at least in part on the NES conditional handover threshold, and / or the UE may perform a conditional handover to the target network node. Alternatively, the UE may not detect the occurrence of a conditional handover triggering event (e.g., based at least in part on the NES conditional handover threshold), and may subsequently avoid performing a conditional handover to the target network node.

[0095] In some aspects, network nodes may send indications of NES conditional handover conditions, such as NES conditional handover thresholds. For example, a network node may use a mechanism different from RRC signaling (such as RRC signaling associated with sending an RRC reconfiguration message) to send indications of NES conditional handover. Exemplarily, a network node may send indications of NES conditional handover in Layer 1 (L1) signaling and / or Layer 2 (L2) signaling. As another example, the indication of NES conditional handover may indicate the selection of a specific NES conditional handover threshold from a plurality of NES conditional handover thresholds, and / or the selection of a specific conditional handover configuration from a plurality of conditional handover configurations, as described below. In some aspects, a conditional handover configuration may specify any combination of conditional handover conditions (e.g., triggering events), conditional handover criteria (e.g., cell selection criteria for conditional handover), and / or conditional handover thresholds.

[0096] Using NES conditional handover thresholds allows a source network node to offload attached UEs without sending corresponding RRC signaling to each UE instructing it to perform a handover. For example, using L1 signaling, L2 signaling, and / or System Information Blocks (SIBs) as described below, a source network node can send a first NES conditional handover threshold that increases the conditional handover threshold associated with the source network node, causing the UE to trigger a conditional handover to the target network node. Therefore, compared to the RRC signaling described with respect to Example 400, the source network node can use less RRC signaling and / or lower latency to offload attached UEs. Reducing RRC signaling allows the source network node to reduce power consumption and / or transition to NES mode more quickly. Alternatively or additionally, a faster transition to NES mode allows the source network node to shrink the coverage area it provides more quickly and reduce its power consumption. In some respects, reducing RRC signaling allows the UE to perform faster handovers, which reduces service interruptions and / or alleviates the need for the UE to use complementary RRC signaling (e.g., RRC reconfiguration complete messages) to respond. Reducing RRC signaling also lowers UE power consumption and maintains UE battery life.

[0097] Signaling the NES conditional handover threshold via a mechanism different from RRC signaling allows the source network node to indicate a second NES conditional handover threshold that increases the conditional handover threshold associated with the target network node and mitigates the conditional threshold triggered by the UE at the target network node. In other words, the source network node can use less RRC signaling than that described with respect to Example 400 to indicate the NES conditional handover threshold, reducing UE power consumption and / or preserving UE battery life. Alternatively or additionally, if another network node is available, the NES conditional handover threshold can enable the UE to avoid selecting a network node operating in NES mode for handover.

[0098] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0099] Figure 5 This is a diagram illustrating an example 500 of a wireless communication process between a source network node 502 (e.g., network node 110), a UE 504 (e.g., UE 120), and a target network node 506 (e.g., another node 110) according to this disclosure.

[0100] As indicated by reference numeral 510 in the accompanying drawings, source network node 502 and UE 504 may establish a communication link with each other. As part of establishing the communication link and / or at least in part based on establishing the communication link, source network node 502 may send information to UE 504, and / or UE 504 may send information to source network node 502. For example, UE 504 may indicate support for NES conditional handover procedures (e.g., the use and / or dynamic configuration of NES conditional handover thresholds). Exemplarily, UE 504 may indicate support for NES conditional handover procedures in UE capability information. Alternatively or additionally, UE 504 may indicate support for NES conditional handover procedures in messages sent separately from UE capability information (e.g., L1 messages, L2 messages, and / or Layer 3 (L3) messages). NES conditional handover procedures may include UE 504 receiving an indication of an NES conditional handover threshold, and / or at least in part based on monitoring received signals using the NES conditional handover threshold, as described below.

[0101] The baseline condition switching threshold may be associated with condition switching conditions (e.g., A3 threshold and / or A5 threshold) based at least in part on network nodes operating in active mode and / or non-NES mode. The baseline condition switching threshold may also be referred to as the non-NES condition switching threshold. In some aspects, the NES condition switching threshold may be associated with the same condition switching conditions (e.g., A3 threshold and / or A5 threshold) and may be based at least in part on the same network nodes operating in NES mode. For example, and as described below, the NES condition switching threshold may be an offset applied to the baseline condition switching threshold and / or the current condition switching threshold based at least in part on the associated network nodes operating in NES mode. Having different configurations and / or modes for condition switching conditions (such as a baseline condition switching threshold for a first operating mode and an NES condition switching threshold for a second operating mode) allows network nodes to modify the limits of the condition switching conditions as the operating modes of the source network node and / or the target network node change. For example, regarding the A5 threshold, the network node may increase the first signal level threshold associated with the target network node, at least in part, based on the target network node switching to NES mode and reducing the second signal level associated with the source network node. Increasing the first signal level threshold associated with the target network node can mitigate the UE performing a conditional handover to the target network node. Alternatively or additionally, regarding the A5 threshold, the network node may decrease the first signal level threshold associated with the target network node and increase the second signal level associated with the source network node, at least in part, based on the source network node switching to NES mode. Increasing the second signal level threshold associated with the source network node can cause the UE to perform a conditional handover from the source network node to the target network node. Therefore, the NES conditional handover threshold can be a conditional handover threshold and / or conditional handover condition associated with a network node operating in NES mode.

[0102] Based at least in part on establishing a communication link with UE 504, source network node 502 may send indications of multiple conditional handover configurations and / or NES conditional handover conditions (e.g., NES conditional handover thresholds) for future selection. In other words, source network node 502 may indicate multiple options for conditional handover configurations and / or NES conditional handover thresholds after establishing a communication link with UE 504, and, as described with respect to reference numeral 520, may indicate the selection of one of the multiple options. By sending multiple options before selecting a particular option, source network node 502 may indicate the selected option (e.g., a specific conditional handover configuration and / or a specific NES conditional handover threshold) based at least in part on using a communication mechanism faster than RRC signaling (e.g., L1 messages and / or L2 messages).

[0103] As an example of indicating multiple options, source network node 502 may use RRC signaling to send one or more tables (e.g., one or more RRC-configured tables), and the tables may include multiple conditional handover configurations. Each conditional handover configuration may be associated with any combination of conditional handover conditions (e.g., triggering events), conditional handover criteria (e.g., cell selection criteria for conditional handover), and / or conditional handover thresholds. Conditional handover thresholds (e.g., NES conditional handover thresholds and / or baseline conditional handover thresholds) may be based at least in part on an offset associated with any combination of timing thresholds, power level thresholds, signal level thresholds, and / or quality thresholds. For example, source network node 502 may send one or more non-NES mode conditional handover configurations associated with network nodes operating in non-NES mode (e.g., source network node and / or target network node) as at least a portion of a table. Alternatively or additionally, source network node 502 may send one or more source network node NES conditional handover configurations associated with a source network node operating in NES mode as at least a portion of a table. In some aspects, source network node 502 may send one or more target network node NES condition switching configurations associated with one or more target network nodes operating in NES mode as at least part of a table. As described with respect to reference numeral 520, source network node may indicate (e.g., from multiple condition switching configurations) the selected condition switching configuration as at least part of an indication of an NES condition switching threshold.

[0104] As another example of indicating multiple options, source network node 502 may send one or more conditional handover configurations, one or more NES conditional handover thresholds, and / or one or more cell selection criteria in a System Information Block (SIB). Exemplarily, network node 502 may send SIB1, SIB2, and / or SIB4 indicating cell selection criteria. Some non-limiting examples of cell selection criteria may include signal strength criteria (e.g., signal strength threshold, RSRP threshold, and / or denoted as Srxlev), signal quality criteria (e.g., signal quality threshold, RSRQ threshold, and / or denoted as Squal), and / or offset criteria (e.g., those temporarily applied when evaluating cells and / or denoted as Qoffset). tempThe cell selection criteria indicated by the SIB may be associated with RRC idle state and / or RRC inactive state, and the source network node 502 may (e.g., implicitly or explicitly) indicate that the cell selection criteria associated with RRC idle state be reused as NES cell selection criteria. Alternatively or additionally, the cell selection criteria in the SIB may explicitly indicate NES cell selection criteria (e.g., offset and / or NES conditional handover threshold). Exemplarily, the SIB may include cell selection criteria (e.g., Q) associated with the conditional handover of a target cell operating in NES mode. CHO-NES-offset In other words, Q CHO-NES-offset Conditional handover conditions and / or evaluations may be applied (e.g., by the UE) to one or more active and / or configured conditions. Alternatively or additionally, cell selection criteria may be cell reselection criteria. In some aspects, NES conditional handover thresholds may be associated with and / or at least partially based on cell selection criteria. For example, a first NES conditional handover threshold may be associated with a first cell selection criterion, and a second NES conditional handover threshold may be associated with a second cell selection criterion.

[0105] Alternatively or additionally, the source network node 502 may send an NES SIB (e.g., including an NES Information Element (IE) and / or an SIB with an SIB format associated with indicating NES condition handover conditions, such as NES condition handover threshold information), which may indicate multiple options for future selection. However, in other examples, the source network node 502 may send SIBs (e.g., SIB1, SIB2, SIB4, and / or NES SIBs) to indicate NES condition handover thresholds, as described below with respect to reference numeral 520. Exemplarily, the NES SIB may include DTX information associated with a network node (e.g., on duration, on start time, off duration, off start time, and / or duty cycle), DRX information associated with a network node (e.g., on duration, on start time, off duration, off start time, and / or duty cycle), cell selection offset (and / or cell reselection offset) associated with a network node, and / or any combination of NES condition handover thresholds associated with a network node. The NES SIB may include DTX information, DRX information, cell selection offset, and / or NES conditional handover thresholds that are generally applicable and / or applicable to a group and / or all network nodes, or the NES SIB may include DTX information, DRX information, cell selection offset, and / or NES conditional handover thresholds specific to a particular network node. Therefore, the SIB (e.g., the NES SIB) may indicate any combination of serving network node NES information (e.g., DTX information, DRX information, cell selection offset, and / or NES conditional handover thresholds), such as server network node NES information associated with source network node 502, target network node NES information, and / or general network node NES information. As described above, NES network node information may include NES conditional handover threshold information and / or incremental conditional handover threshold information. For example, NES network node information (e.g., source network node and / or target network node) may include any combination of a first offset associated with evaluating multiple and / or all condition switching conditions, a second offset associated with an A3 threshold, a third offset associated with an A4 threshold, and / or a fourth offset associated with an A5 threshold.

[0106] In some aspects, the serving network node NES information may indicate multiple configurations for a single condition switching condition associated with the serving network node. For example, a first configuration for the A3 threshold may be associated with a serving network node operating in normal and / or non-NES mode (e.g., source network node 502), and a second configuration for the A3 threshold may be associated with a serving network node operating in NES mode. Therefore, the serving network node NES information may indicate multiple offset values ​​for the condition switching condition as multiple configurations. Alternatively or additionally, the serving network node NES information may include multiple configurations for multiple condition switching conditions, such as a first set of configurations for a first condition switching condition (e.g., a first configuration for a first operating mode of the network node and a second configuration for a second operating mode of the network node), a second set of configurations for a second condition switching condition, and / or a third set of configurations for a third condition switching condition. In a similar manner to the source network node NES information, the target network node NES information may indicate multiple configurations for a single condition switching condition associated with a target network node (e.g., target network node 506) and / or multiple configurations for multiple condition switching conditions. In some aspects, the target network node NES information may indicate multiple condition switching conditions and / or multiple configurations for different target network nodes, such as one or more configurations for a first NES condition switching condition (e.g., a first A3 threshold) associated with a first target network node, and one or more configurations for a second NES condition switching condition (e.g., a second A3 threshold) associated with a second target network node. The source network node 502 may selectively include target network node NES information, at least in part, based on which target network nodes support transitioning to NES mode. In other words, the source network node 502 may include only target network node NES information for target network nodes capable of transitioning to NES mode.

[0107] As indicated by reference numeral 520 in the accompanying drawings, source network node 502 may send an indication of NES conditional handover conditions (e.g., NES conditional handover threshold), and UE 504 may receive an indication of NES conditional handover conditions (e.g., NES conditional handover threshold). In some aspects, source network node 502 may send the indication of the NES conditional handover threshold at least in part based on UE 504 indicating support for the NES conditional handover procedure. Source network node 502 may send the indication of the NES conditional handover threshold at least in part based on determining a transition to NES mode. Again, as per [reference to...] Figure 6As described, source network node 502 may send an indication of an NES condition switching threshold based at least in part on receiving a message from a target network node indicating that the target network node is transitioning to NES mode. Therefore, source network node 502 may instruct the configuration used for the condition switching condition to switch to an NES configuration (e.g., the NES condition switching threshold). Alternatively or additionally, source network node 502 may send (e.g., explicitly or implicitly) an instruction to begin evaluating network nodes (e.g., source network node 502 and / or target network node 506) based at least in part on the NES condition switching. Exemplarily, sending an indication of an NES condition switching threshold may implicitly instruct the start of evaluating network nodes using the NES condition switching threshold. Alternatively or additionally, source network node 502 may send L1 signaling and / or L2 signaling (e.g., broadcast messages, multicast messages, and / or unicast messages) explicitly associated with the instruction to begin evaluating network nodes using the NES condition switching threshold, as described below.

[0108] In some aspects, the indication sent by the source network node 502 may indicate (e.g., from a plurality of options indicated by the source network node 502) the selected NES conditional handover threshold, as described with respect to reference numeral 510. Alternatively or additionally, the indication sent by the source network node 502 may include and / or indicate the NES conditional handover threshold and / or NES conditional handover information. In other words, in some aspects, the source network node 502 may not send the plurality of options as described with respect to reference numeral 510, but may instead send the NES conditional handover threshold. The source network node 502 may send the indication in broadcast messages, multicast messages (e.g., multicast messages), and / or unicast messages. Exemplarily, the source network node 502 may send the indication in L1 multicast messages and / or L2 multicast messages destined for UEs that support the NES conditional handover procedure. Alternatively or additionally, the source network node 502 may avoid sending the indication to UEs that do not support the NES conditional handover procedure.

[0109] In some aspects, NES conditional handover thresholds may be based at least in part on offsets (e.g., differences from a baseline and / or increments), such as a first offset associated with a power level (e.g., a SINR threshold), a second offset associated with a signal level (e.g., an RSRP threshold), a third offset associated with a quality level (e.g., an RSRQ threshold), and / or a fourth offset associated with a time period (e.g., a timeToTrigger threshold associated with a conditional handover condition). Exemplarily, source network node 502 may indicate a baseline conditional handover threshold associated with the conditional handover conditions of network nodes (e.g., source network node 502 and / or target network node 506) operating in active mode and / or non-NES mode. Alternatively or additionally, source network node 502 may indicate NES conditional handover thresholds (e.g., offsets) and / or incremental conditional handover thresholds that UE 504 may use to configure and / or evaluate conditional handover conditions. By sending an offset, source network node 502 can implicitly instruct the generation of a modified conditional handover threshold by applying the offset to (e.g., adding and / or subtracting) the baseline conditional handover threshold and / or the current conditional handover threshold being used by UE 504. Source network node 502 can also instruct the use of the modified conditional handover threshold to evaluate candidate cells (e.g., for conditional handover) and / or identify measurement report triggering events (e.g., measurement report triggering events associated with reporting measurement reports, such as those related to...). Figure 4 (As described by reference numeral 445 in the accompanying drawings). In other respects, source network node 502 may indicate the absolute value of an NES conditional switching threshold. The NES conditional switching threshold may be based at least in part on a power level criterion (e.g., a threshold), a signal level criterion, a quality level criterion, and / or a time criterion.

[0110] In some aspects, source network node 502 may indicate a network node-specific NES conditional handover threshold. Exemplarily, source network node 502 may indicate an NES source network node offset (e.g., a source network node NES conditional handover threshold) as an NES conditional handover threshold to be applied (e.g., added to or subtracted from the latter) to a non-NES source network node conditional threshold condition. Alternatively or additionally, source network node 502 may indicate an NES target network node offset (e.g., a target network node NES conditional handover threshold) as an NES conditional handover threshold to be applied to a non-NES target network node conditional threshold condition. In some aspects, source network node 502 may indicate multiple NES conditional handover thresholds, and each NES conditional handover threshold may be associated with a corresponding cell selection criterion. For example, a first NES conditional handover threshold may be associated with a first cell selection criterion, and a second NES conditional handover threshold may be associated with a second cell selection criterion. Thus, source network node 502 may indicate multiple NES conditional handover thresholds, and each NES conditional handover threshold may be associated with a corresponding network node and / or a corresponding cell selection criterion.

[0111] In some aspects, the source network node 502 may indicate the NES conditional switching threshold at least in part based on sending an indication to select from multiple options (e.g., multiple conditional switching configurations and / or multiple NES conditional switching thresholds). For example, the source network node 502 may send an indication to an index that maps to an entry in a table (such as an RRC configuration table), as described with respect to reference numeral 510. Alternatively or additionally, the source network node 502 may indicate the NES conditional switching threshold as a first configuration in the serving network node NES information and / or a second configuration in the target network node NES information indicated in the selected NES SIB. Sending an indication to select from multiple options reduces the amount of air interface resources used by the source network node 502 to indicate the NES conditional switching threshold at least in part based on an index using fewer data bits. Using fewer data bits allows the source network node 502 to quickly indicate the NES conditional switching threshold, and using fewer air interface resources allows the source network node 502 to allocate more air interface resources to other uses.

[0112] Source network node 502 may use a mechanism different from RRC signaling to send an indication of the NES conditional handover threshold. For example, source network node 502 may use a mechanism different from the RRC signaling associated with the RRC reconfiguration message to indicate the NES conditional handover threshold, such as regarding... Figure 5As described by reference numeral 455. For example, source network node 502 may send an indication of the NES conditional handover threshold as a broadcast message in L1 signaling (e.g., downlink control information (DCI)) and / or L2 signaling (e.g., MAC control element (CE)). For example, as described above, source network node 502 may send an index mapped to an entry in a table in L1 signaling and / or L2 signaling. As another example, source network node 502 may indicate the selection of at least one of a plurality of conditional handover configurations indicated in the NES SIB, as described with respect to reference numeral 510. Alternatively or additionally, source network node 502 may send an indication in an SIB (such as SIB1, SIB2, SIB3, SIB4 and / or NES SIB as described above) to indicate the NES conditional handover threshold.

[0113] In some respects, UE 504 may recover the SIB at least in part based on the detection of an SIB acquisition trigger event, and subsequently recover the indication of the NES conditional handover threshold. In other words, UE 504 may avoid recovering at least some SIB transmissions at least in part based on the absence of a detected SIB acquisition trigger event. Some non-limiting examples of SIB acquisition trigger events may include periodic timer expiration, receipt of an SIB update indication, and / or detection that the source network node signal level fails to meet a quality threshold. Exemplarily, UE 504 may internally configure a periodic timer and proactively acquire the SIB at least in part based on timer expiration. As another example, UE 504 may proactively acquire the SIB at least in part based on the source network node signal level failing to meet a quality threshold. Alternatively or additionally, UE 504 may receive an SIB update indication from source network node 502 in an L1 broadcast message and / or L1 multicast message, and acquire the SIB at least in part based on receiving the SIB update indication. Therefore, UE 504 may recover the indication of the NES conditional handover threshold from the SIB.

[0114] Alternatively or additionally, UE 504 may restore the SIB based at least in part on the UE 504's operating state. For example, UE 504 may determine that the current operating state includes both RRC connected state and UE 504 operating at the cell edge. In some aspects, UE 504 may use one or more parameters of the RRC configuration to determine that the current operating state includes cell edge operation, such as the CellEdgeEvaluation-r16 standard included in the Information Element (IE). Based at least in part on the current operating state satisfying both RRC connected state and cell edge operation, UE 504 may restore the SIB and subsequently restore the NES conditional handover threshold. By restoring the SIB based at least in part on being in RRC connected state, unnecessary signaling and / or updates can be avoided when the UE is operating in RRC idle state and / or RRC inactive state. Alternatively or additionally, by restoring the SIB at least partially based on operating at the cell edge and subsequently avoiding SIB restoration at least partially based on not operating at the cell edge, unnecessary signaling and / or updates can be avoided when the UE operates in a cell coverage area that is unlikely to change when the network node switches to NES mode.

[0115] As indicated by reference numeral 530, UE 504 may monitor one or more signals at least in part based on an indication of an NES conditional handover threshold. In some aspects, UE 504 may begin monitoring signals using the NES conditional handover threshold at least in part based on receiving an instruction to begin evaluating network nodes (e.g., source network node 502 and / or target network node 506) using the NES conditional handover threshold (e.g., as an offset and / or as an absolute value). Exemplarily, UE 504 may receive the instruction in the same transmission as the NES conditional handover threshold and / or in a separate transmission in L1 signaling and / or L2 signaling. Alternatively or additionally, UE 504 may receive the instruction as a broadcast message, multicast and / or multicast message and / or unicast message. Exemplarily, source network node 502 may send an instruction to begin evaluating signals using the NES conditional handover threshold in an L1 multicast message and / or L2 multicast message addressed to a UE that supports the NES conditional handover process. Alternatively or additionally, source network node 502 may avoid sending instructions to UEs that do not support the NES conditional handover procedure.

[0116] In some respects, UE 504 may apply (e.g., add to or subtract from) an NES conditional switching threshold (e.g., offset) and / or an incremental conditional switching threshold to a baseline conditional switching threshold and / or a current conditional switching threshold, and UE 504 may use the updated values ​​to evaluate conditional switching associated with network nodes operating in NES mode (e.g., source network node 502 and / or target network node 506). Alternatively or additionally, the NES conditional switching threshold may be an absolute value (e.g., not combined with another value) used by UE 504 to evaluate network nodes operating in NES mode.

[0117] The source network node 502 may, in the same and / or different signaling as the indication of the NES conditional handover threshold, indicate a first instruction to begin evaluating a conditional handover condition at least partially based on the NES conditional handover threshold and / or a second instruction to stop evaluating the conditional handover condition at least partially based on the NES conditional handover threshold. For example, the source network node 502 may use L2 signaling (e.g., MAC CE) to indicate the NES conditional handover threshold. In some aspects, MAC CE may indicate and / or include any combination of one or more of the following: a network node identifier, an operating mode associated with the identified network node (e.g., a first bit indicating whether the NES mode is enabled or disabled), an offset associated with the conditional handover condition, the conditional handover condition, and / or the operating mode associated with the conditional handover condition (e.g., a second bit indicating whether to begin evaluating the conditional handover condition and / or stop evaluating the conditional handover condition).

[0118] In some aspects, UE 504 may evaluate conditional handover to a network node at least in part based on a non-NES conditional handover threshold associated with a network node (e.g., the same network node) operating in a mode different from the NES mode (such as active mode, peak-hour operating mode, full-function operating mode, and / or baseline operating mode). Thus, different conditional handover thresholds may be associated with a network node, and each conditional handover threshold may be associated with a corresponding operating mode of the network node. In some aspects, the operating mode may not be visible to UE 504. In other words, in some aspects, UE 504 may be instructed to update the conditional handover thresholds at least in part based on NES conditional handover thresholds and / or non-NES conditional handover thresholds (e.g., at least in part based on offsets and / or absolute values) without receiving information indicating the operating mode of the network node. In some aspects, UE 504 may maintain separate, distinct conditional handover thresholds associated with the corresponding operating modes of the network node and monitor one or more signals at least in part based on these distinct conditional handover thresholds.

[0119] In some aspects, UE 504 may stop monitoring signals at least in part based on an NES conditional handover threshold. Exemplarily, UE 504 may receive a stop indication specifying the cessation of evaluation of a conditional handover condition at least in part based on an NES conditional handover threshold. The stop indication may specify the conditional handover condition and / or the network node associated with the conditional handover condition. For example, the stop indication may specify the cessation of evaluation at least in part based on a first NES conditional handover condition and / or a first conditional handover condition associated with a source network node 502. Alternatively or additionally, the stop indication may specify the cessation of evaluation at least in part based on a second NES conditional handover condition and / or a second conditional handover condition associated with a target network node 506. UE 504 may receive the stop indication in any combination of L1 signaling, L2 signaling, broadcast messages, multicast messages, and / or unicast messages. In some aspects, UE 504 may receive instructions (e.g., via L1 signaling, L2 signaling, broadcast messages, multicast messages, and / or unicast messages) to remove specific conditional handover thresholds (such as NES conditional handover thresholds associated with a specific target network node) from memory and / or cell monitoring lists. For example, the instruction to remove a conditional handover threshold may be associated with a target network node that is planned (or has already) been shut down. Therefore, UE 504 may remove conditional handover thresholds from the list and / or cease using conditional handover thresholds to monitor signals associated with the network node.

[0120] As indicated by reference numeral 540 in the attached figure, UE 504 can detect conditional handover triggering events. In other words, UE 504 can detect that a conditional handover condition, at least in part based on NES conditional handover, has been met (e.g., a first conditional handover condition associated with the A3 threshold has been met and / or a second conditional handover condition associated with the A5 threshold has been met).

[0121] As shown by reference numeral 550 in the attached figure, UE 504, source network node 502, and target network node 506 can perform a handover (e.g., conditional handover). During a handover, UE 504 can disconnect and / or break the communication link with source network node 502, and / or establish a second communication link with target network node 506.

[0122] Using NES conditional handover conditions (e.g., NES conditional handover thresholds) allows the source network node to offload attached UEs without sending corresponding RRC signaling instructing each UE to perform a handover. For example, the source network node can send a first NES conditional handover threshold that increases the conditional handover threshold associated with the source network node, causing the UE to trigger a conditional handover to the target network node. Therefore, the source network node can offload attached UEs without sending corresponding RRC signaling to each UE, reducing the amount of RRC signaling performed by the source network node and the corresponding UE. Reducing the amount of RRC signaling allows the source network node to reduce power consumption and / or transition to NES mode more quickly. Alternatively or additionally, reducing the amount of RRC signaling from the source network node can also reduce the amount of RRC signaling performed by each UE, reducing UE power consumption, maintaining UE battery life, enabling UEs to perform handovers more quickly, and / or reducing service interruptions at the UE.

[0123] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0124] Figure 6 This illustrates a second target network node 602 (e.g., another network node 110) according to this disclosure, and as per the above. Figure 5 A diagram of example 600 illustrating the wireless communication process between source network node 502, UE 504 and target network node 506.

[0125] Such as about Figure 5 As described and indicated by reference numeral 510 in the accompanying drawings, source network node 502 and UE 504 may establish a communication link with each other. As part of establishing the communication link and / or at least in part based on establishing the communication link, source network node 502 may send information to UE 504, and / or UE 504 may send information to source network node 502. Exemplarily, source network node 502 may send and / or indicate multiple options for NES conditional handover thresholds and / or conditional handover configurations. Alternatively or additionally, source network node 502 may send and / or indicate one or more non-NES conditional handover thresholds and / or conditional handover configurations. In some aspects, UE 504 may (e.g., in UE capability information and / or in messages transmitted differently from UE capability information) indicate support for the NES conditional handover procedure.

[0126] As shown by reference numeral 610-1, source network node 502 may send an indication that UE 504 supports the NES conditional handover procedure, and target network node 506 may receive the indication that UE 504 supports the NES conditional handover procedure. Alternatively or additionally, as shown by reference numeral 610-2, source network node 502 may send an indication that UE 504 supports the NES conditional handover procedure, and second target network node 602 may receive the indication that UE 504 supports the NES conditional handover procedure. Exemplarily, source network node 502 may use a backhaul link to communicate the indication that UE 504 supports the NES conditional handover procedure to target network node 506 and / or second target network node 602. In some aspects, the indication that UE 504 supports the NES conditional handover procedure may mask the identity of UE 504. For example, source network node 502 may send an indication that a UE supporting the NES conditional handover procedure (e.g., UE 504) is attached to source network node 502. Although Figure 6 The illustration shows source network node 502 sending an instruction to target network node (e.g., target network node 506 and / or second target network node 602), but other examples may include different network nodes of a decomposed base station sending and / or receiving instructions from UE 504 to support the NES conditional handover procedure. For example, as per [reference to...] Figure 3 The CU of the described decomposed base station can send instructions to the DU of the decomposed base station.

[0127] As shown by reference numeral 620 in the accompanying drawings, the target network node 506 may send an indication that it has switched to or will switch to NES mode, and the source network node may receive this indication. For example, the target network node 506 may send the indication of NES mode operation via a backhaul link. Alternatively or additionally, the target network node 506 may send the indication of NES mode operation based at least in part on receiving an indication that UE 504 supports the NES conditional handover procedure and / or that a UE attached to the source network node 502 supports the NES conditional handover procedure. In some aspects, the target network node 506 may indicate a start time associated with the switch to NES mode. Although Figure 6 The illustration shows a target network node 506 sending an instruction to the source network node 502 to switch to NES mode; however, other examples may include different network nodes of a decomposed base station sending and / or receiving instructions to switch to NES mode. For example, as per [reference to...] Figure 3 The DU of the described decomposed base station can send instructions to the CU of the decomposed base station.

[0128] As shown by reference numeral 520 in the attached figure, the source network node 502 can send an indication of NES conditional handover conditions (e.g., NES conditional handover threshold), and the UE 504 can receive an indication of NES conditional handover conditions (e.g., NES conditional handover threshold), as per [reference to...]. Figure 5 As described. In some aspects, source network node 502 may send an indication of the NES condition switching threshold based at least in part on an indication and / or message received from target network node 506, as described with respect to reference numeral 620 (e.g., the target network node is switching to NES mode and / or operating in NES mode).

[0129] Source network node 502 may use L1 signaling and / or L2 signaling to send an indication of the NES conditional handover threshold. Alternatively or additionally, source network node 502 may send the indication of the NES conditional handover threshold in the SIB. The NES conditional handover threshold may be network node-specific (e.g., target network node 506-specific). Therefore, source network node 502 may indicate a network node identifier and / or associate a network node identifier with an NES conditional handover threshold. In some aspects, source network node 502 may indicate the NES conditional handover threshold based at least in part on sending an indication to select from multiple options (e.g., multiple conditional handover configurations and / or multiple NES conditional handover thresholds). Source network node 502 may broadcast the indication, send the indication in multicast and / or multicast messages, and / or send the indication in unicast messages, such as by sending a multicast message to a UE that supports the NES conditional handover procedure.

[0130] In some respects, UE 504 may receive and / or recover an SIB indicating a NES conditional handover threshold based at least in part on the detection of an SIB acquisition trigger event. Alternatively or additionally, UE 504 may receive and / or recover an SIB based at least in part on the operating state of UE 504, such as SIB recovery conditions associated with both the current operating state of UE 504, including RRC connectivity and UE 504 operating at the cell edge.

[0131] As indicated by reference numeral 530 in the attached figure, UE 504 can monitor one or more signals, at least in part, based on an indication of an NES conditional handover threshold, such as regarding Figure 5 As described above. In some aspects, UE 504 may begin to monitor signals using the NES conditional handover threshold based at least in part on receiving an instruction to begin evaluating network nodes (e.g., source network node 502 and / or target network node 506) based at least in part on an NES conditional handover threshold and / or a conditional threshold condition associated with the NES conditional handover threshold. For example, UE 504 may receive an instruction in the MAC CE as described above.

[0132] In some aspects, UE 504 may stop monitoring signals at least in part based on an NES conditional handover threshold. Exemplarily, UE 504 may receive a stop indication specifying a conditional handover condition for stopping evaluation at least in part based on an NES conditional handover threshold. For example, UE 504 may receive a MAC CE specifying a network node, a conditional handover condition associated with the network node, and / or an operating mode (e.g., start evaluation and / or stop evaluation). UE 504 may receive the stop indication in any combination of L1 signaling, L2 signaling, broadcast messages, multicast messages, and / or unicast messages.

[0133] In some respects, UE 504 may receive instructions to remove specific conditional handover thresholds (e.g., NES conditional handover thresholds and / or non-NES conditional handover thresholds) from the memory and / or cell monitoring list. Therefore, UE 504 may remove specific conditional handover thresholds from the list and / or cease using specific conditional handover thresholds to monitor signals associated with network nodes.

[0134] As indicated by reference numeral 540 in the attached figure, UE 504 can detect a conditional handover trigger event. In other words, UE 504 can detect that a conditional handover condition, at least in part based on NES conditional handover, has been met.

[0135] As shown by reference numeral 630 in the attached figure, UE 504, source network node 502, and second target network node 602 can perform a handover (e.g., conditional handover). During the handover, UE 504 can disconnect and / or break the communication link with source network node 502, and / or establish a second communication link with second target network node 602.

[0136] Using NES conditional handover thresholds allows the source network node to mitigate the condition thresholds triggered by the UE when attempting to hand over to a target network node operating in NES mode. In some respects, the source network node can use a different mechanism than RRC signaling to send indications of the NES conditional handover thresholds. Mitigating UE attempts to hand over to a target network node operating in NES mode reduces the amount of RRC signaling between the UE and the source network node, and between the UE and the target network node operating in NES mode. Reduced RRC signaling reduces UE power consumption, preserves UE battery life, enables faster handovers, and / or reduces service interruptions at the UE.

[0137] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0138] Figure 7This is a diagram illustrating an example procedure 700 performed by a UE according to this disclosure. Example procedure 700 is an example in which a UE (e.g., UE 120) performs operations associated with conditional switching based on network power saving mode.

[0139] like Figure 7 As shown, in some aspects, process 700 may include: receiving an indication of an NES conditional handover threshold (box 710). For example, the UE (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein may receive an indication of the NES condition switching threshold, as described above.

[0140] like Figure 7 As further shown, in some aspects, process 700 may include monitoring one or more received signals (block 720) at least in part based on an NES conditional handover threshold. For example, the UE (e.g., using...) Figure 9 The communication manager 906 described herein can monitor one or more received signals, at least in part, based on NES condition switching thresholds, as described above.

[0141] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0142] In the first aspect, process 700 includes detecting a conditional handover triggering event based at least in part on an NES conditional handover threshold, and performing a conditional handover to a target network node.

[0143] In the second aspect, receiving an indication of the NES condition switching threshold includes using a mechanism different from RRC signaling to receive the indication.

[0144] Thirdly, the different mechanism differs from RRC reconfiguration messages.

[0145] In the fourth aspect, the NES conditional switching threshold includes the incremental conditional switching threshold.

[0146] In the fifth aspect, the NES conditional handover threshold includes the NES conditional handover offset associated with the conditional handover power level threshold.

[0147] In the sixth aspect, receiving an indication of the NES condition switching threshold includes receiving the indication in the SIB.

[0148] In the seventh aspect, the SIB is the NES SIB, the NES conditional handover threshold is the first NES conditional handover threshold, and the NES SIB indicates at least one of the DTX information associated with the target network node, the DRX information associated with the target network node, the cell selection offset associated with the target network node, or the second NES conditional handover threshold associated with the target network node.

[0149] In the eighth aspect, process 700 includes detecting an SIB acquisition trigger event and receiving an indication in the SIB based at least in part on the detection of the SIB acquisition trigger event.

[0150] In the ninth aspect, the SIB acquisition trigger event includes at least one of a periodic timer or receiving an SIB update indication.

[0151] In the tenth aspect, SIB indicates at least one of the serving network node NES information or the target network node NES information.

[0152] In the eleventh aspect, the Serving Network Node NES information indicates at least two configurations for a single condition switching condition associated with the Serving Network Node.

[0153] In the twelfth aspect, the target network node NES information indicates at least two configurations for a single condition switching condition associated with the target network node.

[0154] In the thirteenth aspect, the target network node NES information at least indicates a first NES condition switching condition associated with the first target network node and a second NES condition switching condition associated with the second target network node.

[0155] In the fourteenth aspect, process 700 includes receiving an SIB update indication in at least one of an L1 broadcast message or an L1 multicast message, and receiving the indication in the SIB is based at least in part on the receipt of the SIB update indication.

[0156] In the fifteenth aspect, process 700 includes instructing support for the NES conditional switching process, and receiving an instruction on the NES conditional switching threshold is based at least in part on the instruction to support the NES conditional switching process.

[0157] In the sixteenth aspect, indicating support for the NES conditional handover process includes sending UE capability information indicating support for the NES conditional handover process.

[0158] In the seventeenth aspect, the NES conditional switching threshold includes a time threshold.

[0159] In the eighteenth aspect, process 700 includes receiving at least one cell selection criterion associated with the RRC idle state in the SIB, and the NES conditional handover threshold is based at least in part on at least one cell selection criterion.

[0160] In the nineteenth aspect, receiving an indication of the NES condition handover threshold includes receiving an indication of the NES condition handover threshold in the SIB, and the NES condition handover includes an offset associated with at least one of evaluating candidate cells or identifying measurement report triggering events.

[0161] In the twentieth aspect, process 700 includes determining the current operating state, including being in an RRC connected state and operating at the cell edge, and restoring the SIB based at least in part on the current operating state.

[0162] In the twentieth aspect, the indication of the NES condition switching threshold is a first indication, and the process 700 includes receiving a second indication in the SIB to remove at least one condition switching condition associated with the target network node.

[0163] In the twenty-second aspect, receiving an indication of the NES condition switching threshold includes receiving the indication of the NES condition switching threshold as a broadcast message in L1 signaling or L2 signaling.

[0164] In the twenty-third aspect, the indication is a first indication, and the process 700 includes receiving a plurality of conditional handover configurations, the plurality of conditional handover configurations including at least one of the following: one or more normal operation conditional handover configurations, one or more source network node NES conditional handover configurations, or one or more target network node NES conditional handover configurations, and receiving an indication of an NES conditional handover threshold includes receiving a selection of one of the plurality of conditional handover configurations in a broadcast message in L1 signaling or L2 signaling.

[0165] In the twenty-fourth aspect, receiving multiple conditional switching configurations includes receiving multiple conditional switching configurations in RRC signaling.

[0166] In the twenty-fifth aspect, receiving an instruction on an NES condition switching threshold includes receiving at least one of the following as an NES condition switching threshold: an NES source network node offset to be applied to a non-NES source network node condition threshold condition or an NES target network node offset to be applied to a non-NES target network node condition threshold condition.

[0167] In the twenty-sixth aspect, process 700 includes receiving an instruction in L1 signaling or L2 signaling to begin evaluating the NES conditional handover threshold.

[0168] In aspect twenty-seven, L1 signaling includes downlink control information.

[0169] In aspect twenty-eight, L2 signaling includes MAC CE.

[0170] In the twentieth aspect, the indication of the NES condition switching threshold is a first indication, and the process 700 includes receiving a second indication in a broadcast message in L1 signaling or L2 signaling to stop evaluating at least one condition switching condition associated with the target network node.

[0171] In the thirtieth aspect, the indication of the NES condition switching threshold is a first indication, and the process 700 includes receiving a second indication of the NES mode of the target network node as a broadcast message in L1 signaling or L2 signaling.

[0172] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted may be fewer, different, or arranged differently than additional boxes, boxes, or boxes in a different manner. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0173] Figure 8 This is a diagram illustrating an example process 800 performed by a network node according to this disclosure. Example process 800 is an example in which a network node (e.g., network node 110) performs operations associated with conditional switching based on network power saving modes.

[0174] like Figure 8 As shown, in some aspects, process 800 may include sending an indication of an NES conditional switching threshold (box 810). For example, a network node (e.g., using...) Figure 10 The transmitting component 1004 and / or the communication manager 1006 described herein can transmit an indication of the NES condition switching threshold, as described above.

[0175] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other process descriptions described elsewhere in this document.

[0176] In the first aspect, sending an indication of the NES condition switching threshold includes using a mechanism different from RRC signaling to send the indication.

[0177] Secondly, RRC signaling includes RRC reconfiguration messages.

[0178] In the third aspect, the NES conditional switching threshold includes the incremental conditional switching threshold.

[0179] In the fourth aspect, the NES conditional handover threshold includes the NES conditional handover offset associated with the conditional handover power level threshold.

[0180] In the fifth aspect, sending an indication of the NES condition switching threshold includes sending the indication in the SIB.

[0181] In the sixth aspect, the SIB is the NES SIB, the NES conditional handover threshold is the first NES conditional handover threshold, and the NES SIB indicates at least one of the DTX information associated with the target network node, the DRX information associated with the target network node, the cell selection offset associated with the target network node, or the second NES conditional handover threshold associated with the target network node.

[0182] In the seventh aspect, process 800 includes sending an SIB update instruction associated with the NES SIB.

[0183] In the eighth aspect, sending the SIB update instruction includes sending the SIB update instruction in at least one of an L1 broadcast message or an L1 multicast message.

[0184] In the ninth aspect, SIB indicates at least one of the serving network node NES information or the target network node NES information.

[0185] In the tenth aspect, the Serving Network Node NES information indicates at least two configurations for a single condition switching condition associated with the Serving Network Node.

[0186] In the eleventh aspect, the target network node NES information indicates at least two configurations for a single condition switching condition associated with the target network node.

[0187] In the twelfth aspect, the target network node NES information indicates at least a first NES condition switching condition associated with the first target network node and a second NES condition switching condition associated with the second target network node.

[0188] In the thirteenth aspect, the indication of the NES condition handover threshold is a first indication, and the process 800 includes receiving a second indication that the UE supports the NES condition handover process, and sending the indication of the NES condition handover threshold is based at least in part on receiving the second indication that the UE supports the NES condition handover process.

[0189] In the fourteenth aspect, receiving the second instruction includes receiving UE capability information including the second instruction.

[0190] In the fifteenth aspect, the network node is the first network node, and the process 800 includes forwarding a second instruction to the second network node to support the NES conditional handover process for the UE.

[0191] In the sixteenth aspect, the indication of the NES condition switching threshold is a first indication, the network node is a first network node, and the process 800 includes receiving from a second network node a second indication specifying that the second network node is switching to NES mode, and sending the indication of the NES condition switching threshold is at least in part based on receiving the second indication.

[0192] In the seventeenth aspect, the NES conditional switching threshold includes a time threshold.

[0193] In the eighteenth aspect, procedure 800 includes transmitting in the SIB at least one cell selection criterion associated with the UE operating in RRC idle state, and the NES conditional handover threshold is based at least in part on at least one cell selection criterion.

[0194] In the nineteenth aspect, sending an indication of the NES condition handover threshold includes sending an SIB that includes the NES condition handover threshold, and the NES condition handover threshold includes an offset associated with at least one of evaluating candidate cells or identifying measurement report triggering events.

[0195] In the twentieth aspect, the indication of the NES condition switching threshold is a first indication, and the process 800 includes sending a second indication in the SIB to remove at least one condition switching condition associated with the target network node.

[0196] In the twenty-first aspect, sending an indication of the NES condition switching threshold includes sending the indication of the NES condition switching threshold as a broadcast message in L1 signaling or L2 signaling.

[0197] In the twentieth aspect, the indication is a first indication, and the process 800 includes sending a plurality of conditional handover configurations, the plurality of conditional handover configurations including at least two of the following: one or more normal operation conditional handover configurations, one or more source network node NES conditional handover configurations, or one or more target network node NES conditional handover configurations, and sending an indication of an NES conditional handover threshold includes sending a selection of one of the plurality of conditional handover configurations in a broadcast message in L1 signaling or L2 signaling.

[0198] In aspect twenty-three, sending multiple conditional switching configurations includes sending multiple conditional switching configurations in RRC signaling.

[0199] In the twentieth aspect, sending an instruction for an NES condition switching threshold includes sending at least one of the following as an NES condition switching threshold: an NES source network node offset to be applied to a non-NES source network node condition threshold condition or an NES target network node offset to be applied to a non-NES target network node condition threshold condition.

[0200] In the twentieth aspect, process 800 includes sending an instruction in L1 signaling or L2 signaling to begin evaluating the NES conditional switching threshold.

[0201] In aspect twenty-six, L1 signaling includes downlink control information.

[0202] In aspect twenty-seven, L2 signaling includes MAC CE.

[0203] In the twentieth aspect, the indication of the NES condition switching threshold is a first indication, and the process 800 includes sending a second indication in a broadcast message in L1 signaling or L2 signaling to stop evaluating at least one condition switching condition associated with the target network node.

[0204] In the twenty-ninth aspect, the indication of the NES condition switching threshold is a first indication, and the process 800 includes sending a second indication of the NES mode of the target network node as a broadcast message in L1 signaling or L2 signaling.

[0205] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0206] Figure 9 This is a diagram of an example device 900 for wireless communication according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 906 is combined with... Figure 1 The described communication manager 140. As shown, device 900 can use receiving component 902 and transmitting component 904 to communicate with another device 908 (such as UE or network node (such as CU, DU, RU or base station)).

[0207] In some respects, device 900 can be configured to perform the functions described herein. Figures 4 to 8 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein (such as...). Figure 7 The process 700) or a combination thereof. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0208] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0209] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in a transceiver.

[0210] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0211] The communication manager 906 can receive an indication of the NES conditional handover threshold via the receiving component 902. The communication manager 906 can monitor one or more received signals, at least in part, based on the NES conditional handover threshold. In some aspects, the communication manager 906 can detect conditional handover triggering events, at least in part, based on the NES conditional handover threshold. Alternatively or additionally, the communication manager 906 can perform a conditional handover to a target network node.

[0212] The communication manager 906 can detect an SIB acquisition trigger event and receive an indication in the SIB based at least in part on the detection of the SIB acquisition trigger event. In some aspects, the communication manager 906 can receive an SIB update indication via the receiving component 902 in at least one of an L1 broadcast message or an L1 multicast message.

[0213] The communication manager 906 can instruct support for the NES conditional handover procedure, and receives an indication of the NES conditional handover threshold based at least in part on the indication of support for the NES conditional handover procedure. The communication manager can receive instructions to begin evaluating the NES conditional handover threshold in L1 signaling or L2 signaling via the receiving component 902.

[0214] In some aspects, the communication manager 906 can receive at least one cell selection criterion associated with the RRC idle state in the SIB via the receiving component 902, and the NES conditional handover threshold is based at least in part on at least one cell selection criterion. The communication manager 906 can determine the current operating state, including being in the RRC connected state and operating at the cell edge. Based at least in part on the current operating state, the communication manager 906 can restore the SIB.

[0215] Figure 9 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The set (one or more) components shown are executable and described as being composed of Figure 9 The other set of components shown performs one or more functions.

[0216] Figure 10This is a diagram of an example device 1000 for wireless communication according to the present disclosure. Device 1000 may be a network node, or a network node may include device 1000. In some aspects, device 1000 includes a receiving component 1002, a transmitting component 1004, and / or a communication manager 1006 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1006 is combined with... Figure 1 The described communication manager 150. As shown, device 1000 can use receiving component 1002 and transmitting component 1004 to communicate with another device 1008 (such as UE or network node (such as CU, DU, RU or base station)).

[0217] In some respects, device 1000 can be configured to perform the functions described herein. Figures 4 to 8 One or more operations as described herein. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein (such as...). Figure 8 The process 800) or a combination thereof. In some respects, Figure 10 The illustrated device 1000 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0218] Receiver 1002 may receive communications from device 1008, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1000. In some aspects, receiver 1002 may include combinations of... Figure 2The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 1002 and / or transmitter component 1004 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals from device 1000 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0219] Transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1008. In some aspects, one or more other components of device 1000 may generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1008. In some aspects, transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1008. In some aspects, transmitting component 1004 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1004 may be co-located with the receive component 1002 in a transceiver.

[0220] The communication manager 1006 may support the operation of the receiving component 1002 and / or the transmitting component 1004. For example, the communication manager 1006 may receive information associated with configuring the reception of communications by the receiving component 1002 and / or the transmission of communications by the transmitting component 1004. Additionally or alternatively, the communication manager 1006 may generate control information and / or provide control information to the receiving component 1002 and / or the transmitting component 1004 to control the reception and / or transmission of communications.

[0221] The communication manager 1006 may send an indication of the NES conditional handover threshold via the sending component 1004. Alternatively or additionally, the communication manager 1006 may send an SIB update indication associated with the NES SIB via the sending component 1004. In some aspects, the communication manager 1006 may send in the SIB at least one cell selection criterion associated with the UE operating in RRC idle state, and the NES conditional handover threshold is at least partially based on at least one cell selection criterion. The communication manager 1006 may send in L1 signaling or L2 signaling an instruction to begin evaluating the NES conditional handover threshold via the sending component 1004.

[0222] Figure 10The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 10 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The set (one or more) components shown are executable and described as being composed of Figure 10 The other set of components shown performs one or more functions.

[0223] The following provides an overview of some aspects of this disclosure:

[0224] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of a network power saving (NES) condition switching threshold; and monitoring one or more received signals based at least in part on the NES condition switching threshold.

[0225] Aspect 2: According to the method of aspect 1, the method further includes: detecting a conditional handover triggering event based at least in part on the NES conditional handover threshold; and performing a conditional handover to the target network node.

[0226] Aspect 3: The method according to any one of Aspects 1 and 2, wherein receiving the indication for the NES conditional switching threshold comprises: receiving the indication using a mechanism different from Radio Resource Control (RRC) signaling.

[0227] Aspect 4: The method described in aspect 3, wherein the different mechanism is different from the RRC reconfiguration message.

[0228] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the NES condition switching threshold includes an incremental condition switching threshold.

[0229] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the NES conditional switching threshold includes an NES conditional switching offset associated with a conditional switching power level threshold.

[0230] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the indication for the NES condition switching threshold comprises: receiving the indication in a System Information Block (SIB).

[0231] Aspect 8: According to the method of aspect 7, wherein the SIB is an NES SIB, wherein the NES condition handover threshold is a first NES condition handover threshold, and wherein the NES SIB indicates at least one of the following: discontinuous transmission (DTX) information associated with the target network node, discontinuous reception (DRX) information associated with the target network node, cell selection offset associated with the target network node, or a second NES condition handover threshold associated with the target network node.

[0232] Aspect 9: The method according to aspect 7, the method further comprising: detecting an SIB acquisition trigger event, wherein receiving the indication in the SIB is based at least in part on detecting the SIB acquisition trigger event.

[0233] Aspect 10: According to the method of aspect 9, the SIB acquisition trigger event includes at least one of the following: periodic timer expiration and receiving an SIB update indication.

[0234] Aspect 11: According to the method of aspect 7, wherein the SIB indicates at least one of the following: serving network node NES information or target network node NES information.

[0235] Aspect 12: According to the method of aspect 11, wherein the serving network node NES information indicates at least two configurations for a single condition switching condition associated with the serving network node.

[0236] Aspect 13: According to the method of aspect 11, wherein the target network node NES information indicates at least two configurations for a single condition switching condition associated with the target network node.

[0237] Aspect 14: According to the method of aspect 11, the target network node NES information indicates at least: a first NES condition switching condition associated with a first target network node and a second NES condition switching condition associated with a second target network node.

[0238] Aspect 15: The method according to aspect 7, the method further comprising: receiving an SIB update indication in at least one of: a Layer 1 (L1) broadcast message or an L1 multicast message, wherein receiving the indication in the SIB is at least partially based on receiving the SIB update indication, wherein receiving the indication in the SIB is at least partially based on receiving the SIB update indication.

[0239] Aspect 16: The method according to any one of Aspects 1 to 15, the method further comprising: instructing support for the NES conditional switching procedure, wherein receiving the instruction on the NES conditional switching threshold is at least in part based on the instruction to support the NES conditional switching procedure.

[0240] Aspect 17: According to the method of aspect 16, wherein indicating support for the NES conditional handover process includes: sending UE capability information indicating support for the NES conditional handover process.

[0241] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the NES condition switching threshold includes a time threshold.

[0242] Aspect 19: The method according to any one of Aspects 1 to 18, the method further comprising: receiving in a System Information Block (SIB) at least one cell selection criterion associated with a Radio Resource Control (RRC) idle state, wherein the NES conditional handover threshold is based at least in part on the at least one cell selection criterion.

[0243] Aspect 20: The method according to any one of Aspects 1 to 19, wherein receiving the indication for the NES condition handover threshold comprises: receiving the indication for the NES condition handover threshold in a System Information Block (SIB), wherein the NES condition handover includes an offset associated with at least one of: evaluating candidate cells or identifying a measurement report trigger event.

[0244] Aspect 21: The method according to aspect 20 further includes: determining a current operating state including being in a radio resource control (RRC) connected state and operating at the cell edge; and restoring the SIB based at least in part on the current operating state.

[0245] Aspect 22: The method according to any one of Aspects 1 to 21, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: receiving in a System Information Block (SIB) a second indication to remove at least one condition switching condition associated with the target network node.

[0246] Aspect 23: The method according to any one of Aspects 1 to 22, wherein receiving the indication for the NES condition switching threshold comprises: receiving the indication for the NES condition switching threshold as a broadcast message in Layer 1 signaling or Layer 2 signaling.

[0247] Aspect 24: The method according to aspect 23, wherein the indication is a first indication, and the method further comprises: receiving a plurality of conditional switching configurations, the plurality of conditional switching configurations including at least one of the following: one or more normal operation conditional switching configurations, one or more source network node NES conditional switching configurations, or one or more target network node NES conditional switching configurations, wherein receiving the indication for the NES conditional switching threshold includes receiving a selection of one of the plurality of conditional switching configurations in a broadcast message in layer 1 signaling or layer 2 signaling.

[0248] Aspect 25: According to the method of aspect 24, receiving the plurality of conditional switching configurations includes: receiving the plurality of conditional switching configurations in radio resource control (RRC) signaling.

[0249] Aspect 26: According to the method of aspect 23, receiving the indication for the NES condition switching threshold includes: receiving at least one of the following as the NES condition switching threshold: an NES source network node offset to be applied to a non-NES source network node condition threshold condition or an NES target network node offset to be applied to a non-NES target network node condition threshold condition.

[0250] Aspect 27: According to the method of aspect 23, the method further includes: receiving an instruction to begin evaluating the NES conditional handover threshold in the L1 signaling or the Layer 2 signaling.

[0251] Aspect 28: According to the method of aspect 23, the layer 1 signaling includes downlink control information.

[0252] Aspect 29: According to the method of aspect 23, the layer 2 signaling includes a media access control (MAC) control element (CE).

[0253] Aspect 30: The method according to any one of Aspects 1 to 29, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: receiving a second indication in a broadcast message in Layer 1 signaling or Layer 2 signaling to stop evaluating at least one condition switching condition associated with the target network node.

[0254] Aspect 31: The method according to any one of Aspects 1 to 30, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: receiving a second indication of the NES mode of the target network node as a broadcast message in Layer 1 signaling or Layer 2 signaling.

[0255] Aspect 32: A method for wireless communication performed by a network node, the method comprising: sending an indication of a network power saving (NES) condition switching threshold;

[0256] Aspect 33: According to the method of aspect 32, the sending of the indication to the NES condition switching threshold includes: sending the indication using a mechanism different from Radio Resource Control (RRC) signaling.

[0257] Aspect 34: The method according to aspect 33, wherein the RRC signaling includes an RRC reconfiguration message.

[0258] Aspect 35: The method according to any one of Aspects 32 to 34, wherein the NES condition switching threshold includes an incremental condition switching threshold.

[0259] Aspect 36: The method according to any one of Aspects 32 to 35, wherein the NES conditional switching threshold includes an NES conditional switching offset associated with a conditional switching power level threshold.

[0260] Aspect 37: The method according to any one of Aspects 32 to 36, wherein sending the indication for the NES condition switching threshold comprises: sending the indication in a System Information Block (SIB).

[0261] Aspect 38: The method according to aspect 37, wherein the SIB is an NES SIB, wherein the NES condition handover threshold is a first NES condition handover threshold, and wherein the NES SIB indicates at least one of the following: discontinuous transmission (DTX) information associated with the target network node, discontinuous reception (DRX) information associated with the target network node, cell selection offset associated with the target network node, or a second NES condition handover threshold associated with the target network node.

[0262] Aspect 39: The method according to aspect 38 further includes: sending an SIB update indication associated with the NES SIB.

[0263] Aspect 40: The method according to aspect 39, wherein sending the SIB update indication includes sending the SIB update indication in at least one of the following: a Layer 1 (L1) broadcast message or an L1 multicast message.

[0264] Aspect 41: The method according to aspect 37, wherein the SIB indicates at least one of the following: serving network node NES information or target network node NES information.

[0265] Aspect 42: According to the method of aspect 41, wherein the serving network node NES information indicates at least two configurations for a single condition switching condition associated with the serving network node.

[0266] Aspect 43: According to the method of aspect 41, wherein the target network node NES information indicates at least two configurations for a single condition switching condition associated with the target network node.

[0267] Aspect 44: According to the method of aspect 41, the target network node NES information indicates at least: a first NES condition switching condition associated with a first target network node and a second NES condition switching condition associated with a second target network node.

[0268] Aspect 45: The method according to any one of Aspects 32 to 44, wherein the indication of the NES conditional handover threshold is a first indication, and the method further comprises: receiving a second indication that the user equipment (UE) supports the NES conditional handover procedure, wherein sending the indication of the NES conditional handover threshold is at least in part based on receiving the second indication that the UE supports the NES conditional handover procedure.

[0269] Aspect 46: According to the method of aspect 45, receiving the second instruction includes receiving UE capability information including the second instruction.

[0270] Aspect 47: The method according to aspect 45, wherein the network node is a first network node, and the method further includes: forwarding the second indication that the UE supports the NES conditional handover procedure to a second network node.

[0271] Aspect 48: The method according to any one of Aspects 32 to 47, wherein the indication for the NES condition switching threshold is a first indication, wherein the network node is a first network node, and the method further comprises: receiving from a second network node a second indication specifying that the second network node is transitioning to NES mode, wherein sending the indication for the NES condition switching threshold is at least in part based on receiving the second indication.

[0272] Aspect 49: The method according to any one of Aspects 32 to 48, wherein the NES condition switching threshold includes a time threshold.

[0273] Aspect 50: The method according to any one of Aspects 32 to 49, the method further comprising: transmitting in a System Information Block (SIB) at least one cell selection criterion associated with a User Equipment (UE) operating in Radio Resource Control (RRC) idle state, wherein the NES conditional handover threshold is based at least in part on the at least one cell selection criterion.

[0274] Aspect 51: The method according to any one of Aspects 32 to 50, wherein sending the indication of the NES condition handover threshold comprises sending a System Information Block (SIB) including the NES condition handover threshold, wherein the NES condition handover threshold includes an offset associated with at least one of: evaluating candidate cells, or identifying a measurement report triggering event.

[0275] Aspect 52: The method according to any one of Aspects 32 to 51, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: sending a second indication in a System Information Block (SIB) to remove at least one condition switching condition associated with the target network node.

[0276] Aspect 53: The method according to any one of Aspects 32 to 52, wherein sending the indication of the NES condition switching threshold comprises: sending the indication of the NES condition switching threshold as a broadcast message in Layer 1 signaling or Layer 2 signaling.

[0277] Aspect 54: The method according to aspect 53, wherein the indication is a first indication, and the method further comprises: sending a plurality of conditional switching configurations, the plurality of conditional switching configurations including at least two of the following: one or more normal operation conditional switching configurations, one or more source network node NES conditional switching configurations, or one or more target network node NES conditional switching configurations, wherein sending the indication for the NES conditional switching threshold includes sending a selection of one of the plurality of conditional switching configurations in the broadcast message in layer 1 signaling or layer 2 signaling.

[0278] Aspect 55: According to the method of aspect 54, sending the plurality of conditional switching configurations includes: sending the plurality of conditional switching configurations in radio resource control (RRC) signaling.

[0279] Aspect 56: According to the method of aspect 53, wherein sending the indication for the NES condition switching threshold comprises: sending at least one of the following as the NES condition switching threshold: an NES source network node offset to be applied to a non-NES source network node condition threshold condition or an NES target network node offset to be applied to a non-NES target network node condition threshold condition.

[0280] Aspect 57: According to the method of aspect 53, the method further includes: sending an instruction to begin evaluating the NES conditional switching threshold in the layer 1 signaling or the layer 2 signaling.

[0281] Aspect 58: According to the method of aspect 53, the layer 1 signaling includes downlink control information.

[0282] Aspect 59: According to the method of aspect 53, the layer 2 signaling includes a media access control (MAC) control element (CE).

[0283] Aspect 60: The method according to any one of Aspects 32 to 59, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: sending a second indication in a broadcast message in Layer 1 signaling or Layer 2 signaling to stop evaluating at least one condition switching condition associated with the target network node.

[0284] Aspect 61: The method according to any one of Aspects 32 to 60, wherein the indication of the NES condition switching threshold is a first indication, and the method further comprises: sending a second indication of the NES mode of the target network node as a broadcast message in Layer 1 signaling or Layer 2 signaling.

[0285] Aspect 62: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 61.

[0286] Aspect 63: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 61.

[0287] Aspect 64: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 61.

[0288] Aspect 65: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1 to 61.

[0289] Aspect 66: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 61.

[0290] Aspect 67: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of a network power saving (NES) condition switching condition; and monitoring one or more received signals based at least in part on the NES condition switching condition.

[0291] Aspect 68: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspect 67.

[0292] Aspect 69: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspect 67.

[0293] Aspect 70: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 67.

[0294] Aspect 71: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of aspect 67.

[0295] Aspect 72: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspect 67.

[0296] Aspect 73: A method for wireless communication performed by a network node, the method comprising: sending an indication of a network power saving (NES) condition switching condition.

[0297] Aspect 74: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspect 73.

[0298] Aspect 75: An apparatus for wireless communication, the apparatus comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspect 73.

[0299] Aspect 76: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 73.

[0300] Aspect 77: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of aspect 73.

[0301] Aspect 78: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspect 73.

[0302] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various practices.

[0303] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced herein to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0304] As used in this article, depending on the context, "meeting the threshold" can mean a value 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, not equal to the threshold, etc.

[0305] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” the list of items means any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0306] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: Receive instructions on switching conditions for Network Energy Saving (NES); as well as One or more received signals are monitored, at least in part, based on the NES condition switching conditions.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: The conditional handover triggering event is detected at least in part based on an NES conditional handover threshold indicated by the NES conditional handover condition; and Perform a conditional switch to the target network node.

3. The apparatus of claim 1, wherein, in order for the UE to receive the indication of the NES condition switching condition, the one or more processors are configured to cause the UE to: The instruction is received using a different mechanism than Radio Resource Control (RRC) signaling.

4. The apparatus of claim 3, wherein the different mechanism is different from the RRC reconfiguration message.

5. The apparatus of claim 1, wherein the NES condition switching condition includes an NES condition switching threshold, the NES condition switching threshold being at least partially based on an NES condition switching offset associated with a condition switching power level threshold.

6. The apparatus of claim 1, wherein, in order for the UE to receive the indication of the NES condition switching condition, the one or more processors are configured to cause the UE to: Receive Serving Network Node (NES) information, which indicates at least two configurations for a single condition switching condition associated with the Serving Network Node.

7. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE Send UE capability information indicating support for NES conditional handover procedures.

8. The apparatus of claim 1, wherein, in order for the UE to receive the indication of the NES condition switching condition, the one or more processors are configured to cause the UE to: The indication of the NES condition switching condition is received in Layer 1 signaling as... Broadcast message or Multicast message.

9. The apparatus of claim 8, wherein the one or more processors are further configured to cause the UE to: Receive multiple condition switching configurations, wherein the multiple condition switching configurations include at least one of the following: One or more normal operation condition switching condition configurations or Configure NES condition switching conditions for one or more source network nodes.

10. The apparatus of claim 9, wherein, in order for the UE to receive the plurality of conditional handover configurations, the one or more processors are configured to cause the UE to: The multiple conditional switching configurations are received in Radio Resource Control (RRC) signaling.

11. The apparatus of claim 8, wherein the one or more processors are further configured to cause the UE to: In the Layer 1 signaling, an instruction is received to begin evaluating the NES condition handover threshold indicated by the NES condition handover condition, and Begin using the NES condition switching threshold to monitor one or more signals.

12. The apparatus of claim 8, wherein the one or more processors are further configured to transmit the UE downlink control information.

13. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Send an instruction on switching conditions for Network Energy Saving (NES).

14. The apparatus of claim 13, wherein, in order for the network node to send the indication of the NES condition switching condition, the one or more processors are configured to cause the network node to: The instruction is transmitted using a different mechanism than Radio Resource Control (RRC) signaling.

15. The apparatus of claim 14, wherein the RRC signaling includes an RRC reconfiguration message.

16. The apparatus of claim 13, wherein the NES condition switching condition indicates an NES condition switching threshold, the NES condition switching threshold being at least partially based on an NES condition switching offset associated with a condition switching power level threshold.

17. The apparatus of claim 13, wherein, in order for the network node to send the indication of the NES condition switching condition, the one or more processors are configured to cause the network node to: Send Serving Network Node (NES) information, which indicates at least two configurations for a single condition switching condition associated with the Serving Network Node.

18. The apparatus of claim 13, wherein the indication of the NES condition switching condition is a first indication, and The one or more processors are further configured to cause the network node to: Receive a second indication from the user equipment (UE) that it supports the NES conditional handover procedure. In order for the network node to send the first indication of the NES condition switching condition, the one or more processors are configured to cause the network node to: The first indication for the NES conditional handover condition is sent at least in part based on receiving the second indication that the UE supports the NES conditional handover procedure.

19. The apparatus of claim 18, wherein, in order for the network node to receive the second instruction, the one or more processors are configured to cause the network node to: Receive UE capability information including the second indication.

20. The apparatus of claim 13, wherein, in order for the network node to send the indication of the NES condition switching condition, the one or more processors are configured to cause the network node to: The indication of the NES condition switching condition will be sent as a broadcast message in Layer 1 signaling.

21. The apparatus of claim 20, wherein the one or more processors are further configured to cause the network node to: Send multiple condition switching configurations, wherein the multiple condition switching configurations include at least two of the following: One or more normal operation condition switching condition configurations or Configure NES condition switching conditions for one or more source network nodes.

22. The apparatus of claim 21, wherein, in order for the network node to send the plurality of condition switching configurations, the one or more processors are configured to cause the network node to: The multiple conditional switching configurations are sent in the Radio Resource Control (RRC) signaling.

23. The apparatus of claim 20, wherein the one or more processors are further configured to cause the network node to: In the Layer 1 signaling, an instruction is sent to begin evaluating the NES condition switching threshold indicated by the NES condition switching condition.

24. The apparatus of claim 20, wherein the one or more processors are further configured to transmit downlink control information of the network node.

25. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive instructions on switching conditions for Network Energy Saving (NES); as well as One or more received signals are monitored, at least in part, based on the NES condition switching conditions.

26. The method according to claim 25, further comprising: Condition switching trigger events are detected at least in part based on an NES condition switching threshold indicated by the NES condition switching condition; as well as Perform a conditional switch to the target network node.

27. The method of claim 25, wherein receiving the indication for the NES condition switching condition comprises: The instruction is received using a different mechanism than Radio Resource Control (RRC) signaling.

28. A method for wireless communication performed by a network node, the method comprising: Send an instruction on switching conditions for Network Energy Saving (NES).

29. The method of claim 28, wherein sending the indication for the NES condition switching condition comprises: The instruction is transmitted using a different mechanism than Radio Resource Control (RRC) signaling.

30. The method of claim 28, wherein the NES condition switching condition includes an NES condition switching threshold.

Images