Enhancement for providing protection signal in IAB network

Abstract

An integrated access and backhaul (IAB) node can receive a parent knowledge message indicating whether a parent IAB node of a child IAB node has received an optional signaling message, determine to transition between a first resource and a second resource at a transition time, the first resource being associated with use of a mobile terminal of the child IAB node and the second resource being associated with use of a distributed unit of the child IAB node, and determine a number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 62 / 983,384, filed on February 28, 2020, entitled “ENHANCEMENTS FOR PROVIDED GUARD SIGNALS IN IAB NETWORK,” and U.S. Patent Application No. 17 / 166,811, filed on February 3, 2021, entitled “ENHANCEMENTS FOR PROVIDED GUARD SIGNALS IN IAB NETWORK,” which are expressly incorporated herein by reference in their entireties. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to an integrated access and backhaul (IAB) network. Background Art

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

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

[0006] The following provides a simplified overview of one or more aspects in order to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all anticipated aspects, and is neither intended to identify the key or important elements of all aspects, nor 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 a more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an integrated access and backhaul (IAB) node. The apparatus may receive a parent knowledge message indicating whether the parent IAB node of the child IAB node has received an optional signaling message; determine to transition between a first resource and a second resource at a transition time, the first resource being associated with the use of a mobile terminal of the child IAB node, and the second resource being associated with the use of a distributed unit of the child IAB node; and determine the number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an IAB node. The apparatus may receive an optional signaling message from a central unit of an IAB donor; send a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signaling message; and provide a plurality of guard symbols at a transition time of the child IAB node, the number of which is based on the optional signaling message.

[0009] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an IAB donor. The apparatus may send an optional signaling message to a parent IAB node; and send a parent knowledge message to a child IAB node of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message.

[0010] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an IAB donor. The apparatus may send a first configuration message to a first group of IAB nodes of an IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first group of IAB nodes; and send a second configuration message to a second group of IAB nodes of the IAB network, the second configuration message configuring the second group of IAB nodes not to provide protection symbols at transition instances of child IAB nodes in the second group of IAB nodes.

[0011] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an IAB node. The apparatus may receive a configuration message from an IAB donor, the configuration message instructing the parent IAB node whether to provide protection symbols to the child IAB node of the parent IAB node or not to provide protection symbols; determine a transition instance of the child IAB node of the parent IAB node, the transition instance being a transition between the use of a mobile terminal of the child IAB node and the use of a distributed unit of the child IAB node; if the configuration message instructs the parent IAB node to provide protection symbols, then provide protection symbols at the transition instance; and if the configuration message instructs the parent IAB node not to provide protection symbols, then do not provide protection symbols at the transition instance.

[0012] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of a few of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0014] Figure 2A , Figure 2B , Figure 2C and Figure 2D Figures showing examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

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

[0016] Figure 4 is a diagram illustrating an Integrated Access and Backhaul (IAB) network.

[0017] Figure 5 is a diagram illustrating an IAB network and its components.

[0018] Figure 6 is a diagram showing an example of interaction between an IAB donor, an IAB node, and child IAB nodes.

[0019] Figure 7 is a diagram showing the communication between a child IAB node and its parent.

[0020] Figure 8is a table showing IAB node transition types.

[0021] Fig. 9 is a communication diagram illustrating protection symbol signaling between a child IAB node and a parent IAB device.

[0022] Fig. 10A is a diagram showing guard symbols at the transition from DU to MT.

[0023] Fig. 10B is a diagram showing guard symbols at the transition from MT to DU.

[0024] Fig.11 is a diagram showing the communication between a child IAB node and its parent.

[0025] Fig.12 is a diagram illustrating the communication between a child IAB node and its parent including DU resources with cell-specific signals.

[0026] Fig.13 is a diagram illustrating the communication between a child IAB node and its parent including DU resources with cell-specific signals.

[0027] Fig.14 is a diagram 1400 showing communications between a child IAB node and its parent including dynamically scheduled resources.

[0028] Fig.15 is a diagram showing the communication between a child IAB node and its parent including dynamically scheduled resources.

[0029] Fig.16 is a communication flow diagram illustrating providing protection symbols based on optional signaling.

[0030] Fig.17 is a communication diagram showing an example of protection symbol signaling and transitions between a child IAB node and a parent IAB device.

[0031] Fig.18 is a diagram showing communication between three IAB nodes.

[0032] Fig.19 is a diagram showing an IAB network.

[0033] Fig. 20 is a flow chart of a wireless communication method.

[0034] Fig.21 is a flow chart of a wireless communication method.

[0035] Fig. 22 is a flow chart of a wireless communication method.

[0036] Fig.23 is a flow chart of a wireless communication method.

[0037] Fig.24 is a flow chart of a wireless communication method.

[0038] Fig.25 are diagrams showing examples of hardware implementations for an apparatus.

[0039] Fig.26 are diagrams showing examples of hardware implementations for an apparatus.

[0040] Fig. 27 are diagrams showing examples of hardware implementations for an apparatus.

[0041] Fig.28 are diagrams showing examples of hardware implementations for an apparatus.

[0042] Fig.29 are diagrams showing examples of hardware implementations for an apparatus. DETAILED DESCRIPTION

[0043] In conjunction with the accompanying drawings, the detailed description set forth below is intended as a description of various configurations, and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it should be understood by those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

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

[0045] For example, an element or any part 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, graphics 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, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, programs, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

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

[0047] Figure 1 1 is a diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0048] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment 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 warning messaging. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) via a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0049] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' can 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 can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input and multiple output (MIMO) antenna technology including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. Base stations 102 / UEs 104 may use spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth per carrier, each carrier being allocated in carrier aggregation for transmission in each direction up to a total of Yx MHz (x component carriers). Carriers may or may not be contiguous to each other. Carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell), and a secondary component carrier may be referred to as a secondary cell (SCell).

[0050] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

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

[0052] The small cell 102' may operate in licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed frequency spectrum may increase coverage and / or increase capacity of the access network.

[0053] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or in near-mmW frequencies for communicating with UE 104. When the gNB 180 operates in mmW frequencies or near-mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in the band may be referred to as millimeter waves. Near mmW may extend down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using the mmW / near-mmW radio frequency bands (e.g., 3 GHz to 300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 for the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0054] Base station 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also send beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0055] 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. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provision and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0056] 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 a unified 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 procedures and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0057] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, 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., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, an oven, a vehicle, a heart rate monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0058] Reference again Figure 1In some aspects, the base station 180 may be part of an integrated access and backhaul (IAB) network (e.g., may be or may include an IAB node or an IAB donor), such as an IAB node or an IAB donor. The base station 180 may include a guard symbol providing component 198. The guard symbol providing component 198 may be configured to determine whether a resource is associated with use of a mobile terminal (MT) of the IAB node or with use of a distributed unit (DU) of the IAB node, and may determine to provide a guard symbol to the IAB node based on the determination. Although the following description may focus on 5GNR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0059] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B 230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram showing an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to DL or UL; or can be TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (mainly DL), where D is DL, U is UL, and X is used flexibly between DL / UL, and subframe 3 is configured with slot format 34 (mainly UL). Although subframes 3 and 4 are shown in slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2 to 61 include a mixture of DL, UL and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling) through the received slot format indicator (SFI). It should be noted that the description below also applies to the 5G / NR frame structure as TDD.

[0060] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and numerology. For slot configuration 0, different numerical parameters μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerical parameters 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerical parameter μ, there are 14 symbols / slot and 2 μ time slots / subframe. Subcarrier spacing and symbol length / duration are functions of digital parameters. Subcarrier spacing can be equal to 2 μ *15kHz, where μ is a digital parameter from 0 to 5. Thus, a digital parameter μ=0 has a subcarrier spacing of 15kHz, and a digital parameter μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0, with 14 symbols per slot and a numerical parameter μ = 2, with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0061] The frame structure can be represented using a resource grid. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which 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.

