Power efficient sub-THz deployment with multi-hop link

Abstract

An apparatus, a method, and a computer program product for communicating with sub-terahertz (THz) are provided. An example method may include establishing a first communication with a network entity on a primary cell. The example method may also include receiving, from the network entity, an activation for a sub-terahertz (THz) relay operation for the wireless device, the sub-THz relay operation being on a first frequency range of the first communication that does not include the second frequency. The example method may also include amplifying and forwarding at least one data channel transmission as part of the sub-THz relay operation.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Israel Patent Application Serial No. 296244, filed on September 6, 2022, entitled “POWER EFFICIENT SUB-THZ DEPLOYMENT WITH MULTI-HOP LINKS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems having sub-terahertz (THz) communications. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a first communication with a user equipment (UE) and at least one sub-THz (THz) repeater on a primary cell. The memory and the at least one processor coupled to the memory may be further configured to receive a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for the sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being in a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range. The memory and the at least one processor coupled to the memory may be further configured to send an activation for the sub-THz communication to the UE. The memory and the at least one processor coupled to the memory may be further configured to transmit activation for the sub-THz communication for each of the at least one sub-THz repeater. The memory and the at least one processor coupled to the memory may be further configured to communicate scheduling information for at least one data channel transmission via the primary cell. The memory and the at least one processor coupled to the memory may be further configured to communicate the at least one data channel transmission via the at least one sub-THz repeater and the sub-THz communication.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a repeater are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a first communication with a network entity on a primary cell. The memory and the at least one processor coupled to the memory may be configured to receive activation of a sub-THz relay operation for the wireless device from the network entity, the sub-THz relay operation being at a first frequency range of the first communication that does not include a second frequency. The memory and the at least one processor coupled to the memory may be further configured to amplify and forward at least one data channel transmission as part of the sub-THz relay operation.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example sub-THz deployment.

[0017] Figure 5 are diagrams illustrating different scenarios for sub-THz deployment.

[0018] Figure 6 is a diagram illustrating example communications between a network entity and a UE via one or more relays.

[0019] Figure 7 is a flow chart of a method of wireless communication.

[0020] Figure 8 is a flow chart of a method of wireless communication.

[0021] Fig. 9 is a flow chart of a method of wireless communication.

[0022] Fig.10 is a flow chart of a method of wireless communication.

[0023] Fig.11 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0024] Fig.12 is a diagram illustrating an example of a hardware implementation for a network entity. DETAILED DESCRIPTION

[0025] The example methods provided herein may include a single-hop or multi-hop link / relay between a sub-THz UE and a sub-THz network entity transceiver. Sub-THz deployments based on sub-THz multi-hop links can be addressed using inter-band carrier aggregation and as Scells that can be dynamically activated and deactivated for each UE to improve power efficiency, while the link establishment / activation process can be significantly simplified by strongly relying on Pcell connectivity in many aspects to allow low-complexity and low-latency dynamic activation. Multi-hop links on sub-THz can be based on one or more sub-THz NW-controlled repeaters with out-of-band (OOB) control based on Pcell connectivity. The repeaters involved in the multi-hop link can be dynamically activated / deactivated according to the Scell / sub-THz link activation / deactivation for the corresponding sub-THz UE.

[0026] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic part, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0029] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0031] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0032] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0035] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0036] In some aspects, CU 110 may host one or more high-level control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] The low-level functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based on functional splitting such as lower-level functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0039] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0040] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0041] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0042] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0043] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0045] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0048] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0049] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0050] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0051] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0052] Reference again Figure 1In some aspects, the base station 102 or a network entity (such as a repeater) may include a communication component 199. In some aspects, the communication component 199 may be configured to establish a first communication with a user equipment (UE) and at least one sub-THz repeater on a primary cell. In some aspects, the communication component 199 may be configured to receive a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being in a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication for the UE. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication for each of the at least one sub-THz repeaters. In some aspects, the communication component 199 may be configured to communicate scheduling information for at least one data channel transmission via the primary cell. In some aspects, the communication component 199 may be configured to communicate at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. In some aspects, the communication component 199 may be configured to establish a first communication with a network entity on a primary cell. In some aspects, the communication component 199 may be configured to receive activation of a sub-THz relay operation for a wireless device from the network entity, the sub-THz relay operation being at a first frequency range of the first communication that does not include a second frequency. In some aspects, the communication component 199 may be configured to amplify and forward at least one data channel transmission as part of the sub-THz relay operation.

[0053] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0054] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0055] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or sent by the first network node.

[0056] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling).

[0057] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0058]

[0059] Table 1: Parameter set, SCS and CP

[0060] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0061] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0064] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0065] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0066] Figure 3370 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0067] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0068] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0072] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0073] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The communication component 199 combines various aspects.

[0075] Sub-THz may refer to a frequency range greater than 90 GHz and less than 1 THz (e.g., less than 300 GHz). Sub-THz communications may be used in wireless communication systems to increase overall communication capacity and throughput. For large-scale sub-THz deployments, there may be several challenges. First, sub-THz may be associated with lower maximum power amplifier (PA) PA output power characteristics (e.g., about 10 decibels (dB) less than the millimeter wave (mmW) band). Due to the much higher signal bandwidth (BW) and relatively low maximum PA output power for sub-THz, sub-THz links may have insufficient effective isotropic radiated power (EIRP). Correspondingly, this insufficient EIRP may result in more limited sub-THz link coverage (one of the main challenges of sub-THz links) compared to the mmW band. The sub-THz EIRP deficiency can be partially compensated by higher BF gain, but this is limited by practical beamwidth considerations (higher beamformer gain / directivity results in narrower beams, which leads to unstable systems, where maintaining accurate beam tracking / beam management processes may be very challenging).

[0076] In addition, for sub-THz deployment, because the sub-THz PA efficiency may be at least reduced by half (e.g., compared to mmW), the sub-THz link power consumption characteristics / energy efficiency may be poor. Correspondingly, another challenge associated with sub-THz deployment may be the higher power consumption (compared to lower frequencies) of sub-THz Rx / Tx (e.g., due to higher signal BW and lower PA power efficiency) and extremely high data rates. Higher power consumption may be caused by lower power efficient RF processing, higher power consumption related to analog / digital or digital / analog components with increased sampling rates (which can be approximately linearly converted into increased power consumed), higher rate digital processing, high bit rates to be addressed on the decoder side, higher memory / storage (intermediate buffer) related power consumption, etc. The various aspects provided herein provide mechanisms for solving challenges associated with sub-THz while providing the benefits of extremely high data rates / link capacity that can be achieved using sub-THz communications. In some aspects, sub-THz communications may be used via non-independent (non-SA) or non-self-contained deployments (e.g., deployed with other frequency bands such as FR1 / FR2 and not deployed by themselves). In some aspects, sub-THz communications may be used to offload UE data / cell traffic from "data hungry" UEs using high data rates. In some aspects, sub-THz communications may be used to offload traffic (e.g., DL / UL traffic) by utilizing sub-THz "access points" (APs) (and may be otherwise referred to as "repeaters") in areas with high data volume demand potential. In some aspects, these APs may provide high capacity channels on demand for UEs that meet sub-THz conditions (e.g., support sub-THz communications and meet a list of prerequisites) that are registered and continuously connected to a lower frequency band primary cell or "primary" cell (e.g., a FR1 / FR2 based cell, which may also be referred to as a "PCell" or "Pcell", or may also be referred to as a secondary cell on a lower frequency band compared to the sub-THz band), and these APs may provide increased capacity local point-based coverage under a wider Pcell (e.g., FR1 based Pcell) or lower frequency band Scell ​​(e.g., FR2 based Scell) coverage. Sub-THz communications may be supplementary high-capacity channels that may be deployed as secondary cells (which may also be referred to as "SCells" or "Scells") with bursty activity patterns for timely sparse use by sub-THz eligible UEs. As one of the prerequisites for more power-efficient point-based non-SA sub-THz deployments that will rely on inter-band carrier aggregation, sub-THz eligible UEs should be continuously connected to the PCell via lower frequency bands (e.g., FR1 / FR2 / FR4).As used herein, the terms "primary cell" or "primary cell" may be used interchangeably and may refer to a low-band cell that establishes an initial connection between a sub-THz eligible UE and a gNB and maintains a connection continuously, and this continuous connection is used as a reference for coarse synchronization and beam management processes based on a higher-band Scell ​​(e.g., sub-THz based), and also for all registrations and any control plane signaling of a sub-THz based secondary cell. As used herein, the term "secondary cell" may refer to a non-primary cell. Correspondingly, the sub-THz based Scell ​​will support the minimum range of critical functionality and will strongly rely on Pcell connectivity in many aspects (sub-THz related control signaling, coarse synchronization and coarse beam management to support dynamic low latency and low power and low complexity activation / deactivation processes). The sub-THz based Scell ​​will allow point-based coverage under the coverage of the lower-band Pcell, and will be mainly used for large-scale data offloading using relatively short data offloading sessions for sub-THz eligible UEs (meeting the prerequisites). This type of sub-THz deployment (Scells with minimal scope for critical functionality and strong dependency on Pcell / “primary” cells allowing for dynamic low latency, low complexity activation / deactivation procedures to support bursty activity modes of sub-THz Scells) is believed to allow for improved power efficiency of sub-THz deployments for a wider range of scenarios and use cases.

