Beam indication of repeater backhaul link

Abstract

Aspects of the present disclosure relate to devices and methods for a network controlled repeater (NCR) to determine beam indications received from a network device on a side first link for configuring NCR forwarding of wireless communications. The forwarding includes a downlink radio frequency (RF) signal from a network device that is relayed to a user equipment (UE), and includes an uplink RF signal from the UE that is relayed to the network device. In some cases, an association of a default beam of a first link is applied to a forwarded physical channel controlled by NCR mobile terminal Downlink Control Information (DCI). When side control information is received in a different component carrier or from a different transmission and reception point (TRP), a transmission configuration indicator (TCI) state is signaled for a forwarded physical channel. Beam indication enables improved communication performance through NCR.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 371,070, filed on August 10, 2022, the contents of which are incorporated herein in their entirety. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to relaying wireless communications using receive-transmit beam pair selection. Background Art

[0004] A wireless communication system may include one or more network communication devices (including base stations), which may be referred to as eNodeB (eNB), next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, sub-time slots, sub-frames, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth generation (6G)).

[0005] Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their deployments. Deploying conventional full-stack cells is an option, but may not always be technically or economically feasible. Therefore, new network nodes are considered to increase the flexibility of mobile operators for their network deployments. For example, Integrated Access and Backhaul (IAB) is a new type of network node that does not require wired backhaul. Another type of network node is a radio frequency (RF) repeater, which simply amplifies and forwards any signal received by the RF repeater. RF repeaters have been widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. The 5G New Radio (NR) radio access technology (RAT) has RF and electromagnetic compatibility (EMC) requirements for such RF repeaters for NR for both frequency range 1 (FR1) and frequency range 2 (FR2). Summary of the invention

[0006] The present disclosure relates to methods, apparatus, and systems for providing procedures and signaling for a network controlled repeater (NCR) to determine beam indications received from a network device on a side control link. The NCR applies beam indications to configure NCR forwarding of wireless communications. Forwarding includes downlink radio frequency (RF) signals from a network device that are relayed to a user equipment (UE), and uplink RF signals from a UE that are relayed to the network device. In some cases, the association of a default beam of a control link is applied to a forwarded physical channel controlled by NCR mobile terminal downlink control information (DCI). When side control information is received in different component carriers or from different transmission and reception points (TRPs), a transmission configuration indicator (TCI) status is signaled for the forwarded physical channel. Beam indication enables improved communication performance of the NCR.

[0007] Some implementations of the methods and apparatus described herein may include a method for wireless communication through a repeater device. The method includes receiving configuration information for a repeater control resource set (CORESET) from at least one network node via at least one transceiver of the repeater device. The repeater CORESET includes an indicator of spatial relationship information to be applied to the transceiver when a relayed signal is sent via one of the following items: (i) a backhaul link to a network; and (ii) an access link to a user device, at least one transceiver being communicatively coupled to at least one network node via (i) a control link; and (ii) a backhaul link. The method includes configuring at least one transceiver with the configuration information to monitor the repeater CORESET received on the control link. The method includes decoding the spatial relationship information based on the indicator. The method includes determining an offset between repeater downlink control information (DCI) on a repeater CORESET and a corresponding one of: (i) a physical channel received by the repeater device on a control link; (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on a backhaul link; or (iii) a downlink (DL) RF signal sent by the repeater device on an access link. The method includes applying spatial relationship information to at least one transceiver in response to the offset being less than a threshold offset value. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 An example of a wireless communication system that enables a network controller repeater (NCR) device to relay wireless communications in accordance with aspects of the present disclosure is illustrated.

[0009] Figure 2 A portion of a wireless communication system according to aspects of the present disclosure is illustrated, the wireless communication system including a network device, an NCR device, and a user equipment (UE) outside a coverage area of ​​the network device;

[0010] Figure 3 A wireless communication system is illustrated when there is no spatial relationship information in NRC mobile terminal (MT) downlink control information (DCI) when beam indication for a backhaul forwarding link occurs according to various aspects of the present disclosure.

[0011] Figure 4 A wireless communication system is illustrated when there is spatial relationship information in NRC-MT DCI and when there is beam indication for a backhaul forwarding link according to various aspects of the present disclosure.

[0012] Figure 5 A wireless communication system is illustrated when there is spatial relationship information in NRC-MT DCI for multiple transmission and reception points (TRPs) and when there is beam indication for a backhaul forwarding link according to various aspects of the present disclosure.

[0013] Figure 6 A block diagram of a device that performs relaying of wireless communications according to aspects of the present disclosure is illustrated.

[0014] Figure 7 A flow chart of a method performed by a user equipment according to aspects of the present disclosure is illustrated to support side wireless communication with reduced time for an access procedure when other technologies are indicated as not present. DETAILED DESCRIPTION

[0015] Although conventional RF repeaters present a cost-effective way to extend network coverage to communication systems, RF repeaters have their limitations. RF repeaters simply perform amplification and forwarding operations without taking into account various factors that can improve performance. Such factors can include information about semi-static and / or dynamic downlink / uplink configurations, adaptive transmitter / receiver spatial beamforming, switch states, etc. Network controlled repeaters (NCRs) are an enhancement to conventional RF repeaters with the ability to receive and process side control information from the network. Side control information can allow NCRs to perform amplification and forwarding operations in a more efficient manner. Potential benefits can include mitigating unnecessary noise amplification, having better spatial directionality transmission and reception, and simplified network integration. NCRs have problems implementing the additional functionality enabled by side control information.

[0016] The backhaul link and the control link between the network equipment and the NCR are generally expected to experience the same large-scale properties of the channel. In particular, at least when the NCR mobile terminal (MT) communicating via the control link and the NCR forwarding part communicating via the backhaul link operate in the same carrier, it is expected that both the control link and the backhaul link will experience channel properties involving Type-A and Type-D (if applicable). However, if the operating frequency of the NCR-MT is different from the operating frequency of at least one component carrier of the backhaul link, the indication of the backhaul beam needs to be considered.

[0017] The present disclosure solves the problem of indicating spatial relationship information, transmission configuration indicator (TCI), quasi co-location (QCL), and beam identifier (ID) for the backhaul link when the component carrier (CC) for NCR-MT and the CC for the NCR forwarding part are not on the same carrier of one network device or are sent separately by multiple transmission and reception points (TRP). The fields for spatial relationship information and beam ID to be applied on the forwarding backhaul link are included in the relay-specific downlink control information (DCI) carried by the relay-specific physical downlink control channel (rPDCCH). The spatial relationship information indicates the relationship between the receiving control link (i.e., rPDCCH) and the physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), and sounding reference signal (SRS) in the receiving and / or transmitting backhaul link. A procedure is defined for the NCR to apply spatial relationship information, QCL, and beam ID on a forwarded physical channel based on an offset between receiving and decoding an rPDCCH carrying control information and receiving the physical channel and applying the control information. The procedure for indicating and / or applying the spatial relationship / beam ID is based on whether the rPDCCH is sent from the same TRP or in the same CC. The NCR-MT is configured with side control information in an NCR-MT Control Resource Set (CORESET), where the CORESET is associated with a TCI / QCL assumption / beam ID for which the TCI / QCL assumption / beam ID applies as the default beam for receiving a forwarded physical channel controlled by a DCI of the CORESET on the backhaul link. There may be fields in the DCI for spatial relationship information and beam ID to be applied on the forwarding link.

