Measurement configuration for on-demand synchronization signal block and time domain synchronization signal block adjustment

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. The wireless communication system can support measurement configurations for on-demand synchronization signal blocks (SSBs) and time-domain SSB adjustment. The user equipment (UE) of the wireless communication system can receive one or more first control messages from a first network entity associated with the UE's serving cell. These one or more first control messages include a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer. The measurement timing configuration can be associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs. The UE can monitor the first set of multiple SSBs according to the measurement timing configuration.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 618,198, filed March 27, 2024, entitled “MEASUREMENT CONFIGURATION FOR ON-DEMAND SYNCHRONIZATION SIGNAL BLOCK AND TIME-DOMAIN SYNCHRONIZATION SIGNAL BLOCK ADAPTATION”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following content relates to wireless communication, including measurement configurations for on-demand synchronization signal blocks (SSBs) and time-domain SSB adjustment. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can 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, LTE-A Advanced (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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0004] Wireless communication devices (such as UEs) can receive synchronization signal blocks (SSBs) to perform beam management, such as beam scanning; measure the coverage level of network entities; measure interference levels; and so on. For example, a UE can periodically receive and measure SSBs and determine one or more characteristics of the channel based on the measurements of the SSBs. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting measurement configurations for on-demand synchronization signal blocks (SSBs) and time-domain SSB adjustment. For example, the described technology provides receiving a control message at a user equipment (UE) that configures the UE with a measurement timing configuration. The measurement timing configuration indicates the set of SSBs to be received by the UE from neighboring cells (such as secondary cells) via a first frequency layer. Furthermore, the measurement timing configuration may be associated with the neighboring cells' ability to dynamically time-adjust SSBs. For example, the neighboring cells may support on-demand or time-adjusted SSBs. The UE can monitor the SSB set according to the measurement timing configuration.

[0006] A method for wireless communication by a UE is described. The method may include: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; and monitoring the first set of multiple SSBs according to the measurement timing configuration.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code to cause the UE to: receive one or more first control messages from a first network entity associated with the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; and monitor the first set of multiple SSBs according to the measurement timing configuration.

[0008] Another UE for wireless communication is described. The UE may include: components for receiving one or more first control messages from a first network entity associated with the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; and components for monitoring the first set of multiple SSBs according to the measurement timing configuration.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive one or more first control messages from a first network entity associated with a serving cell of a UE, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; and monitor the first set of multiple SSBs according to the measurement timing configuration.

[0010] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving one or more second control messages that are dynamically timed to activate or deactivate a measurement timing configuration based on a first set of multiple SSBs, wherein monitoring of the first set of multiple SSBs may be performed based on the activation or deactivation of the measurement timing configuration.

[0011] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, the one or more second control messages include Media Access Control (MAC)-Control Element (CE) messages or Downlink Control Information (DCI) messages.

[0012] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for disabling measurement timing configurations based on the deactivation of a timer at the UE or based on the expiration of a threshold duration.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more first control messages may further include a second measurement timing configuration that indicates a second set of a plurality of SSBs to be received by the UE via a first frequency layer.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second measurement timing configuration relates to a non-dynamically time-adjusted SSB, and the second set of multiple SSBs can be a non-dynamically time-adjusted SSB.

[0015] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving a first SSB in a first set of a plurality of SSBs according to a first power level, a first beamwidth, or both; and receiving a second SSB in a second set of a plurality of SSBs according to a second power level, a second beamwidth, or both.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the first SSB type including dynamically time-adjusted SSBs and the second SSB type including non-dynamically time-adjusted SSBs.

[0017] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving one or more second control messages that modify the period of a first periodicity associated with a first SSB type, wherein the one or more second control messages include MAC-CE messages or DCI messages.

[0018] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing a measurement procedure on a first set of multiple SSBs based on the measurement state of the UE, wherein the measurement procedure includes one of the following: measuring the first set of multiple SSBs or avoiding measuring the first set of multiple SSBs.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the methods, apparatus, and nontransitory computer-readable media may include additional operations, features, components, or instructions for avoiding the measurement of a first set of multiple SSBs based on the radio resource management (RRM) measurement status at the UE.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the methods, apparatus, and nontransitory computer-readable media may include additional operations, features, components, or instructions for measuring a first set of multiple SSBs based on satisfying a threshold mobility level, satisfying a threshold signal quality, or both.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, monitoring may include operations, features, components, or instructions for monitoring a first set of multiple SSBs from the set of multiple neighboring cells according to a measurement timing configuration that indicates a set of multiple neighboring cells.

[0022] A method for wireless communication by a network entity is described. The method may include: sending one or more first control messages to a UE via a serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration; and sending one or more second control messages associated with the UE's mobility management based on the measurement report.

[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code to cause the network entity to: transmit one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; receive a measurement report from the UE indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration; and transmit one or more second control messages to the UE related to the UE's mobility management based on the measurement report.

[0024] Another network entity for wireless communication is described. This network entity may include: components for: transmitting one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; components for: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration; and components for: transmitting one or more second control messages associated with the UE's mobility management based on the measurement report.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs; receive a measurement report from the UE indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration; and send one or more second control messages to the UE related to the UE's mobility management based on the measurement report.

[0026] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of activation or deactivation of a dynamically time-adjusted SSB from a second network entity in a neighboring cell via a backhaul link; and sending one or more third control messages to the UE, the one or more third control messages activating or deactivating the measurement timing configuration based on the indication of activation or deactivation from the second network entity.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more third control messages include MAC-CE messages or DCI messages.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more first control messages may further include a second measurement timing configuration that indicates a second set of a plurality of SSBs to be received by the UE via a first frequency layer.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second measurement timing configuration relates to a non-dynamically time-adjusted SSB, and the second set of multiple SSBs can be a non-dynamically time-adjusted SSB.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the second SSB type including dynamically time-adjusted SSBs.

[0031] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending one or more third control messages that modify the period of a first periodicity associated with a first SSB type, wherein the one or more third control messages include MAC-CE messages or DCI messages. Attached Figure Description

[0032] Figure 1 and Figure 2 An example of a wireless communication system is shown that supports a measurement configuration for on-demand synchronization signal blocks (SSBs) and time-domain SSB adjustment, according to one or more aspects of this disclosure.

[0033] Figure 3 An example of a timing diagram showing a measurement configuration supporting on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown.

[0034] Figure 4 An example of a process flow for a measurement configuration supporting on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0035] Figure 5 and Figure 6 A block diagram of a device for a measurement configuration supporting on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0036] Figure 7 A block diagram of a communication manager supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0037] Figure 8 A diagram of a system including a device supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0038] Figure 9 and Figure 10 A block diagram of a device for a measurement configuration supporting on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0039] Figure 11 A block diagram of a communication manager supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0040] Figure 12 A diagram of a system including a device supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown.

[0041] Figures 13 to 16 A flowchart illustrating a method for supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown. Detailed Implementation

[0042] Wireless communication systems can support synchronization signal block (SSB)-based measurements based on measurement timing configurations. For example, a network entity can instruct a user equipment (UE) on a measurement timing configuration (e.g., a synchronization signal (SS) or physical broadcast channel (PBCH) block measurement timing configuration (SMTC)) that indicates periodicity, timing offset, or both associated with the SSB-based measurement. In some cases, the measurement timing configuration can be associated with the UE's secondary cell, where the network entity belongs to the UE's serving cell. For example, a network entity can instruct a measurement timing configuration associated with SSB-based radio resource management (RRM).

