Extending non-serving cells by repeater

Abstract

Methods, systems, and devices for wireless communication are described. The relay may receive, from a network device, a control signal indicating that the relay will forward, for the UE, one or more messages associated with a non-serving cell of the relay. The network device may output a control signal for the repeater. The network device may be a serving cell of the repeater. The network device may additionally output an indication of beam directions and time resources associated with the non-serving cell. The relay may forward one or more messages associated with the non-serving cell for the UE using a beam direction associated with the non-serving cell and via time resources associated with the non-serving cell according to the control signal.

Description

Cross-referencing

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 325,956, filed May 30, 2023, entitled “EXTENDING A NON-SERVING CELL BY A REPEATER,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following discussion pertains to wireless communications, including the extension of non-serving cells by repeaters. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting the extension of non-serving cells by a repeater. For example, the described technology provides a repeater forwarding messages to or from a user equipment (UE) in a wireless communication system. In some cases, the repeater may receive control signals from a network device instructing the repeater to forward one or more messages associated with the repeater's non-serving cell to the UE. For example, the network device may output control signals for the repeater. In some examples, the network device may be the serving cell of the repeater. The network device may additionally output indications of beam direction and timing resources associated with the non-serving cell. In some cases, the repeater may, based on the control signals, use the beam direction associated with the non-serving cell and via the timing resources associated with the non-serving cell to forward one or more messages associated with the non-serving cell to the UE (e.g., from or to the UE). Attached Figure Description

[0005] Figure 1An example is shown of a wireless communication system that supports the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0006] Figure 2 An example of a network architecture supported by a repeater extending a non-serving cell, according to one or more aspects of this disclosure, is shown.

[0007] Figures 3 to 5 An example is shown of a wireless communication system that supports the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0008] Figure 6 An example of a process flow supported by a repeater for extending a non-serving cell according to one or more aspects of this disclosure is shown.

[0009] Figure 7 and Figure 8 A block diagram is shown that supports a device for extending a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0010] Figure 9 A block diagram is shown that supports a communication manager for extending a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0011] Figure 10 A diagram is shown of a system including equipment that supports the extension of non-serving cells by a repeater, according to one or more aspects of this disclosure.

[0012] Figure 11 and Figure 12 A block diagram is shown that supports a device for extending a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0013] Figure 13 A block diagram is shown that supports a communication manager for extending a non-serving cell by a repeater, according to one or more aspects of this disclosure.

[0014] Figure 14 A diagram is shown of a system including equipment that supports the extension of non-serving cells by a repeater, according to one or more aspects of this disclosure.

[0015] Figures 15 to 18 A flowchart illustrating a method for extending a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0016] Repeaters (e.g., network-controlled repeaters (NCRs)) can extend the coverage area of ​​a network entity to a non-serving cell. In some cases, user equipment (UE), the NCR mobile terminal (MT) element, or both may be configured with carrier aggregation. For example, a first cell and a second cell may serve the UE, and the NCR-MT may receive indications via a carrier aggregation framework. In some cases, the carrier aggregation framework may be associated with excessive power consumption of the NCR-MT (e.g., for low traffic levels at the NCR-MT).

[0017] Additionally or alternatively, a network entity (also referred to herein as a network device) may serve the UE via a repeater associated with a first cell (e.g., the serving cell). In some cases, during the handover of the repeater from the first cell to the second cell (e.g., due to link degradation, environmental changes, repeater mobility, etc.), the repeater may interrupt the forwarding of signals from the first cell to the UE, causing the UE to also be handed over from the first cell to the second cell. For example, the UE may have coverage via the repeater and may communicate with the first cell, the second cell, or both without independence. In some cases, the UE may receive a handover command before measuring the second cell (e.g., blind handover), making the handover potentially associated with a high failure probability. Therefore, the UE may receive a message associated with the second cell before the handover. That is, in some cases, the repeater may forward signals from the second cell (e.g., the non-serving cell of the repeater's NCR-MT) to the UE.

[0018] The techniques described herein can support the extension of coverage of non-serving cells by repeaters. For example, network entities can send control signaling to a repeater, and the repeater can forward messages to or from a non-serving cell for a UE based on that control signaling. In some cases, network entities can output control signaling, beam direction indications, time resource indications, etc., to the repeater. In some examples, the repeater can use beam direction and time resources to forward messages to or from a UE.

[0019] Additionally or alternatively, components of a network entity, including centralized units (CUs) and distributed units (DUs), may convey information associated with coverage extension. For example, a CU of a network entity may additionally indicate repeater unavailability to the DU via time resources. In some cases, the DU may indicate ancillary information (e.g., including access beams) that the CU may use to generate indications for one or more messages to be forwarded by the repeater.

[0020] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can support improved signaling coverage, reduced latency, and increased signaling throughput by supporting control messages instructing the relayer to forward messages between the UE and the non-serving cell. Additionally, managing a network by which messages are forwarded by the relayer in this manner enables dynamically scheduled UEs to communicate with non-serving cells. Therefore, such systems may experience more efficient signaling and fewer handover processes, among other benefits.

[0021] The aspects of this disclosure are first described in the context of a wireless communication system. Then, the aspects of this disclosure are described in the context of network architecture, other wireless communication systems, and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to the extension of non-serving cells by repeaters.

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

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

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

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

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

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

[0028] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a DU 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

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

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

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

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

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

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

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

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

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

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

[0041] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

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

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

[0044] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0046] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

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

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

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

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

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

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

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

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

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

[0056] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

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

[0058] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

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

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

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

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

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

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

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

[0066] As described herein, wireless communication system 100 can provide extended coverage of a repeater to a non-serving cell. In some cases, the repeater may receive control signals from network entity 105 (also referred to herein as a network device) instructing the repeater to forward one or more messages associated with the repeater's non-serving cell to or from UE 115. For example, network entity 105 may output control signals for the repeater. In some examples, network entity 105 may be the serving cell of the repeater. Network entity 105 may additionally output indications of beam direction and timing resources associated with the non-serving cell. In some cases, the repeater may, based on the control signals, use the beam direction associated with the non-serving cell and via the timing resources associated with the non-serving cell to forward one or more messages associated with the non-serving cell to UE 115.

