Random access channel opportunity configuration for on-demand synchronization signal blocks

Abstract

Methods, systems, and devices for wireless communication are described. In order to save energy at a network, synchronization signal blocks (SSBs) may be transmitted in an on-demand manner. For example, the network may transmit an SSB in response to a request for the SSB or an uplink wake-up signal (WUS) from a user equipment (UE). The SSBs may be mapped to corresponding random access channel opportunities (ROs) via control signaling such as radio resource control or system information. For example, the described techniques provide rules and / or signaling that may indicate whether a network entity should monitor in an RO corresponding to an on-demand SSB, and thus indicate whether a UE may transmit in the RO. In some examples, a UE may send a request for an on-demand SSB, receive the SSB based on the request, and selectively send a message to a network entity in an RO corresponding to the SSB based on the reception of the SSB.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 481,970, filed October 5, 2023, entitled “RANDOM ACCESSCHANNEL OCCASION CONFIGURATION FOR ON-DEMAND SYNCHRONIZATION SIGNAL BLOCKS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communication, including the random access channel timing configuration for on-demand synchronization of signal blocks. 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). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for configuring Random Access Channel (RACH) timing (RO) for on-demand synchronization signal blocks (SSBs). For example, the described technology provides rules and / or signaling that can instruct network entities whether they should monitor in the RO corresponding to the on-demand SSB, and therefore whether user equipment (UE) can transmit in the RO corresponding to the on-demand SSB. In some examples, SSBs can be transmitted on demand to save energy at the network. For example, the network can transmit an SSB in response to a request from the UE for an SSB or an uplink wake-up signal (WUS). The SSB can be mapped to the corresponding RO via control signaling such as Radio Resource Control (RRC) or System Information (SI). In some examples, the UE can send a request for an on-demand SSB, receive the SSB based on the request, and selectively transmit messages to network entities in the RO corresponding to the SSB based on the SSB reception. In some examples, the UE can be allowed to transmit messages in the RO even if no SSB corresponding to the RO is transmitted. In some examples, if an SSB corresponding to an RO is sent, the UE can be allowed to transmit within the RO. In some examples, a separate mapping can be provided between on-demand SSBs and ROs and legacy SSBs (e.g., periodically scheduled unrequested or unprompted SSBs) and ROs. In some examples, network entities can dynamically indicate the corresponding RO for a requested SSB in response to a request for an SSB (e.g., via downlink control information (DCI)).

[0006] A method for wireless communication by a user equipment (UE) is described. The method may include sending a request for a Service Serving SSB to a network entity; receiving the SSB from the network entity and in response to the request; and selectively sending messages in an Operational Route (RO) to the network entity based on the receipt of the SSB, wherein the RO is associated with the SSB.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute code to cause the UE to send a request for an SSB to a network entity; receive an SSB from the network entity and in response to the request; and selectively send messages to the network entity and, based on the receipt of the SSB, in ROs, wherein the RO is associated with the SSB.

[0008] Another UE for wireless communication is described. This UE may include components for sending a request for an SSB to a network entity; components for receiving an SSB from the network entity and in response to the request; and components for selectively sending messages in ROs to the network entity and based on the receipt of the SSB, wherein the RO is associated with the SSB.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send a request for an SSB to a network entity; receive an SSB from the network entity and in response to the request; and selectively send messages to the network entity and, based on the receipt of the SSB, in ROs, wherein the ROs are associated with the SSB.

[0010] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving control signaling from a network entity indicating a first mapping between a first set of SSBs and a first set of ROs, wherein the first set of SSBs includes SSBs, the first set of ROs includes ROs, and the first mapping indicates that an RO may be associated with an SSB.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, based on the determination that a second SSB in the first SSB set has not been received, the transmission of a second message in a second RO associated with the second SSB in the first RO set is selectively suppressed, wherein a first mapping indicates that the second RO can be associated with the SSB.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a second message is selectively sent in a second RO of a first RO set associated with a second SSB that has not been received in the first SSB set, based on control signaling indicating that the first SSB set may be an on-demand SSB, wherein a first mapping indicates that the second RO may be associated with an SSB.

[0013] The methods described herein, examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for receiving an indication of a second mapping between a second SSB set and a second RO set using control signaling, wherein the control signaling indicates that the first SSB set may be on-demand SSBs, and wherein the control signaling indicates that the second SSB set may be unrequested.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first maximum duration between any SSB in the first SSB set according to the first mapping and an associated RO in the first RO set may be less than the second maximum duration between any SSB in the second SSB set according to the second mapping and an associated RO in the second RO set.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for receiving control signaling via RRC messages when in RRC connection mode with a network entity.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for receiving control signaling via the SI.

[0017] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving control signaling from a network entity in response to a request, indicating an RO associated with an SSB.

[0018] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving an indication of a set of preambles associated with an RO using control signaling, wherein sending a message includes sending a preamble from the set of preambles.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for receiving DCI via a downlink control channel associated with the SSB.

[0020] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving DCI via downlink control channel monitoring timing associated with scheduling downlink shared channel transmission from network entities.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the request may include operations, features, components, or instructions for sending an uplink WUS to a network entity.

[0022] A method for wireless communication by a network entity is described. The method may include receiving a request for an SSB from a UE; transmitting an SSB to and in response to the request to the UE; and selectively monitoring messages from the UE in an RO based on the SSB transmission, wherein the RO is associated with the SSB.

[0023] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively operable to execute code to enable the network entity to: receive a request for an SSB from a UE; transmit an SSB to and in response to the UE; and selectively monitor messages from the UE in an RO based on the SSB transmission, wherein the RO is associated with the SSB.

[0024] Another network entity for wireless communication is described. This network entity may include components for receiving a request for an SSB from a UE; components for transmitting an SSB to and in response to the UE; and components for selectively monitoring messages from the UE in an RO based on the transmission of the SSB, wherein the RO is associated with the SSB.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to perform the following operations: receiving a request for an SSB from a UE; transmitting an SSB to and in response to the UE; and selectively monitoring messages from the UE in an RO based on the SSB transmission, wherein the RO is associated with the SSB.

[0026] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to a UE indicating a first mapping between a first set of SSBs and a first set of ROs, wherein the first set of SSBs includes SSBs, the first set of ROs includes ROs, and the first mapping indicates that ROs may be associated with SSBs.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, based on the suppression of transmission of a second SSB in a first SSB set, monitoring of a second message from the UE in a second RO associated with the second SSB in a first RO set is selectively suppressed, wherein a first mapping indicates that the second RO can be associated with an SSB.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second message is selectively monitored in a second RO of a first RO set associated with an unsent second SSB in the first SSB set, based on control signaling indicating that the first SSB set may be an on-demand SSB, wherein a first mapping indicates that the second RO may be associated with an SSB.

