Repeater beam request for transparent beam management

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may report an initial capability to maintain a latency condition and a number of supported beams (e.g., a threshold number of beams that the UE may support for relaying downlink communications, such as a synchronization signal block (SSB)). The network entity may then transmit multiple SSBs directly to the repeater (e.g., on the same beam). The relay may relay the SSB across multiple beams to provide services to a coverage area. After relaying signaling between a served UE and the network entity, the relay may send a report requesting a specific (e.g., improved or more accurate) number of beams (e.g., more or less beams than the number of SSBs originally provided). When an updated configuration of a number of beams is received, the repeater may receive more SSBs on a single beam and relay SSBs on the updated number of beams.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 835,767, filed by Horn et al. on June 8, 2022, entitled “REPEATER BEAM REQUESTS FOR TRANSPARENT BEAM MANAGEMENT,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications including repeater beam requests for transparent beam management. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for 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 that support repeater beam requests for transparent beam management. For example, a user equipment (UE) may report an initial capability to maintain a latency condition and the number of beams supported (e.g., a threshold number of beams that the UE may support for relaying downlink communications such as synchronization signal blocks (SSBs)) based on a specified latency condition. The network entity may then send the SSBs, and may send a subset of the SSBs (e.g., multiple SSBs) directly to the repeater (e.g., on the same beam rather than on multiple beams). The repeater may relay the SSBs across multiple beams to provide services to a coverage area (e.g., a geographic area that is not directly served by the network entity based on an obstruction or structure, or the interior of a structure, etc.). After relaying signaling between any served UE and the network entity, the repeater may send a report requesting a specific (e.g., improved or more accurate) number of beams (e.g., more beams or fewer beams than the number of SSBs initially provided and relayed by the repeater). The UE may include a request for the number of beams or beam directions in the report, and may determine the number of beams to request based on the UE being served, the service, the coverage area, or the spatial sensor, etc. Upon receiving an updated configuration of several beams, the repeater may receive more SSBs and relay them on the updated number of beams.

[0006] A method for wireless communication at a repeater is described. The method may include: sending a capability report including an indication of latency capability and a number of beams supported by the repeater; receiving a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater; relaying the set of multiple SSBs via a first beam set associated with a coverage area served by the repeater; and sending a repeater report including an indication of a second beam set associated with service to one or more UEs located in the coverage area served by the repeater based on relaying the set of multiple SSBs via the first beam set.

[0007] An apparatus for wireless communication at a repeater is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a capability report including an indication of latency capability and a number of beams supported by the repeater; receive a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater; relay the set of multiple SSBs via a first beam set associated with a coverage area served by the repeater; and send a repeater report including an indication of a second beam set associated with a service to one or more UEs located in the coverage area served by the repeater based on relaying the set of multiple SSBs via the first beam set.

[0008] Another apparatus for wireless communication at a repeater is described. The apparatus may include: a component for sending a capability report, the capability report including an indication of latency capability and a number of beams supported by the repeater; a component for receiving a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater; a component for relaying the set of multiple SSBs via a first set of beams associated with a coverage area served by the repeater; and a component for sending a repeater report including an indication of a second set of beams associated with service to one or more UEs located in the coverage area served by the repeater based on relaying the set of multiple SSBs via the first set of beams.

[0009] A non-transitory computer-readable medium is described that stores code for wireless communication at a repeater. The code may include instructions that can be executed by a processor to perform the following: send a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater; receive a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponds to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater; relay the set of multiple SSBs via a first beam set associated with a coverage area served by the repeater; and send a repeater report including an indication of a second beam set associated with service to one or more UEs located in the coverage area served by the repeater based on relaying the set of multiple SSBs via the first beam set.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a beam assignment message including beam information of the second set of beams based on sending the repeater report.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the beam assignment message may include operations, features, components, or instructions for: an indication of a number of beams for the second beam set, an indication of a beam direction for each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the beam assignment message may include operations, features, components, or instructions for: a one-bit message indicating that the second set of beams may be the same as the first set of beams.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving a second set of multiple SSBs via the first beam, each SSB in the second set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the second set of multiple SSBs satisfies the second beam set; and relaying the second set of multiple SSBs via the second beam set.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repeater report may include operations, features, components, or instructions for: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between duplicate beams of the first beam set, or a combination thereof.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for estimating the number of beams of the second beam set based on: the number of random access opportunities associated with the random access message relayed by the repeater from the one or more UEs to the network entity, the number of UEs located in the coverage area served by the repeater, the spatial spacing between corresponding beams in the first beam set, or a combination thereof, wherein sending the repeater report may be based on estimating the number of beams.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: determining a size of a coverage area served by a repeater based on: one or more sensors, a preconfigured area input by a user, a history of locations of one or more UEs served by the repeater, a number of messages received from one or more UEs based on relaying a set of multiple SSBs, or a combination thereof; and estimating a number of beams of the second beam set based on the size of the coverage area served by the repeater, wherein sending the repeater report may be based on estimating the number of beams.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, signaling is relayed from a network entity to one or more UEs served by the relay and signaling is relayed from the one or more UEs to the network entity based on relaying the set of multiple SSBs.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, relaying the signaling from the network entity to the one or more UEs and relaying the signaling from the one or more UEs to the network entity may include operations, features, apparatus, or instructions for receiving a random access message associated with a corresponding SSB index of the set of multiple SSBs from the one or more UEs using the first beam set, and relaying the received random access message to the network entity using the first beam.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: receiving an indication of an SSB index set including each respective SSB index corresponding to each SSB in the set of multiple SSBs from a network entity; and determining a time opportunity for receiving each SSB in the set of multiple SSBs based on the indication of the SSB index set, wherein receiving the set of multiple SSBs may be based on the determination.

[0020] A method for wireless communication at a network entity is described. The method may include: obtaining a capability report including an indication of latency capability and a number of beams supported by a repeater; outputting a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the set of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater; obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs; and obtaining a repeater report including an indication of the repeater for a second beam set associated with service to one or more UEs located in a coverage area served by the repeater.

[0021] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain a capability report, the capability report including an indication of latency capability and the number of beams supported by a repeater; output a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the set of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater; obtain one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs; and obtain a repeater report including an indication of the repeater for a second beam set associated with service to one or more UEs located in a coverage area served by the repeater.

[0022] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for obtaining a capability report, the capability report including an indication of latency capability and a number of beams supported by a repeater; a component for outputting a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the set of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater; a component for obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs; and a component for obtaining a repeater report including an indication of the repeater for a second beam set associated with service to one or more UEs located in a coverage area served by the repeater.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: obtain a capability report, the capability report including an indication of latency capability and the number of beams supported by a repeater; output a set of multiple SSBs via a first beam, each SSB in the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the set of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater; obtain one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs; and obtain a repeater report including an indication of the repeater for a second beam set associated with service to one or more UEs located in a coverage area served by the repeater.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: outputting a beam assignment message including beam information of the second set of beams based on obtaining the repeater report.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the beam assignment message may include operations, features, components, or instructions for: an indication of a number of beams for the second beam set, an indication of a beam direction for each beam in the second beam set, or a combination thereof, wherein the second beam set may be different from the first beam set.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the beam assignment message may include operations, features, components, or instructions for: a one-bit message indicating that the second set of beams may be the same as the first set of beams.

[0027] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: outputting a second set of multiple SSBs via a second beam, each SSB in the second set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the second set of multiple SSBs satisfies the second beam set.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the repeater report may include operations, features, components, or instructions for: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between duplicate beams of the first beam set, or a combination thereof.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following: outputting an indication of a set of SSB indexes including each respective SSB index corresponding to each SSB in the set of the plurality of SSBs, wherein outputting the set of the plurality of SSBs may be based on outputting the indication of the set of SSB indexes. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 An example of a wireless communication system supporting repeater beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated.

[0031] Figure 2A An example of a wireless communication system supporting repeater beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 2B An example of a wireless communication system supporting repeater beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 3 An example of a process flow diagram for supporting repeater beam requests for transparent beam management in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 4 and Figure 5 A block diagram of a device supporting repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown.

[0035] Figure 6 A block diagram of a communication manager supporting repeater beam requests for transparent beam management is shown in accordance with one or more aspects of the present disclosure.