[0043] In some cases, wireless communication systems may also support SSB adjustment. For example, network entities may adjust SSBs in the time domain (e.g., adjust periodicity), such as activating or deactivating SSBs on a periodic basis via System Information Block (SIB) indication (e.g., SIB1). UEs may receive and decode SIBs (e.g., periodically), where some SIBs can activate or deactivate SSBs. However, the periodicity associated with an SIB may not support a threshold level of energy efficiency at the network entity, UE, or both. For example, while the UE waits to decode an SIB, the network entity may activate or deactivate SSBs relatively slowly to achieve network energy savings. Alternatively, network entities may dynamically activate or deactivate (e.g., add or remove) SSBs. For example, wireless communication systems may support on-demand SSB operation, SSB adjustment in the time domain, or both. In some examples, dynamic adjustment of SSBs may be associated with a higher level of energy efficiency compared to SSB adjustment via SIBs. That is, the UE can receive information associated with SSB adjustment based on whether the SSB is to be activated or deactivated, rather than periodically, which can support network energy savings (NES). For example, dynamic SSB adjustment allows one or more devices in a wireless communication system to enter sleep mode more quickly compared to adjustment via SIB indication. However, measurement timing configuration may not support dynamic SSB adjustment.

[0044] Measurement timing configurations can be adjusted as described herein to support dynamic activation or deactivation based on on-demand SSBs, time-domain adjustments of SSBs, or both. Additionally, SSB-based RRM can be adjusted based on on-demand SSBs, time-domain adjustments of SSBs, or both. The adjusted measurement timing configurations enable network entities to activate or deactivate the measurement timing configuration based on whether on-demand SSBs or time-adjusted SSBs are enabled or disabled in neighboring cells (including the UE's secondary cell). To support measurement configurations for on-demand SSBs and time-domain SSB adjustments, network entities can send control messages to the UE configuring the UE with measurement timing configurations associated with SSBs to be received by the UE via neighboring cells (e.g., secondary cells). For example, network entities can instruct the UE on measurement timing configurations based on SSBs that include on-demand SSBs or time-adjusted SSBs. That is, neighboring cells can activate on-demand SSBs as a supplement to or alternative to always-on SSBs (e.g., non-time-adjusted SSBs). In some examples, network entities may indicate to the UE the activation or deactivation of on-demand SSBs or time-adjusted SSBs via dynamic indications such as Media Access Control (MAC)-Control Element (CE) or Downlink Control Information (DCI) messages. For example, a network entity may obtain on-demand or time-adjusted SSB activation or deactivation information from a second network entity in a neighboring cell via a backhaul link and indicate this activation or deactivation information to the UE. After receiving the measurement timing configuration, and in some examples, after receiving the activation or deactivation information, the UE may monitor the SSB according to the measurement timing configuration.

[0045] The various aspects of this disclosure are first described in the context of a wireless communication system. They are also described in the context of timing diagrams and process flows. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to measurement configurations for on-demand SSB and time-domain SSB adjustment.

[0046] Figure 1 An example of a wireless communication system 100 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 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 under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0047] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0048] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are shown below. Figure 1 As shown, the UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including the UE 115 or network entity 105).

[0049] As described herein, a node in 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0050] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0051] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0052] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and 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, network entity 105 may include one or more of the following: a Central Unit (CU) (such as CU 160), a Distributed Unit (DU) (such as DU 165), a Radio Unit (RU) (such as RU 170), a RAN Intelligent Controller (RIC) (such as 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) system (such as SMO system 180), or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0053] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to 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)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, MAC layer) functionality and signaling, and can each be at least partially controlled by CU 160. Alternatively or additionally, a functional split of the protocol stack can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0054] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support 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., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0055] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB nodes, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0056] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in a variety of objects such as appliances, vehicles, or meters.

[0057] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0058] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0059] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0060] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0061] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0062] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where 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 decoding 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 modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal 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.

[0063] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0064] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0065] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be 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 to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0066] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0067] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can 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 set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0068] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0069] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and can allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. Small cells may be associated with network entities 105 that operate at lower power relative to macro cells (e.g., base station 140 operating at lower power), and small cells may operate using the same or different (e.g., licensed or unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or may provide restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0070] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0071] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0072] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0073] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as 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 may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 sends to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0074] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can 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), 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), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0075] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0076] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0077] Network entity 105 (e.g., base station 140, RU 170) or 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) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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 network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0078] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., for the antenna array of the transmitting or receiving device or for some other orientation).

[0079] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0080] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0081] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0082] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0083] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0084] As described herein, network entity 105 may send a control message to UE 115 configuring UE 115 with a measurement timing configuration associated with an SSB to be received by UE 115 from a neighboring cell, such as from another network entity 105 associated with the neighboring cell. For example, network entity 105 may indicate the measurement timing configuration to UE 115 based on an SSB that includes an on-demand SSB or a time-adjusted SSB. In some examples, network entity 105 may indicate the activation or deactivation of an on-demand SSB or a time-adjusted SSB to UE 115 via dynamic indication. For example, network entity 105 may obtain on-demand SSB or time-adjusted SSB activation or deactivation information from another network entity 105 in a neighboring cell via a backhaul link (which may be an example of communication link 125) and indicate such activation or deactivation information to UE 115. After receiving the measurement timing configuration, and in some examples, after receiving the activation or deactivation information, UE 115 may monitor the SSB according to the measurement timing configuration.

[0085] Figure 2 An example of a wireless communication system 200 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, various aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a, network entity 105-b, coverage area 110, UE 115, and communication link 125, which may be as referenced... Figure 1 Examples of the corresponding devices described.

[0086] Wireless communication system 200 can support on-demand SSB secondary cell operation for UEs in connected mode, these UEs being configured with carrier aggregation, such as in-band or inter-band carrier aggregation. For example, wireless communication system 200 may include a first cell supported by network entity 105-a having a coverage area 110, wherein the first cell is the serving cell of UE 115. Additionally, wireless communication system 200 may include a second cell supported by network entity 105-b, wherein the second cell is a secondary cell of UE 115. The second cell may be a neighboring cell of the first cell. Although references... Figure 2 A neighboring cell has been illustrated and described; however, it should be understood that more than one cell may be adjacent to the serving cell of UE 115. For example, receiving on-demand SSB from a secondary cell at UE 115 may occur for more than one secondary cell of UE 115. Furthermore, signaling between network entity 105-a and network entity 105-b, as illustrated and described, may occur between network entity 105-a and additional or different network entities in different neighboring cells of the first cell.

[0087] Network entity 105-a may configure UE 115 with multiple measurement timing configurations associated with a corresponding frequency layer (e.g., the NR frequency layer). A measurement timing configuration may refer to an SMTC (e.g., SMTC1 or SMTC2) within a measurement configuration (e.g., MeasObjectNR). In other words, a measurement configuration may include one or more measurement timing configurations. In some examples, network entity 105-a may configure UE 115 with multiple measurement configurations, multiple measurement timing configurations, or both associated with multiple frequency layers. That is, network entity 105-a may send a control message to UE 115 indicating a measurement timing configuration 205 (e.g., a first measurement timing configuration) associated with a first frequency layer, a second measurement timing configuration associated with a second frequency layer, etc. Alternatively or additionally, network entity 105-a may send a control message indicating a first measurement configuration (e.g., a first MeasObjectNR) associated with a first frequency layer, a second measurement configuration (e.g., a second MeasObjectNR) associated with a second frequency layer, etc. For example, network entity 105-a may indicate a list of measurement configurations for the corresponding frequency layer associated with on-demand SSB transmissions from neighboring cells, such as from network entity 105-b.

