On-demand non-cell-defined synchronization signal block transmission

Abstract

Methods, systems, and devices are described for wireless communication. In some systems, a network entity can transmit control signaling to a user equipment (UE) via one or more transmission opportunities within an operating bandwidth of the UE, the control signaling configuring an on-demand transmission scheme for a first synchronization signal block (SSB) of a cell. The cell can be associated with a carrier bandwidth that includes the operating bandwidth of the UE. The UE can transmit a message requesting transmission of one or more instances of the first SSB. The network entity can transmit the one or more instances of the first SSB based on the message. The one or more instances can be transmitted in the operating bandwidth of the UE and via at least one of the one or more transmission opportunities.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 506,365, filed November 10, 2023, entitled “ON-DEMAND NON-CELL-DEFINING SYNCHRONIZATION SIGNAL BLOCK TRANSMISSION”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following content relates to wireless communication, including on-demand non-cell-defined (NCD) synchronization signal block (SSB) transmission. Background Technology

[0004] 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).

[0005] In some systems, network entities can transmit synchronization signal blocks (SSBs) via the cell's carrier bandwidth. SSBs can be associated with system information for the cell, such as system information blocks (SIBs). The UE can measure the SSBs used for communication within the cell. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting on-demand non-cell-defined (NCD) synchronization signal block (SSB) transmission. For example, the described technology provides a network entity configured with an on-demand NCD-SSB transmission scheme (e.g., enabling on-demand NCD-SSB transmission) and a user equipment (UE) that requests the NCD-SSB according to the on-demand configuration. The network entity may send control signaling configuring the on-demand NCD-SSB transmission scheme. The control signaling may indicate a set of transmission opportunities allocated for the NCD-SSB within the UE's operating bandwidth. The network entity may avoid transmitting the NCD-SSB until it receives a request, reducing overhead compared to a system where the network entity periodically transmits the NCD-SSB. The UE may periodically switch to a second frequency outside the UE's operating frequency but within the cell's carrier frequency to monitor cell-defined SSBs (CD-SSBs) during one or more measurement intervals. If the UE detects that more frequent SSB measurements could be beneficial, the UE may send a message requesting a certain number of one or more NCD-SSBs. The network entity may then send at least that number of one or more NCD-SSBs based on the transmission timing within the UE's operating bandwidth, based on the request. The UE may monitor and measure that number of NCD-SSBs, and may subsequently revert to periodically monitoring the CD-SSBs. Thus, the UE can request bursts of NCD-SSB transmissions that are more frequent than CD-SSB transmissions, improving communication reliability and throughput while reducing overhead.

[0007] A method for wireless communication by a UE is described. The method may include: receiving control signaling via one or more of a plurality of transmission opportunities within a set of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; transmitting a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and receiving the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the plurality of transmission opportunities.

[0008] 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 be able to operate individually or jointly to execute the code, thereby enabling the UE to: receive control signaling via one or more of a set of multiple transmission opportunities within the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; transmit a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and receive the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the multiple transmission opportunities.

[0009] Another UE for wireless communication is described. The UE may include: components for receiving control signaling via one or more of a plurality of transmission opportunities within a set of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; components for transmitting a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and components for receiving the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the plurality of transmission opportunities.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive control signaling via one or more of a plurality of transmission opportunities within a set of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; transmit a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and receive the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the plurality of transmission opportunities.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing the following actions: receiving an indication of the number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB, wherein the first instance may be received at least the number of time slots after the message can be sent.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the message may include operations, features, components, or instructions for performing the following actions: sending an indication via the message of the number of instances requested by the UE, wherein the one or more instances of the first SSB include that number of instances based on the message.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the message may include operations, features, components, or instructions for performing the following actions: sending a selection request via the message that requests a network entity to select a default number of one or more instances, wherein the one or more instances include the default number of instances based on the selection request.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing actions such as receiving an indication of the default number of instances of the first SSB via the control signaling.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more instances receiving the first SSB may include operations, features, components, or instructions for performing the following actions: receiving a set of multiple instances of the first SSB via a first set of multiple transmission opportunities based on a default number of instances associated with a semi-persistent transmission mode; monitoring a second set of one or more transmission opportunities in the set of multiple transmission opportunities; and, after monitoring the second set of one or more transmission opportunities that excludes a threshold number of the first SSB, switching to periodically monitoring a second frequency in the carrier bandwidth for a second SSB that can be associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE.

[0016] The methods described herein, examples of UEs, and non-transitory computer-readable media may further include operations, features, components, or instructions for performing the following actions: sending a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein receiving control signaling may be based on the capability message.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a second frequency in the carrier bandwidth is periodically monitored for a second SSB that can be associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE, wherein the transmission of the message may be based on a change in one or more conditions associated with the second SSB.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the change in one or more conditions includes timing drift of the beam associated with the second SSB, or a change in the beam to the link, or both.

[0019] The methods described herein, examples of UEs, and nontransitory computer-readable media may further include operations, features, components, or instructions for performing the following actions: evaluating one or more communication metrics during a first time period based on monitoring the second frequency against the second SSB; and evaluating the one or more communication metrics during a second time period based on receiving the one or more instances of the first SSB, wherein the second time period may be longer than the first time period.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, after receiving one or more instances of the first SSB, a second frequency in the carrier bandwidth, which is outside the operating bandwidth of the UE, is periodically monitored for a second SSB that can be associated with system information of the cell.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing the following actions: receiving an indication via the control signaling for: a frequency associated with the first SSB, a periodicity associated with the first SSB, a time offset associated with the first SSB, or any combination thereof, wherein the frequency may be within the operating bandwidth of the UE.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Logical Channel Identifier (LCID) of the message indicates a request for transmission of one or more instances of the first SSB.

[0023] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the control signaling includes Radio Resource Control (RRC) signaling, and the message includes a Media Access Control-Control Element (MAC-CE).

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first SSB may be different from a second SSB that may be associated with system information of the cell, the first SSB including an NCD-SSB and the second SSB including a CD-SSB.

[0025] A method for wireless communication by a network entity is described. The method may include: transmitting control signaling via one or more of a plurality of transmission opportunities within a set of operational bandwidth of a UE, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the operational bandwidth of the UE; receiving a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and transmitting the one or more instances of the first SSB within the operational bandwidth of the UE based on the message via at least one of the plurality of transmission opportunities.

[0026] 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 be able to operate individually or jointly to execute the code, thereby enabling the network entity to: transmit control signaling via one or more of a plurality of transmission opportunities in a set of UE operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; receive a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and based on the message, transmit the one or more instances of the first SSB in the UE's operating bandwidth via at least one of the plurality of transmission opportunities.

[0027] Another network entity for wireless communication is described. This network entity may include: components for transmitting control signaling via one or more of a plurality of transmission opportunities within a set of UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; components for receiving a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and components for transmitting the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the plurality of transmission opportunities.

[0028] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit control signaling via one or more of a plurality of transmission opportunities within a set of UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; receive a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB; and based on the message, transmit the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for performing the following actions: sending an indication of a threshold number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB, wherein the first instance may be sent at least the threshold number of time slots after the message becomes receivable.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the message may include operations, features, components, or instructions for performing the following actions: receiving via the message an indication of the number of instances requested by the UE, wherein the one or more instances of the first SSB include that number of instances based on the message.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the message may include operations, features, components, or instructions for performing the following actions: receiving a selection request via the message, the selection request requesting the network entity to select a default number of one or more instances, wherein the one or more instances include the default number of instances based on the selection request.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the control signal may include operations, features, components, or instructions for performing the following actions: sending an indication via the control signal of the default number of instances of the first SSB.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more instances that transmit the first SSB may include operations, features, components, or instructions for performing the following actions: transmitting a set of multiple instances of the first SSB via a first set of multiple transmission opportunities based on a default number of instances associated with a semi-persistent transmission mode, wherein the control signaling indicates that the default number of instances may be associated with the semi-persistent transmission mode.

[0034] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for performing the following actions: receiving a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein sending the control signaling may be based on the capability message.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second SSB that can be associated with system information of the cell is periodically transmitted via a second frequency in the carrier bandwidth outside the operating bandwidth of the UE.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second SSB that can be associated with system information of the cell is periodically transmitted after the transmission of the first SSB and via a second frequency in the carrier bandwidth outside the operating bandwidth of the UE.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for performing the following actions: sending instructions via the control signaling for: a frequency associated with the first SSB, a periodicity associated with the first SSB, a time offset associated with the first SSB, or any combination thereof, wherein the frequency may be within the operating bandwidth of the UE.

[0038] The methods, network entities, and some examples of nontransitory computer-readable media described herein may further include operations, features, components, or instructions for performing actions such as avoiding the transmission of the first SSB before receiving the message based on the control signaling configured for the on-demand transmission scheme for the first SSB.

[0039] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the LCID of the message indicates a request to send to one or more instances of the first SSB.

[0040] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the control signaling includes RRC signaling, and the message includes MAC-CE.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first SSB may be different from a second SSB that may be associated with system information of the cell, the first SSB including an NCD-SSB and the second SSB including a CD-SSB. Attached Figure Description

[0042] Figure 1 An example of a wireless communication system supporting on-demand non-cell-defined (NCD) synchronization signal block (SSB) transmission according to one or more aspects of this disclosure is shown.

[0043] Figure 2 An example of a wireless communication system supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0044] Figure 3 An example of a Media Access Control-Control Element (MAC-CE) supporting on-demand NCD-SSB transmission is shown in accordance with one or more aspects of this disclosure.

[0045] Figure 4 An example of a communication timeline supporting on-demand NCD-SSB transmission is shown in accordance with one or more aspects of this disclosure.

[0046] Figure 5 An example flowchart supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0047] Figure 6 An example of a process flow supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0048] Figure 7 and Figure 8 A block diagram of an apparatus supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0049] Figure 9 A block diagram of a communication manager supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0050] Figure 10 A diagram of a system including a device supporting on-demand NCD-SSB transmission is shown in accordance with one or more aspects of this disclosure.

[0051] Figure 11 and Figure 12A block diagram of an apparatus supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0052] Figure 13 A block diagram of a communication manager supporting on-demand NCD-SSB transmission is shown, according to one or more aspects of this disclosure.

[0053] Figure 14 A diagram of a system including a device supporting on-demand NCD-SSB transmission is shown in accordance with one or more aspects of this disclosure.