[0036] Figure 7 A diagram of a system including a device supporting repeater beam request for transparent beam management is shown in accordance with one or more aspects of the present disclosure.

[0037] Figure 8 and Fig. 9 A block diagram of a device supporting repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown.

[0038] Fig.10 A block diagram of a communication manager supporting repeater beam requests for transparent beam management is shown in accordance with one or more aspects of the present disclosure.

[0039] Fig.11A diagram of a system including a device supporting repeater beam request for transparent beam management is shown in accordance with one or more aspects of the present disclosure.

[0040] Figures 12 to 15 A flow chart illustrating a method of supporting repeater beam requests for transparent beam management according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0041] In some wireless communication systems, line of sight (LOS) channels can improve or extend coverage and increase throughput. Some communications may rely on utilizing LOS channels (e.g., may fail without utilizing LOS channels). However, in some cases (e.g., indoor or urban deployments), LOS channels may be difficult to identify or utilize. For example, due to obstacles (e.g., buildings or other structures) or UE locations (e.g., inside a structure or room), some UEs may not be able to use LOS channels to communicate with one or more network entities. Therefore, a wireless communication system may include one or more repeaters (e.g., relays, femtocells, reconfigurable smart surfaces (RIS), etc.) to relay signaling between wireless nodes (e.g., between a network entity and one or more UEs). For example, a repeater may facilitate a LOS channel between a repeater and a network device and between a repeater and one or more UEs, resulting in an effective LOS channel between a UE and a network entity.

[0042] A repeater may maintain low latency communications between a network entity and one or more UEs by ensuring that a channel delay spread does not exceed a threshold (e.g., not by a cyclic prefix (CP) length). A repeater may be able to extend coverage to a specific spatial region (e.g., a room within a structure). In some examples, a UE may communicate directly with a repeater (e.g., may establish a separate communication link with the repeater, and may transmit transmissions to the repeater for relaying to a network entity or monitor communications from the repeater for relaying downlink signaling from the network entity).

[0043] Similarly, the network entity may establish a communication link with the repeater, and may send downlink signaling to the repeater for relaying to the UE, and may monitor signaling from the repeater relaying uplink communications from the UE. Such communications may be referred to as non-transparent relaying (e.g., where the UE establishes a unique connection with the repeater and performs wireless communications with the repeater based on the assumption that the repeater will communicate with the network entity). However, such non-transparent relaying may result in extending the time and computing resources of one or more wireless nodes, increased latency and system delays for relaying signaling, and failure to meet low latency communication requirements, resulting in inter-symbol interference.

[0044] In some examples, as described herein, a network entity may support transparent relaying and beam management procedures. For example, a UE may communicate directly with a network entity (via a repeater) but without establishing a communication link with the repeater itself (e.g., without being aware that the repeater exists, or is part of a communication link). That is, instead of communicating directly with a repeater so that the repeater can relay the communication to the network entity (e.g., as may be the case in non-transparent repeater communications), the UE may communicate directly with the network entity (e.g., and the repeater may facilitate a LOS channel for such communications, even though the UE lacks any information about the existence of the repeater or its role in communicating with the network entity).

[0045] To support the transparent beam management process, the network entity may transmit synchronization signal blocks (SSBs) using multiple beams to cover multiple directions. In some examples, the network entity may transmit multiple SSBs toward a repeater using a single beam (e.g., in a single direction), and the repeater may relay multiple received SSBs along the multiple beams to serve one or more UEs that would otherwise be unable to communicate with the network entity. The repeater may facilitate communication between one or more served UEs and the network entity based on the relayed SSBs (e.g., may relay random access messages between the UE and the network entity based on the relayed SSBs).

[0046] In some examples, the UE may report an initial capability to maintain latency conditions and the number of beams supported (e.g., a threshold number of beams that the UE may support for relaying downlink communications such as SSBs). The network entity may then send the SSBs, and may send a subset of the SSBs (e.g., multiple SSBs) directly to the repeater (e.g., on the same beam instead of on multiple beams). The repeater may relay the SSBs across multiple beams to provide service to a coverage area (e.g., a geographic area not directly served by the network entity based on an obstruction or structure, or the interior of a structure, etc.).

[0047] After relaying signaling between any served UE and a network entity, the repeater may send a report requesting a specific (e.g., improved or more accurate) number of beams (e.g., more beams or fewer beams than the number of SSBs initially provided). The UE may include a request for the number of beams or beam directions in the report, and the number of beams to be requested may be determined based on the served UE, service, coverage area, or spatial sensor, etc. Upon receiving an updated configuration of a number of beams, the repeater may receive more SSBs and relay them on the updated number of beams. Some advantages of the present disclosure may include implementing cell edge augmentation with a low complexity repeater.

[0048] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated and described by and with reference to wireless communication systems and process flows. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to repeater beam requests for transparent beam management.

[0049] Figure 1 An example of a wireless communication system 100 supporting a relay beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0050] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0051] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communications with other UEs 115 or network entities 105) as shown.

[0052] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

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

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

[0055] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 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 (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)). In some examples, the wireless communication system 100 may include a repeater 185. The repeater 185 may be an example of a relay device, a femtocell, a RIS, etc. The repeater 185 may extend coverage with limited (e.g., negligible) power consumption. The repeater 185 may be a nearly passive device or an active device, and may reflect an impinging wave in a desired direction. In some examples, the repeater 185 may be an example of a network entity 105. In some examples, the repeater 185 may facilitate communication between another network entity 105 and a UE 115.

[0056] The functional split between CU 160, DU 165, and RU 170 is flexible and may 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, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0057] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

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

[0059] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access, wireless self-backhaul capabilities for UE 115). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

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

[0061] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support relay beam requests for transparent beam management as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0063] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

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

[0065] In some examples (such as in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a stand-alone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

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

[0068] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to 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 coding rate of the modulation scheme, or both), so that a relatively higher number of resource elements (e.g., in the transmission duration) and a relatively higher order of the modulation scheme may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0069] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0070] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0071] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of a cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0072] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a certain amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0073] Physical channels may be multiplexed for communication using carriers according to various techniques. For example, physical control channels and physical data channels may be multiplexed for signaling via downlink carriers using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a symbol period set and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0075] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0076] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0077] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.

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

[0079] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0080] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication 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 commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0081] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may be unable or not configured to receive transmissions from the network entity 105 for other reasons. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0082] In some systems, the D2D communication link 135 can be an example of a communication channel such as a sidelink communication channel between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure such as roadside units using vehicle-to-network (V2N) communications, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0083] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transported by user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0084] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures for macro cells to provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0085] The wireless communication system 100 may also operate using a super high frequency (SHF) region (which may be in the range of 3 GHz to 30 GHz) (also referred to as a centimeter band) or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within a device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0086] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band to adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entities 105 and UE 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.

[0087] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the 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 sent via the antenna ports.

[0088] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0089] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0090] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the 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 sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by the network entity 105.

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

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

[0093] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive 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).

[0094] As described herein, a transmitting device (e.g., UE 115, network entity 105, repeater 185, or any other wireless node) may perform transmission, or may output wireless signaling. Similarly, a receiving device (e.g., UE 115, network entity 105, repeater 185, or any other wireless node) may perform reception, or may obtain wireless signaling. Outputting signaling may include outputting a set of bits to a modem or other device for modulation, encoding, and transmission, or may include outputting a modulated carrier to an amplifier for transmission through an antenna, or may include outputting a modulated carrier to an external device for transmission, etc. Obtaining signaling may include obtaining, receiving, or forwarding a set of bits to a modem of a device for demodulation and decoding, or may include obtaining a modulated carrier for reception via one or more antennas, or may include obtaining a modulated carrier at an external device (e.g., for decoding or for forwarding to a modem for decoding), etc.