[0062] like Figure 2AAs shown, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) (indicated as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The UE 104 uses the PSS to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The UE uses the SSS to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the above-mentioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides multiple RBs in the system bandwidth and system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

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

[0065] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

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

[0067] The transmit (TX) processor 316 and the 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 the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be segmented into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

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

[0069] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, 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.

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

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

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

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

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

[0075] Figure 4 4 is a diagram illustrating an integrated access and backhaul (IAB) network 400. The IAB network 400 may include an anchor node (which may be referred to herein as an "IAB donor") 410 and an access node (which may be referred to herein as an "IAB node") 420. The IAB donor 410 may be a base station, such as a gNB or an eNB, and may perform a function of controlling the IAB network 400. The IAB node 420 may include an L2 relay node, etc. The IAB donor 410 and the IAB node 420 share resources together to provide an access network and a backhaul network to a core network 490. For example, resources may be shared between an access link and a backhaul link in the IAB network.

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

[0077] Figure 55 is a diagram showing an IAB network 500 and its components. The IAB network 500 includes an IAB donor 510 and an IAB node 520. The IAB node and the IAB donor can provide a wireless access link to a UE 530.

[0078] The IAB donor 510 can be considered as the root node of the tree structure of the IAB network 500. The IAB donor node 510 can be connected to the core network 590 via a wired connection 591. The wired connection can include, for example, a wired optical fiber. The IAB donor node 510 can provide a connection to one or more IAB nodes 520a. The IAB nodes 520a can each be referred to as a child node of the IAB donor node 510. The IAB donor node 510 can also provide a connection to one or more UEs 530a, which can be referred to as child UEs of the IAB donor 510. The IAB donor 510 can be connected to its child IAB node 520a via a backhaul link 560, and can be connected to the child UE 530a via an access link 570. The IAB node 520a, which is a child node of the IAB node 510, can also have (multiple) IAB nodes 520b and / or (multiple) UEs 530b as children. For example, the IAB node 520b may be further connected to child nodes and / or child UEs. Figure 5 IAB nodes 520b are shown providing access links to UEs 530c, respectively.

[0079] 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 be responsible for the configuration of the IAB network 500. The CU may perform RRC / PDCP layer functions. The DU may perform scheduling. For example, the DU may schedule resources for communication of the child IAB node 520a and / or the UE 530a of the IAB donor 510.

[0080] The IAB nodes 520a, 520b may include a mobile terminal (MT) and a DU. The MT of the IAB node 520a may act as a scheduled node, similar to the UE 530a being scheduled by the DU of the parent node (e.g., IAB donor 510). The MT of the IAB node 520b may act as a scheduled node of the parent node 520a. The DU may schedule the child IAB node 520b and the UE 530b of the IAB node 520a. Because the IAB node may provide a connection to an IAB node, which in turn provides a connection for another IAB node, the pattern of the parent IAB node including the DU scheduling the child IAB node / child UE may continue.

[0081] Figure 6 600 is a diagram showing an example of interaction between an IAB donor 610, an IAB node 620, and a child IAB node 630. The CU 612 of the IAB donor 610 can provide centralized management of resources available for IAB node communication. The CU 612 of the IAB donor 610 can allocate resources semi-statically. Additionally or alternatively, the soft resources of the child node can be controlled in a distributed dynamic manner by the parent of the child node (e.g., the DU 624 or 614 of the parent node). For example, the DU 624 of the IAB node 620 can allocate the soft resources of the child IAB node 630 through dynamic control signaling.

[0082] MTs 622 and 632 may have downlink (DL) resources, uplink (UL) resources, or flexible (F) resources. DUs 614, 624, and 634 may have hard DL resources, hard UL resources, and / or hard F resources. DUs 614, 624, and 634 may have soft DL resources, soft UL resources, and / or soft flexible resources. In addition to hard or soft resource types, DUs 614, 624, and 634 may have resources of a not available (NA) type.

[0083] The CU 612 of the IAB donor 610 may communicate with the DU 624 of the IAB node 620 and the DU 634 of the child IAB node 630 through the F1 interface 640. The F1 interface 640 may support exchanging information with the child IAB node (e.g., receiving an MT of a child of the IAB node) or delivering an encapsulated RRC message to the child IAB node (e.g., delivering an encapsulated RRC message for the child IAB node 630 to the DU 624 of the IAB node 620). In some aspects, the CU 612 may configure a resource mode of the DU 624 of the IAB node 620 through the F1 interface 640.

[0084] The DU 624 of the IAB node 620 may communicate with the MT 632 of the child IAB node 630 via the Uu air interface 650. The Uu air interface 650 may support delivery of an RRC message received from the CU 612 of the IAB donor 610 to the MT 632 of the child IAB node 630, and may support the DU 624 of the IAB node 620 to dynamically schedule the MT 632 of the child IAB node 630. In some aspects, the IAB node 620 may dynamically control soft resources of the DU 634 of the child IAB node 630 via the Uu air interface 650.

[0085] Figure 7 7 is a diagram showing communication between a child IAB node and its parent. The child IAB node may be in TDD mode.

[0086] The IAB device may communicate with its parent IAB device (e.g., a DU of a parent IAB node or an IAB donor) using its MT, and may communicate with its child (e.g., a child IAB node or a UE) using its DU. The resources of the DU may be configured as UL, DL, or flexible (F). The DU may send downlink information to a grandchild IAB device (e.g., an MT of a child IAB node or a UE) on resources configured as DL. The DU may receive uplink information from a grandchild IAB device on resources configured as UL. The MT may determine whether the resources configured as F will be used as DL or UL at a later time based on, for example, receiving a request (e.g., from a parent IAB device or an IAB donor of an IAB network) that the resources configured as F should be used as DL or UL.

[0087] The resources of the DU may be additionally configured as hard, soft, or unavailable (NA) to avoid conflicts with resources being utilized by the MT. When a resource is indicated as hard, the DU may assume that it can use the resource regardless of the configuration of the MT. The DU may determine whether to use hard resources to communicate with the child IAB device, regardless of whether the MT has an allocation from the parent IAB device. In some aspects, the DU may decide to ignore the MT allocation from the parent IAB device and use hard resources to communicate with its child node. In some aspects, the DU may decide to give priority to the MT to communicate with the parent IAB device instead of using hard resources to communicate with the grandchild IAB node. When a resource is indicated as NA, it cannot be used by the DU. When a resource is indicated as a soft resource, the DU may determine whether it can do so based on whether utilizing the resource will affect the MT sending or receiving on the resource. Soft resources may be explicitly or implicitly indicated as available. When the parent IAB device indicates to the child IAB node that the resource will be available (for example, the parent does not schedule the MT of the child IAB node to send on the soft resource), the soft resource is explicitly indicated as available. When the child IAB node determines that its DU can utilize the soft resources without interfering with the transmission or reception of the child IAB node's MT (eg, without an indication from the parent IAB device), the soft resources are implicitly indicated as available.

[0088] Figure 7 The diagram 700 shows that a parent IAB device communicates with a child IAB node on a first set of time domain resources 710, a second set of time domain resources 720, and a third set of time domain resources 730. Specifically, the diagram 700 shows the configuration of a DU of a parent IAB device ("parent DU"), the configuration of an MT of a child IAB node ("child MT"), and the configuration of a DU of a child IAB node ("child DU").

[0089] The parent IAB node may send downlink data to the child IAB node on the first set of resources 710. The first set of resources 710 may be configured as hard for the parent DU to allow the parent DU to decide whether to use the resources 710 to send downlink data to the child IAB node regardless of the operation of the MT of the parent IAB device. The first set of resources 710 may be configured as DL for the child MT to receive downlink data from the parent DU. For the child DU, the first set of resources 710 may be configured as NA to prevent the child DU from interfering with the child MT receiving downlink data from the parent DU.

[0090] The child IAB node may send downlink data to a child entity (such as another IAB node or a UE) on the second set of resources 720. The child DU may be configured to be hard for the second set of resources 720, and the parent DU may be configured to be NA for the second set of resources 720, so that the child MT and the parent DU may not communicate with each other on the second set of resources 720.

[0091] The child IAB node may send uplink data to the parent IAB node on the third set of resources 730. The third set of resources 730 may be configured as UL for the child MT to send uplink data to the parent DU. For the child DU, the third set of resources 730 may be configured as NA to prevent the child DU from interfering with the child MT sending uplink data to the parent DU. The third set of resources 730 may be configured as hard for the parent DU so that the parent DU may decide whether to use these resources to receive uplink data from the child node regardless of the operation of the MT of the parent IAB device.

[0092] Since the child IAB node uses its MT to communicate on the first group of resources 710 and uses its DU to communicate on the second group of resources 720, the child IAB node performs a transition between its MT and DU between the two groups of resources at time 714. Similarly, since the child IAB node uses its DU to communicate on the second group of resources 720 and uses its MT to communicate on the third group of resources 730, the child IAB node performs a transition between its DU and MT between the two groups of resources at time 724.

[0093] The parent IAB device and the child IAB node may utilize protection symbols at transition times (e.g., time 714 and time 724). The protection symbol may be a resource on which nothing is sent. The IAB node may utilize one or more different components (e.g., different transmitters, different receivers, or different antennas) and / or different analog beams for its MT and its DU. The protection symbol may provide time for the IAB node to switch between components for the MT and components for the DU. The protection symbol may also prevent conflicts caused by the MT and DU of the IAB node both being operated simultaneously (e.g., due to propagation delay or timing advance).

[0094] For example, Figure 7 As shown, although the parent DU sends downlink data on the first set of resources 710, the transmission may actually be received at the child IAB node on the resource 712 slightly delayed than the first set of resources 710. Some resources 712 overlap with the second set of resources 720, and the child MT is configured to send downlink data to another device on the second set of resources. The protection symbol at the end of the resource 710 provided by the parent DU and / or at the beginning of the resource 740 provided by the child DU can allow the child node to change from using MT to receive downlink data to use DU to send downlink data without conflict. The uplink data sent from the child IAB node to the parent DU on the resource 732 may face similar challenges, and the protection symbol at the end of the resource 740 provided by the child DU and / or at the beginning of the resource 730 provided by the parent DU can allow the child IAB node to change from using DU to send downlink data to use MT to send uplink data without conflict.

[0095] Figure 8 800 is a table showing the types of IAB node transitions. The transition type may be based on the resource configuration immediately before and immediately after the transition. A given resource may be configured for use by an MT or for use by a DU. Resources configured for use by an MT may be configured for receiving downlink data (DL Rx) from a parent or for sending uplink data (UL Tx) to a parent. Resources configured for a DU may be configured for sending downlink data (DL Tx) to a child or for receiving uplink data (UL Rx) from a child.

[0096] The transition from receiving downlink data (DL Rx) using MT to sending downlink data (DL Tx) using DU may be referred to as a type 1 transition. The transition from receiving downlink data (DL Rx) using MT to receiving uplink data (UL Rx) using DU may be referred to as a type 2 transition. The transition from sending uplink data (UL Tx) using MT to sending downlink data (DL Tx) using DU may be referred to as a type 3 transition. The transition from sending uplink data (UL Tx) using MT to receiving uplink data (UL Rx) using DU may be referred to as a type 4 transition. The transition from sending downlink data (DL Tx) using DU to receiving downlink data (DL Rx) using MT may be referred to as a type 5 transition. The transition from sending downlink data (DL Tx) using DU to sending uplink data (UL Tx) using MT may be referred to as a type 6 transition. The transition from receiving uplink data (UL Rx) using DU to receiving downlink data (DL Rx) using MT may be referred to as a type 7 transition. The transition from receiving uplink data (UL Rx) using the DU to sending uplink data (UL Tx) using the MT may be referred to as a Type 8 transition.

[0097] The number of protection symbols provided at the transition time can be based on the transition type of the transition. The number of symbols provided for a given transition type can be based on the switching and signal propagation requirements of the transition. For example, in some aspects, the transitions of types 1, 4, 5, and 8 can receive protection symbols to provide switching from a transmitter to a receiver. In some aspects, the transitions of types 1 and 2 can receive protection symbols to provide propagation delays based on the distance from the parent IAB device. In some aspects, the transitions of types 7 and 8 can receive protection symbols to provide propagation delays based on the distance from the child IAB node or UE. In some aspects, the transitions of types 1 to 8 can receive protection symbols to provide switching antennas. The number of protection symbols provided for a given transition type can be based on the GuardSymbolsDesired signal sent from the child IAB node to the parent IAB device and based on the GuardSymbolsProvided signal sent from the parent IAB device to the child IAB node, which will be discussed further below.

[0098] Fig. 99 is a communication diagram 900 showing guard symbol signaling between a child IAB node 902 and a parent IAB device 904. The guard symbols for a transition may be located on the resources immediately before the transition, the resources immediately after the transition, or may be split between the resources immediately before the transition and the resources immediately after the transition. The child IAB node 902 and the parent IAB device 904 may communicate to determine how many guard symbols the child IAB node 902 will provide and how many guard symbols the parent IAB device 904 will provide.

[0099] The child IAB node 902 may have a set of GuardSymbolDesired values ​​corresponding to different transition types, such as those described above with respect to Figure 8 Types 1 to 8 described. The GuardSymbolsDesired value may identify the number of guard symbols that should be provided for the child IAB node 902 to perform the transition of that type. The child IAB node 902 may send a GuardSymbolsDesired signal 910 to the parent IAB device 904. The GuardSymbolsDesired signal 910 may include some or all GuardSymbolsDesired values ​​corresponding to the transmission type. In some aspects, the GuardSymbolsDesired signal 910 may include one or more medium access control (MAC) control elements (MACCEs). In some aspects, if a value for a transition type is not included, zero guard symbols may be provided for the transition type.

[0100] The parent IAB device 904 may send a GuardSymbolsProvided signal 920 to the child IAB node 902. The GuardSymbolsProvided signal 920 may include a GuardSymbolsProvided value corresponding to a transition type, such as transition types 1 to 8. The GuardSymbolsProvided value for a transition type may indicate the number of guard symbols that the parent IAB device 904 will provide when the child IAB node 902 performs that type of transmission. The value included in the GuardSymbolsProvided signal 920 for the transition type may be equal to or less than the value included in the GuardSymbolsDesired signal 910 for the transition type. In some aspects, the value included in the GuardSymbolsProvided signal 920 may be based on resource utilization and / or performance impact. In some aspects, if a value for a transition type is not included, the parent IAB device 904 may provide zero guard symbols for that type of transition.

[0101] When the child IAB node 902 performs a transition between using its MT and using its DU, the child IAB node 902 and the parent IAB device 904 will provide protection symbols based on the GuardSymbolsDesired and GuardSymbolsProvided values. Since the transition is between the use of the DU of the child IAB node 902 and the MT of the child IAB node 902, the transition will be adjacent to a set of resources allocated to the MT for communication between the child IAB node 902 and the parent IAB device 904 and a second set of resources allocated to the DU for communication between the child IAB node 902 and the child in the child IAB node 902. The parent IAB device 904 and the child IAB node 902 will not send or receive on the protection symbols allocated to the MT, and the number of the protection symbols will be based on the GuardSymbolsProvided value of the transition type. The child IAB node 902 will not transmit or receive on the guard symbols allocated to the DU, the number of which will be based on the value of GuardSymbolsProvided and the value of GuardSymbolsDesired for the transition type. In some aspects, the number of guard symbols provided by the child IAB node 902 on the DU can be the difference between GuardSymbolsDesired and GuardSymbolsProvided.

[0102] For example, Fig. 10A 1000 is a diagram illustrating guard symbols at a transition from a DU to a MT. A child IAB node may transition from using its DU to using its MT at a transition time 1010. The GuardSymbolsDesired value for a transition type of transition may be four, and the GuardSymbolsProvided value may be two. Because the GuardSymbolsProvided value is two, neither the parent IAB device nor the child IAB node may transmit on the two symbols 1020 after the transition time 1010. Because the GuardSybolsDesired value is four, and two guard symbols are provided on resources after the transition time 1010, the child IAB node may not transmit or receive on the two symbols before the transition time 1010, resulting in four guard symbols 1030 for the transition. During the time associated with the four guard symbols 1030, the child IAB node may switch from operation of its DU to operation of its MT.

[0103] In another example, Fig. 10B1050 is a diagram showing guard symbols at a transition from MT to DU. A child IAB node may transition from using its MT to using its DU at a transition time 1060. The GuardSymbolsDesired value for a transition type of transition may be four, and the GuardSymbolsProvided value may be two. Because the GuardSymbolsProvided value is two, neither the parent IAB device nor the child IAB node may transmit on the two symbols 1070 before the transition time 1060. Because the GuardSybolsDesired value is four, and two guard symbols are provided on resources before the transition time 1060, the child IAB node may not transmit or receive on the two symbols after the transition time 1060, resulting in four guard symbols 1080 for the transition. During the time associated with the four guard symbols 1080, the child IAB node may switch from operation of its MT to operation of its DU.

[0104] Fig.11 is a diagram 1100 showing communications between a child IAB node and its parent.

[0105] As described above, the parent IAB device may provide guard symbols to allow the child IAB node to transition between the use of its MT and the use of its DU. GuardSymbolsDesired may indicate the number of guard symbols that the child IAB node expects from the parent IAB device at each transition instance based on the transition type, and GuardSymbolsProvided may indicate the number of guard symbols provided by the parent IAB device at each transition instance based on the transition type. Both the parent IAB device and the child IAB node should make the same determination when a transition instance occurs and the type of transition to transition so that the parent IAB device can include the appropriate number of guard symbols and the child IAB can correctly utilize the provided guard symbols. Therefore, the parent IAB device and the child IAB node should use the same information to determine the transition instance and the transition type.

[0106] The following may be defined based on the transmission or reception status of the child MT and the child DU: Figure 8 The child MT is scheduled by the parent IAB device, and both the parent IAB device and the child IAB node may know the state of the child MT. The transmission or reception state of the child DU may be based on the scheduling decision of the child IAB node, while the parent IAB device may not know the scheduling decision.

[0107] For example, Fig.11As shown, during the first time period 1110, the resource 1114 can be configured as hard for the DU of the parent IAB device to send downlink data to the MT of the child IAB node, and the resource 1114 can be configured as NA for the DU of the child IAB node to prevent interference with the MT of the child IAB node receiving downlink data. During the second time period 1120, the resource 1124 can be configured as NA for the DU of the parent IAB device, and can be configured as hard for the DU of the child IAB node to send downlink data to the child of the child IAB node. During the first time period 1110, the parent IAB node knows that the child IAB node is utilizing its MT. During the second time period 1120, the child IAB node can utilize the resource 1124 to utilize its DU for transmission, or may not transmit on the resource 1124. If the child IAB node does transmit on the resource 1124, it will transition from utilizing its MT during the time period 1110 to utilizing its DU in the time period 1120. The child IAB node does not transition if it does not transmit on resource 1124. Because the parent IAB device does not know whether the child IAB node will transmit on resource 1124, the parent IAB device cannot determine whether the child IAB node will actually transition between usage of its MT and usage of its DU.

[0108] The parent IAB device may know the resource configuration of the child DU (hard / soft / NA, DL / UL / F), the cell-specific signals of the child DU (e.g., synchronization signal block (SSB), channel state information reference signal (CSI-RS), physical random access channel (PRACH), scheduling request (SR)), and the NA of the child DU or soft resources with cell-specific signals will be considered configured as hard. In some aspects, the parent IAB device may identify potential transition instances based on the resource configuration of the child DU and may apply protection symbols based on the identified potential transition instances. Since the parent IAB device may not know the actual transmission or reception state of the child DU, the parent IAB device may not be able to accurately determine the transition instance, which is only a subset of the potential transition instances that the parent IAB device can identify.

[0109] In some aspects, the parent IAB device may determine whether to provide a guard symbol based on whether the resource configuration at the DU of the child IAB node implies that the resource will be used by the MT of the child IAB node (e.g., associated with the use of the MT of the child IAB node) or implies that the resource will be used by the DU of the child IAB node (e.g., associated with the use of the DU of the child IAB node). For example, when the DU of the child IAB node will transition between resources associated with the use of the MT of the child IAB node and resources associated with the use of the DU of the child IAB node at a transition time, the parent IAB device may determine to provide a guard symbol at the transition time.

[0110] In some aspects, if a resource is configured as NA or as a soft resource that is not explicitly available to a DU of a child IAB node, the resource may be a “resource associated with use of a MT of a child IAB node”, where the MT of the child IAB node is allocated to communicate with a parent IAB device. If a resource is configured to explicitly indicate a hard or soft resource that is available for use by a DU of a child IAB node, the resource may be a “resource associated with use of a DU of a child IAB node”.

[0111] In some aspects, the transition between resources associated with the use of the MT and resources associated with the use of the DU may include four cases: Case 1, the resources of the DU of the child IAB node transition between being configured as NA (and the MT of the child IAB node is allocated to communicate with the parent IAB device) and being configured as hard; Case 2, the resources of the DU of the child IAB node transition between being configured as NA (and the MT of the child IAB node is allocated to communicate with the parent IAB device) and being configured as soft resources explicitly indicated as available; Case 3, the resources of the DU of the child IAB node transition between being configured as soft resources not explicitly indicated as available (and the MT of the child IAB node is allocated to communicate with the parent IAB device) and being configured as hard; and Case 4, the resources of the DU of the child IAB node transition between being configured as soft resources not explicitly indicated as available (and the MT of the child IAB node is allocated to communicate with the parent IAB device) and being configured as soft resources explicitly indicated as available.

[0112] In some aspects, the parent IAB device may identify potential transition instances of the child IAB node and provide protection symbols based on whether the change in resource configuration at the child DU falls into one of cases 1 to 4. In some aspects, the parent IAB device may identify potential transition instances of the child IAB node and provide protection symbols in all cases 1 to 4. In some aspects, the parent IAB device may identify potential transition instances of the child IAB node and provide protection symbols in a subset of any cases. For example, in some aspects, the parent IAB device may identify potential transition instances of the child IAB node and provide protection symbols for cases 2 to 4, which involves soft resources and may not identify potential transition instances of the child IAB node and provide protection symbols for case 1, or may identify potential transition instances of the child IAB node and provide protection symbols for case 1, but may not identify potential transition instances of the child IAB node and provide protection symbols for cases 2 to 4.

[0113] Fig.12 1200 is a diagram illustrating communication between a child IAB node and its parent, including DU resources with cell-specific signals. In some aspects, when a cell-specific signal is assigned to one of the resources (e.g., it may be a resource associated with the use of the DU of the child IAB node), the resource configured as NA or soft resource for the DU of the child IAB node may be considered hard. This configuration may be available to the parent IAB device. In some aspects, a group of resources is configured as NA or soft resource for the DU of the child IAB node, wherein the cell-specific signal is assigned to one of the group of resources, and the group of resources may be associated with the use of the DU. The parent IAB node may provide protection symbols accordingly.

[0114] For example, in Fig.12 In the embodiment, for a first set of resources 1214 in a first time period 1210, the parent DU is configured as hard and the child DU is configured as NA. The parent DU can communicate with the MT of the child IAB node on the resources 1214. The child DU can be semi-statically or dynamically assigned as NA. For a second set of resources 1224 in a second time period 1220, the parent DU is configured as hard and the child DU is configured as NA.

[0115] The resource 1214 may be associated with the usage of the MT because the resource 1214 is configured to be NA for the child DU and the child MT is allocated to communicate with the parent DU.

[0116] A cell-specific signal for the child IAB node may be allocated to at least one resource 1228 in the resources 1224. Therefore, since the resource 1224 is configured to be NA for the child DU but the resource 1228 in the resources 1224 is configured to receive the cell-specific signal of the child DU, the resource 1224 may be associated with the use of the DU.

[0117] Because resource 1214 is associated with usage of the MT and resource 1224 is associated with usage of the DU, the parent IAB device may provide a guard symbol at a transition between resource 1214 and resource 1224 .

[0118] Fig.13 is a diagram 1300 illustrating communications between a child IAB node and its parent including DU resources with cell-specific signals.

[0119] exist Fig.13 , for a first set of resources 1314 in a first time period 1310, the parent DU is configured as NA and the child DU is configured as hard. The parent DU may communicate with the MT of the child IAB node on the resources 1314. For a second set of resources 1324 in a second time period 1320, the parent DU is configured as hard and the child DU is configured as NA. The child DU may be semi-statically assigned as NA.

[0120] The resource 1314 may be a resource associated with the use of the DU of the child IAB node because the resource 1314 is configured to be hard for the child DU.

[0121] A cell-specific signal for the child IAB node may be allocated to at least one resource 1328 in the resources 1324. Therefore, since the resource 1324 is configured to be NA for the child DU but the resource 1328 in the resources 1324 is configured to receive the cell-specific signal of the child DU, the resource 1324 may be a resource associated with the use of the DU of the child IAB node.

[0122] Because resource 1314 is associated with the use of a DU and resource 1324 is associated with the use of a DU, the parent IAB device may not be able to identify potential transition instances and / or may not be able to provide protection symbols at the transition between resource 1314 and resource 1324 .

[0123] Fig.14 is a diagram 1400 showing communications between a child IAB node and its parent including dynamically scheduled resources.

[0124] In some aspects, such as when the child MT is dynamically scheduled by the parent IAB device to communicate with the parent DU, the parent DU and the child DU may receive conflicting resource allocations. For example, the resources may be configured to be hard for the parent DU and hard for the child DU. In the case where the resources are scheduled as hard for both the parent DU and the child DU, the child IAB node (e.g., the child DU) may determine whether to give the child MT priority to communicate with the parent DU or give the child DU priority to communicate with the grandchild IAB device (e.g., the child IAB device of the child IAB node). In some aspects, when the child MT is dynamically scheduled to communicate with the parent DU on a set of resources (the set of resources is configured to be explicitly indicated as hard or soft for use by the child DU) and there is no cell-specific signal for the child DU allocated to the set of resources, the resource may be a resource associated with the use of the MT of the child IAB node.

[0125] For example, in Fig.14 1410, the child DU may be configured to be hard for resources 1414 in a first time period 1410. The parent IAB device may dynamically schedule one or more of the resources 1414 for the child MT to communicate with the parent DU during the time period 1410, and the resources 1414 may be configured to be hard for the parent DU. There may not be any cell-specific signals for the child IAB node assigned to the resources 1414. The parent DU may be configured to be NA for resources 1424 in a second time period 1420, and the child DU may be configured to be hard for resources 1424 in the second time period 1420.

[0126] Because resource 1414 is configured as hard for child DUs, child MTs are dynamically scheduled to communicate with parent DUs on resource 1414, and there is no cell-specific signal for child DUs allocated to resource 1414, resource 1414 may be a resource associated with usage of MTs of a child IAB node.

[0127] The resource 1424 may be associated with the usage of the DU because the resource 1424 is configured to be hard for the child DU.

[0128] Because resource 1414 is associated with usage by the MT and resource 1424 is associated with usage by the DU, the parent IAB device may identify potential transition instances and / or may provide guard symbols at the transition between resource 1414 and resource 1424 .

[0129] Fig.15 1500 is a diagram illustrating the communication between a child IAB node and its parent (including dynamically scheduled resources). Fig.151510, the child DU may be configured to be hard for resources 1514 in a first time period 1510. The parent IAB device may dynamically schedule one or more of the resources 1514 for the child MT to communicate with the parent DU during the time period 1510, and the resources 1514 may be configured to be hard for the parent DU. There may not be any cell-specific signals for the child IAB node assigned to the resources 1514. The parent DU may be configured to be hard for resources 1524 in a second time period 1520, the child DU may be configured to be NA for the resources 1524 in the second time period 1520, and the child MT may be assigned to communicate with the parent DU on the resources 1524 during the time period 1520.

[0130] Because resource 1514 is configured as hard for child DUs, child MTs are dynamically scheduled to communicate with parent DUs on resource 1514, and there is no cell-specific signal for child DUs allocated to resource 1514, resource 1514 may be a resource associated with usage of MTs of a child IAB node.

[0131] The resource 1524 may be associated with the usage of the MT because the resource 1524 is configured to be hard for the descendant DU.

[0132] Because resource 1514 is associated with the use of MT and resource 1524 is associated with the use of MT, the parent IAB device may not be able to identify potential transition instances and / or may not be able to provide protection symbols at the transition between resource 1514 and resource 1524.

[0133] When the parent IAB device provides a protection symbol, the parent IAB device and the child IAB node may give up sending on the protection symbol. The parent IAB device may be allocated to send or receive cell-specific signals, such as synchronization signal blocks (SSBs), periodic channel state information reference signals CSI-RS, physical random access channels (PRACHs), or scheduling requests (SRs). The parent IAB device may have one or more cell-specific signals for the parent IAB device that has been determined to provide it as a resource scheduling of a protection symbol for the parent generation. In some aspects, in the case where the parent IAB device has determined that the resource allocation provided as a protection symbol is used for the cell-specific signal of the parent IAB device, the parent IAB node may cancel the provision of the protection symbol. Then, the parent IAB node may send or receive a cell-specific signal on the canceled protection symbol. In some aspects, the child IAB node may also send or receive on the canceled protection symbol.

[0134] The MT of the parent IAB device can allocate resources for communication with the child IAB node through dynamic scheduling. In some aspects, the dynamic scheduling authorization may conflict with the provided protection symbol. For example, in some aspects, the dynamic scheduling authorization can utilize a time slot-based allocation, the dynamically scheduled resources can start within the first three or four resources at the beginning of the time slot, and the parent IAB device can provide zero to four protection symbols at the beginning of the time slot, wherein the time slot includes MT-associated resources, and the previous time slot includes DU-associated resources. In some aspects, in the case where the parent IAB node determines to provide a protection symbol in the time slot dynamically scheduled by the parent IAB node, the parent IAB node can determine to provide multiple protection symbols so that the number of protection symbols is less than or equal to the number of protection symbols before the resources scheduled by the dynamic scheduling authorization. In some aspects, in the case where the parent IAB node determines to provide a protection symbol in the time slot dynamically scheduled by the parent IAB node, the parent IAB node can determine whether the dynamic scheduling authorization overlaps with the provided protection symbol and can determine that if it overlaps with the provided protection symbol, the dynamic scheduling authorization is canceled. In some aspects, in the event that a child IAB node receives a dynamic scheduling grant from a parent IAB device that conflicts with a protection symbol provided by the parent IAB node, the child IAB node may discard the received dynamic scheduling grant.

[0135] The child IAB node may be scheduled to transmit or receive a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH). In some aspects, in the case where the child IAB node is scheduled to transmit or receive a PDSCH or a PUSCH on resources that the parent IAB node has provided as guard symbols, the child IAB device may puncture the provided guard symbols and may attempt to receive the PDSCH or transmit the PUSCH on the punctured guard symbols.