[0054] Figures 15 to 18 A flowchart illustrating a method for supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. Detailed Implementation

[0055] In some wireless communication systems, user equipment (UE) can operate in a bandwidth narrower than the serving cell bandwidth (e.g., a bandwidth portion (BWP)) to reduce power consumption. The UE can monitor and perform measurements on synchronization signal blocks (SSBs) transmitted by network entities for purposes such as beam management, radio resource management, tracking, and radio link monitoring. Network entities can periodically transmit cell-defined SSBs (CD-SSBs). CD-SSBs can be transmitted outside the UE's operating bandwidth and can be associated with system information of the cell. Therefore, in some examples, the UE can be configured to periodically switch from its narrow operating bandwidth to a bandwidth in which CD-SSBs are transmitted to monitor CD-SSBs. However, such switching can increase latency due to, for example, timing drift or changes in beam configuration. In some other examples, periodic non-cell-defined SSBs (NCD-SSBs) can be configured within the UE's operating bandwidth. However, configuring and transmitting periodic NCD-SSBs for each UE can increase control resource overhead.

[0056] The technology described herein allows network entities to configure on-demand NCD-SSB transmission. A network entity can send control signaling to enable on-demand NCD-SSB via a set of transmission opportunities within the UE's operating bandwidth. Enabling on-demand NCD-SSB may include configuring an on-demand NCD-SSB transmission scheme, where the network entity can avoid transmitting NCD-SSBs until it receives a request, reducing overhead compared to systems where the network entity periodically transmits NCD-SSBs. Thus, when the UE detects a need for more frequent SSBs, it can request the network entity to transmit NCD-SSBs. For example, the UE can send a Media Access Control-Control Element (MAC-CE) indicating a request and a certain number of one or more NCD-SSBs. The network entity can transmit at least a certain number of one or more NCD-SSBs based on the request via transmission opportunities within the UE's operating bandwidth. Once the network entity has transmitted that number of one or more NCD-SSBs, the UE can return to periodically switching to a frequency band outside the UE's operating bandwidth to monitor NCD-SSBs.

[0057] The various aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects are described with reference to MAC-CE configurations, communication timelines, process flows, and flowcharts. The various aspects of this disclosure are further illustrated and described by way of example and reference to apparatus diagrams, system diagrams, and flowcharts relating to on-demand NCD-SSB transmission.

[0058] Figure 1 An example of a wireless communication system 100 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0059] 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 one or more communication links 125 (e.g., radio frequency (RF) access links). 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 one or more communication links 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).

[0060] 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 illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0061] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), 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. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or 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.

[0062] 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 one or more backhaul communication links 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 links 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. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0063] One or more network entities in network entity 105 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 (eNodeB, 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 that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0064] 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 two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 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 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0065] 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, and 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 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split 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 support one or more different cells (e.g., via one or more RU 170). 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 different 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 one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more 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 the corresponding network entities 105 communicating via such communication links.

[0066] In a wireless communication system (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 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB 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 a DU 165 of a coupled IAB donor. The IAB-MT may include 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 a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0067] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0068] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0069] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0070] In the context of applying the techniques described herein to a distributed RAN architecture, one or more components of the distributed RAN architecture can be configured to support on-demand NCD-SSB transmission as described herein. For example, some operations described as being performed by UE115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the distributed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0071] 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 various objects such as appliances or vehicles, meters, etc.

[0072] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0073] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical 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 physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, 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 may be configured with 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, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0074] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate 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., the same or different radio access technologies) are used to anchor the connection.

[0075] The communication link 125 shown in 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. A 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).

[0076] 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 particular radio access technology (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 of the carrier bandwidths 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.

[0077] 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, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the 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 may 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.

[0078] 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 with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0079] 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, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the 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).

[0080] 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 be further divided into a 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 number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 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.

[0081] 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. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0082] 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 common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0083] 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), or other identifier). 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, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0084] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, 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 restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or 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.

[0085] 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)).

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

[0087] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0088] 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 or 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 prioritization of 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.

[0089] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group 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 UE 115s 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, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0090] 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.

[0091] 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 lower 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 100 km).

[0092] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology. 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 combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0093] 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.

[0094] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0095] 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 specific orientation relative to 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 by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0096] 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.

[0097] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0098] In some examples of the wireless communication system 100, the serving cell bandwidth for the cell associated with UE 115 may be greater than the operating BWP. For example, the serving cell bandwidth may be up to 100 MHz for a first frequency range, or up to 400 MHz for a second frequency range, or it may be any other bandwidth. UE 115 may be configured to operate in a narrow BWP to reduce power consumption. For example, UE 115 may be configured to operate in a BWP that does not include the CD-SSB and the initial cell definition control resource set (CORESET) (e.g., CORESET0). UE 115 may operate via control signaling (e.g., via parameters, such as...) bwp- WithoutRestriction The UE receives an indication of such a configuration from network entity 105 (or some other parameter), and this configuration may indicate support for BWP operation without bandwidth limitations. Bandwidth limitations for the downlink BWP of the primary cell (PCell) and / or primary / secondary cell (PSCell) mean that the bandwidth of the downlink BWP in the RRC configuration specified by the UE may exclude the bandwidth of CORESET0 (if configured) and CD-SSB. For the secondary cell (SCell), bandwidth limitations may mean that the bandwidth of the downlink BWP may exclude CD-SSB.

[0099] In such cases, UE 115 can measure CD-SSBs outside of its operating BWP via measurement gaps. UE 115 can switch from its operating BWP to another frequency to measure CD-SSBs within one or more measurement gaps. Measurements can be used for tracking, beam management, radio link management, beam failure detection, or any combination thereof. Measurement gaps can be associated with relatively large periodicity (e.g., up to 160 milliseconds or some other periodicity), and UE 115 can share measurement gaps with other measurements, such as measurements on other frequency carriers. Therefore, the frequency at which UE 115 can track CD-SSBs can be relatively low. UE 115 may experience timing drift of the CD-SSB beam when measuring at low frequencies, or the appropriate beam link pair with network entity 105 may change between measurement gaps because UE 115 changes its subarray or the current beam link is associated with congestion.

[0100] In some examples, network entity 105 may transmit periodic NCD-SSBs, which can be configured in a BWP that does not include a CD-SSB. For example, network entity 105 may transmit NCD-SSBs via the operational BWP of UE 115. In some examples, network entity 105 may transmit NCD-SSBs periodically, which may incur relatively large overhead within the BWP and / or cell. In some other examples, the network entity may periodically transmit one or more reference signals via the operational BWP of UE 115. Reference signals may include, for example, Channel State Information (CSI) Reference Signals (CSI-RS), Tracking Reference Signals (TRS), or both. Reference signals may be used by UE 115 for measurements such as beam management, radio link management, and beam failure detection (e.g., reference signals configured for connected mode operation). Frequent transmission of reference signals may increase overhead within the BWP, may not be supported by various network infrastructures, may not be supported by one or more types of UE 115, or any combination thereof. As described in this article, the technology for UE 115 to request NCD-SSB on demand within BWP can reduce network overhead and improve the efficiency and reliability of beam management and tracking operations at UE 115, or both.

[0101] The techniques described herein allow network entity 105 to configure on-demand NCD-SSB transmission. Network entity 105 can transmit control signaling to enable on-demand NCD-SSB via a set of transmission opportunities within the operating bandwidth of UE 115. Network entity 105 can configure relatively short periodicity for NCD-SSBs of relatively short durations (e.g., NCD-SSB bursts), allowing UE 115 to perform more frequent measurements within the operating BWP. If on-demand NCD-SSB is enabled, network entity 105 can avoid transmitting NCD-SSBs until it receives a request, reducing overhead compared to systems where the network entity periodically transmits NCD-SSBs. Thus, when UE 115 detects a need for more frequent SSBs, UE 115 can request network entity 105 to transmit NCD-SSBs. For example, UE 115 can transmit a MAC-CE indicating the request and a certain number of one or more NCD-SSBs. Network entity 105 can transmit at least a certain number of one or more NCD-SSBs based on the request via transmission opportunities within the operating bandwidth. Once network entity 105 sends one or more of the required number of NCD-SSBs, UE 115 can revert to periodically switching to a frequency band outside the operating bandwidth to monitor CD-SSBs.

[0102] Figure 2An example of a wireless communication system 200 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. The wireless communication system 200 may include a network entity 205 and a UE 215, which may be represented as referenced... Figure 1 Examples of network entity 105 and UE 115 described. Network entity 205 and UE 215 can communicate within geographical coverage area 210 and via communication link 220 (e.g., Uu link). UE 215 can support reduced operating bandwidth. In some examples, network entity 205 can be configured to send SSBs on demand within the operating bandwidth of UE 215.

[0103] Network entity 205 and UE 115 can establish communication via a cell. The cell can be associated with a carrier bandwidth 225, which may also be referred to as the system bandwidth, and in some examples, the carrier bandwidth 225 can be relatively large. For example, the carrier bandwidth 225 can be up to 100 MHz or some other relatively wide range of frequencies. To reduce power consumption, UE 215 can be configured to utilize an operating bandwidth 230 smaller than the carrier bandwidth 225. The operating bandwidth 230 can be included within the carrier bandwidth 225 and can be a reduced range of frequencies that UE 215 can use to monitor communications.