[0067] A repeater (e.g., an NCR) can extend the coverage area of ​​network entity 105 to a non-serving cell. The repeater may include a mobile terminal element (e.g., an NCR-MT) and a forwarding element (e.g., an NCR-Fwd). In some cases, the mobile terminal element may exchange information (e.g., sidelink control information (SCI)) with network entity 105 via a control link (e.g., a Uu-based control link). In some cases, the forwarding element may forward (e.g., perform amplification and forwarding) signals (e.g., uplink or downlink radio frequency signals) between network entity 105 and UE 115 via a backhaul link between network entity 105 and the forwarding element, and an access link between the forwarding element and UE 115. In some examples, at least one of a number of carriers associated with the mobile terminal element may operate in the same frequency band as the forwarding element. In some cases, network entity 105, UE 115, or both may perform TDM on messages on both the control link and the backhaul link, while simultaneously performing transmission and reception on both the control link and the backhaul link, or both (e.g., depending on NCR capabilities). In some cases, SCI may include beam information for access links, TDD configuration (e.g., uplink or downlink configuration), on / off information, etc.

[0068] In some examples, the SCI may include an access link beam indicator. For example, the access link beam indicator may include aperiodic (e.g., via DCI) and periodic (e.g., via RRC) indicators. Additionally or alternatively, the access link beam indicator may indicate one or more beam indices with associated time resources. In some cases, the beam index may refer to an orbital angular momentum (OAM) configured access beam.

[0069] Additionally or alternatively, the SCI may include a return beam indication (e.g., a semi-persistent optional beam indication via a Media Access Control (MAC-CE) element). In some cases, the beam index may refer to the RRC configuration beam for the mobile terminal element. In some cases, the return beam indication may be based on one or more predefined rules (e.g., such that no explicit indication exists).

[0070] In some cases, the SCI may include an on / off indication associated with the forwarding element. For example, the on state may be indicated (e.g., implicitly) via an access link beam indication. In some cases, the forwarding element may be in a off state (e.g., when not indicated as on or within a semi-static flexible symbol).

[0071] In some cases, a forwarding element may be associated with TDD information, a transmit or receive timing reference, or both. For example, a forwarding element may use information associated with a mobile terminal element (e.g., to ensure that no new SCI exists).

[0072] Additionally or alternatively, access link beam configuration information may be associated with forwarding elements. For example, OAM may provide information characterizing the beam (e.g., the number of beams, spatial information, direction, etc.) to network devices, repeaters, or both.

[0073] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting the extension of non-serving cells by repeaters, according to one or more aspects of this disclosure, is illustrated. Network architecture 200 may exemplify examples for implementing one or more aspects of wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served simultaneously by multiple RU 170-a.

[0074] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0075] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0076] DU 165-a may correspond to a logical unit comprising one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional breakdown, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate signaling with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0077] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the implementation of DU 165-a and CU160-a units in cloud-based RAN architectures such as vRAN architectures.

[0078] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can (e.g., via the O1 interface) communicate with components configured according to the 4G RAN. Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0079] The non-RT RIC 175-a can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) or machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CU 160-a, one or more DU 165-a, or both, and an O-eNB 210 to the near-RT RIC 175-b.

[0080] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0081] As described herein, network architecture 200 can provide extended coverage of the repeater to non-serving cells. In some cases, the repeater may receive control signals from network entity 105 or network devices (e.g., CU 160-a, DU 165-a, etc.) instructing the repeater to forward one or more messages associated with the repeater's non-serving cell to UE 115-a. For example, the network device may output control signals for the repeater. In some examples, the network device may be the serving cell of the repeater. The network device may additionally output indications of beam direction and timing resources associated with the non-serving cell. In some cases, the repeater may, based on the control signals, use the beam direction associated with the non-serving cell and via the timing resources associated with the non-serving cell to forward one or more messages associated with the non-serving cell to UE 115-a.

[0082] Figure 3 An example of a wireless communication system 300 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. The wireless communication system 300 may implement, or be implemented by, aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include UE 115-b, DU 165-b, coverage area 110-a, and coverage area 110-b, which may be represented as referenced... Figure 1 and Figure 2 Examples of UE 115, DU 165 and coverage area 110 described.

[0083] In some cases, DU 165-b may communicate with UE 115-b via repeater 305-a. For example, UE 115-b may be served by a first cell, a second cell, or both (e.g., configured with carrier aggregation). In some cases, the forwarding element 315-a of repeater 305-a (e.g., NRC-Fwd) may forward semi-static signaling (e.g., synchronization signal block (SSB)), UE 115-b-specific signaling, or both, in the downlink and uplink between the network device associated with DU 165-b and UE 115-b. In some examples, the first backhaul beam associated with the first cell may be different from the second backhaul beam associated with the second cell (e.g., backhaul beam 320-a). For example, the first cell may be associated with a first frequency band, while the second cell may be associated with a second frequency band different from the first frequency band. Additionally or alternatively, the TRPs for the first cell and the second cell may not be co-located.

[0084] In some examples, the mobile terminal element 310-a (e.g., NCR-MT) of repeater 305-b may support carrier aggregation. For example, the scheduler may indicate a backhaul beam to the mobile terminal element 310-a via a carrier aggregation framework, wherein both the first cell and the second cell can be serving cells with corresponding Transmit Configuration Indicator (TCI) states configured for the mobile terminal element 310-a.

[0085] However, mobile terminal element 310-a (e.g., as a UE) may have limited services (e.g., OAM services), which could lead to excessive power consumption associated with the carrier aggregation framework. For example, mobile terminal element 310-a may not support carrier aggregation, thus reducing power consumption.

[0086] In some cases, mobile terminal element 310-a may be configured to receive signals from a first cell (e.g., the serving cell). Additionally or alternatively, mobile terminal element 310-a may receive an indication of a backhaul beam 320-a associated with a second cell (e.g., a non-serving cell). In some cases, the backhaul beam 320-a may support uplink messages, downlink messages, or both. Additionally or alternatively, the backhaul beam 320-a may support the transmission of SSB, SIB, RACH, etc. In some examples, the backhaul beam 320-a may support the transmission of services associated with UE 115-b (e.g., a channel for an indirect UE).

[0087] In some cases, repeater 305-a may determine whether to forward signals to or from a second cell (e.g., a non-serving cell). Additionally or alternatively, a network device (e.g., DU 165-b) may determine whether repeater 305-a should forward signals to or from the second cell. For example, the network device may determine whether repeater 305-a should forward signals based on whether UE 115-b is an indirect UE (e.g., a dynamically scheduled UE). In some examples, dynamic scheduling information associated with whether repeater 305-a is scheduled in a first cell (e.g., a serving cell) or a second cell (e.g., a non-serving cell) is available to the scheduler but not to repeater 305-a.

[0088] Figure 4 An example of a wireless communication system 400 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. The wireless communication system 400 may implement, or be implemented by, aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 400 may include UE 115-c, CU 160-b, DU 165-c, DU 165-d, coverage area 110-c, and coverage area 110-d, which may be represented as referenced in the references to... Figure 1 and Figure 2 Examples of UE 115, CU 160, DU165 and coverage area 110 described.