[0018] The spatial relationship information indicates the relationship between the spatial filters used to receive and transmit physical channels in the forwarding backhaul link, or the spatial filters used to receive the NCR-MT CORESET and receive the forwarded physical channel. If the forwarded physical channel is located on a different CC from the NCR-MT, and the control DCI does not have a spatial relationship information field, and the time offset between the reception of the DCI and the reception of the corresponding forwarded physical channel of the serving cell is equal to or greater than the threshold "timeDurationForQCL", the NCR assumes that the spatial relationship information or Rx beam ID for PDCCH / PDSCH is based on the beam ID associated with the NCR-MT CORESET. If the forwarded physical channel is located on a different CC from the NCR-MT, and the control DCI has a spatial relationship information field, and the time offset between the reception of the DCI and the reception of the corresponding physical channel is equal to or greater than the threshold "timeDurationForQCL", the NCR applies the spatial relationship information of the beam ID indicated in the NCR-MT DCI.

[0019] Therefore, the present disclosure provides a new procedure and signaling to allow the association of the default beam of the control link to be applied to the forwarded physical channels PDCCH / PDSCH / PUCCH / PUSCH controlled by NCR-MT DCI. The present disclosure provides a new procedure and signaling for the TCI status of the forwarded physical channels PDCCH / PDSCH / PUCCH / PUSCH when the side control information is received in different component carriers or from different TRPs.

[0020] Figure 1An example of a wireless communication system 100 according to various aspects of the present disclosure is illustrated, and the wireless communication system 100 enables a network controller repeater (NCR) device to relay wireless communications. The wireless communication system 100 may include one or more network devices 102, one or more UEs 104, a core network 106, and a packet data network 109. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0021] One or more network devices 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network devices 102 described herein may be, may include, or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), a network device, or other suitable terms. The network device 102 and the UE 104 may communicate via a communication link 108, which may be a wireless connection or a wired connection. For example, the network device 102 and the UE 104 may wirelessly communicate (e.g., receive signaling, send signaling) via a user-to-user (Uu) interface.

[0022] The network device 102 may provide a geographic coverage area 110, and the network device 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the network device 102 and the UE 104 may support wireless communications of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network device 102 may be mobile, for example, a satellite 107 associated with a non-terrestrial network and communicating via a satellite link 111. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 110 may be associated with different network devices 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0023] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0024] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1 As shown, UE 104 can communicate with various types of devices, such as network device 102, other UE 104, or network equipment (e.g., core network 106, packet data network 109, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, UE 104 can support communications with other network devices 102 or UE 104 (which can act as a relay in wireless communication system 100).

[0025] UE 104a may also be capable of supporting wireless communications directly with other UE 104b via a communication link 112. For example, UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 112 may be referred to as a side link. For example, UE 104a may support wireless communications directly with another UE 104b via a PC5 interface. PC5 refers to a reference point where UE 104a communicates directly with another UE 104b via a direct channel without the need to communicate with network device 102a.

[0026] The network device 102 may support communication with the core network 106, or with another network device 102, or both. For example, the network device 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, or another network interface). The network devices 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn, or another network interface). In some implementations, the network devices 102 may communicate directly with each other (e.g., between the network devices 102). In some other implementations, the network devices 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more network devices 102 may include a subcomponent (such as an access network entity), which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission and reception points (TRPs).

[0027] In some implementations, the network entity or network device 102 may be configured in a disaggregated architecture that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities or devices 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity or network device 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0028] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission and reception point (TRP). In a disaggregated RAN architecture, one or more components of a network entity or network device 102 may be co-located, or one or more components of a network entity or network device 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities or network devices 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0029] The functional split between CU, DU, and RU can be flexible, and different functions can be supported depending on which function (e.g., network layer function, protocol layer function, baseband function, radio frequency function, and any combination thereof) is performed at the CU, DU, or RU. For example, a functional split of a protocol stack can be adopted between the CU and the DU, so that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and the one or more DUs or RUs can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each can be at least partially controlled by the CU.

[0030] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU, or between the DU and the RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by a different one of the CU, DU, or RU).

[0031] The CU can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU can be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link can be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by the corresponding network entity or network device 102, and the corresponding network entity or network device 102 communicates via such a communication link.

[0032] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for one or more UEs 104 served by one or more network devices 102 associated with the core network 106.

[0033] The core network 106 may communicate with the packet data network 109 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 109 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via a network entity or network device 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0034] In the wireless communication system 100, the network entity or network device 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity or network device 102 and the UE 104 may support different resource structures. For example, the network entity or network device 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity or network device 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity or network device or network device 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity or network device 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0035] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0036] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a 1 ms duration. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0037] Additionally or alternatively, the time interval of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number of time slots (e.g., quantity) for a subframe may depend on the digital technology. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. For a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0038] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz-7.125 GHz), FR2 (24.25 GHz-52.6 GHz), FR3 (7.125 GHz-24.25 GHz), FR4 (52.6 GHz-114.25 GHz), FR4a or FR4-1 (52.6 GHz-71 GHz), and FR5 (114.25 GHz-300 GHz). In some implementations, the network entity or network device 102 and the UE 104 can perform wireless communications on one or more of the operating frequency bands. In some implementations, FR1 can be used by the network entity or network device 102 and the UE 104, as well as other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by network entities or network devices 102 and UEs 104, as well as other equipment or devices for short-range, high data rate capabilities.

[0039] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with: a first digital technology (e.g., μ=0) including a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) including a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with: a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0040] Figure 2 The figure shows a portion of a wireless communication system 100, which includes a network device 102a, an NCR device 130, and a coverage area 110a ( Figure 1 ) outside the UE 104c. Figure 1-Figure 2 , the wireless communication system 100 can extend the coverage area 110a for the network device 102a by including an NCR device 130 that can reach the UE 104c. The NCR device 130 communicates with the network device 102a via both a side control link 132 (which can be referred to as a "C link") and a backhaul link 134. Figure 2 , the side control link 132 terminates at the NCR device 130, which thus acts as an NCR mobile terminal (NCR-MT) 136. The NCR device 130 includes an NCR forwarding portion 138, which receives and amplifies DL radio frequency (RF) signals received via the backhaul link 134, and forwards the DL RF signals to the UE 104c via the access link 140 with minimal delay. Similarly, the NCR forwarding portion 138 receives and amplifies UL RF signals received via the access link 140, and forwards the UL RF signals to the network device 102a via the backhaul link with minimal delay. The network device 102a is able to configure the NCR forwarding portion 138 via configuration information, which is sent to the NCR-MT 136 via the side control link 132.

[0041] Aspects of the present disclosure may be more generally applicable to communication links referenced using different labels.In one or more embodiments, control link 132 may generally be a first link, backhaul link 134 may generally be a second link, and access link 140 may generally be a third link.