[0104] For reference Figure 1 As described, in some examples, CD-SSB 235 may be configured within carrier bandwidth 225 but outside operating bandwidth 230. Network entity 205 may send indications of one or more periodic transmission times of CD-SSB 235 within carrier bandwidth 225 via RRC messages or some other type of control signaling. CD-SSB 235 may be an SSB associated with cell system information (e.g., pointing to or mapping to the cell's SIB-1). To reduce the timing delays and overhead associated with UE 215 periodically shifting out of operating bandwidth 230 to monitor CD-SSB 235, in some examples, network entity 205 may utilize operating bandwidth 230 to transmit periodic SSBs. The SSB may be referred to as NCD-SSB 240. However, NCD-SSB 240 may be associated with increased overhead.

[0105] As described herein, network entity 205 can provide on-demand NCD-SSB configuration. Network entity 205 may send control signaling 250 indicating or including on-demand NCD-SSB configuration. Control signaling 250 may be, for example, an RRC message or some other type of over-the-air configuration. Control signaling 250 may enable on-demand transmission of the cell's NCD-SSB 240 via one or more transmission opportunities within the operating bandwidth 230 of UE 215. Control signaling 250 may enable (e.g., or disable) on-demand configuration, may indicate a certain number of time slots associated with a request for on-demand transmission (e.g., nSlotsAdvance), may indicate a default number of consecutive SSB bursts (e.g., n-SS-Bursts-NCDSSB), or any combination thereof. In some examples, on-demand NCD-SSB configuration may be delivered via information elements within control signaling 250. In some examples, information elements may be included within a substructure of another information element used to configure NCD-SSB 240. Example structures of such information elements are shown below.

[0106]

[0107] In this example, control signaling 250 may include a NonCellDefiningSSB-r17 information element, which may indicate the frequency of NCD-SSB 240, the periodicity of NCD-SSB 240, the time offset of NCD-SSB 240, a pointer to on-demand NCD-SSB configuration, or any combination thereof. On-demand NCD-SSB configuration (e.g., RequestOnDemand) may point to a second information element. The second information element (e.g., RequestOnDemand-NonCellDefiningSSB information element) may indicate whether on-demand NCD-SSB transmission is enabled, the threshold number of time slots (e.g., nSlotsAdvance), the default number of consecutive NCD-SSB bursts (e.g., n-SS-Bursts-NCDSSB), or any combination thereof. It should be understood that the information elements are shown for illustrative purposes, and NCD-SSB configuration, on-demand NCD-SSB configuration, or both may be delivered via any type of control signaling 250 and in any format or structure.

[0108] Therefore, control signaling 250 can indicate whether on-demand transmission is enabled, and if so, indicate one or more parameters for NCD-SSB 240. In some examples, control signaling 250 can configure a set of potential transmission opportunities within operating bandwidth 230 for transmission of NCD-SSB 240. For example, if requested by UE 215, a set of periodic time and frequency resources in operating bandwidth 230 can be reserved for potential NCD-SSB transmissions.

[0109] In some examples, UE 215 may send a capability message 255 indicating whether UE 215 supports on-demand NCD-SSB. Capability message 255 may include capability information indicating the capability. If UE 215 indicates support for the feature, network entity 205 may enable on-demand NCD-SSB, and if UE 215 does not support the feature, on-demand NCD-SSB may not be enabled.

[0110] If on-demand NCD-SSB configuration is enabled (e.g., when " RequestOnDemand "Set and" OnDemand-NonCellDefiningSSB If set to True, network entity 205 can avoid sending NCD-SSB 240 within the default operating bandwidth 230. Instead, to save power and reduce overhead, network entity 205 can wait to send NCD-SSB 240 until it receives a request from UE 215.

[0111] UE 215 may send a message requesting the transmission of NCD-SSB 240 within operating bandwidth 230. This message may be, for example, MAC-CE 245 or some other type of message. UE 215 may send MAC-CE 245 at least a threshold number of time slots before the first time slot (e.g., time slot 0) of the first NCD-SSB transmission. The threshold number of time slots may be indicated via control signaling 250 (e.g., nSlotsAdvance). The identifier (ID) of MAC-CE 245 may indicate that UE 215 is requesting the transmission of NCD-SSB 240. MAC-CE 245 may include one or more parameters associated with NCD-SSB 240. For example, MAC-CE 245 may indicate the number of instances of NCD-SSB 240 that UE 215 wants to receive. The MAC-CE payload and format are further detailed elsewhere herein (including references). Figure 3 (This is a description of the process.)

[0112] UE 215 can use inter-frequency measurement gaps and sharing factors to track and measure CD-SSB 235 in carrier bandwidth 225 to account for other measurements. For example, UE 215 can periodically switch to frequencies outside operating bandwidth 230 to measure CD-SSB 235. If UE 215 detects a need for more frequent SSB tracking and reception, UE 215 can request on-demand NCD-SSB 240. For example, if UE 215 identifies a timing drift of the CD-SSB beam or a change in the link with the appropriate beam of network entity 205, or indicates that UE 215 may need more information from network entity 205 for another parameter or condition to ensure reliable communication, UE 215 can detect a need for more frequent SSB tracking.

[0113] UE 215 may send MAC-CE 245 to request NCD-SSB 240 in response to an indication of a need for more frequent SSB transmissions. Once network entity 205 receives the request, network entity 205 may transmit a first instance of NCD-SSB 240 after at least a threshold number of time slots. Network entity 205 may transmit one or more instances of NCD-SSB 240, wherein the number of instances transmitted may be based on information indicated via MAC-CE 245. When transmitting on-demand NCD-SSB 240, network entity 205 may avoid additional transmissions of other downlink channels (e.g., Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH)) for UE 215 and / or other UE 215 in the cell via SSB resource blocks and symbols.

[0114] Therefore, network entity 205 can reduce overhead and power consumption by enabling on-demand NCD-SSB transmission. UE 215 can monitor tracking information and reliability, and can request on-demand NCD-SSB 240 when UE 215 detects a need for more frequent SSBs. Thus, network entity 205 and UE 215 can maintain reliable communication with reduced overhead.

[0115] Figure 3 An example of a MAC-CE configuration 300 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. In some examples, the MAC-CE configuration 300 may implement, or be implemented by, aspects of wireless communication systems 100 and 200. For example, the MAC-CE configuration 300 illustrates a format of a MAC-CE 345 that may indicate a request for on-demand NCD-SSB transmission made by a UE. The UE may transmit the MAC-CE 345 to a network entity. The UE and the network entity may represent as referenced. Figure 1 and Figure 2 Examples of the corresponding devices described.

[0116] Network entities can configure on-demand NCD-SSB transmission to the UE, as shown in the reference. Figure 2 As described. Therefore, network entities can avoid sending NCD-SSBs until they receive a request. See reference. Figure 2 As described, the UE can periodically switch from its operating bandwidth to another frequency outside its operating bandwidth but within its carrier bandwidth in the frequency domain to monitor and measure the CD-SSB. The UE can switch to other frequencies during periodic measurement intervals, and the UE can share these measurement intervals with other operations / measurements. Therefore, the UE can measure the CD-SSB infrequently. If the UE detects any condition or measurement indicating that the UE would benefit from more frequent SSB measurements, the UE can send a MAC-CE345 requesting one or more instances of the NCD-SSB within its operating bandwidth. The UE can then measure NCD-SSB instances more frequently within its operating bandwidth than the UE measures the CD-SSB itself, which provides more accurate and reliable measurement information at the UE.

[0117] MAC-CE 345 can be transmitted via uplink data or control channels via uplink packet data units (PDUs). A PDU may include one or more MAC sub-PDUs 320. In some examples, MAC sub-PDU 320-a may include a MAC Service Data Unit (SDU) and may include a subheading and a MAC SDU. MAC sub-PDU 320-b may also include an SDU. MAC sub-PDU 320-c may include a MAC-CE 345 requesting NCD-SSB transmission. In some examples, MAC-CE 345 may be a fixed-size MAC-CE (e.g., eight bits or some other size). In some examples, MAC sub-PDU 320-d may include another MAC-CE, which may be a variable-size MAC-CE. In some examples, MAC sub-PDU 320-e may include padding.

[0118] When requesting on-demand NCD-SSB, the UE may send at least MAC sub-PDU 320-c. MAC sub-PDU 320-c can be identified by a Logical Channel ID (LCID), which can be set to a configuration value X indicating the MAC-CE 345 used for the on-demand NCD-SSB request. The LCID value used for on-demand NCD-SSB can be any value configured by the network entity and / or the UE, such as LCID 47, or some other value reserved for the NCD-SSB request. The header of MAC-CE 345 may include one or more reserved bits, a field length bit indicating the length of the field, and the LCID. In this example, the field length may be set to a first value indicating that MAC-CE 345 has an eight-bit payload (e.g., F = 0).

[0119] The payload of MAC-CE 345 can indicate a unique LCID reserved for on-demand NCD-SSB requests and the UE's preference for the number of instances of NCD-SSBs sent (e.g., the number of subsequent SSB bursts, UE_Num_SSB_Burst_Request). The UE can indicate the number of instances via three bits (e.g., the three least significant bits) in the payload of MAC-CE 345. For example, values ​​“001”, “010”, “011”, “100”, “101”, and “111” can correspond to the UE's preference in a set of defined options (e.g., {n1, n2, n4, n8, n16, n32}). This set of defined options can be indicated via control signaling to enable on-demand NCD-SSB requests. The value “000” indicates that the UE has no preference for the number of SSB bursts. In this example, the network entity can send the default number of SSB instances. The default number can be configured via control signaling (e.g., n-SS-Bursts-NCDSSB). Five additional bits in the payload of MAC-CE 345 may be reserved for additional information or any other information related to on-demand NCD-SSB.

[0120] The network entity can receive MAC-CE 345, decode MAC-CE 345, and determine whether to send a MAC-CE request for NCD-SSB based on the configuration value of LCID set for on-demand NCD-SSB. The network entity can decode the payload of MAC-CE 345 to determine whether the UE has requested a certain number of instances of NCD-SSB. The network entity can send the requested number of instances of NCD-SSB based on the request, as further detailed elsewhere in this document (including references). Figure 4 As described in ).

[0121] Figure 4An example of a communication timeline 400 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. The communication timeline 400 may implement, or be implemented by, aspects of, wireless communication systems 100 and 200, as referenced. Figure 1 and Figure 2 As described. For example, communication timeline 400 illustrates communication between a network entity and a UE, which can be represented as shown in the reference. Figures 1 to 3 An example of the corresponding device described. In this example, the network entity can enable on-demand NCD-SSB transmission, the UE can request a burst of NCD-SSB instances, and the network entity can transmit the NCD-SSB instances accordingly. When on-demand NCD-SSB is enabled (e.g., configured), the network entity can avoid transmitting NCD-SSBs until the network entity receives a request for on-demand transmission from the UE.

[0122] The UE can support a reduced bandwidth, which may be referred to as the operating bandwidth 430 or active bandwidth. The operating bandwidth 430 can be a reduced frequency range within the larger carrier bandwidth 425 of the cell. During measurement intervals 420-a, the UE can switch from monitoring the UE's operating bandwidth 430 to monitoring frequencies outside the UE's operating bandwidth 430 but within the cell's carrier bandwidth 425. For example, the UE can switch to a frequency 460 that is within the carrier bandwidth 425 but outside the operating bandwidth 430 to monitor CD-SSB 435. The operating bandwidth 430 and carrier bandwidth 425 may represent reference... Figure 2 Examples of the described operating bandwidth 230 and carrier bandwidth 225 are provided. The network entity may transmit CD-SSB 435 via frequency 460 during measurement gap 420-a. The UE may receive and measure CD-SSB 435 via one or more time slots (e.g., two time slots or a certain other number of time slots). The UE may switch back to operating bandwidth 430 at the end of measurement gap 420-a.

