Signaling support for various timing cases in an IAB node

Abstract

An integrated access and backhaul (IAB) node receives a time difference parameter for over-the-air (OTA) synchronization in an IAB network from a parent IAB node, and adjusts the IAB node's transmission or reception for one of a plurality of types of IAB node alignment based on the time difference parameter.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Application No. 63 / 236,663, entitled "Signaling Support for Different Timing Cases in IAB Nodes," filed on August 24, 2021, and U.S. Non-Provisional Application No. 17 / 811,005, entitled "SIGNALING SUPPORT FOR DIFFERENT TIMING CASES IN IAB NODES," filed on July 6, 2022, the entireties of which are expressly incorporated by reference herein.

[0002] The present disclosure relates generally to communication systems, and more particularly to communications in integrated access and backhaul (IAB) networks. [Background technology]

[0003] introduction Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system 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.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide common protocols that allow various wireless devices to communicate at city, national, regional, or even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0005] SUMMARY OF THE DISCLOSURE The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. It is not intended to identify key or critical elements of all aspects, nor is it intended to delineate 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 the more detailed description that is presented later.

[0006] In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided in an integrated access and backhaul (IAB) node that receives a time difference parameter for over-the-air (OTA) synchronization in an IAB network from a parent IAB node and adjusts transmission or reception of the IAB node for one of a plurality of types of IAB node alignment based on the time difference parameter.

[0007] In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided in a parent IAB node for transmitting or receiving communications with an IAB node that is a child node of the parent IAB node, and transmitting a time difference parameter for over-the-air synchronization in an IAB network, the time difference parameter being applicable to one of a plurality of types of IAB node alignment.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of only a few of the various ways in which the principles of the various aspects may be employed and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a wireless communication system and an access network in accordance with various aspects of the present disclosure. [Figure 2A] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example of a DL channel in a subframe in accordance with various aspects of the present disclosure. [Figure 2C] FIG. 2 illustrates an example of a second frame according to various aspects of the present disclosure. [Figure 2D] FIG. 2 illustrates an example of a UL channel in a subframe in accordance with various aspects of the present disclosure. [Diagram 3] FIG. 2 illustrates an example of an IAB node and user equipment (UE) in a network in accordance with various aspects of the present disclosure. [Figure 4] FIG. 1 illustrates an example IAB network, in accordance with various aspects of the present disclosure. [Diagram 5]FIG. 1 illustrates an exemplary IAB network and its components, according to various aspects of the present disclosure. [Figure 6] FIG. 2 illustrates an example connection for an IAB network, according to various aspects of the present disclosure. [Figure 7A] 1 illustrates various examples of different types of timing alignment for IAB nodes in accordance with various aspects of the present disclosure. [Figure 7B] 1 illustrates various examples of different types of timing alignment for IAB nodes in accordance with various aspects of the present disclosure. [Figure 7C] 1 illustrates various examples of different types of timing alignment for IAB nodes in accordance with various aspects of the present disclosure. [Figure 8] 1 illustrates a timing diagram for communication with a parent IAB node and a child IAB node in accordance with various aspects of the present disclosure. [Figure 9] FIG. 11 is a communication flow diagram illustrating an example aspect of timing alignment based on a time difference parameter indicated by a parent IAB node, according to various aspects of the disclosure. [Figure 10] FIG. 11 is a communication flow diagram illustrating an example aspect of timing alignment based on a time difference parameter indicated by a parent IAB node, according to various aspects of the disclosure. [Figure 11] FIG. 11 is a communication flow diagram illustrating an example aspect of timing alignment based on a time difference parameter indicated by a parent IAB node, according to various aspects of the disclosure. [Figure 12] 1 is a flowchart of a method of wireless communication including timing adjustment based on a time difference parameter from a parent IAB node, in accordance with various aspects of the present disclosure. [Figure 13] 1 is a flowchart of a method of wireless communication including indicating a time difference parameter to a child IAB node, in accordance with various aspects of the present disclosure. [Figure 14] FIG. 1 illustrates an example of a hardware implementation of an apparatus employing a processing system that can be configured to transmit and / or receive a time difference parameter associated with one of multiple types of timing alignment. [Figure 15] FIG. 1 shows a diagram illustrating an exemplary split base station architecture. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The method includes: an IAB node that performs a match between multiple match types, e.g., delta and / or N delta For example, a time difference parameter for over-the-air (OTA) synchronization in an IAB network may be received from a parent IAB node, and the IAB node receiving the time difference parameter may adjust the transmission or reception of the IAB node with respect to one of a plurality of types of alignment in the IAB node and / or parent IAB node based on the time difference parameter. The IAB node may apply the time difference parameter with respect to one of a plurality of potential types of alignment in the IAB. The first type of alignment (e.g., what may be referred to as case 1 alignment) may include downlink transmission timing alignment across each IAB node of the IAB network. The second type of alignment (e.g., what may be referred to as case 6 alignment) may be between uplink transmission at an IAB mobile termination (IAB-MT) of a child IAB node and downlink transmission at an IAB distributed unit (IAB-DU) of the child IAB node. A third type of matching (e.g., what may be referred to as case 7 matching) may be between downlink reception at the IAB-MT of a child IAB node and uplink reception at the IAB-DU of the child IAB node.

[0011] The Detailed Description of the Invention described below in conjunction with the accompanying drawings illustrates various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The Detailed Description of the Invention includes specific details intended to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0012] Certain aspects of a telecommunications system are presented with reference to various apparatus and methods that are described in the Detailed Description below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0013] As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphic processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functionality described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0014] Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, 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 types of computer-readable media, or any other medium that can be accessed by a computer and that can be used to store computer-executable code in the form of instructions or data structures.

[0015] Although aspects, implementations, and / or use cases are described in this application by way of example for some embodiments, additional or different aspects, implementations, and / or use cases may occur in many different configurations and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, the aspects, implementations, and / or use cases may occur via integrated chip implementations and other non-modular component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some embodiments may or may not be specifically targeted to a use case or application, but a wide variety of combination applicability of the described embodiments may occur. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, summers / analog summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or separated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0016] 1 illustrates an embodiment of a wireless communication system and access network 100. The wireless communication system and access network 100 may include an integrated access and backhaul (IAB) network including multiple cells that communicate with each other to provide an access network and a backhaul network to a core network, such as a core network 190 or an evolved packet core (EPC) 160. The core network 190 may be a 5G core (5GC), which is a core network supporting new radio (NR) communications, or another type of core network. The IAB network may include one or more IAB nodes 103. The IAB nodes may exchange communications with other IAB nodes 103, base stations 102 or 180, and / or UEs 104.

[0017] In some aspects, the IAB node 103 may include a time delta component 198 and / or a time delta indication component 199. The time delta component 198 may be configured to receive a time difference parameter for over-the-air (OTA) synchronization in the IAB network from a parent IAB node and adjust the transmission or reception of the IAB node for one of a plurality of types of alignment in the IAB node and / or parent IAB node based on the time difference parameter. The time delta indication component may be configured to transmit, for example, to a child IAB node, a time difference parameter for OTA synchronization in the IAB network, the time difference parameter being applicable to one of a plurality of types of alignment in the child IAB node and / or IAB node. The first type of alignment (e.g., what may be referred to as case 1 alignment) may include downlink transmission timing alignment across each IAB node of the IAB network. A second type of alignment (e.g., what may be referred to as case 6 alignment) may be between an uplink transmission at an IAB mobile termination (IAB-MT) of a child IAB node and a downlink transmission at an IAB distributed unit (IAB-DU) of the child IAB node. A third type of alignment (e.g., what may be referred to as case 7 alignment) may be between a downlink reception at an IAB-MT of a child IAB node and an uplink reception at an IAB-DU of the child IAB node. In some aspects, an IAB node may include both a time delta component 198 and / or a time delta indication component 199 because an IAB node may perform some aspects of wireless communication as a parent IAB node and other aspects as a child IAB node, e.g., an IAB node may have a parent IAB node and a child IAB node. Although the examples in the following description may focus on 5G NR, the concepts described herein may also be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0018] A wireless communication system is also referred to as a wireless wide area network (WWAN). The base station 102 shown in FIG. 1 may support macro cells (high power cellular base stations) and / or small cells (low power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0019] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 over a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 over a second backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions: forwarding of user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and distribution of alert messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184 (e.g., an Xn interface), and the third backhaul link 134 can be wired or wireless.

[0020] In some aspects, the base station 102 or 180 may be referred to as a RAN and may include aggregated or separated components. As an example of a separated RAN, the base station may include a central unit (CU) 111, one or more distributed units (DUs) 105, and / or one or more remote units (RUs) 109, as shown in FIG. 1. The RAN may be separated by a division between the RU 109 and the aggregated CU / DU. The RAN may be separated by a division between the CU 111, the DU 105, and the RU 109. The RAN may be separated by a division between the CU 111 and the aggregated DU / RU. The CU 111 and one or more DUs 105 may be connected via an F1 interface. The DUs 105 and the RUs 109 may be connected via a fronthaul interface. The connection between the CU 111 and the DUs 105 may be referred to as a midhaul, and the connection between the DUs 105 and the RUs 109 may be referred to as a fronthaul. The connection between the CU 111 and the core network may be referred to as a backhaul. The RAN may be based on a functional division between various components of the RAN, for example, between the CU 111, the DU 105, or the RU 109. The CU 111 may be configured to perform processing of one or more aspects of a wireless communication protocol, for example, one or more layers of a protocol stack, and the DU may be configured to process other aspects of the wireless communication protocol, for example, other layers of the protocol stack. In various implementations, the division between layers processed by the CU 111 and layers processed by the DU may occur at various layers of the protocol stack. As one non-limiting example, the DU 105 may provide logical nodes for hosting at least a portion of a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer based on the functional division. The RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing.The CU 111 may host higher layer functions above the RLC layer, such as, for example, a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, etc. In other implementations, the division between layer functions provided by the CU, DU, or RU may be different.