[0095] In some examples, the UE 115 may report an initial ability to maintain a latency condition and a number of supported beams (e.g., a threshold number of beams that the UE 115 may support for relaying downlink communications (such as SSBs)) based on the specified latency condition. The network entity 105 may then send the SSBs, and may send a subset of the SSBs (e.g., multiple SSBs) directly to the repeater (e.g., on the same beam rather than on multiple beams). The repeater may relay the SSBs across multiple beams to provide service to a coverage area (e.g., a geographic area that is not directly served by the network entity 105 based on an obstruction or structure, or the interior of a structure, etc.). After relaying signaling between any served UE 115 and the network entity, the repeater may send a report requesting a specific (e.g., improved or more accurate) number of beams (e.g., more beams or fewer beams than the number of SSBs initially provided and relayed by the repeater). The UE 115 may include a request for the number of beams or beam directions in the report, and the number of beams to be requested may be determined based on the UE 115 being served, the service, the coverage area, or the spatial sensor, etc. Upon receiving an updated configuration of a number of beams, the repeater may receive more SSBs and relay them on the updated number of beams. Some advantages of the present disclosure may include achieving cell edge augmentation with a low complexity repeater.

[0096] Figure 2A An example of a wireless communication system 200 is illustrated, and Figure 2BAn example of a wireless communication system 201 that supports a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include one or more network entities 105 (e.g., network entity 105-a), one or more repeaters 210 (e.g., repeater 210-a), and one or more UEs 115 (e.g., UE 115-a and UE 115-b). The wireless communication system 201 may include one or more network entities 105 (e.g., network entity 105-b), one or more repeaters 210 (e.g., repeater 210-b), and one or more UEs 115 (e.g., UE 115-c).

[0097] Wireless devices in wireless communication system 200 or wireless communication system 201 may use LOS channels to communicate, which may result in improved coverage quality and increased throughput. However, in indoor or urban deployments, the availability of LOS channels may be limited. Therefore, the deployment may rely on one or more repeaters 210 (e.g., relay devices, femtocells, RISs, etc.) to relay signaling between wireless nodes. Relaying signaling may include penetrating windows or bypassing obstructions, such as Figure 2A and Figure 2B Both are shown.