[0088] In some examples, measurement timing configuration 205 may include multiple periodicities associated with different SSB types, such as always-on SSB or on-demand SSB. For example, measurement timing configuration 205 may include a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type. In such examples, the offsets associated with the first SSB type and the second SSB type may be the same.

[0089] Alternatively, network entity 105-a may indicate multiple measurement timing configurations associated with different SSB types (such as always-on SSB or on-demand SSB). For example, measurement timing configuration 205 may be associated with a first SSB type, while a second measurement timing configuration may be associated with a second SSB type. In such examples, the offsets associated with the first and second SSB types may be the same or different.

[0090] The first and second SSB types can be found elsewhere in this article (including references). Figure 3 (For more details) On-demand SSB transmission can support secondary cell time and frequency synchronization, L1 and L3 measurements, and secondary cell activation, and in some examples, it can be used for one or more frequency ranges in the non-shared spectrum (e.g., FR1 and FR2).

[0091] Network entity 105-a may include indications for multiple cells in measurement timing configuration 205, such as indications for multiple PCIDs (e.g., PCI list configuration). For example, the multiple cells in measurement timing configuration 205 may be associated with the capability for time-adjusted SSBs (e.g., on-demand SSBs). UE 115 may determine one or more SSBs sent from one of the indicated cells as on-demand SSBs, and one or more SSBs sent from another cell not indicated among the multiple cells as always-on SSBs. In other words, UE 115 may assume that the cells in the indications for multiple cells can send on-demand SSBs, and / or perform measurements for always-on SSBs for cells not included in the indications for multiple cells.

[0092] Network entity 105-a can activate or deactivate measurement timing configuration 205 at UE 115. For example, network entity 105-a can send a control message to activate or deactivate the measurement timing configuration, such as activation or deactivation message 210. Activation or deactivation message 210 can be a dynamic indication, such as a MAC-CE or DCI message via L1 or L2 signaling. Dynamic indications via L1 or L2 signaling can be more efficient than one or more other signaling types, such as reconfiguration via RRC. In some examples, network entity 105-a can send activation or deactivation message 210 based on the status sent by the SSB from a neighboring cell. For example, network entity 105-a can deactivate the measurement timing configuration at UE 115 based on a deactivation from the SSB of a neighboring cell to save energy at UE 115 (e.g., by avoiding unnecessary measurements, remaining in a wake-up state, etc.).

[0093] For example, network entity 105-a may receive activation or deactivation message 210 from network entity 105-b via communication link 125 (which may be a backhaul communication link). That is, network entity 105-b may share (e.g., indicate) with network entity 105-a whether network entity 105-b should send an on-demand SSB to UE 115. In some examples, network entity 105-b may send an on-demand SSB based on triggering conditions. For example, triggering conditions may include a wake-up signal from UE 115, a cell activation or deactivation (e.g., on / off) indication via a backhaul link, secondary cell activation or deactivation signaling, etc. Network entity 105-a may send activation or deactivation message 210 to UE 115 based on network entity 105-b's indication of on-demand SSB transmission (e.g., or deactivation of on-demand SSB transmission).

[0094] UE 115 may monitor SSBs based on measurement timing configuration 205, activation or deactivation message 210, or both. For example, UE 115 may monitor SSBs during one or more monitoring periods based on the periodicity of SSBs indicated by measurement timing configuration 205. Alternatively, UE 115 may monitor SSBs by being activated via activation or deactivation message 210 based on measurement timing configuration 205. Or, UE 115 may be deactivated via activation or deactivation message 210 based on measurement timing configuration 205 to avoid monitoring SSBs.

[0095] In some examples, UE 115 may check for the presence of on-demand SSB transmission during the timing of measurement timing configuration 205 (e.g., detect on-demand SSB transmission). For example, UE 115 may detect the on-demand SSB before performing the measurement procedure. That is, UE 115 may perform the measurement procedure for the on-demand SSB based on the detection of the on-demand SSB. This can be seen elsewhere in this document (including references). Figure 3 (A more detailed description of the detection of on-demand SSBs)

[0096] UE 115 can receive SSBs from network entity 105-b via one or more beams (such as the first beam 215-a, the second beam 215-b, and the third beam 215-c). For example, each beam can be associated with a different SSB type (such as always-on SSB or on-demand SSB). See elsewhere in this document (including references) Figure 3 (A more detailed description of the transmission of SSB via different beams.)

[0097] UE 115 can measure SSBs received from network entity 105-b. For example, UE 115 can perform a measurement procedure for on-demand SSBs from network entity 105-b (e.g., from a secondary cell) based on conditions at UE 115. As an example, UE 115 can avoid measuring on-demand SSBs from network entity 105-b based on being in a normal or relaxed RRM measurement state. In another example, UE 115 can measure on-demand SSBs from network entity 105-b based on being in a high mobility or poor signal quality state. In some examples, UE 115 can independently determine a high mobility or poor signal quality state (e.g., in the absence of signaling from either network entity 105-a or network entity 105-b) based on parameters indicated by network entity 105-a, or based on whether network entity 105-a enables or disables RRM measurement using on-demand SSBs.

[0098] In some examples, as part of the measurement process, UE 115 can compensate for power offset when filtering reference signal received power (RSRP) or signal-to-interference-noise ratio (SINR) measurements from always-on SSBs and on-demand SSBs. For example, network entity 105-a can be configured to configure the power offset between always-on SSBs and on-demand SSBs. In other words, UE 115 can perform the measurement process based on the power offset between a first SSB type (e.g., always-on SSB) and a second SSB type (e.g., on-demand SSB).

[0099] UE 115 may send a measurement report 220 to network entity 105 based on a measurement of the SSB received from network entity 105-b. For example, network entity 105-a may receive measurement report 220 from UE 115, which indicates one or more measurements based on the SSB received at UE 115 and measurement timing configuration 205. In response to receiving measurement report 220, network entity 105-a may send a mobility management message 225 to UE 115 based on the measurement report.

[0100] Figure 3 An example of a timing diagram 300 supporting a measurement configuration for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown. Timing diagram 300 may implement, or be implemented by, various aspects of wireless communication system 100, wireless communication system 200, or both. For example, timing diagram 300 may include a first cell 305-a, a second cell 305-b, and a third cell 305-c, which may be examples of secondary cells of the UE, such as reference cells. Figure 2The network entity 105-b of the secondary cell is described. Additionally, the timing diagram may include multiple SSBs associated with the first beam 315-a, the second beam 315-b, the third beam 315-c, or the fourth beam 315-d, and these beams may be as shown in the reference... Figure 2 Examples of the first beam 215-a, the second beam 215-b, or the third beam 215-c described.

[0101] UE's secondary cell (such as including, as referenced) Figure 2 The secondary cell of network entity 105-b described herein can send various types of SSBs to the UE. For example, the secondary cell can send legacy SSBs, sparse always-on SSBs, or on-demand SSBs to the UE. In some examples, the secondary cell can adjust one or more of these types of SSBs in the time domain. That is, the secondary cell can adjust the periodicity of one or more of these types of SSBs.