[0136] Fig.16 16 is a communication flow diagram illustrating providing protection symbols based on optional signaling. The IAB network includes an IAB donor 1602, a parent IAB node 1604, and a child IAB node 1606.

[0137] As described above, the actual transition instance between the MT and the DU of the child IAB node 1606 may depend on the dynamic decision of the child IAB node 1606 that is unknown to the parent IAB node 1604, so the parent IAB node 1604 and the child IAB node 1606 may identify the potential transition instance of the child IAB node 1606, and the parent IAB node 1604 may provide a plurality of protection symbols based on the resource configuration before and after the transition. For example, the number of protection symbols provided at the potential transition instance may be based on the MT time slot configuration and scheduling information of the child IAB node 1606, the DU resource configuration for the child IAB node 1606, the allocation of the selected cell-specific signal or channel for the DU of the child IAB node 1606, and / or the explicit availability of the soft resources of the child IAB node 1606.

[0138] The child IAB node 1606 and the parent IAB node 1604 may independently determine the number of protection symbols to be provided by the parent IAB node 1604. To reach the same conclusion, the child IAB node 1606 and the parent IAB node 1604 may utilize the same information when determining and classifying potential transition instances (e.g., information available at both the child IAB node 1606 and the parent IAB node 1604 may be utilized). Some information that may be useful when determining or classifying potential transition instances (e.g., DU resource configuration of the child IAB node 1606 or allocation of selected cell-specific signals or channels for DUs of the child IAB node 1606) may optionally be available at the parent IAB node 1604, but not necessarily at the parent IAB node 1604.