[0042] In a first embodiment (Embodiment 1), the present disclosure provides a backhaul link beam indication for an NCR. The NCR-MT is configured with side control information carried by a repeater-specific CORESET. The CORESET is associated with a TCI, a QCL assumption, and a beam ID, which is applicable as a default beam for receiving and forwarding PDCCH and PDSCH (or backhaul DL RF signals) on the backhaul link and sending PUCCH and PUSCH (or backhaul UL / UL RF signals) controlled / indicated / scheduled by the DCI of the CORESET. In one example, the TCI, QCL assumption, and beam ID are applicable as a default beam for receiving backhaul DL RF signals and amplifying and forwarding backhaul UL RF signals. Based on the network configuration, the TCI field for the spatial QCL assumption, the field for the beam ID, or the spatial relationship information to be applied to the NCR forwarding backhaul link may or may not be present in the side control information DCI. In one example, the spatial relationship information indicates the relationship between the spatial filters for receiving physical channels and transmitting physical channels in the NCR forwarding backhaul link, or for receiving the NCR-MT side control information CORESET on the backhaul link and receiving the forwarded physical channels (e.g., via the backhaul DL RF signal). If there is a spatial relationship information field in the side control information DCI, the NCR applies the TCI state / spatial QCL assumption / beam ID, or the spatial relationship information state on all channels of the backhaul link for the corresponding component carrier associated with the spatial information. The DCI field can contain multiple spatial information for multiple component carriers.