[0102] Legacy SSB transmission can refer to an SSB with a first periodicity (such as a periodicity of 20ms). A secondary cell can transmit legacy SSBs in its first periodicity regardless of whether the secondary cell is activated or deactivated. For example, while one or more other types of SSBs may be deactivated based on the deactivation of the secondary cell, the secondary cell can still transmit legacy SSBs. In some examples, a secondary cell may transmit legacy SSBs to UEs (e.g., legacy UEs) that do not have the ability to receive dynamically time-adjusted SSBs (e.g., on-demand SSBs).

[0103] A sparse always-on SSB can refer to an SSB with a second periodicity (such as a periodicity greater than 20 ms). The secondary cell can transmit a sparse always-on SSB periodically regardless of whether the secondary cell is activated or deactivated. For example, although one or more other types of SSBs can be deactivated based on the deactivation of the secondary cell, the secondary cell can still transmit a sparse always-on SSB. An always-on SSB can refer to a legacy SSB or a sparse always-on SSB. In some examples, the secondary cell can transmit a sparse always-on SSB to a UE (e.g., a legacy UE) that does not have the ability to receive dynamically time-adjusted SSBs (e.g., on-demand SSBs).

[0104] On-demand SSBs can refer to SSBs with a third periodicity. A secondary cell can transmit on-demand SSBs in a third periodicity based on the activation or deactivation of the secondary cell. In some examples, a secondary cell can transmit sparsely always-on SSBs to UEs capable of receiving dynamically time-adjusted SSBs (e.g., on-demand SSBs). A secondary cell can transmit on-demand SSBs during activation, after activation, or at both times. In other words, a secondary cell can transmit on-demand SSBs during the transition from deactivation to activation or before the secondary cell is deactivated. In some examples, a secondary cell can transmit on-demand SSBs in a third periodicity during activation and in a fourth periodicity after activation. For example, a secondary cell can transmit on-demand SSBs during activation with the same periodicity as legacy SSBs (e.g., a first periodicity) and after activation with the same periodicity as sparsely always-on SSBs (e.g., a second periodicity). In some other examples, a secondary cell can transmit on-demand SSBs during and after activation with the same periodicity as legacy SSBs (e.g., a first periodicity).

[0105] The secondary cell may send any combination of one or more types of SSBs to the UE. For example, the secondary cell may send on-demand SSBs in combination with sparse always-on SSBs. As an example, the secondary cell may send always-on SSBs in a deactivated state, and send both always-on SSBs and on-demand SSBs during activation, after activation, or both. In some other examples, the secondary cell may send on-demand SSBs alone, such as without sparse always-on SSBs.

[0106] In the timing diagram example, the secondary cell can send SSBs of different SSB types to the UE via different beams. For example, the first cell 305-a can send sparse always-on SSBs to the UE via the first beam 315-a and the second beam 315-b. In another example, the second cell 305-b can send sparse always-on SSBs and on-demand SSBs via the first beam 315-a, the second beam 315-b, the third beam 315-c, and the fourth beam 315-d. The third cell 305-c can send sparse always-on SSBs and on-demand SSBs via the first beam 315-a, the second beam 315-b, and the third beam 315-c.

[0107] For example, a secondary cell may transmit SSBs to the UE via one or more beams. As an example, the first cell 305-a may transmit always-on SSBs to the UE via two beams (first beam 315-a and second beam 315-b). Alternatively, the secondary cell may transmit different types of SSBs via different beams. For example, the second cell 305-b may transmit always-on SSBs to the UE via first beam 315-a and second beam 315-b, and transmit on-demand SSBs to the UE via third beam 315-c and fourth beam 315-d. As another example, the third cell 305-c may transmit always-on SSBs to the UE via first beam 315-a and second beam 315-b, and transmit on-demand SSBs to the UE via third beam 315-c.

[0108] In some examples, secondary cells can transmit always-on SSB and on-demand SSB with different transmit powers, different beamwidths, or both. For example, second cell 305-b can transmit always-on SSB with a first transmit power and a first beamwidth via first beam 315-a and second beam 315-b, and transmit on-demand SSB with a second transmit power and a second beamwidth via third beam 315-c and fourth beam 315-d.

[0109] In some examples, on-demand SSB timings may overlap with always-on SSB timings. For instance, during the first timing 310-a, on-demand SSBs from the third beam 315-c and the fourth beam 315-d targeting the second cell 305-b may overlap with always-on SSB transmissions from the first beam 315-a and the second beam 315-b. Additionally, during the first timing, on-demand SSBs from the third beam 315-c targeting the third cell 305-c may overlap with always-on SSB transmissions from the first beam 315-a and the second beam 315-b. The UE receiving the SSB may monitor, receive, or both of these SSBs as always-on SSBs based on the overlap during the first timing 310-a. In other words, on-demand SSB timings that overlap with always-on SSB timings can be considered always-on SSB timings.

[0110] The UE can perform detection for on-demand SSBs. For example, during a second timing 310-b, the UE can check for the presence of an on-demand SSB (e.g., based on measurement timing configuration). In some examples, the UE can also perform detection for an on-demand SSB during a first timing 310-a, in which the on-demand SSB overlaps with always-on SSBs from a second cell 305-b and a third cell 305-c. The UE can avoid performing detection for always-on SSBs. For example, during a first timing 310-a (in which the UE has already detected a previous instance of an always-on SSB from one or more of the first cell 305-a, the second cell 305-b, or the third cell 305-c by the first beam 315-a and the second beam 315-b), the UE can avoid detecting always-on SSBs. The UE can avoid detection based on the determination that always-on SSBs will (e.g., always) be sent (e.g., because always-on SSBs are sent regardless of whether the secondary cell is activated or deactivated). However, for on-demand SSBs, the UE can perform detection to identify whether an on-demand SSB is being sent at that time, because, for example, due to the deactivation of a secondary cell, an on-demand SSB may not be sent. That is, the UE can perform detection before measuring on-demand SSBs to ensure that the measurement is performed when the SSB is sent (e.g., to avoid measuring unsent SSBs).

[0111] Figure 4 An example of a process flow 400 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. In some examples, process flow 400 may implement as described in the reference. Figure 1 or Figure 2 The described aspects of wireless communication system 100 or wireless communication system 200, or aspects implemented by these aspects. For example, process flow 400 may be implemented by network entity 105 and UE 115, which may be respectively as referenced Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described. Process flow 400 may also implement, or be implemented by, aspects of timing diagram 300. The following alternative examples may be implemented, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0112] At point 405, network entity 105 may send a first control message to UE 115. The first control message may include measurement timing configuration, such as reference... Figure 2The measurement timing configuration 205 is described. For example, UE 115 may receive a first control message from a network entity 105 associated with the serving cell of UE 115, the first control message including a measurement timing configuration indicating a first set of multiple SSBs to be received by UE 115 from neighboring cells via a first frequency layer. For example, neighboring cells may be having a coverage area or include network entities (such as references). Figure 1 and Figure 2 The cell described is the coverage area 110 or network entity 105. In some examples, the measurement timing configuration may be associated with the ability of neighboring cells to dynamically time a first set of multiple SSBs. Alternatively or additionally, the measurement timing configuration may be associated with the ability of UE 115 to receive dynamic indications to activate or deactivate the measurement timing configuration.