[0077] Figure 4 4 is a diagram illustrating an example sub-THz deployment. By way of example, a network entity (e.g., a gNB or a different type of network entity) 402 and UEs 404A, UE 404B, UE 404C, UE 404D and RP 406A, AP 406B, AP 406C, and AP 406D are illustrated. Figure 4As illustrated, inter-band carrier aggregation (CA) may be used, where sub-THz is used on a Scell ​​providing point-based sub-THz coverage over a wider Pcell coverage range, and the Pcell may be based on a lower frequency band (FR1 / FR2 / FR4). The sub-THz Scell ​​may support minimal critical range functionality and may rely on the Pcell / lower frequency band cell in many aspects, such that the Scell ​​may not support any "always on" signals or resource reservations (e.g., signals that are always present on the sub-THz Scell, such as SSB or RACH opportunities or any periodic RS signals or control signaling resources). In some aspects, the Scell ​​may be dynamically activated on demand, for example, for occasional and short sessions that may have bursty activity patterns. Coarse synchronization and beam management for the Scell / sub-THz may be determined based on the lower frequency band Pcell / "primary" cell. There may be a complementary synchronization and beam refinement process performed for each Scell ​​activation, and the Scell ​​synchronization and beam management (BM) may be based at least in part on the Pcell. As Figure 4As illustrated, there may be single-hop or multi-hop duplication (e.g., enabled by RP 406A and AP 406D to UE 404D) between the sub-THz UE and the sub-THz network entity (e.g., network entity 402) transceiver to bridge within a limited sub-THz range. The AP (or another type of smart repeater, such as RP 406A) may be an efficient smart repeater with out-of-band (OOB) control of Pcell connectivity based on all sub-THz link components (UE, AP, or intermediate repeaters in the case of multi-hop sub-THz links). The AP may include different functional parts, including: (1) a reduced capability (RedCap) UE (RC UE) for Pcell connectivity (e.g., providing OOB control / reporting / feedback); (2) analog amplification and forwarding (AF) functionality for sub-THz data forwarding; and (3) a dedicated network entity for sub-THz local complementary synchronization and beam management sessions using dedicated synchronization and beam management RS (or modified waveform positioned in time SSB mini-burst) Tx / Rx capabilities on the Scell's sub-THz. Multi-hop sub-THz links can use progressive synchronization across hops, using hop-specific synchronization and BM sessions with customized synchronization and BM RS / SSB mini-burst scheduling (through the gNB on the Pcell) to establish / activate and synchronize to send and receive from a first sub-THz hop edge (Tx side) to a corresponding second sub-THz hop edge (Rx side to be synchronized on the Tx side). Based on the aspects provided herein, the synchronization and beam management process can be a fast, low-power, low-latency, and per-Scell ​​activated process. In some aspects, to qualify for a sub-THz session, a UE may be within sub-THz AP or base station coverage, may have mobility less than a threshold (e.g., for semi-static sub-THz beams and channels), may have sub-THz capabilities, may have sufficient battery resources, and may have data volume potential or specifications above a threshold.

[0078] In some aspects, sub-THz communications may be supported in a non-SA manner as a Scell ​​(or secondary component carrier), while a corresponding Pcell (or primary component carrier) may be on a lower frequency range (e.g., FR1 / FR2 / FR4) and may serve as primary cell connectivity to support sub-THz communications (which may have a bursty activity mode). In some aspects, the term "Pcell" may be used interchangeably with the term "primary component carrier", and the term "Scell" may be used interchangeably with the term "secondary component carrier".

[0079] In some aspects, when a sub-THz qualified UE has connectivity on both FR1 and FR2 / FR4 cells / CCs, the higher frequency band associated cell / CC may be used as a primary cell for sub-THz communications even though it is not considered a Pcell from a network perspective. For example, if multiple FR1 CCs and multiple FR2 CCs are activated for a sub-THz qualified UE, where one of the FR1 CCs is configured as a primary CC (Pcell), then in the context of sub-THz connectivity, one of the FR2 CCs would be addressed as a "primary cell" / CC for sub-THz. In some aspects, a network entity or transceiver supporting sub-THz communications may or may not be collocated with a network entity or transceiver supporting lower frequency band communications of the Pcell / primary cell. In some aspects, a network entity or transceiver supporting sub-THz communications may be within the coverage of a network entity or transceiver supporting lower frequency band communications of a Pcell / primary cell to allow a sub-THz qualified UE to be continuously connected to the Pcell as a condition for sub-THz link establishment (e.g., and continuously connected to the Pcell even when it is using sub-THz communications for data offload). As used herein, the term "network entity" may refer to a network supported by a transceiver, an IAB, a gNB, a smart repeater, a radio remote head (RRH), etc. In some aspects, a sub-THz transceiver may be connected to a PCell network entity or base station via a wired or wireless connection, such as optical fiber (digital or analog), Ethernet, coaxial cable, an IAB link over sub-THz, etc.

[0080] As used herein, the term "repeater" may refer to a network-controlled repeater that can receive a transmission and perform network-controlled amplification and forwarding (AF) to send the transmission to a UE, a network entity, or another repeater (e.g., it can be an access point (AP) for direct connection with a UE, a rendezvous point (RP) for an intermediate or direct link with a network entity (such as a base station), or a hybrid that combines the functionality of an AP and a RP). As used herein, the term "sub-THz repeater" may refer to a repeater for amplifying and forwarding sub-THz transmissions (e.g., control information for the sub-THz repeater may be on a different frequency band).

[0081] For sub-THz, in order to achieve denser sub-THz coverage, a denser geographical distribution of sub-THz transceivers can be used. If each sub-THz coverage point is associated with a sub-THz network entity / IAB / small cell (with a direct link to a sub-THz-qualified UE), a full digital demodulation and decoding process of the sub-THz signal can be performed locally at each point before the integrated and remodulated data is transmitted back to the Pcell network entity. Considering that a large number of sub-THz transceivers may be used to cover the Pcell coverage area, the power consumption may be very large. Various aspects provided herein provide mechanisms for implementing multi-hop (e.g., implemented by multiple repeaters) sub-THz deployments to increase the supported point-based sub-THz coverage / coverage density while having less power consumption or energy investment, thereby allowing more power-efficient sub-THz deployments. To improve NW energy efficiency characteristics for sub-THz deployments, aspects provided herein enable extended-range multi-hop sub-THz links based on repeaters, which primarily employ analog sub-THz signal processing (AP / RP), thereby allowing for non-direct UE-to-sub-THz network entity connections instead of more power-hungry approaches based on multiple sub-THz small cells / IABs.

[0082] In some aspects, an extended range sub-THz link between a sub-THz eligible UE and a sub-THz network entity may be enabled by using one or more intermediate sub-THz repeaters. A multi-hop link based on the use of one or more intermediate sub-THz repeaters may achieve a range comparable to the Pcell coverage range in the entire Pcell coverage area (which may enable sub-THz to be deployed as an Scell ​​while Pcell connectivity exists), rather than being based on multiple sub-THz small cells / IABs, which may have higher power / energy consumption characteristics compared to repeaters that primarily employ analog processing. In some aspects, more than one sub-THz smart repeater may be used for long-range sub-THz link establishment. In some aspects, there may be line-of-sight (LOS) links between different involved sub-THz repeaters and between a sub-THz network entity and the nearest sub-THz repeater connected thereto. A NLOS link range for sub-THz may be used when there may be any penetration loss that may contribute to sub-THz link path loss due to the poor penetration characteristics of sub-THz.

[0083] As an example, repeaters may be classified into different types: AP, RP, or hybrid. An AP may be a repeater that provides a local sub-THz coverage point and has a direct link (service link) with a sub-THz qualified UE. An RP may be a repeater that serves as an intermediate repeater between other sub-THz smart repeaters or between another smart repeater and a sub-THz network entity. In some aspects, an RP may not provide a local sub-THz coverage point and may not have a direct link with a sub-THz UE, and may have a connection with other repeaters involved in a multi-hop link or a direct connection with a sub-THz network entity (donor link or intermediate backhaul link). A hybrid repeater may have the functionality of both an AP and an RP, and may simultaneously act as an intermediate repeater and provide a local sub-THz coverage point. In some aspects, different types of repeaters (RP / AP / hybrid) may follow the same link establishment and synchronization and beam management (BM) process, but may have different hardware and BM capabilities. For example, a repeater (AP / hybrid) that provides a local coverage point may support full / wide spatial coverage. The RP may support a relatively narrow spatial sector associated with a LOS link to other repeaters or network entities.

[0084] Figure 5 5 is a diagram illustrating different scenarios, such as example 500, example 510, example 520, example 530, example 540, and example 550 for sub-THz deployment. As illustrated in example 500, in some aspects, there may be one repeater in the link. For UEs with non-line-of-sight (NLOS) direct channels with sub-THz network entities, a single repeater may be used for the sub-THz link. For all components of the multi-hop sub-THz link, there may be Pcell connectivity (e.g., which may be on a frequency range different from sub-THz, such as FR2).

[0085] As illustrated in example 510, in some aspects, for a UE having a long range near line-of-sight (LOS) direct channel with a sub-THz network entity, two repeaters may be used for the sub-THz link. For all components of the multi-hop sub-THz link, there may be Pcell connectivity (e.g., which may be on a frequency range different from sub-THz, such as FR2 or FR1). As an example, a near-LOS link in FR2 may have a range approximately three times greater than a near-LOS link in FR5 or higher frequencies, so LOS connectivity over an extended range may be used for sub-THz to bridge the gap. Two or more sub-THz repeaters (including APs and RPs) may be used with LOS interconnection between them and LOS links to sub-THz network entities.