[0123] After measurement gap 420-a and before the next measurement gap 420, the UE may detect trigger condition 415. The trigger condition may correspond to a condition at the UE indicating that the UE can benefit from more frequent SSB tracking. For example, trigger condition 415 may correspond to the UE detecting timing drift of the CD-SSB beam, a change in the appropriate beam pair, or some other condition. The UE may send a MAC-CE 445 (e.g., a message) requesting one or more NCD-SSB instances based on trigger condition 415. MAC-CE 445 may represent a reference. Figure 2 and Figure 3Examples of MAC-CE 245 or MAC-CE 345 described herein. For example, MAC-CE 445 may indicate a request for NCD-SSB 440 and may indicate the number of instances of NCD-SSB 440.

[0124] The UE may transmit MAC-CE 445 at least a threshold number of time slots 405 prior to the first transmission timing for the first NCD-SSB 440. The threshold number of time slots 405 may be indicated via control signaling received at the UE, as referenced in [reference]. Figure 2 As described. Additionally or alternatively, the UE may transmit MAC-CE 445, and the network entity may determine when to begin NCD-SSB transmission based on the time slot in which MAC-CE 445 is received and a threshold number of time slots 405. Thus, the start boundary of the first instance of NCD-SSB 440 can be received at least a threshold number of time slots 405 after the end boundary of MAC-CE 445.

[0125] A network entity can transmit a first instance of NCD-SSB440 based on a threshold number of time slots 405 and via the UE's operating bandwidth 430. Thus, the UE can receive and measure NCD-SSB440 within the operating bandwidth 430 without switching frequencies. The network entity can transmit one or more instances of NCD-SSB 440. The number of instances transmitted can be based on a number requested via MAC-CE 445. For example, the UE can request a certain number of instances via MAC-CE 445, or the UE can request a default number, and the network entity can select the default number of instances accordingly. Figure 4 In the example, the network entity can send four instances of NCD-SSB 440.

[0126] Instances of NCD-SSB 440 can be transmitted via one or more transmission opportunities within the UE's operating bandwidth 430. Transmission opportunities can be scheduled by the network entity via control signaling that configures on-demand NCD-SSB transmission. For example, the control signaling may indicate the frequency, periodicity 410, and / or time offset of the NCD-SSB 440, as referenced... Figure 2 As described. In some aspects, instances of NCD-SSB 440 may be received according to periodicity 410. Additionally or alternatively, instances may be received at specific times. In some examples, the number of instances of NCD-SSB 440 may be referred to as an NCD-SSB burst.