[0021] An access network may include one or more integrated access and backhaul (IAB) nodes 103 that exchange wireless communications with UEs 104 or other IAB nodes 103 to provide access and backhaul to a core network, for example as described in more detail in connection with Figures 4-6. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. An IAB donor may be a base station 102 or 180 that provides access to a core network 190 or an EPC 160 and / or control to one or more IAB nodes 103. An IAB donor may include a CU 111 and a DU 105. An IAB node 103 may include a DU 105 and a mobile termination (MT). The DU 105 of an IAB node 103 may act as a parent node, and the MT may act as a child node.

[0022] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may provide service to restricted groups known as closed subscriber groups (CSGs). A communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to YMHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to YxMHz (x component carriers) in total, used for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL). The component carriers 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 (P-cell), and the secondary component carrier may be referred to as a secondary cell (S-cell).

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

[0024] Some examples of sidelink communications include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communications device to a road infrastructure node such as a roadside unit (RSU)), vehicle-to-network (V2N) (e.g., from a vehicle-based communications device to one or more network nodes such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-anything (C-V2X), and / or a combination thereof, and / or a vehicle-based communications device capable of communicating from and / or with other devices, which may be collectively referred to as vehicle-to-anything (V2X) communications. Sidelink communications may be based on V2X or other D2D communications such as proximity services (ProSe). In addition to UEs, sidelink communications may also be transmitted and received by other transmitting / receiving devices such as a roadside unit (RSU) 107.

[0025] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STA 152 / AP 150 may perform clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0026] The small cell 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR to use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. By employing NR in the unlicensed frequency spectrum, the small cell 102' may enhance coverage to and / or increase capacity of the access network.

[0027] The electromagnetic spectrum is often subdivided into various classes, 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 higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunications Union (ITU).

[0028] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands within FR3 may inherit the characteristics of FR1 and / or FR2, and therefore may effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is within the EHF band.

[0029] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, frequencies that may be in the range of FR1, or frequencies that may include mid-band frequencies. Further, it should be understood that unless otherwise specified, terms such as "mmWave," as used herein, may broadly refer to frequencies that may be in the range of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or frequencies that may be in the EHF band.

[0030] The base station 102, whether a small cell 102' or a large cell (e.g., macro base station), may include and / or may be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate in the conventional sub-6 GHz spectrum, mmWave frequencies, and / or sub-mmWave frequencies to communicate with the UE 104. If the gNB 180 operates in mmWave or sub-mmWave frequencies, the gNB 180 may be referred to as a mmWave base station. Extremely High Frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band may be referred to as mmWave. Sub-mmWave may go down to a frequency of 3 GHz with a wavelength of 100 millimeters. The Super High Frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter wave. Communications using mmWave / quasi-mmWave radio frequency (RF) bands (e.g., 3 GHz to 300 GHz) have extremely high path losses and short distances. The mmWave base station 180 can utilize beamforming 182 with the UE 104 to compensate for the extremely high path losses and short distances. The base station 180 and the UE 104 can each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0031] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0032] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides allocation of IP addresses for the UE, as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP services 176 may include Internet, Intranet, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for provisioning and delivery of MBMS user services. The BM-SC 170 may act as an entry point for MBMS transmissions of content providers, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and collection of eMBMS related charging information.

[0033] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with an integrated data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, intranets, IP multimedia subsystem (IMS), packet switched (PS) streaming (PSS) services, and / or other IP services.

[0034] A base station may include and / or may be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of the UE 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UEs 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, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration. One or more of these devices may collectively access the network and / or may individually access the network.

[0035] The deployment of communication systems, such as 5G New Radio (NR) systems, can be configured in multiple ways using various components or parts. In a 5G NR system, or network, a network node, network entity, mobility element of the network, Radio Access Network (RAN) node, core network node, network element, or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or separated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a separated base station.

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

[0037] The operation of base station types or network design can take into account the aggregated nature of base station functionality. For example, a separated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as the network configuration supported by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Separation can include distributing functionality across two or more units in various physical locations as well as virtually distributing functionality for at least one unit, which can allow flexibility in network design. Various units of a separated base station or separated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0038] FIG. 15 shows a diagram illustrating an example split base station 1500 architecture. The split base station 1500 architecture may include one or more central units (CUs) 1510 that may communicate directly with a core network 1520 via a backhaul link or indirectly with the core network 1520 through one or more split base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 1525 via an E2 link or a non-real-time (non-RT) RIC 1515 associated with a service management and orchestration (SMO) framework 1505, or both). The CUs 1510 may communicate with one or more distributed units (DUs) 1530 via respective midhaul links, such as an F1 interface. The DUs 1530 may communicate with one or more radio units (RUs) 1540 via respective fronthaul links. The RUs 1540 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 1540 simultaneously.

[0039] Each of the units, i.e., CU 1510, DU 1530, RU 1540, quasi-RT RIC 1525, non-RT RIC 1515, and SMO framework 1505, 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 interfaces of the units, 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 or transmit signals via a wired transmission medium to one or more of the other units. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or transmit signals via a wireless transmission medium to one or more of the other units.

[0040] In some aspects, the CU 1510 can host one or more higher layer control functions. Such control functions can include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1510. The CU 1510 can 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 implementations, the CU 1510 can be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units can bidirectionally communicate with the CU-CP units over an interface such as an E1 interface when implemented in an O-RAN configuration. The CU 1510 can be implemented to communicate with the DU 1530 as needed for network control and signaling.

[0041] The DU 1530 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 1540. In some aspects, the DU 1530 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper 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 division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 1530 may further host one or more lower PHY layers. Each layer (or module) may implement an interface configured to communicate signals with other layers (and modules) hosted by the DU 1530 or to communicate signals with a control function hosted by the CU 1510.

[0042] The lower layer functionality may be implemented by one or more RUs 1540. In some deployments, the RUs 1540 controlled by the DUs 1530 may correspond to logical nodes hosting RF processing functions, or lower 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 a functional division, such as a lower layer functional division. In such an architecture, the RUs 1540 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 1540 may be controlled by the corresponding DUs 1530. In some scenarios, this configuration may enable the DUs 1530 and CUs 1510 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0043] The SMO framework 1505 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1505 can be configured to support deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 1505 can be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 1590) to perform life cycle management of the network elements (such as for instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, the CU 1510, the DU 1530, the RU 1540, and the quasi-RT RIC 1525. In some implementations, the SMO framework 1505 can communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1511, via an O1 interface. Moreover, in some implementations, the SMO framework 1505 can communicate directly with one or more RUs 1540 over an O1 interface. The SMO framework 1505 may also include a non-RT RIC 1515 configured to support the functionality of the SMO framework 1505.

[0044] The non-RT RIC 1515 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / functions in the quasi-RT RIC 1525. The non-RT RIC 1515 can be coupled to or in communication with the quasi-RT RIC 1525 (e.g., via an A1 interface). The quasi-RT RIC 1525 can be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and action via interfaces (e.g., via an E2 interface) that connect one or more CUs 1510, one or more DUs 1530, or both, and the O-eNB to the quasi-RT RIC 1525.

[0045] In some implementations, the non-RT RIC 1515 can receive parameters or external enrichment information from an external server to generate an AI / ML model for deployment in the quasi-RT RIC 1525. Such information can be utilized by the quasi-RT RIC 1525 and can be received in the SMO framework 1505 or the non-RT RIC 1515 from a non-network data source or from a network function. In some embodiments, the non-RT RIC 1515 or the quasi-RT RIC 1525 can be configured to adjust the behavior or performance of the RAN. For example, the non-RT RIC 1515 can employ the AI / ML model to monitor long-term trends and patterns regarding performance and take corrective action through the SMO framework 1505 (e.g., reconfiguration via O1) or through the creation of a RAN management policy (e.g., A1 policy).

[0046] FIG. 2A is a diagram 200 illustrating an example of a first subframe in a 5G / NR frame structure. FIG. 2B is a diagram 230 illustrating an example of a DL channel in a 5G / NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe in a 5G / NR frame structure. FIG. 2D is a diagram 280 illustrating an example of a UL channel in a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within that set of subcarriers are dedicated to either DL or UL, or time division duplex (TDD) where, for a particular set of subcarriers (carrier system bandwidth), subframes within that set of subcarriers are dedicated to both DL and UL. In the example provided by Figures 2A, 2C, the 5G / NR frame structure is assumed to be TDD, subframe 4 is configured with (mostly DL) slot format 28, where D is DL, U is UL, and X is flexible for use between DL / UL, and subframe 3 is configured with (mostly UL) slot format 34. Although subframes 3 and 4 are shown with slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2-61 include a mix of DL symbols, UL symbols, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (either dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). Note that the following description also applies to 5G / NR frame structures that are TDD.

[0047] 2A-2D illustrate a frame structure, and 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 (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (also called Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power limited scenarios, i.e., limited to single stream transmission). The number of slots in a subframe is based on the CP and a mathematical logic, which defines the Subcarrier Spacing (SCS) and effectively the symbol length / duration, which is equal to 1 / SCS.

[0048] [Table 1]

[0049] For normal CP (14 symbols / slot), the different number logics μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, number logic 2 allows 4 slots per subframe. Thus, for normal CP and number logic μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ*15kHz, where μ is a number logic 0-4. Therefore, number logic μ=0 has a subcarrier spacing of 15kHz and number logic μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and number logic μ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is about 16.67μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see Figure 2B), which are frequency division multiplexed. Each BWP may have a specific number logic and CP (normal or extended).

[0050] A resource grid can be used to represent the frame structure. Each time slot contains a resource block (RB), also called a physical RB (PRB), that spans 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0052] FIG. 2B illustrates an example of various DL channels in a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes 6 RE groups (REGs), and each REG includes 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in one BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the CORESET, a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be placed at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the timing of the subframe / symbol and the physical layer identity. A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame. Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A physical broadcast channel (PBCH), which carries a master information block (MIB), may 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 transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0053] As shown in FIG. 2C , some of the REs carry DM-RS (depicted as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0054] 2D illustrates one embodiment of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), 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 also be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0055] 3 is a block diagram of an IAB node 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 or the core network 190 may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and / or Layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer and may run if the IAB node is a donor IAB node. 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 broadcast of system information (e.g., MIBs, SIBs), 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 functionality; RLC layer functionality associated with forwarding of higher layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0056] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers and multiplexed with reference signals (e.g., pilots) in the time and / or frequency domains, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate an RF carrier with the respective spatial stream for transmission.