[0086] As illustrated in example 520, in some aspects, there may be no repeater and the UE may connect directly with the network entity over the sub-THz band. As illustrated in example 530, in some aspects, there may be a single repeater, which may be an AP. As illustrated in example 540, in some aspects, there may be two repeaters, which may be an AP and an RP. As illustrated in example 550, in some aspects, there may be two repeaters, which may be an AP and a hybrid repeater with AP and RP functionality (e.g., capable of connecting directly with both a network entity and a UE).

[0087] Figure 6 600 is a diagram illustrating an example communication between a network entity 602 and a UE 604 via one or more relays, such as an RP 606 and an AP 608. In some aspects, the network entity may be a base station that may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. The network entity may be implemented in a converged or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the RP 606 and the AP 608 may be relays. In some aspects, the RP 606 and the AP 608 may be other types of relays, such as a hybrid, etc.

[0088] like Figure 6 As illustrated, at 612, the network entity 602 may establish a Pcell connection and maintenance for the UE 604. Meanwhile, at 614A, the UE 604 may connect to the Pcell, which may have a lower frequency range than sub-THz communications. The UE 604 may continue to be connected to the Pcell.

[0089] The network entity 602 may send one or more RRC configurations, synchronization RSs, and control information for the Pcell link 616 to the UE 604, the RP 606, and the AP 608 through the Pcell link. Based on the one or more RRC configurations, synchronization RSs, and control information for the Pcell link 616, the RP 606 may be registered and connected through the Pcell. Based on the one or more RRC configurations, synchronization RSs, and control information for the Pcell link 616, the AP 608 may also be registered and connected through the Pcell.

[0090] The UE 604 may send a UE capability indication 618 to the network entity via a Pcell link, which may indicate a capability for sub-THz communication capability. Based on the capability for sub-THz communication capability, the network entity 602 may configure (e.g., at a later time) sub-THz communication for the UE 604. As used herein, the term "UE capability indication" may refer to a message indicating one or more capabilities associated with a UE. The AP 608 may send a repeater capability indication 615 to the network entity 602 via a Pcell link, and the RP 606 may send a repeater capability indication 617 to the network entity 602 via a Pcell link. The repeater capability indication 615 and the repeater capability indication 617 may indicate the capability to act as a repeater for sub-THz communication.

[0091] In some aspects, at a later time based on one or more conditions (e.g., when the UE 604 may have high data traffic and may be within coverage of a sub-THz NW entity transceiver, a sub-THz gNB, or a sub-THz AP (such as AP 608)), the network entity 602 may activate sub-THz communication for the UE 604 at 622 by sending an activation 626 for sub-THz operation to the UE 604, the AP 608, and the RP 606 on the Pcell.

[0092] In some aspects, one or more conditions may include that the UE 604 is within the coverage of the sub-THz transceiver / network entity / small cell / IAB / smart repeater. In some aspects, the network entity 602 may determine that the UE 604 is within the coverage of the sub-THz transceiver / network entity / small cell / IAB / smart repeater based on the UE location information, the sub-THz transceiver coverage area / range information, the range information associated with the RP 606 and the AP 608, and the repeater capability indication 615 and the repeater capability indication 617. In some aspects, the UE location information may be provided to / obtained by the network entity 602 based on Pcell connectivity, which is based on: (1) GPS information from the UE 604 reported or indicated by the Pcell to the network entity 602, or (2) UE location determined based on a positioning process employed based on the Pcell connectivity.

[0093] In some aspects, one or more conditions may include that the UE 604 may have a mobility less than a threshold. In some aspects, the mobility of the UE 604 may be determined based on Doppler measurements or reports from the UE 604 (based on Pcell connectivity), based on speed / mobility range information of the UE 604 indicated by the UE 604 via the Pcell, or may be based on UE location tracking based on Pcell positioning or UE GPS information reporting by the UE 604.

[0094] In some aspects, one or more conditions may include that the UE 604 has sub-THz capabilities (e.g., based on capabilities for sub-THz communication capabilities in the UE capability indication 618). In some aspects, one or more conditions may include that the UE 604 has sufficient battery resources (which may be indicated by the UE 604 on the Pcell). In some aspects, one or more conditions may include that the UE 604 has a data volume potential or usage above a threshold. The data volume potential or usage of the UE 604 may be estimated based on the UE Pcell link capacity / data volume, specific application activations, UE type, and related service or data scheduling requests / reservations for the UE in the DL or UL direction. In some aspects, UE location information, UE speed / mobility range, and battery resource information may be indicated by the UE 604 via Layer 3 (L3) signaling (e.g., as part of a UE Assistance Information (UAI) message).

[0095] Upon receiving the activation 626, at 624, the UE 604 may obtain activation for sub-THz communication on the Scell ​​for data offloading via sub-THz. In some aspects, the sub-THz communication may carry one or more of the following transmissions (e.g., no other transmissions): (1) PDSCH / PUSCH data, (2) LA resources for a PDSCH / PUSCH link adaptation (LA) process directly on the sub-THz link (e.g., a LA for at least one of a rank indicator (RI) based on CSI-RS or SRS, a precoding matrix indicator (PMI), a modulation and coding scheme (MCS), or a channel quality indicator (CQI)), and (3) sub-THz local synchronization and beam management related RS transmissions to support complementary sub-THz synchronization and BM sessions.

[0096] At 632A, 632B, and 632C, the network entity 602 may perform sub-THz synchronization and BM sessions (e.g., activated per sub-THz link / Scell ​​or based on a semi-periodic or scheduled session along a long-duration active sub-THz link or session) for the UE 604, the RP 606, and the AP 608. In some aspects, coarse synchronization and beam / beam direction determination for sub-THz may be based on Pcell connectivity. Complementary time synchronization / refinement and sub-THz beam refinement / reduced range beam search (e.g., including automatic gain control) processes and related RS transmissions may be supported via sub-THz local support on the Scell. In some aspects, sub-THz local synchronization and beam management related RS transmissions may include non-periodic SSB mini-bursts or dedicated synchronization and BM RS scheduling. In some aspects, customized SSB mini-bursts / synchronization and BM RS configurations for the RP 606 may be sent via the Pcell. One or more non-periodic customized SSB / synchronization and BM RSs may be sent via a sub-THz connection on the Scell. In some aspects, the local synchronization and beam management session may be based on a customized per-transmission / UE / RP / AP dedicated RS (e.g., one or more aperiodic customized SSB mini-burst / sync and BM RS transmitted via a sub-THz connection on the Scell). In some aspects, upon receiving one or more aperiodic customized SSB mini-burst / sync and BM RS transmissions from the gNB, the RP 606 may perform sub-THz complementary time synchronization and BM at 634. The dedicated RS may not be based on an SSB waveform. The SSB mini-burst may be an SSB waveform (e.g., modified compared to a non-sub-THz SSB waveform). In some aspects, upon receiving one or more aperiodic customized SSB / sync and BM RS, the RP 606 may send a synchronization (which may also be referred to as a "sync") report and a successful time synchronization and beam refinement confirmation (ACK) to the network entity 602. The ACK may be a "sync" ACK associated with a flag indicating the synchronization status of the RP side of the sub-THz link. The synchronization report and ACK may be sent over the Pcell. Similarly, in some aspects, a customized SSB mini-burst / sync and BM RS configuration to the AP 608 may be sent via the Pcell. One or more aperiodic customized SSB mini-burst / sync and BM RS may be sent by the RP 606 via the sub-THz connection on the Scell ​​in the next step to synchronize the next repeater (e.g., AP) of the multi-hop link being established / activated. In some aspects, the local synchronization and beam management session may be based on a customized per-transmit / per-hop dedicated RS (e.g., one or more aperiodic customized SSB mini-burst / sync and BM RS sent via the sub-THz connection on the Scell).In some aspects, upon receiving one or more aperiodic custom SSB mini-bursts / sync and BM RS sent by the RP, the AP 608 may perform sub-THz complementary time synchronization and BM at 634. In some aspects, upon receiving one or more aperiodic custom SSB / sync and BM RS, the AP 608 may send a synchronization (which may also be referred to as "sync") report and a successful time synchronization and beam refinement confirmation (ACK) to the network entity 602. The ACK may be a "sync" ACK associated with a flag indicating the synchronization status on the AP side of the sub-THz link. The synchronization report and ACK may be sent via the Pcell.

[0097] In some aspects, a customized SSB / sync and BM RS configuration 635 for the UE 604 may be sent via the Pcell. One or more aperiodic customized SSB mini-bursts / sync and BM RS 636 may be sent via a sub-THz connection on the Scell. In some aspects, a local synchronization and beam management session may be based on a customized per-transmission / hop dedicated RS (e.g., one or more aperiodic customized SSB mini-bursts / sync and BM RS sent via a sub-THz connection on the Scell / sub-THz link hop). In some aspects, upon receiving one or more aperiodic customized SSB / sync and BM RS 636, the UE 604 may perform sub-THz complementary time synchronization and BM at 634. In some aspects, upon receiving one or more aperiodic customized SSB mini-bursts / sync and BM RS 636, the AP 604 may send a BM report and a successful time synchronization and beam refinement confirmation (ACK) 637 to the network entity 602. The ACK may be a "sync" ACK associated with a flag indicating the synchronization status on the UE side of the sub-THz link. The BM report and ACK 637 may be sent on the Pcell.