[0029] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: using control signaling to send an indication of a second mapping between a second SSB set and a second RO set, wherein the control signaling indicates that the first SSB set may be on-demand SSBs, and wherein the control signaling indicates that the second SSB set may be unrequested.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first maximum duration between any SSB in the first SSB set according to the first mapping and the associated RO in the first RO set may be less than the second maximum duration between any SSB in the second SSB set according to the second mapping and the associated RO in the second RO set.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending control signaling may include operations, features, components, or instructions for sending control signaling via RRC messages when in RRC connection mode with a network entity.

[0032] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending control signaling may include operations, features, components, or instructions for sending control signaling via SI.

[0033] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to the UE in response to a request, indicating the RO associated with the SSB.

[0034] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting instructions on a set of preambles associated with an RO using control signaling, wherein a receive message includes receiving a preamble from the set of preambles.

[0035] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending control signaling may include operations, features, components, or instructions for sending DCI via a downlink control channel associated with the SSB at a monitored timing.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, transmitting control signaling may include operations, features, components, or instructions for transmitting DCI via downlink control channel monitoring timing associated with scheduling downlink shared channel transmission.

[0037] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, receiving the request may include operations, features, components, or instructions for receiving uplink WUS from the UE. Attached Figure Description

[0038] Figure 1 An example of a wireless communication system supporting random access channel (RACH) timing (RO) configuration for on-demand synchronization signal blocks (SSBs) is shown, according to one or more aspects of this disclosure.

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

[0040] Figure 3 An example of a resource graph supporting RO configuration for on-demand SSB is shown, according to one or more aspects of this disclosure.

[0041] Figure 4 An example of a resource graph supporting RO configuration for on-demand SSB is shown, according to one or more aspects of this disclosure.

[0042] Figure 5 An example of a resource graph supporting RO configuration for on-demand SSB is shown, according to one or more aspects of this disclosure.

[0043] Figure 6 An example of a process flow supporting RO configuration for on-demand SSB is shown, according to one or more aspects of this disclosure.

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

[0045] Figure 9 A block diagram is shown of a communication manager that supports RO configuration for on-demand SSB, according to one or more aspects of this disclosure.

[0046] Figure 10 A diagram of a system including an RO configuration supporting on-demand SSB is shown, according to one or more aspects of this disclosure.

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

[0048] Figure 13 A block diagram is shown of a communication manager that supports RO configuration for on-demand SSB, according to one or more aspects of this disclosure.

[0049] Figure 14 A diagram of a system including an RO configuration supporting on-demand SSB is shown, according to one or more aspects of this disclosure.

[0050] Figure 15 and Figure 16 A flowchart illustrating a method for supporting RO configuration for on-demand SSB according to one or more aspects of this disclosure is shown. Detailed Implementation

[0051] In wireless communication systems, network entities can transmit synchronization signal blocks (SSBs) for purposes such as clock synchronization and beam management. For example, a wireless communication system can support beamforming processes between a network entity and a user equipment (UE). In some examples of beamforming processes, a network entity can transmit multiple SSBs in the direction of the UE on multiple beams to form directional transmission to the UE. The network entity can periodically transmit sets of SSBs. For example, four SSBs occupying four symbols (e.g., time resources) can be transmitted every 20 milliseconds (ms) on each beam (e.g., 64 beam directions).

[0052] Because SSBs are sent periodically, they can be a significant contributor to network energy consumption. In some examples, to conserve energy at the network, SSBs can be sent on demand. For instance, the network can send an SSB in response to a request from a UE for an SSB or an uplink wake-up signal (WUS). SSBs can be mapped to corresponding random access channel (RACH) timings via System Information (SI) (e.g., in a System Information Block (SIB)) or Radio Resource Control (RRC) signaling. For example, based on measurements of received SSBs that meet a threshold, the UE can send a RACH preamble in the corresponding RACH timing (RO). ROs can be used to send initial access messages, SI requests, or scheduling requests. Currently, there are no rules defining whether network entities should monitor ROs corresponding to on-demand SSBs that the network has not sent.

[0053] Various aspects of this disclosure can define whether a network entity should monitor in a RO corresponding to an on-demand SSB, and thus define whether a UE can transmit in that RO. For example, a UE can send a request for an on-demand SSB, receive the SSB based on the request, and selectively send messages to the network entity in the RO corresponding to the SSB based on the reception of the SSB. The network entity can monitor the RO accordingly based on sending the on-demand SSB corresponding to the RO. In some examples, the UE may be allowed to send messages in the RO even if no SSB corresponding to the RO is sent. In some examples, the UE may be allowed to transmit in the RO if the SSB corresponding to the RO is sent. In some examples, a separate mapping may be provided between on-demand SSBs and ROs and legacy SSBs (e.g., periodically scheduled unrequested or unhinted SSBs) and ROs. In some examples, the network entity may dynamically indicate the corresponding RO for a requested SSB in response to a request for the SSB (e.g., via downlink control information (DCI)).

[0054] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described by way of resource diagrams, process flow diagrams, apparatus diagrams, system diagrams, and flowcharts relating to RO configurations for on-demand SSBs.

[0055] Figure 1An example of a wireless communication system 100 supporting RO configuration for on-demand SSBs is shown, according to one or more aspects of this disclosure. 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.

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

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

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

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

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

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

[0062] 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., RRC, Service 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0094] In some examples, network entity 105 may transmit SSBs for purposes such as clock synchronization and beam management. For example, network entity 105 and UE 115 may use SSBs to perform beamforming procedures. In some examples of beamforming procedures, network entity 105 may transmit multiple SSBs in the direction of UE 115 on multiple beams to form directional transmission to UE 115. Network entity 105 may transmit SSB sets periodically. For example, four SSBs occupying four symbols (e.g., time resources) may be transmitted every 20 ms on each beam (e.g., 64 beam directions).

[0095] Network energy consumption can result in high costs for operating cellular networks (e.g., 23% of total costs). A significant portion of network energy consumption (e.g., 50% in 5G NR) may be caused by the RAN. Network energy savings can be valuable for cellular network expansion. In some examples, network entity energy consumption models can be adapted, including relative energy consumption for downlink and uplink (considering factors such as power amplifier efficiency, number of transmit RUs, and network entity load, sleep states and associated transition times, as well as one or more reference parameters or configurations). In some examples, energy consumption model evaluation methods and key performance indicators (KPIs) can be defined. Such evaluation methods can be designed to assess system-level network energy consumption and energy saving gains, and can assess or balance the impact on network and user performance (e.g., spectral efficiency, capacity, user-perceived throughput, latency, handover performance, call drop rate, initial access performance, and service level agreement guarantee-related KPIs), energy efficiency, UE power consumption, and complexity. Evaluation methods may not focus on a single KPI and existing KPIs can be reused where applicable. New KPIs can be developed for various purposes. Some techniques for improving network energy conservation in the transmission and reception of network entity 105 may include more efficient dynamic or semi-static scheduling of transmission or reception, finer granularity of transmission or reception, and / or transmission or reception in one or more energy-saving techniques or modes in the time, frequency, spatial, or power domains. Some techniques for improving network energy conservation may involve support or feedback from UE 115 and potential UE assistance information. Some techniques for improving network energy conservation may involve information exchange or coordination between network entities 105 via network interfaces. Two techniques that can be employed to reduce network energy consumption may include: 1) dynamic adaptation in the spatial and power domains, and 2) discontinuous reception (DRX) and discontinuous transmission (DTX).