[0139] The CU of the IAB donor 1602 may or may not send an optional signaling message 1610 to the parent IAB node 1604. The optional signaling message 1610 may convey to the parent IAB node 1604 information that may be useful in determining or classifying potential transition instances of the child IAB node 1606. For example, the optional signaling message 1610 may convey to the parent IAB node 1604 the DU resource configuration of the child IAB node 1606 or the allocation of a selected cell-specific signal or channel for the DU of the child IAB node 1606. In some aspects, there may be multiple optional signaling messages that the CU of the IAB donor 1602 may send to the parent IAB node 1604, and each optional signaling message may or may not be sent independently of the other optional signaling messages.

[0140] A parent knowledge message 1620 may be sent to a child IAB node 1606. The parent knowledge message 1620 may be sent by a CU of the IAB donor 1602 (e.g., as an RRC or F1-AP message on an F1 interface) or may be sent by a parent IAB node 1604 (e.g., as a medium access control element (MAC-CE)). The parent knowledge message 1620 may indicate to the child IAB node 1606 whether the parent IAB node 1604 has information useful for determining or classifying a potential transition instance. In some aspects, the parent knowledge message 1620 may indicate whether an optional signaling message 1610 was sent (or, in the case of multiple optional signaling messages, which optional signaling messages were sent). In some aspects, the parent knowledge message 1620 may indicate a rule set used in determining and / or classifying a transition instance, and the rule set may be selected based on information available to the parent IAB node 1604 via the optional signaling message 1610. In some aspects, the parent knowledge message 1620 may include an indication of the location of an upcoming potential transition instance.

[0141] As shown at 1632, the parent IAB node 1604 can determine the potential transition instance of the child IAB node 1606 and can determine the number of protection symbols to be provided at the potential transition instance. If the optional signaling message 1610 is received from the IAB donor 1602, the determination can be made based on the information received in the optional signaling message 1610. As shown at 1634, the child IAB node 1606 can independently determine the potential transition instance of the child IAB node 1606 and can determine the number of protection symbols to be provided by the parent IAB node 1604. Based on the parent knowledge message 1620, the determination can be made based on the same information used by the parent IAB node 1604. As shown at 1642, the parent IAB node 1604 can provide the determined number of protection symbols on the transmission 1644 between the child IAB node 1606 and the parent IAB node 1604 at the potential transition instance.

[0142] Fig.17 is a communication diagram 1700 illustrating protection symbol signaling and transition instances between a child IAB node 1702 and a parent IAB device 1704. In some aspects, the child IAB node 1702 and the parent IAB device 1704 may specify at which transition instances protection symbols should or will be provided.

[0143] The child IAB node 1702 may send a GuardSymbolsDesired signal 1710 to the parent IAB device 1704 indicating the number of guard symbols for different transition types, and the parent IAB device 1704 may send a GuardSymbolsProvided signal 1720 to the child IAB node 1702 indicating the number of guard symbols that the parent IAB device will provide for different transmission types. For example, this may be as described above with respect to Fig. 9 Perform as described.

[0144] As shown at 1725, the child IAB node 1702 can determine the transition instance to request the protection symbol. The child IAB node 1702 can determine that the protection symbol is not requested for each transition it performs. For example, the child IAB node 1702 can determine that the child IAB node can provide protection symbols for certain transitions without receiving protection symbols from the parent IAB device, or the child IAB node 1702 can determine that certain transitions do not require protection symbols. The protection symbol may not be used for communication, which may reduce resource utilization. If the protection symbol is provided by the parent IAB device 1704, the resource utilization of the backhaul link between the parent IAB device 1704 and the child IAB node 1702 (e.g., between the parent DU and the child MT) may be reduced. If the protection symbol is provided by the child IAB node 1702, the resource utilization for the child link (e.g., between the child DU and the MT of the grandchild IAB device) may be reduced. To balance resource utilization between the parent backhaul link and the child link, the child IAB node 1702 may request protection symbols from the parent node for a subset of transition instances, and may provide protection symbols for the remaining transition instances themselves. The child IAB node 1702 may determine that it will request protection symbols from the parent IAB device 1704 for other transition instances.

