Synchronization signal block procedure based on network power saving
By coordinating active NES between UE and network entities and adjusting the SSB transmission process, the problems of high processing overhead and power consumption for network power saving in wireless communication systems are solved, and more efficient network power management and SSB measurement accuracy are achieved.
Patent Information
- Application Number
- CN202480012383.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-02-21
- Filing Date
- 2024-02-09
- Publication Date
- 2025-10-03
AI Technical Summary
Existing wireless communication systems have problems with network power conservation, such as high processing overhead and excessive power consumption, especially during the transmission of synchronization signal blocks (SSBs), resulting in low device energy efficiency.
Power savings are achieved by coordinating the active network energy state (NES) between the user equipment (UE) and network entities, adjusting the transmission process of the synchronization signal block (SSB), including reducing the number of transmissions, lowering the transmission power and reducing the number of active antenna ports, and combining relaxation configuration and correction factors to optimize the radio measurement threshold.
It effectively reduces the processing overhead and power consumption of wireless communication systems, improves the accuracy of SSB measurements and the accuracy of cell selection or reselection processes, and achieves optimized management of network power.
Smart Images

Figure CN120752971A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 18 / 172,167, filed by Elshafie et al. on February 21, 2023, entitled “SYNCHRONIZATION SIGNAL BLOCK PROCEDURES BASED ON NETWORK POWER SAVINGS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Background Art
[0003] The following relates to wireless communications, including network power conservation procedures.
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention
[0005] An apparatus for wireless communication at a user equipment terminal (UE) is described. The apparatus may include a processor and a memory coupled to the processor. The processor may be configured to receive, for a network entity, a first indication of an active network energy state (NES) from a set of multiple NESs. In some examples, the processor may be further configured to receive a synchronization signal block (SSB) for the network entity based on the active NES and to communicate based on one or more measurements associated with the SSB.
[0006] A method for wireless communication at a UE is described. The method may include receiving, for a network entity, a first indication of an active NES from a set of multiple NESs. In some examples, the method may also include receiving a SSB for the network entity based on the active NES, and communicating based on one or more measurements associated with the SSB.
[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving, for a network entity, a first indication of an active NES from a set of multiple NESs. In some examples, the apparatus may also include means for receiving a SSB for the network entity based on the active NES, and means for communicating based on one or more measurements associated with the SSB.
[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive, for a network entity, a first indication of an active NES from a set of multiple NESs. In some examples, the code may also include instructions executable by the processor to: receive, for the network entity, a SSB for the network entity based on the active NES; and communicate based on one or more measurements associated with the SSB.
[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second indication of a correction factor corresponding to the active NES; and determining a radio measurement threshold based on the correction factor, the communication further being based on the radio measurement threshold.
[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, to determine the radio measurement threshold, the methods, apparatuses, and non-transitory computer-readable media described herein may include operations, features, components, or instructions for: setting the radio measurement threshold to the value of the correction factor; or modifying the radio measurement threshold based on the value of the correction factor.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a first signal indicating a list of correction factors; and receiving a second signal including the second indication of the correction factor in the list of correction factors.
[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first signal comprises a radio resource control (RRC) signal, a master information block (MIB), a system information block (SIB), a random access channel (RACH) signal, or a combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second signal comprises a medium access channel element (MAC-CE), a downlink control information (DCI) signal, or both. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the radio measurement threshold comprises a reference signal received power (RSRP) threshold, a reference signal received quality (RSRQ) threshold, or both.
[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving the SSB based on a periodicity for the SSB corresponding to the active NES, a skip pattern for the SSB, a first set of SSB opportunities to skip, a second set of SSB opportunities to receive, or a combination thereof.
[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a radio resource management (RRM) relaxation configuration, an RRM relaxation factor, or both based on the active NES, and the periodicity for the SSB, the skip pattern for the SSB, the first set of SSB opportunities to be skipped, the second set of SSB opportunities to be received, or the combination thereof based on the RRM relaxation configuration, the RRM relaxation factor, or both.
[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: sending UE information. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the active NES, the radio measurement configuration for the network entity, or both may be based on the UE information. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, RRC state, or a combination thereof.
[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: sending a third indication of the relaxed measurement configuration for the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the active NES, the radio measurement configuration for the network entity, or both may be based on the relaxed measurement configuration for the UE.
[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a request for an RRM relaxation configuration, an RRM relaxation factor, or both for the network entity. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the active NES, the radio measurement configuration for the network entity, or both may be based on the request.
[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the active NES indicates a number of active antennas, a transmit power, or both for the network entity. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the network entity comprises a serving network entity. In some other examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the network entity comprises a non-serving network entity, and the first indication of the active NES for the non-serving network entity may be received from a serving network entity.
[0019] An apparatus for wireless communication is described. The apparatus may include a processor and a memory coupled to the processor. The processor may be configured to output, for a UE, a first indication of an active NES for a network entity from a set of multiple NESs. In some examples, the processor may be further configured to output a SSB for the network entity based on the active NES, and to communicate based on the SSB.
[0020] A method for wireless communication is described. The method may include outputting, for a UE, a first indication of an active NES for a network entity from a set of multiple NESs. In some examples, the method may also include outputting a SSB for the network entity based on the active NES, and communicating based on the SSB.
[0021] Another apparatus for wireless communication is described. The apparatus may include means for outputting, for a UE, a first indication of an active NES for a network entity from a set of multiple NESs. In some examples, the apparatus may also include means for outputting an SSB for the network entity based on the active NES, and means for communicating based on the SSB.
[0022] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: output, for a UE, a first indication of an active NES for a network entity from a set of multiple NESs. In some examples, the code may also include instructions executable by the processor to: output a SSB for the network entity based on the active NES; and communicate based on the SSB.
[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting, for the UE, a second indication of a correction factor for a radio measurement threshold corresponding to the active NES.
[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a first signal indicating a list of correction factors to the UE; and outputting a second signal including the second indication of the correction factor in the list of correction factors to the UE.
[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the UE includes a first UE, and the correction factor list includes a first list having a first list size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a third signal to a second UE, the third signal indicating a second list of correction factors, the second list of correction factors having a second list size different from the first list size.
[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first signal comprises an RRC signal, an MIB, an SIB, a RACH signal, or a combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second signal comprises a MAC-CE signal, a DCI signal, or both.
[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, to output the SSB, the methods, apparatus, and non-transitory computer-readable media described herein may include operations, features, components, or instructions for outputting the SSB based on a periodicity for the SSB corresponding to the active NES, a skip mode for the SSB, a first set of SSB opportunities to skip, a second set of SSB opportunities to send, or a combination thereof.
[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: obtaining UE information for the UE; and determining the active NES, a radio measurement configuration for the network entity, or both based on the UE information.
[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, RRC state, or a combination thereof.
[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a third indication of a relaxed measurement configuration for the UE; and determining the active NES, the radio measurement configuration for the network entity, or both based on the relaxed measurement configuration for the UE.
[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a request for an RRM relaxation configuration, an RRM relaxation factor, or both for the network entity; and determining the active NES, the radio measurement configuration for the network entity, or both based on the request.
[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining a number of active antennas, transmit power, or both for the network entity based on the active NES.
[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining, for a second network entity, a second active NES, a correction factor for a radio measurement threshold corresponding to the second network entity, or both. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting, for the UE, a fourth indication of the second active NES, the correction factor, or both for the second network entity, wherein the second network entity comprises a non-serving network entity for the UE.
[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting, for a second network entity, the active NES, a correction factor for a radio measurement threshold corresponding to the network entity, or both. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Figure 1 An example of a wireless communication system supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0036] Figure 2 An example of a network architecture supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0037] Figure 3 An example of a wireless communication system supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0038] Figure 4 An example of supporting a relaxed configuration of an SSB procedure based on network power conservation according to one or more aspects of the present disclosure is illustrated.
[0039] Figure 5 An example of a process flow for supporting an SSB process based on network power conservation according to one or more aspects of the present disclosure is illustrated.
[0040] Figure 6 and Figure 7 A block diagram illustrating a device supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0041] Figure 8 A block diagram illustrating a communication manager supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0042] Figure 9 A diagram illustrating a system including a device supporting an SSB procedure based on network power saving in accordance with one or more aspects of the present disclosure is illustrated.
[0043] Figure 10 and Figure 11 A block diagram illustrating a device supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0044] Figure 12 A block diagram illustrating a communication manager supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated.
[0045] Figure 13 A diagram illustrating a system including a device supporting an SSB procedure based on network power saving in accordance with one or more aspects of the present disclosure is illustrated.
[0046] Figures 14 to 17A flow chart illustrating a method of supporting an SSB procedure based on network power saving according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0047] In some wireless communication systems, a network entity may support network power saving procedures. The network entity may switch between different active NESs to trigger corresponding network power saving procedures. As described herein, an active NES may be the current NES (or network power state or network power mode) activated for a particular cell, a particular network entity, or both. The network entity may support multiple NESs, where each NES corresponds to a particular network power saving configuration, a particular network power saving technique, or both. For example, an NES may define or otherwise indicate a relaxation configuration for the network entity or a UE served by the network entity, a subset of antenna ports (e.g., transmit antenna ports, receive antenna ports) to be used for communication, a transmit power to be used for a signal (e.g., SSB), or any combination thereof. The network entity may switch between different active NESs based on power availability at the network entity, the number or capabilities of the UEs served by the network entity, or a combination thereof. According to one or more examples, the network entity may operate according to one active NES at a time.
[0048] In some examples, a network entity may improve processing overhead associated with transmissions (such as SSB transmissions) by using a specific transmission procedure. For example, the specific SSB transmission procedure may involve the network entity reducing the number of SSBs transmitted, reducing the transmit power associated with the SSB transmission, reducing the number of active antenna ports used for SSB transmission, or some combination thereof. SSBs may be an example of a signal that supports UE synchronization with a cell (e.g., a serving cell or a non-serving cell). The UE may use the SSBs received at the UE to perform one or more measurements. For example, the one or more measurements may include RSRP measurements, RSRQ measurements, or any other RRM or radio link monitoring (RLM) measurements for the cell. These measurements may support cell selection or reselection, synchronization with the cell (e.g., timing synchronization, frequency synchronization), or some combination thereof. The currently active NES for the network entity may indicate a specific SSB transmission procedure for use by the network entity. Coordination of the active NES with one or more UEs may support the UE in performing similar power saving techniques for SSB monitoring, improved measurement accuracy, or both. For example, the UE may monitor SSBs based on the specific SSB transmission procedure corresponding to the currently active NES. The UE may achieve UE power savings (e.g., similar to network power savings) by monitoring a reduced number of SSBs transmitted for a particular SSB transmission procedure. Additionally or alternatively, the UE may perform accurate SSB measurements by considering the transmit power, the number of active antenna ports, or both, used for a particular SSB transmission procedure.
[0049] As described herein, a network entity may output, for one or more UEs, an indication of an active NES from a set of multiple NESs configured for the network entity. In some cases, the indication of the active NES may be a field in a signal (e.g., a DCI signal, a MAC-CE, an RRC signal) that includes a bit value indicating the active NES (e.g., based on a bitmap or other configuration of multiple NESs supported by the network entity). According to one or more examples, the multiple NESs may correspond to different SSB transmission configurations at the network entity. The UE may receive an indication of the active NES, where the active NES corresponds to a serving cell or a non-serving cell (e.g., a neighboring cell) for the UE. Based on the indicated active NES, the UE may determine a radio measurement threshold, a relaxed configuration, or both for SSB measurements. The radio measurement threshold may be an example of any threshold that the UE compares to an SSB measurement to determine whether to trigger an action (e.g., trigger a cell handover). The relaxed configuration may be an example of a configured procedure for reducing power associated with SSB transmissions. A network entity may use a relaxed configuration to reduce the number of SSBs transmitted (e.g., skipping transmission opportunities, increasing the periodicity between SSB transmissions), a UE may use a relaxed configuration to reduce the number of times the UE monitors for SSB transmissions, or both. A network entity associated with a serving cell or a non-serving cell may transmit an SSB using one or more parameters associated with an active NES, and the UE may receive the SSB and perform one or more measurements based on the active NES (e.g., based on a radio measurement threshold, the relaxed configuration, or both). The radio measurement threshold, the relaxed configuration, or both may correspond to the active SSB transmission configuration at the network entity. For example, if the network entity transmits an SSB using reduced transmit power, the UE may determine a modified radio measurement threshold for performing measurements to account for the reduced transmit power. Similarly, if the network entity skips an SSB transmission opportunity, the UE may determine a relaxed configuration indicating that monitoring of the SSB is skipped during the skipped SSB transmission opportunity. Thus, the network entity and the UE may coordinate power conservation and SSB configuration based on an indication of the active NES (e.g., a bit value indicating the active NES). The UE may communicate with the network based on the one or more measurements.
[0050] Various aspects of the subject matter described herein may be implemented by a device to support improved processing overhead, improved power consumption, and improved coordination associated with SSB transmissions. In some cases, a network entity may switch to a specific active NES to achieve power savings. For example, the network entity may improve processing overhead and power consumption based on reducing the transmit power used for SSB transmissions, reducing the number of active antenna ports, or both. Additionally or alternatively, the network entity may improve processing overhead and power consumption based on reducing the number of SSB transmissions (e.g., based on skipping one or more SSB transmission opportunities, based on increasing the periodicity between SSB transmissions). By sending an indication of an active NES to one or more UEs, the network entity may improve coordination between devices within a wireless network. A UE receiving an indication of an active NES may determine a radio measurement threshold, a relaxation configuration, or both for SSB measurements. The UE may improve processing overhead, power consumption, and SSB measurement accuracy based on determining the radio measurement threshold, the relaxation configuration, or both. For example, by adjusting one or more radio measurement thresholds to account for reduced SSB transmit power (e.g., lowering an SSB receive power threshold associated with triggering a cell handover to account for a relatively low transmit power used for SSB transmissions), the UE may improve SSB measurement accuracy and refrain from performing a cell selection or reselection procedure that may result from inaccurate measurements (e.g., measurements performed assuming inaccurate transmit power used for SSB transmissions). Additionally or alternatively, the UE may refrain from monitoring the SSB during opportunities in which SSB transmissions are skipped based on the determined relaxation configuration, thereby improving the UE's processing overhead, power consumption, and SSB measurement accuracy. In some examples, the network entity may send an indication of an active NES for a serving cell, one or more non-serving cells, or some combination thereof to the UE, thereby improving the accuracy of a cell selection or reselection procedure for the UE between a serving cell and one or more non-serving cells.
[0051] As described herein, a correction factor may be an example of a scaling factor or other value indicating an adjustment to a threshold (e.g., a radio measurement threshold, such as an RSRP or RSRQ threshold). For example, a UE may increase or decrease a threshold by adding a correction factor to the threshold, subtracting a correction factor from the threshold, multiplying the correction factor by the threshold, or setting the threshold to a correction factor value. In some cases, an active NES may correspond to different correction factors corresponding to different respective radio measurement thresholds. In some examples, the network may configure the UE with a list of correction factors for a particular threshold, where the list may include multiple correction factors. The network may indicate a single correction factor from the list for the UE to use for a particular threshold. A relaxation configuration (e.g., an RRM or RLM relaxation configuration) may configure one or more power saving procedures at the UE, a network entity, or both. For example, a relaxation configuration may indicate a reduction in SSB monitoring at the UE. A relaxation configuration may indicate skipping of one or more SSBs. For example, a UE may be configured with a set of SSB monitoring opportunities (e.g., based on the periodicity of a channel for monitoring SSBs). The periodicity for SSB monitoring opportunities that are not relaxed (e.g., not corresponding to a relaxation configuration at the UE) may be referred to as a "default" periodicity. The relaxation configuration may indicate a subset of a set of SSB monitoring opportunities for the UE to "skip" or otherwise refrain from monitoring SSBs. The relaxation configuration may indicate specific SSB monitoring opportunities, a pattern of SSB monitoring opportunities (e.g., skipping every two opportunities or every three opportunities), or a combination thereof. Additionally or alternatively, the relaxation configuration may indicate an update to the periodicity for SSB monitoring opportunities. If the updated periodicity is longer than the default periodicity configured for the UE, the UE may save power by monitoring the SSBs relatively less frequently.
[0052] Various aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects of the present disclosure are described with reference to relaxation configurations and process flows. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to a network power saving-based SSB process.
[0053] Figure 1 An example of a wireless communication system 100 that supports a network power saving-based SSB procedure according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0054] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication according to one or more radio access technologies (RATs).
[0055] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105 or other UEs 115 or network entities 105 as shown.
[0056] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.
[0057] Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station and it is also disclosed that a first network node is configured to receive information from a second network node), the broader example of the narrower example can be interpreted inversely, but in a broad, open-ended manner. In the above example where the UE is configured to receive information from a base station and it is also disclosed that the first network node is configured to receive information from the second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first one or more components, a first processing entity, etc. configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second one or more components, a second processing entity, etc.
[0058] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of the other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.
[0059] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0060] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an eNodeB (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home eNodeB, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).
[0061] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0062] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165 such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.
[0063] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0064] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the network power saving-based SSB procedure as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).
[0065] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.
[0066] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.
[0067] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0068] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0069] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).
[0070] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0071] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0072] Physical channels may be multiplexed according to various techniques for communication using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0073] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0074] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.
[0075] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication can include private communication or group communication and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.
[0076] In some examples, a UE 115 can be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group can be outside of the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.
[0077] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0078] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region can be referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter long. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macro cell to provide service to a UE 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) than communication using the smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0079] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.
[0080] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0081] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.
[0082] In view of the above aspects, unless otherwise specified, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as frequencies that may be within FR2, FR4, FR4-a, FR4-1, or FR5, or may include mid-band frequencies.
[0083] A network entity 105 (e.g., a base station 140, a RU 170) or a UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.
[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0085] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also support retransmission using error detection, error correction, or both to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.
[0086] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular time slot for data received via previous symbols in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or based on some other time interval.
[0087] In some wireless communication systems 100, the UE 115 may support an RRM relaxation process to save power (e.g., improve processing overhead) at the UE 115. For example, the UE 115 may support one or more trigger criteria for entering an RRM relaxation mode. The UE 115 may relax measurements (e.g., perform relatively fewer measurements) for intra-frequency NR cells, inter-frequency NR cells, inter-RAT Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) cells, or any combination of these or other cells based on the configured trigger criteria.
[0088] The first triggering criterion for RRM relaxation mode may relate to low mobility at UE 115. If UE 115 satisfies Equation 1 for a period T SearchDeltaP , then UE 115 can be considered to have low mobility, where T SearchDeltaP is the time period used for low mobility evaluation.
[0089] (Srxlev Ref -Srxlev) SearchDeltaP , (1)
[0090] Srxlev is a current cell selection reception level value (eg, in decibels (dB)) for a signal (eg, SSB) received from a serving cell. Ref is the reference cell selection reception level value, and S SearchDeltaP is the low mobility assessment threshold for changes in received power (e.g., in dB). Ref >0 (e.g., Srxlev is increasing), relaxation trigger criteria not met for duration T SearchDeltaP or some combination thereof, UE 115 may set Srxlev Ref Set equal to Srxlev.
[0091] A second triggering criterion for the RRM relaxation mode may involve UE 115 not being located near a cell edge (e.g., UE 115 being located in the relative center of the cell). For example, UE 115 may be located near an edge of a cell (e.g., near an edge of coverage area 110 of network entity 105), or may be located in the relative center of a cell (e.g., not near an edge of coverage area 110 of network entity 105). If UE 115 satisfies Equation 2 (if a cell edge evaluation power threshold S is configured), SearchThresholdP ), Equation 3 (If the cell edge assessment quality threshold S is configured SearchThresholdQ ) or both, then it can be considered that UE 115 is not near the cell edge.
[0092] Srxlev>S SearchThresholdP (2)
[0093] Squal>S SearchThresholdQ (3)
[0094] That is, if the measured reception quality and received power at UE 115 meet (e.g., are greater than) the corresponding thresholds, UE 115 can determine that it is not near a cell edge (e.g., in the relative center of the cell). In some examples, network entity 105 can configure one or both of these trigger criteria for UE 115 to trigger RRM relaxation. Additionally or alternatively, network entity 105 can configure whether UE 115 triggers RRM relaxation based on satisfying any one trigger or based on satisfying both or each of the configured triggers.
[0095] Additionally or alternatively, the UE 115 may use one or more other triggering criteria to enter RRM relaxation mode. For example, a reduced capability (Redcap) UE may support a Redcap UE stationed triggering criterion, a Redcap UE stationed not at cell edge triggering criterion, or any other triggering criterion.
[0096] If UE 115 triggers RRM relaxation, UE 115 may reduce the number of measurements performed at UE 115 based on the periodicity of the measurements, the suspension of the measurements, or both. In some cases, UE 115 may apply a first relaxation method (method 1) by extending the periodicity of the RRM measurements. For example, UE 115 may perform relatively fewer RRM measurements based on performing RRM measurements according to relatively long intervals (e.g., periodicity) (according to a scaling factor). In some other cases, UE 115 may apply a second relaxation method (method 2) by suspending or otherwise stopping RRM measurements for a threshold time (e.g., up to one hour). UE 115 may trigger a particular relaxation method based on one or more triggering criteria satisfied by UE 115 (e.g., according to a lookup table or other configured rules). Thus, UE 115 may support improved processing overhead associated with RRM measurements, for example, by reducing the number of measurements performed by UE 115.
[0097] However, in some wireless communication systems 100, the network entity 105 may similarly perform one or more power saving procedures to improve processing overhead at the network entity 105. In some examples, the power saving procedure may involve reducing processing overhead associated with SSB transmission. The network entity 105 may periodically transmit SSBs (e.g., including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH) portion including one or more PBCH demodulation reference signals (DMRS) and PBCH data) to support RRM measurements performed by the UE 115. For example, the UE 115 may receive the SSBs from the network entity 105, perform one or more measurements on the SSBs, and acquire synchronization (e.g., time synchronization, frequency synchronization) with a cell associated with the network entity 105 based on the SSBs. The UE 115 may determine whether to switch to a different cell based on one or more of the SSB measurements.
[0098] In some systems, the network entity 105 may reduce the number of SSB transmissions performed by the network entity 105 to improve processing overhead and power consumption at the network entity 105. This reduction in the number of SSB transmissions may be referred to as "lightweight SSBs." In some cases, the network entity 105 may transmit relatively sparse SSBs or may transmit SSBs according to a relatively longer periodicity. Additionally or alternatively, the network entity 105 may skip one or more SSB transmission opportunities (or, in some cases, one or more SIB 1 transmission opportunities). In some cases, the network entity 105 may transmit simplified SSBs that include a subset of the SSB information. For example, the simplified SSBs may include the PSS without the SSS or PBCH portion, the PSS and SSS without the PBCH portion, or the PSS, SSS, and a portion of the PBCH portion (e.g., a subset of the PBCH DMRS, a subset of the PBCH data). Additionally or alternatively, the network entity 105 may transmit the SSBs using a reduced number of antenna ports, reduced transmit power, or both, based on the currently active NES at the network entity 105.
[0099] Any such changes to SSB transmission at network entity 105 may affect measurements (e.g., RRM measurements, RLM measurements) performed by UE 115 on SSBs. To support coordination between network entity 105 and UE 115, network entity 105 may indicate network power saving information to UE 115. For example, network entity 105 may support (e.g., using communication manager 102) outputting an indication of an active NES for a serving cell or a non-serving cell for one or more UEs 115. UE 115 may support (e.g., using communication manager 101) receiving an indication of an active NES. Based on the active NES, UE 115 may determine changes to SSB transmission for a serving cell or a non-serving cell and may adjust SSB monitoring accordingly. For example, UE 115 may reduce the number of SSB measurements performed (e.g., based on the current active NES), skip SSB measurement opportunities, process simplified SSBs, perform SSB measurements using adjusted thresholds, or any combination thereof to account for corresponding SSB transmission changes at network entity 105.
[0100] If the network entity 105 configures or otherwise adapts a relatively long periodicity for SSB transmissions, the network entity 105 may support signaling for notifying one or more UEs 115 (e.g., a single UE 115 or a group of UEs 115) of the configuration or adaptation. The network entity 105 may support similar signaling for changes to SIB1 transmissions, uplink RACH opportunities, or both. This signaling may improve system information (SI) acquisition, initial access, RRM measurements, RLM measurements, beam management (BM) measurements, UE performance, or any combination thereof, for the UE 115 to determine an updated periodicity based on the signaling.
[0101] If the network entity 105 skips one or more SSB transmission opportunities, SIB1 transmission opportunities, or both, the network entity 105 may support signaling for notifying one or more UEs 115 (e.g., a single UE 115 or a group of UEs 115) of the skipping. The signaling may improve initial access, RRM measurements, RLM measurements, BM measurements, UE performance, or any combination thereof for the UE 115 to determine the skipped SSB transmission opportunities (and, accordingly, which SSB measurement opportunities to skip at the UE 115) based on the signaling. In some cases, the network entity 105 may perform SSB skipping for a carrier based on the UE capabilities of the UE 115 using the carrier (e.g., if the UE 115 supports skipping of SSB measurement opportunities).
[0102] If the network entity 105 transmits a simplified SSB, the network entity 105 may support signaling for notifying one or more UEs 115 (e.g., a single UE 115 or a group of UEs 115) that the network entity 105 is using a simplified version of the SSB. The signaling may improve SI acquisition, initial access, RRM measurements, RLM measurements, UE mobility, or any combination thereof, for the UE 115 to determine and process the simplified version of the SSB based on the signaling. In some cases, the network entity 105 may perform transmission of a simplified SSB for a carrier based on the UE capabilities of the UE 115 using the carrier (e.g., if the UE 115 supports processing of simplified SSBs). Accordingly, the network entity 105 using the communication manager 102 may support signaling for coordinating network power conservation and UE power conservation with one or more UEs 115. The UE 115 may receive such signaling using the communication manager 101 and may perform SSB monitoring, SSB measurements, or both based on the signaling.
[0103] Figure 2An example of a network architecture 200 supporting a network power saving-based SSB process according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may be an example of a disaggregated base station architecture or a disaggregated RAN architecture. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both). The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). A DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be served by multiple RUs 170-a simultaneously.
[0104] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on the wired transmission medium or to transmit signals to one or more of the other network entities 105 on the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to transmit signals on a wireless transmission medium to one or more of the other network entities 105, or both.
[0105] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.
[0106] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on functional partitioning, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.
[0107] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0108] The SMO 180-a can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 can include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some implementations, the SMO 180-a can communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an 01 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.
[0109] The non-RT RIC 175-a may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or in communication with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b (e.g., via an E2 interface).
[0110] In some examples, non-RT RIC 175-a may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in near-RT RIC 175-b. Such information may be utilized by near-RT RIC 175-b and may be received at SMO 180-a or non-RT RIC 175-a from a non-network data source or from a network function. In some examples, non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions through SMO 180-a (e.g., via reconfiguration of O1) or via generation of RAN management policies (such as A1 policies).
[0111] The network architecture 200 may support network power saving procedures. For example, one or more network entities 105 supporting a cell (e.g., a serving cell for UE 115-a, a neighboring cell for UE 115-a) may enter a network power saving mode (e.g., activate a specific NES) to improve processing overhead at the one or more network entities 105. For example, a CU 160-a, a DU 165-a, a RU 170-a, or any combination thereof may perform the network power saving procedure. The RU 170-a may communicate with the UE 115-a to coordinate network power saving information. For example, the RU 170-a may send an indication of an active NES for a cell or network entity 105 (e.g., for the RU 170-a, DU 165-a, CU 160-a) from a set of multiple NESs to the UE 115-a. Additionally, the RU 170-a (or a different RU 170-a corresponding to the indicated active NES) may send an SSB based on the active NES. In some cases, one network entity 105 of the network architecture 200 may output an indication of an active NES, SSB, or both, and the second network entity 105 may obtain the indication. Additionally or alternatively, any network entity 105 (e.g., CU 160-a, DU 165-a, RU 170-a) may further help facilitate communications with UE 115-a based on the active NES.
[0112] Figure 3 An example of a wireless communication system 300 supporting a SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may be as described herein with reference to Figure 1 The wireless communication system 300 may be used as described herein. Figure 2The wireless communication system 300 may include a first network entity 105-a, a second network entity 105-b, and a UE 115-b, which may be referenced herein. Figure 1 and Figure 2 Examples of corresponding devices described. In some examples, the first network entity 105-a can be an example or component of a serving cell 380-a or a serving network entity, and the second network entity 105-b can be an example or component of a non-serving cell 380-b (e.g., a neighboring cell 380-b) or a non-serving network entity. The first network entity 105-a can communicate with the UE 115-b via a downlink channel 305-a and an uplink channel 310-a. The second network entity 105-b can communicate with the UE 115-b via the downlink channel 305-b and the uplink channel 310-b. The first network entity 105-a and the second network entity 105-b can communicate via one or more links 370 (e.g., a backhaul link). The first network entity 105-a can indicate network power saving information to the UE 115-b, and the UE 115-b can determine a configuration for communication based on the indicated network power saving information (e.g., the indicated active NES 315-a).
[0113] The network entity 105 may support multiple NESs to dynamically adjust network power savings. For example, the network entity 105 may switch from a first NES to a second NES to improve power consumption at the network entity 105. Additionally or alternatively, the network entity 105 may switch from the second NES to the first NES to improve communication coverage, reliability, or both for a set of UEs 115 (e.g., a set of UEs 115 served by the network entity 105). In some examples, the first NES may be referred to as a "default" or "legacy" NES, and the second NES may be referred to as a "power-saving" NES. The network entity 105 may support any number of NESs (e.g., configured at the network entity 105, configured by the core network). In some cases, the first network entity 105-a and the second network entity 105-b may support different numbers of NESs.
[0114] The NES may correspond to a specific number of active antenna ports at the network entity 105 (e.g., active antenna ports for transmission, active antenna ports for reception, or both), a specific transmit power for the network entity 105 (e.g., for control or synchronization signals such as SSB), or both. In some cases, the network entity 105-a may enter a power save mode. The network entity 105-a may reduce the number of active antenna ports, lower the transmit power, or both to improve processing overhead (e.g., improve power consumption) at the network entity 105-a. For example, the network entity 105-a may include an antenna port array 320. The network entity 105-a may deactivate one or more antenna ports in the antenna port array 320 upon entering a low-power mode or switching to a relatively lower-power NES. For example, the network entity 105-a may deactivate physical antennas, logical antenna ports, or both. The network entity 105-a may activate one or more antenna ports in the antenna port array 320 upon entering a full-power mode (e.g., corresponding to a default NES) or switching to a relatively higher-power NES.
[0115] The currently active NES 315-a for the network entity 105-a may affect the transmissions of the network entity 105-a. The network entity 105-a may transmit one or more reference signals, one or more control signals, or both using the number of active antenna ports, the transmit power, or both corresponding to the active NES 315-a. For example, the network entity 105-a may transmit an SSB 340-a based on parameters of the active NES 315-a (e.g., the corresponding number of active antenna ports, the corresponding transmit power). A UE 115-b receiving the SSB 340-a may perform one or more measurements 365 using the SSB 340-a. The measurements 365 (e.g., RRM measurements, RLM measurements) may be affected by the active NES 315-a. For example, the UE 115-b may determine a relatively low-power measurement 365, a relatively low-quality measurement 365, or both based on the network entity 105-a transmitting the SSB 340 using the relatively low-power active NES 315-a.
[0116] The network entity 105-a and the UE 115-b may coordinate network power saving information to take into account the currently active NES 315-a. For example, the network entity 105-a may send an indication of an active NES 315-a (e.g., from a set of multiple NESs supported by the network entity 105) to the UE 115-b. For example, the network entity 105-a may be an example of a serving cell 380-a sending an indication of an active NES 315-a for the serving cell 380-a or sending an indication of an active NES 315-b for the non-serving cell 380-b (e.g., corresponding to the network entity 105-b). The UE 115-b may receive the indication of the active NES (e.g., for the serving cell 380-a or the non-serving cell 380-b) and may determine one or more parameters for receiving SSBs from the serving cell 380-a or the non-serving cell 380-b based on the indicated NES. If the network changes the active NES for a cell, the network entity 105 - a may send an indication of the updated active NES for the cell to one or more UEs 115 .
[0117] In some examples, UE 115-b may determine one or more radio measurement thresholds 350 based on the active NES. For example, the network may change one or more RRM thresholds, one or more RLM thresholds, a duration T for low mobility evaluation, and the like based on the active NES. SearchDeltaP or any combination thereof (e.g., a power save mode at the network). UE 115-b may determine one or more changed thresholds (e.g., adaptation of a threshold, correction of a threshold, different thresholds) based on the indication of the active NES. In some examples, UE 115-b may determine a correction factor 325-a for a radio measurement threshold 350 (e.g., an RSRP threshold, an RSRQ threshold) based on the indicated active NES 315-a. Correction factor 325-a may be an absolute correction (e.g., a value to which the threshold is set) or may be an incremental correction relative to a default power state. For example, UE 115-b may be configured with a default value for radio measurement threshold 350. In some cases, the default value may correspond to NES1 (e.g., a non-power save NES). UE 115-b may determine an active NES (e.g., different from NES1 (the default NES)) and may update the default value for radio measurement threshold 350 based on correction factor 325-a corresponding to the active NES. UE 115 - b may increase or decrease the default value by adding correction factor 325 - a to the default value, subtracting correction factor 325 - a from the default value, multiplying correction factor 325 - a by the default value, or setting the value of radio measurement threshold 350 to the correction factor 325 - a value.
[0118] Additionally or alternatively, UE 115-b may adjust one or more measurements 365 performed based on the indicated active NES 315-a. For example, UE 115-b may apply correction factor 325-a to radio resource measurements performed on SSB 340. UE 115-b may compare the adjusted measurements 365 to default radio measurement thresholds 350. In some examples, UE 115-b may adjust one or more measurements 365 based on active NES 315-a (e.g., using one or more correction factors), adjust one or more radio measurement thresholds 350, or both.
[0119] The network entity 105-a may send a signal configuring one or more correction factors for the UE 115-b. In some examples, the network entity 105-a may indicate the correction factors using L1 signaling, L2 signaling, L3 signaling, or some combination thereof. In some cases, the network entity 105-a may indicate an association between an NES (e.g., a power saving state) and a correction factor. In such cases, the UE 115-b may determine one or more corresponding correction factors to use based on the indicated active NES 315-a. In some other cases, the network entity 105-a may utilize the indicated active NES 315-a to indicate an indication of the one or more corresponding correction factors. In still other cases, the network entity 105-a may indicate the associated one or more correction factors for use by the UE 115-b, and the indicated one or more correction factors may implicitly indicate the currently active NES.
[0120] In some examples, the network entity 105-a may configure one or more lists 330 of correction factors for one or more UEs 115. For example, the network entity 105-a may configure the correction factor list 330 via L3 signaling (such as an RRC signal, an MIB, a SIB (e.g., SIB1 or other SIB), a RACH message, or some other signaling). The correction factor list 330 may include multiple correction factors. The network entity 105-a may indicate a specific correction factor 325-a for use by the UE 115-b from the configured correction factor list 330 for the NES (e.g., for each configured NES). For example, the network entity 105-a may dynamically indicate the correction factor 325-a in the list via L1 signaling or L2 signaling (such as a DCI signal, a MAC-CE, or some other signaling). The network entity 105-a may configure different list sizes for different UEs 115, different NESs, or both. For example, the network entity 105-a may configure the UE 115-b with a first list 330 of correction factors of a first size for a first NES (e.g., having a first number of configured values), configure the UE 115-b with a second list 330 of correction factors of a second size for a second NES, configure a different UE 115 with a third list 330 of correction factors of a third size for the first NES, or any combination thereof. The network entity 105-a may configure a relatively larger list size to support relatively more dynamic configuration (e.g., more options for selecting the correction factors 325-a). The network entity 105-a may configure a relatively smaller list size to support relatively lower signaling overhead (e.g., for configuring the list, for indicating the values within the list).
[0121] As an example, the network entity 105-a may configure the UE 115-b with a first radio measurement threshold 350S for RSRP. SearchThresholdP1 and the second radio measurement threshold 350S for RSRQ SearchThresholdQ1 If a cell (eg, serving cell 380-a or non-serving cell 380-b) is operating with a first NES (NES1), UE 115-b may use the configured threshold S SearchThresholdP1 and S SearchThresholdQ1 For example, if the RSRP measured for SSB 340 satisfies S SearchThresholdP1 If the measured RSRQ for SSB 340 satisfies S SearchThresholdQ1 Or both, UE 115-b may connect to the cell.
[0122] The network entity 105-a may additionally configure the UE 115-b with increment values (e.g., correction factors) for one or more configured thresholds for one or more additional NESs. For example, the network entity 105-a may configure correction factors X1, X2, Y1, Y2, Z1, and Z2 for NES2, NES3, and NES4. Table 1 illustrates how the UE 115-b may use the configured thresholds and configured correction factors to determine thresholds for different active NESs.
[0123]
[0124] Table 1: Example determination of radio measurement thresholds
[0125] In some cases, rather than configuring a single value for a correction factor (eg, X1 or another correction factor), the network entity 105 - a may configure a correction factor list 330 for X1 and may indicate specific values in the list for the UE 115 - b to use for X1.
[0126] In some examples, cells may communicate power state information, correction factor information, or both (e.g., gNB to gNB) to coordinate between cells. Additionally or alternatively, a core network entity or core network function may coordinate power state information, correction factor information, or both across multiple cells (e.g., across network entity 105). Network entity 105-a may be associated with a serving cell 380-a for UE 115-b. Network entity 105-b may be associated with a non-serving cell 380-b (e.g., a neighboring cell 380-b) for UE 115-b. Network entity 105-b may output to network entity 105-a via link 370 (e.g., an Xn interface, an X2 interface) at least one power saving state for the non-serving cell 380-b (e.g., an active NES 315-b for the non-serving cell 380-b), one or more correction factors 325-b, one or more thresholds or configurations for RRM measurements, or any combination thereof. The serving cell 380-a for UE 115-b may provide power state information, correction factor information, or both for one or more other cells (e.g., neighboring cells) to UE 115-b. For example, the network entity 105-a may send an indication of the active NES 315-b, the correction factor 325-b, or both for the network entity 105-b (e.g., associated with the non-serving cell 380-b) to UE 115-b. Accordingly, UE 115-b may adjust RRM measurements (e.g., measurements 365), thresholds (e.g., radio measurement thresholds 350, such as duration T for low mobility), and the like. SearchDeltaP) or any combination thereof for receiving signals (e.g., SSBs) from one or more other cells. For example, UE 115-b may use the indicated active NES 315-b to monitor and measure SSBs 340-b from network entity 105-b (e.g., associated with non-serving cell 380-b). UE 115-b may communicate with network entity 105-b (e.g., via communication 345) based on the measurements of SSBs 340-b. For example, UE 115-b may receive one or more downlink communications 345-c, send one or more uplink communications 345-d, or both.
[0127] In some examples, UE 115-b may determine a relaxed configuration 335-a for a cell (e.g., serving cell 380-a, non-serving cell 380-b) based on the indicated active NES. The relaxed configuration 335-a may indicate to UE 115-b the timing for monitoring SSB 340, the timing for skipping monitoring SSB 340, or both. In some cases, network entity 105-a may send a signal configuring the relaxed configuration (or no relaxation) for the corresponding NES. The signaling may be L1 signaling, L2 signaling, L3 signaling, or some other signaling. UE 115-b may monitor SSB 340 based on the relaxed configuration 335-a corresponding to the indicated active NES 315-a.
[0128] In some examples, UE 115-b may refrain from measuring SSB 340 based on relaxed configuration 335-a. Additionally or alternatively, UE 115-b may drop one or more measurements 365 for SSB 340 based on relaxed configuration 335-a, radio measurement threshold 350, or both. For example, UE 115-b may measure received SSB 340 and may compare measurement 365 of SSB 340 to adjusted radio measurement threshold 350. Based on the comparison, UE 115-b may determine to drop measurement 365 (e.g., UE 115-b may operate as if UE 115-b skipped measurement 365). In some cases, UE 115-b may determine to drop, relax, skip, or cancel one or more measurement opportunities based on the configuration of relaxed configuration 335-a, the configuration of radio measurement threshold 350 for UE 115-b, or both. For example, UE 115-b may refrain from performing measurements based on the configured radio measurement threshold 350 (e.g., UE 115-b may not perform measurements, skip performing measurements, cancel a measurement opportunity, enter a relatively low power mode, or any combination thereof), or UE 115-b may perform these measurements but may refrain from storing these measurements based on the configured radio measurement threshold 350.
[0129] In some cases, one or more UEs 115 may indicate information to a network (e.g., a network entity 105, such as a base station, a core network entity, or any other network entity 105), and the network may use the UE information to select an active NES, determine a correction factor, determine a relaxation configuration, or any combination thereof. For example, a UE 115-b may send UE information 355 to a network entity 105-a (e.g., via L1, L2, or L3 signaling), a core network entity (e.g., via an L1 upper layer protocol, an L2 upper layer protocol, or an L3 upper layer protocol), or both. In some cases, the network entity 105-a may be an example or component of a core network entity. The UE 115-b may send a UE capability report or other UCI signaling indicating the UE information 355. The UE information 355 may include one or more UE capabilities, a UE type, a power state for the UE, a power save mode for the UE, a sleep mode for the UE, a mobility prediction for the UE, or any combination thereof. Based on the obtained UE information 355, the network entity 105-a or the core network entity may determine or otherwise select a configuration (e.g., correction factor 325-a, relaxation configuration 335-a) for the active NES 315-a. The network entity 105-a may indicate the determined configuration for the active NES 315-a to the UE 115-b. In some cases, the network entity 105-a or the core network entity may determine the configuration for the active NES 315-a based on UE information obtained from multiple UEs 115. Additionally or alternatively, multiple cells may coordinate information so that the network (e.g., at the core network) can determine the configuration of the active NES for the non-serving cell.
[0130] In some examples, UE 115-b may indicate to network entity 105-a or a core network entity (e.g., via one or more upper layer protocols) whether the UE supports a relaxation configuration 335-b (e.g., a relaxation mode, one or more specific relaxation configurations), and network entity 105-a or a core network entity may determine an active NES 315-a or a configuration for the active NES 315-a (e.g., a correction factor 325-a, a relaxation configuration 335-a) based on the indicated UE relaxation support. Additionally or alternatively, UE 115-b may indicate to network entity 105-a or a core network entity a currently active UE relaxation configuration 335-b at UE 115-b (e.g., a relaxation measurement configuration). For example, multiple UEs 115 may indicate to network entity 105-a or a core network entity that UE 115 is stationed. In response, the network entity 105-a or the core network entity may determine a relaxed configuration 335-a for these stationed UEs 115 for a certain time period (e.g., one hour) or based on a scaling factor. In some cases, the network may trigger a network power save mode, select a specific SSB configuration, select a specific RRM measurement setting, or any combination thereof for a cell based on the indicated relaxed configuration 335-b for one or more UEs 115 served by the cell.
[0131] Additionally or alternatively, UE 115-b may send a relaxed configuration request 360 to network entity 105-a or a core network entity. For example, UE 115-b may determine the relaxed configuration based on mobility of UE 115-b, a power save mode of UE 115-b, a power state of UE 115-b, a sleep mode of UE 115-b, an RRC state of UE 115-b, or any other UE information 355. UE 115-b may send a request for the determined relaxed configuration (e.g., a request for RRM relaxed configuration) via L1 signaling, L2 signaling, L3 signaling, or any other signaling (e.g., in user assistance information, a dedicated physical uplink control channel (PUCCH) signal, a dedicated physical uplink shared channel (PUSCH) signal, an RRC signal, a MAC-CE). In some examples, UE 115 - b may transmit the determined relaxation configuration to the core network via an L1 upper layer protocol, an L2 upper layer protocol, an L3 upper layer protocol, or some combination thereof. Additionally or alternatively, UE 115 - b may send a request for a specific relaxation factor 375 (e.g., an RRM relaxation factor) to network entity 105 - a or a core network entity (e.g., together with or in place of relaxation configuration request 360). In some examples, UE 115 - b may multiplex relaxation configuration request 360 with L1 signaling, L2 signaling, L3 signaling, or any other signaling (e.g., a scheduling request (SR), a buffer status report (BSR), a HARQ-ACK message, a power headroom (PHR) signal, a channel state information (CSI), a RACH message, a PUSCH message). Based on the relaxed configuration request 360, the network entity 105-a or the core network may determine a relaxed configuration 335-a for the UE 115-b (e.g., corresponding to the active NES 315-a). The network entity 105-a or the core network may select the requested configuration or may select a different configuration based on the request.
[0132] In some examples, network entity 105-a, network entity 105-b, or both may communicate with the core network to support network power saving. For example, network entity 105-a, network entity 105-b, or both may transmit configuration information for one or more network entities 105, one or more UEs 115, or both to the core network, and the core network (e.g., using core network functions) may determine NES information, threshold information, configuration information (e.g., for relaxation configuration), or any combination thereof based on the received configuration information. In some cases, the core network may communicate NES information, threshold information, configuration information, or a combination thereof with one or more network entities 105. For example, the core network may transmit configuration or relaxation information for UE 115 (e.g., UE 115-b) to one or more network entities 105 for different RRC states or NES states. Additionally or alternatively, the core network can support one or more upper layer protocols dedicated to communicating (e.g., with network entity 105, with UE 115) information related to network power saving, such as active NES information, correction factor information, slack configuration information, UE information 355, slack configuration request 360, slack factor 375, or any combination thereof. According to one or more examples, the core network can perform one or more operations described herein with reference to network entity 105-a, network entity 105-b, or both.
[0133] UE 115-b may receive SSB 340-a from network entity 105-a based on active NES 315-a and may perform one or more measurements 365 based on active NES 315-a. UE 115-b may communicate with network entity 105-a based on the measurements of SSB 340-a (e.g., via communication 345). For example, UE 115-b may receive one or more downlink communications 345-a, send one or more uplink communications 345-b, or both.
[0134] Figure 4 An example of a relaxed configuration 400 for supporting a SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The network entity 105-c and the UE 115-c (which may be a reference to Figures 1 to 3400. The example of the described apparatus) may coordinate a relaxation configuration 400. The network entity 105-c may, for example, configure a discontinuous reception (DRX) active time set for the UE 115-c based on a first periodicity 420-a. The DRX active time set may correspond to no relaxation 405 at the network. For example, if the network entity operates according to a first NES associated with no relaxation 405 (e.g., a "default" NES, such as an NES associated with no power saving procedures or ignorable power saving procedures at the network), the network entity may transmit an SSB during each configured DRX active time. During the DRX active time, the network entity 105-c may transmit the SSB, and the UE 115-c may monitor and receive the SSB and perform one or more RRM measurements using the received SSB. However, in some examples, the network entity 105-c may switch to a different active NES 430, which may correspond to a different relaxation configuration 410. For the relaxed configuration 410, the network entity 105 may reduce the number of SSBs sent for reception by the UE 115. To improve coordination between the network entity 105-c and the UE 115-c, the network entity 105 may indicate the current relaxed configuration 410 to the UE 115.
[0135] In some cases, the network entity 105-c may send an indication of an active NES 430 corresponding to a particular relaxation configuration 410. For example, the network entity 105-c (e.g., a serving cell) may configure a relaxation configuration 410 (e.g., an RRM relaxation process) for the UE 115-c per the NES. In some other cases, the network entity 105-c may send an indication of an active relaxation configuration 410 (e.g., based on the active NES 430 at the network entity 105-c). The network entity 105-c may send an indication of the relaxation configuration 410 for the serving cell, one or more corresponding relaxation configurations 410 for one or more non-serving cells, or both. The UE 115-c may modify the configured DRX active time based on the one or more indicated relaxation configurations.
[0136] In some examples, the network entity 105-c may support multiple RRM relaxation configurations, each of which may indicate configuring a specific periodicity length, skipping periodicity, or both. Additionally or alternatively, the RRM relaxation configuration may indicate one or more threshold changes (e.g., an incremental value or threshold for an RSRP threshold, an RSRQ threshold, or another threshold). In some other examples, the network entity 105-c may support a single RRM relaxation configuration that supports multiple RRM measurement relaxation factors. For example, the RRM measurement relaxation factor may define or otherwise indicate a periodicity length, skipping periodicity, or both. Additionally or alternatively, the RRM measurement relaxation factor may indicate one or more threshold changes.
[0137] The network entity 105 may coordinate NES information, relaxed configuration information, or both via one or more interfaces (e.g., an Xn interface or an X2 interface). For example, a neighboring cell may output active NES information to other cells via a backhaul interface so that the serving cell may store active NES information for the neighboring cell (e.g., including corresponding relaxed configuration information). The serving cell may determine an SSB transmission configuration for one or more neighboring cells. The serving cell may send an indication of the relaxed configuration 410 (e.g., for the serving cell or for a non-serving cell), an indication to skip one or more RRM measurement opportunities, an indication of RRM measurement periodicity, or any combination thereof to the UE 115. For example, the serving cell may send the indication via an L1 signal (e.g., a DCI signal), an L2 signal (e.g., a MAC-CE), or an L3 signal (e.g., an RRC signal, a MIB, a SIB, a RACH message).
[0138] In some examples, the network entity 105 - c may configure one or more lists of relaxation factors, RRM measurement configurations, or both via first signaling (e.g., RRC signaling, MAC-CE). The network entity 105 - c may indicate the active relaxation factors, RRM measurement configurations, or both in the list for use by the UE 115 - c via second signaling (e.g., MAC-CE, DCI signaling) based on the currently active NES.
[0139] If configured with no relaxation 405, the UE 115-c may monitor SSBs during a first DRX active time 415-a, a second DRX active time 415-b, a third DRX active time 415-c, and a fourth DRX active time 415-d according to a first periodicity 420-a. The relaxation configuration 410 may involve skipping one or more DRX active times, a modified periodicity, or both. For example, a first relaxation configuration 410-a (e.g., corresponding to a first NES) may involve a first DRX active time 415-e, a skipped DRX opportunity 425-a, a second DRX active time 415-f, and another skipped DRX opportunity 425-b. That is, the network entity 105-c may save power by reducing the number of SSBs transmitted (e.g., by refraining from transmitting every other SSB). UE 115 - c may use the corresponding first relaxed configuration 410 - a to monitor during DRX active times when network entity 105 - c sends SSBs, and refrain from monitoring during skipped DRX opportunities when network entity 105 - c similarly refrains from sending SSBs.
[0140] A second relaxation configuration 410-b (e.g., corresponding to a second NES) may involve a first DRX active time 415-g, a skipped DRX opportunity 425-c, another skipped DRX opportunity 425-d, and a second DRX active time 415-h. The second relaxation configuration 410-b may involve relatively more skipped opportunities than the first relaxation configuration 410-a (e.g., based on the second relaxation configuration 410-b corresponding to a relatively lower energy NES or correspondingly relatively greater network power savings compared to the first relaxation configuration 410-a). A third relaxation configuration 410-c (e.g., corresponding to a third NES) may involve a modified periodicity (e.g., a second periodicity 420-b that is relatively longer than the periodicity 420-a used for no relaxation 405). The third relaxation configuration 410-c may involve a first DRX active time 415-i and a second DRX active time 415-j according to the second periodicity 420-b. The network entity 105 - c may send the SSB according to the second periodicity 420 - b , and the UE 115 - c may monitor the SSB according to the second periodicity 420 - b .
[0141] Figure 5 An example of a process flow 500 for supporting an SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, or any combination thereof. For example, the process flow 500 may include a UE 115-d, a network entity 105-d (e.g., associated with a serving cell for the UE 115-d), and a network entity 105-e (e.g., associated with a non-serving cell for the UE 115-d), which may be as described in reference Figures 1 to 4 UE 115 and network entity 105 are described as examples. Network entity 105-d, network entity 105-e, or both may be examples of a CU, a DU, a RU, a core network entity, or any combination thereof. In the following description of process flow 500, operations between devices may be performed in a different order or at different times. Some operations may be excluded from process flow 500, or other operations may be added. Although UE 115-d, network entity 105-d, and network entity 105-e are shown as performing the operations of process flow 500, some aspects of some operations may also be performed by one or more other devices.
[0142] In some examples, at 505, UE 115-d may send UE information for UE 115-d to network entity 105-d (e.g., associated with a serving cell). The UE information may include UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, RRC state, or a combination thereof.
[0143] In some examples, at 510, UE 115-d may send relaxation configuration information to network entity 105-d. In some cases, the relaxation configuration information may indicate a relaxed measurement configuration for UE 115-d (e.g., indicating that the UE is stationary, indicating that the UE is not near a cell edge). In some other cases, the relaxation configuration information may include a request for an RRM relaxation configuration, an RRM relaxation factor, or both for network entity 105-d. For example, UE 115-d may request network entity 105-d to select a particular relaxation configuration for the active NES.
[0144] In some cases, at 515, the network entity 105-d may determine active NES information. In some examples, the network entity 105-d may determine the active NES information based on the UE information obtained at 505, the relaxed configuration information obtained at 510, or both. Determining the active NES information may involve the network entity 105-d selecting an NES to activate. Additionally or alternatively, determining the active NES information may involve selecting a configuration corresponding to the active NES. The configuration may include a radio measurement threshold corresponding to the active NES, a correction factor for the radio measurement threshold corresponding to the active NES, a relaxed configuration corresponding to the active NES (e.g., an RRM relaxed configuration, an RLM relaxed configuration), a periodicity for SSBs corresponding to the active NES, a skip pattern for SSBs corresponding to the active NES, a first set of SSB opportunities to be skipped for the active NES, a second set of SSB opportunities to be monitored for the active NES, or any combination thereof.
[0145] In some examples, multiple cells may coordinate active NES information such that a serving cell may provide network power saving information to one or more non-serving cells (e.g., neighboring cells). For example, at 520, the network entity 105-e may output a second active NES for the network entity 105-e, a correction factor for a radio measurement threshold corresponding to the second active NES for the network entity 105-e, or both, and the network entity 105-d may obtain the second active NES, the correction factor, or both. Similarly, at 525, the network entity 105-d may output an active NES for the network entity 105-d, a correction factor for a radio measurement threshold corresponding to the active NES for the network entity 105-d, or both, and the network entity 105-e may obtain the active NES, the correction factor, or both.
[0146] At 530, the network entity 105-d may output an indication of an active NES for a network entity (e.g., the network entity 105-d corresponding to the serving cell, the network entity 105-e corresponding to the non-serving cell) from a set of multiple NESs supported by the network. The network entity 105-d may output the indication to a specific UE (e.g., UE 115-d) or may output the indication to multiple UEs served by the network entity 105-d (e.g., via broadcast, multicast, or unicast signaling). The UE 115-d may receive the indication of the active NES.
[0147] In some examples, at 535, UE 115-d may determine one or more radio measurement thresholds based on the indicated active NES. For example, UE 115-d may determine (e.g., receive) a correction factor corresponding to the active NES. UE 115-d may use the correction factor to determine the radio measurement threshold, for example, by setting the radio measurement threshold to a value of the correction factor or by modifying the radio measurement threshold by a value of the correction factor (e.g., adding the correction factor as an incremental value).
[0148] In some examples, at 540, UE 115-d may determine a relaxation configuration based on the indicated active NES. For example, UE 115-d may determine (e.g., receive) an RRM relaxation configuration, an RRM relaxation factor, or both based on the indicated active NES. UE 115-d may determine a periodicity for SSBs, a skip pattern for SSBs, a first set of SSB opportunities to skip, a second set of SSB opportunities to receive, or a combination thereof based on the relaxation configuration.
[0149] At 545, the network entity 105-d may output the SSB based on the active NES. The network entity 105-d may output the SSB according to the relaxed configuration. Additionally or alternatively, the network entity 105-d may output the SSB using the number of antenna ports, transmit power, or both corresponding to the active NES. The UE 115-d may receive the SSB based on the active NES. For example, the UE 115-d may perform one or more measurements of the SSB using the determined one or more radio measurement thresholds. In some cases, the UE 115-d may receive the SSB from a non-serving cell (e.g., the network entity 105-e) based on the active NES for the non-serving cell.
[0150] At 550, UE 115-d may communicate based on one or more measurements of one or more SSBs. In some cases, UE 115-d may communicate with network entity 105-d based on SSBs from network entity 105-d (e.g., according to an active NES of network entity 105-d). In some other cases, UE 115-d may communicate with network entity 105-e based on SSBs from network entity 105-e (e.g., according to an active NES of network entity 105-e).
[0151] Figure 6 A block diagram 600 illustrates a device 605 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure. The device 605 can be an example of aspects of the UE 115 as described herein. The device 605 can include a receiver 610, a transmitter 615, and a communication manager 620, which can be an example of the communication manager 101 as described herein. The device 605 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0152] Receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SSB procedures based on network power conservation). The information may be communicated to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.
[0153] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., a control channel, a data channel, an information channel related to an SSB process based on network power conservation), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.
[0154] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the network power saving based SSB process as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0155] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0156] Additionally or alternatively, in some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0157] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
[0158] According to examples disclosed herein, the communication manager 620 can support wireless communications at a UE. For example, the communication manager 620 can be configured to or otherwise support components for receiving, for a network entity, an indication of an active NES from a set of multiple NESs. The communication manager 620 can be configured to or otherwise support components for receiving an SSB for the network entity based on the active NES. The communication manager 620 can be configured to or otherwise support components for communicating based on one or more measurements associated with the SSB.
[0159] By including or configuring a communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support techniques for improving processing overhead, improving power consumption, more efficiently utilizing communication resources, or any combination thereof for the device 605. For example, the device 605 can determine an RRM relaxation configuration corresponding to an indicated active NES and can receive SSBs according to the RRM relaxation configuration. Based on the relaxation configuration, the device 605 can refrain from monitoring SSBs during skipped SSB transmission opportunities, reduce monitoring opportunities based on an extended periodicity for SSB transmission opportunities, reduce processing resources used to process SSBs based on a simplified version of the SSB, or any combination thereof. Additionally or alternatively, the device 605 can improve measurement accuracy based on determining when to measure SSBs according to the active NES. The improved measurement accuracy can reduce the likelihood that the device 605 will perform unnecessary cell handover or acquisition procedures, thereby further improving processing overhead at the device 605.
[0160] Figure 7 A block diagram 700 illustrates a device 705 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure. The device 705 can be an example of aspects of the device 605 or the UE 115 as described herein. The device 705 can include a receiver 710, a transmitter 715, and a communication manager 720, such as the communication manager 101 as described herein. The device 705 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0161] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to SSB procedures based on network power conservation). The information may be communicated to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.
[0162] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., a control channel, a data channel, an information channel related to an SSB process based on network power conservation), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.
[0163] Device 705 or its various components may be examples of components for performing various aspects of the SSB process based on network power saving as described herein. For example, communication manager 720 may include active NES component 725, SSB component 730, communication component 735, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
[0164] According to examples disclosed herein, the communication manager 720 can support wireless communications at a UE. The active NES component 725 can be configured to or otherwise support means for receiving, for a network entity, an indication of an active NES from a set of multiple NESs. The SSB component 730 can be configured to or otherwise support means for receiving an SSB for the network entity based on the active NES. The communication component 735 can be configured to or otherwise support means for communicating based on one or more measurements associated with the SSB.
[0165] Figure 8 A block diagram 800 illustrates a communication manager 820 that supports a network power saving based SSB process according to one or more aspects of the present disclosure. The communication manager 820 can be an example of aspects of the communication manager 101, the communication manager 620, the communication manager 720, or some combination thereof as described herein. The communication manager 820 or its various components can be examples of components for performing various aspects of the network power saving based SSB process as described herein. For example, the communication manager 820 can include an active NES component 825, an SSB component 830, a communication component 835, a correction factor component 840, a UE information component 845, a relaxation configuration component 850, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).
[0166] According to examples disclosed herein, a communication manager 820 can support wireless communications at a UE. An active NES component 825 can be configured to or otherwise support means for receiving, for a network entity, an indication of an active NES from a set of multiple NESs. An SSB component 830 can be configured to or otherwise support means for receiving an SSB for the network entity based on the active NES. A communication component 835 can be configured to or otherwise support means for communicating based on one or more measurements associated with the SSB.
[0167] In some examples, correction factor component 840 can be configured to or otherwise support means for receiving a second indication of a correction factor corresponding to the active NES. In some examples, correction factor component 840 can be configured to or otherwise support means for determining a radio measurement threshold based on the correction factor, the communication further being based on the radio measurement threshold. In some examples, to determine the radio measurement threshold, correction factor component 840 can be configured to or otherwise support means for setting the radio measurement threshold to the value of the correction factor. In some other examples, to determine the radio measurement threshold, correction factor component 840 can be configured to or otherwise support means for modifying the radio measurement threshold based on the value of the correction factor.
[0168] In some examples, correction factor component 840 can be configured to or otherwise support means for receiving a first signal indicating a correction factor list. In some examples, correction factor component 840 can be configured to or otherwise support means for receiving a second signal including a second indication of a correction factor in the correction factor list. In some examples, the first signal includes an RRC signal, an MIB, an SIB, a RACH signal, or a combination thereof. In some examples, the second signal includes a MAC-CE signal, a DCI signal, or both.
[0169] In some examples, the radio measurement threshold includes an RSRP threshold, an RSRQ threshold, or both.
[0170] In some examples, to receive SSBs, SSB component 830 can be configured to or otherwise support means for receiving SSBs based on a periodicity for SSBs, a skip pattern for SSBs, a first set of SSB opportunities to be skipped, a second set of SSB opportunities to be received, or a combination thereof corresponding to an active NES. In some examples, slack configuration component 850 can be configured to or otherwise support means for determining an RRM slack configuration, an RRM slack factor, or both based on the active NES. In some examples, the periodicity for SSBs, the skip pattern for SSBs, the first set of SSB opportunities to be skipped, the second set of SSB opportunities to be received, or a combination thereof can be based on the RRM slack configuration, the RRM slack factor, or both.
[0171] In some examples, UE information component 845 can be configured to or otherwise support components for transmitting UE information for the UE. In some examples, the active NES, the radio measurement configuration for the network entity, or both can be based on the UE information. In some examples, the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, RRC state, or a combination thereof.
[0172] In some examples, relaxed configuration component 850 can be configured as or otherwise support means for sending a second indication of a relaxed measurement configuration for the UE.In some examples, the active NES, the radio measurement configuration for the network entity, or both can be based on the relaxed measurement configuration for the UE.
[0173] In some examples, slack configuration component 850 can be configured as or otherwise support means for sending a request for an RRM slack configuration, an RRM slack factor, or both for a network entity. In some examples, an active NES, a radio measurement configuration for the network entity, or both can be based on the request.
[0174] In some examples, the active NES indicates the number of active antennas, transmit power, or both for the network entity. In some examples, the network entity comprises a serving network entity. In some other examples, the network entity comprises a non-serving network entity, wherein the indication of the active NES for the non-serving network entity is received from the serving network entity.
[0175] Figure 9A diagram illustrating a system 900 including a device 905 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure is shown. The device 905 may be an example of, or include components of, a device 605, a device 705, or a UE 115 as described herein. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).
[0176] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor, such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.
[0177] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets; providing the modulated packets to the one or more antennas 925 for transmission; and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and the one or more antennas 925, may be examples of the transmitter 615, the transmitter 715, the receiver 610, the receiver 710, or any combination thereof, or components thereof, as described herein.
[0178] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform the various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0179] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., various functions or tasks of supporting an SSB process based on network power saving). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, the processor 940 and the memory 930 being configured to perform the various functions described herein.
[0180] According to examples disclosed herein, the communication manager 920 can support wireless communications at a UE. For example, the communication manager 920 can be configured to or otherwise support components for receiving, for a network entity, an indication of an active NES from a set of multiple NESs. The communication manager 920 can be configured to or otherwise support components for receiving an SSB for the network entity based on the active NES. The communication manager 920 can be configured to or otherwise support components for communicating based on one or more measurements associated with the SSB.
[0181] By including or configuring a communication manager 920 according to the examples described herein, the device 905 may support techniques for improving communication reliability, improving power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof. For example, based on the network entity coordinating an active NES with the device 905, the device 905 may perform accurate and efficient SSB measurements based on the active NES. For example, the device 905 may improve processing overhead and power consumption by skipping SSB measurements, performing SSB measurements according to increased periodicity, or both. Additionally or alternatively, the device 905 may support improved measurement accuracy based on using a measurement threshold corresponding to the indicated active NES. The improved measurement accuracy may result in improved cell selection for the device 905.
[0182] In some examples, the communication manager 920 can be configured to use or otherwise cooperate with the transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the SSB process based on network power saving as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support such operations.
[0183] Figure 10 A block diagram 1000 illustrates a device 1005 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020, which may be an example of the communication manager 102 as described herein. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0184] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0185] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.
[0186] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the network power saving based SSB process as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0187] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0188] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in this disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0189] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
[0190] According to examples disclosed herein, the communication manager 1020 can support wireless communications. For example, the communication manager 1020 can be configured to or otherwise support components for outputting, for a UE, an indication of an active NES for a network entity from a set of multiple NESs. The communication manager 1020 can be configured to or otherwise support components for outputting an SSB for the network entity based on the active NES. The communication manager 1020 can be configured to or otherwise support components for communicating (e.g., with a UE) based on the SSB.
[0191] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for improving processing overhead and improving power consumption for the device 1005. For example, the device 1005 can support an active NES, thereby allowing the device 1005 to reduce the number of SSB transmissions. Reducing the number of SSB transmissions can improve processing overhead and power consumption at the device 1005. Additionally or alternatively, based on indicating the active NES to the UE 115, the device 1005 can improve coordination with the UE 115, thereby improving the accuracy of the cell selection or reselection process at the UE 115. Thus, the device 1005 can improve the processing overhead and power consumption associated with the cell selection and reselection process for the UE 115.
[0192] Figure 11 A block diagram 1100 illustrates a device 1105 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120, which may be an example of the communication manager 102 as described herein. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0193] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0194] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.
[0195] Device 1105 or its various components may be examples of components for performing various aspects of the SSB process based on network power saving as described herein. For example, communication manager 1120 may include active NES component 1125, SSB component 1130, communication component 1135, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
[0196] According to examples disclosed herein, a communication manager 1120 can support wireless communications. An active NES component 1125 can be configured to or otherwise support means for outputting, for a UE, an indication of an active NES for a network entity from a set of multiple NESs. An SSB component 1130 can be configured to or otherwise support means for outputting an SSB for the network entity based on the active NES. A communication component 1135 can be configured to or otherwise support means for communicating based on the SSB.
[0197] Figure 12A block diagram 1200 illustrates a communication manager 1220 that supports a network power saving based SSB process according to one or more aspects of the present disclosure. The communication manager 1220 can be an example of aspects of the communication manager 102, the communication manager 1020, the communication manager 1120, or some combination thereof as described herein. The communication manager 1220 or its various components can be examples of means for performing various aspects of the network power saving based SSB process as described herein. For example, the communication manager 1220 can include an active NES component 1225, an SSB component 1230, a communication component 1235, a correction factor component 1240, a UE information component 1245, a slack configuration component 1250, a network coordination component 1255, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.
[0198] According to examples disclosed herein, the communication manager 1220 can support wireless communications. The active NES component 1225 can be configured to or otherwise support means for outputting, for a UE, an indication of an active NES for a network entity from a set of multiple NESs. The SSB component 1230 can be configured to or otherwise support means for outputting an SSB for the network entity based on the active NES. The communication component 1235 can be configured to or otherwise support means for communicating based on the SSB.
[0199] In some examples, correction factor component 1240 may be configured to or otherwise support means for outputting, for a UE, a second indication of a correction factor for a radio measurement threshold corresponding to an active NES. In some examples, correction factor component 1240 may be configured to or otherwise support means for outputting, for a UE, a first signal indicating a correction factor list. In some examples, correction factor component 1240 may be configured to or otherwise support means for outputting, for a UE, a second signal including a second indication of a correction factor in the correction factor list. In some examples, the UE may be an example of a first UE, and the correction factor list may be an example of a first list having a first list size. In some examples, correction factor component 1240 may be configured to or otherwise support means for outputting, for a second UE, a third signal indicating a second list of correction factors, the second list of correction factors having a second list size different from the first list size. In some examples, the first signal comprises an RRC signal, an MIB, an SIB, a RACH signal, or a combination thereof. In some examples, the second signal comprises a MAC-CE signal, a DCI signal, or both.
[0200] In some examples, to output SSB, SSB component 1230 may be configured or otherwise support components for outputting SSB based on a periodicity for SSB corresponding to an active NES, a skip mode for SSB, a first set of SSB opportunities to skip, a second set of SSB opportunities to send, or a combination thereof.
[0201] In some examples, UE information component 1245 can be configured to or otherwise support components for obtaining UE information for the UE. In some examples, UE information component 1245 can be configured to or otherwise support components for determining an active NES, a radio measurement configuration for a network entity, or both based on the UE information. In some examples, the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, RRC state, or a combination thereof.
[0202] In some examples, relaxed configuration component 1250 can be configured as or otherwise support means for obtaining a second indication of a relaxed measurement configuration for the UE. In some examples, relaxed configuration component 1250 can be configured as or otherwise support means for determining an active NES, a radio measurement configuration for a network entity, or both based on the relaxed measurement configuration for the UE.
[0203] In some examples, slack configuration component 1250 can be configured as or otherwise support means for obtaining a request for an RRM slack configuration, an RRM slack factor, or both for a network entity. In some examples, slack configuration component 1250 can be configured as or otherwise support means for determining an active NES, a radio measurement configuration for the network entity, or both based on the request.
[0204] In some examples, active NES component 1225 may be configured or otherwise support means for determining the number of active antennas, transmit power, or both for a network entity based on the active NES.
[0205] In some examples, network coordination component 1255 can be configured to or otherwise support means for obtaining a second active NES for a second network entity, a correction factor for a radio measurement threshold corresponding to the second network entity, or both. In some examples, network coordination component 1255 can be configured to or otherwise support means for outputting, for the UE, a second indication of the second active NES, the correction factor, or both for the second network entity, wherein the second network entity comprises a non-serving network entity for the UE.
[0206] In some examples, network coordination component 1255 can be configured or otherwise support means for outputting an active NES for a second network entity, a correction factor for a radio measurement threshold corresponding to the network entity, or both.
[0207] Figure 13 A diagram illustrates a system 1300 including a device 1305 that supports a network power saving-based SSB process according to one or more aspects of the present disclosure. Device 1305 may be an example of, or include components of, device 1005, device 1105, or a network entity 105 (e.g., a CU, DU, RU, or some combination thereof) as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).
[0208] The transceiver 1310 may support bidirectional communication as described herein via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1310 can include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof.
[0209] In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).
[0210] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0211] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., various functions or tasks of supporting an SSB process based on network power saving). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality for performing (e.g., by executing code 1330) the functions of device 1305. Processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within memory 1325).
[0212] In some implementations, the processor 1335 may be a component of a processing system. A processing system may refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs that can be passed to other systems or components (e.g., device 1305). For example, the processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of device 1305.
[0213] The processing system of device 1305 can interface with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information, for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, allowing device 1305 to transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, allowing device 1305 to obtain information or signal input and pass the information to the processing system. One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.
[0214] In some examples, bus 1340 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).
[0215] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications to client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for coordinating communications with UEs 115 with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0216] According to examples disclosed herein, the communication manager 1320 can support wireless communications. For example, the communication manager 1320 can be configured to or otherwise support components for outputting, for a UE, an indication of an active NES for a network entity from a set of multiple NESs. The communication manager 1320 can be configured to or otherwise support components for outputting an SSB for the network entity based on the active NES. The communication manager 1320 can be configured to or otherwise support components for communicating based on the SSB.
[0217] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 can support techniques for improving communication reliability, improving power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof. For example, the device 1305 can operate according to an active NES to improve processing overhead and power consumption, and the device 1305 can indicate the active NES to one or more UEs 115 to improve coordination between devices within the wireless network.
[0218] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 can include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the SSB process based on network power saving as described herein, or the processor 1335 and the memory 1325 can be otherwise configured to perform or support such operations.
[0219] Figure 14 A flowchart illustrating a method 1400 for supporting a SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9 The UE 115 described herein performs the functions described herein. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0220] At 1405, the method may include receiving, for a network entity, an indication of an active NES in a set of multiple NESs. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described activities are performed by NES component 825.
[0221] At 1410, the method may include receiving an SSB for a network entity based on the active NES. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The SSB component 830 is described as performing.
[0222] At 1415, the method may include communicating based on one or more measurements associated with the SSB. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The communication component 835 is described as executing.
[0223] Figure 15 A flowchart illustrating a method 1500 for supporting a SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0224] At 1505, the method may include receiving, for a network entity, an indication of an active NES in a set of multiple NESs. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described activities are performed by NES component 825.
[0225] In some examples, at 1510, the method may include receiving a second indication of a correction factor corresponding to the active NES. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The correction factor component 840 is described as performing.
[0226] In some examples, at 1515, the method may include determining a radio measurement threshold based on the correction factor. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The correction factor component 840 is described as performing.
[0227] In some cases, at 1520, to determine the radio measurement threshold, the method may include setting the radio measurement threshold to a value of the correction factor. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The correction factor component 840 is described as performing.
[0228] In some other cases, at 1525, to determine the radio measurement threshold, the method may include modifying the radio measurement threshold according to the value of the correction factor. The operations of 1525 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 8 The correction factor component 840 is described as performing.
[0229] At 1530, the method may include receiving an SSB for the network entity based on the active NES. The operations of 1530 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1530 may be performed as described in reference to Figure 8 The SSB component 830 is described as performing.
[0230] At 1535, the method may include communicating based on one or more measurements associated with the SSB and further based on a radio measurement threshold. For example, the method may include comparing a measurement in the one or more measurements to a radio measurement threshold determined for the active NES. The operations of 1535 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1535 may be performed as described in reference to Figure 8 The communication component 835 is described as executing.
[0231] Figure 16 A flowchart illustrating a method 1600 for supporting an SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The UE 115 described herein performs the functions described herein. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.
[0232] In some examples, at 1605, the method may include sending UE information for the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The UE information component 845 is described as performing.
[0233] In some examples, at 1610, the method may include sending an indication of a relaxed measurement configuration for the UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The described relaxation configuration component 850 performs.
[0234] At 1615, the method may include receiving, for the network entity, an indication of an active NES from a set of multiple NESs. The active NES, the radio measurement configuration for the network entity, or both may be based on UE information, a relaxed measurement configuration for the UE, or both. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The described activities are performed by NES component 825.
[0235] At 1620, the method may include receiving an SSB for the network entity based on the active NES. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 8 The SSB component 830 is described as performing.
[0236] At 1625, the method may include communicating based on one or more measurements associated with the SSB. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Figure 8 The communication component 835 is described as executing.
[0237] Figure 17 A flow chart illustrating a method 1700 for supporting a SSB process based on network power saving according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a network entity (e.g., a RU, a DU, a CU, or some combination thereof) or a component thereof as described herein. The network entity may be associated with a serving cell for a UE or a non-serving cell for a UE (e.g., a neighboring cell). The operations of the method 1700 may be implemented by a network entity (e.g., a RU, a DU, a CU, or some combination thereof) or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13The network entity described herein performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0238] At 1705, the method may include outputting, for the UE, an indication of an active NES for the network entity from a set of multiple NESs. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 12 The described activities are performed by NES component 1225.
[0239] At 1710, the method may include outputting an SSB for a network entity based on the active NES. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 12 The SSB component 1230 described performs.
[0240] At 1715, the method may include communicating based on SSB. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 12 The communication component 1235 is described as executing.
[0241] The following provides an overview of various aspects of the disclosure:
[0242] Aspect 1: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; and a memory coupled to the processor, the processor configured to: receive a first indication of an active network energy state among a plurality of network energy states for a network entity; receive a synchronization signal block for the network entity based at least in part on the active network energy state; and communicate based at least in part on one or more measurements associated with the synchronization signal block.
[0243] Aspect 2: An apparatus according to Aspect 1, wherein the processor is further configured to: receive a second indication of a correction factor corresponding to the active network energy state; and determine a radio measurement threshold based at least in part on the correction factor, and the communication is further based at least in part on the radio measurement threshold.
[0244] Aspect 3: The apparatus according to aspect 2, wherein, in order to determine the radio measurement threshold, the processor is configured to: set the radio measurement threshold to the value of the correction factor; or modify the radio measurement threshold according to the value of the correction factor.
[0245] Aspect 4: An apparatus according to any one of Aspects 2 to 3, wherein the processor is further configured to: receive a first signal indicating a correction factor list; and receive a second signal, the second signal including the second indication of the correction factor in the correction factor list.
[0246] Aspect 5: An apparatus according to Aspect 4, wherein the first signal comprises a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and the second signal comprises a medium access channel element, a downlink control information signal, or both.
[0247] Aspect 6: The apparatus according to any one of aspects 2 to 5, wherein the radio measurement threshold comprises a reference signal received power threshold, a reference signal received quality threshold, or both.
[0248] Aspect 7: An apparatus according to any one of Aspects 1 to 6, wherein, in order to receive the synchronization signal block, the processor is configured to: receive the synchronization signal block based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip mode for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be received, or a combination thereof.
[0249] Aspect 8: An apparatus according to Aspect 7, wherein the processor is further configured to: determine a radio resource management relaxation configuration, a radio resource management relaxation factor, or both based at least in part on the active network energy state, the periodicity of the synchronization signal block, the skip mode for the synchronization signal block, the first set of synchronization signal block opportunities to be skipped, the second set of synchronization signal block opportunities to be received, or the combination thereof based at least in part on the radio resource management relaxation configuration, the radio resource management relaxation factor, or both.
[0250] Aspect 9: The apparatus according to any one of aspects 1 to 8, wherein the processor is further configured to: send UE information, the active network energy state, the radio measurement configuration for the network entity, or both are at least partially based on the UE information.
[0251] Aspect 10: The apparatus according to aspect 9, wherein the UE information comprises UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
[0252] Aspect 11: An apparatus according to any one of Aspects 1 to 10, wherein the processor is further configured to: send a third indication of a relaxed measurement configuration for the UE, the active network energy state, the radio measurement configuration for the network entity, or both being at least partially based on the relaxed measurement configuration for the UE.
[0253] Aspect 12: An apparatus according to any one of Aspects 1 to 11, wherein the processor is further configured to: send a request for a radio resource management relaxation configuration, a radio resource management relaxation factor, or both for the network entity, and the active network energy state, the radio measurement configuration for the network entity, or both are at least partially based on the request.
[0254] Aspect 13: The apparatus according to any one of aspects 1 to 12, wherein the active network energy state indicates the number of active antennas, transmit power, or both for the network entity.
[0255] Aspect 14: The apparatus according to any one of aspects 1 to 13, wherein the network entity comprises a serving network entity.
[0256] Aspect 15: The apparatus of any one of aspects 1 to 13, wherein the network entity comprises a non-serving network entity; and the first indication of the active network energy state for the non-serving network entity is received from a serving network entity.
[0257] Aspect 16: An apparatus for wireless communication, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to: output, for a UE, a first indication of an active network energy state for a network entity among a plurality of network energy states; output a synchronization signal block for the network entity based at least in part on the active network energy state; and communicate based at least in part on the synchronization signal block.
[0258] Aspect 17: The apparatus according to aspect 16, wherein the processor is further configured to: output, for the UE, a second indication of a correction factor for a radio measurement threshold corresponding to the active network energy state.
[0259] Aspect 18: The apparatus according to Aspect 17, wherein the processor is further configured to: output a first signal indicating a correction factor list to the UE; and output a second signal to the UE, the second signal including the second indication of the correction factor in the correction factor list.
[0260] Aspect 19: An apparatus according to Aspect 18, wherein the UE includes a first UE and the correction factor list includes a first list having a first list size, and the processor is further configured to: output a third signal for a second UE, the third signal indicating a second list of correction factors, and the second list of correction factors having a second list size different from the first list size.
[0261] Aspect 20: An apparatus according to any one of Aspects 18 to 19, wherein the first signal comprises a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and the second signal comprises a medium access channel element, a downlink control information signal, or both.
[0262] Aspect 21: An apparatus according to any one of Aspects 16 to 20, wherein, in order to output the synchronization signal block, the processor is configured to: output the synchronization signal block based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip mode for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be sent, or a combination thereof.
[0263] Aspect 22: An apparatus according to any one of Aspects 16 to 21, wherein the processor is further configured to: obtain UE information for the UE; and determine the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the UE information.
[0264] Aspect 23: The apparatus according to aspect 22, wherein the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
[0265] Aspect 24: An apparatus according to any one of Aspects 16 to 23, wherein the processor is further configured to: obtain a third indication of a relaxed measurement configuration for the UE; and determine the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the relaxed measurement configuration for the UE.
[0266] Aspect 25: An apparatus according to any one of Aspects 16 to 24, wherein the processor is further configured to: obtain a request for a radio resource management relaxation configuration, a radio resource management relaxation factor, or both for the network entity; and determine the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the request.
[0267] Aspect 26: The apparatus of any one of aspects 16 to 25, wherein the processor is further configured to determine the number of active antennas, transmit power, or both for the network entity based at least in part on the active network energy state.
[0268] Aspect 27: An apparatus according to any one of Aspects 16 to 26, wherein the processor is further configured to: obtain a second active network energy state, a correction factor for a radio measurement threshold corresponding to the second network entity, or both for a second network entity; and output a fourth indication of the second active network energy state, the correction factor, or both for the second network entity for the UE, wherein the second network entity includes a non-serving network entity for the UE.
[0269] Aspect 28: The apparatus according to any one of aspects 16 to 27, wherein the processor is further configured to: output the active network energy state, a correction factor for a radio measurement threshold corresponding to the network entity, or both for a second network entity.
[0270] Aspect 29: A method for wireless communication at a UE, the method comprising: receiving a first indication of an active network energy state among a plurality of network energy states for a network entity; receiving a synchronization signal block for the network entity based at least in part on the active network energy state; and communicating based at least in part on one or more measurements associated with the synchronization signal block.
[0271] Aspect 30: The method according to Aspect 29 further includes: receiving a second indication of a correction factor corresponding to the active network energy state; and determining a radio measurement threshold based at least in part on the correction factor, the communication being further based at least in part on the radio measurement threshold.
[0272] Aspect 31: According to the method of aspect 30, determining the radio measurement threshold comprises: setting the radio measurement threshold to a value of the correction factor; or modifying the radio measurement threshold according to the value of the correction factor.
[0273] Aspect 32: The method according to any one of aspects 30 to 31, further comprising: receiving a first signal indicating a correction factor list; and receiving a second signal, the second signal comprising the second indication of the correction factor in the correction factor list.
[0274] Aspect 33: A method according to Aspect 32, wherein the first signal includes a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and the second signal includes a medium access channel element, a downlink control information signal, or both.
[0275] Aspect 34: The method according to any one of aspects 30 to 33, wherein the radio measurement threshold comprises a reference signal received power threshold, a reference signal received quality threshold, or both.
[0276] Aspect 35: According to the method described in any one of Aspects 29 to 34, receiving the synchronization signal block includes: receiving the synchronization signal block based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip mode for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be received, or a combination thereof.
[0277] Aspect 36: According to the method of Aspect 35, the method also includes: determining a radio resource management relaxation configuration, a radio resource management relaxation factor, or both based at least in part on the active network energy state, the periodicity of the synchronization signal block, the skip mode for the synchronization signal block, the first set of synchronization signal block opportunities to be skipped, the second set of synchronization signal block opportunities to be received, or the combination thereof based at least in part on the radio resource management relaxation configuration, the radio resource management relaxation factor, or both.
[0278] Aspect 37: The method according to any one of aspects 29 to 36 further comprises: sending UE information, the active network energy state, the radio measurement configuration for the network entity, or both being based at least in part on the UE information.
[0279] Aspect 38: The method according to aspect 37, wherein the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
[0280] Aspect 39: According to any one of Aspects 29 to 38, the method further includes: sending a third indication of a relaxed measurement configuration for the UE, the active network energy state, the radio measurement configuration for the network entity, or both being at least partially based on the relaxed measurement configuration for the UE.
[0281] Aspect 40: The method according to any one of Aspects 29 to 39, further comprising: sending a request for a radio resource management relaxation configuration, a radio resource management relaxation factor, or both for the network entity, the active network energy state, the radio measurement configuration for the network entity, or both being at least partially based on the request.
[0282] Aspect 41: The method according to any one of aspects 29 to 40, wherein the active network energy state indicates the number of active antennas, transmit power, or both for the network entity.
[0283] Aspect 42: The method according to any one of aspects 29 to 41, wherein the network entity comprises a serving network entity.
[0284] Aspect 43: The method according to any one of aspects 29 to 41, wherein the network entity comprises a non-serving network entity; and the first indication of the active network energy state for the non-serving network entity is received from a serving network entity.
[0285] Aspect 44: A method for wireless communication, the method comprising: outputting, for a UE, a first indication of an active network energy state for a network entity among a plurality of network energy states; outputting a synchronization signal block for the network entity based at least in part on the active network energy state; and communicating based at least in part on the synchronization signal block.
[0286] Aspect 45: The method according to aspect 44, further comprising: outputting, for the UE, a second indication of a correction factor for a radio measurement threshold corresponding to the active network energy state.
[0287] Aspect 46: The method according to aspect 45 further includes: outputting a first signal indicating a correction factor list to the UE; and outputting a second signal to the UE, the second signal including the second indication of the correction factor in the correction factor list.
[0288] Aspect 47: A method according to Aspect 46, wherein the UE includes a first UE, and the correction factor list includes a first list having a first list size, and the method further includes: outputting a third signal for a second UE, the third signal indicating a second list of correction factors, and the second list of correction factors having a second list size different from the first list size.
[0289] Aspect 48: A method according to any one of Aspects 46 to 47, wherein the first signal includes a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and the second signal includes a medium access channel element, a downlink control information signal, or both.
[0290] Aspect 49: According to the method described in any one of Aspects 44 to 48, outputting the synchronization signal block includes: outputting the synchronization signal block based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip mode for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be sent, or a combination thereof.
[0291] Aspect 50: The method according to any one of Aspects 44 to 49, further comprising: obtaining UE information for the UE; and determining the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the UE information.
[0292] Aspect 51: The method according to aspect 50, wherein the UE information includes UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
[0293] Aspect 52: According to the method described in any one of Aspects 44 to 51, the method further includes: obtaining a third indication of a relaxed measurement configuration for the UE; and determining the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the relaxed measurement configuration for the UE.
[0294] Aspect 53: According to the method described in any one of Aspects 44 to 52, the method also includes: obtaining a request for a radio resource management relaxation configuration, a radio resource management relaxation factor, or both for the network entity; and determining the active network energy state, the radio measurement configuration for the network entity, or both based at least in part on the request.
[0295] Aspect 54: The method according to any one of aspects 44 to 53, further comprising: determining the number of active antennas, transmit power, or both for the network entity based at least in part on the active network energy state.
[0296] Aspect 55: According to the method described in any one of Aspects 44 to 54, the method further includes: obtaining a second active network energy state, a correction factor for a radio measurement threshold corresponding to the second network entity, or both for a second network entity; and outputting a fourth indication of the second active network energy state, the correction factor, or both for the second network entity for the UE, wherein the second network entity includes a non-serving network entity for the UE.
[0297] Aspect 56: The method according to any one of aspects 44 to 55, further comprising: outputting the active network energy state, a correction factor for a radio measurement threshold corresponding to the network entity, or both, for a second network entity.
[0298] Aspect 57: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 29 to 43.
[0299] Aspect 58: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 29 to 43.
[0300] Aspect 59: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to any one of aspects 44 to 56.
[0301] Aspect 60: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of aspects 44 to 56.
[0302] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0303] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0304] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0305] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).
[0306] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.
[0307] Computer-readable media includes both non-transient computer storage media and communication media, and the communication media includes any medium that promotes a computer program to be transferred from one location to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, a server or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL) or a wireless technology such as infrared, radio and microwave, then the coaxial cable, the fiber optic cable, the twisted pair, the DSL or the wireless technology such as infrared, radio and microwave are included in the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Magnetic disks can reproduce data magnetically, and optical discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
[0308] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."
[0309] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.
[0310] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description can apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.
[0311] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0312] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; as well as a memory coupled to the processor, the processor being configured to: receiving, for a network entity, a first indication of an active network energy state among a plurality of network energy states; receiving a synchronization signal block for the network entity based at least in part on the active network energy state; as well as Communicating is performed based at least in part on one or more measurements associated with the synchronization signal block.
2. The apparatus of claim 1 , wherein the processor is further configured to: receiving a second indication of a correction factor corresponding to the active network energy state; and A radio measurement threshold is determined based at least in part on the correction factor, the communicating being further based at least in part on the radio measurement threshold.
3. The apparatus of claim 2 , wherein to determine the radio measurement threshold, the processor is configured to: setting the radio measurement threshold to the value of the correction factor; or The radio measurement threshold is modified according to the value of the correction factor.
4. The apparatus of claim 2, wherein the processor is further configured to: receiving a first signal indicative of a list of correction factors; and A second signal is received, the second signal including the second indication of the correction factor in the correction factor list.
5. The device according to claim 4, wherein: The first signal comprises a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and The second signal includes a medium access channel element, a downlink control information signal, or both. The apparatus according to claim 2 , wherein the radio measurement threshold comprises a reference signal received power threshold, a reference signal received quality threshold, or both.
7. The apparatus of claim 1 , wherein to receive the synchronization signal block, the processor is configured to: The synchronization signal block is received based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip pattern for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be received, or a combination thereof.
8. The apparatus of claim 7, wherein the processor is further configured to: determining a radio resource management slack configuration, a radio resource management slack factor, or both based at least in part on the active network energy state, The periodicity for synchronization signal blocks, the skip mode for the synchronization signal blocks, the first set of synchronization signal block opportunities to be skipped, the second set of synchronization signal block opportunities to be received, or the combination thereof is at least partially based on the radio resource management relaxation configuration, the radio resource management relaxation factor, or both.
9. The apparatus of claim 1 , wherein the processor is further configured to: Send UE information, The active network energy state, a radio measurement configuration for the network entity, or both are based at least in part on the UE information.
10. The apparatus of claim 9, wherein the UE information comprises UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
11. The apparatus of claim 1 , wherein the processor is further configured to: sending a third indication of a relaxed measurement configuration for the UE, The active network energy state, the radio measurement configuration for the network entity, or both are based at least in part on the relaxed measurement configuration for the UE.
12. The apparatus of claim 1 , wherein the processor is further configured to: sending a request for a radio resource management slack configuration, a radio resource management slack factor, or both for the network entity, The active network energy state, a radio measurement configuration for the network entity, or both are based at least in part on the request.
13. The apparatus of claim 1, wherein the active network energy state indicates a number of active antennas, transmit power, or both for the network entity.
14. The apparatus of claim 1, wherein the network entity comprises a serving network entity.
15. The apparatus according to claim 1, wherein: The network entity comprises a non-serving network entity; and The first indication of the active network energy state for the non-serving network entity is received from a serving network entity.
16. An apparatus for wireless communication, the apparatus comprising: processor; as well as a memory coupled to the processor, the processor being configured to: outputting, for a user equipment (UE), a first indication of an active network energy state for a network entity among a plurality of network energy states; outputting a synchronization signal block for the network entity based at least in part on the active network energy state; as well as Communicating is performed based at least in part on the synchronization signal blocks.
17. The apparatus of claim 16, wherein the processor is further configured to: A second indication of a correction factor for a radio measurement threshold corresponding to the active network energy state is output for the UE.
18. The apparatus of claim 17, wherein the processor is further configured to: outputting a first signal indicating a correction factor list to the UE; and A second signal is outputted for the UE, the second signal including the second indication of the correction factor in the correction factor list.
19. The apparatus of claim 18, wherein the UE comprises a first UE and the correction factor list comprises a first list having a first list size, the processor being further configured to: A third signal is output for a second UE, the third signal indicating a second list of correction factors, the second list of correction factors having a second list size different from the first list size.
20. The apparatus of claim 18, wherein: The first signal comprises a radio resource control signal, a master information block, a system information block, a random access channel signal, or a combination thereof; and The second signal includes a medium access channel element, a downlink control information signal, or both.
21. The apparatus of claim 16, wherein to output the synchronization signal block, the processor is configured to: The synchronization signal block is output based at least in part on a periodicity for the synchronization signal block corresponding to the active network energy state, a skip mode for the synchronization signal block, a first set of synchronization signal block opportunities to be skipped, a second set of synchronization signal block opportunities to be sent, or a combination thereof.
22. The apparatus of claim 16, wherein the processor is further configured to: obtaining UE information for the UE; and The active network energy state, a radio measurement configuration for the network entity, or both are determined based at least in part on the UE information.
23. The apparatus of claim 22, wherein the UE information comprises UE capabilities, UE type, UE mobility information, UE power state, power saving mode, sleep mode, radio resource control state, or a combination thereof.
24. The apparatus of claim 16, wherein the processor is further configured to: obtaining a third indication of a relaxed measurement configuration for the UE; and The active network energy state, a radio measurement configuration for the network entity, or both are determined based at least in part on the relaxed measurement configuration for the UE.
25. The apparatus of claim 16, wherein the processor is further configured to: obtaining a request for a radio resource management slack configuration, a radio resource management slack factor, or both for the network entity; and The active network energy state, a radio measurement configuration for the network entity, or both are determined based at least in part on the request.
26. The apparatus of claim 16, wherein the processor is further configured to: A number of active antennas, a transmit power, or both, is determined for the network entity based at least in part on the active network energy state.
27. The apparatus of claim 16, wherein the processor is further configured to: obtaining, for a second network entity, a second active network energy state, a correction factor for a radio measurement threshold corresponding to the second network entity, or both; and A fourth indication of the second active network energy state, the correction factor, or both for the second network entity is output for the UE, wherein the second network entity comprises a non-serving network entity for the UE.
28. The apparatus of claim 16, wherein the processor is further configured to: The active network energy state, a correction factor for a radio measurement threshold corresponding to the network entity, or both are output for a second network entity.
29. A method for wireless communication at a user equipment (UE), the method comprising: receiving, for a network entity, a first indication of an active network energy state among a plurality of network energy states; receiving a synchronization signal block for the network entity based at least in part on the active network energy state; as well as Communicating is performed based at least in part on one or more measurements associated with the synchronization signal block.
30. A method for wireless communication, the method comprising: outputting, for a user equipment (UE), a first indication of an active network energy state for a network entity among a plurality of network energy states; outputting a synchronization signal block for the network entity based at least in part on the active network energy state; as well as Communicating is performed based at least in part on the synchronization signal blocks.