[0043] Figure 3 The wireless communication system 100 is illustrated when there is no spatial relationship information in the NRC-MT DCI and when the beam indication for the backhaul forwarding link is performed. The network device 102a sends the first CC (CC#1) 301 via the control link 132 and sends the second CC (CC#2) 302a to the NCR device 130 via the backhaul link 134. The NCR-MT 136 ( Figure 2) is associated with a relatively short "Duration for QCL" value 304, which indicates that the DCI can be decoded after receiving rPDCCH 306 on NCR-MT CORESET 308 in CC#1 301 before receiving or sending physical channels 310 on the backhaul link on CC#2 302a. Physical channels 310 include PDCCH, PDSCH, PUSCH, PDCCH, PDSCH, PDSCH, and PUSCH. The NCR device 130 receives the physical channels based on the activated QCL, beam ID for receiving the NCR-MT CORESET 308. The NCR device 130 sends the relay CC#2 302b to the UE 104c via the access link 140.

[0044] In one implementation, it is determined whether the following conditions exist:

[0045] (i) forwarding PDCCH / PDSCH / PUCCH / PUSCH (or backhauling DL / UL RF signals) on a different component carrier (CC) from the NCR-MT; and

[0046] (ii) Control (or side control information) DCI does not have TCI status / spatial QCL pseudo

[0047] Assume / beam ID, or there is no spatial relationship information field; and

[0048] (iii) Correspondence between the reception of the DCI and the serving cell

[0049] The time offset between the reception of PDCCH / PDSCH / PUCCH / PUSCH (or backhaul DL / UL RF signals) is equal to or greater than a threshold "timeDurationForQCL", where the threshold is based on the reported capability of the NCR-MT for decoding side control information and applying the information on the forwarding link or NCR forwarding backhaul link to determine the time for receiving PDCCH / PDSCH (or backhaul DL RF signals) and / or sending

[0050] The spatial relationship information / antenna port quasi-co-location of PUCCH / PUSCH / SRS (or backhaul UL RF signal). Although NCR-MT can decode the spatial information from DCI,

[0051] But the spatial information does not exist.

[0052] When this condition exists, the NCR assumes the TCI state / spatial QCL assumption / beam ID, or the spatial relationship information for the forwarded PDCCH / PDSCH / PUCCH / PUSCH / SRS (or backhauled DL / UL RF signals) on the NCR forwarding backhaul link is based on TCI / QCL / beam ID (associated with the NCR-MT CORESET used for transmitting side control information) 1, where rPDCCH represents NCR-MT PDCCH.

[0053] Figure 4 The wireless communication system 100 is shown in FIG. 1 when there is spatial relationship information in the NRC-MT DCI and when a beam indication is provided for a backhaul forwarding link. Figure 3 As described above, but with a "longer duration for QCL" value, which results in an inability to decode the spatial information in the DCI for the first part of the physical channels 310a including PDCCH, PDSCH, and PUSCH. The first part of the physical channels 310a is received / sent based on the activated QCL / beam ID for receiving the NCR-MT CORESET. The second part of the physical channels 310b of PDCCH, PDSCH, PDSCH, and PUSCH are received / sent based on the indicated spatial information and beam ID for the NCR-MT DCI.

[0054] In this implementation, determine whether the following conditions exist:

[0055] (i) forwarding PDCCH / PDSCH / PUCCH / PUSCH (or backhauling DL / UL RF signals) on a different component carrier than the NCR-MT; and

[0056] (ii) Control (or side control information) NCR-MT DCI has TCI status / spatial QCL assumption / beam ID, or spatial relationship information field, and

[0057] (iii) the time offset between the reception of the DCI and the reception of the corresponding PDCCH / PDSCH / PUCCH / PUSCH (or backhaul DL / UL RF signal) of the serving cell is less than the threshold timeDurationForQCL,

[0058] The threshold is based on the ability to decode side control information and apply the information on a forwarding link or an NCR forwarding backhaul link to determine the quasi-co-location of antenna ports for receiving PDCCH / PDSCH (or backhauling DL RF signals) and / or sending PUCCH / PUSCH / SRS (or backhauling UL RF signals).

[0059] When this condition exists, the NCR assumes the TCI state / spatial QCL assumption / beam ID, or the spatial relationship information for the forwarded PDCCH / PDSCH / PUCCH / PUSCH / SRS (or backhauled DL / UL RF signals) on the NCR forwarding backhaul link is based on the TCI / QCL / beam ID associated with the NCR-MT CORESET used for transmitting side control information (e.g., in the latest timeslot).

[0060] In another example, if the forwarded PDCCH / PDSCH / PUCCH / PUSCH (or backhauled DL / UL RF signal) is located on a different component carrier from the NCR-MT, and the control DCI has a TCI status / spatial QCL assumption / beam ID, or there is a spatial relationship information field, and the time offset between the reception of the DCI and the reception of the corresponding PDCCH / PDSCH / PUCCH / PUSCH of the serving cell is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on the reported capability of the NCR-MT for decoding side control information and applying the information on the forwarding link to determine the quasi-co-location of antenna ports for receiving PDCCH / PDSCH and / or sending PUCCH / PUSCH / SRS, the NCR applies the TCI status / spatial QCL assumption / beam ID, or the spatial relationship information indicated in the NCR-MT DCI.

[0061] In an alternative embodiment, if the forwarded PDCCH / PDSCH / PUCCH / PUSCH (or backhauled DL / UL RF signals) are located on the same component carrier as the NCR-MT, in order to determine the quasi-co-location of the antenna ports for receiving PDCCH / PDSCH and / or sending PUCCH / PUSCH / SRS, the NCR assumes the TCI state / spatial QCL assumption / beam ID, or the spatial relationship information for the forwarded PDCCH / PDSCH / PUCCH / PUSCH / SRS is based on the TCI / QCL / beam ID (associated with the NCR-MT CORESET used to send side control information within the active BWP of the serving cell).

[0062] In one embodiment, the NCR-MT transmits forwarded PUCCH / PUSCH / SRS (or UL signals received on the NCR forwarded access link) using the same spatial domain transmission filter used to receive forwarded PDCCH / PDSCH / DL RS (or backhauled DL signals on the NCR forwarded backhaul link). The NCR can receive unified DCI for both forwarded DL and forwarded UL, where a single TCI state / spatial relationship information (or joint TCI state) is indicated for both UL and DL of the forwarded (NCR forwarded) backhaul link.

[0063] In a second embodiment (Embodiment 2), the present disclosure provides a beam indication for an NCR backhaul link with multiple transmission and reception points (mTRPs). Figure 5 The diagram shows how Figure 4 The communication system 500 described, but where the network device 102a is an mTRP 502, has a first TRP 504a that sends CC#1 301 on the control link 132 and a second TRP 504b that sends CC#2 302a on the return link 134. In one or more embodiments, for the mTRP, the spatial information can be different even if the CCs used for the two links are the same. Whether the same CC or different CCs, for the mTRP, the spatial information of the return link needs to be signaled or related to the control link.

[0064] According to Embodiment 2, the NCR-MT is configured with side control information carried by the CORESET from the TRP, wherein the CORESET associated with the TCI state / QCL assumption / beam ID carries the DCI to control the forwarded PDCCH / PDSCH / PUCCH / PUSCH (or backhauled DL / UL RF signal) received from and / or sent to another TRP. A single NCR can be used to extend the coverage of multiple TRPs belonging to the same network. Since the spatial information received from and / or sent to different TRPs is different, multiple TCI states / spatial QCL assumptions / spatial relationship information for the forwarded (NCR forwarding) backhaul link can be indicated in the NCR-MT DCI. Each TCI state / spatial QCL assumption / spatial relationship information is associated with a certain TRP.

[0065] If the forwarded PDCCH / PDSCH or PUCCH / PUSCH (or backhaul DL / UL RF signals) is received / sent from a TRP different from the TRP used to control the NCR-MT, and the control DCI has a TCI status / spatial QCL assumption / beam ID, or there is spatial relationship information, and the time offset between the reception of the DCI and the reception of the corresponding PDCCH / PDSCH / PUCCH / PUSCH of the serving cell is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on the reported capability of the NCR-MT for decoding side control information and applying the information on the forwarding link or the NCR forwarding backhaul link to determine the quasi-co-location of the antenna ports for receiving PDCCH / PDSCH (or backhaul DL RF signals) and / or sending PUCCH / PUSCH / SRS (or backhaul UL RF signals), the NCR-MT applies the TCI status / spatial QCL assumption / beam ID, or the spatial relationship information in the NCR-MT DCI for the corresponding TRP associated with the spatial information.

[0066] In a third embodiment (Embodiment 3), the present disclosure provides for determining a timeDurationForQCL value when the NCR-MT and the NCR forwarding operate in different carriers and / or different TRPs. According to Embodiment 3, the NCR-MT is configured with side control information DCI carried by a CORESET, wherein the CORESET is associated with a TCI / QCL assumption / beam ID and a duration for QCL (timeDurationForQCL, e.g., expressed in terms of the number of OFDM symbols) based on the reported capability of the NCR-MT for decoding and applying the side control information on (multiple) corresponding UL / DL time slots. In one implementation, if the NCR DCI carrying the side control information is received on a component carrier different from the component carrier of the forwarding (or NCR forwarding backhaul) link controlled by the DCI, an additional time delay (or offset) is added to the timeDurationForQCL of the NCR-MT. This situation may occur if the subcarrier spacing of the forwarded PDCCH / PDSCH (or DL ​​RF signal on the NCR forwarded backhaul link) is greater than the subcarrier spacing of the NCR-MT CORESET, where in one example the additional delay is proportional to the ratio between the SCS of the forwarded PDCCH / PDSCH (or DL ​​RF signal on the NCR forwarded backhaul link) and the SCS of the CORESET on the control link. In another implementation, if the NCR DCI carrying the side control information is received on a component carrier different from the component carrier of the forwarded link (or NCR forwarded backhaul link) controlled by the DCI, no additional time delay is added to the timeDurationForQCL of the NCR-MT if the subcarrier spacing of the forwarded PDCCH / PDSCH (or DL ​​RF signal on the NCR forwarded backhaul link) is less than or equal to the subcarrier spacing of the NCR-MT CORESET.

[0067] In one implementation, if an NCR DCI carrying side control information is received on a first TRP that is different from a second TRP of a forwarding link (or NCR forwarding backhaul) controlled by the DCI, an additional time delay (or offset) is added to the timeDurationForQCL of the NCR-MT. This may occur if the subcarrier spacing of the forwarded PDCCH / PDSCH (or DL ​​RF signal on the NCR forwarding backhaul link from the second TRP) is greater than the subcarrier spacing of the first TRP from the NCR-MT CORESET. In another implementation, if an NCR DCI carrying side control information is received on a first TRP that is different from a second TRP of a forwarding link (or NCR forwarding backhaul link) controlled by the DCI, no additional time delay is added to the timeDurationForQCL of the NCR-MT if the subcarrier spacing of the forwarded PDCCH / PDSCH (or DL ​​RF signal on the NCR forwarding backhaul link from the second TRP) is equal to or less than the subcarrier spacing of the NCR-MT CORESET from the first TRP.

[0068] In a fourth embodiment (Embodiment 4), the present disclosure provides PDCCH transmission on multiple carriers. According to one or more of the above embodiments, and in one implementation, the base station sends NCR-MT DCI (rPDCCH) on a configured component carrier and / or using multiple TRPs to enhance rPDCCH decoding performance by utilizing frequency and / or spatial diversity. In order to determine the QCL assumption / spatial information for receiving PDCCH / PDSCH (or backhaul DL RF signal) and sending PUCCH / PUSCH / SRS (or backhaul UL RF signal), the NCR uses the QCL assumption / spatial information for receiving NCRCORESET for each component carrier in the component carrier.

[0069] In a first example, the same set of fields of the NCR-MT DCI is sent on a configured component carrier and / or multiple TRPs. In a second example, a set of fields of the NCR-MT DCI is sent on one configured component carrier, and a subset of the set of fields of the NCR-MT DCI is sent on the rest of the configured component carriers.

[0070] In another implementation, the base station sends a predetermined sequence on each component carrier and / or from each TRP to enable the NCR to determine the optimal Tx / Rx beam pair for receiving PDCCH / PDSCH (or backhauled DL RF signals) and sending PUCCH / PUSCH / SRS (or backhauled UL RF signals).

[0071] In another implementation, the base station sends rPDCCH on one component carrier, and based on UL signaling on the forwarding link, the base station determines the relationship between the beam corresponding to one CC and all other beams corresponding to other configured component carriers. The base station signals the information to the NCR-MT for applying the corresponding spatial relationship information to receive / send the forwarded physical channel. In one example, the signaled information is reported in the form of a set of at least one field of the NCR-MT DCI.

[0072] The present disclosure supports a method for wireless communication at an NCR device. The method includes receiving a configuration for an NCR-MT control resource set (CORESET) from a network, the configuration including an indicator for spatial information to be applied on a forwarding link or an NCR forwarding backhaul link. The method includes monitoring the NCR CORESET and decoding spatial relationship information. The method includes determining whether to apply spatial relationship information on a forwarded physical channel or a backhaul DL / UL RF signal of a backhaul link based on an offset between a DCI on the NCR-MT CORESET and a corresponding PDCCH / PDSCH / PUCCH / PUSCH or a backhaul DL / UL RF signal on the NCR forwarding backhaul link.

[0073] In one or more embodiments, the indicator indicates to the repeater the spatial relationship information, TCI, QCL assumption, and / or beam ID for receiving and transmitting RF UL / DL signals in the backhaul link. In one or more embodiments, multiple spatial relationship information is indicated in the NCR-MT DCI for multiple component carriers of the forwarding link. In one or more embodiments, for each component carrier of the forwarding link, a single spatial relationship information is indicated in the NCR-MT DCI for both UL / DL of the backhaul forwarding link.

[0074] In one or more embodiments, if the forwarded physical channel is located on a different component carrier (CC) from the NCR-MT and the control DCI does not have a spatial relationship information field, the NCR assumes that the spatial relationship information or beam ID for the corresponding physical channel is based on the TCI / QCL / beam ID associated with the NCR-MT CORESET used to transmit side control information.

[0075] In one or more embodiments, if the forwarded physical channel is located on a different component carrier (CC) from the NCR-MT and the control DCI has a spatial relationship information field, if the time offset between the reception of the CORESET and the reception of the corresponding PDCCH / PDSCH / PUCCH / PUSCH is less than the NCR-MT threshold timeDurationForQCL, the NCR assumes that the relationship information or beam ID for the corresponding physical channel is based on the TCI / QCL / beam ID associated with the NCR-MT CORESET.

[0076] In one or more embodiments, if the forwarded physical channel is located on a different component carrier (CC) from the NCR-MT and the control DCI has a spatial relationship information field, if the time offset between the reception of the CORESET and the reception of the corresponding PDCCH / PDSCH / PUCCH / PUSCH is greater than the threshold timeDurationForQCL of the NCR-MT, the NCR will apply the spatial relationship information received on the DCI in the NCR-MT CORESET to the forwarded physical channel of the backhaul link or the backhaul DL / UL RF signal.

[0077] In one or more embodiments, if the forwarded physical channel is located on a different component carrier (CC) from the NCR-MT and a spatial relationship information field is present in the control DCI, the NCR applies the spatial information signaled in the DCI to both UL and DL transmissions between the NCR and the base station.

[0078] In one or more embodiments, if the forwarded physical channel is located on the same component carrier (CC) as the NCR-MT, the NCR does not expect to receive spatial information in the DCI, and the NCR applies the QCL assumption associated with the NCR-MT CORESET for the receive / transmit physical channel on the forwarded backhaul link.

[0079] In one or more embodiments, multiple spatial relationship information is indicated in the NCR-MT DCI for forwarded physical channels received from / sent to multiple TRPs. In one or more embodiments, if the subcarrier spacing of the forwarding link is greater than the subcarrier spacing of the C link, the time threshold timeDurationForQCL at the NCR is updated with an additional delay.

[0080] In one or more embodiments, a network device (such as a base station) sends a predetermined sequence on each component carrier to enable the NCR to determine the best Tx / Rx beam pair for receiving PDCCH / PDSCH and sending PUCCH / PUSCH / SRS. In one or more embodiments, the base station sends a relay PDCCH (rPDCCH) on one component carrier, and based on UL signaling on the forwarding link, the base station determines the relationship between the beam corresponding to one CC and all other beams corresponding to other configured component carriers.

[0081] Figure 6 An example of a block diagram 600 of a device 602 supporting beam indication for NCR devices according to aspects of the present disclosure is illustrated. The device 602 may be a network entity or a network device 102 or a UE 104 ( Figure 1 ). Device 602 may support wireless communications with one or more network entities or network devices 102, UE 104, or any combination thereof. Device 602 may include components for bidirectional communications, including components for sending and receiving communications (such as processor 604, memory 606, transceiver 608, and I / O controller 610). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0082] The processor 604, the memory 606, the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 604, the memory 606, the transceiver 608, or various combinations thereof or components thereof may support methods for performing one or more operations described herein.