[0096] Since SSBs are sent periodically, they can be a significant contributor to network energy consumption. Therefore, network energy consumption can be reduced by implementing on-demand SSBs. By implementing on-demand SSBs, network entity 105 can conserve energy associated with SSB transmission when UE 115 does not require an SSB. As described herein, SSBs can be mapped to corresponding ROs. Therefore, in the absence of rules or signaling indicating whether UE 115 can transmit in an RO corresponding to an untransmitted SSB (e.g., since no UE 115 requests an SSB), it may be unclear whether UE 115 can transmit in an RO corresponding to an untransmitted SSB. Similarly, it may be unclear whether network entity 105 should monitor the RO for RACH messages from UE 115 in an RO corresponding to an untransmitted SSB.

[0097] Various aspects of this disclosure can define whether network entity 105 should monitor in the RO corresponding to the on-demand SSB, and thus define whether UE 115 can transmit in that RO. For example, UE 115 can send a request for an on-demand SSB, receive the SSB based on the request, and selectively send messages to the network entity in the RO corresponding to the SSB based on the reception of the SSB. Network entity 105 can monitor the RO accordingly based on sending the on-demand SSB corresponding to the RO. In some examples, UE 115 may be allowed to send messages in the RO even if no SSB corresponding to the RO is sent. In some examples, UE 115 may be allowed to transmit in the RO if an SSB corresponding to the RO is sent. In some examples, a separate mapping can be provided between on-demand SSBs and ROs and legacy SSBs (e.g., periodically scheduled unrequested or unhinted SSBs) and ROs. In some examples, the network entity may dynamically indicate the corresponding RO for a requested SSB in response to a request for an SSB (e.g., via DCI). The use of on-demand SSBs and the rules and / or signaling that indicate whether network entity 105 should monitor in the RO corresponding to the on-demand SSB, and thus indicate whether UE 115 can transmit in that RO, can: enable network entity 105 to sleep for a longer duration (e.g., by avoiding wake-ups to transmit unwanted SSBs); enable the network to provide low latency to UEs requesting ROs (e.g., by mapping ROs to desired SSBs); and enable network entity 105 to save energy by not transmitting unwanted SSBs and / or not monitoring in ROs where UE 115 is not expected to transmit RACH messages.

[0098] Figure 2 An example of a wireless communication system 200 supporting RO configuration for on-demand SSBs, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may include a network entity 105-a, which may be an example of network entity 105 as described herein.

[0099] UE 115-a can communicate with network entity 105-a using communication link 125-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a can include a bidirectional link that enables both uplink and downlink communication. For example, UE 115-a can use communication link 125-a to send uplink signals 205 (e.g., uplink transmissions), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a can use communication link 125-a to send downlink signals 210 (e.g., downlink transmissions), such as downlink control signals or downlink data signals, to UE 115-a.

[0100] Network entity 105-a can use beamforming technology to transmit downlink signal 210 to UE 115-a. For example, network entity 105-a can transmit downlink signal 210 via beam 215 (e.g., as shown in the image). Figure 2 Beams 215-a, 215-b, and 215-c (shown) transmit SSB 230. As described herein, network entity 105-a may transmit SSB 230 on demand in response to a request 225 from UE 115-a. For example, UE 115-a may send a request 225 for SSB 230 to network entity 105-a, for example, for beam management purposes or for clock synchronization purposes. In response to request 225, network entity 105-a may transmit SSB 230 (e.g., in the requested configured SSB resource). In some examples, network entity 105-a may send control signaling 220 to schedule SSB timings and ROs and map SSB timings to ROs. In such examples, request 225 may indicate the requested SSB timing. In some examples, based on the reception of SSB 230, UE 115-a can send RACH message 240 (e.g., RACH preamble or MsgA) in the RO mapped to SSB 230, and network entity 105-a can monitor the RO for RACH message 240 from UE 115 based on sending SSB 230 in response to request 225.

[0101] In some examples, UE 115-a may be allowed to send RACH message 240 in the RO corresponding to the unsent SSB 230, and correspondingly, network entity 105-a may monitor RACH messages in all ROs, regardless of whether network entity 105-a sent the corresponding SSB. For example, even if the corresponding SSB is not sent, UE 115-a may still send it in the RO to send a system information request or scheduling request to network entity 105-a.

[0102] In some examples, such as reference Figure 4 As described, control signaling 220 may indicate separate mappings between a first legacy SSB set (e.g., periodically scheduled unclaimed or unhinted SSBs) and a first RO set, as well as between on-demand SSBs and a second RO set. In some examples, network entity 105-a may monitor RACH messages 240 in each RO in the first RO set, and network entity 105-a may monitor RACH messages 240 in each RO in the second RO set corresponding to an on-demand SSB actually sent by network entity 105-a (e.g., and accordingly, UE 115-a may be allowed to send RACH messages in the second RO set corresponding to an on-demand SSB actually sent by network entity 105-a).

[0103] In some examples, such as reference Figure 5 As described, in response to the transmission of the on-demand SSB 230, network entity 105-a can dynamically indicate (e.g., in DCI 235) the uplink resources for the RO corresponding to the on-demand SSB.

[0104] Figure 3 An example of resource diagram 300 supporting RO configuration for on-demand SSB is shown according to one or more aspects of this disclosure. Resource diagram 300 may implement aspects of wireless communication system 100 or wireless communication system 200, or may be implemented by these aspects.

[0105] In some examples, network entity 105 can be configured (e.g., via RRC or SI) to associate or map on demand SSB 305 (e.g., first SSB 305-a, second SSB 305-b, third SSB 305-c, and fourth SSB 305-d) with corresponding ROs (e.g., first RO 310-a, second RO 310-b, third RO 310-c, and fourth RO 310-d). For example, first SSB 305-a can be mapped to first RO 310-a, second SSB 305-b can be mapped to second RO 310-b, third SSB 305-c can be mapped to third RO 310-c, and fourth SSB 305-d can be mapped to fourth RO 310-d.

[0106] In some examples, network entity 105 can be configured to always monitor whether the corresponding on-demand SSB 305 has been sent in RO 310. Similarly, UE 115 can be allowed to send in each RO 310 regardless of whether the corresponding on-demand SSB 305 has been received. For example, if network entity 105 does not send the third SSB 305-c and the fourth SSB 305-d because network entity 105 has not received requests for the third SSB 305-c and the fourth SSB 305-d, network entity 105 can still monitor the corresponding third RO 310-c and the corresponding fourth RO 310-d for uplink messages from UE 115. Similarly, even if UE 115 has not received the third SSB 305-c or the fourth SSB 305-d, UE 115 can still be allowed to send in the third RO 310-c and the fourth RO 310-d.