[0098] In some examples, the relay 210 can maintain low latency communication between the UE 115 and the network entity 105 such that the UE channel delay spread satisfies a threshold (e.g., the channel delay spread of the UE 115 is maintained within the CP length). The relay 210 can also provide for a specific spatial region (e.g., as shown in FIG. Figure 2A The illustrated room 215, or as referenced Figure 2B The repeater 210 may support communications to multiple UEs 115. In some examples, the repeater 210 may represent a zero-delay repeater, which may be used to avoid low noise amplifier (LNA) oscillation transmission leakage. The repeater 210 may support isolation techniques, which may include physical separation of antennas, antenna polarization switching, active cancellation that may be based on analog cancellation, or any combination thereof.

[0099] Repeater 210 may not support digital processing of received SSBs sent on beam 205 (e.g., which may be derived from a relay low latency threshold (e.g., below the CP length)). In some examples, the conditions for the transparent beam management process may include the network entity 105a sending multiple beams 205 in the same direction of the repeater 210-a. The repeater 210-a may then relay the beam 205 received from the network entity 105a to a different spatial location (e.g., where the UE 115 is located). Although illustrated with reference to a single beam 205 carrying multiple SBSs, in some examples, the repeater 210 may receive multiple SBSs from a single TRP (e.g., a single network entity 105) or from multiple TRPs (e.g., in a multi-TRP (mTRP) deployment).

[0100] In some examples, to support low latency relaying by repeater 210, repeater 210 may perform a transparent beam management procedure (TBMP). In such examples, network entity 105 may send SSBs in different spatial directions, but may send multiple SSBs on a single beam 205 in the direction of repeater 210. In such examples, repeater 210 may then use multiple beams 205 to forward multiple received SSBs. In some examples, to support the transparent beam management procedure, repeater 210 may request a number of supported beams 205 (e.g., a threshold number of beams 205), and may then estimate and request an updated or more accurate number of requested beams 205, and network entity 105 may provide the requested number of SSBs on a single beam 205 to repeater 210, as described in reference to FIG. Figure 2A , Figure 2B and Figure 3 Describe in more detail.

[0101] As reference Figure 2A As illustrated, network entity 105-a, repeater 210-a, UE 115-a, and UE 115-b may perform an example of a transparent beam management process, which may be an example of an outdoor-to-indoor scenario. In some examples, UE 115-a and UE 115-b may be located in a geographic area (e.g., inside room 215) that does not support a LOS channel with network entity 105-a. Repeater 210-a may support a transparent beam management process with UE 115 and may relay signaling between network entity 105-a and UE 115 accordingly.

[0102] The network entity 105-a may transmit multiple SSBs on multiple beams 205. However, the network entity 105-a may transmit multiple SSBs on a single beam 205 to a repeater 210-a, which may be mounted on a surface (e.g., a window of a room 215). For example, the network entity 105-a may transmit SSB 0 on beam 205-a, may transmit SSB 1 on beam 205-a, may transmit SSB 6 on beam 205-d, and may transmit SSB 7 on beam 205-e. However, UE 115-a and UE 115-b may not receive signaling on beam 205-a, beam 205-b, beam 205-d, or beam 205-e. In some examples, UE 115-a and UE 115-b are also unable to directly receive signaling sent on beam 205-c (e.g., due to the walls of room 215 or the location of UE 115 within room 215). When performing a transparent beam management process, network entity 105-a may also send multiple SSBs (e.g., SSB 2 to SSB 5) on beam 205-c, which may be directed to repeater 210-a (e.g., beam indices associated with SSB 2, SSB3, SSB4, and SSB 5 may be spatially correlated). Repeater 210-a may then relay the received SSBs (e.g., SSB 2 to SSB5) to a coverage area that network entity 105 does not reach (e.g., room 215). For example, upon receiving SSB 2 to SSB 5 on beam 205-c, repeater 210-a may relay SSB 2 on beam 205-f, may relay SSB 3 on beam 205-g, may relay SSB 4 on beam 205-h, and may relay SSB 5 on beam 205-i. UE 115 in room 215 may receive at least one SSB, and UE 115 may perform a random access procedure with network entity 105-a based on the at least one SSB.

[0103] Figure 2B An example of a wireless communication system 201 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is illustrated. The wireless communication system 201 may include one or more network entities 105 (e.g., network entity 105-b), one or more repeaters 210 (e.g., repeater 210-b), and one or more UEs 115 (e.g., UE 115-c).

[0104] As reference Figure 2BAs illustrated, network entity 105-b, repeater 210-b, and UE 115-c may perform an example of a transparent beam management process, which may be an example of an outdoor-to-outdoor scenario. In some examples, UE 115-c may be located in a geographic area that does not support a LOS channel with network entity 105-b (e.g., the network entity may not be able to successfully communicate with UE 115-c using beam 205-n because UE 115-c is located on the opposite side of an obstruction such as structure 220-a). Repeater 210-b may support a transparent beam management process with UE 115-c and may relay signaling between network entity 105-a and UE 115-c accordingly.

[0105] The network entity 105b may transmit multiple SSBs on multiple beams 205. However, the network entity 105-b may transmit multiple SSBs on a single beam 205 to a repeater 210b, which may be mounted on a surface (e.g., structure 220-b) or another point within the wireless communication system 201. For example, the network entity 105-a may transmit SSB 0 on beam 205-j, may transmit SSB 1 on beam 205-k, may transmit SSB 5 on beam 205-m, and may transmit SSB 6 on beam 205-n. However, the UE 115-c may not receive signaling on beam 205-j, beam 205-k, beam 205-m, or beam 205-n (e.g., due to its location on an opposite side of the structure 220-a). In some examples, UE 115-c is also unable to directly receive signaling sent on beam 205-1 (e.g., due to the direction of beam 205-1, which is oriented toward repeater 210-b). When performing a transparent beam management process, network entity 105-b may also send multiple SSBs (e.g., SSB2 to SSB 4) on beam 205-1, which may be directed to repeater 210-a (e.g., beam indices associated with SSB 2, SSB3, and SSB4 may be spatially correlated). Repeater 210-b may then relay the received SSBs (e.g., SSB2 to SSB4) to a coverage area that network entity 105-b does not reach. For example, upon receiving SSB 2 to SSB 4 on beam 205-1, repeater 210-b may relay SSB 2 on beam 205-o, may relay SSB 3 on beam 205-p, and may relay SSB 4 on beam 205-q. UE 115-c located on an opposite side of an obstacle (e.g., such as structure 220-a) may receive at least one SSB (e.g., at least on beam 205-p), and UE 115-c may perform a random access procedure with network entity 105-b based on the at least one SSB.

[0106] The techniques described herein may support such transparent beam management procedures. However, without receiving information from the repeater 210 indicating the number of beams requested by the repeater 210 (e.g., the number of spatially related SSB indices of SSBs to be transmitted on a single beam toward a particular repeater 210), the network entity 105 may not be able to support such procedures. Figure 3 Described in more detail, the repeater 210 may send one or more reports (e.g., beam reports) indicating the number of requested beams of the repeater (e.g., the number of beams for the repeater 210 to deliver good spatial coverage to the captured area). As described herein, the repeater 210 may send a report of a threshold number of requested beams. The network entity 105 may then provide the requested number of SSBs in the direction of the repeater 210. The repeater 210 may then relay the SSBs to its coverage area and facilitate communication between one or more UEs 115 and the network entity 105. The repeater 210 may estimate the number of SSBs (e.g., the number of beams) to be requested from the network entity based on the actual coverage area, the number of UEs served in the coverage area, the number of random access resources utilized, etc. Based on the updated (e.g., more accurate) number of requested beams, the network entity 105 may send an updated number of SSBs to the repeater 210 for relaying to the UE 115.

[0107] Figure 3 An example of a process flow diagram 300 for supporting relay beam requests for transparent beam management in accordance with one or more aspects of the present disclosure is illustrated. The UE 115-d may be a Figure 1 2. The relay 310 may be as described in reference Figure 1 2 or 210. The network entity 105-c may be a network entity such as a relay 185 or a relay 210 as described in reference to FIG. Figure 1 2 .

[0108] At 305, the repeater 310 may establish a connection with the network entity 105-c and may send a repeater report or a capability report. The repeater report may include an indication of the latency capability and the number of beams supported by the repeater. For example, the repeater report may include in the report an indication of the repeater 310's ability to relay signals according to a threshold latency (e.g., less than the CP length). In some examples, the repeater report may include in the report a threshold number of beams that the repeater 310 may receive or transmit (e.g., a maximum number of beams). The indication of the threshold number of beams may be based on one or more conditions or parameter values, such as hardware limitations or capabilities at the repeater 310, or coverage limitations (e.g., the size of the geographic coverage area, which may be a small area).

[0109] At the repeater 310, the network entity 105-c may send, and the repeater 310 may receive, an indication of the set of SSB indices. The repeater 310 may determine a time opportunity for receiving each SSB in the set of one or more SSBs based at least in part on the indication of the set of SSB indices.

[0110] At 315, via the first beam, the network entity 105-c may send and the repeater 310 may receive one or more SSBs, each of the one or more SSBs corresponding to a corresponding SSB index (e.g., an SSB index indicated at the repeater 310). In some examples, the number of the one or more SSBs may satisfy (e.g., may be less than or equal to) the number of beams supported by the repeater 310. For example, the network entity 105-c may send multiple SSBs toward the repeater 310 using a single beam (e.g., in a single direction). Each SSB may be associated with a different SSB index for transparent beam management. In some examples, the UE 115-d may communicate directly with the network (via the repeater 310), but without establishing an independent communication link with the repeater 310 (e.g., without recognizing the presence of the repeater, or part of the communication link).

[0111] At 320, repeater 310 may relay one or more SSBs via a first set of beams associated with a coverage area served by repeater 310. In some examples, repeater 310 may relay the SSB beams in different spatial directions according to a beam management algorithm. Repeater 310 may relay the SSB beams to one or more UEs 115 (e.g., including UE 115-d). The beam management algorithm may improve coverage of the deployed area.

[0112] At 325, the repeater 310 may receive and send information from the UE 115-d. At 330, the network entity 105-c may receive and send information from the repeater 310. Thus, based at least in part on relaying the one or more SSBs, the repeater 310 may relay signaling from the network entity 105-c to one or more UEs 115 served by the repeater 310, and relay signaling from one or more UEs 115 (e.g., including UE 115-d) to the network entity 105-c. The relaying may include receiving a random access message associated with a corresponding SSB index of the one or more SSBs from one or more UEs 115 (e.g., including UE 115-d) using a first set of beams, and relaying the received random access message to the network entity 105-c (e.g., using the first beam). The repeater 310 may also relay data from and to the network entity 105-c. The relayed information may include control signaling and data signaling from and to UE 115-d.

[0113] At 335, the repeater 310 may estimate the number of beams to be used for subsequent communications with the network entity 105-c (e.g., the updated number of beams). For example, the repeater 310 may indicate a threshold number of beams supported by the repeater 310 at 305, but may determine that the repeater 310 may use fewer beams (e.g., based on a small coverage area, a limited number of UEs within the coverage area, etc.). For example, the repeater 310 may estimate the number of beams in the second set of beams (e.g., different from the first set of beams used to relay SSBs at 320) based at least in part on the number of random access opportunities associated with random access messages relayed by the repeater 310 from one or more UEs 115 to the network entity 105-c, the number of UEs 115 located in the coverage area served by the repeater 310, the spatial spacing between corresponding beams in the first set of beams, or a combination thereof. In some examples, the estimated number of beams may be a preferred or supported number of beams based on previous communications or other conditions. In some examples, the repeater 310 may estimate the number of beams in the second set of beams based on the size of the served or captured area. The size of the captured coverage area may be determined based on dedicated sensing hardware or sensors at the repeater 310, may be preconfigured by an installer, may be based on a history of active UEs 115 and respective locations of the UEs 115, transmitted SSB reception, or any combination thereof. In some examples, the repeater 310 may estimate the number of beams in the second set of beams based on the spatial separation between the beams (e.g., which may define a threshold signal to interference and noise ratio (SINR) for each UE 115), and may be based at least in part on the radio frequency architecture, a departure angle of the desired beam, or a combination thereof.

[0114] At 340, based at least in part on relaying one or more SSBs via the first beam set, the repeater 310 may send, and the network entity 105-c may receive, a repeater report (e.g., a beam report) including an indication of a second beam set associated with service to one or more UEs 115 located in a coverage area served by the repeater 310. The repeater 310 may request (e.g., in the repeater report at 340) the number of beams of the second beam set estimated at 335. The repeater report may include a request for the second beam set, a periodicity of the second beam set, a threshold time between duplicate beams of the first beam set, a number of beams, or a minimum or maximum time between duplicate beams, or a combination thereof. The repeater report may be based on an RRC or MAC CE message (e.g., in an example where the report changes slowly).

[0115] At 345, based at least in part on sending the repeater report, the network entity 105-c may send, and the repeater 310 may receive, a beam assignment message including beam information for a second beam set. In some examples, the beam assignment message may include an indication of a number of beams for the second beam set, an indication of a beam direction for each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set. The beam assignment message may update the repeater 310 with the number of beams and the direction of each beam. In some examples, one or more beams may have the same angle of arrival (AOA). In some other examples, the number of the first beam set and the number of the second beam set may be the same number, and the network entity 105-c may signal the beam assignment message including a one-bit message indicating that the second beam set is the same as the first beam set.

[0116] At 350, the repeater 310 may receive a second set of one or more SSBs via the first beam, each SSB in the second set of one or more SSBs corresponding to a corresponding SSB index, and a number of the second set of one or more SSBs may satisfy the second set of beams, and relay the set of one or more SSBs via the second set of beams. The repeater 310 may transmit a number of beams as configured by the network entity 105-c.

[0117] Figure 4 A block diagram 400 of a device 405 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of a repeater (e.g., repeater 185, repeater 210, or repeater 310) as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0118] Receiver 410 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 405. In some examples, receiver 410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0119] The transmitter 415 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 405. For example, the transmitter 415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 415 and the receiver 410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0120] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of repeater beam requests for transparent beam management as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0121] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0122] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0123] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or be integrated with receiver 410, transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0124] According to examples as disclosed herein, the communication manager 420 may support wireless communications at a repeater. For example, the communication manager 420 may be configured to or otherwise support a component for sending a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The communication manager 420 may be configured to or otherwise support a component for receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. The communication manager 420 may be configured to or otherwise support a component for relaying a set of multiple SSBs via a first beam set associated with a coverage area served by the repeater. The communication manager 420 may be configured to or otherwise support a component for sending a repeater report including an indication of a second beam set associated with a service to one or more UEs located in the coverage area served by the repeater based on relaying a set of multiple SSBs via a first beam set.