[0145] The parent IAB device 1704 may not know all the scheduling information for the child IAB node 1702. For example, the parent IAB device 1704 may know the semi-static resource configuration for the resources for the child IAB node 1702 (e.g., configured as hard, soft or NA, and TDD), but may not know more detailed scheduling information. The parent IAB device 1704 may not accurately identify each transition instance. In some aspects, the child IAB node 1702 may request protection symbols for the transition instance based on the scheduling information of the child IAB node 1702 (e.g., based on the slot format indication (SFI) of the child IAB node or the scheduling plan of the resources).

[0146] Based on the knowledge available to the parent IAB device 1704, some transition instances may be ambiguous for the parent IAB device 1704. For example, in the case where the symbol of the DU adjacent to the transition instance and allocated to the child IAB node 1702 is configured as flexible, the parent IAB node may not know what type of transition the resource instance will have. In some aspects, requesting a protection symbol for the transition instance may resolve the ambiguity or may include additional information that resolves the ambiguity. For example, requesting a protection symbol for the transition instance may indicate the transition type of the transition instance. The child IAB node 1702 may determine the transition type of the transition instance based on the SFI and / or scheduling information of the child DU.

[0147] The child IAB node 1702 may send a transition instance desired signal 1730 to the parent IAB device 1704. The transition instance desired signal 1730 may identify a set of transition instances at which the child IAB node 1702 will transition between use of its MT and use of its DU, and the child IAB node 1702 determines at 1725 to request protection symbols from the parent IAB device 1704.

[0148] The transition instance expectation signal 1730 may include a transition time for the identified transition instance. In some aspects, the transition instance expectation signal 1730 may include a bitmap identifying the transition time of the transition instance. In some aspects, the bitmap may include bits corresponding to each instance in which the child IAB node 1702 transitions between its MT and its DU, and the value of a given bit may indicate whether the child IAB node 1702 is requesting a protection symbol for the transition. In some aspects, the bits of the bitmap may correspond to resources (e.g., each bit is a time slot or a symbol), and the value of a given bit may indicate whether the transition will occur at a resource for which the child IAB node 1702 requests a protection symbol. In some aspects, the transition instance expectation symbol may include a set of resource indexes identifying the resource at which the transition will occur, and the child IAB node 1702 requests a protection symbol for the resource.

[0149] The transition instance desired signal 1730 may also include additional information for each indicated transition instance. In some aspects, the transition instance desired signal 1730 may identify the transition type of the identified transition instance. The transition type may be the transition type described above with respect to Figure 8The child IAB node 1702 may be able to provide a transition type for a transition instance based on information that is not available to the parent IAB device 1704 (such as MAC layer scheduling information of the child IAB node), so the child IAB node 1702 can provide a transition type for a transition instance when the information is not available to the parent IAB device 1704. The parent IAB device 1704 can use the transition type to determine whether to provide a protection symbol for the transition instance, or to determine how to provide a protection symbol for the transition instance, for example, as described above with respect to Fig. 9 as described.

[0150] In some aspects, the transition instance desired signal 1730 may include a composite transition type for the identified transmission instance. The composite transition type may include the Figure 8 One or more of the transition types 1 to 8 described above. For example, the composite transition type for a given transition instance may identify transition type 2 (transitioning from DL resources on the MT to UL resources on the DU) and transition type 1 (transitioning from DL resources on the MT to DL resources on the DU). In some aspects, the child IAB node 1702 may request protection symbols for a transition that includes flexible resources (e.g., allocated to the DU) adjacent to the transition time. The child IAB node 1702 may send a transition instance expectation signal 1730 to the parent IAB device 1704 before determining whether to convert the flexible resource to UL or to DL. The transition instance expectation signal 1730 may include a composite transition type that indicates a transition type that will occur if the flexible resource is converted to UL and a transition type that will occur if the flexible resource is converted to DL.

[0151] The parent IAB device 1704 may utilize the composite transition type to determine whether to provide a guard symbol for a transition instance, or to determine how many guard symbols to provide for a transition instance. For example, the parent IAB device 1704 may determine a guard symbol request value for each transition type identified in the composite transition type (e.g., based on the GuardSymbolsDesired signal 1710), and may select one of these values. In some aspects, the parent IAB device 1704 may select the highest value. In some aspects, the parent IAB device 1704 may select the lowest value.

[0152] In some aspects, the transition instance desired signal 1730 may include an index for the identified transmission instance. The index may correspond to a predefined or preconfigured set of values ​​for the number of requested protection symbols. The parent IAB device 1704 may utilize the index to determine the protection symbols requested for the transition instance based on a predefined or preconfigured set of values.

[0153] In some aspects, the information for the transition included in the transition instance expectation signal 1730 can depend on the characteristics of the indicated transition. For example, the included information can be based on the transition type of the transition or based on the number of gap symbols requested for the transition type. In some aspects, the transition instance expectation signal 1730 can include multiple transition instance expectation signals corresponding to different transition types, and the transition instance expectation signal for a given transition type can indicate a transition instance with a given transition type. In some aspects, the transition instance expectation signal 1730 can include multiple transition instance expectation signals corresponding to different numbers of protection symbols to be provided for the identified transmission instance.

[0154] In some aspects, as shown at 1735, the parent IAB device 1704 may determine the transition instance to provide protection symbols. The selection criteria may be based on factors including resource utilization of the parent backhaul link, resources reserved for cell-specific signals (e.g., the parent IAB device 1704 may not provide protection symbols for the transition instance due to the presence of cell-specific signals). In some aspects, the parent IAB device 1704 may determine that the transition instance is to provide protection symbols based on the transition instance indicated in the transition instance desired signal 1710 by selecting some or all of the indicated transmission instances. In some aspects, the IAB device 1704 may determine that the transmission instance is to provide protection symbols independently.

[0155] The parent IAB device 1704 may send a transition instance providing signal 1740 to the child IAB node 1702. The transition instance providing signal 1740 may identify a set of transition instances at which the parent IAB device 1704 will provide protection symbols. The transition instance providing signal 1740 may include a transition time associated with the indicated transition instance. In some aspects, the transition instance providing signal 1740 may also include a number of protection symbols for the identified transition instance, which identifies the number of protection symbols that the parent IAB device 1704 will provide at the transition instance.

[0156] The child IAB node 1702 may receive the transition instance provision signal 1740 and may utilize it to determine how many guard symbols the child IAB node 1702 will provide at each of the identified transition instances. For example, the child IAB node 1702 may compare the number of guard symbols that will be received at the transition instance with the number of guard symbols required for the transition instance and determine to provide the remaining guard symbols.

[0157] In some aspects, the transition instance expected signal 1730 and the transition instance provided signal 1740 may be a medium access control (MAC) control element (CE). The transition instance expected signal 1730 and the transition instance provided signal 1740 may indicate a periodic pattern of signals applied before receiving a new MAC CE.

[0158] In some aspects, the transition instance expected signal 1730 and the transition instance provided signal 1740 may include L1 signaling. The child IAB node 1702 may send the transition instance expected signal 1730 at the allocated physical resources, and the parent IAB device 1704 may monitor the transition instance expected signal 1730 on the allocated physical resources. The parent IAB device 1704 may send the transition instance provided signal 1740 at the allocated physical resources, and the child IAB node 1702 may monitor the transition instance provided signal 1740 at the allocated physical resources. If no signal is received, a default value may be assumed (e.g., requesting / providing protection symbols for all transition instances). If received, the transition instance identified in the transition instance expected signal 1730 and / or the transition instance provided signal 1740 may be observed within a set or preconfigured time span.

[0159] Fig.18 18 is a diagram showing communication between three IAB nodes. IAB Node 0 may be a parent node of IAB Node 1 and a grandparent node of IAB Node 2. IAB Node 1 may be a parent node of IAB Node 2. IAB Node 2 may be a child node of IAB Node 1 and a grandchild node of IAB Node 0.

[0160] IAB Node 1 may transition from use of its MT to use of its DU between the first time slot 1810 and the second time slot 1820. As described above, IAB Node 0 may provide protection symbols for IAB Node 1 when transitioning.

[0161] Between the first time slot 1810 and the second time slot 1820, the IAB node 2 may switch from the use of its DU to the use of its MT. As described above, the IAB node 1 may provide protection symbols for the IAB node 2 at the time of the switch. Since the IAB node 1 provides the protection symbols at the beginning of the second time slot 1820, the protection symbols provided by the IAB node 0 at the end of the first time slot 1810 may be redundant.

[0162] In some aspects, the IAB node may utilize the above description of Fig.17 The signaling described above is used to avoid redundant protection symbols in simultaneous multi-hop transitions. Fig.18, IAB Node 1 may determine that it will provide protection symbols for IAB Node 2 at the transition instance between the first time slot 1810 and the second time slot 1820. Therefore, when IAB Node 1 sends a transition instance desired message to IAB Node 0, it will not indicate that it requires protection symbols from IAB Node 0 at the transition instance between the first time slot 1810 and the second time slot 1820.

[0163] Fig.19 1900 is a diagram illustrating an IAB network. The IAB network includes an IAB donor 1910. The IAB nodes of the IAB network may be divided into different groups based on their hop counts from the IAB donor 1910. The hop count may be the number of IAB nodes (including itself) removed from the IAB donor 1910. A first group of IAB nodes 1920 may include IAB nodes with a hop count of 1. A second group of IAB nodes 1930 may include IAB nodes with a hop count of 2. A third group of IAB nodes 1940 may include IAB nodes with a hop count of 3. A fourth group of IAB nodes 1950 may include IAB nodes with a hop count of 4.

[0164] The IAB donor 1910 may send a configuration message to an IAB node of the IAB network. For example, the configuration message may be sent to the IAB node via an F1 interface. The configuration message may configure whether the IAB node provides protection symbols to its child IAB node. In the case where the configuration message instructs the IAB node to provide protection symbols, the IAB node may send GuardSymbolsProvided and provide the protection symbols as described above. In the case where the configuration message instructs the IAB node not to provide protection symbols, the IAB node may not provide protection symbols at the transition instance of its child IAB node.

[0165] In some aspects, in response to the configuration message directing the IAB node not to provide protection symbols, the IAB node may set all values ​​of GuardSymbolsProvided for the IAB node to zero. When the IAB node sends GuardSymbolsProvided to its child IAB node, it will indicate to the child IAB node that the IAB node will not provide protection symbols for the transition.

[0166] In some aspects, in response to a configuration message directing the IAB node not to provide guard symbols, the IAB node may not send GuardSymbolsProvided to its child IAB node, and the child IAB node may be configured to assume that zero symbols will be provided when GuardSymbolsProvided is not received.

[0167] The IAB donor 1910 may configure the IAB network so that whether the IAB node provides protection symbols at the transition instance of its child node alternates once per hop. In some aspects, the IAB donor 1910 may send a configuration message directing the IAB node to provide protection symbols to IAB nodes with even hop counts (e.g., the second group of IAB nodes 1930 and the fourth group of IAB nodes 1950), and may send a configuration message directing the IAB node not to provide protection symbols to IAB nodes with odd hop counts (e.g., the first group of IAB nodes 1920 and the third group of IAB nodes 1940). In some aspects, the IAB donor 1910 may send a configuration message directing the IAB node to provide protection symbols to IAB nodes with odd hop counts (e.g., the first group of IAB nodes 1920 and the third group of IAB nodes 1940), and may send a configuration message directing the IAB node not to provide protection symbols to IAB nodes with even hop counts (e.g., the second group of IAB nodes 1930 and the fourth group of IAB nodes 1950). Therefore, if an IAB node provides a guard symbol for the transition of its child IAB node, its parent IAB node will not provide a guard symbol at the transition instance, so redundant guard symbols can be avoided.