[0098] In other words, the synchronization process may be a progressive synchronization across hops. At the first step, the hop closest to the network entity (e.g., RP 606) may be fully synchronized with the network entity 602 in terms of: RP local timing synchronization on sub-THz / Scell, RP UL timing synchronization on sub-THz / Scell ​​(for timing advance (TA) of the network entity), frequency synchronization on sub-THz / Scell ​​(derived based on Pcell), sub-THz refined beams including Tx beam and Rx beam (RP) pairs of the hop. Then, the relay closest to the network entity (e.g., RP 606) may become a reference point for timing synchronization of the next hop (e.g., AP 608) (which may perform local synchronization RS transmission aligned with its local Rx timing synchronization for the network entity / previous Tx node). At the next step, the next hop in the DL direction (between RP 606 and AP 608, or AP 608) can fully synchronize its receiving edge / node (e.g., AP 608) with its transmitting edge / node (e.g., RP 606) in terms of: its local timing synchronization on sub-THz / Scell, UL timing synchronization on sub-THz / Scell ​​(TA for the transmitting node / RP of this hop in the DL direction), frequency synchronization on sub-THz / Scell ​​(derived based on Pcell), sub-THz refined beams including Tx beam (for RP 606) and Rx beam (AP) pairs for this hop. Once this step is completed, the receiving node (e.g., AP 608) of this hop can become the reference point for timing synchronization of the next hop (between AP and sub-THz compliant UEs (such as UE 604)). Accordingly, once synchronized, it may perform local synchronized RS transmissions that are aligned with its local Rx timing synchronization for the previous Tx node (e.g., RP 606). The same synchronization steps may be performed for the last sub-THz link hop between the AP and the sub-THz eligible UE so that the UE may be fully synchronized with the AP 608. Thus, at the end of the synchronization process, each component / node of the multi-hop link may be synchronized on its local Rx timing for sub-THz / Scell ​​transmissions between the network entity 602 and the UE 604 (on the multi-hop link), and frequency coherent on the sub-THz / Scell, and may know the selected Tx and Rx beam pairs for each hop. In some aspects, hop-specific synchronization and BM sessions may be based on and customized as desired and per-session locally synchronized RS / SSB mini-burst transmissions that may be scheduled by the network entity for sub-THz and for different nodes on the Pcell link (e.g., for a sub-THz network controlled repeater with OOB control on the Pcell). Local SSB / synchronous RS Tx / Rx capabilities may be present on each node (eg, RP 606, AP 608, and UE 604).In some aspects, the configuration of hop-specific synchronization and BM sessions for corresponding Tx and Rx sides / nodes may be provided by the network entity 602 through the Pcell. There may be no dependency / association between the synchronization RS / SSB mini-bursts sent on different hops, but there may be a sequential order. At the end of each hop synchronization and BM session, the receiving side of each hop will provide synchronization-related reports (e.g., BM reports and "sync" ACK flag) to the network entity through the Pcell. In some aspects, all multi-hop link establishment processes including progressive synchronization across hops are completely controlled by the Pcell network entity (e.g., network entity 602). From the UE's perspective, all involved relays can be completely transparent.

[0099] At 642, a sub-THz LA (e.g., DL or UL) for the UE 604 may be performed by the network entity 602. The network entity 602 may send one or more LA RSs via the RP 606 and the AP 608 on the Pcell and a corresponding report schedule 645 for the UE 604. The UE 604 may communicate one or more Scell ​​sub-THz LA RSs 646 with the network entity 602 based on the sub-THz communication and the Scell. At 644, based on the communicated Scell ​​sub-THz LA RSs 646, the UE 604 may perform a channel state feedback (CSF) report evaluation. In some aspects, an alternative may be an SRS transmission by the UE to the gNB via the AP and the RP on the sub-THz link. The UE 604 may send an associated CSF report 647 based on the Pcell. In some aspects, an amplification and forwarding configuration for forwarding sub-THz communications may be provided by the network entity 602 to the RP 606 and the AP 608.

[0100] In some aspects, one or more procedures may not be supported on sub-THz communications on Scell. For example, in some aspects, RACH procedures and initial acquisition may not be supported on sub-THz communications through Scell ​​(the Scell ​​connection establishment process is fully controlled and initiated by the network entity, and DL and UL complementary time synchronization and beam refinement for sub-THz can be completed based on UE, RP, AP Rx configuration, scheduling (through Pcell) and corresponding transmission by NW, RP, AP on sub-THz synchronization and BM sessions for each hop (repeater or UE) in a progressive manner). In some aspects, there may be no "always on" transmission on sub-THz (e.g., SSB). In some aspects, sub-THz UEs can be continuously connected on Pcell, and Scell / sub-THz links can be activated through sessions. Such sessions can use complementary synchronization and beam refinement sessions for each activation (or for each certain duration of a long-lasting active sub-THz link / data offload session). In some aspects, the sub-THz / Scell ​​control plane (e.g., UE RRC connection / registration, sub-THz offload activation / deactivation, scheduling of BM / sync RS / LA RS, DL / UL scheduling, all sub-THz related feedback / reporting) may be sent on the Pcell instead of the Scell. In some aspects, the beam failure detection (BFD) and radio link failure (RLF) procedures for sub-THz / Scell ​​may be replaced by a "sync" flag reported on the Pcell as a response to each sub-THz synchronization and BM session. If the "sync" flag is not set (e.g., in the BM report and ACK 637), the sub-THz synchronization and BM session may be rescheduled by the network entity 602 and relayed with a modified configuration (beam list, timing uncertainty bounds, power level, etc.). Correspondingly, in some aspects, there may be no other beam failure recovery (BFR) procedures for sub-THz communications (because the Pcell connectivity is preserved, the synchronization and beam refinement sessions for sub-THz may be triggered / rescheduled by the gNB on the Pcell). There may be sub-THz BM reports (e.g., 637) for sub-THz beams measured multiple times during the synchronization and BM session sent from the UE 604 or RP / AP on the Pcell to the network entity 602. In some aspects, the relayed / additional synchronization session may be scheduled as a response to the "sync" flag not being set or based on another event.

[0101] In some aspects, Scell ​​activation or dedicated customized synchronization and beam management session scheduling on the sub-THz transceiver side (for transmission) to support Scell ​​activation and sub-THz link establishment / synchronization session for a specific sub-THz qualified UE (e.g., UE 604) may be controlled by a Pcell supporting entity (e.g., Pcell gNB). The corresponding sub-THz transceiver / gNB / small cell / IAB / smart repeater to be used for sub-THz link establishment for a specific sub-THz qualified UE (e.g., UE 604) may be determined based on UE location information (associated with UE eligibility criteria (e.g., one or more conditions) for dynamic Scell / sub-THz session activation).

[0102] At 652, the network entity 602 may perform PDSCH or PUSCH data transmission or reception and sub-THz communication on the Scell. Correspondingly, at 654, the UE 604 may perform PDSCH or PUSCH data transmission or reception and sub-THz communication on the Scell. The network entity 602 may send scheduling information 656 for PDSCH or PUSCH data transmission on the Pcell. PDSCH or PUSCH data 657 may be sent or received through the Scell ​​and based on sub-THz communication via the RP 606 and the AP 608. The UE 604 may perform associated ACK or NACK reporting 658 based on Pcell connectivity. As used herein, the term "scheduling information" may be used to refer to information about scheduled time and frequency resources for PDSCH or PUSCH, which may be carried by the PDCCH.

[0103] At 662, the network entity 602 may terminate the sub-THz communication session and deactivate the Scell ​​by sending a deactivation 666 to the UE 604, the AP 608, and the RP 606. Based on the deactivation 666, at 664, the UE 604 may terminate the sub-THz communication session and deactivate the Scell. The AP 608 and the RP 606 may also terminate the sub-THz communication session and deactivate the Scell ​​based on the deactivation 666.

[0104] In some aspects, the sub-THz / Scell ​​synchronization and beam management process may be based in part on the Pcell to allow dynamic Scell ​​activation / deactivation, each activation having low latency, low complexity, and low power penalty. In some aspects, there may be no frequency tracking loop or frequency synchronization for Scell ​​and sub-THz communications. In some aspects, the frequency tracking or frequency synchronization used for Pcell may be reused for Scell ​​and sub-THz communications. In some aspects, the Pcell time tracking loop (TTL) and Pcell timing may be used as coarse timing for Scell ​​and sub-THz communications. In some aspects, independent TTL may not be used on Scell ​​and sub-THz communications, and there may be complementary fine timing estimates to derive relative sub-THz link / Scell ​​timing offsets for Pcell timing. In some aspects, the coarse beam / beam direction for sub-THz / Scell ​​may be determined based on Pcell beam association or based on primary cell link channel and pre-coding information. Correspondingly, a reduced candidate beam list size and a reduced time uncertainty range for complementary synchronization sessions (where the session start time and duration can be indicated as referring to Pcell timing) can be addressed for each Scell / sub-THz link activation (e.g., reduced range time search / refinement and beam refinement for sub-THz instead of a full range beam and time search as in the conventional initial acquisition process).

[0105] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 602, network entity 1102).

[0106] At 710, the network entity may establish a first communication with the UE and at least one sub-THz repeater on the primary cell. For example, the network entity 602 may establish a first communication with the UE 604 and at least one sub-THz repeater (e.g., RP 606 and AP 608) on the primary cell. In some aspects, 710 may be performed by the communication component 199.

[0107] At 720, the network entity may receive a UE capability indication from a UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication excluding a second frequency, the second frequency being lower than the first frequency range. For example, the network entity 602 may receive a UE capability indication (e.g., 618) from a UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication excluding a second frequency, the second frequency being lower than the first frequency range. In some aspects, 720 may be performed by the communication component 199.