[0125] By including or configuring a communication manager 420 according to examples as described herein, a device 405 (e.g., a processor controlling or otherwise coupled to a receiver 410, a transmitter 415, a communication manager 420, or a combination thereof) may support techniques for a transparent beamforming process that result in, among other things, reduced processing, reduced power consumption, and more efficient use of communication resources.

[0126] Figure 5 A block diagram 500 of a device 505 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The device 505 can be an example of aspects of the device 405 or a repeater (e.g., repeater 185, repeater 210, or repeater 310) as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0127] The receiver 510 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 505. In some examples, the receiver 510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0128] The transmitter 515 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 505. For example, the transmitter 515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 515 and the receiver 510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0129] The device 505 or its various components may be examples of components for performing various aspects of repeater beam requests for transparent beam management as described herein. For example, the communication manager 520 may include a capability report manager 525, an SSB manager 530, a repeater report manager 535, or any combination thereof. The communication manager 520 may be an example of various aspects of the communication manager 420 as described herein. In some examples, the communication manager 520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 510, the transmitter 515, or both. For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0130] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a repeater. The capability report manager 525 may be configured to or otherwise support a component for sending a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The SSB manager 530 may be configured to or otherwise support a component for receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. The SSB manager 530 may be configured to or otherwise support a component for relaying a set of multiple SSBs via a first set of beams associated with a coverage area served by the repeater. The repeater report manager 535 may be configured to or otherwise support a component for sending a repeater report including an indication of a second set of beams associated with a service to one or more UEs located in the coverage area served by the repeater based on relaying a set of multiple SSBs via a first set of beams.

[0131] Figure 6 A block diagram 600 of a communication manager 620 supporting repeater beam requests for transparent beam management according to one or more aspects of the present disclosure is shown. The communication manager 620 can be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components can be examples of means for performing various aspects of the repeater beam requests for transparent beam management as described herein. For example, the communication manager 620 can include a capability reporting manager 625, an SSB manager 630, a repeater reporting manager 635, a beam assignment manager 640, a beam estimation manager 645, a relay manager 650, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0132] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a repeater. The capability report manager 625 may be configured to or otherwise support a component for sending a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The SSB manager 630 may be configured to or otherwise support a component for receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. In some examples, the SSB manager 630 may be configured to or otherwise support a component for relaying a set of multiple SSBs via a first beam set associated with a coverage area served by the repeater. The repeater report manager 635 may be configured to or otherwise support a component for sending a repeater report including an indication of a second beam set associated with a service to one or more UEs located in the coverage area served by the repeater based on relaying a set of multiple SSBs via a first beam set.

[0133] In some examples, beam assignment manager 640 can be configured or otherwise support means for receiving a beam assignment message including beam information for a second set of beams based on transmitting a relay report.

[0134] In some examples, to support beam assignment messages, the beam assignment manager 640 may be configured to or otherwise support components for: an indication of a number of beams in a second beam set, an indication of a beam direction for each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set.

[0135] In some examples, to support beam assignment messages, beam assignment manager 640 can be configured or otherwise support means for: a one-bit message indicating that the second set of beams is the same as the first set of beams.

[0136] In some examples, the SSB manager 630 may be configured to or otherwise support means for receiving a second set of multiple SSBs via the first beam, each SSB in the second set of multiple SSBs corresponding to a respective SSB index, wherein the number of the second set of multiple SSBs satisfies the second beam set. In some examples, the SSB manager 630 may be configured to or otherwise support means for relaying the second set of multiple SSBs via the second beam set.

[0137] In some examples, to support repeater reporting, the repeater reporting manager 635 may be configured to or otherwise support components for: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between duplicate beams of the first beam set, or a combination thereof.

[0138] In some examples, the beam estimation manager 645 may be configured to or otherwise support components for estimating the number of beams of the second beam set based on: the number of random access opportunities associated with random access messages relayed by the repeater from one or more UEs to a network entity, the number of UEs located in the coverage area served by the repeater, the spatial spacing between corresponding beams in the first beam set, or a combination thereof, wherein sending the repeater report is based on the estimate.

[0139] In some examples, the beam estimation manager 645 may be configured to or otherwise support means for determining a size of a coverage area served by the repeater based on one or more sensors, a preconfigured area input by a user, a history of locations of one or more UEs served by the repeater, a number of messages received from one or more UEs based on relaying a set of multiple SSBs, or a combination thereof. In some examples, the beam estimation manager 645 may be configured to or otherwise support means for estimating a number of beams of a second set of beams based on a size of a coverage area served by the repeater, wherein sending the repeater report is based on the estimation.

[0140] In some examples, relay manager 650 may be configured or otherwise support components for relaying signaling from a network entity to one or more UEs served by the relay based on relaying a set of multiple SSBs and relaying signaling from one or more UEs to the network entity.

[0141] In some examples, to support relaying, the relay manager 650 may be configured to or otherwise support means for receiving, from one or more UEs, random access messages associated with respective SSB indices of a set of multiple SSBs using a first set of beams. In some examples, to support relaying, the relay manager 650 may be configured to or otherwise support means for relaying the received random access message to a network entity using the first beam.

[0142] In some examples, the SSB manager 630 may be configured or otherwise support means for receiving, from a network entity, an indication of a set of SSB indices including each respective SSB index corresponding to each SSB in a set of multiple SSBs. In some examples, the SSB manager 630 may be configured or otherwise support means for determining a time opportunity for receiving each SSB in a set of multiple SSBs based on the indication of the set of SSB indices, wherein receiving the set of multiple SSBs is based on determining.

[0143] Figure 7 A diagram of a system 700 including a device 705 supporting repeater beam requests for transparent beam management according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a repeater (e.g., repeater 185, repeater 210, or repeater 310) as described herein or include components thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, a transceiver 710, an antenna 715, a memory 725, code 730, and a processor 735. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 740).

[0144] The transceiver 710 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 705 may include one or more antennas 715 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 710 may also include a modem for modulating a signal, providing a modulated signal for transmission (e.g., via one or more antennas 715, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 715, from a wired receiver), and demodulating a signal. The transceiver 710 or transceiver 710 and one or more antennas 715 or wired interfaces (where applicable) may be examples of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0145] The memory 725 may include RAM and ROM. The memory 725 may store computer-readable, computer-executable code 730 including instructions that, when executed by the processor 735, cause the device 705 to perform various functions described herein. The code 730 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 730 may not be directly executable by the processor 735, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, in addition to this, the memory 725 may also include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0146] The processor 735 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 735 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 735. The processor 735 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 725) to enable the device 705 to perform various functions (e.g., functions or tasks supporting a repeater beam request for transparent beam management). For example, the device 705 or a component of the device 705 may include a processor 735 and a memory 725 coupled to the processor 735, and the processor 735 and the memory 725 are configured to perform various functions described herein. The processor 735 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 730) to perform the functions of the device 705.

[0147] In some examples, bus 740 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 740 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 705, or communications performed between different components of device 705 that may be co-located or located in different locations (e.g., where device 705 may refer to a system in which one or more of communication manager 720, transceiver 710, memory 725, code 730, and processor 735 may be located in one of the different components or divided between the different components).

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

[0149] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a repeater. For example, the communication manager 720 may be configured to or otherwise support a component for sending a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The communication manager 720 may be configured to or otherwise support a component for receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. The communication manager 720 may be configured to or otherwise support a component for relaying a set of multiple SSBs via a first beam set associated with a coverage area served by the repeater. The communication manager 720 may be configured to or otherwise support a component for sending a repeater report including an indication of a second beam set associated with a service to one or more UEs located in the coverage area served by the repeater based on relaying a set of multiple SSBs via a first beam set.

[0150] By including or configuring a communication manager 720 according to the examples described herein, the device 705 may support techniques for a transparent beamforming process resulting in improved communication reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing power, etc.