[0168] Fig. 20 2000 is a flow chart of a wireless communication method. The method may be performed by a child IAB node (eg, IAB node 1606).

[0169] At 2002, the child IAB node may receive a parent knowledge message indicating whether the parent IAB node of the child IAB node has received an optional signaling message. The optional signaling message may identify the resource configuration of the child IAB node to the parent IAB node or may identify the allocation of the cell-specific signal of the child IAB node to the parent IAB node. The parent knowledge message may be received from the parent IAB node. The parent knowledge message may be received from the central unit of the IAB donor. The parent knowledge message may identify a selected rule for determining a potential transition instance from a list of predefined rules based on the optional signaling message. The parent knowledge message may be carried by a medium access control control element (MAC-CE). The MAC-CE may indicate a protection symbol provided by the parent node. The parent knowledge message may be carried by an F1-AP message. The parent knowledge message may be carried by a radio resource control (RRC) message.

[0170] At 2004, the child IAB node may determine to transition between a first resource associated with usage of a mobile terminal of the child IAB node and a second resource associated with usage of a distributed unit of the child IAB node at a transition time.

[0171] At 2006, the child IAB node may determine the number of guard symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

[0172] In some aspects, the child IAB node may determine the number of guard symbols to provide at the transition time based on the determined number of guard symbols provided by the parent IAB node.

[0173] Fig.21 21 is a flow chart of a wireless communication method. The method may be performed by a parent IAB node (eg, IAB node 1604).

[0174] At 2102, the parent IAB node may receive an optional signaling message from a central unit of an IAB donor. The optional signaling message may identify resource configuration of the child IAB node to the parent IAB node or identify allocation of cell-specific signals of the child IAB node to the parent IAB node.

[0175] At 2104, the parent IAB node may send a parent knowledge message to the child IAB node indicating that the parent IAB node has received the optional signaling message.

[0176] At 2106, the parent IAB node may provide a number of guard symbols at the transition time of the child IAB node. The number of guard symbols may be based on an optional signaling message.

[0177] Fig. 22 2200 is a flow chart of a method of wireless communication. The method may be performed by an IAB donor (eg, IAB donor 1602).

[0178] At 2202, the IAB donor may send an optional signaling message to the parent IAB node. The optional signaling message may identify resource configuration of the child IAB node to the parent IAB node or may identify allocation of cell-specific signals from the child IAB node to the parent IAB node.

[0179] At 2204, the IAB donor may send a parent knowledge message to a child IAB node of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message.

[0180] Fig.23 2300 is a flow chart of a wireless communication method. The method may be performed by an IAB donor (eg, IAB donor 1910).

[0181] At 2302, the IAB donor may send a first configuration message to a first set of IAB nodes of the IAB network. The first configuration message may configure the first set of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first set of IAB nodes.

[0182] At 2304, the IAB donor may send a second configuration message to a second group of IAB nodes of the IAB network. The second configuration message may configure the second group of IAB nodes to not provide protection symbols at transition instances of child IAB nodes in the second group of IAB nodes. In some aspects, the first group of IAB nodes may be IAB nodes having an even hop count from the IAB donor, and the second group of IAB nodes may be IAB nodes having an odd hop count from the IAB donor. In some aspects, the first group of IAB nodes may be IAB nodes having an odd hop count from the IAB donor, and the second group of IAB nodes may be IAB nodes having an even hop count from the IAB donor.

[0183] Fig.24 2400 is a flow chart of a wireless communication method. The method may be performed by an IAB node (eg, an IAB node of the first group of IAB nodes 1920, the second group of IAB nodes 1930, or the third group of IAB nodes 1940).

[0184] At 2402, the IAB node may receive a configuration message from the IAB donor. The configuration message may direct the parent IAB node to provide protection symbols or not to provide protection symbols to the child IAB node of the parent IAB node. In some aspects, the parent IAB node may have an even hop count from the IAB donor. In some aspects, the parent IAB node may have an odd hop count from the IAB donor.

[0185] At 2404, the IAB node may determine a transition instance of a child IAB node of the parent IAB node, the transition instance being a transition between usage of a mobile terminal of the child IAB node and usage of a distributed unit of the child IAB node.

[0186] At 2406, if the configuration message directs the parent IAB node to provide guard symbols, the IAB node may provide guard symbols at the transition instance.

[0187] At 2408, if the configuration message directs the parent IAB node not to provide guard symbols, the IAB node may not provide guard symbols at the transition instance.

[0188] Fig.252500 is a diagram showing an example of a hardware implementation for an apparatus 2502. The apparatus 2502 may be an IAB apparatus. The apparatus 2502 may be a child IAB node and may have a parent IAB node 102 / 180. The apparatus 2502 includes a baseband unit 2504. The baseband unit 2504 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2504 may include a computer-readable medium / memory. The baseband unit 2504 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 2504, causes the baseband unit 2504 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2504 when executing the software. The baseband unit 2504 also includes a receiving component 2530, a communication manager 2532, and a sending component 2534. The communication manager 2532 includes one or more of the components shown. The components within the communication manager 2532 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2504. The baseband unit 2504 may be a component of the BS 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.

[0189] The communication manager 2532 includes a parent knowledge component 2540 that receives a parent knowledge message indicating whether the parent IAB node of the child IAB node has received an optional signaling message, such as in conjunction with Fig. 20 The communication manager 2532 also includes a transition instance component 2542 that determines to transition between a first resource and a second resource at a transition time, the first resource being associated with the use of the mobile terminal of the child IAB node, and the second resource being associated with the use of the distributed unit of the child IAB node, for example, as described in conjunction with Fig. 20 The communication manager 2532 also includes a protection symbol determination component 2544, which determines the number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message, for example, as combined with Fig. 20 Described in 2006.

[0190] The apparatus may include executing Fig. 20 The additional components of each of the blocks of the algorithm in the aforementioned flowchart of. Thus, Fig. 20Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components that are specifically configured to perform the recited process / algorithm, implemented by a processor configured to perform the recited process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0191] In one configuration, the apparatus 2502, specifically the baseband unit 2504, includes: a component for receiving a parent knowledge message, the parent knowledge message indicating whether the parent IAB node of the child IAB node has received an optional signaling message; a component for determining a transition between a first resource and a second resource at a transition time, the first resource being associated with the use of a mobile terminal of the child IAB node, and the second resource being associated with the use of a distributed unit of the child IAB node; and a component for determining the number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message. The aforementioned components may be one or more of the aforementioned components of the apparatus 2502, which are configured to perform the functions recited by the aforementioned components. As described above, the apparatus 2502 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be the TX processor 316, the RX processor 370, and the controller / processor 375, which are configured to perform the functions recited by the aforementioned components.

[0192] Fig.262600 is a diagram showing an example of a hardware implementation for an apparatus 2602. The apparatus 2602 may be an IAB apparatus. The apparatus 2602 may be a parent IAB apparatus and may have a child IAB node 102 / 180. The apparatus 2602 includes a baseband unit 2604. The baseband unit 2604 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2604 may include a computer-readable medium / memory. The baseband unit 2604 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 2604, causes the baseband unit 2604 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2604 when executing the software. The baseband unit 2604 also includes a receiving component 2630, a communication manager 2632, and a sending component 2634. The communication manager 2632 includes one or more of the components shown. The components within the communication manager 2632 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2604. The baseband unit 2604 may be a component of the BS 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.

[0193] The communication manager 2632 includes an optional signaling message component 2640 that receives optional signaling messages from the central unit of the IAB donor, such as, for example, in conjunction with Fig.21 The communication manager 2632 also includes a parent knowledge message component 2642, which sends a parent knowledge message to the child IAB node indicating that the parent IAB node has received the optional signaling message, for example, as described in conjunction with Fig.21 The communication manager 2632 also includes a protection symbol providing component 2644, which provides a plurality of protection symbols at the transition time of the child IAB node, the number of protection symbols being based on an optional signaling message, for example, as combined with Fig.21 As described in 2104.

[0194] The apparatus may include executing Fig.21 The additional components of each of the blocks of the algorithm in the aforementioned flowchart of. Thus, Fig.21 Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components that are specifically configured to perform the recited process / algorithm, implemented by a processor configured to perform the recited process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0195] In one configuration, the device 2602, specifically the baseband unit 2604, includes: a component for receiving an optional signaling message from a central unit of an IAB donor; a component for sending a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signaling message; and a component for providing a plurality of protection symbols at a transition time of the child IAB node, the number of which is based on the optional signaling message. The aforementioned components may be one or more of the aforementioned components of the device 2602, which are configured to perform the functions described by the aforementioned components. As described above, the device 2602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions described by the aforementioned components.

[0196] Fig. 27 2700 is a diagram showing an example of a hardware implementation for an apparatus 2702. The apparatus 2702 may be an IAB donor. The apparatus 2705 may communicate with a network of IAB nodes, the IAB nodes including a first IAB node 2762 and a second IAB node 2764, wherein the first IAB node 2762 may be a parent IAB node of the second IAB node 2764 and the second IAB node 2764 may be a child IAB node of the first IAB node 2762. The apparatus 2702 includes a baseband unit 2704. The baseband unit 2704 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2704 may include a computer-readable medium / memory. The baseband unit 2704 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 2704, causes the baseband unit 2704 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2704 when executing the software. The baseband unit 2704 also includes a receiving component 2730, a communication manager 2732, and a transmitting component 2734. The communication manager 2732 includes one or more of the components shown. The components within the communication manager 2732 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2704. The baseband unit 2704 may be a component of the BS 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.

[0197] The communication manager 2732 includes an optional signaling message component 2740 that sends an optional signaling message to a parent IAB node (eg, the first IAB node 2762), such as in conjunction with Fig. 22The communication manager 2732 also includes a parent knowledge message component 2742, which sends a parent knowledge message to the child IAB node (e.g., 2764) of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message, for example, as combined Fig. 22 As described in 2204.

[0198] The apparatus may include executing Fig. 22 The additional components of each of the blocks of the algorithm in the aforementioned flowchart of. Thus, Fig. 22 Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components that are specifically configured to perform the recited process / algorithm, implemented by a processor configured to perform the recited process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0199] In one configuration, the device 2702, specifically the baseband unit 2704, includes: a component for sending an optional signaling message to a parent IAB node; and a component for sending a parent knowledge message to a child IAB node in the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message. The aforementioned components may be one or more of the aforementioned components of the device 2702, which are configured to perform the functions described by the aforementioned components. As described above, the device 2702 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions described by the aforementioned components.