[0108] At 730, the network entity may send activation for sub-THz communication for the UE. For example, the network entity 602 may send activation for sub-THz communication for the UE (eg, 626). In some aspects, 730 may be performed by the communication component 199.

[0109] At 740, the network entity may transmit activation for sub-THz communication for each of the at least one sub-THz repeater. For example, the network entity 602 may transmit activation for sub-THz communication (e.g., 626) for each of the at least one sub-THz repeater (e.g., RP 606 and RP 608). In some aspects, 740 may be performed by the communication component 199.

[0110] At 750, the network entity may communicate scheduling information for at least one data channel transmission via the primary cell. For example, the network entity 602 may communicate scheduling information for at least one data channel transmission via the primary cell (e.g., 656). In some aspects, 750 may be performed by the communication component 199. In some aspects, the scheduling information may be provided for synchronization and beam management sessions at sub-THz per hop or node (e.g., UE or repeater), and also for link adaptation sessions (end-to-end). After the synchronization and beam management session and link adaptation, there may be scheduling for PDSCH or PUSCH transmission at sub-THz. PDSCH / PUSCH Tx at sub-THz may also use scheduling or configuration for repeaters (beam information, power information, etc. (depending on the allocated bandwidth), scheduling resources in time (when to apply analog forwarding and in which direction DL / UL, etc.).

[0111] At 760, the network entity may transmit at least one data channel via at least one sub-THz repeater and the sub-THz communication communication. For example, the network entity 602 may transmit at least one data channel via at least one sub-THz repeater (e.g., RP 606 and AP 608) and the sub-THz communication communication (e.g., 657). In some aspects, 760 may be performed by the communication component 199.

[0112] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 602, network entity 1102).

[0113] At 810, the network entity may establish a first communication with the UE and at least one sub-THz repeater on the primary cell. For example, the network entity 602 may establish a first communication with the UE 604 and at least one sub-THz repeater (e.g., RP 606 and AP 608) on the primary cell. In some aspects, 810 may be performed by the communication component 199.

[0114] At 812, the network entity may communicate control information, control information associated with the primary cell, with at least one repeater on the primary cell. For example, the network entity 602 may communicate control information associated with the primary cell with a first sub-THz repeater (e.g., RP 606). In some aspects, 812 may be performed by the communication component 199. In some aspects, the control information includes at least one of the following: capability information of a sub-THz frequency band for at least one sub-THz repeater, a radio resource control (RRC) configuration for at least one sub-THz repeater based on corresponding capability information for relay operation on sub-THz, repeater location information associated with at least one sub-THz repeater, or activation for sub-THz communication or deactivation for sub-THz communication for at least one sub-THz repeater. In some aspects, the network entity may communicate at least one sub-THz local synchronization and beam management RS via a secondary cell associated with sub-THz communication. In some aspects, at least one sub-THz local synchronization and beam management RS includes a hop-specific non-periodic synchronization signal block (SSB) mini-burst based on a dedicated configuration of each of at least one sub-THz repeater. In some aspects, a sequence of hop-specific SSB / beams may be sent back (e.g., Tx beam scanning). The sequence may be repeated several times with a certain time gap between each repetition of the sequence (to allow Rx beam scanning across repetitions on the Rx side node, which may be a repeater or a UE). The sequence of hop-specific SSB / beams may be configured and scheduled for both the Tx side node and the Rx side node of the addressed hop, and the configuration may be hop-specific and may be provided by a network entity on the Pcell (synchronization and BM RS Tx / Rx may be on sub-THz). The term "hop" may be used to refer to a repeater or a UE.

[0115] At 820, the network entity may receive a UE capability indication from a UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication excluding a second frequency, the second frequency being lower than the first frequency range. For example, the network entity 602 may receive a UE capability indication (e.g., 618) from a UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication excluding a second frequency, the second frequency being lower than the first frequency range. In some aspects, 820 may be performed by the communication component 199.

[0116] At 830, the network entity may send activation for sub-THz communication for the UE. For example, the network entity 602 may send activation for sub-THz communication for the UE (eg, 626). In some aspects, 830 may be performed by the communication component 199.

[0117] At 840, the network entity may transmit activation for sub-THz communication for each of the at least one sub-THz repeater. For example, the network entity 602 may transmit activation for sub-THz communication (e.g., 626) for each of the at least one sub-THz repeater (e.g., RP 606 and RP 608). In some aspects, 840 may be performed by the communication component 199.

[0118] At 842, the network entity may synchronize with the first sub-THz repeater based on the first sub-THz local synchronization and beam management RS transmission session. For example, the network entity 602 may synchronize with the first sub-THz repeater (e.g., RP 606) based on the first sub-THz local synchronization and beam management RS transmission session. In some aspects, 842 may be performed by the communication component 199.

[0119] At 844, the network entity may configure a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater and the second sub-THz repeater based on the synchronization of the first sub-THz repeater as a first step. For example, the network entity 602 configures a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater (e.g., RP 606) and the second sub-THz repeater (e.g., AP 608) based on the synchronization of the first sub-THz repeater as a first step. In some aspects, 844 may be performed by the communication component 199. In some aspects, the synchronization includes one or more of: local timing synchronization for sub-THz communication, uplink timing synchronization for sub-THz communication, time synchronization or refinement for sub-THz communication, or refined beam pair synchronization for sub-THz communication. In some aspects, synchronization associated with at least one sub-THz repeater and the UE includes one or more of: time synchronization or refinement for sub-THz communications, or refined beam pair determination for sub-THz communications.

[0120] In some aspects, the control information includes at least one of: a dynamic time slot format or time domain duplex mode for the first sub-THz repeater or the second repeater, amplification and forwarding (AF) direction information for the first sub-THz repeater or the second repeater, AF gain or power control information for the first sub-THz repeater or the second repeater, or at least one carrier frequency configuration. In some aspects, the second sub-THz repeater is selected based on at least one of: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, repeater capability associated with the second sub-THz repeater, repeater coverage associated with the first sub-THz repeater, transmit power associated with the second sub-THz repeater, or repeater type associated with the second sub-THz repeater.