[0057] At the UE 350, each receiver 354Rx receives a signal through its respective 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 streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). This frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the IAB node 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the IAB node 310 on the physical channel. The data and control signals are then provided to a controller / processor 359, which implements Layer 3 and Layer 2 functionality.

[0058] The controller / processor 359 can 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 transport and logical channel demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0059] Similar to the functionality described in connection with downlink transmissions by the IAB node 310, the controller / processor 359 provides RRC layer functionality associated with obtaining system information (e.g., MIBs, SIBs), RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding of higher layer PDUs, error correction via 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 of logical channels to transport channels, multiplexing of MAC SDUs onto the TB, demultiplexing of MAC SDUs from the TB, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0060] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the IAB node 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters TX 354. Each transmitter 354Tx can modulate an RF carrier with a respective spatial stream for transmission.

[0061] The UL transmissions are processed at the IAB node 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver 318Rx receives the signal through its respective antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0062] 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 transport and logical channel demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160 or the core network 190 via a donor IAB node, for example, if the IAB node is not a donor IAB node. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0063] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects related to the time delta component 198 and / or the time delta instruction component 199, for example, as described in connection with FIG. 1.

[0064] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects related to the time delta component 198 and / or the time delta instruction component 199, for example, as described in connection with FIG. 1.

[0065] FIG. 4 illustrates an IAB network 400. The IAB network provides access network functionality between access nodes (ANs) and other ANs / UEs, and backhaul network functionality between ANs. The ANs include IAB donors, which have a wired connection to a core network, and IAB nodes, which operate wirelessly and relay traffic to and from the IAB donors through one or more AN hops. The IAB ANs share resources between access and backhaul; that is, resources used for access communication between the ANs and the ANs / UEs are also used for backhaul communication between ANs.

[0066] The IAB network 400 may include an anchor node 410 (which may be referred to herein as an “IAB donor”) and an access node 420 (which may be referred to herein as an “IAB node”). The IAB donor 410 may be a base station, such as a gNB or an eNB, and may perform functions for controlling the IAB network 400. The IAB node 420 may include an L2 relay node, etc. Collectively, the IAB donor 410 and the IAB node 420 share resources to provide an access network and a backhaul network to the core network 490. For example, resources may be shared between access links and backhaul links in the IAB network.

[0067] The UE 430 interfaces with the IAB node 420 or the IAB donor 410 through an access link 470. The IAB nodes 420 communicate with each other and with the IAB donor 410 through a backhaul link 460. The IAB donor 410 is connected to the core network 490 through a wired backhaul link 450. The UE 430 communicates with the core network by relaying messages to the IAB network 400 through their respective access links 470, which can then communicate to the core network through the wired backhaul link 450 by relaying the messages to the IAB donor 410 through the backhaul link 460. Similarly, the core network can communicate with the UE 430 by sending messages to the IAB donor 410 through the wired backhaul link 450. The IAB donor 410 sends a message through the IAB network 400 via a backhaul link 460 to an IAB node 420 connected to the UE 430, and the IAB node 420 transmits the message to the UE 430 via an access link 470.

[0068] For example, each IAB node, including the IAB donor 410 and each IAB node 420, may use a PCI value. The PCI value may serve as an identifier for that IAB donor 410 or IAB node 420. The PCI value may be used to determine a scrambling sequence to be applied to a physical signal and / or channel transmitted by a particular IAB node. For example, the PSS and / or SSS transmitted by each IAB donor 410 or IAB node 420 may be scrambled using a scrambling sequence based on the PCI used by the respective IAB node.

[0069] 5 shows a second diagram illustrating an IAB network 500 and its components. The IAB network 500 includes an IAB donor 510 and IAB nodes 520a and 520b. These IAB nodes as well as the IAB donor can provide wireless access links to UEs 530a, 530b, and 530c.

[0070] The IAB donor 510 may be considered as the root node of the tree structure of the IAB network 500. The IAB donor node 510 may be connected to the core network 590 via a wired connection 591. The wired connection may include, for example, wired fiber. The IAB donor node 510 may provide a connection to one or more IAB nodes 520a. Each of the IAB nodes 520a may be referred to as a child node of the IAB donor node 510. The IAB donor node 510 may also provide a connection to one or more UEs 530a, which may be referred to as child UEs of the IAB donor 510. The IAB donor 510 may be connected to its child IAB node 520a via a backhaul link 560 and to a child UE 530a via an access link 570. The IAB node 520a, which is a child node of the IAB node 510, may also have an IAB node 520b and / or a UE 530b as a child. For example, IAB node 520b may further connect to child nodes and / or child UEs. Figure 5 shows that IAB node 520b each provides an access link to UE 530c.

[0071] The IAB donor 510 may include a central unit (CU) and a distributed unit (DU). The central unit CU may provide control for the IAB nodes 520a, 520b in the IAB network 500. For example, the CU may control the IAB network 500 through configuration. The CU may perform RRC / PDCP layer functions. The IAB donor 510 further includes a DU that performs scheduling. For example, the DU may schedule resources for communication by the child IAB nodes 520a and / or UEs 530a of the IAB donor 510. The DU performs radio link control (RLC) functions, medium access control (MAC) functions, and physical (PHY) layer functions.

[0072] IAB nodes 520a, 520b may include a mobile termination (MT) and a DU. The IAB nodes are L2 relay nodes. The MT of IAB node 520a may act as a scheduled node, which is scheduled by the DU of a parent node, e.g., IAB donor 510, as well as the UE 530a. The MT of IAB node 520b may act as a scheduled node of the parent node 520a. The DU may schedule the child IAB node 520b of IAB node 520a, as well as the UE 530b. This is because an IAB node may provide a connection to an IAB node, which provides a connection to another IAB node. The pattern of a parent IAB node with a DU scheduling a child IAB node / child UE may continue for more connections as shown in FIG. 5.

[0073] FIG. 6 is a diagram 600 illustrating RLC channels in an IAB network. As discussed above, the IAB network provides both access network functionality and backhaul network functionality. The IAB network includes an IAB donor having a CU 602 and a DU 604. For each access network functionality, the IAB ANs 606a, 606b, and 606c can communicate with other UEs 608a and 608b and / or MTs of other IAB ANs through access RLC channels. For each backhaul network functionality, the IAB ANs 606a, 606b, and 606c can route traffic to other ANs (e.g., 606a, 606b, and 606c) through backhaul RLC channels. The access RLC channels include UE-to-DU / DU-to-UE channels carrying PDCP for RRC or Data Radio Bearer (DRB) and MT-to-DU / DU-to-MT channels carrying PDCP for RRC (or DRB). The backhaul RLC channels include MT-to-DU / DU-to-MT channels carrying Backhaul Adaptation Protocol (BAP) messages for backhauling access traffic.