[0089] In some cases, repeater 305-b may utilize coverage area 110-c to extend the coverage area of ​​the first cell. For example, the first cell may be the serving cell of mobile terminal element 310-b of repeater 305-b. In some cases, CU160-b may serve DU 165-c, and DU 165-c may serve repeater 305-b.

[0090] In some cases, the forwarding element 315-b of repeater 305-b can forward signals from a second cell (e.g., a non-serving cell) of mobile terminal element 310-b having coverage area 110-d to an indirect UE in the second cell. In some examples, the second cell may be served by the same DU, a different DU (e.g., DU 165-d), or a different network device (e.g., a different CU).

[0091] In some examples, mobile terminal element 310-b may be transferred from the first cell to the second cell (e.g., due to link degradation, environmental changes, repeater mobility, etc.). In some cases, repeater 305-b may interrupt the forwarding of signaling from the first cell and UE 115-c, causing UE 115-c to also be transferred from the first cell to the second cell. For example, UE 115-c may have coverage via repeater 305-b (e.g., the UE may not be able to independently observe cells with a threshold quality level, etc.).

[0092] In some cases, UE 115-c may receive a handover command to a second cell (e.g., a blind handover command). For example, UE 115-c may receive the handover command before measuring the second cell, making the handover highly likely to fail (i.e., the opposite of measuring the second cell before handover). In some examples, when UE 115-c is connected to a first cell (e.g., the source cell), UE 115-c may receive a reference signal (e.g., SSB) from a second cell (e.g., the target cell). For example, the forwarding element 315-b of repeater 305-b may forward the reference signal from the second cell to UE 115-c (e.g., during handover).

[0093] In some cases, network devices (e.g., CU 160-b, DU 165-c, DU 165-d) can manage (e.g., control) the expansion of non-serving cells. For example, a network device can send an SCI to repeater 305-b, and based on the SCI, repeater 305-b can forward signals to or from non-serving cells.

[0094] In some cases, measurement reports from mobile terminal element 310-b of repeater 305-b may indicate multiple neighboring cells. In some examples, the network device may determine the cell to which mobile terminal element 310-b, UE 115-c (e.g., an indirect UE), or both can migrate among multiple neighboring cells. For example, the network device may determine the cell based on the measurement report. In some cases, mobile terminal element 310-b may receive signaling instructing the forwarding of a reference signal to a second cell instead of a third cell, wherein the measurement report may include measurements associated with a second cell, a third cell, or both.

[0095] In some cases, repeater 305-b can forward reference signals from neighboring cells, enabling an indirect UE (e.g., idle, inactive, etc.) to camp and initiate initial access to the neighboring cell based on the migration of repeater 305-b to the neighboring cell. In this way, the movement of the repeater towards the neighboring cell allows the UE to initiate initial access. In some cases, the handover of UE 115-c from the first cell to the second cell can be based on one or more CSI-RS. For example, the configuration of the CSI-RS can be specific to the indirect UE. In some cases, repeater 305-b can receive signaling from network equipment indicating resources that can be activated on it for forwarding (e.g., resources on which CSI-RS of the second cell can be transmitted).

[0096] In some cases, repeater 305-b may not be aware of the indirect UEs in the remote access direction, while the network equipment is aware of these indirect UEs. In such cases, repeater 305-b may suppress forwarding reference signals before mobile terminal element 310-b connects to a non-serving cell (e.g., if no indirect UEs exist).

[0097] Figure 5 An example of a wireless communication system 500 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. The wireless communication system 500 may implement, or be implemented by, aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 500 may include UE 115-d, CU 160-c, DU 165-e, network entity 105-a, coverage area 110-e, and coverage area 110-f, which may be represented as referenced. Figure 1 and Figure 2 Examples of UE 115, CU160, DU 165, network entity 105, and coverage area 110 described.

[0098] In some cases, repeater 305-c can extend the coverage area of ​​a first cell associated with coverage area 110-e. For example, the first cell may be the serving cell of mobile terminal element 310-c (e.g., NCT-MT) of repeater 305-c. In some cases, forwarding element 315-c of repeater 305-c can forward one or more messages from DU 165-e, CU 160-c, or both to UE 115-d (e.g., via one or more access beams 320-c). In some cases, CU 160-c may serve DU 165-e, and DU 165-e may serve the repeater.

[0099] In some examples, repeater 305-c may receive an instruction from DU 165-e of a first cell (e.g., serving cell) to forward signaling associated with a second cell (e.g., a non-serving cell) in coverage area 110-f to or from UE 115-d. Additionally or alternatively, repeater 305-c may forward one or more messages from the second cell to or from UE 115-d based on the instruction.

[0100] For example, the indication may include sidelink control information. In some cases, the sidelink control information may include an indication of the backhaul beam direction of the backhaul beam 320-b associated with the second cell. Additionally or alternatively, the indication of the backhaul beam 320-b may include an indication of the identifier of the second cell. For example, the indication may include the beam index of the second cell. Additionally or alternatively, the indication of the backhaul beam 320-b may include a TCI status value associated with a beam (e.g., an access beam) of the second cell. For example, repeater 305-c may receive a configuration of the TCI status associated with the beam of the second cell. In some cases, the beam of the second cell may be an SSB beam, CSI-RS, Position Reference Signal (PRS), etc. In some cases, network equipment (e.g., DU 165-e) may send the indication of the backhaul beam 320-b to repeater 305-c via dynamic signaling.

[0101] In some examples, sidelink control information may include communication resources (e.g., time resources) on which repeater 305-c can direct backhaul beam 320-b to the second cell. In some cases, network devices or DU 165-e may send (or output) indications of communication resources to repeater 305-c via RRC messages, dynamic indications of RRC configuration modes, etc.

[0102] In some cases, sidelink control information may include the direction of forwarding to or from the second cell (e.g., uplink or downlink). For example, the direction may indicate to repeater 305-c whether to forward a message from network entity 105-a of the second cell to UE 115-d or from UE 115-d to the second cell. In some cases, the network device may send the indication of the forwarding direction via an RRC message or SIB of the second cell. In some cases, repeater 305-c may report measurements of the second cell (e.g., L3 measurement reports, L1 measurement reports, etc.) to DU165-e, CU 160-c, or both. For example, DU165-e, CU 160-c, or both may send the indication based on the measurements of the second cell reported by repeater 305-c. In some cases, the repeater may receive the indication via RRC signaling, MAC-CE, DCI, SIB, or a combination thereof. For example, the repeater may receive the indication via dynamic signaling (e.g., DCI).