[0121] At 850, the network entity may communicate scheduling information for at least one data channel transmission via the primary cell. For example, the network entity 602 may communicate scheduling information (e.g., 656) for at least one data channel transmission via the primary cell. In some aspects, 850 may be performed by the communication component 199. In some aspects, the scheduling information for at least one data channel transmission is communicated via at least one of the following: a physical downlink control channel (PDCCH). In some aspects, sub-THz communication does not include control channel communication, always-on synchronization signal blocks, beam failure recovery procedures, beam failure detection procedures, radio link failure procedures, full-range initial acquisition, or random access procedures. In some aspects, scheduling information may be provided for synchronization and BM sessions on sub-THz per hop or node (e.g., a repeater or UE) and also for link adaptation sessions (end-to-end), and after synchronization, there may be scheduling for PDSCH or PUSCH transmission on sub-THz. PDSCH / PUSCH transmission on sub-THz may also use scheduling / configuration for repeaters (beam information, power information (depending on the allocated bandwidth), scheduling resources in time (when to apply simulated forwarding and in which direction DL / UL, etc.). In some aspects, scheduling information may be provided for synchronization and beam management sessions on sub-THz per hop or node (e.g., UE or repeater), and also for link adaptation sessions (end-to-end). After the synchronization and beam management session and link adaptation, there may be scheduling for PDSCH or PUSCH transmission on sub-THz. PDSCH / PUSCH Tx on sub-THz may also use scheduling or configuration for repeaters (beam information, power information, etc. (depending on the allocated bandwidth), scheduling resources in time (when to apply simulated forwarding and in which direction DL / UL, etc.).

[0122] At 860, the network entity may communicate at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. For example, the network entity 602 may communicate at least one data channel transmission (e.g., 657) via at least one sub-THz repeater (e.g., RP 606 and AP 608) and sub-THz communication. In some aspects, 860 may be performed by the communication component 199. In some aspects, the at least one data channel transmission includes at least one of: a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH).

[0123] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a repeater (eg, RP 606, AP 608, network entity 1260).

[0124] At 910, the first wireless device may establish a first communication with a network entity on a primary cell. For example, the RP 606 or the AP 608 may establish a first communication with the network entity 602 on the primary cell. In some aspects, 910 may be performed by the communication component 199.

[0125] At 920, the first wireless device may receive from the network entity an activation for sub-THz relay operation for the wireless device, the sub-THz relay operation being at a first frequency range of the first communication that does not include the second frequency. For example, the RP 606 or the AP 608 may receive from the network entity an activation (e.g., 626) for sub-THz communication for the RP 606 or the AP 608, the sub-THz communication being at a first frequency range of the first communication that does not include the second frequency. In some aspects, 920 may be performed by the communication component 199.

[0126] At 930, the first wireless device may communicate (e.g., amplify and forward) at least one data channel transmission with the UE and the network entity via sub-THz communication (e.g., as part of a sub-THz relay operation). For example, the RP 606 or the AP 608 may communicate at least one data channel transmission (e.g., 657) with the UE and the network entity via sub-THz communication. In some aspects, 930 may be performed by the communication component 199.

[0127] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a first wireless device (eg, RP 606, AP 608, network entity 1260).

[0128] At 1010, the first wireless device may establish a first communication with a network entity on a primary cell. For example, the RP 606 or the AP 608 may establish a first communication with the network entity 602 on the primary cell. In some aspects, 1010 may be performed by the communication component 199.

[0129] At 1012, the first wireless device may communicate control information associated with the primary cell with the network entity. For example, the RP 606 or the AP 608 may communicate control information associated with the primary cell with the network entity 602 (e.g., 616). In some aspects, 1012 may be performed by the communication component 199. In some aspects, the first wireless device is a second sub-THz repeater, and wherein the control information includes at least one of: an RRC configuration associated with a repeater capability of the second sub-THz repeater, a repeater location information associated with the second sub-THz repeater, or activation for sub-THz communication or deactivation for sub-THz communication. In some aspects, the first wireless device may communicate (e.g., receive or send) at least one sub-THz local synchronization and beam management RS. In some aspects, the at least one sub-THz local synchronization and beam management RS includes a hop-specific non-periodic synchronization signal block (SSB) mini-burst based on a dedicated configuration of each of the at least one sub-THz repeater.

[0130] At 1020, the first wireless device may receive from the network entity activation for sub-THz communication for the UE, the sub-THz communication being on a first frequency range of the first communication that does not include the second frequency. For example, the RP 606 may receive from the network entity activation (e.g., 626) for sub-THz communication for the UE, the sub-THz communication being on a first frequency range of the first communication that does not include the second frequency. In some aspects, 1010 may be performed by the communication component 199.

[0131] At 1022, the first wireless device may communicate control information associated with the primary cell with a second sub-THz repeater, wherein the second sub-THz repeater is connected to the first sub-THz repeater, and wherein the first sub-THz repeater is connected to the UE via the second sub-THz repeater. For example, the RP 606 may communicate control information associated with the primary cell with a second sub-THz repeater (e.g., the AP 608), wherein the second sub-THz repeater is connected to the first sub-THz repeater, and wherein the first sub-THz repeater is connected to the UE via the second sub-THz repeater. In some aspects, 1022 may be performed by the communication component 199.

[0132] At 1024, the first wireless device may synchronize with the network entity based on at least one sub-THz local synchronization and beam management RS sent from the network entity in sub-THz. For example, RP 606 may synchronize with network entity 602 based on at least one sub-THz local synchronization and beam management RS sent from the network entity in sub-THz. In some aspects, 1024 may be performed by communication component 199.

[0133] At 1026, the first wireless device may synchronize with the second sub-THz repeater based on at least one other sub-THz local synchronization and beam management RS transmission to the second sub-THz repeater on sub-THz, further based on the sub-THz local synchronization of the network entity as a first step. For example, RP 606 may synchronize with the second sub-THz repeater (e.g., AP 608) based on at least one sub-THz local synchronization and beam management RS, further based on the synchronization of the network entity as a first step. In some aspects, 1026 may be performed by communication component 199.

[0134] In some aspects, synchronization includes one or more of: local timing synchronization for sub-THz communication, uplink timing synchronization for sub-THz communication, time synchronization or refinement for sub-THz communication, or refined beam pair synchronization for sub-THz communication. In some aspects, control information includes at least one of: a dynamic slot format or time domain duplex mode for the first wireless device, amplification and forwarding (AF) direction information for the first wireless device, AF gain or power control information for the first wireless device, or at least one carrier frequency configuration. In some aspects, the first wireless device is a second sub-THz repeater, and wherein the second sub-THz repeater is selected based on at least one of: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, repeater capability associated with the second sub-THz repeater, repeater coverage associated with the first sub-THz repeater, transmit power associated with the second sub-THz repeater, or repeater type associated with the second sub-THz repeater.

[0135] At 1030, the first wireless device may communicate at least one data channel transmission with the UE and the network entity via sub-THz communication. For example, the RP 606 may communicate at least one data channel transmission (e.g., 657) with the UE and the network entity via sub-THz communication. In some aspects, 1010 may be performed by the communication component 199. In some aspects, at least one data channel transmission includes at least one of the following: a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission. In some aspects, at least one data channel transmission may include a link adaptation (LA) reference signal (RS), or a hop-specific synchronization and beam management reference signal (RS). In some aspects, scheduling information for at least one data channel transmission is communicated via a physical downlink control channel (PDCCH) of a primary cell. In some aspects, sub-THz communication does not include control channel communication. In some aspects, scheduling information may be provided for synchronization and beam management sessions on sub-THz per hop or node (e.g., UE or repeater), and also for link adaptation sessions (end-to-end). After synchronization and beam management session and link adaptation, there may be scheduling for PDSCH or PUSCH transmission on sub-THz. PDSCH / PUSCHTx on sub-THz may also use scheduling or configuration for repeaters (beam information, power information, etc. (depending on the allocated bandwidth), scheduling resources in time (when to apply analog forwarding and in which direction DL / UL, etc.).

[0136] Fig.111100 is a diagram illustrating one example of a hardware implementation for a network entity 1102. The network entity 1102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1102 may include at least one of a CU 1110, a DU 1130, or a RU 1140. For example, depending on the layer functionality handled by the component 199, the network entity 1102 may include a CU 1110; both a CU 1110 and a DU 1130; each of the CU 1110, the DU 1130, and the RU 1140; the DU 1130; both a DU 1130 and a RU 1140; or a RU 1140. The CU 1110 may include a CU processor 1112. The CU processor 1112 may include an on-chip memory 1112'. In some aspects, the CU 1110 may also include an additional memory module 1114 and a communication interface 1118. CU 1110 communicates with DU 1130 via a midhaul link, such as an F1 interface. DU 1130 may include a DU processor 1132. DU processor 1132 may include on-chip memory 1132'. In some aspects, DU 1130 may also include an additional memory module 1134 and a communication interface 1138. DU 1130 communicates with RU 1140 via a fronthaul link. RU 1140 may include a RU processor 1142. RU processor 1142 may include on-chip memory 1142'. In some aspects, RU 1140 may also include an additional memory module 1144, one or more transceivers 1146, an antenna 1180, and a communication interface 1148. RU 1140 communicates with UE 104. On-chip memory 1112', 1132', 1142' and additional memory modules 1114, 1134, 1144 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1112, 1132, 1142 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0137] As discussed herein, the communication component 199 may be configured to establish a first communication with a user equipment (UE) and at least one sub-THz repeater on a primary cell. In some aspects, the communication component 199 may be configured to receive a UE capability indication from the UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with at least one sub-THz repeater, the sub-THz communication being in a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication to the UE. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication to each of the at least one sub-THz repeaters. In some aspects, the communication component 199 may be configured to communicate scheduling information for at least one data channel transmission via the primary cell. In some aspects, the communication component 199 may be configured to communicate at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. In some aspects, the communication component 199 may be configured to establish a first communication with a network entity on a primary cell. In some aspects, the communication component 199 may be configured to receive activation of a sub-THz relay operation for a wireless device from a network entity, the sub-THz relay operation being in a first frequency range of the first communication that does not include a second frequency. In some aspects, the communication component 199 may be configured to amplify and forward at least one data channel transmission as part of the sub-THz relay operation. The communication component 199 may be within one or more processors of one or more of the CU 1110, DU 1130, and RU 1140. The communication component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or a combination of these operations. The network entity 1102 may include a variety of components configured for various functions. In one configuration, the network entity 1102 includes a component for establishing a first communication with a UE and at least one sub-THz repeater on a primary cell. In some aspects, the network entity 1102 may also include a component for receiving a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range.In some aspects, the network entity 1102 may also include a component for sending activation for sub-THz communication for the UE. In some aspects, the network entity 1102 may also include a component for sending activation for sub-THz communication for each of at least one sub-THz repeater. In some aspects, the network entity 1102 may also include a component for communicating scheduling information for at least one data channel transmission via a primary cell. In some aspects, the network entity 1102 may also include a component for communicating at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. In some aspects, the network entity 1102 may also include a component for communicating control information associated with sub-THz communication and control information associated with the primary cell with at least one repeater on the primary cell. In some aspects, the network entity 1102 may also include a component for communicating at least one sub-THz local synchronization and beam management reference signal (RS) via a secondary cell associated with sub-THz communication, wherein the second sub-THz repeater is connected to the first sub-THz repeater, and wherein the first sub-THz repeater is connected to the UE via the second sub-THz repeater. In some aspects, the network entity 1102 may also include components for synchronizing the RS transmission session with the first sub-THz repeater based on the first sub-THz local synchronization and beam management. In some aspects, the network entity 1102 may also include components for configuring a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater and the second sub-THz repeater as a first step based on the synchronization of the first sub-THz repeater. These components may be the communication components 199 of the network entity 1102 configured to perform the functions recorded by the components. As described herein, the network entity 1102 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, these components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recorded by the components.

[0138] Fig.121200 is an example of a hardware implementation for a network entity 1260. In one example, the network entity 1260 may be within the core network 120. The network entity 1260 may include a network processor 1212. The network processor 1212 may include an on-chip memory 1212'. In some aspects, the network entity 1260 may also include an additional memory module 1214. The network entity 1260 communicates directly (e.g., a backhaul link) or indirectly (e.g., through a RIC) with the CU 1202 via a network interface 1280. The on-chip memory 1212' and the additional memory module 1214 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1212 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0139] As discussed herein, the communication component 199 may be configured to establish a first communication with a user equipment (UE) and at least one sub-THz repeater on a primary cell. In some aspects, the communication component 199 may be configured to receive a UE capability indication from the UE and at least one repeater capability indication from at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with at least one sub-THz repeater, the sub-THz communication being in a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication to the UE. In some aspects, the communication component 199 may be configured to send an activation for sub-THz communication to each of the at least one sub-THz repeaters. In some aspects, the communication component 199 may be configured to communicate scheduling information for at least one data channel transmission via the primary cell. In some aspects, the communication component 199 may be configured to communicate at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. In some aspects, the communication component 199 may be configured to establish a first communication with a network entity on a primary cell. In some aspects, the communication component 199 may be configured to receive activation of a sub-THz relay operation for a wireless device from a network entity, the sub-THz relay operation being in a first frequency range of the first communication that does not include a second frequency. In some aspects, the communication component 199 may be configured to amplify and forward at least one data channel transmission as part of the sub-THz relay operation. Component 199 may be within processor 1212. Component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. Network entity 1260 may include a variety of components configured for various functions. In one configuration, the network entity 1260 includes a component for establishing a first communication with a UE and at least one sub-THz repeater on a primary cell. In some aspects, the network entity 1260 may also include a component for receiving a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being at a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range. In some aspects, the network entity 1260 may also include a component for sending an activation for the sub-THz communication for the UE.In some aspects, the network entity 1260 may also include a component for sending activation for sub-THz communication for each of the at least one sub-THz repeater. In some aspects, the network entity 1260 may also include a component for communicating scheduling information for at least one data channel transmission via a primary cell. In some aspects, the network entity 1260 may also include a component for communicating at least one data channel transmission via at least one sub-THz repeater and sub-THz communication. In some aspects, the network entity 1260 may also include a component for communicating control information associated with sub-THz communication and control information associated with the primary cell with at least one repeater on the primary cell. In some aspects, the network entity 1260 may also include a component for communicating at least one sub-THz local synchronization and beam management reference signal (RS) via a secondary cell associated with sub-THz communication, wherein the second sub-THz repeater is connected to the first sub-THz repeater, and wherein the first sub-THz repeater is connected to the UE via the second sub-THz repeater. In some aspects, the network entity 1260 may further include means for synchronizing the RS transmission session with the first sub-THz repeater based on the first sub-THz local synchronization and beam management. In some aspects, the network entity 1260 may further include means for configuring a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater and the second sub-THz repeater as a first step based on the synchronization of the first sub-THz repeater. The means may be a component 199 of the network entity 1260 configured to perform the functions recited by the means.