[0074] 7A, 7B, and 7C illustrate example aspects of various timing modes for IAB communications. FIG. 7A illustrates a timing example 700 of downlink transmission timing alignment across IAB node 702 and IAB node 704. In some aspects, downlink transmission timing can be aligned across each IAB node in an IAB network. Downlink timing transmission alignment may be referred to as "Case 1" alignment or may be otherwise named. FIG. 7A illustrates that a DL transmission 708 by a DU of IAB node 702 is aligned in time with a DL transmission 706 from a DU of IAB node 704. An uplink timing adjustment framework may be applied in which a child IAB node (e.g., IAB node 704) receives an uplink timing adjustment from a parent IAB node (e.g., IAB node 702) to apply to uplink transmissions to the parent IAB node. 7B and 7C show time diagrams 725 and 750, respectively, illustrating aspects of additional timing modes that may be used, for example, to provide or improve duplex capability between an IAB node's IAB-MT and IAB DU. These additional timing modes may provide improved timing alignment of an IAB node's MT and DU for spatial division multiplexing, for example, when an IAB node performs IAB-MT downlink reception in one direction and IAB-DU uplink reception in another direction, and / or IAB-MT uplink transmission in one direction and IAB-DU downlink reception in another direction, simultaneously, for example, with at least partial overlap in time and / or frequency.

[0075] FIG. 7B illustrates an example time diagram 725 showing a mode or type of timing alignment that aligns an uplink transmission timing of an IAB-MT of an IAB node (e.g., IAB node 704) with a downlink transmission timing of an IAB-DU of the IAB node, for example, to facilitate simultaneous (e.g., at least partially overlapping in time) IAB-MT transmissions (e.g., UL transmissions 710) and IAB-DU transmissions (e.g., DL transmissions 706) at an IAB node (e.g., IAB node 704). The mode of alignment in FIG. 7B involving transmission alignment between the MT and DU of an IAB node may be referred to as "Case 6" alignment or may be otherwise named. This timing alignment may further include downlink transmission timing alignment (e.g., Case 1 alignment) across IAB nodes as shown in FIG. 7B and described in connection with FIG. 7A.

[0076] FIG. 7C illustrates an example time diagram 750 showing a mode or type of timing alignment that aligns the downlink receive timing of an IAB-MT of an IAB node (e.g., IAB node 704) with the uplink receive timing of an IAB-DU of that IAB node, e.g., the timing alignment facilitates simultaneous (e.g., at least partially overlapping in time) reception by the IAB-MT (e.g., DL receive 716) and reception by the IAB-DU (e.g., UL receive 714) at the IAB node (e.g., IAB node 704). The mode of alignment in FIG. 7C involving receive alignment between the MT and DU of an IAB node may be referred to as "Case 7" alignment or may be otherwise named. This timing alignment may further include downlink transmit timing alignment (e.g., Case 1 alignment) across IAB nodes as illustrated in FIG. 7C and described in connection with FIG. 7A.

[0077] For an alignment mode that aligns IAB node MT and DU transmissions (e.g., case 6), the timing at a given IAB node may include an IAB-MT transmit timing that is set by the IAB node to the timing obtained for that node's downlink transmissions. For an alignment mode that aligns IAB node MT and DU receptions (e.g., case 7), the timing at a parent IAB node (as opposed to a given IAB node, e.g., for a transmit alignment mode) may include an IAB-MT transmit timing that is obtained based on a timing advance loop, plus an offset from the parent IAB node. Aspects presented herein provide timing alignment that also supports OTA synchronization between IAB nodes.

[0078] OTA synchronization provides a mechanism for an IAB node to set its downlink transmission timing based on OTA signals received from one or more parent IAB nodes. OTA synchronization allows IAB nodes of an IAB network to synchronize with each other separately from an independent synchronization source, such as a Global Navigation Satellite Positioning System (GNSS), to provide DL transmission alignment across IAB nodes as described in connection with FIG. 7A. OTA synchronization provides timing advance (TA) control for uplink transmissions and an additional offset (T) indicated by the parent IAB node. delta ) The parent IAB node is based on TA and T delta may be indicated within the MAC-CE to a child IAB node, for example to an MT of the child IAB node.

[0079] 8 illustrates an example time diagram 800 showing the timing difference between uplink transmission at a child IAB node 804 and uplink reception at the parent IAB node relative to the downlink transmission timing at the parent IAB node. The difference between the uplink reception and the downlink transmission corresponds to delta (Δ). Because the parent IAB node 802 and the child IAB node 804 operate with timing alignment between the downlink transmissions from the DUs of each IAB node, the transmission time is TxD =Tx P D where the transmission time of the DU of the IAB node 804 is Tx D and the transmission time of the DU of the parent IAB node is Tx P D The timing advance may correspond to TA=2Tp+Δ, and Δ=TA-2Tp, where Tp corresponds to the propagation time between the parent IAB node 802 and the child IAB node 804, as shown in terms of the difference between the time that DL TX 806 ends and the time that the receive DL RX 808 ends at the IAB node 804 for the corresponding transmission from its parent IAB node 802. The same propagation time is shown between the end of an uplink transmission 810 from the IAB node 804 and the end of the receive 812 of the corresponding uplink transmission at the parent IAB node 802. In this example, Tx D =Rx D -Tp=Rx D -(TA-Δ) / 2, where Rx D corresponds to downlink reception at the DU of the IAB node 804. Similarly, Tp=TA / 2+T delta Therefore, T delta =-Δ / 2=(Rx P U -Tx P D ) / 2, where Rx P U corresponds to the uplink receive time (e.g., 812) at the parent IAB node 802.

[0080] Similarly, the IAB node receives the timing delta MAC CE from the serving cell with the exponent T delta If provided, the IAB node shall TA / 2+N delta +T delta '·G step )·T c But, N TA / 2+N delta +T delta G stepIf N > 0, it can be assumed that it is the time difference between the DU transmission of the signal from the serving cell and the reception of the signal by the IAB-MT. TA N can be obtained in the same manner as for UEs in a TAG that includes a serving cell. delta and G step can be determined as follows: If the serving cell providing the timing delta MAC CE operates in FR1, N delta =-70528 and G step =64. If the serving cell providing the timing delta MAC CE operates in FR2, then N delta =-17664 and G step =32.

[0081] IAB nodes can use this time difference to determine DU transmission times.

[0082] If the IAB node is operating based on the transmission timing alignment between the MT and DU of the IAB node (e.g., case 6), e.g., as described in connection with FIG. 7B, the IAB-MT sets its own uplink transmission timing to be aligned with the downlink transmission timing of the DU of the IAB node (e.g., the one that is co-located with the MT of the IAB node, which may be referred to as a co-located DU). In this embodiment, there is no uplink timing advance because the parent IAB node does not control the uplink transmission timing of the child IAB-MT and does not send TA commands. In the absence of closed-loop feedback in TA commands from the parent IAB node, the child IAB node cannot reliably synchronize the downlink transmission timing of its IAB-DU (e.g., as described in connection with FIG. 7A, the downlink transmission timing is synchronized for all DUs in the IAB network), and the synchronization of the IAB node with other IAB nodes may experience drift.

[0083] In some aspects, the IAB nodedelta 7B, etc., in conjunction with transmit timing alignment at the IAB nodes (e.g., FIG. 7B, etc.) and / or receive timing alignment at the IAB nodes (e.g., FIG. 7C, etc.) to assist in OTA synchronization. delta is a function of and captures the offset (e.g., delta or difference) between the uplink receive timing and the downlink transmit timing at the parent node. Because the IAB node operates in a mode with transmit timing alignment at the IAB node (e.g., case 6, or alignment as described in FIG. 7B), the parent IAB node can track the receive timing from the IAB node and its offset with respect to the parent IAB node's downlink transmit timing. This offset may be equal to the one-way propagation delay from the IAB node to the parent IAB node (because, for example, the IAB node's uplink transmit timing in case 6 is the same as its downlink transmit timing, as shown with respect to 710 and 706 in FIG. 7B, and is also aligned with the parent IAB node's downlink transmit timing based on its downlink transmit timing, as shown with 706 and 708 in FIGS. 7A and 7B). The parent IAB node may, for example, update the timing offset between DL transmission and UL reception (based on UL reception of a signal from a child IAB node) by updating the updated T delta The child IAB node can then send the updated T delta The value may be received to adjust its downlink transmission timing to account for possible drift in the synchronization of parent and child IAB nodes.

[0084] In some aspects, an IAB node may change between timing alignment modes, e.g., between downlink transmission alignment across DUs of an IAB network (e.g., case 1), and transmit timing alignment at a given IAB node (e.g., case 6) and / or receive timing alignment at an IAB node (e.g., case 7). Because an IAB node may change between at least these three different timing alignment modes, and possibly other timing alignment modes, the timing alignment mode may be changed to accommodate the timing alignment from a parent IAB node. delta The indication and / or interpretation of values ​​may vary.

[0085] As an example, if the IAB-MT follows downlink transmission timing alignment between DUs (e.g., case 1 alignment) without transmission or reception alignment at the IAB nodes, the IAB node's uplink signal will arrive at a first time reference with a first offset relative to the parent node's downlink transmission timing. This first offset is configured or determined by the parent IAB node, e.g., based on the parent IAB node's implementation choice. In contrast, if the IAB-MT operates based on transmission timing alignment at a given IAB node (e.g., case 6) and chooses to align its own uplink transmission timing with its downlink transmission timing, the IAB node's uplink signal will arrive at a second time reference with a second offset relative to the parent IAB node's downlink transmission timing. This second offset is, for example, a function of the one-way propagation delay between the IAB node and the parent node. If an IAB node operates based on receive timing alignment at the IAB node (e.g., case 7) and the node's IAB-MT transmit timing is obtained from the parent IAB node through a TA that instructs the IAB-MT to adjust its uplink transmit timing, then the IAB node's uplink signal will arrive at the parent node at a third time with a third offset relative to the parent IAB node's downlink transmit timing, the third offset being a function of the one-way propagation delay between the parent IAB node and its own parent.