[0107] In some examples, network entity 105 can be configured to monitor only in the RO corresponding to the sent on-demand SSB 305. Similarly, UE 115 can be allowed to send uplink messages only in the RO corresponding to the received on-demand SSB 305. For example, if network entity 105 responds to a request from UE 115 to send a first SSB 305-a and a second SSB 305-b, then network entity 105 can monitor uplink transmissions from UE 115 in the corresponding first RO 310-a and the corresponding second RO 310-b. If network entity 105 does not send the third SSB 305-c and the fourth SSB 305-d because network entity 105 has not received a request for the third SSB 305-c and the fourth SSB 305-d, then network entity 105 may suppress the monitoring of the corresponding third RO 310-c and the corresponding fourth RO 310-d for uplink messages from UE 115, and UE 115 may suppress the transmission in the corresponding third RO 310-c and the corresponding fourth RO 310-d.

[0108] Figure 4 Examples of resource diagrams 400 and 415 supporting RO configuration for on-demand SSB according to one or more aspects of this disclosure are shown. Resource diagrams 400 and 415 may implement, or may be implemented by, aspects of wireless communication system 100 or wireless communication system 200.

[0109] In some examples, as shown in resource diagram 400, network entity 105 may configure (e.g., via RRC or SI) an association or mapping between legacy SSB 405 (e.g., periodically scheduled unclaimed or unhinted SSBs, including first SSB 405-a, second SSB 405-b, third SSB 405-c, and fourth SSB 405-d) and a first corresponding RO set (e.g., first RO 410-a, second RO 410-b, third RO 410-c, and fourth RO 410-d). In some examples, as shown in resource diagram 415, network entity 105 can also be individually configured (e.g., via RRC or SI) to associate or map on-demand SSBs 420 (e.g., first SSB 420-a, second SSB 420-b, third SSB 420-c, and fourth SSB 420-d) with second corresponding RO sets (e.g., first RO 425-a, second RO 425-b, third RO 425-c, and fourth RO 425-d). For example, a field or information element can configure the association or mapping between legacy SSB 405 and the first RO set 410, and a second field or information element can configure the association or mapping between on-demand SSB 420 and the second RO set 425. Individual configuration of the association between on-demand SSB 420 and the second RO set can be implemented based on a request from UE 115 to map on-demand SSB 420 and RO 425. As shown in the figure, the time between the on-demand SSB 420 and RO 425 is shorter than that between the older SSB 405 and RO 410, which allows for a more efficient connection between the on-demand SSB 420 and RO 425.

[0110] Figure 5 An example of a resource diagram 500 supporting RO configuration for on-demand SSB is shown, according to one or more aspects of this disclosure. Resource diagram 500 may implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200.

[0111] In some examples, network entity 105 may dynamically indicate uplink resources for RO 510 corresponding to on-demand SSB 505. For example, in response to a request for on-demand SSB 505 from UE 115, network entity 105 may make an online decision regarding uplink resources for RO 510 corresponding to on-demand SSB 505. Network entity 105-a may send dynamic signaling 515 indicating uplink resources for RO 510. In some examples, dynamic signaling 515 may provide information about the set of preambles that UE 115 can use or send in RO 510. For example, dynamic signaling 515 may indicate a specific preamble or a set of candidate preambles. In some examples, dynamic signaling 515 may be a MAC control element (MAC CE) or a DCI.

[0112] For example, dynamic signaling 515 could be a DCI received by the UE during a pre-configured (e.g., via RRC-configured) Physical Downlink Control Channel (PDCCH) monitoring event associated with On-Demand SSB 505. The DCI received during the PDCCH monitoring event associated with On-Demand SSB 505 could indicate scheduling information for the Msg1 preamble that UE 115 can transmit in RO 510. As another example, dynamic signaling 515 could be a DCI received by the UE during a pre-configured (e.g., via RRC-configured) PDCCH monitoring event configured to schedule the Physical Downlink Shared Channel (PDSCH). For example, the DCI used for scheduling the PDSCH could be reinterpreted or reused to schedule uplink resources for the Msg1 preamble that UE 115 can transmit in RO 510.

[0113] Figure 6 An example of a process flow 600 supporting RO configuration for on-demand SSBs according to one or more aspects of this disclosure is shown. Process flow 600 may include UE 115-b, which may be an example of UE 115 as described herein. Process flow 600 may include network entity 105-b, which may be an example of network entity 105 as described herein. In the following description of process flow 600, operations between network entity 105-b and UE 115-b may be sent in a different order than the example order shown, or operations performed by network entity 105-b and UE 115-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0114] At position 605, UE 115-b can send a request for an SSB to network entity 105-b. In some examples, this request could be an uplink WUS.

[0115] At 610, network entity 105-b can send an SSB to UE 115-b in response to the request.

[0116] At 615, UE 115-b can selectively send messages in ROs (Redirect Entities) to network entity 105-b based on the reception of the SSB, where the RO is associated with the SSB. At 620, network entity 105-b can accordingly selectively monitor messages from UE 115-b in ROs associated with the SSB based on the transmission of the SSB at 610. As used herein, selectively performing an action (e.g., selectively sending or selectively monitoring) based on one or more factors should be understood to mean that whether an action is performed is based on (e.g., depends on) one or more factors.

[0117] In some examples, UE 115-b may receive control signaling from network entity 105-b indicating a first mapping between a first SSB set and a first RO set, wherein the first SSB set includes SSBs, the first RO set includes ROs, and the first mapping indicates that an RO is associated with an SSB. In some examples, UE 115-b may selectively suppress the transmission of a second message in a second RO associated with a second SSB in the first RO set based on determining that a second SSB in the first SSB set has not been received, wherein the first mapping indicates that the second RO is associated with an SSB. In such examples, network entity 105-b may selectively suppress monitoring of a second message from UE 115-b in a second RO associated with a second SSB in the first RO set based on suppressing the transmission of a second SSB in the first SSB set. In some examples, UE 115-b may selectively transmit a second message in a second RO in the first RO set associated with a second SSB that has not been received in the first SSB set based on control signaling indicating that the first SSB set is an on-demand SSB, wherein the first mapping indicates that the second RO is associated with an SSB. In such examples, network entity 105-b may selectively monitor a second message in a second RO of a first RO set associated with an unsent second SSB in the first SSB set, based on control signaling indicating that the first SSB set is an on-demand SSB. In some examples, UE 115-b may utilize control signaling to receive an indication of a second mapping between the second SSB set and the second RO set, wherein the control signaling indicates that the first SSB set is an on-demand SSB and that the control signaling indicates that the second SSB set is unclaimed. In some examples, a first maximum duration between any SSB in the first SSB set according to the first mapping and an associated RO in the first RO set is less than a second maximum duration between any SSB in the second SSB set according to the second mapping and an associated RO in the second RO set. In some examples, control signaling may be received via RRC messages when UE 115-b is in RRC connection mode with network entity 105-b. In some examples, control signaling may be received via SI.