[0083] In some implementations, the processor 604, memory 606, transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured as or otherwise supports components for performing the functions described in the present disclosure. In some implementations, the processor 604 and the memory 606 coupled to the processor 604 (within the controller 607) may be configured to perform one or more functions as the controller 607, as described herein (e.g., the processor 604 executes instructions stored in the memory 606). In an example, the processor 604 of the device controller 614 executes an NCR beam indication application 609 to act as an NCR-MT when determining a beam indication for configuring the transceiver 608 of the device 602 to perform NCR forwarding.

[0084] The processor 604 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 604 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 604. The processor 604 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 606) to cause the device 602 to perform various functions of the present disclosure.

[0085] The memory 606 may include random access memory (RAM) and read-only memory (ROM). The memory 606 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 604, cause the device 602 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some implementations, the code may not be directly executed by the processor 604, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 606 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0086] I / O controller 610 can manage input and output signals for device 602. I / O controller 610 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 610 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 610 can utilize an operating system, such as

[0087] or another known operating system. In some implementations, I / O controller 610 may be implemented as part of a processor, such as processor 604. In some implementations, a user may interact with device 602 via I / O controller 610 or via hardware components controlled by I / O controller 610.

[0088] In some implementations, the device 602 may include a single antenna 612. However, in some other implementations, the device 602 may have more than one antenna 612 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, and more than one antenna 612 may be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 608 may use one or more receivers 615 and one or more transmitters 617 to perform bidirectional communication via one or more antennas 612, wired links, or wireless links (as described herein). For example, the transceiver 608 may represent a wireless transceiver and may perform bidirectional communication with another wireless transceiver. The transceiver 608 may also include a modem to modulate packets, thereby providing the modulated packets to one or more antennas 612 for transmission, and demodulating packets received from one or more antennas 612.

[0089] According to aspects of the present disclosure, the device 602 may be an NCR device 130 ( Figure 1-Figure 6 The device 602 has at least one transceiver 608, which includes at least one receiver 615 and at least one transmitter 617, which enables the device 602 to communicate with a network entity or network device 102a and a network entity such as UE 104a ( Figure 1 Specifically, at least one transceiver 608 enables the device 602 to: (i) communicate with a user device via (a) a control link 132 ( Figure 1-Figure 5 ) or (b) return link 134 ( Figure 1-Figure 5 ) and the wireless communication system 100( Figure 1 ) of at least one network device 102a ( Figure 1 ) communication; and (ii) via access link 140 ( Figure 1-Figure 5 ) and user equipment (UE 104a( Figure 1)) communication. The controller 607 of the device 602 is communicatively coupled to at least one transceiver 608. The controller 607 receives the wireless communication system 100 ( Figure 1 ) receiving configuration information for a repeater control resource set (CORESET), the configuration information including an indicator of spatial relationship information to be applied to at least one transceiver 608 when transmitting a relayed signal via one of the following: (i) an uplink backhaul link 134 to the wireless communication system 100; Figure 1 ); and (ii) forwarding access link 140 to the user equipment ( Figure 1-Figure 5 ). The controller 607 configures at least one transceiver 608 with the configuration information to monitor the repeater CORESET received on the control link 132. The controller 607 decodes the spatial relationship information based on the indicator. The controller 607 determines an offset between the repeater downlink control information (DCI) on the repeater CORESET and a corresponding one of the following items: (i) a physical channel received by the repeater device on the control link; or (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on the backhaul link; and (iii) a downlink (DL) RF signal sent by the repeater device on the access link. In response to the offset being less than a threshold offset value, the controller 607 applies the spatial relationship information to at least one transceiver.

[0090] In one or more embodiments, the repeater device is a network controlled repeater (NCR) device. The controller 607 includes a controller 607 that communicates with the repeater device via a control link 140 ( Figure 1-Figure 5 ) is an NCR mobile terminal (MT) that communicates with at least one network node. The repeater CORESET is an NCR MT CORESET. In one or more embodiments, the physical channel received by the repeater device is via a repeater physical downlink control channel (rPDCCH) on the first link, the UL RF signal sent by the repeater device is via one or more of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) on the second link, and the DL RF signal sent by the repeater device is via one or more of a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) on the third link.