[0140] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0141] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0142] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0143] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0144] Aspect 1 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to: establish a first communication with a user equipment (UE) and at least one sub-THz (THz) repeater on a primary cell; receive a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating a capability for sub-THz communication associated with the UE, the at least one repeater capability indication indicating at least one capability for the sub-THz communication associated with the at least one sub-THz repeater, the sub-THz communication being in a first frequency range of the first communication that does not include a second frequency, the second frequency being lower than the first frequency range; send activation for the sub-THz communication to the UE; send the activation for the sub-THz communication for each of the at least one sub-THz repeaters; communicate scheduling information for at least one data channel transmission via the primary cell; and communicate the at least one data channel transmission via the at least one sub-THz repeater and the sub-THz communication.

[0145] Aspect 2 is the apparatus of aspect 1, wherein the at least one processor is further configured to: communicate control information associated with the sub-THz communication with the at least one repeater over the primary cell.

[0146] Aspect 3 is an apparatus according to any one of Aspects 1 to 2, wherein the control information includes at least one of the following: capability information of a sub-THz frequency band for the at least one sub-THz repeater, a radio resource control (RRC) configuration for the at least one sub-THz repeater based on the corresponding capability information for the relay operation of the sub-THz communication on sub-THz, repeater location information associated with the at least one sub-THz repeater, or the activation of the sub-THz communication or the deactivation of the sub-THz communication for the at least one sub-THz repeater.

[0147] Aspect 4 is an apparatus according to any one of aspects 1 to 3, wherein the at least one processor is further configured to: communicate at least one sub-THz local synchronization and beam management reference signal (RS) via a secondary cell associated with the sub-THz communication.

[0148] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the at least one sub-THz local synchronization and beam management RS includes a non-periodic synchronization signal block (SSB) mini-burst based on a hop-specific non-periodic synchronization signal block (SSB) mini-burst based on a dedicated configuration of each of the at least one sub-THz repeaters.

[0149] Aspect 6 is an apparatus according to any one of aspects 1 to 5, wherein the at least one sub-THz repeater includes a first sub-THz repeater and a second sub-THz repeater, the first sub-THz repeater having a direct link with the network entity.

[0150] Aspect 7 is an apparatus according to any one of Aspects 1 to 6, wherein the at least one processor is further configured to: synchronize with the first sub-THz repeater based on a first sub-THz local synchronization and beam management RS transmission session; and based on the synchronization of the first sub-THz repeater as a first step, configure a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater and the second sub-THz repeater.

[0151] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the synchronization associated with the at least one sub-THz repeater and the UE includes one or more of the following: time synchronization or refinement for the sub-THz communication, or refined beam pair determination for the sub-THz communication.

[0152] Aspect 9 is an apparatus according to any one of Aspects 1 to 8, wherein the control information includes at least one of the following: a dynamic time slot format or time division duplex mode for the at least one sub-THz repeater, amplification and forwarding (AF) direction information for the at least one sub-THz repeater, AF gain or power control information for the at least one sub-THz repeater, or at least one carrier frequency configuration for the at least one repeater.

[0153] Aspect 10 is an apparatus according to any one of Aspects 1 to 9, wherein a second sub-THz repeater among the at least one repeater is selected based on at least one of the following: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, repeater capability associated with the second sub-THz repeater, repeater coverage associated with the second sub-THz repeater, transmission power associated with the second sub-THz repeater, or a repeater type associated with the second sub-THz repeater.

[0154] Aspect 11 is an apparatus according to any one of Aspects 1 to 10, wherein the at least one data channel transmission includes at least one of the following: a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission.

[0155] Aspect 12 is an apparatus according to any one of aspects 1 to 11, wherein the scheduling information for the at least one data channel transmission is conveyed via a physical downlink control channel (PDCCH) of the primary cell.

[0156] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the sub-THz communication does not include control channel communication, always-on synchronization signal blocks, beam fault recovery procedures, beam fault detection procedures, radio link failure procedures, full-range initial acquisition or random access procedures.

[0157] Aspect 14 is an apparatus for performing wireless communications at a first wireless device, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: establish a first communication with a network entity on a primary cell; receive activation of a sub-THz relay operation for the wireless device from the network entity, the sub-THz relay operation being in a first frequency range of the first communication that does not include a second frequency; and amplify and forward at least one data channel transmission as part of the sub-THz relay operation.

[0158] Aspect 15 is an apparatus according to aspect 14, wherein the at least one processor is further configured to communicate control information associated with the primary cell with the network entity.

[0159] Aspect 16 is an apparatus according to any one of aspects 14 to 15, wherein the first wireless device is a second sub-THz repeater, and wherein the control information includes at least one of the following: a radio resource control (RRC) configuration associated with a repeater capability of the second sub-THz repeater, repeater location information associated with the second sub-THz repeater, or activation of a sub-THz communication and an associated direct access link with a user equipment (UE) or deactivation of the sub-THz communication.

[0160] Aspect 17 is an apparatus according to any one of aspects 14 to 16, wherein the at least one processor is configured to communicate at least one sub-THz local synchronization and beam management reference signal (RS).

[0161] Aspect 18 is an apparatus according to any one of aspects 14 to 17, wherein the at least one sub-THz local synchronization and beam management RS comprises a non-periodic synchronization signal block (SSB) burst.

[0162] Aspect 19 is an apparatus according to any one of Aspects 14 to 18, wherein the first wireless device is a first sub-THz repeater, and wherein the at least one processor is further configured to: synchronize with the network entity based on at least one sub-THz local synchronization and beam management RS sent from the network entity on sub-THz; and synchronize with the second sub-THz repeater based on the sub-THz local synchronization of the network entity as a first step based on the at least one other sub-THz local synchronization and beam management RS sent to the second sub-THz repeater on sub-THz.

[0163] Aspect 20 is an apparatus according to any one of Aspects 14 to 19, wherein synchronization includes one or more of the following: local timing synchronization for the sub-THz communication, uplink timing synchronization for the sub-THz communication, time synchronization or refinement for the sub-THz communication, or refined beam pair synchronization for the sub-THz communication for a first sub-THz link between the first wireless device and the network entity, a second sub-THz link between the first wireless device and another sub-THz repeater, or a third sub-THz link between the first wireless device and a user equipment (UE).

[0164] Aspect 21 is an apparatus according to any one of Aspects 14 to 20, wherein the control information includes at least one of the following: a dynamic time slot format or time domain duplex mode for the first wireless device, amplification and forwarding (AF) direction information for the first wireless device, AF gain or power control information for the first wireless device, or at least one carrier frequency configuration.

[0165] Aspect 22 is an apparatus according to any one of Aspects 14 to 21, wherein the first wireless device is a second sub-THz repeater, and wherein the second sub-THz repeater is selected based on at least one of the following: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, repeater capability associated with the second sub-THz repeater, repeater coverage associated with the second sub-THz repeater, transmit power associated with the second sub-THz repeater, or repeater type associated with the second sub-THz repeater.

[0166] Aspect 23 is an apparatus according to any one of Aspects 14 to 22, wherein the at least one data channel transmission includes at least one of the following: a physical downlink shared channel (PDSCH) transmission, a link adaptation (LA) reference signal (RS), or a hop-specific synchronization and beam management reference signal (RS).

[0167] Aspect 24 is an apparatus according to any one of aspects 14 to 23, wherein scheduling information for the at least one data channel transmission is conveyed via a physical downlink control channel (PDCCH) of the primary cell.