[0127] The requested number of instances are sent by the network entity and received by the UE in NCD-SSB 440 (e.g., Figure 4After the final instance of the four instances (in the above), on-demand NCD-SSB transmission can be completed. Therefore, the network entity can continue to transmit periodic CD-SSB 435. After receiving the final NCD-SSB 440, the UE can monitor the operating bandwidth 430 until the next measurement gap 420-b is allocated for SSB measurement. The UE can switch from the operating bandwidth 430 to a frequency outside the operating bandwidth 430 but within the carrier bandwidth 425 (e.g., frequency 460) to monitor and receive CD-SSB 435. Thus, the UE can continue to periodically measure CD-SSB 435 via measurement gap 420 after an NCD-SSB burst. If another trigger condition 415 is identified, the UE can later request another on-demand NCD-SSB transmission.

[0128] The number of instances can be requested by the UE via MAC-CE 445 (e.g., n-SS-Bursts-NCDSSB = n4), or it can be a default number (e.g., if the UE requests a default number via MAC-CE 445). The default number can be a defined number. Additionally or alternatively, in some examples, the default number of instances configured by the network entity is set to a disabled default value (e.g., nContTxUntilDeact). In such cases, if the MAC-CE 445 sent by the UE indicates that the UE does not have a preference regarding the number of instances of the sent NCD-SSB 440 (e.g., UE_Num_SSB_Burst_Request = 000) and the default number is set to a disabled default value, the network entity can send NCD-SSB 440 in a semi-persistent manner until NCD-SSB 440 is disabled by the network entity. For example, a network entity may send a first instance of NCD-SSB 440 via a first anticipated location (e.g., the next transmission opportunity after at least a threshold number of time slots 405 following MAC-CE 445) and may send the remaining instances in a semi-persistent manner across subsequent transmission opportunities. The network entity may stop NCD-SSB 440 after a certain duration. In some examples, the default NCD-SSB transmission pattern and duration may be determined by the network entity. If the UE does not detect NCD-SSB 440 across a threshold number (K) of consecutive transmission opportunities (e.g., SSB burst locations), the UE may determine to fall back to tracking CD-SSB 435. The threshold number may be a fixed value configured for the UE or defined by the UE (e.g., K=6, K=8, or some other number). That is, the UE may monitor a certain number of transmission opportunities, and if no NCD-SSB is detected for at least a threshold number of transmission opportunities, the UE may fall back to periodically monitoring CD-SSB 435 via measurement intervals.

[0129] As a result, network entities and UEs can perform on-demand NCD-SSB communication within the UE's operating bandwidth 430, which improves communication reliability and reduces overhead compared to systems that continuously (e.g., periodically) send NCD-SSB 440.

[0130] When NCD-SSB 440 is not configured during the evaluation period, the UE can measure CD-SSB 435. The UE can perform radio link management, beam fault detection, Layer 1 Reference Signal Received Power (RSRP) measurement, or any combination thereof during the evaluation period. The evaluation period can be based on a combination of the periodicity of measurement gap 420, the periodicity of CD-SSB 435, and a sharing factor (e.g., for sharing measurement gap 420). When on-demand NCD-SSB is configured based on the UE's request, the UE evaluation period for radio link management, beam fault detection, or RSRP measurement, etc., can be based on the periodicity of NCD-SSB 440.

[0131] When a UE requests on-demand NCD-SSB 440, a transition period 450 may exist, during which the UE may be in the middle of an evaluation period based on CD-SSB 435, but the UE may have already requested activation of NCD-SSB 440. During this transition period 450, the UE may meet relaxed measurement requirements. For example, the UE may meet a first requirement (e.g., the duration of a first evaluation period) based on a combination of the periodicity of CD-SSB 435 for an evaluation period, the periodicity of the measurement gap 420, and a common factor, and the UE may meet a second requirement (e.g., the duration of a second evaluation period) based on the periodicity of NCD-SSB 440 for the next evaluation period. That is, during the transition period 450, an evaluation period may have a first evaluation period duration, and during the subsequent transition period 455, an evaluation period may have a second evaluation period duration.

[0132] Figure 5 An example flowchart 500 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. Flowchart 500 may implement, or be implemented by, aspects of, wireless communication systems 100 and 200, MAC-CE configuration 300, or communication timeline 400, as referenced. Figures 1 to 4 As described. For example, flowchart 500 illustrates an algorithm for on-demand NCD-SSB transmission between a network entity and a UE. The network entity and the UE can be represented as shown in the reference. Figures 1 to 4 Examples of the corresponding devices described.

[0133] In the following description of flowchart 500, operations may be performed in different orders or at different times. Some operations may also be omitted from flowchart 500, or other operations may be added. Flowchart 500 illustrates various decisions and operations performed by network entities, UEs, one or more other wireless devices or components, or any combination thereof, in a wireless communication system. Although Figure 5 The illustrated operations are described as being performed by network entities and / or UEs, but it should be understood that the operations can be performed by any device to facilitate on-demand transmission of NCD-SSB from the network to the UE.

[0134] At point 505, the network entity and the UE can determine whether to configure on-demand NCD-SSB. For example, the network entity and the UE can determine whether to configure NCD-SSB in the UE's active BWP and whether on-demand NCD-SSB requests have been enabled (e.g., RequestOnDemand=setup && OnDemand-NonCellDefiningSSB=True?). If NCD-SSB is not configured, the network entity may not send NCD-SSB. If NCD-SSB is configured but on-demand NCD-SSB is not enabled, at point 510, the network entity can perform periodic NCD-SSB transmission. For example, the network entity can periodically send NCD-SSB based on NCD-SSB configuration via one or more transmission times within the UE's active BWP. The UE can monitor and receive NCD-SSB accordingly.

[0135] At point 515, if on-demand NCD-SSB is enabled, network entities can avoid periodically sending NCD-SSB. That is, network entities can default to not sending NCD-SSB in the UE's active BWP and can instead send NCD-SSB on demand. The UE can determine whether to monitor NCD-SSB based on whether on-demand NCD-SSB is enabled (e.g., based on control signaling received at the UE).

[0136] At 520, the UE can track CD-SSB via one or more measurement gaps. Network entities can periodically transmit CD-SSB via frequencies outside the UE's active BWP but within the carrier bandwidth. The UE can track and measure CD-SSB based on on-demand NCD-SSB activation. At 525, the UE can determine whether more frequent SSB measurements would be beneficial. The UE can make this determination based on one or more conditions, such as reference... Figures 2 to 4 As described. If more frequent SSB measurements are not beneficial, the UE can continue to track CD-SSB via measurement gaps.

[0137] At point 530, if the UE determines that more frequent SSB tracking would be beneficial, the UE may send a MAC-CE to the network entity. The MAC-CE may instruct the network entity to send one or more NCD-SSB requests. The MAC-CE may indicate the number of requests and NCD-SSB instances, as shown in the reference. Figure 3 and Figure 4 As described. The time slot in which the UE transmits the Physical Uplink Shared Channel (PUSCH) containing the uplink MAC-CE (e.g., an LCID indicating a request for an on-demand NCD-SSB) can be referred to as time slot Y. At 535, it can be determined whether the network entity has successfully decoded the MAC-CE.

[0138] At 540, if the network entity fails to decode the MAC-CE, in some examples, the network entity may determine whether to send an uplink grant to the UE to request a retransmission of the MAC-CE. At 545, if the network entity does not send an uplink grant, the UE may avoid retransmitting the MAC-CE, and at 520, the UE may continue to track the CD-SSB via the measurement gap. In some examples, the UE may receive a NACK or some other indication that the network entity has not decoded the MAC-CE. Additionally or alternatively, the UE may determine that it has not sent an NCD-SSB in response to the MAC-CE, and the UE may return to monitoring the CD-SSB after a threshold time period in which the UE has not detected the NCD-SSB.

[0139] At 550, if a network entity sends an uplink grant and requests a retransmission of MAC-CE, the network entity can increment time slot Y to the time slot scheduled for MAC-CE retransmission. At 530, the UE can retransmit MAC-CE via time slot Y indicated by the uplink grant.

[0140] At 555, if the network entity successfully decodes the MAC-CE (e.g., the first transmission or retransmission), the network entity and the UE can determine whether to transmit the MAC-CE within a threshold number of time slots before allocating time slot X for NCD-SSB transmission (e.g., a time slot within an NCD-SSB burst containing an NCD-SSB instance with index zero). One or more transmission opportunities (e.g., time slots) can be scheduled for an NCD-SSB burst with index N. The network entity and the UE can determine the transmission opportunity (e.g., frame position) based on the periodicity of the SSB configured via NCD-SSB configuration, the SSB offset, or both. Time slot X can be the first time slot within the most recent burst N after the MAC-CE. The threshold number of time slots can represent a reference... Figure 4 An example of the threshold number for the described time slot 405. Network entities and UEs can determine (e.g., set, store) the intended location (time slot) through which they can transmit NCD-SSB based on the threshold number.

[0141] For example, at 560, if no MAC-CE is transmitted in at least a threshold number of time slots before the next transmission opportunity (e.g., Where nSlotsAdvance is the threshold number of slots), the network entity and UE can increment the index of the expected NCD-SSB burst to N+1. At 565, if MAC-CE is sent in at least the threshold number of slots before the next transmission opportunity (e.g., ...), If nSlotsAdvance is the threshold number of time slots, then the network entity and UE can set the index of the expected NCD-SSB burst to N (e.g., the first transmission timing). In this way, the network entity and UE can determine which transmission timing is available for NCD-SSB.

[0142] At 570, the network entity can determine whether the UE has requested a certain number of instances. That is, the network entity can determine, based on the indication in the MAC-CE, whether the UE has requested a certain number of instances from the NCD-SSB or indicated a request for the network entity to select that number of instances (e.g., the default number). At 575, if the UE has not explicitly requested a certain number of instances, the network entity can set a default number of instances. In some examples, the default number can be configured or indicated via NCD-SSB configuration, as referenced... Figure 2 and Figure 3 As described. At 580, if the UE does request a certain number of instances, the network entity may set that number to be equal to the number indicated via the request.

[0143] At 585, the network entity may send that number of NCD-SSB instances. The network entity may send the first instance of NCD-SSB to the UE via time slot X within the expected burst N or N+1 as determined at 560 and 565. If the number of instances is greater than one, the network entity may send the remaining instances of NCD-SSB via subsequent time slots according to the NCD-SSB periodicity and time offset configured by the network entity, as referenced. Figure 4 As described. The UE can monitor and receive this number of instances of NCD-SSB.

[0144] At 590, it can be determined whether the UE has successfully decoded the required number of NCD-SSB instances. In some examples, the UE can make this determination internally, or the UE can send an acknowledgment or a negative acknowledgment to indicate whether the UE has decoded the NCD-SSB or not. If the UE cannot decode the NCD-SSB, the UE can return to 520 to track the CD-SSB during the measurement interval. At 595, if the UE is able to successfully decode the NCD-SSB, the UE can track the required number of NCD-SSB instances. The UE can continue to periodically monitor the indicated NCD-SSB frequency for at least the required number of instances based on the NCD-SSB. After the UE has tracked the required number of NCD-SSB instances, the UE can return at 520 to track the CD-SSB via the measurement interval.

[0145] Therefore, network entities can configure and facilitate on-demand NCD-SSB transmission. When on-demand NCD-SSB is configured, the UE can dynamically request NCD-SSB transmission when the UE needs more frequent SSB measurements, and the UE can monitor NCD-SSB in an external frequency when the UE does not need more frequent SSB measurements. This allows both network entities and the UE to support improved throughput and reliability while reducing overhead.

[0146] Figure 6 An example of a process flow 600 supporting on-demand NCD-SSB transmission according to one or more aspects of this disclosure is shown. Process flow 600 may implement, or be implemented by, aspects of, wireless communication systems 100 and 200, MAC-CE configuration 300, communication timeline 400, or flowchart 500, as referenced. Figures 1 to 5 As described. For example, process flow 600 illustrates communication between network entity 605 and UE 615, which can be represented as shown in reference. Figures 1 to 5 Examples of the corresponding devices described.

[0147] In the following description of process flow 600, operations may be performed in different orders or at different times. Some operations may also be omitted from process flow 600, or other operations may be added. Although network entity 605 and UE 615 are shown as performing operations of process flow 600, some aspects of some operations may also be performed by one or more other wireless devices.

[0148] At 620, network entity 605 may send control signaling to UE 615 to enable on-demand transmission of the first SSB of the cell. The control signaling enables the first SSB to be transmitted via one or more transmission opportunities within the operating bandwidth of UE 615. For example, the control signaling (e.g., an RRC message or some other type of signaling) may configure SSB periodicity, time offset, frequency, or any combination thereof, as referenced. Figure 2As described. In some examples in this document, SSB may represent an example of NCD-SSB. Control signaling may be represented as in the reference. Figure 2 Examples of control signaling 250 are described in further detail below. In some examples, UE 615 may send a capability message indicating that UE 615 supports the capability of on-demand SSB communication, and network entity 605 may send control signaling in response to or based on the UE capability message. Network entity 605 may avoid periodically or semi-statically sending the first SSB until network entity 605 receives a request for on-demand transmission based on control signaling.

[0149] UE 615 can periodically monitor a second SSB within a second frequency in the cell's carrier bandwidth. The second SSB can be associated with system information of the cell. For example, the second SSB can be associated with CORESET0, SIB-1, or some other type of system information. The second SSB can be, for example, a CD-SSB as described herein. The second frequency can be outside the UE's operating frequency.

[0150] In some examples, at 625, UE 615 may detect a change in one or more conditions associated with UE 615, the second SSB, or both. For example, UE 615 may detect timing drift of the beam associated with the second SSB, or a change in the beam to the link, or both. A change in one or more conditions may indicate that more frequent measurements could be beneficial to communication (e.g., more frequent than with CD-SSB).

[0151] At 630, UE 615 may send a message to network entity 605 requesting the transmission of one or more instances of the first SSB. UE 615 may send the message based on control signaling, a change detected at 625, or both. The message may be a MAC-CE or some other type of message. The message ID may indicate the request for transmission of the first SSB. In some examples, the message may include an indication of the number of instances of the first SSB that UE 615 is requesting.

[0152] At 635, network entity 605 may send one or more instances of the first SSB to UE 615 based on this message. The first SSB may be sent within the operating bandwidth of UE 615 and via at least one of the transmission opportunities configured by control signaling. The timing of the first SSB instance may be determined according to an algorithm, as further detailed elsewhere herein (including references). Figure 5As described in the description. If the message indicates the number of instances, network entity 605 may send the requested number of instances or a number based in part on the requested number. If the message indicates that UE 615 does not have a preference regarding the number, network entity 605 may send the default number of instances for the first SSB. The default number may be indicated via control signaling.

[0153] UE 615 can monitor and receive one or more instances of the first SSB within its operating bandwidth. After receiving one or more instances, UE 615 can continue to periodically transmit according to the second frequency to monitor the second SSB.

[0154] Figure 7 A block diagram 700 of a device 705 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure is shown. Device 705 may be an example of aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] Receiver 710 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 associated with on-demand NCD SSB transmission). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a group of multiple antennas.

[0156] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with on-demand NCD SSB transmission), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a group of multiple antennas.

[0157] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of on-demand NCD SSB transmission as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0158] In some examples, the communication manager 720, receiver 710, transmitter 715, 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).

[0159] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, 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).

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

[0161] Additionally or alternatively, the communication manager 720 may support wireless communications according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operated to support components for performing the following actions: receiving control signaling via one or more of a plurality of transmission opportunities in a set of multiple transmission opportunities within the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The communication manager 720 may be capable of, configured to, or operated to support components for performing the following actions: transmitting a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB. The communication manager 720 may be capable of, configured to, or operated to support components for performing the following actions: receiving the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0162] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently, etc.

[0163] Figure 8 A block diagram 800 of a device 805 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820) may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] Receiver 810 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 associated with on-demand NCD SSB transmission). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0165] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with on-demand NCD SSB transmission), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0166] Device 805 or its various components may be examples of parts used to perform various aspects of on-demand NCD SSB transmission as described herein. For example, communication manager 820 may include control signal component 825, request component 830, SSB component 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0167] Communication manager 820 can support wireless communication according to examples disclosed herein. Control signal component 825 is capable of, configured to, or operable to support components for performing the following actions: receiving control signaling via one or more of a set of multiple transmission opportunities in the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. Request component 830 is capable of, configured to, or operable to support components for performing the following actions: transmitting a message according to the on-demand transmission scheme, the message requesting the transmission of one or more instances of the first SSB. SSB component 835 is capable of, configured to, or operable to support components for performing the following actions: receiving the one or more instances of the first SSB in the UE's operating bandwidth via at least one of the set of multiple transmission opportunities based on the message.

[0168] Figure 9A block diagram 900 of a communication manager 920 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of on-demand NCD SSB transmission as described herein. For example, the communication manager 920 may include a control signal component 925, a request component 930, an SSB component 935, a threshold component 940, an instance component 945, a capability component 950, a measurement component 955, 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).

[0169] Additionally or alternatively, the communication manager 920 may support wireless communication according to the examples disclosed herein. The control signaling component 925 is capable of, configured to, or operable to support components for performing the following actions: receiving control signaling via one or more of a plurality of transmission opportunities within a set of multiple transmission opportunities of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The request component 930 is capable of, configured to, or operable to support components for performing the following actions: transmitting a message according to the on-demand transmission scheme, the message requesting the transmission of one or more instances of the first SSB. The SSB component 935 is capable of, configured to, or operable to support components for performing the following actions: receiving the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0170] In some examples, in order to support receiving the control signaling, the threshold component 940 is capable, configured, or operable to support components for performing the following actions: receiving an indication of the number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB, wherein the first instance is received at least the number of time slots after the message is sent.