[0091] In one or more embodiments, when applying the spatial relationship information to at least one transceiver, the controller 607 semi-statically configures the at least one transceiver with a default pattern of beams for more than one transmit and receive positions (TRPs), the more than one TRPs including a first TRP and a second TRP. The default pattern includes a periodic plurality of time slots. The default beam is periodically oriented toward the first TRP for a first integer "M" number of time slots in the plurality of time slots, and then oriented toward the second TRP for a second integer "N" number of time slots in the plurality of time slots.

[0092] In one or more embodiments, the indicator of the spatial relationship information is applied to configure at least one transceiver to transmit to the user equipment on the access link. The controller 607 receives the DL RF signal to be relayed from at least one network node via the backhaul link. The controller 607 sends the DL RF signal to the user equipment via the access link. In one or more embodiments, the controller 607 identifies one or more of the transmission configuration indicator (TCI), quasi co-location (QCL) assumption, and beam identifier (ID) for receiving and transmitting UL RF signals and DL RF signals respectively via the backhaul link based on the indicator. In one or more specific embodiments, when decoding the spatial relationship information, in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does not include a spatial relationship information field, the controller 607 determines that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of the TCI, QCL, and beam ID associated with the repeater CORESET for transmitting side control information.

[0093] In one or more specific embodiments, when decoding spatial relationship information, in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does include a spatial relationship information field, and when the time offset between receiving the repeater CORESET and receiving the corresponding physical channel is less than the "duration for QCL" value associated with the repeater device, the controller 607 determines that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of the TCI, QCL, and beam ID associated with the repeater CORESET.

[0094] In one or more specific embodiments, the controller 607, in response to determining that the forwarded physical channel is located on the same component carrier (CC) as the repeater CORESET: (i) determines that the repeater DCI does not include a spatial relationship information field; (ii) identifies the spatial information used to configure the transceiver to communicate via the control link; and (iii) applies the QCL assumption to use the spatial information associated with the control link and the repeater CORESET for receiving and transmitting the physical channel on the backhaul link.

[0095] In one or more embodiments, at least one network node includes more than one network node located at multiple transmission points (TRPs). Multiple spatial relationship information is indicated in the repeater DCI for forwarded physical channels received from and sent to the multiple TRPs, respectively. In one or more embodiments, when decoding the spatial relationship information, the controller 607: (i) decodes for each component carrier, a single spatial relationship information is indicated in the repeater DCI for both the UL RF signal and the DL RF signal on the backhaul link; and (ii) applies the single spatial relationship information to the transceiver for each component carrier to communicate via the backhaul link.

[0096] In one or more embodiments, in response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does include a spatial relationship information field, the controller 607 determines a threshold offset value based on a "time-duration-for-QCL value" associated with the repeater device. In one or more specific embodiments, the controller 607 increases the "duration-for-QCL" value in response to determining that the subcarrier spacing of the forwarding link is greater than the subcarrier spacing of the control link. In one or more specific embodiments, the controller 607 also determines the threshold offset value based on the "duration-for-QCL" value associated with the repeater device in response to determining that the repeater device does not support multiple panels.

[0097] In one or more embodiments, in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does include a spatial relationship information field, the controller 607 applies the spatial relationship information received on the repeater DCI in the repeater CORESET to both the DL RF signals and the UL RF signals communicated between the repeater device and at least one network node.

[0098] In one or more embodiments, the controller 607 receives at least one predetermined sequence from the network on each component carrier. The controller 607 determines the best transmit-receive pair for receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH), and for transmitting a physical uplink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS).

[0099] In one or more embodiments, the controller 607 receives a relay physical downlink control channel (rPDCCH) from the network on one of more than one configured component carriers (CCs). The controller 607 configures the transceiver based on the rPDCCH. The controller 607 sends UL RF signaling on a control link via more than one configured CC to enable at least one network node to determine a relationship between a beam corresponding to one CC and a beam corresponding to at least one other configured CC.

[0100] Figure 7 1 is a flow chart of a method 700 that enables an NCR device to determine a beam indication using a side control link according to aspects of the present disclosure. The operations of the method 700 may be implemented by a device or component thereof as described herein. For example, the operations of the method 700 may be implemented by an NCR device such as the NCR device 130 ( Figure 1-Figure 5 ) or device 602( Figure 6 ) is performed by a repeater device of the network device. In some implementations, the user device can execute an instruction set to control the functional elements of the network device to perform the described functions. Additionally or alternatively, the user device can use dedicated hardware to perform aspects of the described functions.

[0101] At 705, method 700 may include receiving, via at least one transceiver of a repeater device, configuration information for a repeater control resource set (CORESET) from at least one network node, the configuration information including an indicator of spatial relationship information to be applied to the transceiver when transmitting a relayed signal via one of: (i) a backhaul link to a network; and (ii) an access link to a user device, the at least one transceiver being communicatively coupled to the at least one network node via (i) a control link; and (ii) a backhaul link. The operations of 705 may be performed according to examples described herein. In some implementations, aspects of the operations of 705 may be performed by reference to Figure 1-Figure 6 The described device performs.

[0102] At 710, method 700 may include configuring at least one transceiver with configuration information to monitor a repeater CORESET received on a control link. The operations of 710 may be performed according to examples described herein. In some implementations, aspects of the operations of 710 may be described with reference to Figure 1-Figure 6 The described device performs.

[0103] At 715, method 700 may include decoding spatial relationship information based on the indicator. The operations of 715 may be performed according to the examples described herein. In some implementations, aspects of the operations of 715 may be described with reference to Figure 1-Figure 6 The described device performs.

[0104] At 720, method 700 may include determining an offset between repeater downlink control information (DCI) on the repeater CORESET and a corresponding one of: (i) a physical channel received by the repeater device on the control link; (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on the backhaul link; or (iii) a downlink (DL) RF signal sent by the repeater device on the access link. The operations of 720 may be performed according to the examples described herein. In some implementations, aspects of the operations of 720 may be performed by reference to Figure 1-Figure 6 The described device performs.

[0105] At 725, method 700 may include, in response to the offset being less than a threshold offset value, applying the spatial relationship information to at least one transceiver. The operations of 725 may be performed according to examples described herein. In some implementations, aspects of the operations of 725 may be described with reference to Figure 1-Figure 6 The described device performs.

[0106] In one or more embodiments, the repeater device is a network controlled repeater (NPR) device. The repeater CORESET is an NCR mobile terminal (MT) CORESET. Method 700 may include communicating with at least one network node via a control link using the NCR MT. In one or more embodiments, the physical channel received by the repeater device is via a repeater physical downlink control channel (rPDCCH) on a first link, the UL RF signal sent by the repeater device is via one or more of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) on a second link, and the DL RF signal sent by the repeater device is via one or more of a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) on a third link.

[0107] In one or more embodiments, applying spatial relationship information to at least one transceiver includes semi-statically configuring at least one transceiver with a default pattern of beams for more than one transmit and receive positions (TRPs), the more than one TRPs including a first TRP and a second TRP. The default pattern includes a periodic plurality of time slots, wherein the default beam is periodically oriented toward the first TRP for a first integer "M" number of time slots in the plurality of time slots, and then oriented toward the second TRP for a second integer "N" number of time slots in the plurality of time slots.