[0118] In some examples, UE 115-b may receive control signaling indicating the RO associated with the SSB from network entity 105-b and in response to a request at 605. In some examples, UE 115-b may utilize the control signaling to receive an indication of a set of preambles associated with the RO, and the transmission message may include transmitting a preamble from the preamble set. In some examples, the control signaling may be a DCI received via a downlink control channel monitoring event (e.g., a PDCCH monitoring event) associated with the SSB. In some examples, the control signaling may be a DCI received via a downlink control channel monitoring event (e.g., a PDCCH monitoring event) associated with scheduling transmission from a downlink shared channel (e.g., a PDSCH) from a network entity.

[0119] Figure 7 A block diagram 700 illustrates a device 705 supporting RO configuration for on-demand SSB according to one or more aspects of this disclosure. Device 705 may be an example of various 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 can be coupled to at least one memory to individually or collectively support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0120] 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 RO configuration for on-demand SSB). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0121] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with RO configuration for on-demand SSB). 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 collection of multiple antennas.

[0122] 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 the RO configuration for on-demand SSB 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.

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

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

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

[0126] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for sending a request for an SSB to a network entity. The communication manager 720 may be capable of, configured to, or operable to support components for receiving an SSB from a network entity in response to the request. The communication manager 720 may be capable of, configured to, or operable to support components for selectively sending messages to a network entity in an RO based on the receipt of an SSB, wherein the RO is associated with an SSB.

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

[0128] Figure 8 A block diagram 800 of a device 805 supporting RO configuration for on-demand SSBs is shown according to one or more aspects of this disclosure. 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 can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] 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 RO configuration for on-demand SSB). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0130] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with RO configuration for on-demand SSB). 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.

[0131] Device 805 or its various components may be examples of parts used to perform various aspects of RO configuration for on-demand SSB as described herein. For example, communication manager 820 may include SSB request manager 825, SSB receive manager 830, RO manager 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., receive, acquire, monitor, output, transmit). 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.

[0132] Communication manager 820 may support wireless communication according to examples disclosed herein. SSB request manager 825 is capable of, configured to, or operable to support components for sending a request for an SSB to a network entity. SSB receive manager 830 is capable of, configured to, or operable to support components for receiving an SSB from a network entity in response to the request. RO manager 835 is capable of, configured to, or operable to support components for selectively sending messages to a network entity in ROs based on the receipt of an SSB, wherein the RO is associated with an SSB.

[0133] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting RO configuration for on-demand SSBs according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of RO configuration for on-demand SSBs as described herein. For example, the communication manager 920 may include an SSB request manager 925, an SSB receive manager 930, an RO manager 935, an SSB-RO mapping manager 940, an uplink WUS manager 945, an RRC connection mode manager 950, an SI manager 955, an RO preamble manager 960, a DCI receive manager 965, 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).

[0134] Communication manager 920 may support wireless communication according to examples disclosed herein. SSB request manager 925 is capable of, configured to, or operable to support components for sending a request for an SSB to a network entity. SSB receive manager 930 is capable of, configured to, or operable to support components for receiving an SSB from a network entity in response to the request. RO manager 935 is capable of, configured to, or operable to support components for selectively sending messages to a network entity in ROs based on the receipt of an SSB, wherein the RO is associated with an SSB.

[0135] In some examples, the SSB-RO mapping manager 940 is capable of, configured to, or operable to support components for receiving control signaling from a network entity indicating a first mapping between a first SSB set and a first RO set, wherein the first SSB set includes SSBs, the first RO set includes ROs, and the first mapping indicates that an RO is associated with an SSB.

[0136] In some examples, the RO manager 935 is capable of, configured to, or able to operate to support components for selectively suppressing the transmission of a second message in a second RO associated with a second SSB in the first RO set based on the determination that a second SSB in the first SSB set has not been received, wherein the first mapping indicates that the second RO is associated with an SSB.

[0137] In some examples, the RO manager 935 is capable of, configured to, or able to operate to support components for selectively sending a second message in a second RO of a first RO set associated with a second SSB that has not been received in the first SSB set, based on control signaling indicating that the first SSB set is an on-demand SSB, wherein the first mapping indicates that the second RO is associated with an SSB.

[0138] In some examples, the SSB-RO mapping manager 940 is capable of, configured to, or operable to support components for receiving instructions on a second mapping between a second SSB set and a second RO set using control signaling, wherein the control signaling indicates that the first SSB set is an on-demand SSB, and wherein the control signaling indicates that the second SSB set is not requested.

[0139] In some examples, the first maximum duration between any SSB in the first SSB set according to the first mapping and the associated RO in the first RO set is less than the second maximum duration between any SSB in the second SSB set according to the second mapping and the associated RO in the second RO set.

[0140] In some examples, in order to support the reception of control signaling, the RRC connection mode manager 950 can be configured or operated to support components for receiving control signaling via RRC messages when in an RRC connection mode with a network entity.

[0141] In some examples, in order to support receiving control signaling, the SI manager 955 can be configured or operated to support components for receiving control signaling via the SI.

[0142] In some examples, the SSB-RO mapping manager 940 is capable of, configured to, or able to operate to support components for receiving control signaling from network entities in response to a request, indicating the RO associated with the SSB.

[0143] In some examples, the RO preamble manager 960 is capable of, configured to, or able to operate to support components for receiving indications to a set of preambles associated with the RO using control signaling, wherein sending a message includes sending a preamble from the set of preambles.

[0144] In some examples, in order to support receive control signaling, the DCI receive manager 965 can be configured or operated to support components for receiving DCI via downlink control channel monitoring timing associated with the SSB.

[0145] In some examples, the DCI receive manager 965 is capable of, configured to, or able to operate to support components for receiving DCI via downlink control channel monitoring timing associated with scheduling downlink shared channel transmission from network entities.

[0146] In some examples, in order to support sending requests, the uplink WUS manager 945 can be, configured, or operated to support components for sending uplink WUS to network entities.

[0147] Figure 10A diagram of a system 1000 including device 1005 supporting RO configuration for on-demand SSB is shown according to one or more aspects of this disclosure. 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).

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

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

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

[0151] 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 RO configuration for on-demand SSB). 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 receive input and process such input to produce, generate, or obtain output. 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, capable of being configured, or operable to cause device 1005 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” 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.

[0152] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for sending a request for an SSB to a network entity. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving an SSB from a network entity in response to the request. The communication manager 1020 may be capable of, configured to, or operable to support components for selectively sending messages to a network entity in an RO based on the receipt of an SSB, wherein the RO is associated with an SSB.