[0151] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 710, one or more antennas 715 (e.g., where applicable), or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 735, the memory 725, the code 730, the transceiver 710, or any combination thereof. For example, the code 730 may include instructions that are executable by the processor 735 to cause the device 705 to perform various aspects of the repeater beam request for transparent beam management as described herein, or the processor 735 and the memory 725 may be otherwise configured to perform or support such operations.

[0152] Figure 8 A block diagram 800 of a device 805 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0153] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0154] The transmitter 815 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0155] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of repeater beam requests for transparent beam management as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0156] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0157] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0158] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0159] According to the examples disclosed herein, the communication manager 820 may support wireless communication at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for obtaining a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The communication manager 820 may be configured to or otherwise support a component for outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The communication manager 820 may be configured to or otherwise support a component for obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs. The communication manager 820 may be configured to or otherwise support a component for obtaining a repeater report including an indication of a second beam set associated with a service to one or more UEs located in a coverage area served by the repeater.

[0160] By including or configuring a communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) may support techniques for a transparent beamforming process that result in, among other things, reduced processing, reduced power consumption, and more efficient use of communication resources.

[0161] Fig. 9 A block diagram 900 of a device 905 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0163] The transmitter 915 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0164] The device 905 or its various components may be examples of components for performing various aspects of repeater beam requests for transparent beam management as described herein. For example, the communication manager 920 may include a capability report manager 925, an SSB manager 930, a relay manager 935, a repeater report manager 940, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0165] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a network entity. The capability report manager 925 may be configured to or otherwise support a component for obtaining a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The SSB manager 930 may be configured to or otherwise support a component for outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The relay manager 935 may be configured to or otherwise support a component for obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs. The relay report manager 940 may be configured to or otherwise support a component for obtaining a relay report including an indication of a second beam set associated with a service to one or more UEs located in a coverage area served by the repeater.

[0166] Fig.10 A block diagram 1000 of a communication manager 1020 supporting repeater beam requests for transparent beam management according to one or more aspects of the present disclosure is shown. The communication manager 1020 can be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components can be examples of means for performing various aspects of the repeater beam requests for transparent beam management as described herein. For example, the communication manager 1020 can include a capability reporting manager 1025, an SSB manager 1030, a relay manager 1035, a repeater reporting manager 1040, a beam assignment manager 1045, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0167] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The capability report manager 1025 may be configured to or otherwise support a component for obtaining a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The SSB manager 1030 may be configured to or otherwise support a component for outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The relay manager 1035 may be configured to or otherwise support a component for obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting the set of multiple SSBs. The relay report manager 1040 may be configured to or otherwise support a component for obtaining a relay report including an indication of a second beam set associated with a service to one or more UEs located in a coverage area served by the repeater.

[0168] In some examples, beam assignment manager 1045 can be configured to or otherwise support means for outputting a beam assignment message including beam information for a second set of beams based on obtaining the repeater report.

[0169] In some examples, to support beam assignment messages, the beam assignment manager 1045 may be configured to or otherwise support components for: an indication of a number of beams in a second beam set, an indication of a beam direction for each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set.

[0170] In some examples, to support beam assignment messages, the beam assignment manager 1045 can be configured or otherwise support means for: a one-bit message indicating that the second set of beams is the same as the first set of beams.

[0171] In some examples, the SSB manager 1030 may be configured to or otherwise support components for outputting a second set of multiple SSBs via a second beam, each SSB in the second set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of the second set of multiple SSBs satisfies the second beam set.

[0172] In some examples, to support repeater reporting, the repeater reporting manager 1040 may be configured to or otherwise support components for: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between duplicate beams of the first beam set, or a combination thereof.

[0173] In some examples, to support repeater reporting, the repeater reporting manager 1040 may be configured to or otherwise support components for: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between duplicate beams of the first beam set, or a combination thereof.

[0174] In some examples, the SSB manager 1030 may be configured to or otherwise support components for outputting an indication of a set of SSB indexes including each respective SSB index corresponding to each SSB in a set of multiple SSBs, wherein outputting the set of multiple SSBs is based on the indication of the set of SSB indexes.

[0175] Fig.11 A diagram of a system 1100 including a device 1105 supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0176] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, providing a modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and demodulating a signal. The transceiver 1110 or transceiver 1110 and one or more antennas 1115 or wired interfaces (where applicable) may be examples of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0177] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 1125 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks to support repeater beam requests for transparent beam management). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1130) to perform the functions of device 1105.

[0179] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of the different components or divided between the different components).

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

[0181] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for obtaining a capability report, the capability report including an indication of latency capability and the number of beams supported by the repeater. The communication manager 1120 may be configured to or otherwise support a component for outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The communication manager 1120 may be configured to or otherwise support a component for obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based on outputting a set of multiple SSBs. The communication manager 1120 may be configured to or otherwise support a component for obtaining a repeater report including an indication of a second beam set associated with a service to one or more UEs located in a coverage area served by the repeater.

[0182] By including or configuring a communication manager 1120 according to the examples described herein, the device 1105 may support techniques for a transparent beamforming process resulting in improved communication reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing power, etc.

[0183] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of the repeater beam request for transparent beam management as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0184] Fig.12 A flow chart illustrating a method 1200 for supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a repeater or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a repeater or a component thereof as described herein. Figures 1 to 7In some examples, the repeater may execute an instruction set to control the functional elements of the repeater to perform the functions described. Additionally or alternatively, the repeater may use dedicated hardware to perform various aspects of the functions described.

[0185] At 1205, the method may include sending a capability report including an indication of latency capability and the number of beams supported by the repeater. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 6 The described capability reporting manager 625 is executed.

[0186] At 1210, the method may include receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference Figure 6 The described SSB manager 630 is executed.

[0187] At 1215, the method may include relaying a set of multiple SSBs via a first set of beams associated with a coverage area served by the repeater. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 6 The described SSB manager 630 is executed.

[0188] At 1220, the method may include sending a relay report including an indication of a second beam set associated with service to one or more UEs located in a coverage area served by the relay based on relaying a set of multiple SSBs via a first beam set. The operations of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed as described in reference to Figure 6 The described repeater report manager 635 is executed.

[0189] Fig.13 A flow chart illustrating a method 1300 for supporting a repeater beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a repeater or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a repeater or a component thereof as described herein. Figures 1 to 7 In some examples, the repeater may execute an instruction set to control the functional elements of the repeater to perform the functions described. Additionally or alternatively, the repeater may use dedicated hardware to perform various aspects of the functions described.

[0190] At 1305, the method may include sending a capability report including an indication of latency capability and the number of beams supported by the repeater. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 6 The described capability reporting manager 625 is executed.

[0191] At 1310, the method may include receiving a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs satisfies the number of beams supported by the repeater. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference Figure 6 The described SSB manager 630 is executed.

[0192] At 1315, the method may include relaying a set of multiple SSBs via a first set of beams associated with a coverage area served by the repeater. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 6 The described SSB manager 630 is executed.

[0193] At 1320, the method may include sending a relay report including an indication of a second beam set associated with service to one or more UEs located in a coverage area served by the relay based on relaying a set of multiple SSBs via a first beam set. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 6 The described repeater report manager 635 is executed.

[0194] At 1325, the method may include receiving a beam assignment message including beam information of a second set of beams based on the transmitted relay report. The operations of 1325 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1325 may be performed as described in reference to Figure 6 The beam assignment manager 640 described herein is performed.

[0195] Fig.14 A flow chart illustrating a method 1400 for supporting a relay beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 as well as Figures 8 to 11In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0196] At 1405, the method may include obtaining a capability report including an indication of latency capability and a number of beams supported by the repeater. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.10 The described capability reporting manager 1025 is executed.

[0197] At 1410, the method may include outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference Fig.10 The described SSB manager 1030 is executed.

[0198] At 1415, the method may include obtaining one or more uplink messages from one or more UEs served by the relay via the relay based on outputting the set of multiple SSBs. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.10 The relay manager 1035 is used to execute.

[0199] At 1420, the method may include obtaining a relay report including an indication by the relay of a second beam set associated with service to one or more UEs located in a coverage area served by the relay. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Fig.10 The described repeater report manager 1040 is executed.