[0171] In some examples, in order to support the sending of the message, instance component 945 is able to be configured or can operate to support components for performing the following actions: sending an indication of the number of instances requested by the UE via the message, wherein the one or more instances of the first SSB include that number of instances based on the message.

[0172] In some examples, in order to support sending the message, instance component 945 can, be configured, or operate to support components for performing the following actions: sending a selection request via the message, the selection request requesting a network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances based on the selection request.

[0173] In some examples, in order to support receiving the control signaling, instance component 945 is able to be configured or operated to support components for receiving an indication of the default number of instances of the first SSB via the control signaling.

[0174] In some examples, to support the reception of one or more instances of the first SSB, instance component 945 is capable of, configured to, or able to operate to support components for performing the following actions: receiving one or more instances of the first SSB via a first set of transmission opportunities based on the default number of instances associated with the semi-persistent transmission mode. In some examples, to support the reception of one or more instances of the first SSB, instance component 945 is capable of, configured to, or able to operate to support components for performing the following actions: monitoring one or more second sets of transmission opportunities within the first set of transmission opportunities. In some examples, to support the reception of one or more instances of the first SSB, instance component 945 is capable of, configured to, or able to operate to support components for performing the following actions: after monitoring one or more second sets of transmission opportunities that exclude a threshold number of the first SSB, switching to periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE.

[0175] In some examples, capability component 950 is capable of, configured to, or able to operate to support components for performing the following actions: sending a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein receiving the control signaling is based on the capability message.

[0176] In some examples, SSB component 935 is capable of, configured to, or able to operate to support components for performing the following actions: periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE, wherein the message is transmitted based on a change in one or more conditions associated with the second SSB. In some examples, the change in one or more conditions includes a timing drift of the beam associated with the second SSB, or a change in the beam to the link, or both.

[0177] In some examples, the measurement component 955 is capable of, configured to, or operable to support components for performing the following actions: monitoring the second frequency for the second SSB to evaluate one or more communication metrics during a first time period. In some examples, the measurement component 955 is capable of, configured to, or operable to support components for performing the following actions: evaluating one or more communication metrics during a second time period based on the one or more instances of the first SSB being received, wherein the second time period is longer than the first time period.

[0178] In some examples, SSB component 935 is capable of, configured to, or able to operate to support components for performing the following actions: after receiving one or more instances of the first SSB, periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE.

[0179] In some examples, in order to support receiving the control signaling, the SSB component 935 is capable, configured, or operable to support components for performing the following actions: receiving instructions via the control signaling for: the frequency associated with the first SSB, the periodicity associated with the first SSB, the time offset associated with the first SSB, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

[0180] In some examples, the LCID of the message indicates a request for transmission of one or more instances of the first SSB. In some examples, the control signaling includes RRC signaling, and the message includes MAC-CE. In some examples, the first SSB differs from the second SSB associated with the cell's system information; the first SSB includes a non-cell-defined SSB, and the second SSB includes a cell-defined SSB.

[0181] Figure 10A diagram of a system 1000 including device 1005 supporting on-demand NCD SSB transmission, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

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

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

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

[0185] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting on-demand NCD SSB transmission). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, wherein at least one processor 1040 and at least one memory 1030 are configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1040 may be a component of a processing system, which may refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or components that receive or obtain input and process that 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. Thus, at least one processor 1040 or a processing system including at least one processor 1040 may be configured, configured to, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable 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 1030 or otherwise.

[0186] Additionally or alternatively, the communication manager 1020 may support wireless communications according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operated to support components for performing the following actions: receiving control signaling via one or more of a plurality of transmission opportunities in a set of multiple transmission opportunities within the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The communication manager 1020 may be capable of, configured to, or operated to support components for performing the following actions: transmitting a message according to the on-demand transmission scheme, the message requesting transmission of one or more instances of the first SSB. The communication manager 1020 may be capable of, configured to, or operated to support components for performing the following actions: receiving the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0187] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, and improving processing power utilization, etc.

[0188] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1015, one or more antennas 1025, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by at least one processor 1040 to cause device 1005 to perform various aspects of on-demand NCD SSB transmission as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0189] Figure 11A block diagram 1100 of a device 1105 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] Receiver 1110 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 passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0191] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 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 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0192] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of on-demand NCD SSB transmission as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0193] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, 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).

[0194] Additionally or alternatively, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, 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).

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

[0196] Additionally or alternatively, the communication manager 1120 may support wireless communication according to the examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operated to support components for performing the following actions: transmitting control signaling via one or more of a plurality of transmission opportunities in a set of multiple transmission opportunities of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The communication manager 1120 may be capable of, configured to, or operated to support components for performing the following actions: receiving a message according to the on-demand transmission scheme, the message requesting the transmission of one or more instances of the first SSB. The communication manager 1120 may be capable of, configured to, or operated to support components for performing the following actions: transmitting the one or more instances of the first SSB in the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0197] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently, etc.

[0198] Figure 12 A block diagram 1200 of a device 1205 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220) may include at least one processor that can be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0199] Receiver 1210 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 passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0200] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 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 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 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 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0201] Device 1205 or its various components may be examples of parts used to perform various aspects of on-demand NCD SSB transmission as described herein. For example, communication manager 1220 may include control signal component 1225, request component 1230, SSB component 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use receiver 1210, transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0202] Communication manager 1220 can support wireless communication according to examples disclosed herein. Control signal component 1225 is capable of, configured to, or operable to support components for performing the following actions: transmitting control signaling via one or more of a set of multiple transmission opportunities within the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. Request component 1230 is capable of, configured to, or operable to support components for performing the following actions: receiving a message according to the on-demand transmission scheme, the message requesting the transmission of one or more instances of the first SSB. SSB component 1235 is capable of, configured to, or operable to support components for performing the following actions: transmitting the one or more instances of the first SSB within the UE's operating bandwidth based on the message via at least one of the set of multiple transmission opportunities.

[0203] Figure 13 A block diagram 1300 is shown of a communication manager 1320 supporting on-demand NCD SSB transmission according to one or more aspects of this disclosure. The communication manager 1320 may be an example of aspects of the communication manager 1120, communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of on-demand NCD SSB transmission as described herein. For example, the communication manager 1320 may include a control signal component 1325, a request component 1330, an SSB component 1335, a threshold component 1340, an instance component 1345, a capability component 1350, or any combination thereof. These components, or each of their 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), and such communication may include communication within 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.

[0204] Additionally or alternatively, the communication manager 1320 may support wireless communication according to the examples disclosed herein. The control signaling component 1325 is capable of, configured to, or operable to support components for performing the following actions: transmitting control signaling via one or more of a plurality of transmission opportunities within a set of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The request component 1330 is capable of, configured to, or operable to support components for performing the following actions: receiving a message based on the control signaling, the message requesting the transmission of one or more instances of the first SSB. The SSB component 1335 is capable of, configured to, or operable to support components for performing the following actions: transmitting the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0205] In some examples, in order to support the transmission of the control signaling, the threshold component 1340 is capable of, configured to, or able to operate to support components for performing the following actions: transmitting an indication of a number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB, wherein the first instance is transmitted at least the number of time slots after the message is received.

[0206] In some examples, in order to support receiving the message, instance component 1345 is able to be configured or operated to support components for performing the following actions: receiving an indication of the number of instances requested by the UE via the message, wherein the one or more instances of the first SSB include that number of instances based on the message.

[0207] In some examples, in order to support receiving the message, instance component 1345 can be, configured, or operated to support components for performing the following actions: receiving a selection request via the message, the selection request requesting a network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances based on the selection request.

[0208] In some examples, in order to support the sending of the control signaling, instance component 1345 is able to be configured or operated to support components for sending an instruction via the control signaling for the default number of instances of the first SSB.

[0209] In some examples, in order to support the transmission of one or more instances of the first SSB, instance component 1345 is capable of, configured to, or able to operate to support components for performing the following actions: transmitting a set of multiple instances of the first SSB via a first set of multiple transmission opportunities based on the default number of instances associated with the semi-persistent transmission mode, wherein the control signaling indicates that the default number of instances is associated with the semi-persistent transmission mode.

[0210] In some examples, capability component 1350 is capable of, configured to, or able to operate to support components for performing the following actions: receiving a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein the control signaling is sent based on the capability message.

[0211] In some examples, SSB component 1335 is capable of, configured to, or able to operate to support components for performing the following actions: periodically transmitting a second SSB associated with system information of the cell via a second frequency in the carrier bandwidth, the second frequency being outside the operating bandwidth of the UE.

[0212] In some examples, SSB component 1335 is capable of, configured to, or able to operate to support components for performing the following actions: after transmitting one or more instances of the first SSB, and periodically transmitting a second SSB associated with system information of the cell via a second frequency in the carrier bandwidth outside the operating bandwidth of the UE.

[0213] In some examples, in order to support the transmission of the control signaling, the SSB component 1335 is capable of, configured to, or able to operate to support components for performing the following actions: transmitting instructions via the control signaling for: the frequency associated with the first SSB, the periodicity associated with the first SSB, the time offset associated with the first SSB, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

[0214] In some examples, SSB component 1335 is capable of, configured to, or able to operate to support components for performing the following action: preventing the first SSB from being sent before receiving the message based on the control signaling of the on-demand sending scheme configured for the first SSB.

[0215] In some examples, the LCID of the message indicates a request for transmission of one or more instances of the first SSB. In some examples, the control signaling includes RRC signaling, and the message includes MAC-CE. In some examples, the first SSB differs from the second SSB associated with the cell's system information; the first SSB includes a non-cell-defined SSB, and the second SSB includes a cell-defined SSB.

[0216] Figure 14 A diagram of a system 1400 including device 1405 supporting on-demand NCD SSB transmission, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components that support output and enable communication, such as a communication manager 1420, a transceiver 1410, an antenna 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1440).

[0217] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0218] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by one or more of at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by a processor in at least one processor 1435, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may also include a BIOS, among other things, that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 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).

[0219] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks supporting on-demand NCD SSB transmission). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more of the at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 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 (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 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 1435 may be a component of a processing system, which can refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1435) and memory circuitry (which may include at least one memory 1425) that receives or receives input and processes that input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1435 or a processing system including at least one processor 1435 may be configured, configured to, or operated to cause the device 1405 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 1425 or otherwise.