[0086] Aspects presented herein enable an IAB node to apply or maintain OTA synchronization when the IAB node applies one of several different types of timing alignment, such as Case 1, Case 6, or Case 7.

[0087] In some aspects, for a mode with transmit timing alignment at the child IAB node (e.g., case 6) and / or a mode with receive timing alignment at the child IAB node (e.g., case 7), the T delta The IAB node may not have a T indication from its parent IAB node. delta If a child IAB node receives a T delta It can be determined that T is associated with downlink transmission timing across DUs (e.g., case 1) and corresponds to the first offset in the above example. The IAB node may determine that T is associated with downlink transmission timing across DUs (e.g., case 2) and corresponds to the first offset in the above example. The IAB node may determine that T is associated with downlink transmission timing across DUs (e.g., case 3) and corresponds to the first offset in the above example. The IAB node may determine that T is associated with downlink transmission timing across DUs (e.g., case 4) and corresponds to the first offset in the above example. delta can be applied.

[0088] 9 illustrates an example communication flow 900 between an IAB node 902 and a parent IAB node 904. At 906, the IAB node 902 operates based on one of a number of different timing alignment modes. For example, the IAB node 902 can operate based on any of case 1 timing alignment of downlink transmissions between DUs (e.g., FIG. 7A ), case 6 timing alignment of transmissions at the IAB node (e.g., FIG. 7B ), and / or case 7 timing alignment of receptions at the IAB node (e.g., FIG. 7C ). At 908, the IAB node 902 receives a time difference parameter T from the parent IAB node 904. delta The IAB node 902 receives T deltais applicable to the timing alignment of downlink transmissions between DUs in case 1. In 912, the IAB node 902 determines T for the timing alignment of case 1 to adjust the downlink transmission timing of the DUs of the IAB node to align with the DUs of the parent IAB node 904. delta The IAB node 902 then applies T delta In a further aspect, the IAB node can avoid drift and perform OTA synchronization if the IAB node is configured to operate based on Case 1 timing alignment for a frequent set of resources that can provide the IAB node with feedback from a parent IAB node to set and / or govern the timing of the IAB node. As an example, the IAB node can be configured to operate based on Case 1 timing at least every 100 ms. In other examples, the IAB node can be configured to operate based on Case 1 timing at a frequency less than 100 ms or at a longer frequency, such as every 200 ms, 300 ms, 400 ms, 500 ms, 600 ms, or 640 ms. As an example, the frequency can be associated with a length of several hundred ms.

[0089] In some aspects, the IAB node's IAB-MT transmission timing can be obtained from a TA command from a parent IAB node plus an offset from the parent node. An IAB node operating with timing alignment according to Case 7 can obtain the T delta (For application to timing alignment in case 7) = T delta (associated with the match in case 1) plus the offset shown.

[0090] In some embodiments, T deltacan be denoted for use in various types of timing alignment in IAB nodes. The parent IAB node is denoted T delta A child IAB node may be provided with information indicating the association between the timing alignment and the type of timing alignment associated with it. For example, this indication may be provided when a parent node is operating in case 1 and a child node is not operating in case 6. delta This indication indicates whether T was measured while the parent node was operating in case 7 and the child node was not operating in case 6. delta This indication indicates whether T was measured while the child node was operating in case 6. delta This indication can be used to indicate whether a received T delta This can assist the IAB node in determining the type of timing alignment for the IAB node to apply.

[0091] In some aspects, the parent IAB node may generate a new T delta and / or N delta FIG. 10 illustrates how a parent IAB node 1004 can provide an additional T delta and / or N delta 10 illustrates an example communication flow 1000 illustrating one embodiment providing a T delta and / or N delta 1009 is applicable to case 1. delta and / or N delta In addition to 1008, it may be configured and / or shown. delta and / or N delta 1009 may signal to the IAB node 1002 in the MAC-CE and / or DCI. delta and / or N delta is the T for the consistency of case 1 deltaand / or N delta 1008, for example in a separate message, to the IAB node. delta and / or N delta 1009 is the timing alignment for case 1. delta and / or N delta 1008, may be signaled to the IAB node 1002, for example in the same message.

[0092] In some aspects, the parent IAB node 1004 may delta and / or N delta An additional offset value 1010 can be indicated for T 1008. The additional offset 1010 is a function of the T delta and / or N delta In addition to 1008, an offset parameter associated with the timing alignment of case 6 may be configured and indicated. delta and / or N delta The additional offset 1010 to 1008 is the T delta and / or N delta 1008, for example in a separate message, to the IAB node 1002. In another aspect, the additional offset 1010 may be indicated to the IAB node 1002 separately from the T delta and / or N delta 1008 to the IAB node 1002, e.g., in the same message. The offset 1010 for the timing alignment for Case 6 may be signaled to the IAB node 1002 in the MAC-CE and / or DCI.

[0093] In 1012, the IAB node 1002 performs an additional T for the timing alignment of Case 6 to adjust the transmission timing of the MT / DU of the IAB node. delta and / or N delta 1009 or offset 1010. Then, the IAB node 1002 applies Tdelta and / or N delta 1009 or offset 1010. In some aspects, the IAB node 1002 may transmit a downlink transmission 1014 having a timing adjusted based on T delta and / or N delta Receipt of 1009 or offset 1010 may be interpreted as an instruction to switch from a different timing alignment mode to case 6 timing alignment at 1010. For example, at 1006, IAB node 1002 may operate / perform with case 1 or case 7 timing alignment, and IAB node 1002 may delta and / or N delta In response to receiving 1009 or offset 1010, the timing alignment may switch to case 6. Although this embodiment is described with respect to case 6, in some aspects, additional T delta and / or N delta 1009 or offset 1010 may also be associated with timing alignment of case 7. Thus, at 1014 and 1016, IAB node 1002 may adjust its transmit timing or receive timing according to timing alignment of case 6 or case 7.

[0094] In some embodiments, the same T delta and / or N delta The parameters can be used between different types of timing alignment. delta and / or N delta , the parent node may also indicate the type of timing alignment to which the parameter applies. FIG. 11 illustrates a case in which a parent IAB node 1104 indicates to an IAB node 1102 (e.g., a child node of the parent IAB node 1104) the type of timing alignment to which the parameter applies. delta and / or N delta 11 shows an example communication flow 1100 illustrating one embodiment providing 1108. delta and / or N deltaThe transmission indicating 1108 may further indicate a type of timing alignment associated with the indicated parameter, e.g., the type of timing alignment on which the parameter is based and / or the type of timing alignment to which the parameter is intended to be applied. delta and / or N delta 1108 may signal to the IAB node 1102 in the MAC-CE and / or DCI. delta and / or N delta One or more bit flags in a message carrying T1108 can indicate one of different types of timing alignment (e.g., case 1, case 6, and / or case 7). The inclusion of the flags themselves and / or particular values ​​of the flags can be used to indicate, for example, delta and / or N delta 1108 may indicate that the flag is associated with case 6 transmit timing alignment at a given IAB node. Similarly, the inclusion of the flag itself and / or a particular value of the flag may indicate, for example, delta and / or N delta 1108 may indicate that the IAB node is associated with case 7 receive timing alignment. If the flag indicates either case 1 or case 6, the flag may include a single bit. As an example, a "1" may indicate case 6 and a "0" may indicate case 1, or vice versa, a "0" may indicate case 6 and a "1" may indicate case 1. If the flag indicates either case 1, case 6, and case 7, or other timing alignment cases, the flag may include two or more bits.

[0095] In some aspects, the resource on which the indication is transmitted may indicate the type of timing alignment associated with it. The IAB node 1102 may determine whether or not the timing alignment is to be performed based on the resource of the message carrying the parameter. delta and / or N deltaThe type of timing alignment associated with 1108 may be inferred or otherwise determined. As an example, if an IAB node 1102 determines that a timing alignment is associated with T delta and / or N delta If you receive 1108, delta and / or N delta The time resources in 1108 may indicate association with case 1 timing alignment or case 6 timing alignment, respectively. As another example, case 1 timing alignment and case 6 timing alignment may be associated with separate spatial resources. The IAB-MT may use beam 1 when operating in case 1 (which may be associated with multiplexing scenarios such as TDM only) and may use beam 2 when operating in case 6 (which may be associated with multiplexing scenarios such as SDM-TX or (MT-TX&DU-TX)), in which case an IAB node 1102 (e.g., MT) may use beam 2 on a given beam. delta and / or N delta When an 1108 is received, the IAB node can associate the receipt with the corresponding timing case.

[0096] At 1112, the IAB node 1102 aligns the received T with respect to the timing alignment of the type shown to adjust the transmit / receive timing of the MT / DU of the IAB node 1102 as shown at 1114 and 1116. delta and / or N delta In some aspects, the IAB node 1102 applies a timing alignment command to the IAB node 1102 in accordance with the T delta and / or N delta Receipt of 1108 may be interpreted as an instruction to switch to performing the indicated type of timing alignment. For example, at 1106, the IAB node 1102 may operate / perform with a first type of timing alignment and at 1110, the IAB node 1102 may operate / perform with a first type of timing alignment. delta and / or N delta1108 can be switched to different types of timing alignment.