[0103] In some cases, RRC messages can semi-statically configure repeater 305-c. For example, an RRC message can configure repeater 305-c to forward signaling associated with a second cell without involving DU 165-e. In some cases, CU 160-c can output an indication to repeater 305-c to forward signaling associated with the second cell on time resources. Additionally or alternatively, CU 160-c can output an indication of the unavailability of repeater 305-c to DU 165-e on time resources.

[0104] In some examples, the RRC message may configure one or more access beams 320-c. For example, the RRC message may configure the direction of one or more access beams 320-c for a time resource on which the repeater 305-c may forward messages associated with the second cell. Additionally or alternatively, DU 165-e may output auxiliary information to CU 160-c. For example, DU 165-e may output auxiliary information to CU 160-c based on DU 165-e knowing that UE 115-d is served by one or more access beams 320-c. That is, in some examples, DU 165-e may indicate one or more access beams 320-c associated with signaling forwarding the second cell to CU 160-c, wherein CU 160-c may generate the indication based on auxiliary information received from DU 165-e. In some cases, the indication of the access beam may or may not be associated with UE 115-d (e.g., it may be device-agnostic). Additionally or alternatively, the indication of the access beam may include time resources.

[0105] In some cases, network devices may send indications via MAC-CE, DCI, or both. For example, a network device may send MAC-CE, DCI, or both based on a trigger message output from CU 160-c to DU 165-e (e.g., F1AP trigger) (e.g., when the indication can be based on an L3 measurement report). In some cases, CU 160-c may output an indication or a portion thereof to DU 165-e, and DU 165-e may send an indication to mobile terminal element 310-c.

[0106] Figure 6An example of a process flow 600 supporting the extension of a non-serving cell by a repeater according to one or more aspects of this disclosure is shown. In some examples, process flow 600 may implement, or be implemented by, aspects of wireless communication system 100, network architecture 200, wireless communication system 300, wireless communication device 400, wireless communication system 500, or any combination thereof. For example, process flow 600 may include network entity 105-b, repeater 305-d, and UE 115-e, which may be referenced herein. Figure 1 , Figure 2 and Figure 3 Examples of the corresponding devices described. The following alternative examples may be implemented, some of which may be performed in a different order than described, or not at all. In some cases, steps may include additional features not mentioned below, or other steps may be added. Although network entity 105-b, repeater 305-d, and UE 115-e are shown as performing the operations of process flow 600, some aspects of some operations may also be performed by one or more other wireless devices.

[0107] At point 605, repeater 305-d can send a measurement report to network entity 105-b. For example, repeater 305-d can send a report indicating one or more measurements associated with the serving cell. This report can be an L1 measurement report or an L3 measurement report.

[0108] At 610, network entity 105-b may send a control signal to repeater 305-d, instructing repeater 305-d to forward one or more messages associated with a non-serving cell of repeater 305-d to UE 115-e. In some cases, network entity 105-b may be the serving cell of repeater 305-d. In some cases, repeater 305-d may receive control information based on measurement reports. In some cases, network entity 105-b may be a DU. In some examples, the DU may obtain an indication from the CU of network entity 105-b to forward one or more messages to UE 115-e. Additionally or alternatively, the DU may output a MAC-CE for repeater 305-d indicating that it will forward one or more messages to UE 115-e based on the obtained indication.

[0109] At 615, network entity 105-b may send to repeater 305-d an indication of beam direction associated with a non-serving cell, an indication of time resources, or both. Additionally or alternatively, the indication may include an identifier associated with the non-serving cell, a beam index associated with the non-serving cell, or both.

[0110] In some examples, the indication may include a value of the TCI state associated with the beam of the non-serving cell. In some cases, the beam of the non-serving cell may be associated with one or more of the SSB, CSI-RS, or PRS. Additionally or alternatively, repeater 305-d may receive an indication of the configuration of the TCI state associated with the beam of the non-serving cell. For example, forwarding one or more messages may be based on this configuration. In some cases, the indication may be an indication of the access beam associated with the non-serving cell. In some examples, one or more messages are forwarded to UE 115-e using the access beam. In some cases, the indication may be an indication of the direction of forwarding. In some examples, the direction may indicate that repeater 305-d will send one or more messages to UE 115-e or receive one or more messages from UE 115-e. In some examples, the CU may obtain auxiliary information from the DU indicating the access beam associated with the non-serving cell. Additionally or alternatively, the CU may generate an indication of forwarding one or more messages to UE 115-e based on the auxiliary information.

[0111] At 620, repeater 305-d can forward messages from network entity 105-b to UE 115-e. For example, repeater 305-d can forward one or more messages associated with a non-serving cell to UE 115-e via time resources associated with the non-serving cell, based on control signals. That is, repeater 305-d can forward messages from the non-serving cell to UE 115-e or from UE 115-e to the non-serving cell.

[0112] Figure 7 A block diagram 700 is shown of a device 705 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure. Device 705 may be an example of various aspects of a repeater wireless device as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0113] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with a non-serving cell extended by a repeater). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

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

[0115] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of extending a non-serving cell by a repeater as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0117] Additionally or alternatively, in some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting components for performing the functions described in this disclosure).

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

[0119] According to the examples disclosed herein, the communication manager 720 can support wireless communication at a repeater radio device. For example, the communication manager 720 can be, configured, or operated to support components for receiving control signals from a network device instructing the repeater radio device to forward one or more messages associated with a non-serving cell of the repeater radio device to a UE, wherein the network device is the serving cell of the repeater radio device. The communication manager 720 can be, configured, or operated to support components for forwarding one or more messages associated with a non-serving cell to a UE via time resources associated with the non-serving cell, based on the control signals.

[0120] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., at least one processor that controls or otherwise couples receiver 710, transmitter 715, communication manager 720, or a combination thereof) can support techniques for extending non-serving cells by repeaters, thereby improving communication reliability, increasing the efficiency of communication resource utilization, reducing latency, improving device coverage, and increasing signaling throughput.

[0121] Figure 8 A block diagram 800 of a device 805 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of aspects of device 705 as described herein or repeater wireless device 115. Device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. Device 805 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with non-serving cells extended by repeaters). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

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

[0124] Device 805 or its various components may be examples of parts used to perform various aspects of extending a non-serving cell by a repeater as described herein. For example, communication manager 820 may include control signal component 825, forwarding component 830, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0125] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the repeater radio device. The control signal component 825 is capable of, configured to, or operable to support components for receiving from a network device an instruction that the repeater radio device will forward one or more messages associated with a non-serving cell of the repeater radio device to a UE, wherein the network device is the serving cell of the repeater radio device. The forwarding component 830 is capable of, configured to, or operable to support components for forwarding one or more messages associated with a non-serving cell to a UE via time resources associated with the non-serving cell, based on the control signals.