[0220] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 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 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

[0221] In some examples, the communication manager 1420 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 1420 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1420 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1420 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0222] Additionally or alternatively, the communication manager 1420 may support wireless communications according to examples disclosed herein. For example, the communication manager 1420 may be capable of, configured to, or operated to support components for performing the following actions: transmitting control signaling via one or more of a plurality of transmission opportunities within a set of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The communication manager 1420 may be capable of, configured to, or operated to support components for performing the following actions: receiving a message based on the control signaling, the message requesting the transmission of one or more instances of the first SSB. The communication manager 1420 may be capable of, configured to, or operated to support components for performing the following actions: transmitting the one or more instances of the first SSB within the UE's operating bandwidth via at least one of the plurality of transmission opportunities based on the message.

[0223] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, and improving processing power utilization, etc.

[0224] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by at least one processor 1435 to cause the device 1405 to perform various aspects of on-demand NCD SSB transmission as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0225] Figure 15 A flowchart illustrating a method 1500 for supporting on-demand NCD SSB transmission according to aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be implemented by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0226] At 1505, the method may include receiving control signaling via one or more of a plurality of transmission opportunities in a set of multiple transmission opportunities through the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of the cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference]. Figure 9 The control signal component 925 described herein is used to execute this.

[0227] At 1510, the method may include sending a message according to the on-demand sending scheme, the message requesting sending from one or more instances of the first SSB. The operation of block 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 9 The requested component 930 is used to execute the request.

[0228] At 1515, the method may include receiving one or more instances of the first SSB in the UE's operating bandwidth based on the message via at least one of the multiple transmission opportunities in the set. The operation of block 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to... Figure 9 The SSB component 935 described is used to perform this.

[0229] Figure 16 A flowchart illustrating method 1600 for supporting on-demand NCD SSB transmission according to aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be implemented by, as referenced... Figures 1 to 10 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0230] At 1605, the method may include sending a capability message indicating that the UE supports the capability of on-demand SSB communication. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 9 The described capability component 950 is used to perform this.

[0231] At 1610, the method may include receiving control signaling based on the capability message via one or more of a plurality of transmission opportunities in a set of multiple transmission opportunities of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of the cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth. Operation of block 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 9 The described control signal component 925 is executed.

[0232] At 1615, the method may include sending a message according to the on-demand sending scheme, the message requesting sending from one or more instances of the first SSB. The operation of block 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 9The requested component 930 is used to execute the request.

[0233] At 1620, the method may include receiving one or more instances of the first SSB in the UE's operating bandwidth based on the message via at least one of the multiple transmission opportunities in the set. Operation of block 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 9 The SSB component 935 described is used to perform this.

[0234] Figure 17 A flowchart illustrating method 1700 for supporting on-demand NCD SSB transmission according to aspects of this disclosure is shown. Operation of method 1700 can be implemented by a network entity or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this 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. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0235] At 1705, the method may include transmitting control signaling via one or more of a plurality of transmission opportunities in a set of operating bandwidths of the UE, the control signaling configuring an on-demand transmission scheme for a first SSB of the cell, wherein the cell is associated with a carrier bandwidth including the operating bandwidth of the UE. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to [reference needed]. Figure 13 The described control signal component 1325 is executed.

[0236] At 1710, the method may include receiving a message according to the on-demand sending scheme, the message requesting sending from one or more instances of the first SSB. The operation of block 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to [reference needed]. Figure 13 The requested component 1330 is used to execute the request.

[0237] At 1715, the method may include transmitting one or more instances of the first SSB in the operating bandwidth of the UE based on the message via at least one of the multiple transmission opportunities in the set. The operation of block 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 13 The described SSB component 1335 is used to perform this.

[0238] Figure 18A flowchart illustrating method 1800 for supporting on-demand NCD SSB transmission according to aspects of this disclosure is shown. Operation of method 1800 can be implemented by a network entity or its components as described herein. For example, operation of method 1800 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The network entity described is used to perform this 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. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0239] At 1805, the method may include transmitting control signaling via one or more of a plurality of transmission opportunities in a set of operating bandwidths of the UE, the control signaling configuring an on-demand transmission scheme for a first SSB of the cell, wherein the cell is associated with a carrier bandwidth including the operating bandwidth of the UE. The operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The described control signal component 1325 is executed.

[0240] At 1810, the method may include sending an indication of a time slot for a threshold number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB. The operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be provided by reference to [reference needed]. Figure 13 The threshold component 1340 described is used for execution.

[0241] At 1815, the method may include receiving a message according to the on-demand sending scheme, the message requesting sending from one or more instances of the first SSB. The operation of block 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 13 The requested component 1330 is used to execute the request.

[0242] At 1820, the method may include transmitting one or more instances of the first SSB in the operating bandwidth of the UE based on the message via at least one of the multiple transmission opportunities in the set, wherein the first instance is transmitted in at least a threshold number of time slots after receiving the message. The operation of block 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1820 may be as described in the references... Figure 13 The described SSB component 1335 is used to perform this.

[0243] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving control signaling via one or more of a plurality of transmission opportunities of the UE's operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the UE's operating bandwidth; transmitting a message at least in part based on the control signaling, the message requesting transmission of one or more instances of the first SSB; and receiving, at least in part based on the message, the one or more instances of the first SSB in the UE's operating bandwidth via at least one of the plurality of transmission opportunities.

[0244] Aspect 2: According to the method of aspect 1, receiving the control signaling includes: receiving an indication of the number of time slots via the control signaling, the time slots being between the message and a first instance of one or more instances of the first SSB, wherein the first instance is received at least the number of time slots after the message is sent.

[0245] Aspect 3: The method according to any one of Aspects 1 to 2, wherein sending the message comprises: sending via the message an indication of the number of instances requested by the UE, wherein the one or more instances of the first SSB include the number of instances at least in part based on the message.

[0246] Aspect 4: The method according to any one of Aspects 1 to 2, wherein sending the message includes: sending a selection request via the message, the selection request requesting a network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances at least in part based on the selection request.

[0247] Aspect 5: According to the method of aspect 4, receiving the control signaling includes: receiving an indication of the default number of instances of the first SSB via the control signaling.

[0248] Aspect 6: According to the method of aspect 4, receiving the one or more instances of the first SSB includes: receiving multiple instances of the first SSB via a first set of transmission opportunities, at least in part based on the default number of instances associated with a semi-persistent transmission mode; monitoring a second set of one or more transmission opportunities among the multiple transmission opportunities; and after monitoring the second set of one or more transmission opportunities that exclude a threshold number of the first SSB, switching to periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE.

[0249] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: sending a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein receiving the control signaling is at least partially based on the capability message.

[0250] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE, wherein the transmission of the message is based at least in part on a change in one or more conditions associated with the second SSB.

[0251] Aspect 9: According to the method of aspect 8, the change of said one or more conditions includes timing drift of the beam associated with the second SSB, or beam-to-link change, or both.

[0252] Aspect 10: The method according to any one of Aspects 8 to 9, the method further comprising: evaluating one or more communication metrics during a first time period based at least in part on monitoring the second frequency for the second SSB; and evaluating the one or more communication metrics during a second time period based at least in part on the one or more instances of receiving the first SSB, wherein the second time period is longer than the first time period.

[0253] Aspect 11: The method according to any one of aspects 1 to 10, the method further comprising: after receiving the one or more instances of the first SSB, periodically monitoring a second frequency in the carrier bandwidth for a second SSB associated with system information of the cell, the second frequency being outside the operating bandwidth of the UE.

[0254] Aspect 12: The method according to any one of Aspects 1 to 11, wherein receiving the control signaling comprises: receiving via the control signaling an indication of: a frequency associated with the first SSB, a periodicity associated with the first SSB, a time offset associated with the first SSB, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

[0255] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the logical channel identifier of the message indicates a request for transmission of the one or more instances of the first SSB.

[0256] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the control signaling includes RRC signaling and the message includes MAC-CE.

[0257] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the first SSB is different from the second SSB associated with the system information of the cell, the first SSB including NCD-SSB and the second SSB including CD-SSB.

[0258] Aspect 16: A method for wireless communication at a network entity, the method comprising: transmitting control signaling via one or more of a plurality of transmission opportunities of an operating bandwidth of a UE, the control signaling configuring an on-demand transmission scheme for a first SSB of a cell, wherein the cell is associated with a carrier bandwidth including the operating bandwidth of the UE; receiving a message at least in part based on the control signaling, the message requesting transmission of one or more instances of the first SSB; and transmitting the one or more instances of the first SSB in the operating bandwidth of the UE at least in part based on the message via at least one of the plurality of transmission opportunities.

[0259] Aspect 17: According to the method of aspect 16, sending the control signaling includes: sending an indication of a threshold number of time slots via the control signaling, the time slots being between the message and a first instance of the one or more instances of the first SSB, wherein the first instance is sent at least a threshold number of time slots after receiving the message.

[0260] Aspect 18: The method according to any one of Aspects 16 to 17, wherein receiving the message comprises: receiving via the message an indication of the number of instances requested by the UE, wherein the one or more instances of the first SSB include the number of instances at least in part based on the message.

[0261] Aspect 19: The method according to any one of Aspects 16 to 17, wherein receiving the message comprises: receiving a selection request via the message, the selection request requesting the network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances at least in part based on the selection request.

[0262] Aspect 20: The method according to aspect 19, wherein sending the control signaling includes: sending an indication of the default number of instances of the first SSB via the control signaling.

[0263] Aspect 21: According to the method of aspect 19, wherein sending the one or more instances of the first SSB comprises: sending multiple instances of the first SSB via a first set of transmission opportunities from the multiple transmission opportunities, based at least in part on the default number of instances associated with a semi-persistent transmission mode, wherein the control signaling indicates that the default number of instances is associated with the semi-persistent transmission mode.

[0264] Aspect 22: The method according to any one of Aspects 16 to 21, the method further comprising: receiving a capability message indicating that the UE supports the capability of on-demand SSB communication, wherein the control signaling is transmitted at least in part based on the capability message.

[0265] Aspect 23: The method according to any one of aspects 16 to 22, the method further comprising: periodically transmitting a second SSB associated with system information of the cell via a second frequency in the carrier bandwidth, the second frequency being outside the operating bandwidth of the UE.