[0108] In one or more embodiments, the indicator of the spatial relationship information identifies configuration details for at least one transceiver to transmit to the user equipment on the access link. The method 700 may also include receiving a DL RF signal to be relayed from at least one network node via a backhaul link; and transmitting the DL RF signal to the user equipment via the access link.

[0109] In one or more embodiments, method 700 may include identifying one or more of a transmission configuration indicator (TCI), a quasi co-location (QCL) assumption, and a beam identifier (ID) for receiving and transmitting UL RF signals and DL RF signals, respectively, via a backhaul link based on the indicator.

[0110] In one or more embodiments, method 700 may include decoding spatial relationship information in the following manner: in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does not include a spatial relationship information field, determining that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of the TCI, QCL, and beam ID associated with the repeater CORESET used to transmit side control information.

[0111] In one or more embodiments, method 700 may include decoding spatial relationship information in the following manner: in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does include a spatial relationship information field, and when the time offset between receiving the repeater CORESET and receiving the corresponding physical channel is less than the "duration for QCL" value associated with the repeater device, the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of the TCI, QCL, and beam ID associated with the repeater CORESET.

[0112] In one or more embodiments, method 700 may include: in response to determining that the forwarded physical channel is located on the same component carrier (CC) as the repeater CORESET: (i) determining that the repeater DCI does not include a spatial relationship information field; (ii) identifying spatial information used to configure the transceiver to communicate via a control link; and (iii) applying a QCL assumption to use the spatial information associated with the control link and the repeater CORESET for receiving and transmitting the physical channel on the backhaul link.

[0113] In one or more embodiments, the at least one network node includes more than one network node located at multiple transmission points (TRPs). The method 700 may include receiving, in a relay DCI, an indication of multiple spatial relationship information for forwarded physical channels received from and sent to the multiple TRPs, respectively.

[0114] In one or more embodiments, method 700 may include decoding the spatial relationship information by: (i) identifying, for each component carrier, indicating a single spatial relationship information in a repeater DCI for both UL RF signals and DL RF signals on a backhaul link; and (ii) applying the single spatial relationship information to a transceiver for each component carrier to communicate via the backhaul link.

[0115] In one or more embodiments, method 700 may include: in response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does include a spatial relationship information field, determining a threshold offset value based on a "duration used for QCL" value associated with the repeater device. In one or more specific embodiments, method 700 may include: in response to determining that the subcarrier spacing of the forwarding link is greater than the subcarrier spacing of the control link, increasing the "duration used for QCL" value. In one or more specific embodiments, determining the threshold offset value based on the "duration used for QCL" value associated with the repeater device is also in response to determining that the repeater device does not support multiple panels.

[0116] In one or more embodiments, method 700 may include: in response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and the repeater DCI does include a spatial relationship information field, applying the spatial relationship information received on the repeater DCI in the repeater CORESET to both the DL RF signals and the UL RF signals communicated between the repeater device and at least one network node.

[0117] In one or more embodiments, the method 700 may include receiving at least one predetermined sequence from the network on each component carrier (CC). The method 700 may include measuring one or more of the received signal power and quality of at least one predetermined sequence on each CC. The method 700 may include comparing the measurements for each CC. The method 700 may include determining the best transmit-receive pair for receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH), for sending a physical uplink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS).

[0118] In one or more embodiments, the method 700 may include receiving a relay physical downlink control channel (rPDCCH) from at least one network node on one of more than one configured component carriers (CCs). The method 700 may include configuring a transceiver based on the rPDCCH. The method 700 may include sending uplink RF signaling on a control link via more than one configured CC to enable at least one network node to determine a relationship between a beam corresponding to one CC and at least one other configured CC.

[0119] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0120] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0121] Computer-readable media include both non-transient computer storage media and communication media, and the communication media include any medium that facilitates the transfer of computer programs from one place to another. Non-transient storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or any other non-transient medium of a general-purpose or special-purpose processor.

[0122] Any connection can be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically using lasers. The above combination is also included in the scope of computer-readable media.

[0123] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may 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 "based at least in part on." In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0124] When referring to a network entity, the terms "transmit," "receive," or "communicate" may refer to any part of a network entity of a RAN (e.g., a base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0125] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technology can be practiced without this specific detail. In some instances, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0126] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A repeater device for wireless communication, the repeater device comprising: at least one transceiver to enable the repeater device to (i) communicate with at least one network node of the network via (a) the first link or (b) the second link; and (ii) communicating with the user equipment via a third link; as well as a controller communicatively coupled to the at least one transceiver and the controller: receiving configuration information for a relay control resource set (CORESET) from the network via a downlink first link, the configuration information comprising an indicator of spatial relationship information to be applied to the transceiver when transmitting a relayed signal via one of: (i) an uplink second link to the network; as well as (ii) forwarding a third link to the user equipment; configuring the at least one transceiver using the configuration information to monitor the repeater CORESET received on the first link; decoding the spatial relationship information based on the indicator; determining an offset between repeater downlink control information (DCI) on the repeater CORESET and a corresponding one of: (i) a physical channel received by the repeater device on the first link; or (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on the second link; and (iii) a downlink (DL) RF signal sent by the repeater device on the third link; as well as In response to the offset being less than a threshold offset value, the spatial relationship information is applied to the at least one transceiver.

2. The repeater device according to claim 1, wherein: The repeater device comprises a network controlled repeater (NCR) device; The first link comprises a control link; The second link includes a backhaul link; The third link comprises an access link; The controller includes an NCR mobile terminal (MT) in communication with the at least one network node via the first link; as well as The repeater CORESET includes NCR MT CORESET.

3. The repeater device according to claim 2, wherein: The physical channel received by the relay device is received via a relay physical downlink control channel (rPDCCH) on the first link; The UL RF signal transmitted by the relay device is transmitted via one or more of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) on the second link; and The DL RF signal transmitted by the relay device is transmitted via one or more of a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) on the third link.

4. A repeater device according to claim 1, wherein when applying the spatial relationship information to the at least one transceiver, the controller semi-statically configures the at least one transceiver using a default pattern of beams for more than one multiple transmit and receive positions (TRPs), the more than one multiple TRPs including a first TRP and a second TRP, the default pattern including a periodic plurality of time slots, wherein the default beam is periodically oriented toward the first TRP for a first integer "M" number of time slots in the plurality of time slots, and then oriented toward the second TRP for a second integer "N" number of time slots in the plurality of time slots.

5. The repeater device according to claim 1, wherein: The indicator of the spatial relationship information is used to configure the at least one transceiver to transmit to the user equipment on the third link; and The controller: receiving the DL RF signal to be relayed from the at least one network node via the second link; and The DL RF signal is sent to the user equipment via the third link.

6. The repeater device of claim 1, wherein the controller identifies one or more of the following based on the indicator: a transmission configuration indicator (TCI) for receiving and sending the UL RF signal and the DL RF signal, respectively, via the second link, a quasi co-location (QCL) assumption, and a beam identifier (ID).

7. The repeater device according to claim 6, wherein when decoding the spatial relationship information, the controller: In response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET and the repeater DCI does not include a spatial relationship information field, determining that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of: the TCI associated with the repeater CORESET used for sending side control information, the QCL, and the beam ID.

8. The repeater device according to claim 7, wherein when decoding the spatial relationship information, the controller: In response to determining that the forwarded physical channel is located on a different component carrier (CC) from the repeater CORESET, and the repeater DCI does include a spatial relationship information field, and when the time offset between receiving the repeater CORESET and receiving the corresponding physical channel is less than the "duration for QCL" value associated with the repeater device, determining that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of: the TCI associated with the repeater CORESET, the QCL, and the beam ID.