[0200] Fig.15 A flow chart illustrating a method 1500 for supporting a relay beam request for transparent beam management according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 as well as Figures 8 to 11In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0201] At 1505, the method may include obtaining a capability report including an indication of latency capability and a number of beams supported by the repeater. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.10 The described capability reporting manager 1025 is executed.

[0202] At 1510, the method may include outputting a set of multiple SSBs via a first beam, each SSB of the set of multiple SSBs corresponding to a corresponding SSB index, wherein the number of sets of multiple SSBs corresponds to the number of beams of the first beam set that satisfies the number of beams supported by the repeater. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference Fig.10 The described SSB manager 1030 is executed.

[0203] At 1515, the method may include obtaining one or more uplink messages from one or more UEs served by the relay via the relay based on outputting the set of multiple SSBs. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.10 The relay manager 1035 is used to execute.

[0204] At 1520, the method may include obtaining a relay report including an indication by the relay of a second set of beams associated with service to one or more UEs located in a coverage area served by the relay. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.10 The described repeater report manager 1040 is executed.

[0205] At 1525, the method may include outputting a beam assignment message including beam information of a second set of beams based on obtaining the repeater report. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Fig.10 The beam assignment manager 1045 described above is executed.

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

[0207] Aspect 1: A method for wireless communication at a repeater, the method comprising: sending a capability report, the capability report comprising an indication of latency capability and the number of beams supported by the repeater; receiving a plurality of SSBs via a first beam, each of the plurality of SSBs corresponding to a corresponding SSB index, wherein the number of the plurality of SSBs satisfies the number of beams supported by the repeater; relaying the plurality of SSBs via a first beam set associated with a coverage area served by the repeater; and sending a repeater report comprising an indication of a second beam set associated with service to one or more UEs located in the coverage area served by the repeater based at least in part on relaying the plurality of SSBs via the first beam set.

[0208] Aspect 2: The method according to aspect 1 further includes: receiving a beam assignment message including beam information of the second set of beams based at least in part on sending the relay report.

[0209] Aspect 3: A method according to Aspect 2, wherein the beam assignment message includes: an indication of the number of beams of the second beam set, an indication of the beam direction of each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set.

[0210] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the beam assignment message comprises: a one-bit message indicating that the second beam set is the same as the first beam set.

[0211] Aspect 5: An apparatus according to any one of Aspects 2 to 4, the apparatus further comprising: receiving a second plurality of SSBs via the first beam, each SSB in the second plurality of SSBs corresponding to a corresponding SSB index, wherein the number of the second plurality of SSBs satisfies the second beam set; and relaying the second plurality of SSBs via the second beam set.

[0212] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the repeater report includes: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between replicated beams of the first beam set, or a combination thereof.

[0213] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method also includes: estimating the number of beams of the second beam set based at least in part on: the number of random access opportunities associated with the random access message relayed by the relay from the one or more UEs to the network entity, the number of UEs located in the coverage area served by the relay, the spatial interval between the corresponding beams in the first beam set, or a combination thereof, wherein sending the relay report is at least in part based on estimating the number of beams.

[0214] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: determining the size of the coverage area served by the repeater based at least in part on: one or more sensors, a preconfigured area input by a user, a history of the locations of the one or more UEs served by the repeater, a number of messages received from the one or more UEs based on relaying the multiple SSBs, or a combination thereof; and estimating the number of beams of the second beam set based at least in part on the size of the coverage area served by the repeater, wherein sending the repeater report is based at least in part on estimating the number of beams.

[0215] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method also includes: at least partially based on relaying the multiple SSBs, relaying signaling from the network entity to one or more UEs served by the relay and relaying signaling from the one or more UEs to the network entity.

[0216] Aspect 10: A method according to Aspect 9, wherein relaying the signaling from the network entity to the one or more UEs and relaying the signaling from the one or more UEs to the network entity includes: receiving a random access message associated with the corresponding SSB index of the multiple SSBs from the one or more UEs using the first beam set; and relaying the received random access message to the network entity using the first beam.

[0217] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving an indication of an SSB index set including each corresponding SSB index corresponding to each SSB in the multiple SSBs from a network entity; and determining a time opportunity for receiving each SSB in the multiple SSBs based at least in part on the indication of the SSB index set, wherein receiving the multiple SSBs is based at least in part on the determination.

[0218] Aspect 12: A method for performing wireless communications at a network entity, the method comprising: obtaining a capability report, the capability report comprising an indication of latency capability and the number of beams supported by a repeater; outputting a plurality of SSBs via a first beam, each of the plurality of SSBs corresponding to a corresponding SSB index, wherein the number of the plurality of SSBs corresponds to the number of beams of a first beam set that satisfies the number of beams supported by the repeater; obtaining one or more uplink messages from one or more UEs served by the repeater via the repeater based at least in part on outputting the plurality of SSBs; and obtaining a repeater report comprising an indication of the repeater for a second beam set associated with service to one or more user equipment (UE) located in a coverage area served by the repeater.

[0219] Aspect 13: The method according to aspect 12 further comprises: outputting a beam assignment message including beam information of the second set of beams based at least in part on obtaining the relay report.

[0220] Aspect 14: A method according to Aspect 13, wherein the beam assignment message includes: an indication of the number of beams of the second beam set, an indication of the beam direction of each beam in the second beam set, or a combination thereof, wherein the second beam set is different from the first beam set.

[0221] Aspect 15: The method according to any one of Aspects 13 to 14, wherein the beam assignment message comprises: a one-bit message indicating that the second beam set is the same as the first beam set.

[0222] Aspect 16: A method according to any one of Aspects 13 to 15, wherein the method further comprises: outputting a second plurality of SSBs via a second beam, each SSB in the second plurality of SSBs corresponding to a corresponding SSB index, wherein the number of the second plurality of SSBs satisfies the second beam set.

[0223] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the repeater report includes: the number of beams of the second beam set, the periodicity of the second beam set, the threshold time between replicated beams of the first beam set, or a combination thereof.

[0224] Aspect 18: According to any one of Aspects 12 to 17, the method further includes: outputting an indication of an SSB index set including each corresponding SSB index corresponding to each SSB in the multiple SSBs, wherein outputting the multiple SSBs is at least partially based on outputting the indication of the SSB index set.

[0225] Aspect 19: An apparatus for wireless communication at a repeater, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 11.

[0226] Aspect 20: An apparatus for wireless communication at a relay, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 11.

[0227] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication at a relay, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0228] Aspect 22: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 12 to 18.

[0229] Aspect 23: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 12 to 18.

[0230] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 18.

[0231] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0232] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0234] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The 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 in conjunction with a DSP core, or any other such configuration).

[0235] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using them. 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 may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0236] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates the transmission of computer program from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0237] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0238] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0239] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0240] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0241] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present 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. An apparatus for wireless communication at a repeater, the apparatus comprising: processor; a memory in electronic communication with the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to: sending a capability report, the capability report including an indication of latency capability and a number of beams supported by the repeater; Receiving a plurality of synchronization signal blocks via a first beam, each synchronization signal block in the plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the plurality of synchronization signal blocks satisfies the number of beams supported by the repeater; relaying the plurality of synchronization signal blocks via a first set of beams associated with a coverage area served by the repeater; as well as A relay report including an indication of a second beam set associated with service to one or more user equipment (UE) located in the coverage area served by the relay is sent based at least in part on relaying the plurality of synchronization signal blocks via the first beam set.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to: A beam assignment message including beam information for the second set of beams is received based at least in part on sending the relay report.

3. The apparatus according to claim 2, wherein the beam assignment message comprises: An indication of a number of beams of the second set of beams, an indication of a beam direction of each beam in the second set of beams, or a combination thereof, wherein the second set of beams is different from the first set of beams.

4. The apparatus according to claim 2, wherein the beam assignment message comprises: A one-bit message indicating that the second set of beams is the same as the first set of beams.

5. The apparatus of claim 2, wherein the instructions are further executable by the processor to: receiving a second plurality of synchronization signal blocks via the first beam, each synchronization signal block in the second plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the second plurality of synchronization signal blocks satisfies the second beam set; and The second plurality of synchronization signal blocks are relayed via the second set of beams.