[0126] Figure 9A block diagram 900 is shown of a communication manager 920 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of parts for performing the various aspects of the extension of a non-serving cell by a repeater as described herein. For example, the communication manager 920 may include a control signal component 925, a forwarding component 930, a reporting component 935, a control signal indication component 940, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0127] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the repeater radio device. The control signal component 925 is capable of, configured to, or operable to support components for receiving from a network device an instruction that the repeater radio device will forward one or more messages associated with a non-serving cell of the repeater radio device to a UE, wherein the network device is the serving cell of the repeater radio device. The forwarding component 930 is capable of, configured to, or operable to support components for forwarding one or more messages associated with a non-serving cell to a UE via time resources associated with the non-serving cell, based on the control signals.

[0128] In some examples, the reporting component 935 is capable of, configured to, or able to operate to support components for sending reports to network devices indicative of one or more measurements associated with the serving cell, wherein receiving control signals is based on the reports.

[0129] In some examples, to support the reception of control signals, the control signal indication component 940 is capable, configured, or operable to support components for receiving indications of beam direction associated with the non-serving cell and indications of time resources. In some examples, the indications include an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

[0130] In some examples, the indicator includes a value for the TCI state associated with the beam of the non-serving cell. In some examples, the beam of the non-serving cell is associated with one or more of the SSB, CSI-RS, or PRS.

[0131] In some examples, the control signal indication component 940 is capable of, configured to, or able to operate to support components for receiving indications of the configuration of the TCI state associated with the beam of a non-serving cell, wherein forwarding one or more messages is based on the configuration.

[0132] In some examples, in order to support receiving control signals, the control signal indication component 940 is capable of, configured to, or able to operate to support components for receiving indications of access beams associated with non-serving cells, wherein one or more messages are forwarded to the UE using the access beams.

[0133] In some examples, in order to support receiving control signals, the control signal indication component 940 is capable of, configured to, or able to operate to support components for receiving indications of the direction of forwarding, wherein the direction indication repeater radio device will send one or more messages to the UE or receive one or more messages from the UE.

[0134] Figure 10 A diagram of a system 1000 including device 1005 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or a repeater wireless device as described herein, or may include components thereof. Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, a transceiver 1010, an antenna 1015, at least one memory 1025, code 1030, at least one processor 1035, and an I / O controller 1045. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1040).

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

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

[0137] At least one processor 1035 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1035 may be configured to operate at least one memory array using at least one memory controller. In some other cases, at least one memory controller may be integrated into at least one processor 1035. At least one processor 1035 may be configured to execute computer-readable instructions stored in at least one memory (e.g., at least one memory 1025) to cause device 1005 to perform various functions (e.g., supporting functions or tasks such as extending a non-serving cell by a repeater). For example, device 1005 or components of device 1005 may include at least one processor 1035 and at least one memory 1025 coupled to or coupled to at least one processor 1035, wherein at least one processor 1035 and at least one memory 1025 are configured to perform the various functions described herein.

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

[0139] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at a repeater wireless device. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving from a network device one or more messages, instructing the repeater wireless device to forward to a UE one or more messages associated with a non-serving cell of the repeater wireless device, wherein the network device is the serving cell of the repeater wireless device. The communication manager 1020 may be capable of, configured to, or operable to support components for forwarding to a UE one or more messages associated with a non-serving cell via time resources associated with the non-serving cell, based on the control signals.

[0140] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for extending non-serving cells by repeaters, thereby improving communication reliability, increasing communication resource utilization efficiency, reducing latency, improving device coverage, and increasing signaling throughput.

[0141] In some examples, the communication manager 1020 may be configured to cooperate with or otherwise collaborate with transceiver 1010, one or more antennas 1015, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported by or executed by at least one processor 1035, at least one memory 1025, code 1030, or any combination thereof. For example, code 1030 may include instructions that can be executed by at least one processor 1035 to cause device 1005 to perform various aspects of extending a non-serving cell by a repeater as described herein, or at least one processor 1035 and at least one memory 1025 may be otherwise configured to perform or support such operations.

[0142] Figure 11A block diagram 1100 of a device 1105 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Device 1105 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0145] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of extending a non-serving cell by a repeater as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0147] Additionally or alternatively, in some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting components for performing the functions described in this disclosure).

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

[0149] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at a network device. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for outputting control signals to a repeater wireless device instructing that one or more messages associated with a non-serving cell of the repeater wireless device will be forwarded to a UE, wherein the network device is the serving cell of the repeater wireless device. The communication manager 1120 may also be capable of, configured to, or operable to support components for outputting indications to a repeater wireless device of beam direction and timing resources associated with a non-serving cell, wherein one or more messages are forwarded to a UE using beam direction and via timing resources.

[0150] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., at least one processor that controls or otherwise couples receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof) can support techniques for extending non-serving cells by repeaters, thereby improving communication reliability, increasing the efficiency of communication resource utilization, reducing latency, improving device coverage, and increasing signaling throughput.

[0151] Figure 12 A block diagram 1200 of a device 1205 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. Device 1205 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0154] Device 1205 or its various components may be examples of parts used to perform various aspects of extending a non-serving cell by a repeater as described herein. For example, communication manager 1220 may include control signaling component 1225, message forwarding instruction component 1230, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0155] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a network device. The control signal transmission component 1225 is capable of, configured to, or operable to support components for outputting control signals to a repeater radio device instructing that one or more messages associated with a non-serving cell of the repeater radio device will be forwarded to a UE, wherein the network device is the serving cell of the repeater radio device. The message forwarding indication component 1230 is capable of, configured to, or operable to support components for outputting indications to a repeater radio device of beam direction and timing resources associated with a non-serving cell, wherein one or more messages are forwarded to a UE using beam direction and via timing resources.

[0156] Figure 13A block diagram 1300 is shown of a communication manager 1320 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure. The communication manager 1320 may be an example of a communication manager 1120, a communication manager 1220, or aspects of both as described herein. The communication manager 1320 or its various components may be examples of parts for performing the various aspects of the extension of a non-serving cell by a repeater as described herein. For example, the communication manager 1320 may include a control signaling component 1325, a message forwarding indication component 1330, an unavailability indication component 1335, an auxiliary information component 1340, an indication sending component 1345, a report receiving component 1350, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between the protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0157] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a network device. The control signal transmission component 1325 is capable of, configured to, or operable to support components for outputting control signals to a repeater radio device instructing that one or more messages associated with a non-serving cell of the repeater radio device will be forwarded to a UE, wherein the network device is the serving cell of the repeater radio device. The message forwarding indication component 1330 is capable of, configured to, or operable to support components for outputting indications to a repeater radio device of beam direction and timing resources associated with a non-serving cell, wherein one or more messages are forwarded to a UE using beam direction and via timing resources.