[0153] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for power consumption, more efficient use of communication resources, and improved coordination between devices.

[0154] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using 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 the RO configuration for on-demand SSB 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.

[0155] Figure 11 A block diagram 1100 of a device 1105 supporting RO configuration for on-demand SSBs 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).

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

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

[0158] 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 the RO configuration for on-demand SSB 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.

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

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

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

[0162] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be, configured, or operable to support components for receiving a request for an SSB from a UE. The communication manager 1120 may be, configured, or operable to support components for transmitting an SSB to and in response to a UE. The communication manager 1120 may be, configured, or operable to support components for selectively monitoring messages from the UE in an RO based on the SSB, wherein the RO is associated with an SSB.

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

[0164] Figure 12 A block diagram 1200 of a device 1205 supporting RO configuration for on-demand SSBs is shown, according to one or more aspects of this disclosure. 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 techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0167] Device 1205 or its various components may be examples of parts for performing various aspects of RO configuration for on-demand SSB as described herein. For example, communication manager 1220 may include SSB request manager 1225, SSB send manager 1230, RO manager 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.

[0168] Communication manager 1220 may support wireless communication according to examples disclosed herein. SSB request manager 1225 is capable of, configured to, or operable to support components for receiving requests for SSBs from the UE. SSB transmission manager 1230 is capable of, configured to, or operable to support components for transmitting SSBs to and in response to the UE. RO manager 1235 is capable of, configured to, or operable to support components for selectively monitoring messages from the UE in ROs for SSB-based transmission, wherein the RO is associated with an SSB.

[0169] Figure 13A block diagram 1300 is shown of a communication manager 1320 supporting RO configuration for on-demand SSBs 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 RO configuration for on-demand SSBs as described herein. For example, the communication manager 1320 may include an SSB request manager 1325, an SSB sending manager 1330, an RO manager 1335, an SSB-RO mapping manager 1340, an uplink WUS manager 1345, an RRC connection mode manager 1350, an SI manager 1355, an RO preamble manager 1360, a DCI sending manager 1365, 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.

[0170] Communication manager 1320 may support wireless communication according to examples disclosed herein. SSB request manager 1325 is capable of, configured to, or operable to support components for receiving requests for an SSB from a UE. SSB transmission manager 1330 is capable of, configured to, or operable to support components for transmitting an SSB to and in response to the UE. RO manager 1335 is capable of, configured to, or operable to support components for selectively monitoring messages from the UE in an RO for SSB-based transmission, wherein the RO is associated with an SSB.

[0171] In some examples, the SSB-RO mapping manager 1340 is capable of, configured to, or operable to support components for sending control signaling to the UE indicating a first mapping between a first SSB set and a first RO set, wherein the first SSB set includes SSBs, the first RO set includes ROs, and the first mapping indicates that an RO is associated with an SSB.

[0172] In some examples, the RO manager 1335 is capable of, configured to, or able to operate to support a component for selectively suppressing the monitoring of a second message from the UE in a second RO associated with the second SSB in the first RO set based on the suppression of transmission of a second SSB in the first SSB set, wherein the first mapping indicates that the second RO is associated with the SSB.

[0173] In some examples, the RO manager 1335 is capable of, configured to, or able to operate to support components for selectively monitoring second messages in a second RO of a first RO set associated with an unsent second SSB in the first SSB set, based on control signaling indicating that the first SSB set is an on-demand SSB, wherein a first mapping indicates that the second RO is associated with an SSB.

[0174] In some examples, the SSB-RO mapping manager 1340 is capable of, configured to, or operable to support components for sending instructions on a second mapping between a second SSB set and a second RO set using control signaling, wherein the control signaling indicates that the first SSB set is an on-demand SSB, and wherein the control signaling indicates that the second SSB set is not requested.

[0175] In some examples, the first maximum duration between any SSB in the first SSB set according to the first mapping and the associated RO in the first RO set is less than the second maximum duration between any SSB in the second SSB set according to the second mapping and the associated RO in the second RO set.

[0176] In some examples, to support the sending of control signaling, the RRC connection mode manager 1350 can be configured or operated to support components for sending control signaling via RRC messages when in an RRC connection mode with a network entity.

[0177] In some examples, in order to support the transmission of control signaling, the SI manager 1355 can be configured or operated to support components used for transmitting control signaling via the SI.

[0178] In some examples, the SSB-RO mapping manager 1340 is capable of, configured to, or able to operate to support components for sending control signaling to the UE in response to a request, indicating the RO associated with the SSB.

[0179] In some examples, the RO preamble manager 1360 is capable of, configured to, or operable to support components for sending instructions to a set of preambles associated with the RO using control signaling, wherein receiving a message includes receiving a preamble from the set of preambles.

[0180] In some examples, in order to support the transmission of control signaling, the DCI transmission manager 1365 can be configured or operated to support components for transmitting DCI via downlink control channel monitoring timing associated with the SSB.

[0181] In some examples, in order to support the transmission of control signaling, the DCI transmission manager 1365 can be configured or operated to support components for transmitting DCI via downlink control channel monitoring timing associated with scheduling downlink shared channel transmission.

[0182] In some examples, in order to support the reception request, the uplink WUS manager 1345 is able to be configured or can operate to support components for receiving uplink WUS from the UE.

[0183] Figure 14 A diagram of a system 1400 including device 1405 supporting RO configuration for on-demand SSB is shown according to one or more aspects of this disclosure. 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).

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

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

[0186] 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 RO configuration for on-demand SSB). 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.

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

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

[0189] The communication manager 1420 may support wireless communication according to examples disclosed herein. For example, the communication manager 1420 may be, configured, or operable to support components for receiving a request for an SSB from a UE. The communication manager 1420 may be, configured, or operable to support components for transmitting an SSB to and in response to a UE. The communication manager 1420 may be, configured, or operable to support components for selectively monitoring messages from the UE in an RO based on the SSB, wherein the RO is associated with an SSB.

[0190] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for power consumption, more efficient use of communication resources, and improved coordination between devices.

[0191] 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 one or more processors in at least one processor 1435 to cause the device 1405 to perform various aspects of the RO configuration for on-demand SSB 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.

[0192] Figure 15 A flowchart illustrating a method 1500 for supporting RO configuration for on-demand SSB according to various 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 achieved 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.

[0193] At 1505, the method may include sending a request for the SSB to the network entity. The operation of box 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 9 The SSB Request Manager 925 described is used to execute this.

[0194] At 1510, the method may include receiving an SSB from and in response to a network entity. The operation of box 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 9 The SSB Receiver Manager 930 described is used to perform this.

[0195] At 1515, the method may include selectively sending messages in a RO based on the reception of the SSB to a network entity, wherein the RO is associated with the SSB. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 9 The RO Manager 935 described is used to execute this.

[0196] Figure 16 A flowchart illustrating method 1600 for supporting RO configuration for on-demand SSB according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 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.