[0113] The first control message may include a second measurement timing configuration indicating a second set of multiple SSBs to be received by UE 115 via a first frequency layer. In other words, network entity 105 may configure multiple measurement timing configurations (e.g., a list thereof) associated with a frequency layer. In some examples, the second measurement timing configuration may relate to non-dynamically time-adjusted SSBs, and the second set of multiple SSBs may be non-dynamically time-adjusted SSBs. For example, network entity 105 may configure separate measurement timing configurations for sparse always-on SSBs and dense on-demand SSBs. In some examples, the offset associated with always-on SSBs may be the same as or different from that of on-demand SSBs.

[0114] Alternatively, the measurement timing configuration may include a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, wherein the first SSB type includes dynamically time-adjusted SSBs and the second SSB type includes non-dynamically time-adjusted SSBs. In other words, network entity 105 may configure measurement timing configurations with different periodicities for sparse always-on SSBs and dense on-demand SSBs. In some examples, the offset associated with always-on SSBs may be the same as that associated with on-demand SSBs.

[0115] At 410, network entity 105 may receive an indication of activation or deactivation of the measurement timing configuration. For example, network entity 105 may receive an indication of activation or deactivation of the dynamically timed SSB from a second network entity in a neighboring cell via a backhaul link. In some examples, the neighboring cell may indicate an on-demand SSB trigger state and indicate the transmission of on-demand SSBs. That is, network entity 105 may activate the measurement timing configuration when the on-demand SSB trigger state is met or when the neighboring cell indicates the transmission of on-demand SSBs.

[0116] At 415, network entity 105 may send a second control message to UE 115. For example, the second control message may activate or deactivate a measurement timing configuration based on dynamic timing adjustments made to a first set of multiple SSBs. Network entity 105 may send the second control message based on receiving an indication for activation or deactivation from a second network entity at 410. In some examples, the second control message may include a MAC-CE message or a DCI message. In other words, network entity 105 may activate or deactivate the measurement timing configuration via dynamic indications (e.g., L1 or L2 signaling) based on the status of on-demand SSBs transmitted from neighboring cells.

[0117] In some other examples, the second control message may modify the period of the first periodicity associated with the first SSB type, wherein one or more of the second control messages include MAC-CE messages or DCI messages.

[0118] At 420, UE 115 can monitor SSBs. For example, UE 115 can monitor a first set of multiple SSBs according to a measurement timing configuration. Alternatively, UE 115 can monitor a first set of multiple SSBs based on the activation or deactivation of the measurement timing configuration received via a second control message at 415.

[0119] In some examples, UE 115 may monitor a first set of multiple SSBs from a set of neighboring cells according to a measurement timing configuration indicating a set of neighboring cells. That is, a first control message indicating the measurement timing configuration may include an indication of the set of neighboring cells. For example, the first control message may include a PCID list configuration for on-demand SSBs, wherein UE 115 may monitor on-demand SSBs from cells in the PCID list configuration. Alternatively, for cells not included in the PCID list configuration, UE 115 may monitor, measure, or both monitor and measure SSBs always enabled.

[0120] At 425, UE 115 can receive SSBs. For example, UE 115 can receive SSBs from neighboring cells based on measurement timing configuration and monitoring at 420. In some examples, UE 115 can receive a first SSB from a first set of multiple SSBs based on a first power level, a first beamwidth, or both. Alternatively, UE 115 can receive a second SSB from a second set of multiple SSBs based on a second power level, a second beamwidth, or both. As an example, neighboring cells can transmit always-on SSBs and on-demand SSBs with different transmit powers, different beamwidths, or both.

[0121] At 430, UE 115 may perform measurement procedure 430. For example, UE 115 may perform a measurement procedure on a first set of multiple SSBs based on UE 115's measurement state, wherein the measurement procedure includes measuring the first set of multiple SSBs or avoiding measuring the first set of multiple SSBs. For example, UE 115 may avoid measuring the first set of multiple SSBs based on RRM measurement state at UE 115. Alternatively, UE 115 may measure the first set of multiple SSBs based on meeting a threshold mobility level, meeting a threshold signal quality, or both. In other words, UE 115 may not (e.g., may not need to) measure on-demand SSBs when in a normal or relaxed RRM measurement state, but may (e.g., may need to) measure on-demand SSBs when in a high mobility or poor signal quality state.

[0122] In some examples, as part of the measurement process, UE 115 can compensate for power offset when filtering RSRP or SINR measurements from always-on SSBs and on-demand SSBs. For example, network entity 105 can configure the power offset between always-on SSBs and on-demand SSBs. In other words, UE 115 can perform the measurement process based on the power offset between a first SSB type (e.g., on-demand SSB) and a second SSB type (e.g., always-on SSB).

[0123] At 435, UE 115 may send a measurement report to network entity 105. For example, network entity 105 may receive a measurement report from UE 115 indicating one or more measurements based on a first set of multiple SSBs and a measurement timing configuration. In response to receiving the measurement report, at 440, network entity 105 may send a third control message to UE 115. For example, network entity 105 may send a third control message associated with mobility management of UE 115 based on the measurement report.

[0124] At 445, UE 115 can disable the measurement timing configuration 445. For example, UE 115 can disable the measurement timing configuration based on an indication from a second network entity in a neighboring cell to disable the dynamically timed SSB, based on a disable timer at UE 115, or based on the expiration of a threshold duration.

[0125] Figure 5A block diagram 500 illustrates a device 505 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0126] Receiver 510 may provide components 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, and control channels related to measurement configurations for on-demand SSB and time-domain SSB adjustment). The information may be delivered to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0127] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit 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 measurement configurations for on-demand SSB and time-domain SSB adjustment). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0128] The communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be examples of components used to perform various aspects of the measurement configuration for on-demand SSB and time-domain SSB adjustment as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0129] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0130] Alternatively or concurrently, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0131] In some examples, the communication manager 520 may be configured to use a receiver 510, a transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0132] Communication Manager 520 may support wireless communication according to examples disclosed herein. For example, Communication Manager 520 may be capable of, configured to, or operable to support components for: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of the plurality of SSBs. Communication Manager 520 may be capable of, configured to, or operable to support components for: monitoring the first set of the plurality of SSBs according to the measurement timing configuration.

[0133] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0134] Figure 6 A block diagram 600 illustrates a device 605 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] Receiver 610 may provide components 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, and control channels related to measurement configurations for on-demand SSB and time-domain SSB adjustment). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0136] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit 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 measurement configurations for on-demand SSB and time-domain SSB adjustment). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0137] Device 605 or its various components may be examples of parts for performing various aspects of measurement configurations for on-demand SSB and time-domain SSB adjustment as described herein. For example, communication manager 620 may include measurement timing configuration component 625, monitoring component 630, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0138] Communication manager 620 may support wireless communication according to examples disclosed herein. Measurement timing configuration component 625 is capable of, configured to, or operable to support components for receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of the plurality of SSBs. Monitoring component 630 is capable of, configured to, or operable to support components for monitoring the first set of the plurality of SSBs according to the measurement timing configuration.