[0158] In some examples, the unavailability indication component 1335 is capable of being configured or operated to support a component for outputting an indication to the repeater wireless device via time resources that it is unavailable for forwarding one or more messages.

[0159] In some examples, the auxiliary information component 1340 is capable of, configured to, or operable to support components for obtaining auxiliary information from the DU indicating the access beam associated with the non-serving cell. In some examples, the message forwarding indication component 1330 is capable of, configured to, or operable to support components for generating an indication based on the auxiliary information regarding the forwarding of one or more messages to the UE. In some examples, the auxiliary information is associated with the UE or is device-agnostic.

[0160] In some examples, to support output control signals, the message forwarding indication component 1330 is capable, configured, or operable to support components for obtaining an indication from the CU regarding the forwarding of one or more messages to the UE. In some examples, to support output control signals, the indication sending component 1345 is capable, configured, or operable to support components for outputting a MAC-CE or DCI to the repeater radio device, based on the obtained indication, indicating that one or more messages will be forwarded to the UE.

[0161] In some examples, the report receiving component 1350 is capable of, configured to, or operable to support components for obtaining reports from the repeater radio device indicating one or more measurements associated with the serving cell, wherein the reception control signals are based on the reports. In some examples, the indication includes an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

[0162] In some examples, the indication includes a TCI state value associated with the beam of the non-serving cell. In some examples, the beam of the non-serving cell is associated with one or more of the SSB, Channel State Information Reference Signal, or Location Reference Signal.

[0163] In some examples, the sending component 1345 is an indication of a component that can, is configured to, or is capable of operating to support an indication of the configuration for outputting the TCI status associated with the beam of a non-serving cell, wherein forwarding one or more messages is based on the configuration.

[0164] In some examples, to support output control signals, the transmitting component 1345 is instructed to be, configured to, or capable of operating to support components for outputting indications of access beams associated with non-serving cells, wherein one or more messages are forwarded to the UE using the access beams.

[0165] In some examples, in order to support output control signals, the instruction transmitting component 1345 is enabled, configured, or able to operate to support components for outputting an indication of the direction of forwarding, wherein the direction indication repeater radio device will send one or more messages to or receive one or more messages from the UE.

[0166] Figure 14A diagram of a system 1400 including device 1405 supporting the extension of a non-serving cell by a repeater, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components that support output and enable communication, such as a communication manager 1420, a transceiver 1410, an antenna 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

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

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

[0169] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using at least one memory controller. In some other cases, at least one memory controller may be integrated into at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in at least one memory (e.g., at least one memory 1425) to cause device 1405 to perform various functions (e.g., supporting functions or tasks such as extending a non-serving cell by a repeater). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within at least one memory 1425). In some implementations, at least one processor 1435 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive input and process that input to produce a set of outputs that can be passed to, for example, other systems or components of device 1405. For example, the processing system of device 1405 may refer to a system that includes various other components or sub-components of device 1405 (such as at least one processor 1435, transceiver 1410, communication manager 1420, or other components or combinations of components of device 1405). The processing system of device 1405 can interface with other components of device 1405 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information or for receiving information, or both. These one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, and other specific implementations. In some specific implementations, these one or more interfaces may refer to the interface between the processing system of the chip or modem and a transmitter, enabling device 1405 to transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1405 to receive information or signal input, and such information to be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

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

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

[0172] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a network device. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting control signals to a repeater radio device instructing that one or more messages associated with a non-serving cell of the repeater radio device will be forwarded to a UE, wherein the network device is the serving cell of the repeater radio device. The communication manager 1420 may also be capable of, configured to, or operable to support components for outputting indications to a repeater radio device of beam direction and timing resources associated with a non-serving cell, wherein one or more messages are forwarded to a UE using beam direction and via timing resources.

[0173] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for extending non-serving cells by repeaters, thereby improving communication reliability, increasing communication resource utilization efficiency, reducing latency, improving device coverage, and increasing signaling throughput.

[0174] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported by or performed by the transceiver 1410, at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof. For example, code 1430 may include instructions that can be executed by at least one processor 1435 to cause the device 1405 to perform various aspects of extending a non-serving cell by a repeater as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations.

[0175] Figure 15 A flowchart illustrating a method 1500 for extending a non-serving cell by a repeater, according to various aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a repeater wireless device or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 10 The described repeater wireless device performs the functions described herein. In some examples, the repeater wireless device may execute a set of instructions to control the functional elements of the repeater wireless device to perform the described functions. Additionally or alternatively, the repeater wireless device may use dedicated hardware to perform aspects of the described functions.

[0176] At 1505, the method may include receiving from a network device a control signal instructing the repeater radio device to forward one or more messages associated with a non-serving cell of the repeater radio device to the UE, wherein the network device is the serving cell of the repeater radio device. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from references... Figure 9 The described control signal component 925 is executed.

[0177] At 1510, the method may include forwarding one or more messages associated with a non-serving cell to the UE via time resources associated with the non-serving cell, based on control signals. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to... Figure 9 The described forwarding component 930 is executed.

[0178] Figure 16 A flowchart illustrating method 1600, which exemplifies various aspects of this disclosure, for extending a non-serving cell by a repeater. Operation of method 1600 may be implemented by a repeater wireless device or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 10 The described repeater wireless device performs the functions described herein. In some examples, the repeater wireless device may execute a set of instructions to control the functional elements of the repeater wireless device to perform the described functions. Additionally or alternatively, the repeater wireless device may use dedicated hardware to perform aspects of the described functions.

[0179] At 1605, the method may include sending a report to the network device indicating one or more measurements associated with the serving cell, wherein receiving control signals is based on the report. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 9 The described reporting component 935 is executed.

[0180] At 1610, the method may include receiving from a network device a control signal instructing the repeater radio device to forward one or more messages associated with a non-serving cell of the repeater radio device to the UE, wherein the network device is the serving cell of the repeater radio device. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 9 The described control signal component 925 is executed.

[0181] At 1615, the method may include forwarding one or more messages associated with a non-serving cell to the UE via time resources associated with the non-serving cell, based on control signals. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to... Figure 9 The described forwarding component 930 is executed.

[0182] Figure 17A flowchart illustrating method 1700, which exemplifies various aspects of this disclosure, for extending a non-serving cell by a repeater. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0183] At 1705, the method may include outputting a control signal to the repeater radio device instructing it to forward one or more messages associated with a non-serving cell of the repeater radio device to the UE, wherein the network device is the serving cell of the repeater radio device. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 13 The control signal sending component 1325 described herein is executed.