[0266] Aspect 24: The method according to any one of aspects 16 to 23, the method further comprising: after transmitting the one or more instances of the first SSB and periodically transmitting a second SSB associated with system information of the cell via a second frequency in the carrier bandwidth, the second frequency being outside the operating bandwidth of the UE.

[0267] Aspect 25: The method according to any one of Aspects 16 to 24, wherein sending the control signaling comprises: sending via the control signaling an indication of: a frequency associated with the first SSB, a periodicity associated with the first SSB, a time offset associated with the first SSB, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

[0268] Aspect 26: The method according to any one of aspects 16 to 25, wherein the logical channel identifier of the message indicates a request for transmission of the one or more instances of the first SSB.

[0269] Aspect 27: The method according to any one of Aspects 16 to 26, wherein the control signaling includes RRC signaling and the message includes MAC-CE.

[0270] Aspect 28: The method according to any one of Aspects 16 to 27, wherein the first SSB is different from the second SSB associated with the system information of the cell, the first SSB including a non-cell-defined SSB and the second SSB including a cell-defined SSB.

[0271] Aspect 29: The method according to any one of Aspects 16 to 28, the method further comprising: avoiding sending the first SSB before receiving the message based at least in part on the control signaling configured for the on-demand sending scheme for the first SSB.

[0272] Aspect 30: 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, thereby enabling the UE to perform a method according to any one of aspects 1 to 15.

[0273] Aspect 31: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 15.

[0274] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0275] Aspect 33: 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, thereby enabling the network entity to perform a method according to any one of aspects 16 to 29.

[0276] Aspect 34: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 16 to 29.

[0277] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 16 to 29.

[0278] It should be noted that the methods described herein describe possible specific implementations, and the 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.

[0279] 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.

[0280] The information and signals described herein can be represented using any of a variety of different techniques and methods. 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.

[0281] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, 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 cooperating 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 functions or operations individually or jointly.

[0282] 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.

[0283] 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.

[0284] 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".

[0285] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can 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".

[0286] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. 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, building, and other similar actions.

[0287] 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 reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0288] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all implementable or 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 instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0289] 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: Control signaling is received via one or more of a plurality of transmission opportunities of the UE’s operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first synchronization signal block of a cell, wherein the cell is associated with a carrier bandwidth including the UE’s operating bandwidth; A message is sent according to the on-demand sending scheme, the message requesting the sending of one or more instances of the first synchronization signal block; as well as The message is received, at least in part, via at least one of the plurality of transmission opportunities in the operating bandwidth of the UE in one or more instances of the first synchronization signal block.

2. The UE according to claim 1, wherein, In order to receive the control signaling, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The control signaling receives an indication of the number of time slots between the message and a first instance of one or more instances of the first synchronization signal block, wherein the first instance is received at least the number of time slots after the message is sent.

3. The UE according to claim 1, wherein, In order to send the message, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The message sends an indication of the number of instances requested by the UE, wherein the one or more instances of the first synchronization signal block include the number of instances at least in part based on the message.

4. The UE according to claim 1, wherein, In order to send the message, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: A selection request is sent via the message, which requests the network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances at least in part based on the selection request.

5. The UE according to claim 4, wherein, In order to receive the control signaling, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The control signaling receives an indication of the default number of instances of the first synchronization signal block.

6. The UE according to claim 4, wherein, In order to receive the one or more instances of the first synchronization signal block, the one or more processors can operate individually or jointly to execute the code to enable the UE to: Multiple instances of the first synchronization signal block are received via a first set of transmission opportunities, at least in part based on the default number of instances associated with the semi-persistent transmission mode; Monitor one or more of the second group of the plurality of transmission opportunities; as well as After monitoring one or more of the second group of transmission opportunities that exclude a threshold number of the first synchronization signal blocks, the process switches to periodically monitoring a second frequency in the carrier bandwidth for a second synchronization signal block associated with the system information of the cell, the second frequency being outside the operating bandwidth of the UE.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the UE to: Send a capability message indicating that the UE supports the capability of on-demand synchronization signal block communication, wherein the control signaling is received at least in part based on the capability message.

8. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the UE to: A second frequency in the carrier bandwidth is periodically monitored for a second synchronization signal block associated with the system information of the cell, the second frequency being outside the operating bandwidth of the UE, wherein the transmission of the message is based at least in part on a change in one or more conditions associated with the second synchronization signal block.

9. The UE of claim 8, wherein the change of one or more conditions includes timing drift of the beam associated with the second synchronization signal block, or beam-to-link change, or both.

10. The UE of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the UE to: At least in part, one or more communication metrics are evaluated during a first time period based on monitoring the second frequency for the second synchronization signal block; and The one or more communication metrics are evaluated during a second time period, which is longer than the first time period, based at least in part on the one or more instances of receiving the first synchronization signal block.

11. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the UE to: After receiving one or more instances of the first synchronization signal block, a second frequency in the carrier bandwidth is periodically monitored for a second synchronization signal block associated with the system information of the cell, the second frequency being outside the operating bandwidth of the UE.

12. The UE according to claim 1, wherein, In order to receive the control signaling, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The control signaling receives an indication of the following: the frequency associated with the first synchronization signal block, the periodicity associated with the first synchronization signal block, the time offset associated with the first synchronization signal block, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

13. The UE of claim 1, wherein the logical channel identifier of the message indicates a request for transmission of the one or more instances of the first synchronization signal block.

14. The UE of claim 1, wherein the control signaling includes radio resource control signaling, and the message includes a media access control element.

15. The UE of claim 1, wherein the first synchronization signal block is different from the second synchronization signal block associated with the system information of the cell, the first synchronization signal block including a non-cell-defined synchronization signal block and the second synchronization block including a cell-defined synchronization signal block.

16. A network entity, the network entity 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 network entity: Control signaling is transmitted via one or more of a plurality of transmission opportunities of the user equipment (UE) operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first synchronization signal block of a cell, wherein the cell is associated with a carrier bandwidth including the operating bandwidth of the UE; Messages are received according to the on-demand sending scheme, wherein the messages request the sending of one or more instances of the first synchronization signal block; as well as The message is received, at least in part, via at least one of the plurality of transmission opportunities in the operating bandwidth of the UE in one or more instances of the first synchronization signal block.

17. The network entity according to claim 16, wherein, In order to send the control signaling, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The control signaling sends an indication of a threshold number of time slots between the message and a first instance of one or more instances of the first synchronization signal block, wherein the first instance is sent at least a threshold number of time slots after the message is received.

18. The network entity according to claim 16, wherein, In order to receive the message, the one or more processors can operate individually or jointly to execute the code, thereby enabling the network entity to: The message receives an indication of the number of instances requested by the UE, wherein the one or more instances of the first synchronization signal block include the number of instances at least in part based on the message.

19. The network entity according to claim 16, wherein, In order to receive the message, the one or more processors can operate individually or jointly to execute the code, thereby enabling the network entity to: The network entity receives a selection request via the message, the selection request requesting the network entity to select a default number of the one or more instances, wherein the one or more instances include the default number of instances at least in part based on the selection request.

20. The network entity according to claim 19, wherein, In order to send the control signaling, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The control signaling sends an indication of the default number of instances of the first synchronization signal block.

21. The network entity according to claim 19, wherein, In order to send the one or more instances of the first synchronization signal block, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: Multiple instances of the first synchronization signal block are transmitted via a first set of transmission opportunities from the multiple transmission opportunities, based at least in part on the default number of instances associated with the semi-persistent transmission mode, wherein the control signaling indicates that the default number of instances are associated with the semi-persistent transmission mode.

22. The network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code thereby enabling the network entity to: The UE receives a capability message indicating its ability to support on-demand synchronization signal block communication, wherein the control signaling is transmitted based at least in part on the capability message.

23. The network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the network entity to: A second synchronization signal block associated with the system information of the cell is periodically transmitted via a second frequency in the carrier bandwidth, the second frequency being outside the operating bandwidth of the UE.

24. The network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the network entity to: After transmitting one or more instances of the first synchronization signal block, a second synchronization signal block associated with the system information of the cell is periodically transmitted via a second frequency in the carrier bandwidth, the second frequency being outside the operating bandwidth of the UE.

25. The network entity according to claim 16, wherein, In order to send the control signaling, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: Instructions are sent via the control signaling for the following: the frequency associated with the first synchronization signal block, the periodicity associated with the first synchronization signal block, the time offset associated with the first synchronization signal block, or any combination thereof, wherein the frequency is within the operating bandwidth of the UE.

26. The network entity of claim 16, wherein the one or more processors are further capable of operating individually or jointly to execute the code, thereby enabling the network entity to: Avoid sending the first synchronization block before receiving the message based at least in part on the control signaling that enables the on-demand sending scheme for the first synchronization block.

27. A method for conducting wireless communication at a user equipment (UE), the method comprising: Control signaling is received via one or more of a plurality of transmission opportunities of the UE’s operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first synchronization signal block of a cell, wherein the cell is associated with a carrier bandwidth including the UE’s operating bandwidth; A message is sent according to the on-demand sending scheme, the message requesting the sending of one or more instances of the first synchronization signal block; as well as The message is received, at least in part, via at least one of the plurality of transmission opportunities in the operating bandwidth of the UE in one or more instances of the first synchronization signal block.

28. The method of claim 27, wherein receiving the control signaling comprises: The control signaling receives an indication of the number of time slots between the message and a first instance of one or more instances of the first synchronization signal block, wherein the first instance is received at least the number of time slots after the message is sent.

29. A method for conducting wireless communication at a network entity, the method comprising: Control signaling is transmitted via one or more of a plurality of transmission opportunities of the user equipment (UE) operating bandwidth, the control signaling configuring an on-demand transmission scheme for a first synchronization signal block of a cell, wherein the cell is associated with a carrier bandwidth including the operating bandwidth of the UE; Messages are received according to the on-demand sending scheme, wherein the messages request the sending of one or more instances of the first synchronization signal block; as well as The message is received, at least in part, via at least one of the plurality of transmission opportunities in the operating bandwidth of the UE in one or more instances of the first synchronization signal block.

30. The method of claim 29, wherein sending the control signaling comprises: The control signaling sends an indication of a threshold number of time slots between the message and a first instance of one or more instances of the first synchronization signal block, wherein the first instance is sent at least a threshold number of time slots after the message is received.

Images