[0139] Figure 7A block diagram 700 illustrates a communication manager 720 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of measurement configurations for on-demand SSB and time-domain SSB adjustment as described herein. For example, the communication manager 720 may include a measurement timing configuration component 725, a monitoring component 730, an activation component 735, a measurement process component 740, an SSB component 745, a periodicity component 750, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0140] The communication manager 720 may support wireless communication according to examples disclosed herein. The measurement timing configuration component 725 is capable of, configured to, or operable to support components for receiving one or more first control messages from a first network entity associated with the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of the plurality of SSBs. The monitoring component 730 is capable of, configured to, or operable to support components for monitoring the first set of the plurality of SSBs according to the measurement timing configuration.

[0141] In some examples, the activation component 735 is capable of, configured to, or able to operate to support components for: receiving one or more second control messages that are dynamically time-adjusted based on a first set of multiple SSBs to activate or deactivate a measurement timing configuration, wherein monitoring of the first set of multiple SSBs is performed based on the activation or deactivation of the measurement timing configuration.

[0142] In some examples, the one or more second control messages include MAC-CE messages or DCI messages.

[0143] In some examples, the activation component 735 is capable of, can be configured to, or can operate to support components for: disabling the dynamically time-adjusted SSB based on a second network entity from a neighboring cell, disabling a deactivation timer at the UE, or disabling a measurement timing configuration based on the expiration of a threshold duration.

[0144] In some examples, the one or more first control messages also include a second measurement timing configuration that indicates a second set of multiple SSBs to be received by the UE via a first frequency layer.

[0145] In some examples, the second measurement timing configuration is related to a non-dynamically time-adjusted SSB. In some examples, the second set of multiple SSBs is a non-dynamically time-adjusted SSB.

[0146] In some examples, SSB component 745 is capable of, configured to, or operable to support components for receiving a first SSB from a first set of a plurality of SSBs based on a first power level, a first beamwidth, or both. In some examples, SSB component 745 is capable of, configured to, or operable to support components for receiving a second SSB from a second set of a plurality of SSBs based on a second power level, a second beamwidth, or both.

[0147] In some examples, the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the first SSB type including dynamically time-adjusted SSBs and the second SSB type including non-dynamically time-adjusted SSBs.

[0148] In some examples, the periodic component 750 is capable of, configured to, or operable to support components for receiving one or more second control messages that modify the period of a first periodicity associated with a first SSB type, wherein the one or more second control messages include MAC-CE messages or DCI messages.

[0149] In some examples, the measurement process component 740 is capable of, configured to, or able to operate to support components for performing a measurement process on a first set of multiple SSBs based on the measurement state of the UE, wherein the measurement process includes one of the following: measuring the first set of multiple SSBs or avoiding measuring the first set of multiple SSBs.

[0150] In some examples, in order to support the measurement process for a first set of multiple SSBs, the measurement process component 740 is capable of, can be configured to, or is operable to support components for avoiding the measurement of the first set of multiple SSBs based on the RRM measurement status at the UE.

[0151] In some examples, in order to support a measurement process for a first set of multiple SSBs, the measurement process component 740 is capable of, configured to, or operable to support components for measuring a first set of multiple SSBs based on a threshold mobility level, a threshold signal quality, or both.

[0152] In some examples, to support monitoring, monitoring component 730 is capable of, configured to, or able to operate to support components for monitoring a first set of multiple SSBs from multiple neighboring cells according to a measurement timing configuration indicating a set of multiple neighboring cells.

[0153] Figure 8 A diagram of a system 800 including device 805 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller (e.g., I / O controller 810), a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0154] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0155] In some cases, device 805 may include a single antenna. However, in other cases, device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825 as described herein using a wired or wireless link. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0156] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable code, computer-executable code, or processor-executable code, such as code 835. Code 835 may include instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 830 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0157] At least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting measurement configurations for on-demand SSB and time-domain SSB adjustment). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, the at least one processor 840 and the at least one memory 830 being configured to perform the various functions described herein.

[0158] In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 835 (e.g., processor-executable code) stored in at least one memory 830 or otherwise.

[0159] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of the plurality of SSBs. The communication manager 820 may be capable of, configured to, or operable to support components for: monitoring the first set of the plurality of SSBs according to the measurement timing configuration.

[0160] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0161] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of the measurement configuration for on-demand SSB and time-domain SSB adjustment as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0162] Figure 9 A block diagram 900 illustrates a device 905 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0163] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0164] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 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, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Alternatively or additionally, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0165] The communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be examples of components used to perform various aspects of the measurement configuration for on-demand SSB and time-domain SSB adjustment as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0166] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0167] Alternatively or concurrently, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0168] In some examples, the communication manager 920 may be configured to use a receiver 910, a transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0169] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for: sending one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of the plurality of SSBs. The communication manager 920 may be capable of, configured to, or operable to support components for: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of the plurality of SSBs and the measurement timing configuration. The communication manager 920 may be capable of, configured to, or operable to support components for: sending one or more second control messages to the UE associated with the UE's mobility management based on the measurement report.

[0170] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0171] Figure 10 A block diagram 1000 of a device 1005 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, communication manager 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0172] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0173] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, 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, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Alternatively or concurrently, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may co-located in a transceiver, which may include or be coupled to a modem.

[0174] Device 1005 or its various components may be examples of parts used to perform various aspects of measurement configurations for on-demand SSB and time-domain SSB adjustments as described herein. For example, communication manager 1020 may include measurement timing configuration manager 1025, measurement reporting manager 1030, mobility management manager 1035, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0175] Communication Manager 1020 can support wireless communication according to examples disclosed herein. Measurement Timing Configuration Manager 1025 is capable of, configured to, or operable to support components for: sending one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs. Measurement Report Manager 1030 is capable of, configured to, or operable to support components for: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration. Mobility Management Manager 1035 is capable of, configured to, or operable to support components for: sending one or more second control messages associated with the UE's mobility management based on the measurement report.

[0176] Figure 11 A block diagram 1100 illustrates a communication manager 1120 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment according to one or more aspects of this disclosure. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of measurement configurations for on-demand SSB and time-domain SSB adjustment as described herein. For example, the communication manager 1120 may include a measurement timing configuration manager 1125, a measurement reporting manager 1130, a mobility management manager 1135, an activation manager 1140, a periodicity manager 1145, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0177] Communication Manager 1120 may support wireless communication according to examples disclosed herein. Measurement Timing Configuration Manager 1125 is capable of, configured to, or operable to support components for: sending one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs. Measurement Report Manager 1130 is capable of, configured to, or operable to support components for: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration. Mobility Management Manager 1135 is capable of, configured to, or operable to support components for: sending one or more second control messages associated with the UE's mobility management based on the measurement report.

[0178] In some examples, the activation manager 1140 is capable of, configured to, or operable to support components for receiving, via a backhaul link, an indication of activation or deactivation of a dynamically time-adjusted SSB from a second network entity in a neighboring cell. In some examples, the activation manager 1140 is capable of, configured to, or operable to support components for sending one or more third control messages to the UE, which activate or deactivate a measurement timing configuration based on an indication of activation or deactivation from the second network entity.

[0179] In some examples, the one or more third control messages include MAC-CE messages or DCI messages.

[0180] In some examples, the one or more first control messages also include a second measurement timing configuration that indicates a second set of multiple SSBs to be received by the UE via a first frequency layer.

[0181] In some examples, the second measurement timing configuration is related to a non-dynamically time-adjusted SSB. In some examples, the second set of multiple SSBs is a non-dynamically time-adjusted SSB.

[0182] In some examples, the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the second SSB type including a dynamically time-adjusted SSB.