[0184] At 1710, the method includes outputting an indication to the repeater radio device of beam direction and time resources associated with a non-serving cell, wherein one or more messages are forwarded to the UE using the beam direction and via the time resources. The operation of block 1710 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 can be derived from references... Figure 13 The described message component 1330 is executed.

[0185] Figure 18 A flowchart illustrating method 1800, which exemplifies various aspects of this disclosure, for extending a non-serving cell by a repeater. Operation of method 1800 may be implemented by a network entity or its components as described herein. For example, operation of method 1800 may be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0186] At 1805, the method may include obtaining from the repeater wireless device a report indicating one or more measurements associated with the serving cell, wherein receiving control signals is based on the report. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The report receiving component 1350 described is executed.

[0187] At 1810, the method may include outputting a control signal to the repeater radio device instructing it to forward one or more messages associated with a non-serving cell of the repeater radio device to the UE, wherein the network device is the serving cell of the repeater radio device. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be provided by reference to [reference needed]. Figure 13 The control signal sending component 1325 described herein is executed.

[0188] At 1815, the method includes outputting an indication to the repeater radio device of beam direction and time resources associated with a non-serving cell, wherein one or more messages are forwarded to the UE using the beam direction and via the time resources. The operation of block 1815 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 can be derived from references... Figure 13 The described message component 1330 is executed.

[0189] The following provides an overview of the various aspects of this disclosure.

[0190] Aspect 1: A method for wireless communication at a repeater wireless device, the method comprising: receiving from a network device a control signal instructing the repeater wireless device to forward one or more messages associated with a non-serving cell of the repeater wireless device to a UE, wherein the network device is a serving cell of the repeater wireless device; and forwarding the one or more messages associated with the non-serving cell to the UE via time resources associated with the non-serving cell, according to the control signal.

[0191] Aspect 2: According to the method of aspect 1, the method further includes: sending a report to the network device indicating one or more measurements associated with the serving cell, wherein the control signal is received at least in part based on the report.

[0192] Aspect 3: The method according to any one of Aspects 1 to 2, wherein receiving the control signal includes: receiving an indication of the beam direction associated with the non-serving cell and an indication of the time resources.

[0193] Aspect 4: According to the method of aspect 3, wherein the indication includes an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

[0194] Aspect 5: The method according to any one of Aspects 3 to 4, wherein the indication includes a value of a TCI state associated with a beam of the non-serving cell, the beam of the non-serving cell being associated with one or more of an SSB, CSI-RS, or PRS.

[0195] Aspect 6: According to the method of aspect 5, the method further includes: receiving an indication of the configuration of the TCI state associated with the beam of the non-serving cell, wherein forwarding of the one or more messages is based at least in part on the configuration.

[0196] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the control signal comprises: receiving an indication of an access beam associated with the non-serving cell, wherein the access beam is used to forward the one or more messages to the UE.

[0197] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the control signal comprises: receiving an indication of the direction of the forwarding, wherein the direction indicates that the repeater wireless device will send the one or more messages to the UE or receive the one or more messages from the UE.

[0198] Aspect 9: A method for wireless communication at a network device, the method comprising: outputting a control signal to a repeater wireless device instructing that one or more messages associated with a non-serving cell of the repeater wireless device be forwarded to a UE, wherein the network device is a serving cell of the repeater wireless device; and outputting an indication to the repeater wireless device of beam direction and timing resources associated with the non-serving cell, wherein the one or more messages are forwarded to the UE using the beam direction and via the timing resources.

[0199] Aspect 10: The method according to aspect 9, wherein the network device is a centralized unit, the method further comprising: outputting an indication to a distributed unit via the time resource that the repeater wireless device is unavailable for forwarding the one or more messages.

[0200] Aspect 11: The method according to any one of Aspects 9 to 10, wherein the network device is a centralized unit, the method further comprising: obtaining auxiliary information from a distributed unit indicating an access beam associated with the non-serving cell; and generating, at least in part, an indication regarding forwarding the one or more messages to the UE based on the auxiliary information.

[0201] Aspect 12: According to the method of aspect 11, the auxiliary information is associated with the UE or is unknown to the device.

[0202] Aspect 13: The method according to any one of Aspects 9 to 12, wherein the network device is a distributed unit, and wherein outputting the control signal comprises: obtaining from a centralized unit an indication to forward the one or more messages to the UE; and outputting a MAC-CE or DCI indicating to the repeater radio device to forward the one or more messages to the UE, at least in part based on obtaining the indication.

[0203] Aspect 14: The method according to any one of Aspects 9 to 13, the method further comprising: obtaining from the repeater wireless device a report indicating one or more measurements associated with the serving cell, wherein the control signal is received at least in part based on the report.

[0204] Aspect 15: The method according to any one of Aspects 9 to 14, wherein the indication includes an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

[0205] Aspect 16: The method according to any one of Aspects 9 to 15, wherein the indication includes a TCI state value associated with a beam of the non-serving cell, the beam of the non-serving cell being associated with one or more of SSB, CSI-RS or PRS.

[0206] Aspect 17: The method according to aspect 16, the method further comprising: outputting an indication of the configuration of the TCI state associated with the beam of the non-serving cell, wherein forwarding of the one or more messages is at least partially based on the configuration.

[0207] Aspect 18: The method according to any one of Aspects 9 to 17, wherein outputting the control signal comprises: outputting an indication of an access beam associated with the non-serving cell, wherein the access beam is used to forward the one or more messages to the UE.

[0208] Aspect 19: The method according to any one of Aspects 9 to 18, wherein outputting the control signal comprises: outputting an indication of the direction of the forwarding, wherein the direction indicates that the repeater wireless device will send the one or more messages to the UE or receive the one or more messages from the UE.

[0209] Aspect 20: An apparatus for wireless communication at a repeater wireless device, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of aspects 1 to 8.

[0210] Aspect 21: An apparatus for wireless communication at a repeater wireless device, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 8.

[0211] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication at a repeater wireless device, the code comprising instructions executable by at least one processor to perform the method according to any one of methods 1 to 8.

[0212] Aspect 23: An apparatus for wireless communication at a network device, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of aspects 9 to 19.

[0213] Aspect 24: An apparatus for wireless communication at a network device, the apparatus comprising at least one component for performing the method according to any one of aspects 9 to 19.

[0214] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a network device, said code comprising instructions executable by at least one processor to perform the method according to any one of methods 9 to 19.

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

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

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

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

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

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

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

[0222] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in at least one memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

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

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

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

Claims

1. An apparatus for wireless communications at a relay wireless device, the apparatus comprising: at least one processor; at least one memory coupled with the at least one processor, the at least one processor configured to: receive, from a network device, a control signal indicating that the relay wireless device is to forward, for a user equipment (UE), one or more messages associated with a non-serving cell of the relay wireless device, wherein the network device is a serving cell of the relay wireless device; and in accordance with the control signal, forward, for the UE, the one or more messages associated with the non-serving cell via time resources associated with the non-serving cell.