[0197] At 1605, the method may include receiving a request for an SSB from the UE. The operation of block 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 13 The SSB request manager 1325 described is used to execute this.

[0198] At 1610, the method may include sending an SSB to and in response to the UE. The operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 13 The SSB sending manager 1330 described is used to perform this.

[0199] At 1615, the method may include selectively monitoring messages from the UE in the RO based on the SSB, wherein the RO is associated with the SSB. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 13 The RO Manager 1335 described is used for execution.

[0200] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: sending a request for an SSB to a network entity; receiving the SSB from the network entity and in response to the request; and selectively sending a message in an RO to the network entity and at least in part based on the receipt of the SSB, wherein the RO is associated with the SSB.

[0201] Aspect 2: According to the method of aspect 1, the method further includes: receiving from the network entity a control signaling indicating a first mapping between a first SSB set and a first RO set, wherein the first SSB set includes the SSBs, wherein the first RO set includes the ROs, and wherein the first mapping indicates that the ROs are associated with the SSBs.

[0202] Aspect 3: According to the method of aspect 2, the method further includes: selectively suppressing the transmission of a second message in a second RO associated with the second SSB in the first RO set, at least in part based on determining that a second SSB in the first SSB set has not been received, wherein the first mapping indicates that the second RO is associated with the SSB.

[0203] Aspect 4: The method according to any one of Aspects 2 to 3, the method further comprising: selectively sending a second message in a second RO of a first RO set associated with an unreceived second SSB in the first SSB set, based at least in part on the control signaling indicating that the first SSB set is an on-demand SSB, wherein the first mapping indicates that the second RO is associated with the SSB.

[0204] Aspect 5: The method according to any one of Aspects 2 to 4, the method further comprising: using the control signaling to receive an indication of a second mapping between a second SSB set and a second RO set, wherein the control signaling indicates that the first SSB set is an on-demand SSB, and wherein the control signaling indicates that the second SSB set is not requested.

[0205] Aspect 6: The method according to aspect 5, wherein a first maximum duration between any SSB in the first SSB set according to the first mapping and an associated RO in the first RO set is less than a second maximum duration between any SSB in the second SSB set according to the second mapping and an associated RO in the second RO set.

[0206] Aspect 7: The method according to any one of Aspects 2 to 6, wherein receiving the control signaling comprises: receiving the control signaling via an RRC message when in an RRC connection mode with the network entity.

[0207] Aspect 8: The method according to any one of Aspects 2 to 6, wherein receiving the control signaling includes: receiving the control signaling via SI.

[0208] Aspect 9: The method according to aspect 1, the method further comprising: receiving control signaling from the network entity in response to the request indicating the RO associated with the SSB.

[0209] Aspect 10: The method according to aspect 9, the method further comprising: using the control signaling to receive an indication of a set of preambles associated with the RO, wherein sending the message includes sending a preamble from the set of preambles.

[0210] Aspect 11: The method according to any one of Aspects 9 to 10, wherein receiving the control signaling comprises: receiving DCI via a downlink control channel monitoring timing associated with the SSB.

[0211] Aspect 12: The method according to any one of Aspects 9 to 10, the method further comprising: receiving DCI via a downlink control channel monitoring timing associated with scheduling downlink shared channel transmission from the network entity.

[0212] Aspect 13: The method according to any one of Aspects 1 to 12, wherein sending the request comprises: sending an uplink WUS to the network entity.

[0213] Aspect 14: A method for wireless communication at a network entity, the method comprising: receiving a request for an SSB from a UE; transmitting the SSB to the UE and in response to the request; and selectively monitoring messages from the UE in an RO, at least in part based on the transmission of the SSB, wherein the RO is associated with the SSB.

[0214] Aspect 15: The method according to aspect 14, the method further comprising: sending to the UE control signaling indicating a first mapping between a first SSB set and a first RO set, wherein the first SSB set includes the SSBs, wherein the first RO set includes the ROs, and wherein the first mapping indicates that the ROs are associated with the SSBs.

[0215] Aspect 16: The method according to aspect 15, the method further comprising: selectively suppressing the monitoring of a second message from the UE in a second RO associated with the second SSB in the first RO set, based at least in part on suppressing the transmission of a second SSB in the first SSB set, wherein the first mapping indicates that the second RO is associated with the SSB.

[0216] Aspect 17: The method according to any one of Aspects 15 to 16, the method further comprising: selectively monitoring a second message in a second RO of a first RO set associated with an unsent second SSB in the first SSB set, based at least in part on the control signaling indicating that the first SSB set is an on-demand SSB, wherein the first mapping indicates that the second RO is associated with the SSB.

[0217] Aspect 18: The method according to any one of Aspects 15 to 17, the method further comprising: using the control signaling to send an indication of a second mapping between a second SSB set and a second RO set, wherein the control signaling indicates that the first SSB set is an on-demand SSB, and wherein the control signaling indicates that the second SSB set is not requested.

[0218] Aspect 19: The method according to aspect 18, wherein a first maximum duration between any SSB in the first SSB set according to the first mapping and an associated RO in the first RO set is less than a second maximum duration between any SSB in the second SSB set according to the second mapping and an associated RO in the second RO set.

[0219] Aspect 20: The method according to any one of Aspects 15 to 19, wherein sending the control signaling comprises: sending the control signaling via an RRC message when in an RRC connection mode with the network entity.

[0220] Aspect 21: The method according to any one of aspects 15 to 19, wherein sending the control signaling comprises: sending the control signaling via SI.

[0221] Aspect 22: The method according to aspect 14, the method further comprising: in response to the request, sending to the UE control signaling indicating the RO associated with the SSB.

[0222] Aspect 23: The method according to aspect 22, the method further comprising: using the control signaling to send an indication of a set of preambles associated with the RO, wherein receiving the message includes receiving a preamble from the set of preambles.

[0223] Aspect 24: The method according to any one of Aspects 22 to 23, wherein transmitting the control signaling comprises: transmitting DCI via a downlink control channel monitoring timing associated with the SSB.

[0224] Aspect 25: The method according to any one of Aspects 22 to 23, wherein transmitting the control signaling comprises: transmitting DCI via a downlink control channel monitoring timing associated with scheduling downlink shared channel transmission.

[0225] Aspect 26: The method according to any one of Aspects 14 to 25, wherein receiving the request comprises: receiving an uplink WUS from the UE.

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

[0227] Aspect 28: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 13.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0243] 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: Send a request for a synchronization signal block to the network entity; Receive the synchronization signal block from the network entity and in response to the request; as well as Messages are selectively sent to the network entity during random access channel timings, at least in part based on the receipt of the synchronization signal block, wherein the random access channel timings are associated with the synchronization signal block.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The network entity receives control signaling indicating a first mapping between a first set of synchronization signal blocks and a first set of random access channel opportunities, wherein the first set of synchronization signal blocks includes the synchronization signal blocks, wherein the first set of random access channel opportunities includes the random access channel opportunities, and wherein the first mapping indicates that the random access channel opportunities are associated with the synchronization signal blocks.