[0183] In some examples, the periodicity manager 1145 is capable of, configured to, or able to operate to support components for sending one or more third control messages that modify the period of a first periodicity associated with a first SSB type, wherein the one or more third control messages include MAC-CE messages or DCI messages.

[0184] Figure 12 A diagram of a system 1200 including device 1205 supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0185] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1215, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components, or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to perform the following operations: perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination of these two operations. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both), may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0186] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1230. Code 1230 may include instructions that, when executed by one or more processors of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by a processor of at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0187] At least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting measurement configurations for on-demand SSB and time-domain SSB adjustment). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more processors in at least processor 1235, the at least one processor 1235 and the at least one memory 1225 being configured to perform the various functions described herein. At least one processor 1235 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 can host functions (e.g., by executing code 1230) to perform the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories in at least one memory 1225).

[0188] In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, capable of being configured, or operable to cause device 1205 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

[0189] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).

[0190] In some examples, the communication manager 1220 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1220 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., cooperating with one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1220 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0191] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be, configured to, or operable to support components for: transmitting one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of multiple SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first set of multiple SSBs. The communication manager 1220 may be, configured to, or operable to support components for: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on the first set of multiple SSBs and the measurement timing configuration. The communication manager 1220 may be, configured to, or operable to support components for: transmitting one or more second control messages to the UE associated with the UE's mobility management based on the measurement report.

[0192] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for reducing power consumption and utilizing communication resources more efficiently.

[0193] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or in cooperation with transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors of at least one processor 1235 to cause device 1205 to perform various aspects of the measurement configuration for on-demand SSB and time-domain SSB adjustment as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0194] Figure 13A flowchart illustrating a method 1300 for supporting measurement configuration for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0195] At 1305, the method may include: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from a neighboring cell via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cell's ability to dynamically time the first set of the plurality of SSBs. Operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 7 The described measurement timing configuration component 725 is executed.

[0196] At 1310, the method may include: monitoring a first set of multiple SSBs according to a measurement timing configuration. The operation of 1310 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The monitoring component 730 described is executed.

[0197] Figure 14 A flowchart illustrating a method 1400 for supporting measurement configuration for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0198] At 1405, the method may include: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from a neighboring cell via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cell's ability to dynamically time the first set of the plurality of SSBs. Operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 7 The described measurement timing configuration component 725 is executed.

[0199] At 1410, the method may include: receiving one or more second control messages, the one or more second control messages activating or deactivating a measurement timing configuration based on a first set of multiple SSBs dynamically timed, wherein monitoring of the first set of multiple SSBs is performed according to the activation or deactivation of the measurement timing configuration. Operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to [reference]. Figure 7 The described activation component 735 is executed.

[0200] At 1415, the method may include: monitoring a first set of multiple SSBs according to a measurement timing configuration. The operation of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 7 The monitoring component 730 described is executed.

[0201] Figure 15 A flowchart illustrating a method 1500 for supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0202] At 1505, the method may include: sending one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from a neighboring cell via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cell's ability to dynamically time the first set of the plurality of SSBs. Operation of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 11 The described measurement timing configuration manager 1125 is executed.

[0203] At 1510, the method may include: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on a first set of multiple SSBs and a measurement timing configuration. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 11 The described measurement report manager 1130 is executed.

[0204] At point 1515, the method may include: sending one or more second control messages associated with the mobility management of the UE to the UE based on a measurement report. The operation of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to... Figure 11 The described mobility management manager 1135 is executed.

[0205] Figure 16 A flowchart illustrating a method 1600 for supporting measurement configurations for on-demand SSB and time-domain SSB adjustment, according to one or more aspects of this disclosure, is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0206] At 1605, the method may include: sending one or more first control messages to the UE via the UE's serving cell, the one or more first control messages including a measurement timing configuration indicating a first set of a plurality of SSBs to be received by the UE from a neighboring cell via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cell's ability to dynamically time the first set of the plurality of SSBs. Operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1605 may be provided by reference to [reference needed]. Figure 11 The described measurement timing configuration manager 1125 is executed.

[0207] At 1610, the method may include: receiving an indication of activation or deactivation of a dynamically time-adjusted SSB from a second network entity of a neighboring cell via a backhaul link. Operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference needed]. Figure 11 The described activation manager 1140 is executed.

[0208] At 1615, the method may include: sending one or more third control messages to the UE, the one or more third control messages activating or deactivating a measurement timing configuration based on an indication for activation or deactivation from a second network entity. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference needed]. Figure 11 The described activation manager 1140 is executed.

[0209] At 1620, the method may include: receiving a measurement report from the UE, the measurement report indicating one or more measurements based on a first set of multiple SSBs and a measurement timing configuration. Operation of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1620 may be provided by reference to... Figure 11 The described measurement report manager 1130 is executed.

[0210] At 1625, the method may include: sending one or more second control messages associated with the mobility management of the UE to the UE based on a measurement report. The operation of 1625 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1625 may be provided by reference to [reference needed]. Figure 11 The described mobility management manager 1135 is executed.

[0211] The following provides an overview of the various aspects of this disclosure:

[0212] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving one or more first control messages from a first network entity associated with a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first plurality of SSBs to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the ability of the neighboring cells to dynamically time the first plurality of SSBs; and monitoring the first plurality of SSBs according to the measurement timing configuration.

[0213] Aspect 2: According to the method of aspect 1, the method further includes: receiving one or more second control messages, the one or more second control messages activating or deactivating the measurement timing configuration based at least in part on the first plurality of SSBs being dynamically timed, wherein monitoring of the first plurality of SSBs is performed based on the activation or deactivation of the measurement timing configuration.

[0214] Aspect 3: According to the method of aspect 2, the one or more second control messages include MAC-CE messages or DCI messages.

[0215] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: deactivating the measurement timing configuration at least in part based on a deactivation timer at the UE or based on the expiration of a threshold duration.

[0216] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the one or more first control messages further include a second measurement timing configuration, the second measurement timing configuration indicating a second plurality of SSBs to be received by the UE via the first frequency layer.

[0217] Aspect 6: According to the method of aspect 5, wherein the second measurement timing configuration is related to a non-dynamically time-adjusted SSB, and the second plurality of SSBs is the non-dynamically time-adjusted SSB.

[0218] Aspect 7: The method according to any one of Aspects 5 to 6, the method further comprising: receiving a first SSB among the first plurality of SSBs according to a first power level, a first beamwidth, or both; and receiving a second SSB among the second plurality of SSBs according to a second power level, a second beamwidth, or both.

[0219] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the first SSB type including dynamically time-adjusted SSBs and the second SSB type including non-dynamically time-adjusted SSBs.

[0220] Aspect 9: According to the method of aspect 8, the method further includes: receiving one or more second control messages, the one or more second control messages modifying the period of the first periodicity associated with the first SSB type, wherein the one or more second control messages include MAC-CE messages or DCI messages.

[0221] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: performing a measurement process on the first plurality of SSBs at least in part based on the measurement state of the UE, wherein the measurement process includes one of: measuring the first plurality of SSBs or avoiding measuring the first plurality of SSBs.

[0222] Aspect 11: The method according to aspect 10, wherein the measurement process includes avoiding measurement of the first plurality of SSBs, the method comprising: avoiding measurement of the first plurality of SSBs at least in part based on the RRM measurement state at the UE.

