Timing control for relays
A forwarding timing advance procedure for repeaters aligns transmit and receive boundaries based on internal delays, addressing signal loss and interference issues in wireless communication systems, improving reliability and efficiency.
Patent Information
- Application Number
- CN202380035708.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-04-27
- Filing Date
- 2023-04-28
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face challenges in aligning the transmit and receive boundaries of repeaters, leading to signal loss and interference due to improper timing alignment, which is not adequately addressed in current technologies.
Implement a forwarding timing advance procedure for repeaters, determining reception and transmission times based on internal delays to align these boundaries accurately, preventing signal loss and interference.
The solution ensures precise timing alignment, preventing signal loss and interference, thereby enhancing the reliability and efficiency of wireless communication systems.
Smart Images

Figure CN119072974A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 363,941, filed on April 29, 2022, and entitled “Timing Control of Repeaters,” and U.S. Non-Provisional Patent Application Serial No. 18 / 308,499, filed on April 27, 2023, and entitled “Timing Control of Repeaters,” the entire texts of which are expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems having repeaters. 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. 5GNR 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] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole 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 for wireless communication at a first network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to perform a forwarding timing advance procedure. To perform the forwarding timing advance procedure, the at least one processor may be configured to: determine a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is targeted for a third network entity; receive the transmission from the second network entity at the first time; and forward the transmission to the third network entity at a second time.
[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication at a first network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: provide a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or the third network entity and determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; and perform one of the following: provide the transmission to the second network entity; or receive the transmission from the second network entity.
[0009] To achieve the aforementioned and related purposes, one or more aspects may include the features fully described below and specifically 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 2Bis a diagram illustrating an example of downlink (DL) channels within a subframe according to 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 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 4A is a diagram illustrating an example network controlled repeater (NCR).
[0017] Figure 4B is a diagram illustrating an example base station in communication with an NCR and a UE.
[0018] Figure 5 is a call flow diagram illustrating example communications between a network node, an NCR, and a UE.
[0019] Figure 6 is a diagram illustrating example timing associated with communications between a base station, an NCR, and a UE.
[0020] Fig. 7A is a diagram illustrating example timing associated with communications between an NCR and a UE.
[0021] Figure 7B is a diagram illustrating example timing associated with communications between an NCR and a UE.
[0022] Fig. 8A is a diagram illustrating example timing associated with communications between an NCR and a UE.
[0023] Figure 8B is a diagram illustrating example timing associated with communications between a base station, an NCR, and a UE.
[0024] Fig. 9 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.
[0025] Fig.10 is a flow chart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure.
[0026] Fig.11 is a flow chart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure.
[0027] Fig.12 is a flow chart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure.
[0028] Fig.13 is a flow chart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure.
[0029] Fig.14 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.
[0030] Fig.15 is a diagram illustrating an example of a hardware implementation for an example network entity.
[0031] Fig.16 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION
[0032] Various aspects relate generally to communication systems. More specifically, some aspects relate to timing control of a repeater. In some examples, a repeater (e.g., a network controlled repeater (NCR)) may perform a forwarding timing advance procedure. According to the procedure, the repeater determines a first time for receiving a transmission from a network entity (e.g., a network node or a UE) based on forwarding timing advance information. The forwarding timing advance information may be based on an internal delay of the repeater. The first time may be determined before the repeater receives the transmission. The repeater may forward the transmission to another network entity at a second time. For example, for an uplink transmission, the repeater may receive an uplink transmission from a UE at a determined first time and forward the uplink transmission to a network node at a second time. For a downlink transmission, the repeater may receive a downlink transmission from a network node at a determined first time and forward the downlink transmission to a UE at a second time.
[0033] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the transmit and receive boundaries of the repeater may be aligned by taking into account the internal delay of the repeater when receiving and / or forwarding transmissions. If such boundaries are not properly aligned, the repeater may attempt to forward the signal too early, resulting in a portion of the signal being lost. In another example, the repeater may continue to forward after the transmission of the signal is completed. This may cause the repeater to transmit noise and interference, which may cause inter-symbol interference at the transmission target (e.g., a network node or UE). Therefore, correctly aligning the transmit and receive boundaries of the repeater enables the repeater to accurately determine when to start forwarding a signal and when to stop forwarding a signal, which prevents signal loss and interference.
[0034] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in 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 cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.
[0035] 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 are 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.
[0036] 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. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, 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 instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
[0037] 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 in 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 media that can be accessed by a computer. By way of 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 may be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0038] 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, various 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 or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can 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) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.
[0039] 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 or 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.
[0040] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can 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 (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0041] 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. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0042] 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.
[0043] 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 transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.
[0044] In some aspects, CU 110 may host one or more higher layer 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 configured to communicate signals with other control functions hosted by CU 110. CU110 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.
[0045] DU 130 may correspond to a logical unit that includes one or more base station functions to control 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.) at least in part according to a functional split such as those 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.
[0046] The lower layer 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 at least in part on functional splitting (such as lower layer 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).
[0047] 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 instantiating 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 .
[0048] 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.
[0049] 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).
[0050] 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 be 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 with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to 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).
[0051] 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 link 158 may be implemented via various wireless D2D communication systems such as, for example, Bluetooth TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard TM (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE or NR) for D2D communication.
[0052] 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.
[0053] The wireless communication system may also include a network controlled repeater (NCR) 160. The NCR 160 may be an in-band RF repeater for extending network coverage on some frequencies such as the FR1 band and the FR2 band. The NCR 160 may be controlled by the base station 102 and may be an extension of the base station 102, improving coverage and service for end users on behalf of the base station. The NCR 160 may include multiple antenna arrays. The first antenna array may be oriented toward the base station 102 (e.g., RU 140), and the second antenna array may be oriented toward the UE (e.g., UE 104). The NCR 160 may be configured to receive signals from the base station 102 and forward these signals to the UE 104, and may be configured to receive signals from the UE 104 and forward these signals to the base station 102.
[0054] 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 different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0055] 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.
[0056] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may 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 herein, it may 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.
[0057] 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 different. The transmit direction and receive direction of the UE 104 may be the same or different.
[0058] 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 and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).
[0059] 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 processes signaling between UE 104 and the 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 processing, 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, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signal can 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 / positioning 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, an NR signal (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.
[0060] 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.
[0061] Reference again Figure 1 In some aspects, the NCR 160 may include a timing control component 198. In some aspects, the timing control component 198 may be configured to perform a forward timing advance procedure. To perform the forward timing advance procedure, the timing control component 198 may be configured to: determine a first time for receiving a transmission from a second network entity based on forward timing advance information, wherein the forward timing advance information is based on an internal delay of the first network entity, and wherein the transmission is destined for a third network entity; receive the transmission from the second network entity at the first time; and forward the transmission to the third network entity at the second time.
[0062] In some aspects, the base station 102 may have a timing configuration providing component 199, which may be configured to: provide a forwarding configuration to the second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or the third network entity and determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; and perform one of the following items: provide the transmission to the second network entity; or receive the transmission from the second network entity.
[0063] 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 group 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 group of one or more components, a second processing entity, etc.
[0064] As described herein, different terms may be used in various aspects to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes 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, disclosure that the first network node is configured to send information to the second network node includes 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, disclosure that the first network node is configured to send information to the second network node includes 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.
[0065] 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 full DL and full 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). Note that the following description also applies to the 5G NR frame structure as TDD.
[0066] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be 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 equal 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) extended OFDM (DFT-s-OFDM) symbol (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.
[0067]
[0068] Table 1: Parameter set, SCS and CP
[0069] 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. Thus, 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).
[0070] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0071] 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 one 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).
[0072] 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 identification. 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 number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.
[0073] 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 combs in the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.
[0074] 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 buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0075] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In some aspects, communication between the base station 310 and the UE 350 may be provided by the NCR 160, such as in conjunction with Figure 1 , Figure 3 , Figure 4A , Figure 4B , Figure 5 , Figure 6 , Fig. 7A , Figure 7B , Fig. 8A , Figure 8B , Figures 9 to 13 and Fig.16 3. The NCR 160 may include multiple antenna arrays. The first antenna array may be oriented toward the base station 310, and the second antenna array may be oriented toward the UE 350. The NCR 160 may be configured to receive signals from the base station 310 and forward these signals to the UE 350, and may be configured to receive signals from the UE 350 and forward these signals to the base station 310.
[0076] In the DL, Internet Protocol (IP) packets may be provided to the 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.
[0077] The transmit (TX) processor 316 and the 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 processes 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 coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together 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 based on reference signals and / or channel condition 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 with a corresponding spatial stream for transmission.
[0078] 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 combined 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 symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate 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.
[0079] 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.
[0080] 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.
[0081] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted 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 separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.
[0082] 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 corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
[0083] 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.
[0084] NCR 160 can be configured to perform Figure 1 Various aspects related to the timing control component 198.
[0085] 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 timing configuration provides various aspects related to component 199.
[0086] Figure 4A 4 is a diagram 400 illustrating an example network controlled repeater (NCR) 402. In some aspects, the NCR may be an in-band RF repeater for extending network coverage on some frequencies such as the FR1 band and the FR2 band. FR2-based deployments may be used for both outdoor scenarios and outdoor to indoor (O2I) scenarios. In some aspects, the NCR may be a single-hop fixed network controlled repeater (e.g., forwarding transmissions from the UE to the network without an additional hop of the NCR). In some aspects, the NCR may be transparent to the UE. In some aspects, the NCR may maintain both a base station (e.g., gNB)-relay link and a relay-UE link. Some control information (e.g., side control information) may facilitate the operation of the network controlled repeater, such as beamforming information, timing information for aligning the transmit boundary / receive boundary of the network controlled repeater, information about the UL-DL TDD configuration, switch information for efficient interference management and improved energy efficiency, and power control information for efficient interference management. In some aspects, layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling (associated with configuration) may be used to carry side control information. Various aspects provided herein may provide a timing mechanism that may improve repeater-based communications. Figure 4A As shown, NCR 402 can be associated with a full stack UE (and can function as a full stack UE). NCR 402 can be communicatively coupled to DU 404 via PHY / MAC / RLC layers, and can be communicatively coupled to CU 406 via RRC / PDCP layers. NCR 402 can also be communicatively coupled to core network (CN) 408 via non-access stratum (NAS) layers.
[0087] Figure 4B 4 is a diagram illustrating an example base station 410 in communication with an NCR 412 and a UE 422. Figure 4BAs illustrated in FIG. 4 , the base station may include a CU 416 and a DU 414. The NCR 412 may include a UE function (shown as NCR-UE 418) and an amplify and forward (A&F) function (shown as A&F 420). The UE function may also be referred to as a mobile terminal node (NCR-MT). The NCR-UE 418 may be a component of the NCR 412 that maintains a control link (C-link) between the base station and the NCR 412 to enable information exchange (e.g., side control information). The NCR-UE 418 may include a communication interface (e.g., a modem, such as a reference Fig.14 The cellular baseband processor 1424 described above can be used to control and / or configure the NCR 412 through the communication interface (e.g., via commands or control information provided via the communication interface) provided by the base station. The A&F 420 can also be referred to as a forwarding node (NCR-FWD). The A&F 420 can be a component of the NCR 412 that maintains a backhaul link between the base station and the NCR 412 and an access link between the NCR 412 and the UE 422. The A&F 420 can include multiple antennas for sending and receiving RF signals, such as antenna elements, antenna panels, and / or antenna arrays. The A&F 420 can also provide gain control to amplify the signal before sending. In some aspects, the NCR-UE 418 and the A&F 420 can be co-located. For example, the NCR-UE 418 and the A&F 420 can be included in the same device housing. In another example, the NCR-UE 418 and the A&F 420 can be located in the same room. In other aspects, the NCR-UE 418 and the A&F 420 may not be co-located. For example, the NCR-UE 418 and the A&F 420 may be included in different equipment housings. In another example, the NCR-UE 418 may be located on the first floor of a building, and the A&F 420 may be located on the second floor of the building. The A&F 420 may receive downlink signals from a base station (e.g., from the DU 414) and forward these downlink signals to the UE 422. Similarly, the A&F 420 may receive uplink signals from the UE 422 and forward these uplink signals to the base station (e.g., to the DU 414).
[0088] Also like Figure 4BAs shown, DU 414 may be communicatively coupled to NCR-UE 418 (such as a UE to UTRAN (Uu) interface). Similarly, UE 422 may be communicatively coupled to DU 414 via A&F 420 using a second interface (e.g., a Uu interface). For example, signals transmitted from UE 422 may be received by a first antenna array of A&F 420, and A&F 420 may forward these signals to DU 414 using a second antenna array of A&F 420. Similarly, signals transmitted from DU 414 may be received by a second antenna array of A&F 420, and A&F 420 may forward these signals to UE 422 using the second antenna array of A&F 420.
[0089] Figure 5 5 is a call flow diagram 500 illustrating example communications between a network node 502, an NCR 506, and a UE 504. The network node 502 may be an example of a base station 102 or a base station 310. Although various aspects are described with respect to the network node 502, these aspects may be performed by a network node in an aggregation and / or by one or more components of the network node 502 (e.g., such as a CU 110, a CU 406, or a CU 416, a DU 130, a DU 404, or a DU 414, and / or a RU 140). At 508, the NCR 506 and the network node 502 may establish and maintain an interface (e.g., a Uu interface) between each other (e.g., over which the NCR 506 and the network node 502 communicate).
[0090] At 510, during NCR integration, NCR 506 may identify itself as a relay (eg, in addition to being a UE) and share its capabilities (eg, to network node 502 and / or other UEs (eg, UE 504)). NCR 506 may perform NCR integration based on authorization.
[0091] At 512, during configuration, the network node 502 and / or the NCR 506 may exchange L1 / L2 control messages to configure operations for the NCR 506 (eg, for the A&F 516 of the NCR 506).
[0092] At 514, the network node 502 may provide a downlink signal to the UE 504. The NCR 506 (eg, the A&F 516 of the NCR 506) may receive the downlink signal and, at 518, may forward the downlink signal to the UE 504. Figure 5As shown, at 514, the network node 502 may also provide a downlink signal to the NCR-UE (or NCR-MT). In some aspects, the downlink signal to the NCR-UE may be multiplexed (e.g., in the same time resource) with the downlink signal to the UE 504. In other aspects, the downlink signal to the NCR-UE may not be multiplexed with the downlink signal to the UE 504.
[0093] At 520, UE 504 may provide uplink signals to network node 502. NCR 506 (e.g., A&F 516 of NCR 506) may receive the uplink signals and, at 522, may forward these uplink signals to network node 502. Figure 5 As shown, at 518, the NCR 506 (e.g., an NCR-UE (or NCR-MT) of the NCR 506) may also provide an uplink signal to the network node. In some aspects, the uplink signal provided by the NCR-UE may be multiplexed (e.g., in the same time resource) with the uplink signal provided by the UE 504. In other aspects, the uplink signal provided by the NCR-UE may not be multiplexed with the uplink signal provided by the UE 504.
[0094] Figure 6 is a diagram 600 illustrating example timing associated with communications between a base station 602 , an NCR 606 , and a UE 604 . Figure 6 Each "DL" in may be a DL time slot, and Figure 6 Each "UL" in may be a UL timeslot. Figure 6 The "F" in the parameter "T" may be one or more flexible time slots associated with a guard period (GP) for switching from UL to DL. During the GP, the device may not transmit to avoid interference within the cell and ensure coexistence between cells by compensating for propagation delay. P1 ” may represent a first propagation delay for a DL transmission, which may represent the amount of time it takes for a DL transmission from base station 602 to be received by NCR 606. Parameter “T P2 " may represent a second propagation delay, which may represent the amount of time it takes for a DL transmission from NCR 606 to be received by UE 604. Parameter "T GD " may represent the group delay (also referred to as "repeater delay" or "internal delay") for forwarding a UL or DL transmission by the NCR 606. The group delay may take into account the propagation delay and repeater processing delay associated with forwarding the UL / DL transmission. The group delay may correspond to the additional latency caused by the amplification chain at the repeater. That is, the group delay may correspond to the amount of time it takes the repeater to amplify and / or transmit (or forward) a received signal.
[0095] As an example, the UL frame 608 of a certain frame number may start with a timing advance (TA) before the DL frame 610 of the same frame number, and the timing advance (TA) may be equal to (N TA(UE) +N TA,offset )T c Parameter T c The parameter N may represent a basic time unit, such as a bit period (eg, approximately 3.69 microseconds). TA,offset The parameter N may represent the TA value offset based on the frequency band (e.g., in nanoseconds). TA(UE) N may represent a TA command provided by the base station 602 to the UE 604. The parameter N may be defined and / or signaled based on the locations of the UE 604 and the base station 602. TA(UE) Parameter N TA(UE) Absolute timing or the ability to adjust the UL timing of the UE 604 may be provided to the UE 604. By way of example, in some wireless communication systems, TA may be a value between 0 and 63, where each step between 0 and 63 represents an advance of one bit period (e.g., approximately 3.69 microseconds). In some aspects, where the signal (radio wave) travels at approximately 300,000,000 meters / second (i.e., 300 meters / microsecond), one TA step may represent a change of approximately 1,100 meters in round-trip distance (twice the propagation range). Thus, in such an example, TA may change for every 550 meters change in range between the UE and the TRP / base station. The NCR 606 may be adjusted based on the group delay T of the NCR 606. GD The UL frame is forwarded 608. The forwarded UL frame is shown as 608'.
[0096] Various aspects provided herein provide a mechanism for a relay to align its Tx / Rx timing. For a relay with UE functionality, the relay may follow the DL Rx timing from the base station and set its DL Rx (and DL Tx / forward) timing accordingly. For example, Figure 6 As shown in the example, DL Tx timing is equal to DL Rx timing (T P1 )+T GD For example, Figure 6 As shown, the DL frame 612 received by the NCR 606 (based on the DL Rx timing (T P1 ) is sent to the UE 604 based on the DL Tx timing. The DL frame sent by the NCR 606 is shown as 612'. However, for the UL Rx timing, it is assumed that there is no repeater delay (T GD =0), NCR 606 may receive a timing advance command TAC (2T P1+Δ) (where Δ represents a value specified by the base station 602 for controlling the timing between downlink transmission and uplink transmission), the timing advance command TAC can be used for UL forwarding of the signal of the UE 604. Various aspects provided herein can allow a repeater with repeater delay to use forwarding timing that can facilitate improved forwarding operation. It should be noted that the group delay may be non-negligible. For example, the group delay can be as small as tens of nanoseconds. In some deployments, the gNB side and service side units can be non-co-located (for example, a 100-foot line corresponds to 100 nanoseconds).
[0097] In some aspects, a repeater may know its group delay (eg, the exact group delay or an estimate thereof) and may adjust / advance its UL forward timing compared to its own UL Tx timing (eg, the UL Tx timing for UL transmissions originating from the repeater). Fig. 7A 7 is a diagram 700 illustrating example timing associated with communications between an NCR 706 and a UE 704. Fig. 7A As illustrated in FIG. 1 , UE 704 may send UL transmission 702 to be forwarded by NCR 706 to a base station. NCR 706 may transmit UL transmission 702 based on the propagation delay T P2 The NCR 706 may receive the UL transmission 702 (shown as 708). The NCR 706 may receive the UL transmission 702 (shown as 708) based on the repeater delay T earlier than the repeater's own UL transmission 710. GD The received UL transmission 708 may be forwarded with a timing advance of 100 ms. That is, the UL reception timing of the NCR 706 (e.g., the A&R (or NCR-FWD) of the NCR 706) for the UL signal (or UL transmission 708) received by the NCR 706 from the UE 704 may be advanced compared to the UL transmission timing of the NCR 706 (e.g., the NCR-UE (or NCR-MT) or the A&R (or NCR-FWD) of the NCR 706) for the UL signal (or UL transmission 710) forwarded to the network node (e.g., the gNB). The UL reception timing may be advanced by an internal delay T compared to the UL transmission timing. GD For example, in some aspects, the UL reception timing of the NCR-FWD may be ahead of the UL transmission timing of the NCR-MT (or NCR-FWD) by a certain delay (eg, an internal delay).
[0098] In some aspects, the group delay may not be precisely known (e.g., it may be known with uncertainty / inaccuracy), and it may be beneficial for the NCR 706 to begin receiving / forwarding the UL signal with sufficient time in advance. Figure 7B 7 is a diagram 750 illustrating example timing associated with communications between NCR 706 and UE 704 where the group delay is not precisely known. Figure 7BAs illustrated in FIG. 1 , the duration of the UL forwarding (shown as 712) (or UL forwarding window) may be increased to be greater than a single OFDM symbol to ensure that the entire UL signal can be captured and forwarded upon reception. Fig. 7A The duration of the UL forwarding shown (indicated via the dashed box) is in contrast, which corresponds to the length of the UL transmission 708 because of the internal delay T GD is accurately known for NCR 706. Similarly, the duration of a DL forward (shown as 714) (or DL forwarding window) may be increased to be greater than a single OFDM symbol to ensure that the entire DL signal can be captured and forwarded upon reception.
[0099] In some aspects, the relay may be configured / instructed by the network (eg, via L1 / L2 / L3 signaling) to widen its UL / DL forwarding window (eg, the duration of UL forwarding 712, such as Figure 7B ). A forwarding window may be a time window configured for both monitoring a transmission to be forwarded and forwarding the transmission. Fig. 8A 8 is a diagram 800 illustrating example timing associated with communications between an NCR 806 and a UE 804. Fig. 8AAs illustrated in , the forwarding window 808 may be widened so that the NCR 806 may start at t1 (which may be a value in nanoseconds (ns)) before the first DL / UL symbol relative to its own DL / UL Rx / Tx timing reference, and may continue forwarding at t2 (which may be a value in ns) after the last scheduled DL / UL symbol in the burst (for NCR806 DL / UL transmissions between the NCR 806 and the base station). In some aspects, the exact values of t1 and t2 may be indicated. In some aspects, t2 may be 0. In some aspects, t1 may be equal to t2. In some aspects, the maximum / minimum value (or range) of any one of the offset values (e.g., t1 or t2) may be indicated. In some aspects, the network (e.g., base station) may update the offset and indicate the new offset to the NCR 806. In some aspects, the indication may be based on a relative adjustment to the current offset. In some aspects, the offsets may be beam-specific (each offset is associated with a respective beam of the NCR 806, wherein a signal transmitted or received via a first beam of the NCR 806 utilizes a first set of offset values, and a signal transmitted or received via a second beam of the NCR 806 utilizes a second set of offset values), may be channel-specific (e.g., depending on the channel type being PUCCH, PUSCH, PDCCH, PDSCH, PRACH, sounding reference signal (SRS), synchronization signal block (SSB), channel state information (CSI) reference signal (CSI-RS), positioning reference signal (PRS), etc.), may be specific to a set of time / frequency resources used for transmission or reception, etc. In some aspects, the offset values (e.g., t1 or t2) may be different for DL and UL. In such aspects, the network may indicate to the NCR 806 which offset value is used for DL and which offset is used for UL.
[0100] In some aspects, a repeater may indicate (e.g., via L1 / L2 / L3 signaling) information about a repeater delay (i.e., group delay or internal delay) to the network. For example, the repeater may indicate whether it knows the group delay accurately within a certain maximum error and / or indicate a known group delay. If the repeater does not know the group delay accurately, the repeater may indicate an uncertainty range for the group delay (e.g., a range in which the group delay is expected to be within a specified confidence level). Two or more ranges may be defined, and the repeater may indicate an index (or associated type / class). For example, a first range may be associated with a first index (e.g., corresponding to a first type, class, or confidence level), and a second range may be associated with a second index (e.g., corresponding to a second type, class, or confidence level). The repeater may also indicate that certain offset values are authorized (e.g., as combined with Fig. 8AIn some aspects, the repeater may indicate that the group delay in the DL direction and the UL direction may be different, and indicate multiple values associated with different directions (for example, the repeater may indicate a first group delay for DL transmission and indicate a second group delay for UL transmission). In some aspects, the repeater may indicate that the group delay within a "flexible" symbol may be different (compared to DL / UL symbols for which information may be known in advance) and / or indicate the group delay of the "flexible" symbol. For example, within a "flexible" symbol, the group delay may be different because the NCR 806 may not know in advance whether the "flexible" symbol will be used for UL transmission or DL transmission. Therefore, the operation of the NCR 806 on the "flexible" symbol may be different from that of the UL symbol and the DL symbol. This may result in different group delays for the "flexible" symbol because additional processing may be utilized at the NCR 806 when determining whether the "flexible" symbol is to be used for UL transmission or DL transmission. In some aspects, the repeater may indicate that the group delays in different directions (or different backhaul directions and access direction pairs) may be different. For example, the repeater may indicate that the group delay of the access link between the repeater and the UE is different from the group delay of the backhaul link between the base station and the repeater. The repeater may indicate the group delay of the access link and the backhaul link to the network. In some aspects, the group delay may depend on the Rx antenna array, the Tx antenna array, and / or a combination thereof. For example, the repeater may indicate that the group delay of the receiving antenna array set is different from the group delay of the transmitting antenna array set. In such scenarios, the repeater may indicate the corresponding group delays of the Rx antenna array and the Tx antenna array. In some aspects, the repeater may indicate that the group delay may depend on the level of the incoming signal power. In such aspects, the repeater may indicate different group delays or group delay ranges, each of which corresponds to a specific level of the incoming signal power. In some aspects, the group delay may change over time. In such scenarios, the repeater may indicate the group delay to the network each time it changes (or once every N times, where N is any positive integer). The network may configure a UL or DL forwarding window for the repeater based on the repeater delay information provided by the repeater.
[0101] In some aspects, UL symbols carrying PRACH (e.g., PRACH preambles) may be forwarded without (i.e., without) timing advance. In some aspects, a relay may know the PRACH resources via system information block 1 (SIB1) that provides PRACH configuration (e.g., may know which resources are PRACH resources based on the preamble index included in SIB1), and may not apply timing advance to forward UL signals within the PRACH resources. For example, Figure 8B850 is a diagram illustrating example timing associated with communications between a base station 802, an NCR 806, and a UE 804. In some aspects, the NCR 806 may explicitly receive (via L1 / L2 / L3 signaling) (e.g., by the base station 802) an indication of a set of one or more symbols or time slots within which the NCR 806 may not apply a timing advance for UL forwarding. In some aspects, the indication may be dynamic (e.g., the indication may be indicated via a DCI), semi-static (e.g., the indication may be indicated via RRC signaling), periodic (e.g., the indication may be periodically indicated to the NCR 806 according to a periodic time frame), or semi-persistent (e.g., the indication may be indicated via a PDCCH). In some aspects, the NCR 806 may receive two or more timing offsets to apply when forwarding a UL signal. In some aspects, one of the two or more timing offsets may be zero (e.g., an offset for symbols or time slots for which no timing advance is applied for UL forwarding). As shown in FIG. Figure 8B As shown, NCR 806 may receive an indication from base station 802 that symbol 810 is to be forwarded to base station 802 without a timing advance. Thus, forwarding time / window 812 does not have any timing advance.
[0102] Fig. 9 9 is a call flow diagram 900 illustrating a method of wireless communication according to various aspects of the present disclosure. Fig. 9 As shown, diagram 900 includes a network node 902, a UE 904, and an NCR 906. Network node 902 may be an example of base station 102, base station 310, network node 502, base station 602, or base station 802. UE 904 may be an example of UE 104, UE 350, UE 422, UE 504, UE 604, UE 704, or UE 804. NCR 906 may be an example of NCR 402, NCR 412, NCR 506, NCR 606, NCR 706, or NCR 806. Although various aspects are described with respect to network node 902, these aspects may be performed by a network node in an aggregation and / or by one or more components of network node 502 (e.g., such as CU 110, CU 406, or CU 416, DU 130, DU 404, or DU 414, and / or RU 140).
[0103] At 908 , the NCR 906 may provide the network node 902 with a relay configuration request and / or relay information.
[0104] In some aspects, the NCR 906 may provide the relay configuration request and / or the relay information to the network node 902 via L1 signaling, L2 signaling, or L3 signaling.
[0105] In some aspects, the relay information may include an indication of one or more values, one or more accuracies, or one or more uncertainty ranges associated with an internal delay of the NCR 906. The internal delay may be a delay of the NCR 906 that takes into account propagation delays and processing delays associated with forwarding transmissions to the network node 902 or the UE 904.
[0106] In some aspects, the indication representing the uncertainty ranges can be an index (eg, corresponding to a first type, category, or confidence level for each of the uncertainty ranges).
[0107] In some aspects, the repeater information may include an indication that the internal delay is based on whether the transmission is an UL transmission or a DL transmission. The internal delay may include one or more values, and the one or more values may each be included in the repeater information. A first value of the values of the internal delay may be associated with the UL transmission, and a second value of the values of the internal delay may be associated with the DL transmission. That is, the repeater information may indicate which of the internal delay values are used for the UL transmission and which of the internal delay values are used for the DL transmission.
[0108] In some aspects, the repeater information may include an indication that the value of the internal delay is based on a direction or antenna set associated with the UL transmission or the DL transmission. For example, the repeater information may indicate which of the internal delay values are used in a particular direction or a particular antenna set for UL transmission and which of the internal delay values are used in a particular direction or a particular antenna set for DL transmission.
[0109] In some aspects, the repeater information may include an indication that the value of the internal delay is based on a signal power associated with the reception of the UL transmission or the DL transmission. For example, the repeater information may indicate which of the internal delay values are for a particular signal power associated with the reception of the UL transmission or the DL transmission.
[0110] At 910, network node 902 may provide a relay configuration to NCR 906. The relay configuration may be based on the information provided by NCR 906 at 908.
[0111] In some aspects, the network node 902 may provide the relay configuration to the NCR 906 via L1 signaling, L2 signaling, or L3 signaling.
[0112] In some aspects, the relay configuration may include forwarding timing advance information by which the NCR 906 performs a forwarding timing advance procedure. The forwarding timing advance procedure may be utilized by the NCR 906 to determine a first time for receiving a transmission from the network node 902 or the UE 904 and / or a time for forwarding the transmission to the network node 902 or the UE 904. The NCR 906 may utilize the forwarding timing advance information to perform the forwarding timing advance procedure. The forwarding timing advance information may include information that enables the NCR 906 to determine the first time and / or the second time. For example, the forwarding timing advance information may include an internal delay of the NCR 906 and / or a timing advance value associated with the transmission received by the NCR 906. The timing advance value may be based on a first propagation delay between the network node 902 and the NCR 906 or a second propagation delay between the UE 904 and the NCR 906. The timing advance value may be provided to the NCR 906 by the network node 902.
[0113] In some aspects, forwarding the timing advance information may be based on a timing advance value associated with a DL transmission from the NCR 906 to the UE 904 or a UL transmission from the UE 904 to the NCR 906. At 910, a timing advance value may be received from the network node 902. For example, a relay configuration may include a timing advance command indicating a timing advance value.
[0114] In some aspects, the forwarded timing advance information may be equal to a combination of the timing advance value and an internal delay of the NCR 906. In some aspects, the forwarded timing advance information may be equal to the timing advance value plus the internal delay.
[0115] In some aspects, the forwarded timing advance information may include a timing advance value, and the NCR 906 may determine the forwarded timing advance information based on the timing advance value known to the NCR 906 and its internal delay.
[0116] In some aspects, the relay configuration may include a forwarding configuration by which the NCR 906 forwards the transmission to the network node 902 or the UE 904 .
[0117] In some aspects, the forwarding configuration may include an indication of a UL forwarding window or a DL forwarding window associated with the forwarding timing advance procedure. The UL forwarding window or the DL forwarding window may represent a time window configured for receiving UL or DL transmissions and forwarding the UL or DL transmissions.
[0118] In some aspects, the indication included in the forwarding configuration may include a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
[0119] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with the set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information.
[0120] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information.
[0121] At 912, the NCR 906 may perform a forwarding timing advance procedure, for example, by determining, based on the forwarding timing advance information, a first time for receiving a transmission from the network node 902 or the UE 904. As described above, the forwarding timing advance information may be based on an internal delay of the NCR 906. If the transmission is received from the UE 904, the target of the transmission may be the network node 902. If the transmission is from the network node 902, the target of the transmission may be the UE 904.
[0122] In some aspects, for DL transmissions from the network node 902 to the UE 904, the forwarding advance timing procedure may be based on a timing advance value associated with the DL transmission. For UL transmissions from the UE 904 to the network node 902, the forwarding advance timing procedure may be based on a timing advance value associated with the UL transmission. The start time of the UL forwarding window may be earlier than the start time of the DL transmission or the UL transmission based on the timing advance value by a third value (e.g., t1, such as Fig. 8A The end time of the UL forwarding window or the DL forwarding window may be later than the end of the DL transmission or the UL transmission by a fourth value (eg, t2, as shown). Fig. 8A shown).
[0123] In some aspects, the third value or the fourth value may be associated with a channel type used for DL or UL transmission, a beam associated with receiving or forwarding DL or UL transmission, or a set of time or frequency resources associated with DL or UL transmission.
[0124] In some aspects, the channel type may be one of: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS, or PRS.
[0125] In some aspects, NCR 906 may send a request for the third value and / or the fourth value to network node 902, for example at 908. In such aspects, network node 902 may provide the third value and / or the fourth value via the relay configuration received at 910.
[0126] In one example, at 914, network node 902 may provide a downlink signal to NCR 906, and NCR 906 may receive the downlink signal from NCR 906 at the first time determined at 912. At 916, NCR 906 may forward the downlink signal to UE 904 at a second time.
[0127] As described above, the forwarding timing advance procedure for downlink signals may be based on a combination of a timing advance value associated with the downlink signal and an internal delay of the NCR 906 .
[0128] The downlink signal may be forwarded based on the forwarding configuration received at 910 .
[0129] In another example, at 918, UE 904 may provide an uplink signal to NCR 906, and NCR 906 may receive the uplink signal from NCR 906 at the first time determined at 912. At 920, NCR 906 may forward the uplink signal to network node 902 at a second time.
[0130] As described above, the forwarding timing advance procedure for uplink signals may be based on a combination of a timing advance value associated with the uplink signal and an internal delay of the NCR 906 .
[0131] The uplink signal may be forwarded based on the forwarding configuration received at 910 .
[0132] Fig.10 1000 is a flowchart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure. In some aspects, the first network entity may be Fig.16 The NCR 402, NCR 412, NCR 506, NCR 606, NCR 706, NCR 806 or NCR 906 (or at least one component thereof (e.g., NCR-UE 418 or A&F 420)) or network entity 1660 in a hardware specific implementation of the present invention.
[0133] At 1002, a first network entity may perform a forwarding timing advance procedure. To perform the forwarding timing advance procedure, in some aspects, as part of 1002, at 1004, the first network entity may determine a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is destined for a third network entity. For example, referring to Fig. 9 In one aspect, in which a forwarding timing advance procedure (i.e., a downlink forwarding timing advance procedure) is performed for a DL transmission, the first network node is a base station (e.g., network node 902) or at least one component thereof, and the third network node is a UE (e.g., UE 904) or at least one component thereof, the NCR 906 at 912 may determine a first time for receiving a transmission (e.g., a downlink signal at 914) from the network node 902 based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the NCR 906, and wherein the target of the transmission is UE 904. In one aspect where a forwarding timing advance procedure is performed for an UL transmission (i.e., an uplink forwarding timing advance procedure), the first network node is a UE (e.g., UE 904) or at least one component thereof, and the third network node is a base station (e.g., network node 902) or at least one component thereof, the NCR 906 at 912 may determine a first time for receiving a transmission (e.g., an uplink signal at 918) from the UE 904 based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the NCR 906, and wherein the transmission is targeted for the network node 902. In one aspect, 1004 may be performed by a timing control component 198.
[0134] In some aspects, the forwarding timing advance procedure may be based on a timing advance value associated with a DL transmission or an UL transmission from the first network entity to the third network entity. Fig. 9 , the forwarding timing advance procedure performed by the NCR 906 may be based on a timing advance value associated with a DL transmission (e.g., a downlink signal at 914) from the network node 902 to the UE 904. In another example, referring to Fig. 9 , the forwarding timing advance procedure performed by the NCR 906 may be based on a timing advance value associated with a UL transmission from the UE 904 to the network node 902 (eg, the uplink signal at 918).
[0135] In some aspects, the forwarded timing advance information is equal to the timing advance value plus the internal delay. Fig. 9 , the forwarding timing advance information based on the first time determination at 912 may be equal to the timing advance value plus the internal delay of NCR 906.
[0136] In some aspects, the internal delay can be a delay of the first network entity that takes into account propagation delay and processing delay associated with forwarding transmission. Fig. 9 , the internal delay may be the delay of the NCR 906 that takes into account the propagation delay and processing delay associated with forwarding transmission.
[0137] As part of 1002, at 1006, the first network entity may receive the transmission from the second network entity at the first time. Fig. 9 In one aspect where a forward timing advance procedure is performed for DL transmissions, the NCR 906 at 914 may receive a downlink signal from the network node 902 at a first time determined at 912. In one aspect where a forward timing advance procedure is performed for UL transmissions, the NCR 906 at 918 may receive an uplink signal from the UE 904 at a first time determined at 912. In one aspect, 1006 may be performed by the timing control component 198.
[0138] As part of 1002, at 1008, the first network entity may forward the transmission to a third network entity at a second time. Fig. 9 In one aspect where a forward timing advance procedure is performed for DL transmissions, the NCR 906 can forward the downlink signal to the UE 904 at 916. In one aspect where a forward timing advance procedure is performed for UL transmissions, the NCR 906 can forward the uplink signal to the network node 902 at 920. In one aspect, 1008 can be performed by the timing control component 198.
[0139] In some aspects, the first network entity may receive a forwarding configuration from the second network entity or the third network entity via L1, L2, or L3 signaling, and the first network entity may forward the transmission based on the forwarding configuration. Fig. 9 In one aspect where a DL forwarding timing advance procedure is performed, the second network entity is the network node 902, and the third network entity is the UE 904, the NCR 906 may receive a forwarding configuration from the network node 902 at 910, and may forward a downlink signal based on the forwarding configuration at 916. In one aspect where a UL forwarding timing advance procedure is performed, the second network entity is the UE 904, and the third network entity is the network node 902, the NCR 906 may receive a forwarding configuration from the network node 902 at 910, and may forward an uplink signal based on the forwarding configuration at 920.
[0140] In some aspects, the forwarding configuration may include an indication of a UL forwarding window or a DL forwarding window associated with a forwarding timing advance procedure, wherein the UL forwarding window or the DL forwarding window represents a time window configured to receive the transmission and forward the transmission. Fig. 9 , the forwarding configuration received at 910 may include an indication of a UL forwarding window or a DL forwarding window associated with a forwarding timing advance procedure, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission (e.g., receiving an uplink signal at 918 or receiving a downlink signal at 914) and forwarding the transmission (e.g., forwarding an uplink signal at 920 or forwarding a downlink signal at 916).
[0141] In some aspects, the indication may include a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time. Fig. 9 , the indication of the forwarding configuration received at 910 may include a first value or a first range associated with a start time of a UL forwarding window or a DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
[0142] In some aspects, the forward advance timing procedure may be based on a timing advance value associated with a DL transmission or an UL transmission from a first network entity to a third network entity, wherein a start time is a third value earlier than a start time of the DL transmission or the UL transmission based on the timing advance value, and an end time is a fourth value later than an end of the DL transmission or the UL transmission. For example, with reference to Fig. 9 In one aspect where a DL forward advance timing procedure is performed, the second network entity is the network node 902, and the third network entity is the UE 904, the forward advance timing procedure performed by the NCR 906 may be based on a timing advance value associated with a downlink signal from the network node 902 to the UE 904 (e.g., received at 914), wherein the start time is a third value earlier than the start time of the downlink signal based on the timing advance value, and the end time is a fourth value later than the end of the downlink signal. In one aspect where a UL forward advance timing procedure is performed, the second network entity is the UE 904, and the third network entity is the network node 902, the forward advance timing procedure performed by the NCR 906 may be based on a timing advance value associated with an uplink signal from the UE 904 to the network node 902 (e.g., received at 918), wherein the start time is a third value earlier than the start time of the uplink signal based on the timing advance value, and the end time is a fourth value later than the end of the uplink signal.
[0143] In some aspects, the third value or the fourth value may be associated with a channel type used for the transmission, a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission. Fig. 9 , the third value or the fourth value included in the forwarding configuration received at 910 may be associated with a channel type used for the transmission (e.g., a downlink signal received at 914 or an uplink signal received at 918), a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission.
[0144] In some aspects, the channel type is one of: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS, or PRS. Fig. 9 , the channel type associated with the third value or the fourth value included in the forwarding configuration received at 910 can be one of the following items: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS or PRS.
[0145] In some aspects, the first network entity may send a request for the third value or the fourth value to the second network entity or the third network entity via L1, L2, or L3 signaling. Fig. 9 In aspects where the second network entity or the third network entity is the network node 902, the NCR 906 may send a request for the third value or the fourth value to the network node 902 via L1, L2, or L3 signaling at 908.
[0146] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 , the forwarding configuration received at 910 may include an indication for forwarding at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information. For example, referring to Fig. 9 , the timing advance may correspond to one of the timing advance value based on which the first time determination at 912 is based or the forwarded timing advance information.
[0147] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 , the forwarding configuration received at 910 may include an indication of an instruction to forward at least one transmission associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information. For example, referring to Fig. 9 , the timing advance may correspond to one of the timing advance value based on which the first time determination at 912 is based or the forwarded timing advance information.
[0148] In some aspects, the first network entity may send an indication of a value, accuracy, or uncertainty range associated with the internal delay to the second network entity or the third network entity via L1, L2, or L3 signaling. Fig. 9 In aspects where the second network entity or the third network entity is network node 902 , NCR 906 may send an indication at 908 to network node 902 via L1, L2, or L3 signaling representing a value, accuracy, or uncertainty range associated with an internal delay of NCR 906 .
[0149] In some aspects, the indication representing the uncertainty range can be an index. Fig. 9 , the indication representing the uncertainty range sent at 908 can be an index.
[0150] In some aspects, the indication may further indicate that the internal delay is based on whether the transmission is a UL transmission or a DL transmission, wherein a first value in the value of the internal delay is associated with the transmission being a UL transmission and a second value in the value of the internal delay is associated with the transmission being a DL transmission. Fig. 9 , the indication sent at 908 may also indicate an internal delay of the NCR 906 based on whether the transmission is a UL transmission or a DL transmission, wherein a first value in the value of the internal delay of the NCR 906 is associated with the transmission being a UL transmission, and a second value in the value of the internal delay of the NCR 906 is associated with the transmission being a UDL transmission.
[0151] In some aspects, the indication may also indicate that the value of the internal delay is based on the direction or antenna set associated with the transmission. Fig. 9 The indication sent at 908 may also indicate that the value of the internal delay of the NCR 906 is based on the direction or antenna set (eg, of the NCR 906) associated with the transmission.
[0152] In some aspects, the indication may also indicate that the value of the internal delay is based on the signal power associated with the reception of the transmission. Fig. 9The indication sent at 908 may also indicate that the value of the internal delay of the NCR 906 is based on a signal power associated with the reception of the transmission (eg, determined by the NCR 906).
[0153] Fig.11 1100 is a flowchart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure. In some aspects, the first network entity may be Fig.16 The NCR 402, NCR 412, NCR 506, NCR 606, NCR 706, NCR 806 or NCR 906 (or at least one component thereof (e.g., NCR-UE 418 or A&F 420)) or network entity 1660 in a hardware specific implementation of the present invention.
[0154] At 1102, the first network entity may send an indication of a value, accuracy, or uncertainty range associated with an internal delay of the first network entity to a second network entity or a third network entity via L1, L2, or L3 signaling. Fig. 9 In aspects where the second network entity or the third network entity is the network node 902, the NCR 906 may send an indication to the network node 902 at 908 via L1, L2, or L3 signaling representing a value, accuracy, or uncertainty range associated with an internal delay of the NCR 906. In one aspect, 1102 may be performed by the timing control component 198.
[0155] In some aspects, the first network entity may correspond to a relay or at least one component of a relay, the second network entity may correspond to a UE or at least one component of a UE, and the third network entity may correspond to a base station or one or more components of a base station. Fig. 9 , the first network entity may correspond to NCR 906 or at least one component of NCR 906, the second network entity may correspond to UE 904 or at least one component of UE 904, and the third network entity may correspond to network node 902. In such aspects, the forwarding timing advance procedure described below with reference to 1108 may be a UL forwarding timing advance procedure.
[0156] In some aspects, the first network entity may correspond to a relay or at least one component of a relay, the third network entity may correspond to a UE or at least one component of a UE, and the second network entity may correspond to a base station or one or more components of a base station. Fig. 9, the first network entity may correspond to NCR 906 or at least one component of NCR 906, the third network entity may correspond to UE 904 or at least one component of UE 904, and the second network entity may correspond to network node 902. In such aspects, the forwarding timing advance procedure described below with reference to 1108 may be a UL forwarding timing advance procedure. In such aspects, the forwarding timing advance procedure described below with reference to 1108 may be a DL forwarding timing advance procedure.
[0157] In some aspects, the internal delay can be a delay of the first network entity that takes into account propagation delay and processing delay associated with forwarding transmission. Fig. 9 , the internal delay may be the delay of the NCR 906 that takes into account the propagation delay and processing delay associated with forwarding transmission.
[0158] In some aspects, the indication representing the uncertainty range can be an index. Fig. 9 , the indication representing the uncertainty range sent at 908 can be an index.
[0159] In some aspects, the indication may further indicate that the internal delay is based on whether the transmission received by the relay is an UL transmission or a DL transmission, wherein a first value in the value of the internal delay is associated with the transmission being an UL transmission and a second value in the value of the internal delay is associated with the transmission being a DL transmission. Fig. 9 , the indication sent at 908 may also indicate that the internal delay of NCR 906 is based on whether the transmission received by the repeater is a UL transmission or a DL transmission, wherein a first value in the value of the internal delay of NCR 906 is associated with the transmission being a UL transmission, and a second value in the value of the internal delay of NCR 906 is associated with the transmission being a UDL transmission.
[0160] In some aspects, the indication may also indicate that the value of the internal delay is based on the direction or antenna set associated with the transmission. Fig. 9 The indication sent at 908 may also indicate that the value of the internal delay of the NCR 906 is based on the direction or antenna set (eg, of the NCR 906) associated with the transmission.
[0161] In some aspects, the indication may also indicate that the value of the internal delay is based on the signal power associated with the reception of the transmission. Fig. 9 The indication sent at 908 may also indicate that the value of the internal delay of the NCR 906 is based on a signal power associated with the reception of the transmission (eg, determined by the NCR 906).
[0162] At 1104, the first network entity may send a request for the first value or the second value to the second network entity or the third network entity via L1, L2, or L3 signaling. Fig. 9 In aspects where the second network entity or the third network entity is network node 902, NCR 906 may send a request for the first value or the second value to network node 902 via L1, L2, or L3 signaling at 908. In one aspect, 1104 may be performed by timing control component 198.
[0163] In some aspects, the first value or the second value may be associated with a channel type used for a transmission received by the first network entity, a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission. Fig. 9 The first value or the second value included in the forwarding configuration received at 910 may be associated with a channel type used for the transmission (e.g., a downlink signal received at 914 or an uplink signal received at 918), a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission.
[0164] In some aspects, the channel type is one of: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS, or PRS. Fig. 9 , the channel type associated with the third value or the fourth value included in the forwarding configuration received at 910 can be one of the following items: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS or PRS.
[0165] At 1106, the first network entity may receive a forwarding configuration from the second network entity or the third network entity via L1, L2, or L3 signaling. Fig. 9 In one aspect where a DL forwarding timing advance procedure is performed, the second network entity is the network node 902, and the third network entity is the UE 904, the NCR 906 can receive a forwarding configuration from the network node 902 at 910. In one aspect where a UL forwarding timing advance procedure is performed, the second network entity is the UE 904, and the third network entity is the network node 902, the NCR 906 can receive a forwarding configuration from the network node 902 at 910. In one aspect, 1106 can be performed by the timing control component 198.
[0166] At 1108, the first network entity may perform a forwarding timing advance procedure. To perform the forwarding timing advance procedure, in some aspects, as part of 1108, at 1110, the first network entity may determine a first time for receiving a transmission from the second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is destined for a third network entity. For example, referring to Fig. 9 In one aspect, in which a forwarding timing advance procedure (i.e., a downlink forwarding timing advance procedure) is performed for a DL transmission, the first network node is a base station (e.g., network node 902) or at least one component thereof, and the third network node is a UE (e.g., UE 904) or at least one component thereof, the NCR 906 at 912 may determine a first time for receiving a transmission (e.g., a downlink signal at 914) from the network node 902 based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the NCR 906, and wherein the target of the transmission is UE 904. In one aspect where a forwarding timing advance procedure is performed for an UL transmission (i.e., an uplink forwarding timing advance procedure), the first network node is a UE (e.g., UE 904) or at least one component thereof, and the third network node is a base station (e.g., network node 902) or at least one component thereof, the NCR 906 at 912 may determine a first time for receiving a transmission (e.g., an uplink signal at 918) from the UE 904 based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the NCR 906, and wherein the transmission is targeted for the network node 902. In one aspect, 1110 may be performed by the timing control component 198.
[0167] In some aspects, the forwarding timing advance procedure may be based on a timing advance value associated with a DL transmission or an UL transmission from the first network entity to the third network entity. Fig. 9 , the forwarding timing advance procedure performed by the NCR 906 may be based on a timing advance value associated with a DL transmission (e.g., a downlink signal at 914) from the network node 902 to the UE 904. In another example, referring to Fig. 9 , the forwarding timing advance procedure performed by the NCR 906 may be based on a timing advance value associated with a UL transmission from the UE 904 to the network node 902 (eg, the uplink signal at 918).
[0168] In some aspects, the forwarded timing advance information is equal to the timing advance value plus the internal delay. Fig. 9 , the forwarding timing advance information based on the first time determination at 912 may be equal to the timing advance value plus the internal delay of NCR 906.
[0169] As part of 1108, at 1112, the first network entity may receive the transmission from the second network entity at the first time. Fig. 9 In one aspect where a forward timing advance procedure is performed for DL transmissions, the NCR 906 at 914 may receive a downlink signal from the network node 902 at a first time determined at 912. In one aspect where a forward timing advance procedure is performed for UL transmissions, the NCR 906 at 918 may receive an uplink signal from the UE 904 at a first time determined at 912. In one aspect, 1112 may be performed by the timing control component 198.
[0170] As part of 1108, at 1114, the first network entity may forward the transmission to a third network entity at a second time. Fig. 9 In one aspect where a forward timing advance procedure is performed for DL transmissions, the NCR 906 can forward the downlink signal to the UE 904 at 916. In one aspect where a forward timing advance procedure is performed for UL transmissions, the NCR 906 can forward the uplink signal to the network node 902 at 920. In one aspect, 1114 can be performed by the timing control component 198.
[0171] In some aspects, as part of 1114, at 1116, the first network entity may forward the transmission based on the forwarding configuration. Fig. 9 In one aspect where a DL forward timing advance procedure is performed, the second network entity is the network node 902, and the third network entity is the UE 904, the NCR 906 may forward the downlink signal based on the forwarding configuration at 916. In one aspect where a UL forward timing advance procedure is performed, the second network entity is the UE 904, and the third network entity is the network node 902, the NCR 906 may forward the uplink signal based on the forwarding configuration at 920. In one aspect, 1116 may be performed by the timing control component 198.
[0172] In some aspects, the forwarding configuration may include an indication of a UL forwarding window or a DL forwarding window associated with a forwarding timing advance procedure, wherein the UL forwarding window or the DL forwarding window represents a time window configured to receive the transmission and forward the transmission. Fig. 9, the forwarding configuration received at 910 may include an indication of a UL forwarding window or a DL forwarding window associated with a forwarding timing advance procedure, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission (e.g., receiving an uplink signal at 918 or receiving a downlink signal at 914) and forwarding the transmission (e.g., forwarding an uplink signal at 920 or forwarding a downlink signal at 916).
[0173] In some aspects, the indication may include a third value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a fourth value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time. Fig. 9 , the indication of the forwarding configuration received at 910 may include a third value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a fourth value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
[0174] In some aspects, the forward advance timing procedure may be based on a timing advance value associated with a DL transmission or an UL transmission from the first network entity to the third network entity, wherein the start time is a first value earlier than the start time of the DL transmission or the UL transmission based on the timing advance value (requested at 1104), and the end time is a second value later than the end of the DL transmission or the UL transmission (requested at 1104). For example, referring to Fig. 9 In one aspect where a DL forward advance timing procedure is performed, the second network entity is the network node 902, and the third network entity is the UE 904, the forward advance timing procedure performed by the NCR 906 may be based on a timing advance value associated with a downlink signal from the network node 902 to the UE 904 (e.g., received at 914), wherein the start time is earlier than a start time of the downlink signal based on the timing advance value by a first value, and the end time is later than an end of the downlink signal by a second value. In one aspect where a UL forward advance timing procedure is performed, the second network entity is the UE 904, and the third network entity is the network node 902, the forward advance timing procedure performed by the NCR 906 may be based on a timing advance value associated with an uplink signal from the UE 904 to the network node 902 (e.g., received at 918), wherein the start time is earlier than a start time of the uplink signal based on the timing advance value by a first value, and the end time is later than an end of the uplink signal by a second value.
[0175] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 , the forwarding configuration received at 910 may include an indication for forwarding at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information. For example, referring to Fig. 9 , the timing advance may correspond to one of the timing advance value based on which the first time determination at 912 is based or the forwarded timing advance information.
[0176] In some aspects, the forwarding configuration may include an indication for forwarding at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 , the forwarding configuration received at 910 may include an indication of an instruction to forward at least one transmission associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. In some aspects, the timing advance may correspond to one of a timing advance value or forwarded timing advance information. For example, referring to Fig. 9 , the timing advance may correspond to one of the timing advance value based on which the first time determination at 912 is based or the forwarded timing advance information.
[0177] Fig.12 1200 is a flowchart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure. In some aspects, the first network entity may be Fig.15 The base station 102, the base station 310, the network node 502, the base station 602, the base station 802, or the network node 902, or the network entity 1502 in the hardware specific implementation.
[0178] In some aspects, the first network entity may correspond to a base station or at least one component of a base station, the second network entity may correspond to a relay or at least one component of a relay, and the third network entity may correspond to a UE or one or more components of a UE. Fig. 9 , the first network entity may correspond to the network node 902 or at least one component of the network node 902, the second network entity may correspond to the NCR 906 or at least one component of the NCR 906, and the third network entity may correspond to the UE 904 or one or more components of the UE 904.
[0179] At 1202, the first network entity may provide a forwarding configuration to the second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or a third network entity and to determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity. Fig. 9 , the network node 902 may provide a forwarding configuration to the NCR 906 at 910. The forwarding configuration may be configured to enable the NCR 906 to determine a first time for receiving a transmission from the network node 902 (for downlink transmissions) or the UE 904 (for uplink transmissions) and a second time for forwarding the transmission to the network node 902 (for uplink transmissions) or the UE 904 (for downlink transmissions) based on an internal delay of the NCR 906. In one aspect, 1202 may be performed by a timing configuration providing component 199.
[0180] In some aspects, the internal delay can be a delay of the second network entity that takes into account propagation delay and processing delay associated with forwarding transmission. Fig. 9 , the internal delay can be the delay of the NCR 906, which takes into account the propagation delay and processing delay associated with forwarding transmission (e.g., at 916 or 920).
[0181] At 1204, the first network entity may perform one of the following: provide a transmission to the second network entity; or receive a transmission from the second network entity. Fig. 9 , the network node 902 may provide a downlink signal to the NCR 906 at 914 or receive an uplink signal from the NCR 906 at 920. In one aspect, 1204 may be performed by the timing configuration providing component 199.
[0182] In some aspects, the forwarding configuration may include an indication of a UL forwarding window or a DL forwarding window, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission at the second network entity and forwarding the transmission from the second network entity. Fig. 9 The forwarding configuration provided at 910 may include an indication of a UL forwarding window or a DL forwarding window, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving transmissions at the NCR 906 and forwarding transmissions from the NCR 906.
[0183] In some aspects, the indication may include a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time. Fig. 9 , the indication included in the forwarding configuration provided at 910 may include a first value or a first range associated with a start time of a UL forwarding window or a DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
[0184] In some aspects, the forwarding configuration may include an indication for the second network entity to forward at least one transmitted instruction associated with the set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 The forwarding configuration provided at 910 may include an indication for the NCR 906 to forward at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
[0185] In some aspects, the forwarding configuration may include an indication for the second network entity to forward at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 The forwarding configuration provided at 910 may include an indication for the NCR 906 to forward at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
[0186] In some aspects, the first network entity may receive an indication of a value, accuracy, or uncertainty range associated with an internal delay of the second network entity via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling. Fig. 9 , the network node 902 may receive, at 908, an indication of a value, accuracy, or uncertainty range associated with an internal delay of the NCR 906 via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling.
[0187] In some aspects, the indication may represent a range of uncertainty in the index. Fig. 9 , the indication received at 908 represents a range of uncertainty in the index.
[0188] In some aspects, the indication may further indicate that the internal delay is based on whether the transmission is a UL transmission or a DL transmission, wherein a first value in the value of the internal delay is associated with the transmission being a UL transmission and a second value in the value of the internal delay is associated with the transmission being a DL transmission. Fig. 9The indication received at 908 may also indicate that the internal delay is based on whether the transmission is a UL transmission or a DL transmission, wherein a first value in the values of the internal delay is associated with the transmission being a UL transmission and a second value in the values of the internal delay is associated with the transmission being a DL transmission.
[0189] In some aspects, the indication may also indicate that the value of the internal delay is based on the direction or antenna set associated with the transmission. Fig. 9 The indication received at 908 may also indicate that the value of the internal delay is based on a direction or set of antennas associated with the transmission.
[0190] In some aspects, the indication may also indicate that the value of the internal delay is based on the signal power associated with the reception of the transmission. Fig. 9 , the indication received at 908 may also indicate that the value of the internal delay is based on the signal power associated with the reception of the transmission at 914 or 918.
[0191] Fig.13 1300 is a flowchart illustrating a method of wireless communication at a first network entity according to various aspects of the present disclosure. In some aspects, the first network entity may be Fig.15 The base station 102, the base station 310, the network node 502, the base station 602, the base station 802, or the network node 902, or the network entity 1502 in the hardware specific implementation.
[0192] In some aspects, the first network entity may correspond to a base station or at least one component of a base station, the second network entity may correspond to a relay or at least one component of a relay, and the third network entity may correspond to a UE or one or more components of a UE. Fig. 9 , the first network entity may correspond to the network node 902 or at least one component of the network node 902, the second network entity may correspond to the NCR 906 or at least one component of the NCR 906, and the third network entity may correspond to the UE 904 or one or more components of the UE 904.
[0193] At 1302, a first network entity may receive an indication of a value, accuracy, or uncertainty range associated with an internal delay of a second network entity via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling. Fig. 9 The network node 902 may receive, at 908, via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling, an indication of a value, accuracy, or uncertainty range associated with an internal delay of the NCR 906. In one aspect, 1302 may be performed by the timing configuration providing component 199.
[0194] In some aspects, the internal delay can be a delay of the second network entity that takes into account propagation delay and processing delay associated with forwarding transmission. Fig. 9 , the internal delay can be the delay of the NCR 906, which takes into account the propagation delay and processing delay associated with forwarding transmission (e.g., at 916 or 920).
[0195] In some aspects, the indication may represent a range of uncertainty in the index. Fig. 9 , the indication received at 908 represents a range of uncertainty in the index.
[0196] In some aspects, the indication may further indicate that the internal delay is based on whether the transmission by the second network entity is an UL transmission or a DL transmission, wherein a first value in the value of the internal delay is associated with the transmission by the second network entity being an UL transmission, and a second value in the value of the internal delay is associated with the transmission being a DL transmission. Fig. 9 The indication received at 908 may also indicate whether the internal delay is based on whether the transmission of NCR 906 is a UL transmission or a DL transmission, wherein a first value in the value of the internal delay is associated with the transmission being a UL transmission, and a second value in the value of the internal delay is associated with the transmission being a DL transmission.
[0197] In some aspects, the indication may also indicate that the value of the internal delay is based on a direction or set of antennas associated with the transmission of the second network entity. Fig. 9 The indication received at 908 may also indicate that the value of the internal delay is based on a direction or antenna set associated with the transmission of NCR 906 .
[0198] In some aspects, the indication may further indicate that the value of the internal delay is based on a signal power associated with the reception of the transmission by the second network entity. Fig. 9 , the indication received at 908 may also indicate that the value of the internal delay is based on the signal power associated with the reception of the transmission of NCR 906 at 914 or 918.
[0199] At 1304, the first network entity may provide a forwarding configuration to the second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or the third network entity and a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity. Fig. 9, the network node 902 may provide a forwarding configuration to the NCR 906 at 910. The forwarding configuration may be configured to enable the NCR 906 to determine a first time for receiving a transmission from the network node 902 (for downlink transmissions) or the UE 904 (for uplink transmissions) and a second time for forwarding the transmission to the network node 902 (for uplink transmissions) or the UE 904 (for downlink transmissions) based on an internal delay of the NCR 906. In one aspect, 1304 may be performed by the timing configuration providing component 199.
[0200] In some aspects, the forwarding configuration may be based on the indication received at 908 .
[0201] At 1306, the first network entity may perform one of the following: provide the transmission to the second network entity; or receive the transmission from the second network entity. Fig. 9 , the network node 902 can provide a downlink signal to the NCR 906 at 914 or receive an uplink signal from the NCR 906 at 920. In one aspect, 1306 can be performed by the timing configuration providing component 199.
[0202] In some aspects, the forwarding configuration may include an indication of a UL forwarding window or a DL forwarding window, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission at the second network entity and forwarding the transmission from the second network entity. Fig. 9 The forwarding configuration provided at 910 may include an indication of a UL forwarding window or a DL forwarding window, wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving transmissions at the NCR 906 and forwarding transmissions from the NCR 906.
[0203] In some aspects, the indication may include a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time. Fig. 9 , the indication included in the forwarding configuration provided at 910 may include a first value or a first range associated with a start time of a UL forwarding window or a DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
[0204] In some aspects, the forwarding configuration may include an indication for the second network entity to forward at least one transmitted instruction associated with the set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9The forwarding configuration provided at 910 may include an indication for the NCR 906 to forward at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
[0205] In some aspects, the forwarding configuration may include an indication for the second network entity to forward at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent. Fig. 9 The forwarding configuration provided at 910 may include an indication for the NCR 906 to forward at least one transmitted instruction associated with the PRACH without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
[0206] Fig.141400 is a diagram illustrating an example of a hardware implementation for an apparatus 1404. The apparatus 1404 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., a cellular RF transceiver). The cellular baseband processor 1424 may include on-chip memory 1424'. In some aspects, the apparatus 1404 may also include one or more subscriber identity module (SIM) cards 1420 and an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410. The application processor 1406 may include on-chip memory 1406'. In some aspects, the device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include their own dedicated antennas and / or communicate using antennas 1480. The cellular baseband processor 1424 communicates with the UE 104 and / or with the RU associated with the network entity 1402 through the transceiver 1422 via one or more antennas 1480. The cellular baseband processor 1424 and the application processor 1406 may each include a computer-readable medium / memory 1424', 1406', respectively. The additional memory module 1426 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1424', 1406', 1426 may be non-transitory. The cellular baseband processor 1424 and the application processor 1406 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1424 / application processor 1406 to perform the various functions described above when executed by the cellular baseband processor 1424 / application processor 1406. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1424 / application processor 1406 when executing the software.The cellular baseband processor 1424 / application processor 1406 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1404 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1424 and / or the application processor 1406, while in another configuration, the device 1404 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1404.
[0207] Fig.151500 is a diagram illustrating an example of a hardware implementation for a network entity 1502. The network entity 1502 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1502 may include at least one of a CU 1510, a DU 1530, or a RU 1540. For example, depending on the layer functionality handled by the component 199, the network entity 1502 may include a CU 1510; both a CU 1510 and a DU 1530; each of the CU 1510, the DU 1530, and the RU 1540; the DU 1530; both a DU 1530 and a RU 1540; or a RU 1540. The CU 1510 may include a CU processor 1512. The CU processor 1512 may include an on-chip memory 1512'. In some aspects, the CU 1510 may also include an additional memory module 1514 and a communication interface 1518. CU 1510 communicates with DU 1530 via a midhaul link, such as an F1 interface. DU 1530 may include a DU processor 1532. DU processor 1532 may include on-chip memory 1532'. In some aspects, DU 1530 may also include additional memory modules 1534 and a communication interface 1538. DU 1530 communicates with RU 1540 via a fronthaul link. RU 1540 may include a RU processor 1542. RU processor 1542 may include on-chip memory 1542'. In some aspects, RU 1540 may also include additional memory modules 1544, one or more transceivers 1546, antenna 1580, and communication interface 1548. RU 1540 communicates with UE 104. On-chip memory 1512', 1532', 1542' and additional memory modules 1514, 1534, 1544 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1512, 1532, 1542 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 above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.
[0208] As discussed above, component 199 may be configured to: provide a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from a first network entity or a third network entity and determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; and perform one of: providing the transmission to the second network entity; or receiving the transmission from the second network entity. Component 199 may be configured to perform in conjunction with Fig.12 and Fig.13The various aspects described in the flowchart in and / or by the network node 902 in Fig. 9 1502. The component 199 may be within one or more processors of one or more of the CU 1510, the DU 1530, and the RU 1540. The component 199 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1502 may include a variety of components configured for various functions. In one configuration, the network entity 1502 may include: a component for providing a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from a first network entity or a third network entity based on an internal delay of the second network entity and determine a second time for forwarding the transmission to the first network entity or the third network entity; and a component for performing one of the following items: providing the transmission to the second network entity; or receiving the transmission from the second network entity. The component may be a component 199 of the network entity 1502 configured to perform the function recorded by the component. As described above, the network entity 1502 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.
[0209] Fig.16 1600 is an example of a hardware implementation for a network entity 1660. In one example, the network entity 1660 may be within the core network 120. The network entity 1660 may include a network processor 1612. In one example, the network processor 1612 is a cellular baseband processor (or modem), such as the cellular baseband processor 1424 described above. The network processor 1612 may include an on-chip memory 1612'. In some aspects, the network entity 1660 may also include an additional memory module 1614. The network entity 1660 communicates with the CU 1602 or the UE 104 directly (e.g., a backhaul link) or indirectly (e.g., through the RIC) via a network interface 1680. The on-chip memory 1612' and the additional memory module 1614 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1612 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by a corresponding processor, causes the processor to perform the various functions described above.The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing the software.
[0210] As discussed above, component 198 can be configured to perform a forwarding timing advance procedure. To perform the forwarding timing advance procedure, component 198 can be configured to: determine a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is destined for a third network entity; receive the transmission from the second network entity at a first time; and forward the transmission to the third network entity at a second time. Component 198 can be configured to perform a combined Fig.10 and Fig.11 The various aspects described in the flowcharts in and / or by NCR 906 at Fig. 9 1612. Component 198 may be within processor 1612. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1660 may include a variety of components configured for various functions. In one configuration, network entity 1660 may include a component for performing a forwarding timing advance procedure. To perform the forwarding timing advance procedure, network entity 1660 may include: a component for determining a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is targeted for a third network entity; a component for receiving the transmission from the second network entity at a first time; and a component for forwarding the transmission to the third network entity at a second time. The component may be component 198 of network entity 1660 configured to perform the functions recorded by the component.
[0211] Various aspects relate generally to communication systems. More specifically, some aspects relate to timing control of a repeater. In some examples, a repeater (e.g., a network controlled repeater (NCR)) may perform a forwarding timing advance procedure. According to the procedure, the repeater determines a first time for receiving a transmission from a network entity (e.g., a network node or a UE) based on forwarding timing advance information. The forwarding timing advance information may be based on an internal delay of the repeater. The first time may be determined before the repeater receives the transmission. The repeater may forward the transmission to another network entity at a second time. For example, for an uplink transmission, the repeater may receive an uplink transmission from a UE at a determined first time and forward the uplink transmission to a network node at a second time. For a downlink transmission, the repeater may receive a downlink transmission from a network node at a determined first time and forward the downlink transmission to a UE at a second time.
[0212] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the transmit and receive boundaries of the repeater may be aligned by taking into account the internal delay of the repeater when receiving and / or forwarding transmissions. If such boundaries are not properly aligned, the repeater may attempt to forward the signal too early, resulting in a portion of the signal being lost. In another example, the repeater may continue to forward after the transmission of the signal is completed. This may cause the repeater to transmit noise and interference, which may cause inter-symbol interference at the transmission target (e.g., a network node or UE). Therefore, correctly aligning the transmit and receive boundaries of the repeater enables the repeater to accurately determine when to start forwarding a signal and when to stop forwarding a signal, which prevents signal loss and interference.
[0213] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may 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.
[0214] 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 may 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 "while" do not mean a direct temporal relationship or reaction. That is, these phrases (such as "when ......") do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. 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 advantages over other aspects. Unless otherwise specifically stated, 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 a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. A device configured to "output" data (such as, transmit, signal or message) may, for example, send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data. The information stored in the memory includes instructions and / or data.All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later become known to those 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 recorded using the phrase "component for..."
[0215] 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.
[0216] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.
[0217] Aspect 1 is a method for wireless communication at a first network entity, the method comprising: performing a forwarding timing advance procedure, wherein performing the forwarding timing advance procedure comprises: determining a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, wherein a target of the transmission is a third network entity; receiving the transmission from the second network entity at the first time; and forwarding the transmission to the third network entity at a second time.
[0218] Aspect 2 is a method according to aspect 1, wherein the forwarding timing advance procedure is based on a timing advance value associated with a DL transmission or a UL transmission from the first network entity to the third network entity.
[0219] Aspect 3 is a method according to aspect 2, wherein the forwarded timing advance information is equal to the timing advance value plus the internal delay.
[0220] Aspect 4 is a method according to any one of aspects 1 to 3, the method further comprising: receiving a forwarding configuration from the second network entity or the third network entity via L1, L2 or L3 signaling, and forwarding the transmission comprises: forwarding the transmission based on the forwarding configuration.
[0221] Aspect 5 is a method according to aspect 4, wherein the forwarding configuration includes an indication of a UL forwarding window or a DL forwarding window associated with the forwarding timing advance procedure, and wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission and forwarding the transmission.
[0222] Aspect 6 is a method according to Aspect 5, wherein the indication includes a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, and the start time is earlier than the second time.
[0223] Aspect 7 is a method according to aspect 6, wherein the forwarding advance timing procedure is based on a timing advance value associated with a DL transmission or a UL transmission from the first network entity to the third network entity, and wherein the start time is a third value earlier than the start time of the DL transmission or the UL transmission based on the timing advance value, and the end time is a fourth value later than the end of the DL transmission or the UL transmission.
[0224] Aspect 8 is a method according to Aspect 7, wherein the third value or the fourth value is associated with a channel type used for the transmission, a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission.
[0225] Aspect 9 is a method according to aspect 8, wherein the channel type is one of the following items: PUSCH, PUCCH, PDSCH, PDCCH, PRACH, SRS, SSB, CSI-RS or PRS.
[0226] Aspect 10 is a method according to aspects 7 to 9, the method further comprising: sending a request for the third value or the fourth value to the second network entity or the third network entity via the L1, L2 or L3 signaling.
[0227] Aspect 11 is a method according to any one of Aspects 4 to 10, wherein the forwarding configuration includes an indication for forwarding at least one sent instruction associated with a set of time and frequency resources without timing advance, wherein the indication is dynamic, semi-static, periodic or semi-persistent.
[0228] Aspect 12 is the method according to aspect 11, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
[0229] Aspect 13 is a method according to any one of aspects 4 to 12, wherein the forwarding configuration includes an indication of an instruction for forwarding at least one transmission associated with the PRACH without timing advance, wherein the indication is dynamic, semi-static, periodic or semi-persistent.
[0230] Aspect 14 is a method according to aspect 13, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
[0231] Aspect 15 is a method according to any one of aspects 1 to 14, the method further comprising: sending an indication indicating a value, accuracy or uncertainty range associated with the internal delay to the second network entity or the third network entity via L1, L2 or L3 signaling.
[0232] Aspect 16 is a method according to aspect 15, wherein the indication representing the uncertainty range is an index.
[0233] Aspect 17 is a method according to any one of Aspects 15 and 16, wherein the indication also indicates that the internal delay is based on whether the transmission is a UL transmission or a DL transmission, and wherein a first value of the one or more values of the internal delay is associated with the transmission being the UL transmission, and a second value of the one or more values of the internal delay is associated with the transmission being the DL transmission.
[0234] Aspect 18 is a method according to any one of aspects 15 to 17, wherein the indication further indicates that the one or more values of the internal delay are based on a direction or antenna set associated with the transmission.
[0235] Aspect 19 is a method according to any one of aspects 15 to 18, wherein the indication further indicates that the one or more values of the internal delay are based on a signal power associated with the reception of the transmission.
[0236] Aspect 20 is a method according to any one of Aspects 1 to 19, wherein the first network entity corresponds to a relay or at least one component of the relay, wherein the second network entity corresponds to a UE or at least one component of the UE, wherein the third network entity corresponds to a base station or one or more components of the base station, and wherein the forwarding timing advance procedure is a UL forwarding timing advance procedure.
[0237] Aspect 21 is a method according to any one of Aspects 1 to 19, wherein the first network entity corresponds to a relay or at least one component of the relay, wherein the third network entity corresponds to a UE or at least one component of the UE, wherein the second network entity corresponds to a base station or one or more components of the base station, and wherein the forwarding timing advance procedure is a DL forwarding timing advance procedure.
[0238] Aspect 22 is a method according to any one of aspects 1 to 21, wherein the internal delay is a delay of the first network entity, the delay taking into account propagation delay and processing delay associated with forwarding the transmission.
[0239] Aspect 23 is a method for wireless communication at a first network entity, the method comprising: providing a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or a third network entity and determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; and performing one of the following items: providing the transmission to the second network entity; or receiving the transmission from the second network entity.
[0240] Aspect 24 is a method according to aspect 23, wherein the forwarding configuration includes an indication of a UL forwarding window or a DL forwarding window, and wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission at the second network entity and forwarding the transmission from the second network entity.
[0241] Aspect 25 is a method according to Aspect 24, wherein the indication includes a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, and the start time is earlier than the second time.
[0242] Aspect 26 is a method according to any one of Aspects 23 to 25, wherein the forwarding configuration includes an indication for the second network entity to forward at least one sent instruction associated with a set of time and frequency resources without timing advance, wherein the indication is dynamic, semi-static, periodic or semi-persistent.
[0243] Aspect 27 is a method according to aspect 26, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
[0244] Aspect 28 is a method according to any one of aspects 23 to 25, wherein the forwarding configuration includes an indication of an instruction for forwarding at least one transmission associated with the PRACH without timing advance, wherein the indication is dynamic, semi-static, periodic or semi-persistent.
[0245] Aspect 29 is a method according to aspect 28, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
[0246] Aspect 30 is a method according to any one of aspects 23 to 29, the method also including: receiving an indication of one or more values, one or more accuracies, or one or more uncertainty ranges associated with the internal delay of the second network entity via L1, L2 or L3 signaling.
[0247] Aspect 31 is a method according to aspect 30, wherein the indication representing the one or more uncertainty ranges is an index.
[0248] Aspect 32 is a method according to any one of aspects 30 and 31, wherein the indication further indicates that the internal delay is based on whether the transmission is a UL transmission or a DL transmission, and wherein a first value of the values of the internal delay is associated with the transmission being the UL transmission, and a second value of the values of the internal delay is associated with the transmission being the DL transmission.
[0249] Aspect 33 is a method according to any one of aspects 30 to 32, wherein the indication further indicates that the value of the internal delay is based on a direction or antenna set associated with the transmission.
[0250] Aspect 34 is a method according to any one of aspects 30 to 33, wherein the indication further indicates that the value of the internal delay is based on a signal power associated with receiving the transmission.
[0251] Aspect 35 is a method according to any one of Aspects 23 to 34, wherein the first network entity corresponds to a base station or at least one component of the base station, wherein the second network entity corresponds to a relay or at least one component of the relay, and wherein the third network entity corresponds to a UE or at least one component of the UE.
[0252] Aspect 36 is a method according to any one of aspects 23 to 35, wherein the internal delay is a delay of the second network entity, the delay taking into account propagation delay and processing delay associated with forwarding the transmission.
[0253] Aspect 37 is an apparatus for wireless communication at a first network entity, the apparatus comprising: a memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to implement any one of aspects 1 to 22.
[0254] Aspect 38 is the apparatus of aspect 37, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.
[0255] Aspect 39 is an apparatus for wireless communication at a first network entity, the apparatus comprising: a memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to implement any one of aspects 23 to 36.
[0256] Aspect 40 is the apparatus of aspect 39, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.
[0257] Aspect 41 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 22.
[0258] Aspect 42 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 23 to 36.
[0259] Aspect 43 is a computer-readable medium (eg, non-transitory 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 22.
[0260] Aspect 44 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 23 to 36.
Claims
1. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: performing a forwarding timing advance procedure, wherein in order to perform the forwarding timing advance procedure, the at least one processor is configured to: determining a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, and wherein the transmission is destined for a third network entity; receiving the transmission from the second network entity at the first time; and The transmission is forwarded to the third network entity at a second time.
2. The first network entity of claim 1, wherein the forwarding timing advance procedure is based on a timing advance value associated with a downlink (DL) transmission or an uplink (UL) transmission from the first network entity to the third network entity.
3. The first network entity according to claim 2, wherein the forwarding timing advance information is equal to the timing advance value plus the internal delay.
4. The first network entity of claim 1 , wherein the at least one processor is configured to: A forwarding configuration is received from the second network entity or the third network entity via layer 1 (L1), layer 2 (L2) or layer 3 (L3) signaling, wherein in order to forward the transmission, the at least one processor is configured to forward the transmission based on the forwarding configuration.
5. The first network entity of claim 4, wherein the forwarding configuration comprises an indication of an uplink (UL) forwarding window or a downlink (DL) forwarding window associated with the forwarding timing advance procedure, and wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission and forwarding the transmission.
6. The first network entity of claim 5, wherein the indication comprises a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
7. The first network entity of claim 6, wherein the forward advance timing procedure is based on a timing advance value associated with a DL transmission or a UL transmission from the first network entity to the third network entity, and wherein the start time is earlier by a third value than a start time of the DL transmission or the UL transmission based on the timing advance value, and wherein the end time is later than an end of the DL transmission or the UL transmission by a fourth value.
8. The first network entity of claim 7, wherein the third value or the fourth value is associated with a channel type used for the transmission, a beam associated with receiving or forwarding the transmission, or a set of time or frequency resources associated with the transmission.
9. The first network entity according to claim 8, wherein the channel type is one of the following: Physical uplink shared channel (PUSCH); Physical Uplink Control Channel (PUCCH); Physical Downlink Shared Channel (PDSCH); Physical Downlink Control Channel (PDCCH); Physical Random Access Channel (PRACH); Sounding Reference Signal (SRS); Synchronization Signal Block (SSB); Channel State Information (CSI) Reference Signal (CSI-RS); or Or Positioning Reference Signal (PRS).
10. The first network entity of claim 7, wherein the at least one processor is configured to: A request for the third value or the fourth value is sent to the second network entity or the third network entity via the L1, L2 or L3 signaling.
11. The first network entity of claim 7, wherein the forwarding configuration comprises an indication for forwarding at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
12. The first network entity of claim 11, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
13. The first network entity of claim 7, wherein the forwarding configuration comprises an indication for forwarding at least one transmitted instruction associated with a physical random access channel (PRACH) without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
14. The first network entity of claim 13, wherein the timing advance corresponds to one of the timing advance value or the forwarded timing advance information.
15. The first network entity of claim 1 , wherein the at least one processor is configured to: An indication representing one or more values, one or more accuracies, or one or more uncertainty ranges associated with the internal delay is sent to the second network entity or the third network entity via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling.
16. The first network entity of claim 15, wherein the indication representative of the one or more uncertainty ranges is an index.
17. The first network entity of claim 15, wherein the indication further indicates that the internal delay is based on whether the transmission is an uplink (UL) transmission or a downlink (DL) transmission, and wherein a first value of the one or more values of the internal delay is associated with the transmission being the UL transmission, and a second value of the one or more values of the internal delay is associated with the transmission being the DL transmission.
18. The first network entity of claim 15, wherein the indication further indicates that the one or more values of the internal delay are based on a direction or a set of antennas associated with the transmission.
19. The first network entity of claim 15, wherein the indication further indicates that the one or more values of the internal delay are based on a signal power associated with a reception of the transmission.
20. The first network entity of claim 1, wherein the first network entity corresponds to a relay or at least one component of the relay, wherein the second network entity corresponds to a user equipment (UE) or at least one component of the UE, wherein the third network entity corresponds to a base station or one or more components of the base station, and wherein the forwarding timing advance procedure is an uplink (UL) forwarding timing advance procedure.
21. The first network entity of claim 1, wherein the first network entity corresponds to a relay or at least one component of the relay, wherein the third network entity corresponds to a user equipment (UE) or at least one component of the UE, wherein the second network entity corresponds to a base station or one or more components of the base station, and wherein the forwarding timing advance procedure is a downlink (DL) forwarding timing advance procedure.
22. The first network entity of claim 1, wherein the internal delay is a delay of the first network entity that takes into account propagation delay and processing delay associated with forwarding the transmission.
23. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: providing a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or a third network entity and to determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; as well as Do one of the following: providing the sending to the second network entity; or The transmission is received from the second network entity.
24. The first network entity of claim 23, wherein the forwarding configuration comprises an indication of an uplink (UL) forwarding window or a downlink (DL) forwarding window, and wherein the UL forwarding window or the DL forwarding window represents a time window configured for receiving the transmission at the second network entity and forwarding the transmission from the second network entity.
25. The first network entity of claim 24, wherein the indication comprises a first value or a first range associated with a start time of the UL forwarding window or the DL forwarding window and a second value or a second range associated with an end time of the UL forwarding window or the DL forwarding window, the start time being earlier than the second time.
26. The first network entity of claim 23, wherein the forwarding configuration comprises an indication for the second network entity to forward at least one transmitted instruction associated with a set of time and frequency resources without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
27. The first network entity of claim 23, wherein the forwarding configuration comprises an indication for forwarding at least one transmitted instruction associated with a physical random access channel (PRACH) without a timing advance, wherein the indication is dynamic, semi-static, periodic, or semi-persistent.
28. The first network entity according to claim 23, further comprising: An indication representing one or more values, one or more accuracies, or one or more uncertainty ranges associated with the internal delay of the second network entity is received via layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling.
29. A method of wireless communication performed by a first network entity, the method comprising: Execute the forwarding timing advance procedure, including: determining a first time for receiving a transmission from a second network entity based on forwarding timing advance information, wherein the forwarding timing advance information is based on an internal delay of the first network entity, wherein the transmission is destined for a third network entity; receiving the transmission from the second network entity at the first time; and The transmission is forwarded to the third network entity at a second time.
30. A method of wireless communication performed by a first network entity, the method comprising: providing a forwarding configuration to a second network entity, wherein the forwarding configuration is configured to enable the second network entity to determine a first time for receiving a transmission from the first network entity or a third network entity and to determine a second time for forwarding the transmission to the first network entity or the third network entity based on an internal delay of the second network entity; as well as Do one of the following: providing the sending to the second network entity; or The transmission is received from the second network entity.