3. The UE of claim 2, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: At least in part, based on the determination that a second synchronization block in the first set of synchronization blocks has not been received, the transmission of a second message in a second random access channel opportunity associated with the second synchronization block in the first set of random access channel opportunities is selectively suppressed, wherein the first mapping indicates that the second random access channel opportunity is associated with the synchronization block.

4. The UE of claim 2, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Based at least in part on the control signaling indicating that the first set of synchronization signal blocks is an on-demand synchronization signal block, a second message is selectively sent in a second random access channel opportunity in the first set of random access channel opportunities associated with an unreceived second synchronization signal block in the first set of synchronization signal blocks, wherein the first mapping indicates that the second random access channel opportunity is associated with the synchronization signal block.

5. The UE of claim 2, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The control signaling is used to receive an indication of a second mapping between a second set of synchronization signal blocks and a second set of random access channel timings, wherein the control signaling indicates that the first set of synchronization signal blocks is an on-demand synchronization signal block, and wherein the control signaling indicates that the second set of synchronization signal blocks is not requested.

6. The UE of claim 5, wherein a first maximum duration between any synchronization signal block in the first set of synchronization signal blocks according to the first mapping and an associated random access channel timing in the first set of random access channel timings is less than a second maximum duration between any synchronization signal block in the second set of synchronization signal blocks according to the second mapping and an associated random access channel timing in the second set of random access channel timings.

7. The UE of claim 2, wherein, in order to receive the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: When in a radio resource control connection mode with the network entity, the control signaling is received via radio resource control messages.

8. The UE of claim 2, wherein, in order to receive the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The control signaling is received via system information.

9. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: In response to the request, control signaling indicating the timing of the random access channel associated with the synchronization signal block is received from the network entity.

10. The UE of claim 9, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The control signaling is used to receive an indication of a set of preambles associated with the timing of the random access channel, wherein sending the message includes sending one of the preambles in the set of preambles.

11. The UE of claim 9, wherein, in order to receive the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Downlink control information is received via downlink control channel monitoring timing associated with the synchronization signal block.

12. The UE of claim 9, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: Downlink control information is received via downlink control channel monitoring timing associated with scheduling downlink shared channel transmission from the network entity.

13. The UE of claim 1, wherein, in order to send the request, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Send an uplink wake-up signal to the network entity.

14. 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: Receive requests for synchronization signal blocks from User Equipment (UE); Send the synchronization signal block to the UE and in response to the request; as well as The system selectively monitors messages from the UE during random access channel timings, at least in part based on the transmission of the synchronization signal block, wherein the random access channel timings are associated with the synchronization signal block.

15. The network entity of claim 14, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: A control signaling is sent to the UE to indicate a first mapping between a first set of synchronization signal blocks and a first set of random access channel timings, wherein the first set of synchronization signal blocks includes the synchronization signal blocks, wherein the first set of random access channel timings includes the random access channel timings, and wherein the first mapping indicates that the random access channel timings are associated with the synchronization signal blocks.

16. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: At least in part, based on suppressing the transmission of a second synchronization block in the first set of synchronization blocks, the monitoring of a second message from the UE is selectively suppressed in a second random access channel timing associated with the second synchronization block in the first set of random access channel timings, wherein the first mapping indicates that the second random access channel timing is associated with the synchronization block.

17. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Based at least in part on the control signaling indicating that the first set of synchronization signal blocks is an on-demand synchronization signal block, a second message is selectively monitored in a second random access channel timing in the first set of random access channel timings associated with an untransmitted second synchronization signal block in the first set of synchronization signal blocks, wherein the first mapping indicates that the second random access channel timing is associated with the synchronization signal block.

18. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The control signaling is used to send an indication of a second mapping between a second set of synchronization signal blocks and a second set of random access channel timings, wherein the control signaling indicates that the first set of synchronization signal blocks is an on-demand synchronization signal block, and wherein the control signaling indicates that the second set of synchronization signal blocks is not requested.

19. The network entity of claim 18, wherein a first maximum duration between any synchronization block in the first set of synchronization blocks according to the first mapping and an associated random access channel opportunity in the first set of random access channel opportunities is less than a second maximum duration between any synchronization block in the second set of synchronization blocks according to the second mapping and an associated random access channel opportunity in the second set of random access channel opportunities.

20. The network entity of claim 15, wherein, in order to send the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: The control signaling is sent via radio resource control messages when in radio resource control connection mode with the network entity.

21. The network entity of claim 15, wherein, in order to send the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: The control signaling is sent via system information.

22. The network entity of claim 14, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: In response to the request, control signaling is sent to the UE indicating the timing of the random access channel associated with the synchronization signal block.

23. The network entity of claim 22, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The control signaling is used to send an indication of a set of preambles associated with the timing of the random access channel, wherein receiving the message includes receiving a preamble from the set of preambles.

24. The network entity of claim 22, wherein, in order to send the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: Downlink control information is transmitted via downlink control channel monitoring timing associated with the synchronization signal block.

25. The network entity of claim 22, wherein, in order to send the control signaling, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: Downlink control information is transmitted via downlink control channel monitoring timing associated with the scheduling of downlink shared channel transmission.

26. The network entity of claim 14, wherein, in order to receive the request, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: Receive the uplink wake-up signal from the UE.

27. A method for conducting wireless communication at a user equipment (UE), the method comprising: Send a request for a synchronization signal block to the network entity; Receive the synchronization signal block from the network entity and in response to the request; as well as Messages are selectively sent to the network entity during random access channel timings, at least in part based on the receipt of the synchronization signal block, wherein the random access channel timings are associated with the synchronization signal block.

28. The method of claim 27, further comprising: The network entity receives control signaling indicating a first mapping between a first set of synchronization signal blocks and a first set of random access channel opportunities, wherein the first set of synchronization signal blocks includes the synchronization signal blocks, wherein the first set of random access channel opportunities includes the random access channel opportunities, and wherein the first mapping indicates that the random access channel opportunities are associated with the synchronization signal blocks.

29. The method according to claim 28, further comprising: At least in part, based on the determination that a second synchronization block in the first set of synchronization blocks has not been received, the transmission of a second message in a second random access channel opportunity associated with the second synchronization block in the first set of random access channel opportunities is selectively suppressed, wherein the first mapping indicates that the second random access channel opportunity is associated with the synchronization block.

30. A method for conducting wireless communication at a network entity, the method comprising: Receive requests for synchronization signal blocks from User Equipment (UE); Send the synchronization signal block to the UE and in response to the request; as well as The system selectively monitors messages from the UE during random access channel timings, at least in part based on the transmission of the synchronization signal block, wherein the random access channel timings are associated with the synchronization signal block.

Images