[0200] Fig.282800 is a diagram showing an example of a hardware implementation for an apparatus 2802. The apparatus 2802 may be an IAB donor. The apparatus 2705 may communicate with a network of IAB nodes 2862. The apparatus 2802 includes a baseband unit 2804. The baseband unit 2804 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2804 may include a computer-readable medium / memory. The baseband unit 2804 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 2804, causes the baseband unit 2804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2804 when executing the software. The baseband unit 2804 also includes a receiving component 2830, a communication manager 2832, and a sending component 2834. The communication manager 2832 includes one or more of the components shown. The components within the communication manager 2832 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2804. The baseband unit 2804 may be a component of the BS 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.

[0201] The communication manager 2832 includes a first configuration message component 2840 that sends a first configuration message to a first group of IAB nodes of the IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first group of IAB nodes, for example, as combined with Fig.23 The communication manager 2832 also includes a second configuration message component 2842, which sends a second configuration message to a second group of IAB nodes of the IAB network, and the second configuration message configures the second group of IAB nodes to not provide protection symbols at the transition instance of the child IAB node in the second group of IAB nodes, for example, as combined with Fig.23 As described in 2304.

[0202] The apparatus may include executing Fig.23 The additional components of each of the blocks of the algorithm in the aforementioned flowchart of. Thus, Fig.23 Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components that are specifically configured to perform the recited process / algorithm, implemented by a processor configured to perform the recited process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0203] In one configuration, the device 2802, specifically the baseband unit 2804, includes: a component for sending a first configuration message to a first group of IAB nodes of the IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at the transition instance of the child IAB node in the first group of IAB nodes; and a component for sending a second configuration message to a second group of IAB nodes of the IAB network, the second configuration message configuring the second group of IAB nodes to provide protection symbols at the transition instance of the child IAB node not in the second group of IAB nodes. The aforementioned components may be one or more of the aforementioned components of the device 2802, which are configured to perform the functions described by the aforementioned components. As described above, the device 2802 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions described by the aforementioned components.

[0204] Fig.29 2900 is a diagram showing an example of a hardware implementation for an apparatus 2902. The apparatus 2902 may be an IAB node. The apparatus 2902 may have a child IAB node 2964 and may be included in an IAB network having an IAB donor 2962. The apparatus 2902 includes a baseband unit 2904. The baseband unit 2904 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2904 may include a computer-readable medium / memory. The baseband unit 2904 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 2904, causes the baseband unit 2904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2904 when executing the software. The baseband unit 2904 also includes a receiving component 2930, a communication manager 2932, and a sending component 2934. The communication manager 2932 includes one or more of the components shown. The components within the communication manager 2932 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2904. The baseband unit 2904 may be a component of the BS 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.

[0205] The communication manager 2932 includes a configuration message component 2940 that receives a configuration message from an IAB donor that instructs a parent IAB node whether to provide protection symbols to a child IAB node of the parent IAB node, for example, as described in conjunction with Fig.24The communication manager 2932 also includes a transition instance determination component 2942, which determines a transition instance of a child IAB node of a parent IAB node, the transition instance being a transition between the use of a mobile terminal of the child IAB node and the use of a distributed unit of the child IAB node, for example, as combined with Fig.24 The communication manager 2932 also includes a protection symbol component 2944 that provides protection symbols at the transition instance if the configuration message instructs the parent IAB node to provide protection symbols, and does not provide protection symbols at the transition instance if the configuration message instructs the parent IAB node not to provide protection symbols, for example, as described in conjunction with Fig.24 As described in 2406 and 2408.

[0206] The apparatus may include executing Fig.24 The additional components of each of the blocks of the algorithm in the aforementioned flowchart of. Thus, Fig.24 Each block in the foregoing flow chart of can be performed by a component, and the apparatus may include one or more of these components. The component may be one or more hardware components that are specifically configured to perform the narration process / algorithm, implemented by a processor configured to perform the narration process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0207] In one configuration, the device 2902, specifically the baseband unit 2904, includes: a component for receiving a configuration message from an IAB donor, the configuration message instructing the parent IAB node whether to provide protection symbols to the child IAB node of the parent IAB node; a component for determining a transition instance of the child IAB node of the parent IAB node, the transition instance being a transition between the use of the mobile terminal of the child IAB node and the use of the distributed unit of the child IAB node; a component for providing protection symbols at the transition instance if the configuration message instructs the parent IAB node to provide protection symbols; and a component for not providing protection symbols at the transition instance if the configuration message instructs the parent IAB node not to provide protection symbols. The aforementioned components may be one or more of the aforementioned components of the device 2902, which are configured to perform the functions described by the aforementioned components. As described above, the device 2902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be the TX processor 316, the RX processor 370, and the controller / processor 375, which are configured to perform the functions recited by the aforementioned components.

[0208] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of the various blocks in a sample order, which is not meant to be limited to the specific order or hierarchy presented.

[0209] The above description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications in these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the reference element in the singular form is not intended to mean "one and only one" (unless specifically stated), but "one or more". The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" in this article is not necessarily interpreted as being more preferred or more advantageous than other aspects. Unless specifically 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 A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of one or more A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the disclosure that are known or subsequently known to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be committed to the public, regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not be a substitute for the word "component." Thus, any claim element should not be interpreted as a component plus function unless the element is explicitly recited using the phrase "component for..."

[0210] Implementation examples are described in the following numbered clauses: The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0211] 1. A method for wireless communication at a child integrated access and backhaul (IAB) node, comprising: receiving a parent knowledge message, the parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message; determining to transition between a first resource and a second resource at a transition time, the first resource being associated with use of a mobile terminal of the child IAB node and the second resource being associated with use of a distributed unit of the child IAB node; and determining a number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

[0212] 2. The method of clause 1, wherein the parent knowledge message identifies a selected rule from a list of predefined rules for determining potential transition instances based on the optional signaling message.

[0213] 3. A method according to any one of clauses 1 to 2, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals from the child IAB node to the parent IAB node.

[0214] 4. A method according to any of clauses 1 to 3, wherein the parent knowledge message is received from the parent IAB node.

[0215] 5. A method according to any of clauses 1 to 4, wherein the parent knowledge message is carried by a Medium Access Control Control Element (MAC-CE).

[0216] 6. A method according to any of clauses 1 to 5, wherein the MAC-CE indicates protection symbols provided by the parent node.

[0217] 7. A method according to any of clauses 1 to 3, wherein the parent knowledge message is received from a central unit of an IAB donor.

[0218] 8. A method according to any one of clauses 1 to 3 and 7, wherein the parent knowledge message is carried by an F1-AP message.

[0219] 9. A method according to any of clauses 1 to 3 and 7, wherein the parent knowledge message is carried by a Radio Resource Control (RRC) message.

[0220] 10. A method as described in any of clauses 1 to 9, further comprising providing a plurality of guard symbols at the transition time, the number of guard symbols being based on the determined number of guard symbols provided by the parent IAB node.

[0221] 11. An apparatus for wireless communication at a child integrated access and backhaul (IAB) node, comprising: a component for receiving a parent knowledge message, the parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message; a component for determining a transition between a first resource and a second resource at a transition time, the first resource being associated with use of a mobile terminal of the child IAB node and the second resource being associated with use of a distributed unit of the child IAB node; and a component for determining a number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

[0222] 12. An apparatus for wireless communication at a child integrated access and backhaul (IAB) node, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: receive a parent knowledge message, the parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message; determine to transition between a first resource and a second resource at a transition time, the first resource being associated with use of a mobile terminal of the child IAB node and the second resource being associated with use of a distributed unit of the child IAB node; and determine a number of protection symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

[0223] 13. An apparatus as recited in clause 12, wherein the parent knowledge message identifies a selected rule from a list of predefined rules for determining potential transition instances based on the optional signaling message.

[0224] 14. An apparatus according to any of clauses 12 to 13, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals of the child IAB node to the parent IAB node.

[0225] 15. An apparatus as described in any of clauses 12 to 14, wherein the parent knowledge message is received from the parent IAB node.

[0226] 16. An apparatus as described in any of clauses 12 to 15, wherein the parent knowledge message is carried by a Medium Access Control Control Element (MAC-CE).

[0227] 17. An apparatus as described in any of clauses 12 to 16, wherein the MAC-CE indicates protection symbols provided by the parent node.

[0228] 18. An apparatus as recited in any of clauses 12 to 14, wherein the parent knowledge message is received from a central unit of an IAB donor.

[0229] 19. An apparatus according to any of clauses 12 to 14 and 18, wherein the parent knowledge message is carried by an F1-AP message.

[0230] 20. An apparatus as described in any of clauses 12 to 14 and 18, wherein the parent knowledge message is carried by a Radio Resource Control (RRC) message.

[0231] 21. An apparatus as described in any of clauses 12 to 20, wherein the at least one processor is further configured to provide a number of guard symbols at the transition time, the number of guard symbols being based on the determined number of guard symbols provided by the parent IAB node.

[0232] 22. A non-transitory computer-readable medium storing computer-executable code for wireless communications at a user equipment, wherein the code, when executed by a processor, causes the processor to perform the method of any of clauses 1 to 10.

[0233] 23. A method for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: receiving an optional signaling message from a central unit of an IAB donor; sending a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signaling message; and providing multiple guard symbols at a transition time of the child IAB node, the number of guard symbols being based on the optional signaling message.

[0234] 24. A method according to clause 23, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals of the child IAB node to the parent IAB node.

[0235] 25. An apparatus for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: a component for receiving an optional signaling message from a central unit of an IAB donor; a component for sending a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signaling message; and a component for providing a plurality of guard symbols at a transition time of the child IAB node, the number of the guard symbols being based on the optional signaling message.

[0236] 26. An apparatus for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: receive an optional signaling message from a central unit of an IAB donor; send a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signaling message; and provide a plurality of guard symbols at a transition time of the child IAB node, the number of the guard symbols being based on the optional signaling message.

[0237] 27. An apparatus according to clause 26, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals from the child IAB node to the parent IAB node.

[0238] 28. A non-transitory computer-readable medium storing computer-executable code for wireless communications at a user equipment, wherein the code, when executed by a processor, causes the processor to perform the method according to any of clauses 23 to 24.

[0239] 29. A method for wireless communication at an integrated access and backhaul (IAB) donor, comprising: sending an optional signaling message to a parent IAB node; and sending a parent knowledge message to a child IAB node of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message.

[0240] 30. A method as described in clause 29, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals of the child IAB node to the parent IAB node.

[0241] 31. An apparatus for wireless communication at an integrated access and backhaul (IAB) donor, comprising: a component for sending an optional signaling message to a parent IAB node; and a component for sending a parent knowledge message to a child IAB node of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message.

[0242] 32. An apparatus for wireless communication at an integrated access and backhaul (IAB) donor, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: send an optional signaling message to a parent IAB node; and send a parent knowledge message to a child IAB node of the parent IAB node, the parent knowledge message indicating whether the parent IAB node has received the optional signaling message.

[0243] 33. An apparatus according to clause 32, wherein the optional signalling message identifies resource configuration of the child IAB node to the parent IAB node or identifies allocation of cell-specific signals of the child IAB node to the parent IAB node.

[0244] 34. A non-transitory computer-readable medium storing computer-executable code for wireless communications at a user equipment, wherein the code, when executed by a processor, causes the processor to perform the method of any of clauses 29 to 30.