[0097] 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by an IAB node (e.g., an IAB node 103, 310, 410, 420, 510, 520a, 520b, 704, 902, 1002, 1102; an apparatus 1402; a baseband unit 1404, which may include a memory 376, and which may be the entire IAB node 310 or a component of the IAB node 310, such as the TX processor 316, the RX processor 370, and / or the controller / processor 375). The method may include an IAB node that is capable of selecting between multiple match types, e.g., T delta and / or N delta It may be possible to apply a time difference parameter for over-the-air synchronization, such as:

[0098] At 1202, the IAB node receives a time difference parameter for over-the-air synchronization in the IAB network from a parent IAB node. Figures 9, 10, and 11 illustrate examples in which the IAB node receives the time difference parameter from a parent IAB node. For example, the time difference parameter may be T delta and / or N delta For example, T delta may be based on the time difference between the uplink receive time and the downlink transmit time at the parent IAB node, as described in connection with FIG. 8. The time difference parameter may be, for example, an additional T delta and / or N delta 1009, or T delta and / or N delta 14. In some aspects, the reception of the time difference parameter can be performed by a time difference parameter receiving component 1440 via the receiving component 1430 and / or the RF transceiver 1422 of the apparatus 1402 of FIG.

[0099] At 1204, the IAB node adjusts its transmission or reception based on the time difference parameter with respect to one of a plurality of types of IAB node alignment, e.g., to provide alignment between IAB nodes (for case 1), alignment at the IAB node (for case 6), and / or alignment at a parent IAB node (for case 7). The plurality of types of timing alignment may include a first type of alignment (e.g., case 1) including downlink transmission timing alignment across each IAB node of the IAB network, a second type of alignment (e.g., case 6) between uplink transmission at the IAB-MT of the IAB node and downlink transmission at the IAB-DU of the IAB node, and a third type of alignment (e.g., case 7) between downlink reception at the IAB-MT of the IAB node and uplink reception at the IAB-DU of the IAB node. The adjustment of transmission or reception may be performed by a timing alignment component 1442 of the apparatus 1402 of FIG. 14. For example, an IAB node may adjust the time difference parameter T to align with the downlink transmission timing of other IAB nodes according to the alignment in Case 1. delta In another embodiment, the IAB node may adjust its uplink transmission timing and / or its DL transmission timing to provide alignment between UL and DL transmissions at the IAB node in accordance with the alignment of Case 6. In another embodiment, the IAB node may adjust its uplink receive timing or its downlink receive timing to provide alignment between UL and DL reception in accordance with the alignment of Case 7.

[0100] In some aspects, the time difference parameter is T delta According to the first type of matching, the IAB node may correspond to T delta For example, the IAB node's downlink transmission time can be adjusted based on T deltaReceipt of T can instruct the IAB node to apply the first type of matching. delta 13 shows an example where the timing alignment for case 1 is associated with:

[0101] In some aspects, the time difference parameter may correspond to an offset parameter indicated with a timing advance command for a third type of alignment, and the IAB node may determine the time difference parameter from the offset parameter and, for example, a TA command. delta Based on the third type of match (e.g., case 7), the calculated T delta can be used to adjust the transmission or reception of the IAB nodes.