6. The apparatus of claim 1, wherein the repeater report comprises: The number of beams of the second set of beams, the periodicity of the second set of beams, the threshold time between duplicate beams of the first set of beams, or a combination thereof.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to: The number of beams of the second beam set is estimated at least in part based on: the number of random access opportunities associated with random access messages relayed by the repeater from the one or more UEs to a network entity, the number of UEs located in the coverage area served by the repeater, the spatial spacing between corresponding beams in the first beam set, or a combination thereof, wherein the instructions executable by the processor to send the repeater report are at least in part based on the instructions executable by the processor to estimate the number of beams.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to: determining a size of the coverage area served by the repeater based at least in part on: one or more sensors, a preconfigured area input by a user, a history of locations of the one or more UEs served by the repeater, a number of messages received from the one or more UEs based on relaying the plurality of synchronization signal blocks, or a combination thereof; and The number of beams of the second set of beams is estimated based at least in part on the size of the coverage area served by the repeater, wherein the instructions executable by the processor to send the repeater report are based at least in part on the instructions executable by the processor to estimate the number of beams.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to: Based at least in part on relaying the plurality of synchronization signal blocks, signaling is relayed from a network entity to one or more UEs served by the relay and signaling is relayed from the one or more UEs to the network entity.

10. The apparatus of claim 9, wherein the instructions executable by the processor to relay the signaling from the network entity to the one or more UEs and relay the signaling from the one or more UEs to the network entity comprise instructions executable by the processor to: receiving, from the one or more UEs, a random access message associated with a corresponding synchronization signal block index of the plurality of synchronization signal blocks using the first set of beams; and The received random access message is relayed to the network entity using the first beam.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to: receiving, from a network entity, an indication of a set of synchronization signal block indices, the set of synchronization signal block indices comprising each respective synchronization signal block index corresponding to each synchronization signal block of the plurality of synchronization signal blocks; and A time opportunity for receiving each of the multiple synchronization signal blocks is determined at least in part based on the indication of the synchronization signal block index set, wherein the instructions executable by the processor to receive the multiple synchronization signal blocks are at least in part based on the instructions executable by the processor to determine the time opportunity.

12. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory in electronic communication with the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to: obtaining a capability report, the capability report including an indication of a delay capability and a number of beams supported by the repeater; Outputting a plurality of synchronization signal blocks via a first beam, each synchronization signal block in the plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the plurality of synchronization signal blocks corresponds to the number of beams of a first beam set satisfying the number of beams supported by the repeater; obtaining, via the relay, one or more uplink messages from one or more user equipments (UEs) served by the relay based at least in part on outputting the plurality of synchronization signal blocks; as well as A relay report is obtained that includes an indication by the relay of a second set of beams associated with service to one or more user equipment (UEs) located in a coverage area served by the relay.

13. The apparatus of claim 12, wherein the instructions are further executable by the processor to: Outputting a beam assignment message including beam information for the second set of beams based at least in part on obtaining the repeater report.

14. The apparatus according to claim 13, wherein the beam assignment message comprises: An indication of a number of beams of the second set of beams, an indication of a beam direction of each beam in the second set of beams, or a combination thereof, wherein the second set of beams is different from the first set of beams.

15. The apparatus of claim 13, wherein the beam assignment message comprises: A one-bit message indicating that the second set of beams is the same as the first set of beams.

16. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: A second plurality of synchronization signal blocks is output via a second beam, each synchronization signal block in the second plurality of synchronization signal blocks corresponds to a corresponding synchronization signal block index, wherein the number of the second plurality of synchronization signal blocks satisfies the second beam set.

17. The apparatus of claim 12, wherein the repeater report comprises: The number of beams of the second set of beams, the periodicity of the second set of beams, the threshold time between duplicate beams of the first set of beams, or a combination thereof.

18. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: Outputting an indication of a set of synchronization signal block indices, the set of synchronization signal block indices including each respective synchronization signal block index corresponding to each of the plurality of synchronization signal blocks, wherein the instructions executable by the processor to output the plurality of synchronization signal blocks are based at least in part on the instructions executable by the processor to output the indication of the set of synchronization signal block indices.

19. A method for wireless communication at a repeater, the method comprising: sending a capability report, the capability report including an indication of latency capability and a number of beams supported by the repeater; Receiving a plurality of synchronization signal blocks via a first beam, each synchronization signal block in the plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the plurality of synchronization signal blocks satisfies the number of beams supported by the repeater; relaying the plurality of synchronization signal blocks via a first set of beams associated with a coverage area served by the repeater; as well as A relay report including an indication of a second beam set associated with service to one or more user equipment (UE) located in the coverage area served by the relay is sent based at least in part on relaying the plurality of synchronization signal blocks via the first beam set.

20. The method according to claim 19, further comprising: A beam assignment message including beam information for the second set of beams is received based at least in part on sending the relay report.

21. The method according to claim 20, further comprising: receiving a second plurality of synchronization signal blocks via the first beam, each synchronization signal block in the second plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the second plurality of synchronization signal blocks satisfies the second beam set; and The second plurality of synchronization signal blocks are relayed via the second set of beams.

22. The method of claim 19, wherein the repeater report comprises: The number of beams of the second set of beams, the periodicity of the second set of beams, the threshold time between duplicate beams of the first set of beams, or a combination thereof.

23. The method according to claim 19, further comprising: The number of beams of the second beam set is estimated at least in part based on: the number of random access opportunities associated with random access messages relayed by the relay from the one or more UEs to a network entity, the number of UEs located in the coverage area served by the relay, the spatial spacing between corresponding beams in the first beam set, or a combination thereof, wherein sending the relay report is based at least in part on the estimate.

24. The method according to claim 19, further comprising: determining a size of the coverage area served by the repeater based at least in part on: one or more sensors, a preconfigured area input by a user, a history of locations of the one or more UEs served by the repeater, a number of messages received from the one or more UEs based on relaying the plurality of synchronization signal blocks, or a combination thereof; as well as A number of beams of the second set of beams is estimated based at least in part on the size of the coverage area served by the relay, wherein sending the relay report is based at least in part on the estimation.

25. The method of claim 19, further comprising: Based at least in part on relaying the plurality of synchronization signal blocks, signaling is relayed from a network entity to one or more UEs served by the relay and signaling is relayed from the one or more UEs to the network entity.

26. The method of claim 25, wherein the relaying comprises: receiving, from the one or more UEs, a random access message associated with a corresponding synchronization signal block index of the plurality of synchronization signal blocks using the first set of beams; as well as The received random access message is relayed to the network entity using the first beam.

27. The method of claim 19, further comprising: receiving, from a network entity, an indication of a set of synchronization signal block indices, the set of synchronization signal block indices comprising each respective synchronization signal block index corresponding to each synchronization signal block of the plurality of synchronization signal blocks; as well as A time opportunity for receiving each of the plurality of synchronization signal blocks is determined based at least in part on the indication of the set of synchronization signal block indices, wherein receiving the plurality of synchronization signal blocks is based at least in part on the determination.

28. A method for wireless communication at a network entity, the method comprising: obtaining a capability report, the capability report including an indication of a delay capability and a number of beams supported by the repeater; Outputting a plurality of synchronization signal blocks via a first beam, each synchronization signal block in the plurality of synchronization signal blocks corresponding to a corresponding synchronization signal block index, wherein the number of the plurality of synchronization signal blocks corresponds to the number of beams of a first beam set satisfying the number of beams supported by the repeater; obtaining, via the relay, one or more uplink messages from one or more user equipments (UEs) served by the relay based at least in part on outputting the plurality of synchronization signal blocks; as well as A relay report is obtained that includes an indication by the relay of a second set of beams associated with service to one or more user equipment (UEs) located in a coverage area served by the relay.

29. The method according to claim 28, further comprising: Outputting a beam assignment message including beam information for the second set of beams based at least in part on obtaining the repeater report.

30. The method of claim 29, wherein the beam assignment message comprises: An indication of a number of beams of the second set of beams, an indication of a beam direction of each beam in the second set of beams, or a combination thereof, wherein the second set of beams is different from the first set of beams.

Images