9. The repeater device according to claim 7, wherein the controller: In response to determining that the forwarded physical channel is located on the same component carrier (CC) as the repeater CORESET: Determining that the repeater DCI does not include a spatial relationship information field; identifying spatial information used to configure the transceiver to communicate via the first link; as well as A QCL assumption is applied to use the spatial information associated with the first link and the repeater CORESET for receiving and transmitting the physical channel on the second link.

10. The repeater device according to claim 1, wherein when decoding the spatial relationship information, the controller: decoding, for each component carrier, indicating in the relay DCI a single spatial relationship information for both the UL RF signal and the DL RF signal on the second link; and The single spatial relationship information is applied to the transceiver for each component carrier to communicate via the second link.

11. The repeater device according to claim 1, wherein the controller: In response to determining that the forwarded physical channel is located on a different component carrier (CC) than the relay CORESET, and the relay DCI does include a spatial relation information field: determining the threshold offset value based on a "duration for QCL" value associated with the repeater device; and In response to determining that the subcarrier spacing of the forwarding link is greater than the subcarrier spacing of the first link, increasing the "duration for QCL" value.

12. The repeater device of claim 12, wherein the controller determines the threshold offset value based on the "duration for QCL" value associated with the repeater device further in response to determining that the repeater device does not support multiple panels.

13. The repeater device of claim 1, wherein the controller: In response to determining that the forwarded physical channel is located on a component carrier (CC) different from the repeater CORESET, and that the repeater DCI does include a spatial relationship information field, the spatial relationship information received on the repeater DCI in the repeater CORESET is applied to both the DL RF signal and the UL RF signal communicated between the repeater device and the at least one network node.

14. The repeater device of claim 1, wherein the controller: receiving at least one predetermined sequence from the network on each component carrier; and Determine the best transmit / receive pair for receiving the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH), and for sending the physical uplink control channel (PDCCH), the physical uplink shared channel (PUSCH), and the sounding reference signal (SRS).

15. The repeater device of claim 1, wherein the controller: receiving a relay physical downlink control channel (rPDCCH) from the network on one of more than one configured component carriers (CCs); configuring the transceiver based on the rPDCCH; and UL RF signaling is sent on the first link via the more than one configured CCs to enable the at least one network node to determine a relationship between a beam corresponding to the one CC and at least one other configured CC.

16. A controller for wireless communication via a repeater device, the controller comprising: a memory having stored therein code for network controlled repeater (NCR) beam indication; a processor, communicatively coupled to the memory and processing the code, the code configuring the controller to: receiving configuration information for a relay control resource set (CORESET) from the network via a downlink first link, the configuration information comprising an indicator of spatial relationship information to be applied to the transceiver when transmitting a relayed signal via one of: (i) an uplink second link to the network; as well as (ii) forwarding a third link to the user equipment; configuring the at least one transceiver using the configuration information to monitor the repeater CORESET received on the first link; decoding the spatial relationship information based on the indicator; determining an offset between repeater downlink control information (DCI) on the repeater CORESET and a corresponding one of: (i) a physical channel received by the repeater device on the first link; or (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on the second link; and (iii) a downlink (DL) RF signal sent by the repeater device on the third link; as well as In response to the offset being less than a threshold offset value, the spatial relationship information is applied to the at least one transceiver.

17. The controller of claim 16, wherein processor execution of the code further configures the controller to: identifying, based on the indicator, one or more of: a transmission configuration indicator (TCI), a quasi co-location (QCL) assumption, and a beam identifier (ID) for receiving and transmitting the UL RF signal and the DL RF signal, respectively, via the second link; and In order to decode the spatial relationship information, the controller: In response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does not include a spatial relationship information field, determining that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of: the TCI associated with the repeater CORESET used for transmitting side control information, the QCL, and the beam ID; In response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does include a spatial relationship information field, when a time offset between receiving the repeater CORESET and receiving the corresponding physical channel is less than a "duration for QCL" value associated with the repeater device, basing the spatial relationship information or beam identifier (ID) for the corresponding physical channel on one or more of: the TCI associated with the repeater CORESET, the QCL, and the beam ID; and In response to determining that the forwarded physical channel is located on the same component carrier (CC) as the repeater CORESET: Determining that the repeater DCI does not include a spatial relationship information field; identifying spatial information used to configure the transceiver to communicate via the first link; as well as A QCL assumption is applied to use the spatial information associated with the first link and the repeater CORESET for receiving and transmitting the physical channel on the second link.

18. A method for wireless communication via a repeater device, the method comprising: receiving, via at least one transceiver of the repeater device, configuration information for a repeater control resource set (CORESET) from at least one network node, the configuration information comprising an indicator of spatial relationship information to be applied to the transceiver when transmitting a signal being relayed via one of: (i) a second link to the network; and (ii) a third link to a user equipment, the at least one transceiver being connected via (i) the first link; and (ii) the second link is communicatively coupled to the at least one network node; configuring the at least one transceiver using the configuration information to monitor the repeater CORESET received on the first link; decoding the spatial relationship information based on the indicator; determining an offset between repeater downlink control information (DCI) on the repeater CORESET and a corresponding one of: (i) a physical channel received by the repeater device on the first link; (ii) an uplink (UL) radio frequency (RF) signal sent by the repeater device on the second link; or (iii) a downlink (DL) RF signal sent by the repeater device on the third link; and In response to the offset being less than a threshold offset value, the spatial relationship information is applied to the at least one transceiver.

19. The method of claim 18, wherein applying the spatial relationship information to the at least one transceiver comprises: The at least one transceiver is semi-statically configured with a default pattern of beams for more than one plurality of transmit and receive positions (TRPs), the more than one plurality of TRPs including a first TRP and a second TRP, the default pattern comprising a periodic plurality of time slots, wherein the default beam is periodically oriented toward the first TRP for a first integer "M" number of time slots in the plurality of time slots, and then oriented toward the second TRP for a second integer "N" number of time slots in the plurality of time slots.

20. The method of claim 18, further comprising: identifying, based on the indicator, one or more of: a transmission configuration indicator (TCI), a quasi co-location (QCL) assumption, and a beam identifier (ID) for receiving and transmitting the UL RF signal and the DL RF signal, respectively, via the second link; as well as Wherein decoding the spatial relationship information comprises: In response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does not include a spatial relationship information field, determining that the spatial relationship information or beam identifier (ID) for the corresponding physical channel is based on one or more of: the TCI associated with the repeater CORESET used for transmitting side control information, the QCL, and the beam ID; In response to determining that the forwarded physical channel is located on a different component carrier (CC) than the repeater CORESET, and the repeater DCI does include a spatial relationship information field, when a time offset between receiving the repeater CORESET and receiving the corresponding physical channel is less than a "duration for QCL" value associated with the repeater device, basing the spatial relationship information or beam identifier (ID) for the corresponding physical channel on one or more of: the TCI associated with the repeater CORESET, the QCL, and the beam ID; and In response to determining that the forwarded physical channel is located on the same component carrier (CC) as the repeater CORESET: Determining that the repeater DCI does not include a spatial relationship information field; identifying spatial information used to configure the transceiver to communicate via the first link; and A QCL assumption is applied to use the spatial information associated with the first link and the repeater CORESET for receiving and transmitting the physical channel on the second link.

Images