2. The apparatus of claim 1, wherein the at least one processor is configured to: transmit, to the network device, a report indicating one or more measurements associated with the serving cell, wherein receiving the control signal is based at least in part on the report.

3. The apparatus of claim 1, wherein the at least one processor configured to receive the control signal is further configured to: receive an indication of a beam direction associated with the non-serving cell and an indication of the time resources.

4. The apparatus of claim 3, wherein the indication includes an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

5. The apparatus of claim 3, wherein the indication includes a value of a transmission configuration indicator state associated with a beam of the non-serving cell, wherein the beam of the non-serving cell is associated with one or more of a synchronization signal block, a channel state information reference signal, or a positioning reference signal.

6. The apparatus of claim 5, wherein the at least one processor is configured to: receive an indication of a configuration of the transmission configuration indicator state associated with the beam of the non-serving cell, wherein forwarding the one or more messages is based at least in part on the configuration.

7. The apparatus of claim 1, wherein the at least one processor configured to receive the control signal is further configured to: receive an indication of an access beam associated with the non-serving cell, wherein the one or more messages are forwarded to the UE using the access beam.

8. The apparatus of claim 1, wherein the at least one processor configured to receive the control signal is further configured to: receive an indication of a direction of the forwarding, wherein the direction indicates that the relay wireless device is to transmit the one or more messages to the UE or receive the one or more messages from the UE.

9. An apparatus for wireless communications at a network device, the apparatus comprising: at least one processor; at least one memory coupled with the at least one processor, the at least one processor configured to: output, for a relay wireless device, a control signal indicating that one or more messages associated with a non-serving cell of the relay wireless device are to be forwarded for a user equipment (UE), wherein the network device is a serving cell of the relay wireless device; and output, for the relay wireless device, an indication of a beam direction and a time resource associated with the non-serving cell, wherein the one or more messages are forwarded for the UE using the beam direction and via the time resource.

10. The apparatus of claim 9, wherein the at least one processor is configured to: output, to a distributed unit via the time resource, an indication that the relay wireless device is unavailable to forward the one or more messages.

11. The apparatus of claim 9, wherein the at least one processor is configured to: obtain, from a distributed unit, assistance information indicating an access beam associated with the non-serving cell; and generate the indication that the one or more messages are to be forwarded for the UE based at least in part on the assistance information.

12. The apparatus of claim 11, wherein the assistance information is associated with the UE or is device agnostic.

13. The apparatus of claim 9, wherein the at least one processor configured to output the control signal is further configured to: obtain, from a centralized unit, an indication that the one or more messages are to be forwarded for the UE; and output, for the relay wireless device, a medium access control control element or a downlink control information indicating that the one or more messages are to be forwarded for the UE based at least in part on obtaining the indication.

14. The apparatus of claim 9, wherein the at least one processor is configured to: obtain, from the relay wireless device, a report indicating one or more measurements associated with the serving cell, wherein receiving the control signal is based at least in part on the report.

15. The apparatus of claim 9, wherein the indication includes an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

16. The apparatus of claim 9, wherein the indication includes a transmission configuration indicator state value associated with a beam of the non-serving cell, wherein the beam of the non-serving cell is associated with one or more of a synchronization signal block, a channel state information reference signal, or a positioning reference signal.

17. The apparatus of claim 16, wherein the at least one processor is configured to: output an indication of a configuration of the transmission configuration indicator state value associated with the beam of the non-serving cell, wherein forwarding the one or more messages is based at least in part on the configuration.

18. The apparatus of claim 9, wherein the at least one processor configured to output the control signal is further configured to: output an indication of an access beam associated with the non-serving cell, wherein the one or more messages are forwarded to the UE using the access beam.

19. The apparatus of claim 9, wherein the at least one processor configured to output the control signal is further configured to: output an indication of a direction of the forwarding, wherein the direction indicates that the relay wireless device is to transmit or receive the one or more messages to or from the UE.

20. A method for wireless communications at a relay wireless device, comprising: receiving, from a network device, a control signal indicating that the relay wireless device is to forward, for a user equipment (UE), one or more messages associated with a non-serving cell of the relay wireless device, wherein the network device is a serving cell of the relay wireless device; and forwarding, for the UE, the one or more messages associated with the non-serving cell via time resources associated with the non-serving cell in accordance with the control signal.

21. The method of claim 20, further comprising: transmitting, to the network device, a report indicating one or more measurements associated with the serving cell, wherein receiving the control signal is based at least in part on the report.

22. The method of claim 20, wherein receiving the control signal comprises: receiving an indication of a beam direction associated with the non-serving cell and an indication of the time resources.

23. The method of claim 22, wherein the indication comprises an identifier associated with the non-serving cell and a beam index associated with the non-serving cell.

24. The method of claim 22, wherein the indication comprises a value of a transmission configuration indicator state associated with a beam of the non-serving cell, wherein the beam of the non-serving cell is associated with one or more of a synchronization signal block, a channel state information reference signal, or a positioning reference signal.

25. The method of claim 24, further comprising: receiving an indication of a configuration of the transmission configuration indicator state associated with the beam of the non-serving cell, wherein forwarding the one or more messages is based at least in part on the configuration.

26. A method for wireless communications at a network device, comprising: outputting, for a relay wireless device, a control signal indicating that one or more messages associated with a non-serving cell of the relay wireless device are to be forwarded for a user equipment (UE), wherein the network device is a serving cell of the relay wireless device; and outputting, for the relay wireless device, an indication of a beam direction and time resources associated with the non-serving cell, wherein the one or more messages are forwarded for the UE using the beam direction and via the time resources.

27. The method of claim 26, wherein the network device is a centralized unit, further comprising: outputting, to a distributed unit via the time resources, an indication that the relay wireless device is unavailable to forward the one or more messages. ​ 28. The method of claim 26, wherein the network device is a centralized unit, the method further comprising: obtaining, from a distributed unit, assistance information indicating access beams associated with the non-serving cells; and generating the indication that the one or more messages are to be forwarded for the UE based at least in part on the assistance information.

29. The method of claim 28, wherein the assistance information is associated with the UE or is device agnostic.

30. The method of claim 26, wherein the network device is a distributed unit, and wherein outputting the control signal comprises: obtaining, from a centralized unit, an indication that the one or more messages are to be forwarded for the UE; and outputting, for the relay wireless device, a medium access control control element or a downlink control information indicating that the one or more messages are to be forwarded for the UE based at least in part on obtaining the indication.

Images