[0102] In some aspects, the indication of the time difference parameter received from the parent IAB node may indicate relevance to one of a number of types of matches. For example, a first time difference parameter (T delta and / or N delta ) can be associated with the first type of match, and a second time difference parameter (an additional T delta and / or N delta 1009, or T delta and / or N delta A time offset 1010 relative to the first time difference parameter T may be associated with the second type of alignment. The IAB node may receive both the first time difference parameter and the second time difference parameter from the parent IAB node, for example, as described in connection with the embodiment of FIG. 10. The IAB node may receive the first time difference parameter and the second time difference parameter in separate messages from the parent IAB node. The IAB node may also receive the first time difference parameter and the second time difference parameter in the same message from the parent IAB node. The first time difference parameter (e.g., T delta and / or N delta 1008) may be associated with a first type of match, and the second time difference parameter may be a time offset (T delta and / or Ndelta The IAB node may receive both the first and second time difference parameters from the parent IAB node. The IAB node may receive the first and second time difference parameters in separate messages from the parent IAB node. The IAB node may also receive the first and second time difference parameters in the same message from the parent IAB node.

[0103] In some aspects, the indication of the time difference parameter may include a flag corresponding to a type of alignment associated with the time difference parameter, e.g., as described in connection with the embodiment of FIG. 11. In some aspects, the resource on which the indication of the time difference parameter is received may indicate a type of alignment associated with the time difference parameter, e.g., as described in connection with the embodiment of FIG.

[0104] 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a parent IAB node (e.g., IAB node 103, 310, 410, 420, 510, 520a, 520b, 702, 904, 1004, 1104; device 1402; baseband unit 1404, which may include memory 376, and may be the entire IAB node 310 or a component of the IAB node 310, such as TX processor 316, RX processor 370, and / or controller / processor 375). The method may be performed by an IAB node that is capable of selecting between multiple match types, e.g., T delta and / or N delta It may be possible to apply a time difference parameter for over-the-air synchronization, such as:

[0105] At 1302, a parent IAB node transmits or receives communication with a child IAB node. The communication may be based on any of the aspects described in connection with FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG. 9, FIG. 10, or FIG. 11. The communication may be based on one of a number of types of timing alignment. In some aspects, the transmission and reception may be performed by, for example, the receiving component 1430 and the transmitting component 1434 of the apparatus 1402 of FIG. 10.

[0106] At 1304, the parent IAB node transmits a time difference parameter for over-the-air synchronization in the IAB network, the time difference parameter being applicable to one of a number of types of IAB node coordination, e.g., to provide coordination between IAB nodes (for case 1), coordination at an IAB node (for case 6), and / or coordination at a parent IAB node (for case 7). FIGS. 9, 10, and 11 show examples in which the parent IAB node transmits the time difference parameter from the parent IAB node. For example, the time difference parameter may be a time difference parameter for T, as described, e.g., in connection with FIG. 9 or FIG. 11. delta and / or N delta For example, T delta may be based on the time difference between the uplink receive time and the downlink transmit time at the parent IAB node, as described in connection with FIG. 8. The time difference parameter may be, for example, an additional T delta and / or N delta 1009, or T delta and / or N delta 14. In some aspects, the transmission of the time difference parameter can be performed by a time difference parameter indicator component 1444 via the transmitting component 1434 and / or the RF transceiver 1422 of the apparatus 1402 of FIG.

[0107] The multiple types of timing alignment may include a first type of alignment (e.g., case 1) that includes downlink transmission timing alignment across each IAB node of the IAB network, a second type of alignment (e.g., case 6) between uplink transmissions in the IAB-MT of the IAB node and downlink transmissions in the IAB-DU of the IAB node, and a third type of alignment (e.g., case 7) between downlink receptions in the IAB-MT of the IAB node and uplink receptions in the IAB-DU of the IAB node.

[0108] In some aspects, the time difference parameter is T delta and can be associated with a first type of match. For example, T delta The transmission of T can instruct the child IAB node to apply the first type of matching. delta 13 shows an example where the timing alignment for case 1 is associated with:

[0109] In some aspects, the time difference parameter may correspond to an offset parameter indicated with a timing advance command for a third type of alignment, and the time difference parameter may correspond to a time difference parameter from the offset parameter and, for example, a TA command. delta This concerns the calculation of T calculated based on the third type of matching (e.g., case 7). delta This can be related to the adjustment of transmission or reception of IAB nodes using.

[0110] In some aspects, the indication of the time difference parameter transmitted from the parent IAB node may indicate relevance to one of a number of types of matching. For example, a first time difference parameter (T delta and / or N delta ) can be associated with the first type of match, and a second time difference parameter (an additional T delta and / or N delta 1009, or T delta and / or N delta10) may be associated with a second type of alignment. The parent IAB node may transmit both the first and second time difference parameters to the child IAB node, for example, as described in connection with the embodiment of FIG. 10. The parent IAB node may receive the first and second time difference parameters in separate messages to the child IAB node. The parent IAB node may transmit the first and second time difference parameters in the same message to the child IAB node. The first time difference parameter (e.g., offset 1010 relative to T delta and / or N delta 1008) may be associated with a first type of match, and the second time difference parameter may be a time offset (T delta and / or N delta The parent IAB node may transmit both the first and second time difference parameters to the child IAB node. The parent IAB node may transmit the first and second time difference parameters in separate messages to the child IAB node. The parent IAB node may transmit the first and second time difference parameters in the same message with the child IAB node.

[0111] In some aspects, the indication of the time difference parameter may include a flag corresponding to a type of alignment associated with the time difference parameter, e.g., as described in connection with the embodiment of FIG. 11. In some aspects, the resource on which the indication of the time difference parameter is transmitted may indicate a type of alignment associated with the time difference parameter, e.g., as described in connection with the embodiment of FIG.

[0112] FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for an apparatus 1402. The apparatus 1402 may be an IAB node, a component of an IAB node, or may implement the functionality of an IAB node. The apparatus 1402 may correspond to an IAB node 103, 310, 420, 520a, 520b, 606a, 606b, 702, 704, 802, 804, 902, 904, 1002, 1004, 1102, or 1104. In some aspects, the apparatus may include a baseband unit 1404. The baseband unit 1404 may communicate with one or more UEs 104 through a cellular RF transceiver. The baseband unit 1404 may also communicate with one or more IAB nodes 103 through a cellular RF transceiver. The IAB node 103 may be a parent node of the apparatus or may be a child node of the apparatus. The baseband unit 1404 may include a computer readable medium / memory. The baseband unit 1404 is responsible for overall processing, including the execution of software stored on the computer readable medium / memory. The software, when executed by the baseband unit 1404, causes the baseband unit 1404 to perform the various functions described above. The computer readable medium / memory may also be used to store data that is manipulated by the baseband unit 1404 when executing the software. The baseband unit 1404 further includes a receiving component 1430, a communications manager 1432, and a transmitting component 1434. The communications manager 1432 includes one or more of the illustrated components. The components in the communications manager 1432 may be stored in the computer readable medium / memory and / or may be configured as hardware in the baseband unit 1404. The baseband unit 1404 may be a component of the IAB node 310 and may include a memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375.

[0113] The communications manager 1432 includes a time difference parameter receiving component 1440 configured to receive from a parent IAB node a time difference parameter for over-the-air synchronization in the IAB network, for example, as described in connection with 1202 of FIG. 14. The communications manager 1432 includes a time difference parameter indicator component 1444 configured to indicate to a child IAB node a time difference parameter for over-the-air synchronization in the IAB network, for example, as described in connection with 1304 of FIG. 13. The communications manager 1432 further includes a timing alignment component 1442 configured to adjust transmission or reception of the IAB node with respect to one of a plurality of types of alignment at the IAB node and / or parent IAB node based on the time difference parameter, for example, as described in connection with 1204 of FIG. 14. The apparatus 1402 further includes a receiving component 1430 and a transmitting component 1434 configured to transmit and receive communications with a child IAB node, for example, as described in connection with 1302 of FIG. 13.

[0114] The apparatus may include additional components that perform each of the blocks of the algorithms in the flowcharts of Figures 12 or 13 and / or the aspects performed by the IAB node in any of Figures 9, 10, or 11. Thus, each of the blocks in the flowcharts of Figures 12 or 13 and / or the aspects performed by the IAB node in any of Figures 9, 10, or 11 may be performed by components, and the apparatus may include one or more of those components. Those components may be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by a processor configured to perform the described processes / algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0115] As shown, the apparatus 1402 may include various components configured for various functions. In one configuration, the apparatus 1402, particularly the baseband unit 1404, may include means for receiving a time difference parameter for OTA synchronization in the IAB network from a parent IAB node and means for adjusting transmission or reception of the IAB node with respect to one of a plurality of types of alignment at the IAB node and / or the parent IAB node based on the time difference parameter. The apparatus 1402 may further include means for transmitting or receiving communication with a child IAB node and means for transmitting a time difference parameter for over-the-air synchronization in the IAB network, the time difference parameter applying to one of a plurality of types of alignment at the child IAB node. Since the apparatus 1402 may operate as a parent node for one or more child nodes and may operate as a child node for a parent node, the apparatus 1402 may include means for performing aspects of FIG. 12 and FIG. 13 in some aspects. The means may be one or more of the components of the apparatus 1402 configured to perform the recited functions by the means. As described above, the apparatus 1402 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 the controller / processor 375 configured to perform the recited functions by the means.

[0116] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flow charts is an example of an example approach. It should be understood that the particular order or hierarchy of the blocks in those processes / flow charts can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not meant to be limited to the particular order or hierarchy presented.

[0117] 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 readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims. Reference to an element in the singular does not mean "only one" unless so expressly stated, but rather means "one or more." Terms such as "if," "when," and "while" do not imply an immediate temporal relationship or reaction. That is, these phrases, such as "when," do not imply an immediate action in response to or during the occurrence of an action, but simply mean that an action will occur if a condition is met, but do not require a specific or immediate temporal constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, 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, and may include multiple As, multiple Bs, or multiple Cs.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" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination can include one or more elements of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, for a set of X, X will include one or more elements. When a first device receives data from or transmits data to a second device, the data can be received / transmitted directly between the first device and the second device, or indirectly between the first device and the second device via a set of devices. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and encompassed by the claims. Moreover, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0118] As used herein, the phrase "based on" should not be construed as a reference 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.) is to be construed as "based on at least A," unless expressly stated otherwise.

[0119] The following aspects are exemplary only and can be combined with other aspects or teachings described herein without limitation.

[0120] Aspect 1 is a method of wireless communication in an IAB node, the method including receiving a time difference parameter for over-the-air synchronization in an IAB network from a parent IAB node, and adjusting transmission or reception of the IAB node for one of a plurality of types of IAB node alignment based on the time difference parameter.

[0121] In aspect 2, the method of aspect 1 further includes, the multiple types of IAB node alignment include a first type of alignment including downlink transmission timing alignment across each IAB node of the IAB network, a second type of alignment between uplink transmissions in the IAB-MT of the IAB node and downlink transmissions in the IAB-DU of the IAB node, and a third type of alignment between downlink receptions in the IAB-MT of the IAB node and uplink receptions in the IAB-DU of the IAB node.

[0122] In an embodiment, the method of embodiment 1 or embodiment 2 further includes a time difference parameter associated with the first type match and the third type match.

[0123] In an embodiment, the method of the embodiment may further include a step of: delta , and the IAB node, according to the first type of matching, delta and adjusting a downlink transmission time of the IAB node based on the

[0124] In an embodiment 5, the method of embodiment 4 further comprises: delta Receiving the signal further includes instructing the IAB node to apply the first type of matching.

[0125] In an embodiment, the method of the embodiment 1 or 2 further includes the time difference parameter corresponding to an offset parameter indicated with a timing advance command for a third type of alignment, the method further comprising: determining T delta Based on the third type of matching, T delta and adjusting transmission or reception of the IAB nodes using the received signal.

[0126] In example 7, the method of any of examples 1-3 further includes the indication of the time difference parameter received from the parent IAB node indicating relevance to one of a plurality of types of IAB node matching.

[0127] In aspect 8, the method of aspect 1 or aspect 7 further includes a first time difference parameter associated with the first type of match and a second time difference parameter associated with the second type of match.

[0128] In example 9, the method of example 8 further includes the IAB node receiving both the first time difference parameter and the second time difference parameter from the parent IAB node.

[0129] In example 10, the method of example 9 further includes the IAB node receiving the first time difference parameter and the second time difference parameter in separate messages from the parent IAB node.

[0130] In example 11, the method of example 9 further includes the IAB node receiving the first time difference parameter and the second time difference parameter in a same message from the parent IAB node.

[0131] In example 12, the method of example 8 further includes: a first time difference parameter is associated with a first type of match; and a second time difference parameter is a time offset associated with a second type of match, the time offset being relative to the first time difference parameter.

[0132] In example 13, the method of example 8 further includes the IAB node receiving both the first time difference parameter and the second time difference parameter from the parent IAB node.

[0133] In example 14, the method of example 13 further includes the IAB node receiving the first time difference parameter and the second time difference parameter in separate messages from the parent IAB node.

[0134] In example 15, the method of example 13 further includes the IAB node receiving the first time difference parameter and the second time difference parameter in a same message from the parent IAB node.

[0135] In example 16, the method of any of examples 7-15 further includes: the indication of the time difference parameter includes a flag corresponding to a type of alignment associated with the time difference parameter.

[0136] In example 17, the method of any of examples 7-16 further includes the resource on which the indication of the time difference parameter is received indicating a type of alignment associated with the time difference parameter.

[0137] Example 18 is an apparatus for wireless communication, comprising means for performing the method of any of Examples 1-17.

[0138] In Example 19, the apparatus of Example 18 further includes at least one antenna and a transceiver coupled to the at least one antenna.

[0139] Example 20 is an apparatus for wireless communication comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform any of the methods of Examples 1-17 based at least in part on information stored in the memory.

[0140] In example 21, the apparatus of example 20 further includes at least one of an antenna or a transceiver coupled to the at least one antenna and to the at least one processor.

[0141] Aspect 22 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to perform any of the methods of aspects 1-17.

[0142] Aspect 23 is a method of wireless communication in an IAB parent node, the method including transmitting or receiving communication with an IAB node that is a child node of the parent IAB node, and transmitting a time difference parameter for over-the-air synchronization in the IAB network, the time difference parameter being applicable to one of a plurality of types of IAB node alignment.

[0143] In aspect 24, the method of aspect 23 further includes, the multiple types of IAB node alignment include a first type of alignment including downlink transmission timing alignment across each IAB node of the IAB network, a second type of alignment between uplink transmissions in the IAB-MT of the IAB node and downlink transmissions in the IAB-DU of the IAB node, and a third type of alignment between downlink receptions in the IAB-MT of the IAB node and uplink receptions in the IAB-DU of the IAB node.

[0144] In example 25, the method of example 23 or example 24 further comprises: delta It supports T delta is based on a time difference between an uplink receive time and a downlink transmit time at the parent IAB node.

[0145] In embodiment 26, the method of embodiment 25 further comprises: deltaThe sending of the signal further includes instructing the IAB node to apply the first type of matching.

[0146] In example 27, the method of example 23 or example 24 further includes the indication of the time difference parameter from the parent IAB node indicating relevance to one of a plurality of types of IAB node matches.

[0147] In example 28, the method of example 23, 24, or 27 further includes a first time difference parameter associated with the first type of match and a second time difference parameter associated with the second type of match.

[0148] In example 29, the method of example 23, 24, 27, or 28 further includes the parent IAB node sending both the first time difference parameter and the second time difference parameter to the IAB node.

[0149] In example 30, the method of example 29 further includes the parent IAB node sending the first time difference parameter and the second time difference parameter in separate messages to the IAB node.

[0150] In example 31, the method of example 29 further includes the parent IAB node sending the first time difference parameter and the second time difference parameter in a same message to the IAB node.

[0151] In aspect 32, the method of aspect 23, 24, or 27 further includes: a first time difference parameter is associated with a first type of match; and a second time difference parameter is a time offset associated with a second type of match, the time offset being relative to the first time difference parameter.

[0152] In example 33, the method of example 32 further includes the parent IAB node sending both the first time difference parameter and the second time difference parameter to the IAB node.

[0153] In example 34, the method of example 33 further includes the parent IAB node sending the first time difference parameter and the second time difference parameter in separate messages to the IAB node.

[0154] In example 35, the method of example 33 further includes the parent IAB node sending the first time difference parameter and the second time difference parameter in a same message to the IAB node.

[0155] In example 36, the method of any of examples 27-35 includes the indication of the time difference parameter further including a flag corresponding to a type of alignment associated with the time difference parameter.

[0156] In example 37, the method of any of examples 27-36 includes the resource on which the indication of the time difference parameter is transmitted further indicating a type of alignment associated with the time difference parameter.

[0157] Example 38 is an apparatus for wireless communication comprising means for performing the method of any of Examples 23-37.

[0158] In example 39, the apparatus of example 38 further includes at least one of an antenna or a transceiver coupled to the at least one antenna.

[0159] Example 40 is an apparatus for wireless communication comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform any of the methods of examples 23-37 based at least in part on information stored in the memory.

[0160] In aspect 41, the apparatus of aspect 40 further includes at least one of an antenna or a transceiver coupled to the at least one antenna and to the at least one processor.

[0161] Aspect 42 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to perform any of the methods of aspects 23-37. [Explanation of symbols]

[0162] 100 Wireless communication systems and access networks 102 Base station 103 IAB Nodes 104UE 105 Distributed Unit (DU) 107 Roadside Unit (RSU) 109 Remote Unit (RU) 110 Coverage Area 111 Central Unit (CU) 120 Communication Links 132 1st backhaul link 158 Device-to-Device (D2D) Communication Links 160 Evolved Packet Core (EPC) 174 Home Subscriber Server (HSS) 180 base station 182 Beamforming 190 Core Network

Claims

1. An apparatus for wireless communication in an integrated access and backhaul (IAB) node, comprising: a memory; at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor: receives from a parent IAB node a first time difference parameter and a second time difference parameter regarding wireless-based synchronization in an IAB network; is configured to adjust a transmission timing or a reception timing at the IAB node with respect to one of a plurality of types of IAB node alignments based on the first time difference parameter, wherein the plurality of types of IAB node alignments include: a first type of alignment including downlink transmission timing alignment across each IAB node in the IAB network; a second type of alignment between uplink transmission at an IAB mobile terminal (IAB-MT) of the IAB node and downlink transmission at an IAB distributed unit (IAB-DU) of the IAB node; a third type of alignment between downlink reception at the IAB-MT of the IAB node and uplink reception at the IAB-DU of the IAB node; the first time difference parameter is associated with the first type of alignment and the third type of alignment, and the second time difference parameter is associated with the second type of alignment; Apparatus.

2. The first time difference parameter corresponds to a timing delta (T ｄｅｌｔａ ), based on a time difference between an uplink reception time and a downlink transmission time at the parent IAB node, and the IAB node adjusts the downlink transmission time of the IAB node according to the first type of alignment from the plurality of types of IAB node alignments, based on the T ｄｅｌｔａ ​ The apparatus according to claim 1.

3. The foregoing T ｄｅｌｔａ receiving is to instruct the IAB node to apply the first type of alignment The apparatus according to claim 2.

4. The first time difference parameter corresponds to an offset parameter indicated together with a timing advance command regarding the third type of alignment, and the at least one processor: Calculate T from the offset parameter, and further configured to adjust the transmission or reception of the IAB node using the T based on the third type of alignment ｄｅｌｔａ ｄｅｌｔａ ​​ The apparatus according to claim 1.

5. The at least one processor is configured to receive both the first time difference parameter and the second time difference parameter from the parent IAB node, preferably in separate messages or in the same message. The apparatus according to claim 1.

6. The first time difference parameter is associated with the first type of alignment, the second time difference parameter is a time offset associated with the second type of alignment, and the time offset is relative to the first time difference parameter. The apparatus according to claim 1.

7. The at least one processor is configured to receive both the first time difference parameter and the second time difference parameter from the parent IAB node, preferably in separate messages or in the same message The apparatus according to claim 6.

8. The indication of the first time difference parameter received from the parent IAB node indicates the relevance to one of the plurality of types of IAB node alignment, and optionally, the indication of the first time difference parameter includes a flag corresponding to the type of alignment associated with the first time difference parameter, or the resource from which the indication of the first time difference parameter is received indicates the type of alignment associated with the first time difference parameter The apparatus according to claim 1.

9. An apparatus for wireless communication in a parent integrated access and backhaul (IAB) node, comprising: a memory; at least one processor coupled to the memory, wherein based at least in part on information stored in the memory, the at least one processor is configured to: transmit or receive communication with an IAB node that is a child node of the parent IAB node; transmit a first time difference parameter and a second time difference parameter related to wireless-based synchronization in the IAB network, wherein the first time difference parameter is applicable to one of a plurality of types of IAB node alignment, the plurality of types of IAB node alignment including: a first type of alignment including downlink transmission timing alignment across each IAB node in the IAB network; a second type of alignment between uplink transmission at an IAB mobile terminal (IAB-MT) of the IAB node and downlink transmission at an IAB distributed unit (IAB-DU) of the IAB node; a third type of alignment between downlink reception at the IAB-MT of the IAB node and uplink reception at the IAB-DU of the IAB node; the first time difference parameter is associated with the first type of alignment and the third type of alignment, and the second time difference parameter is associated with the second type of alignment Apparatus.

10. The first time difference parameter corresponds to a timing delta (T ｄｅｌｔａ ), where the T ｄｅｌｔａ is based on a time difference between an uplink reception time and a downlink transmission time at the parent IAB node, and optionally, transmission of the T delta instructs the IAB node to apply the first type of alignment The apparatus according to claim 9.

11. The indication of the time difference parameter from the parent IAB node indicates the relevance to one of the plurality of types of IAB node alignments The apparatus according to claim 9

12. The at least one processor is configured to transmit both the first time difference parameter and the second time difference parameter to the IAB node, and the at least one processor transmit the first time difference parameter and the second time difference parameter in separate messages to the IAB node, or is configured to transmit the first time difference parameter and the second time difference parameter in the same message to the IAB node The apparatus according to claim 9

13. The first time difference parameter is associated with the first type of alignment, the second time difference parameter is a time offset associated with the second type of alignment, the time offset is with respect to the first time difference parameter, and the at least one processor transmit the first time difference parameter and the second time difference parameter in separate messages to the IAB node, or is configured to transmit the first time difference parameter and the second time difference parameter in the same message to the IAB node The apparatus according to claim 9

14. A method of wireless communication in an integrated access and backhaul (IAB) node, comprising receiving, from a parent IAB node, a first time difference parameter and a second time difference parameter regarding wireless synchronization in an IAB network; and adjusting a transmission timing or a reception timing in the IAB node regarding one of a plurality of types of IAB node alignments based on the time difference parameter, wherein the plurality of types of IAB node alignments a first type of alignment including downlink transmission timing alignment across each IAB node in the IAB network; and a second type of alignment between uplink transmission in an IAB mobile terminal (IAB-MT) of the IAB node and downlink transmission in an IAB distributed unit (IAB-DU) of the IAB node including a third type of alignment between downlink reception in the IAB-MT of the IAB node and uplink reception in the IAB-DU of the IAB node the first time difference parameter is associated with the first type of alignment and the third type of alignment, and the second time difference parameter is associated with the second type of alignment Method [

15. ] A method of wireless communication in a parent integrated access and backhaul (IAB) node, comprising: transmitting or receiving communication with an IAB node that is a child node of the parent IAB node transmitting a first time difference parameter and a second time difference parameter related to wireless-based synchronization in an IAB network, the first time difference parameter being applicable to one of a plurality of types of IAB node alignments a first type of alignment including downlink transmission timing alignment across each IAB node in the IAB network a second type of alignment between uplink transmission in the IAB mobile terminal (IAB-MT) of the IAB node and downlink transmission in the IAB distributed unit (IAB-DU) of the IAB node including a third type of alignment between downlink reception in the IAB-MT of the IAB node and uplink reception in the IAB-DU of the IAB node the first time difference parameter is associated with the first type of alignment and the third type of alignment, and the second time difference parameter is associated with the second type of alignment Method

Images