[0245] 35. A method for performing wireless communications at an integrated access and backhaul (IAB) donor, comprising: sending a first configuration message to a first group of IAB nodes of an IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first group of IAB nodes; and sending a second configuration message to a second group of IAB nodes of the IAB network, the second configuration message configuring the second group of IAB nodes not to provide protection symbols at transition instances of child IAB nodes in the second group of IAB nodes.

[0246] 36. The method of clause 35, wherein the first set of IAB nodes are IAB nodes having an even hop count from the IAB donor, and wherein the second set of IAB nodes are IAB nodes having an odd hop count from the IAB donor.

[0247] 37. A method as recited in any of clauses 35 to 36, wherein the first set of IAB nodes are IAB nodes having an odd hop count from the IAB donor, and wherein the second set of IAB nodes are IAB nodes having an even hop count from the IAB donor.

[0248] 38. An apparatus for wireless communication at an integrated access and backhaul (IAB) donor, comprising: a component for sending a first configuration message to a first group of IAB nodes of an IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first group of IAB nodes; and a component for sending a second configuration message to a second group of IAB nodes of the IAB network, the second configuration message configuring the second group of IAB nodes to not provide protection symbols at transition instances of child IAB nodes in the second group of IAB nodes.

[0249] 39. An apparatus for wireless communication at an integrated access and backhaul (IAB) donor, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: send a first configuration message to a first group of IAB nodes of an IAB network, the first configuration message configuring the first group of IAB nodes to provide protection symbols at transition instances of child IAB nodes in the first group of IAB nodes; and send a second configuration message to a second group of IAB nodes of the IAB network, the second configuration message configuring the second group of IAB nodes to not provide protection symbols at transition instances of child IAB nodes in the second group of IAB nodes.

[0250] 40. The apparatus of clause 39, wherein the first set of IAB nodes are IAB nodes having an even hop count from the IAB donor, and wherein the second set of IAB nodes are IAB nodes having an odd hop count from the IAB donor.

[0251] 41. An apparatus as recited in any of clauses 39 to 40, wherein the first set of IAB nodes are IAB nodes having an odd hop count from the IAB donor, and wherein the second set of IAB nodes are IAB nodes having an even hop count from the IAB donor.

[0252] 42. A non-transitory computer-readable medium storing computer-executable code for wireless communications at a user equipment, wherein the code, when executed by a processor, causes the processor to perform the method of any of clauses 35 to 37.

[0253] 43. A method for performing wireless communications at a parent integrated access and backhaul (IAB) node, comprising: receiving a configuration message from an IAB donor, the configuration message instructing the parent IAB node whether to provide protection symbols to a child IAB node of the parent IAB node; determining a transition instance of a child IAB node of the parent IAB node, the transition instance being a transition between use of a mobile terminal of the child IAB node and use of a distributed unit of the child IAB node; if the configuration message instructs the parent IAB node to provide protection symbols, providing protection symbols at the transition instance; and if the configuration message instructs the parent IAB node not to provide protection symbols, not providing protection symbols at the transition instance.

[0254] 44. The method of clause 43, wherein the parent IAB node has an even hop count from the IAB donor.

[0255] 45. The method of any of clauses 43 to 44, wherein the parent IAB node has an odd hop count from the IAB donor.

[0256] 46. ​​An apparatus for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: a component for receiving a configuration message from an IAB donor, the configuration message instructing the parent IAB node whether to provide protection symbols to a child IAB node of the parent IAB node; a component for determining a transition instance of a child IAB node of the parent IAB node, the transition instance being a transition between use of a mobile terminal of the child IAB node and use of a distributed unit of the child IAB node; a component for providing protection symbols at the transition instance if the configuration message instructs the parent IAB node to provide protection symbols; and a component for not providing protection symbols at the transition instance if the configuration message instructs the parent IAB node not to provide protection symbols.

[0257] 47. An apparatus for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: receive a configuration message from an IAB donor, the configuration message instructing the parent IAB node whether to provide protection symbols to a child IAB node of the parent IAB node; determine a transition instance of a child IAB node of the parent IAB node, the transition instance being a transition between use of a mobile terminal of the child IAB node and use of a distributed unit of the child IAB node; if the configuration message instructs the parent IAB node to provide protection symbols, provide protection symbols at the transition instance; and if the configuration message instructs the parent IAB node not to provide protection symbols, do not provide protection symbols at the transition instance.

[0258] 48. The apparatus of clause 47, wherein the parent IAB node has an even hop count from the IAB donor.

[0259] 49. An apparatus as recited in any of clauses 47 to 48, wherein the parent IAB node has an odd hop count from the IAB donor.

[0260] 50. A non-transitory computer-readable medium storing computer-executable code for wireless communications at a user equipment, wherein the code, when executed by a processor, causes the processor to perform the method of any of clauses 43 to 45.

[0261] 51. The method of clause 23, wherein the parent knowledge message is carried by a Medium Access Control Control Element (MAC-CE).

[0262] 52. A method as described in any of clauses 23 and 51, wherein the MAC-CE indicates protection symbols provided by the parent node.

[0263] 53. A method according to any of clauses 23 and 51 to 52, wherein the parent knowledge message identifies a selected rule from a list of predefined rules for determining potential transition instances based on the optional signalling message.

[0264] 54. The apparatus of clause 25, wherein the parent knowledge message is carried by a Medium Access Control Control Element (MAC-CE).

[0265] 55. An apparatus as described in any of clauses 25 and 54, wherein the MAC-CE indicates protection symbols provided by the parent node.

[0266] 56. An apparatus as described in any of clauses 25 and 54 to 55, wherein the parent knowledge message identifies a selected rule from a list of predefined rules for determining potential transition instances based on the optional signaling message.

Claims

1. A method for wireless communication at a child integrated access and backhaul IAB node, comprising: receiving a parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message from a central unit of an IAB donor, wherein the parent knowledge message is received from the parent IAB node; determining to transition between a first resource and a second resource at a transition time, the first resource being associated with usage of a mobile terminal of the child IAB node, and the second resource being associated with usage of a distributed unit of the child IAB node; as well as A number of guard symbols provided by the parent IAB node at the transition time is determined based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

2. The method according to claim 1, wherein the optional signaling message identifies resource configuration from the child IAB node to the parent IAB node or identifies allocation of a cell-specific signal from the child IAB node to the parent IAB node. 3 . The method according to claim 1 , wherein the parent knowledge message is carried by a medium access control element MAC-CE. 4 . The method of claim 3 , wherein the MAC-CE indicates protection symbols provided by the parent IAB node.

5. The method of claim 1, wherein the parent knowledge message is carried by an F1-AP message. The method according to claim 1 , wherein the parent knowledge message is carried by a Radio Resource Control (RRC) message.

7. The method of claim 1, further comprising providing a plurality of guard symbols at the transition time, the number of guard symbols being based on the determined number of guard symbols provided by the parent IAB node.

8. An apparatus for wireless communication at a descendant integrated access and backhaul (IAB) node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving a parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message from a central unit of an IAB donor, wherein the parent knowledge message is received from the parent IAB node; determining to transition between a first resource and a second resource at a transition time, the first resource being associated with usage of a mobile terminal of the child IAB node, and the second resource being associated with usage of a distributed unit of the child IAB node; as well as A number of guard symbols provided by the parent IAB node at the transition time is determined based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

9. The apparatus according to claim 8, wherein the optional signaling message identifies resource configuration from the child IAB node to the parent IAB node or identifies allocation of a cell-specific signal from the child IAB node to the parent IAB node.

10. The apparatus of claim 8, wherein the parent knowledge message is carried by a medium access control element (MAC-CE).

11. The apparatus of claim 10, wherein the MAC-CE indicates protection symbols provided by the parent IAB node.

12. The apparatus of claim 8, wherein the parent knowledge message is carried by an F1-AP message.

13. The apparatus of claim 8, wherein the parent knowledge message is carried by a Radio Resource Control (RRC) message.

14. The apparatus of claim 8, wherein the at least one processor is further configured to provide a plurality of guard symbols at the transition time, the number of guard symbols being based on the determined number of guard symbols provided by the parent IAB node.

15. An apparatus for wireless communication at a parent integrated access and backhaul (IAB) node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving an optional signaling message from a central unit of an IAB donor; sending a parent knowledge message to the child IAB node indicating that the parent IAB node has received the optional signaling message; as well as A plurality of guard symbols are provided at a transition time of the child IAB node, the number of the guard symbols being based on the optional signaling message, wherein the child IAB node is capable of performing a transition between a first resource and a second resource at the transition time, the first resource being associated with use of a mobile terminal of the child IAB node, and the second resource being associated with use of a distributed unit of the child IAB node. 16 . The apparatus according to claim 15 , wherein the optional signaling message identifies resource configuration from the child IAB node to the parent IAB node or identifies allocation of a cell-specific signal from the child IAB node to the parent IAB node.

17. The apparatus of claim 15, wherein the parent knowledge message is carried by a Medium Access Control Element (MAC-CE).

18. The apparatus of claim 17, wherein the MAC-CE indicates protection symbols provided by the parent IAB node.

19. A method for wireless communication at a parent integrated access and backhaul IAB node, comprising: receiving an optional signaling message from a central unit of an IAB donor; sending a parent knowledge message to the child IAB node indicating that the parent IAB node has received the optional signaling message; as well as A plurality of guard symbols are provided at a transition time of the child IAB node, the number of the guard symbols being based on the optional signaling message, wherein the child IAB node is capable of performing a transition between a first resource and a second resource at the transition time, the first resource being associated with use of a mobile terminal of the child IAB node, and the second resource being associated with use of a distributed unit of the child IAB node.

20. An apparatus for wireless communication at a descendant integrated access and backhaul (IAB) node, comprising: means for receiving a parent knowledge message indicating whether a parent IAB node of the child IAB node has received an optional signaling message from a central unit of an IAB donor, wherein the parent knowledge message is received from the parent IAB node; means for determining to transition between a first resource and a second resource at a transition time, the first resource being associated with usage of a mobile terminal of the child IAB node and the second resource being associated with usage of a distributed unit of the child IAB node; as well as means for determining a number of guard symbols provided by the parent IAB node at the transition time based on whether the parent knowledge message indicates that the parent IAB node has received the optional signaling message.

21. An apparatus for wireless communication at a parent integrated access and backhaul IAB node, comprising: means for receiving an optional signalling message from a central unit of an IAB donor; means for sending a parent knowledge message to a child IAB node indicating that the parent IAB node has received the optional signalling message; as well as means for providing a plurality of guard symbols at a transition time of the child IAB node, the number of the guard symbols being based on the optional signaling message, wherein the child IAB node is capable of performing a transition between a first resource associated with use of a mobile terminal of the child IAB node and a second resource associated with use of a distributed unit of the child IAB node at the transition time.

22. A non-transitory computer readable medium storing computer executable code for wireless communication at a descendant integrated access and backhaul (IAB) node, wherein the code, when executed by a processor, causes the processor to perform the method of any one of claims 1-7.

23. A non-transitory computer readable medium storing computer executable code for wireless communication at a parent integrated access and backhaul (IAB) node, wherein the code, when executed by a processor, causes the processor to perform the method of claim 19.

Images