[0223] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the measurement process includes measuring the first plurality of SSBs, the method comprising: measuring the first plurality of SSBs at least in part based on satisfying a threshold mobility level, satisfying a threshold signal quality, or both.

[0224] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the measurement timing configuration further indicates a plurality of neighboring cells including at least a first neighboring cell, wherein the monitoring includes: monitoring the first plurality of SSBs from the plurality of neighboring cells according to the measurement timing configuration indicating the plurality of neighboring cells.

[0225] Aspect 14: A method for wireless communication at a network entity, the method comprising: sending one or more first control messages to the UE via a serving cell of the UE, the one or more first control messages including a measurement timing configuration indicating a first plurality of SSBs to be received by the UE from a neighboring cell via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cell’s ability to dynamically time the first plurality of SSBs; receiving a measurement report from the UE, the measurement report indicating one or more measurements at least in part based on the first plurality of SSBs and the measurement timing configuration; and sending one or more second control messages associated with mobility management of the UE at least in part based on the measurement report.

[0226] Aspect 15: The method according to aspect 14, the method further comprising: receiving an indication for activation or deactivation of a dynamically time-adjusted SSB from a second network entity of the neighboring cell via a backhaul link; and sending one or more third control messages to the UE, the one or more third control messages activating or deactivating the measurement timing configuration at least in part based on the indication for activation or deactivation from the second network entity.

[0227] Aspect 16: According to the method of aspect 15, the one or more third control messages include MAC-CE messages or DCI messages.

[0228] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the one or more first control messages further include a second measurement timing configuration, the second measurement timing configuration indicating a second plurality of SSBs to be received by the UE via the first frequency layer.

[0229] Aspect 18: According to the method of aspect 17, wherein the second measurement timing configuration is related to a non-dynamically time-adjusted SSB, and the second plurality of SSBs is the non-dynamically time-adjusted SSB.

[0230] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the second SSB type including a dynamically time-adjusted SSB.

[0231] Aspect 20: The method according to aspect 19, the method further comprising: sending one or more third control messages, the one or more third control messages modifying the period of the first periodicity associated with the first SSB type, wherein the one or more third control messages include MAC-CE messages or DCI messages.

[0232] Aspect 21: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 13.

[0233] Aspect 22: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 13.

[0234] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 13.

[0235] Aspect 24: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 14 to 20.

[0236] Aspect 25: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 14 to 20.

[0237] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method according to any one of aspects 14 to 20.

[0238] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0239] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0240] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0241] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0242] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0243] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0244] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could 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 "at least partially based on".

[0245] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0246] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0247] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0248] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0249] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: One or more first control messages are received from a first network entity associated with the serving cell of the UE. The one or more first control messages include a measurement timing configuration, which indicates a first plurality of synchronization signal blocks (SSBs) to be received by the UE from neighboring cells via a first frequency layer. The measurement timing configuration is associated with the ability of the neighboring cells to dynamically time the first plurality of SSBs. as well as The first plurality of SSBs are monitored according to the measurement timing configuration.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive one or more second control messages, the one or more second control messages being activated or deactivated at least in part based on the first plurality of SSBs being dynamically timed, wherein monitoring of the first plurality of SSBs is performed in accordance with the activation or deactivation of the measurement timing configuration.

3. The UE according to claim 2, wherein the one or more second control messages include a Media Access Control (MAC)-Control Element (CE) message or a Downlink Control Information (DCI) message.

4. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The measurement timing configuration is disabled at least in part based on a deactivation timer at the UE or based on the expiration of a threshold duration.

5. The UE of claim 1, wherein the one or more first control messages further include a second measurement timing configuration, the second measurement timing configuration indicating a second plurality of SSBs to be received by the UE via the first frequency layer.

6. The UE of claim 5, wherein the second measurement timing configuration relates to a non-dynamically time-adjusted SSB, and the second plurality of SSBs is the non-dynamically time-adjusted SSB.

7. The UE of claim 5, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The first SSB among the plurality of SSBs is received based on a first power level, a first beamwidth, or both; and The second SSB in the plurality of SSBs is received based on the second power level, the second beamwidth, or both.

8. The UE of claim 1, wherein the measurement timing configuration includes a first periodicity associated with a first SSB type and a second periodicity associated with a second SSB type, the first SSB type including dynamically time-adjusted SSBs and the second SSB type including non-dynamically time-adjusted SSBs.

9. The UE of claim 8, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive one or more second control messages, the one or more second control messages modifying the period of the first periodicity associated with the first SSB type, wherein the one or more second control messages include a Media Access Control (MAC)-Control Element (CE) message or a Downlink Control Information (DCI) message.

10. The UE of claim 1, wherein the one or more processors are individually or jointly further capable of executing the code to cause the UE to: The measurement process is performed on the first plurality of SSBs at least in part based on the measurement state of the UE, wherein the measurement process includes one of the following: measuring the first plurality of SSBs or avoiding measuring the first plurality of SSBs.

11. The UE of claim 10, wherein, in order to perform the measurement process, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The measurement of the first plurality of SSBs is avoided at least in part based on the radio resource management (RRM) measurement status at the UE.

12. The UE of claim 10, wherein, in order to perform the measurement process, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The first plurality of SSBs are measured at least in part based on meeting a threshold mobility level, meeting a threshold signal quality, or both.

13. The UE of claim 1, wherein, in order to monitor the first plurality of SSBs, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The first plurality of SSBs from the plurality of neighboring cells are monitored according to the measurement timing configuration that indicates the plurality of neighboring cells.

14. A method for conducting wireless communication at a user equipment (UE), the method comprising: One or more first control messages are received from a first network entity associated with the serving cell of the UE. The one or more first control messages include a measurement timing configuration, which indicates a first plurality of synchronization signal blocks (SSBs) to be received by the UE from neighboring cells via a first frequency layer. The measurement timing configuration is associated with the ability of the neighboring cells to dynamically time the first plurality of SSBs. as well as The first plurality of SSBs are monitored according to the measurement timing configuration.

15. The method according to claim 14, further comprising: Receive one or more second control messages, the one or more second control messages being activated or deactivated at least in part based on the first plurality of SSBs being dynamically timed, wherein monitoring of the first plurality of SSBs is performed in accordance with the activation or deactivation of the measurement timing configuration.

16. The method of claim 15, wherein the one or more second control messages include a Media Access Control (MAC)-Control Element (CE) message or a Downlink Control Information (DCI) message.

17. The method of claim 14, further comprising: The measurement timing configuration is disabled at least in part based on a deactivation timer at the UE or based on the expiration of a threshold duration.

18. A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to: Receive one or more first control messages from a first network entity associated with a serving cell of a user equipment (UE), the one or more first control messages including a measurement timing configuration indicating a first plurality of synchronization signal blocks (SSBs) to be received by the UE from neighboring cells via a first frequency layer, wherein the measurement timing configuration is associated with the neighboring cells' ability to dynamically time the first plurality of SSBs; and The first plurality of SSBs are monitored according to the measurement timing configuration.

19. The non-transitory computer-readable medium of claim 18, wherein the one or more first control messages further include a second measurement timing configuration indicating a second plurality of SSBs to be received by the UE via the first frequency layer.

20. The non-transitory computer-readable medium of claim 19, wherein the second measurement timing configuration relates to a non-dynamically time-adjusted SSB, and the second plurality of SSBs is the non-dynamically time-adjusted SSB.

Images