[0168] Aspect 25 is an apparatus according to any one of Aspects 14 to 24, wherein the sub-THz communication does not include control channel communication, always-on synchronization signal blocks, beam fault recovery procedures, beam fault detection procedures, radio link failure procedures, full range initial acquisition or random access procedures.

[0169] Aspect 26 is an apparatus according to any one of aspects 14 to 25, wherein the first wireless device is a sub-THz repeater having a direct link to the network entity.

[0170] Aspect 27 is an apparatus according to any one of aspects 14 to 26, wherein the first wireless device is a sub-THz repeater with a direct link to a user equipment (UE).

[0171] Aspect 28 is an apparatus according to any one of aspects 14 to 27, wherein the first wireless device is a second sub-THz repeater having direct links to the first sub-THz repeater and the third sub-THz repeater.

[0172] Aspect 29 is a wireless communication method for implementing any one of aspects 1 to 13.

[0173] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 13.

[0174] Aspect 31 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 13.

[0175] Aspect 32 is a wireless communication method for implementing any one of aspects 14 to 28.

[0176] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 14 to 28.

[0177] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 14 to 28.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: establishing a first communication with a user equipment (UE) and at least one sub-terahertz (THz) repeater on a primary cell; receiving a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating capabilities for sub-THz communications associated with the UE, the at least one repeater capability indication indicating at least one capability for the sub-THz communications associated with the at least one sub-THz repeater, the sub-THz communications being at a first frequency range of the first communications that does not include a second frequency, the second frequency being lower than the first frequency range; sending, for the UE, an activation for the sub-THz communication; for each of the at least one sub-THz repeater, sending the activation for the sub-THz communication; communicating scheduling information for at least one data channel transmission via the primary cell; as well as The at least one data channel transmission is communicated via the at least one sub-THz repeater and the sub-THz communication.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: Control information associated with the sub-THz communication is communicated with the at least one repeater over the primary cell.

3. The apparatus according to claim 2, wherein the control information comprises at least one of the following: capability information of a sub-THz frequency band for the at least one sub-THz repeater, a radio resource control (RRC) configuration for the at least one sub-THz repeater based on the corresponding capability information of the relay operation of the sub-THz communication on sub-THz, repeater location information associated with the at least one sub-THz repeater, or the activation for the sub-THz communication or the deactivation for the sub-THz communication for the at least one sub-THz repeater.

4. The apparatus of claim 1 , wherein the at least one processor is further configured to: At least one sub-THz local synchronization and beam management reference signal (RS) is communicated via a secondary cell associated with the sub-THz communication.

5. The apparatus of claim 4, wherein the at least one sub-THz local synchronization and beam management RS comprises a hop-specific non-periodic synchronization signal block (SSB) mini-burst based on a dedicated configuration of each of the at least one sub-THz repeater. 6 . The apparatus of claim 1 , wherein the at least one sub-THz repeater comprises a first sub-THz repeater and a second sub-THz repeater, the first sub-THz repeater having a direct link with the network entity.

7. The apparatus of claim 6, wherein the at least one processor is further configured to: Synchronizing the RS transmission session with the first sub-THz repeater based on the first sub-THz local synchronization and beam management; and Based on the synchronization of the first sub-THz repeater as a first step, a second sub-THz local synchronization and beam management RS transmission session for synchronization between the first sub-THz repeater and the second sub-THz repeater is configured.

8. The apparatus of claim 7, wherein synchronization associated with the at least one sub-THz repeater and the UE comprises one or more of: time synchronization or refinement for the sub-THz communication, or refined beam pair determination for the sub-THz communication.

9. The apparatus of claim 2, wherein the control information comprises at least one of: a dynamic time slot format or time division duplex mode for the at least one sub-THz repeater, amplification and forwarding (AF) direction information for the at least one sub-THz repeater, AF gain or power control information for the at least one sub-THz repeater, or at least one carrier frequency configuration for the at least one repeater.

10. The apparatus of claim 1 , wherein a second sub-THz repeater among the at least one repeater is selected based on at least one of: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, a repeater capability associated with the second sub-THz repeater, a repeater coverage associated with the second sub-THz repeater, a transmit power associated with the second sub-THz repeater, or a repeater type associated with the second sub-THz repeater.

11. The apparatus of claim 1, wherein the at least one data channel transmission comprises at least one of: a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission.

12. The apparatus of claim 1, wherein the scheduling information for the at least one data channel transmission is conveyed via a physical downlink control channel (PDCCH) of the primary cell.

13. The apparatus of claim 1, wherein the sub-THz communication does not include control channel communication, always-on synchronization signal blocks, beam failure recovery procedures, beam failure detection procedures, radio link failure procedures, full range initial acquisition, or random access procedures.

14. An apparatus for wireless communication at a first wireless device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: Establishing a first communication with a network entity on a primary cell; receiving, from the network entity, activation for sub-THz relay operation for the wireless device over a first frequency range of the first communication that does not include a second frequency; and At least one data channel transmission is amplified and retransmitted as part of the sub-THz relay operation.

15. The apparatus of claim 14, wherein the at least one processor is further configured to: Control information associated with the primary cell is communicated with the network entity.

16. The apparatus of claim 15, wherein the first wireless device is a second sub-THz repeater, and wherein the control information comprises at least one of: a radio resource control (RRC) configuration associated with a repeater capability of the second sub-THz repeater, repeater location information associated with the second sub-THz repeater, or activation for sub-THz communication and an associated direct access link with a user equipment (UE) or deactivation for the sub-THz communication.

17. The apparatus of claim 14, wherein the at least one processor is configured to communicate at least one sub-THz local synchronization and beam management reference signal (RS).

18. The apparatus of claim 17, wherein the at least one sub-THz local synchronization and beam management RS comprises aperiodic synchronization signal block (SSB) bursts.

19. The apparatus of claim 14, wherein the first wireless device is a first sub-THz repeater, and wherein the at least one processor is further configured to: synchronizing with the network entity based on at least one sub-THz local synchronization and beam management RS transmitted from the network entity at sub-THz; and Based on at least one other sub-THz local synchronization and beam management RS transmission of the first sub-THz repeater to the second sub-THz repeater on sub-THz, further based on the sub-THz local synchronization of the network entity as a first step, synchronize with the second sub-THz repeater.

20. The apparatus of claim 14, wherein synchronization comprises one or more of: local timing synchronization for the sub-THz communication, uplink timing synchronization for the sub-THz communication, time synchronization or refinement for the sub-THz communication, or refined beam pair synchronization for the sub-THz communication for a first sub-THz link between the first wireless device and the network entity, a second sub-THz link between the first wireless device and another sub-THz repeater, or a third sub-THz link between the first wireless device and a user equipment (UE).

21. An apparatus according to claim 15, wherein the control information includes at least one of the following: a dynamic time slot format or time domain duplex mode for the first wireless device, amplification and forwarding (AF) direction information for the first wireless device, AF gain or power control information for the first wireless device, or at least one carrier frequency configuration.

22. The apparatus of claim 14, wherein the first wireless device is a second sub-THz repeater, and wherein the second sub-THz repeater is selected based on at least one of: UE location information associated with the UE, repeater location information associated with the second sub-THz repeater, a repeater capability associated with the second sub-THz repeater, a repeater coverage associated with the second sub-THz repeater, a transmit power associated with the second sub-THz repeater, or a repeater type associated with the second sub-THz repeater.

23. The apparatus of claim 14, wherein the at least one data channel transmission comprises at least one of: a physical downlink shared channel (PDSCH) transmission, a link adaptation (LA) reference signal (RS) transmission, or a hop-specific synchronization and beam management reference signal (RS) transmission.

24. The apparatus of claim 14, wherein scheduling information for the at least one data channel transmission is conveyed via a physical downlink control channel (PDCCH) of the primary cell.

25. The apparatus of claim 14, wherein the sub-THz communication does not include control channel communication, always-on synchronization signal blocks, beam failure recovery procedures, beam failure detection procedures, radio link failure procedures, full range initial acquisition, or random access procedures.

26. The apparatus of claim 14, wherein the first wireless device is a sub-THz repeater having a direct link to the network entity.

27. The apparatus of claim 14, wherein the first wireless device is a sub-THz repeater with a direct link to a user equipment (UE).

28. The apparatus of claim 14, wherein the first wireless device is a second sub-THz repeater having direct links to a first sub-THz repeater and a third sub-THz repeater.

29. A method for wireless communication at a network entity, the method comprising: establishing a first communication with a user equipment (UE) and at least one sub-terahertz (THz) repeater on a primary cell; receiving a UE capability indication from the UE and at least one repeater capability indication from the at least one sub-THz repeater, the UE capability indication indicating capabilities for sub-THz communications associated with the UE, the at least one repeater capability indication indicating at least one capability for the sub-THz communications associated with the at least one sub-THz repeater, the sub-THz communications being at a first frequency range of the first communications that does not include a second frequency, the second frequency being lower than the first frequency range; sending, for the UE, an activation for the sub-THz communication; for each of the at least one sub-THz repeater, sending the activation for the sub-THz communication; communicating scheduling information for at least one data channel transmission via the primary cell; as well as The at least one data channel transmission is communicated via the at least one sub-THz repeater and the sub-THz communication.

30. A method of wireless communication at a first wireless device, the method comprising: Establishing a first communication with a network entity on a primary cell; receiving, from the network entity, activation for sub-THz relay operation for the wireless device over a first frequency range of the first communication that does not include a second frequency; and At least one data channel transmission is amplified and retransmitted as part of the sub-THz relay operation.

Images