Integrated Access and Backhaul Node Configuration

Abstract

Apparatus, methods, and systems for integrated access and backhaul node configuration are disclosed. A method (800) includes receiving (802) at a first integrated access and backhaul node a resource configuration corresponding to a second integrated access and backhaul node, where the resource configuration includes information indicating soft resources. The method (800) includes obtaining (804) activation parameters corresponding to the second integrated access and backhaul node, where the activation parameters include a first value, a second value, or a combination thereof. The method (800) includes determining (806) whether the activation parameters include the first value. The method (800) includes, in response to determining that the activation parameters include the first value, sending (808) an availability indication message corresponding to a subset of the soft resources.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to wireless communication and, more particularly, to integrated access and backhaul node configurations. Background Art

[0002] The following abbreviations are defined herein, at least some of which are referred to in the following description: 3rd Generation Partnership Project (“3GPP”), 5G QoS Indicator (“5QI”), Aperiodic CSI (“A-CSI”), Availability Indicator (“AI”), Acknowledgement Mode (“AM”), Aperiodic (“AP”), IAB-specific Backhaul Adaptation Protocol (“BAP”), Backhaul (“BH”), Broadcast Multicast (“BM”), Buffer Occupancy (“BO”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Carrier Aggregation (“CA”), Component Carrier (“CC”), Clear Channel Assignment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cell Definition (“CD”), Code Division Multiplexing (“CDM”), Control Element (“CE”), Core Network (“CN”), Coordinated Multipoint (“CoMP”), Class of Requirements (“CoR”), Control Resource Set (“CORESET”), Cyclic Prefix (“CP”), Cyclic Prefix OFDM (“CP-OFDM”), Cyclic Redundancy Check (“CRC”), CSI-RS Resource Indicator (“CRI”), Cell RNTI (“C-RNTI”), Channel State Information (“CSI”), CSI IM (“CSI-IM”), CSI RS (“CSI-RS”), Common Search Space (“CSS”), Channel Quality Indicator (“CQI”), Central Unit (“CU”), Codeword (“CW”), Downlink Assignment Index (“DAI”), Dual Connectivity (“DC”), Downlink Control Information (“DCI”), Downlink (“D” or “DL”), Discrete Fourier Transform Spread (“DFTS”), Discrete Fourier Transform Spread OFDM (“DFT-s-OFDM”), Demodulation Reference Signal (“DMRS” or “DM-RS”), Data Radio Bearer (“DRB”), Dedicated Short Range Communications (“DSRC”), Distributed Unit (“DU”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Enhanced Subscriber Identity Module (“eSIM”), European Telecommunications Standards Institute (“ETSI”), Enhanced (“E”), Flexible (“F”), Frame-based Equipment (“FBE”), Frequency Division Duplexing (“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Frequency Range (“FR”), 450 MHz – 6000 MHz (“FR1”), 24250 MHz – 52600 MHz (“FR2”), Guard Period (“GP”), Hard (“H”), Hybrid Automatic Repeat reQuest (“HARQ”), Hybrid Automatic Repeat reQuest - ACKnowledgement (“HARQ-ACK”), High-Definition Multimedia Interface (“HDMI”),Integrated Access and Backhaul (“IAB”), Identity or Identifier or Identification (“ID”), Information Element (“IE”), Interference Measurement (“IM”), International Mobile Subscriber Identity (“IMSI”), Internet of Things (“IoT”), Internet Protocol (“IP”), Joint Transmission (“JT”), Level 1 (“L1”), L1 RSRP (“L1-RSRP”), L1 SINR (“L1-SINR”), Licensed-Assisted Access (“LAA”), Load-Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel ID (“LCID”), Logical Channel Prioritization (“LCP”), Layer Indicator (“LI”), Long-Term Evolution (“LTE”), Level of Automation (“LoA”), Multiple Access (“MA”), Medium Access Control (“MAC”), Master Cell Group (“MCG”), Modulation and Coding Scheme (“MCS”), Multi-DCI (“M-DCI”), Master Information Block (“MIB”), Multiple-Input Multiple-Output (“MIMO”), Message A (“MsgA”), Message B (“MsgB”), Master Node (“MN”), MsgA PUSCH Opportunity (“MPO”), Mobile Terminal (“MT”), Machine-Type Communication (“MTC”), Multi-PDSCH (“Multi-PDSCH”), Multi-TRP (“M-TRP”), Multi-User (“MU”), Multi-User MIMO (“MU-MIMO”), Multi-User Shared Access (“MUSA”), Minimum Mean Square Error (“MMSE”), Not Available (“NA”), Negative Acknowledgment (“NACK”) or (“NAK”), Narrowband (“NB”), Next Generation (“NG”), Next Generation Node B (“gNB”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Non-Supplementary Uplink (“NUL”) (e.g., “normal” uplink carrier), Non-Zero Power (“NZP”), NZP CSI-RS (“NZP-CSI-RS”), Orthogonal Frequency Division Multiplexing (“OFDM”), Orthogonal Frequency Division Multiple Access (“OFDMA”), Peak-to-Average Power Ratio (“PAPR”), Physical Broadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”), PDSCH Configuration (“PDSCH-Config”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Packet Data Convergence Protocol (“PDCP”), Pattern Division Multiple Access (“PDMA”), Packet Data Network (“PDN”), Protocol Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom Report (“PHR”), Public Land Mobile Network (“PLMN”), Precoding Matrix Indicator (“PMI”)ProSe Per-Packet Priority (“PPPP”), ProSe Per-Packet Reliability (“PPPR”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Packet Switching (“PS”), Physical Sidelink Control Channel (“PSCCH”), Physical Sidelink Shared Channel (“PSSCH”), Phase Tracking RS (“PTRS” or “PT-RS”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Indicator (“QCI”), Quasi-Co-Location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Random Access Procedure (“RACH”), Radio Access Network (“RAN”), Random Access Response (“RAR”), Radio Access Technology (“RAT”), Resource Element (“RE”), Radio Frequency (“RF”), Rank Indicator (“RI”), Radio Link Control (“RLC”), Radio Link Failure (“RLF”), Remaining Minimum System Information (“RMSI”), Radio Network Temporary Identifier (“RNTI”), Resource Pool (“RP”), Radio Resource Control (“RRC”), Remote Radio Head (“RRH”), Radio Resource Management (“RRM”), Reference Signal (“RS”), Resource Spread Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Reference Signal Received Quality (“RSRQ”), Round Trip Time (“RTT”), Receive (“RX”), Soft (“S”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Single Carrier Frequency Domain Spread (“SC-FDSS”), Secondary Cell (“SCell”), Shared Channel (“SCH”), Secondary Cell Group (“SCG”), Subcarrier Spacing (“SCS”), Sparse Code Multiple Access (“SCMA”), Single DCI (“S-DCI”), Space Division Multiplexing (“SDM”), Service Data Unit (“SDU”), Single Frequency Network (“SFN”), System Information Block (“SIB”), Subscriber Identity Module (“SIM”), Signal to Interference and Noise Ratio (“SINR”), Sidelink (“SL”), Secondary Node (“SN”), Semi-Persistent (“SP”), Specific Cell (“SpCell”) (e.g., the PCell of an MCG or SCG), SP CSI (“SP-CSI”), Scheduling Request (“SR”), SRS Resource Indicator (“SRI”), Sounding Reference Signal (“SRS”), Synchronization Signal (“SS”), Synchronization Signal / Physical Broadcast Channel (“SS / PBCH”), SS / PBCH Block (“SSB”), Supplementary Uplink (“SUL”), Transport Block (“TB”), Transport Block Size (“TBS”), Transmission Configuration Indicator (“TCI”), Temporary Cell RNTI (“TC-RNTI”), Time Division Duplex (“TDD”)Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD - OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Transmitted Precoding Matrix Indicator (“TPMI”), Transmission and Reception Point (“TRP”), Technical Standard (“TS”), Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), User Equipment / Device (Mobile Terminal) (“UE”), Universal Integrated Circuit Card (“UICC”), Uplink (“U” or “UL”), Unacknowledged Mode (“UM”), Universal Mobile Telecommunication System (“UMTS”), LTE Radio Interface (“Uu interface”), User Plane (“UP”), Ultra - Reliable Low - Latency Communication (“URLLC”), Universal Subscriber Identity Module (“USIM”), UE - Specific Search Space (“USS”), Universal Terrestrial Radio Access Network (“UTRAN”), Vehicle - to - Everything (“V2X”), Voice over IP (“VoIP”), Visited Public Land Mobile Network (“VPLMN”), Vehicle RNTI (“V - RNTI”), Worldwide Interoperability for Microwave Access (“WiMAX”), Zero - Forcing (“ZF”), Zero Power (“ZP”), and ZP - CSI - RS (“ZP - CSI - RS”). As used herein, “HARQ - ACK” may collectively represent an Acknowledgment (“ACK”) and a Negative Acknowledgment (“NAK”). ACK means that the Transport Block (TB) was correctly received, while NAK means that the TB was incorrectly received.,

[0003] In some wireless communication networks, integrated access and backhaul nodes may be used. Summary of the Invention

[0004] Methods for integrated access and backhaul node configuration are disclosed. Apparatuses and systems also perform the functions of these methods. In one embodiment, the method includes receiving, at a first integrated access and backhaul node, a resource configuration corresponding to a second integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In some embodiments, the method includes obtaining activation parameters corresponding to the second integrated access and backhaul node, where the activation parameters include a first value, a second value, or a combination thereof. In some embodiments, the method includes determining whether the activation parameters include the first value. In various embodiments, the method includes, in response to determining that the activation parameters include the first value, sending an availability indication message corresponding to a subset of the soft resources.

[0005] In one embodiment, an apparatus for integrated access and backhaul node configuration includes a receiver that receives, at a first integrated access and backhaul node, a resource configuration corresponding to a second integrated access and backhaul node, where the resource configuration includes indication of soft resources. In some embodiments, the apparatus includes a processor that: obtains activation parameters corresponding to the second integrated access and backhaul node, where the activation parameters include a first value, a second value, or a combination thereof; and determines whether the activation parameters include the first value. In certain embodiments, the apparatus includes a transmitter that, in response to determining that the activation parameters include the first value, sends an availability indication message corresponding to a subset of the soft resources.

[0006] Another method for integrated access and backhaul node configuration includes receiving, at a first integrated access and backhaul node, a resource configuration, where the resource configuration includes information indicating soft resources. In certain embodiments, the method includes receiving an availability indication message corresponding to a subset of the soft resources. In some embodiments, the method includes determining whether the availability indication message is valid. In various embodiments, the method includes using the subset of the soft resources in response to determining that the availability indication message is valid.

[0007] Another apparatus for integrated access and backhaul node configuration includes a receiver that: receives, at a first integrated access and backhaul node, a resource configuration, where the resource configuration includes information indicating soft resources; and receives an availability indication message corresponding to a subset of the soft resources. In some embodiments, the apparatus includes a processor that: determines whether the availability indication message is valid; and uses the subset of the soft resources in response to determining that the availability indication message is valid.

[0008] A method for integrated access and backhaul node configuration includes receiving, at an integrated access and backhaul donor, first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node. In certain embodiments, the method includes receiving second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In some embodiments, the method includes sending a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources. In various embodiments, the method includes sending a first activation parameter corresponding to the first link to the second integrated access and backhaul node.

[0009] In one embodiment, an apparatus for integrated access and backhaul node configuration includes a receiver that: receives first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node at an integrated access and backhaul donor; and receives second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In various embodiments, the apparatus includes a transmitter that: sends a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources; and sends first activation parameters corresponding to the first link to the second integrated access and backhaul node. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and should not be considered limiting of the scope, the embodiments will be described and explained with additional specificity and detail by using the drawings, in which:

[0011] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for integrated access and backhaul node configuration;

[0012] Figure 2 is a schematic block diagram illustrating an embodiment of an apparatus that can be used for integrated access and backhaul node configuration;

[0013] Figure 3 is a schematic block diagram illustrating an embodiment of an apparatus that can be used for integrated access and backhaul node configuration;

[0014] Figure 4A is a schematic block diagram illustrating an embodiment of a system having an IAB system;

[0015] Figure 4B is a schematic block diagram illustrating an embodiment of DC in a system;

[0016] Figure 5 is a schematic block diagram illustrating an embodiment of a system including a DC architecture for IAB;

[0017] Figure 6 is a schematic block diagram illustrating an embodiment of an IAB DC system;

[0018] Figure 7 is a schematic block diagram illustrating an embodiment of a BAP control PDU format;

[0019] Figure 8 is a schematic flowchart illustrating an embodiment of a method for integrated access and backhaul node configuration;

[0020] Figure 9 is a schematic flowchart illustrating another embodiment of a method for integrated access and backhaul node configuration; and

[0021] Figure 10 is a schematic flowchart illustrating yet another embodiment of a method for integrated access and backhaul node configuration. Detailed implementation manners

[0022] As will be understood by those skilled in the art, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which in this document are generally referred to as "circuitry", "module", or "system". Additionally, the embodiments can take the form of a program product embodied in one or more computer-readable storage devices hereinafter referred to as code, computer-readable code, and / or program code. The storage device can be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain embodiments, the storage device merely takes a signal for accessing the code.

[0023] Certain functional units described in this specification may be marked as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0024] A module may also be implemented in code and / or software for execution by various types of processors. The identified code module may, for example, include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions. However, the executable files of the identified module need not be physically located together, but may include disparate instructions stored in different locations, which, when logically joined together, include the module and implement the stated purpose of the module.

[0025] In fact, a code module can be a single instruction or many instructions and can even be distributed over several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and depicted within a module and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set or can be distributed over different locations including on different computer-readable storage devices. In the case where a module or a portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0026] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be a computer-readable storage medium. The computer-readable storage medium can be a storage device that stores the code. The storage device can be, by way of example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0027] More specific examples (a non-exhaustive list) of storage devices will include the following: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0028] The code for performing the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, and conventional procedural programming languages such as the “C” programming language, and / or machine languages such as assembly language. The code can execute entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the last scenario, the remote computer can be connected to the user's computer through any type of network including a local area network (“LAN”) or a wide area network (“WAN”), or can be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0029] References in this specification to "one embodiment", "an embodiment", or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless otherwise explicitly stated, the phrases "in one embodiment", "in an embodiment", and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise explicitly stated, the terms "comprises", "comprising", "has", and their variants mean "including but not limited to". Unless otherwise explicitly stated, a list of items listed does not indicate that any or all of the items are mutually exclusive. Unless otherwise explicitly stated, the terms "a", "an", and "the" also refer to "one or more".

[0030] Furthermore, the features, structures, or characteristics of the described embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0031] Aspects of the embodiments are described below with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing device create a means for implementing the functions / operations specified in one or more blocks of the schematic flowcharts and / or schematic block diagrams.

[0032] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including the instructions that implement the functions / operations specified in one or more blocks of the schematic flowcharts and / or schematic block diagrams.

[0033] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices, such that a series of operational steps are performed on the computer, other programmable apparatus, or other devices to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in one or more boxes of the flowchart and / or block diagram.

[0034] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of apparatuses, systems, methods, and program products according to various embodiments. To this end, each box in the schematic flowchart and / or schematic block diagram may represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s).

[0035] It should also be noted that in some alternative embodiments, the functions noted in the boxes may not occur in the order noted in the accompanying drawings. For example, depending on the functions involved, two boxes shown in succession may actually be executed substantially simultaneously, or these boxes may sometimes be executed in the reverse order. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more boxes or portions thereof of the illustrated accompanying drawings.

[0036] Although various arrow types and line types may be employed in the flowchart and / or block diagram, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiment. It will also be noted that each box of the block diagram and / or flowchart, and combinations of boxes in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware that performs a specific function or operation, or a combination of dedicated hardware and code.

[0037] The description of the elements in each drawing may refer to the elements of the preceding drawings. The same reference numerals refer to the same elements in all the drawings, including alternative embodiments of the same elements.

[0038] Figure 1 Embodiments of a wireless communication system 100 for integrated access and backhaul node configuration are depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Even Figure 1 a specific number of remote units 102 and network units 104 are depicted, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0039] In one embodiment, the remote unit 102 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a gaming console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), an Internet of Things device, etc. In some embodiments, the remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals and / or the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0040] The network units 104 may be distributed over a geographical area. In certain embodiments, the network units 104 may also be referred to as access points, access terminals, bases, base stations, Node-Bs, eNBs, gNBs, home Node-Bs, client devices, RANs, relay nodes, devices, network devices, IAB nodes, donor IAB nodes, IAB donors, or any other terms used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and other networks like the public switched telephone network. These and other elements of the radio access and core networks are not shown, but are generally well known to those of ordinary skill in the art.

[0041] In one implementation, the wireless communication system 100 complies with the 5G or NG (next generation) standard of the 3GPP protocol, where the network unit 104 uses NG RAN technology for transmission. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as other protocols like LTE, LTE-Advanced, Wi-Fi, or WiMAX. The present disclosure is not intended to be limited to any particular implementation of a wireless communication system architecture or protocol.

[0042] The network unit 104 may serve multiple remote units 102 within the service area of a wireless communication link, e.g., a cell or a cell sector. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain. Additionally, the network unit 104 may communicate directly with other network units 104 via sidelink communication.

[0043] In some embodiments, the remote unit 102 and / or the network unit 104 may receive a resource configuration corresponding to a second integrated access and backhaul node at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In certain embodiments, the remote unit 102 and / or the network unit 104 may obtain activation parameters corresponding to the second integrated access and backhaul node, where the activation parameters include a first value, a second value, or a combination thereof. In some embodiments, the remote unit 102 and / or the network unit 104 may determine whether the activation parameters include the first value. In various embodiments, the remote unit 102 and / or the network unit 104 may send an availability indication message corresponding to a subset of the soft resources in response to determining that the activation parameters include the first value. Accordingly, the remote unit 102 and / or the network unit 104 may be used for integrated access and backhaul node configuration.

[0044] In certain embodiments, the remote unit 102 and / or the network unit 104 may receive a resource configuration at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In certain embodiments, the remote unit 102 and / or the network unit 104 may receive an availability indication message corresponding to a subset of the soft resources. In some embodiments, the remote unit 102 and / or the network unit 104 may determine whether the availability indication message is valid. In various embodiments, the remote unit 102 and / or the network unit 104 may use a subset of the soft resources in response to determining that the availability indication message is valid. Accordingly, the remote unit 102 and / or the network unit 104 may be used for integrated access and backhaul node configuration.

[0045] In various embodiments, the remote unit 102 and / or the network unit 104 may receive first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node at an integrated access and backhaul donor. In certain embodiments, the remote unit 102 and / or the network unit 104 may receive second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In some embodiments, the remote unit 102 and / or the network unit 104 may send a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources. In various embodiments, the remote unit 102 and / or the network unit 104 may send first activation parameters corresponding to the first link to the second integrated access and backhaul node. Accordingly, the remote unit 102 and / or the network unit 104 may be used for integrated access and backhaul node configuration.

[0046] Figure 2Depicts an embodiment of an apparatus 200 that can be used for an integrated access and backhaul node configuration. The apparatus 200 includes an embodiment of a remote unit 102. Additionally, the remote unit 102 can include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 can include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or display 208.

[0047] In one embodiment, the processor 202 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 can be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), a co-processing unit, a field-programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0048] In one embodiment, the memory 204 is a computer-readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 can include RAM, which includes dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 can include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile computer storage media and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0049] In one embodiment, the input device 206 can include any known computer input device, including a touchpad, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 206 can be integrated with the display 208, for example, as a touchscreen or a similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text can be input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices such as a keyboard and a touchpad.

[0050] In one embodiment, the display 208 can include any known electronically controllable display or display device. The display 208 can be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 can include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 208 can include a wearable display such as a smartwatch, smart glasses, a head-up display, etc. Additionally, the display 208 can be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0051] In certain embodiments, the display 208 includes one or more speakers for generating sound. For example, the display 208 can generate an audible alert or notification (e.g., a beep or a ring). In some embodiments, the display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touchscreen or a similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0052] In various embodiments, the receiver 212 can receive, at a first integrated access and backhaul node, a resource configuration corresponding to a second integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In some embodiments, the processor 202 can: obtain activation parameters corresponding to the second integrated access and backhaul node, the activation parameters including a first value, a second value, or a combination thereof; and determine whether the activation parameters include the first value. In certain embodiments, the transmitter 210 can, in response to determining that the activation parameters include the first value, send an availability indication message corresponding to a subset of the soft resources.

[0053] In one embodiment, the receiver 212: receives a resource configuration at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources; and receives an availability indication message corresponding to a subset of the soft resources. In some embodiments, the processor 202: determines whether the availability indication message is valid; and in response to determining that the availability indication message is valid, uses the subset of the soft resources.

[0054] In certain embodiments, the receiver 212: receives first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node at an integrated access and backhaul donor; and receives second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In various embodiments, the transmitter 210: sends a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources; and sends first activation parameters corresponding to the first link to the second integrated access and backhaul node.

[0055] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0056] Figure 3 An embodiment of an apparatus 300 that may be used for integrated access and backhaul node configuration is depicted. The apparatus 300 includes an embodiment of a network unit 104. Additionally, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0057] In various embodiments, the receiver 312 may receive a resource configuration corresponding to a second integrated access and backhaul node at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In some embodiments, the processor 302 may: obtain activation parameters corresponding to the second integrated access and backhaul node, the activation parameters including a first value, a second value, or a combination thereof; and determine whether the activation parameters include the first value. In certain embodiments, the transmitter 310 may send an availability indication message corresponding to a subset of the soft resources in response to determining that the activation parameters include the first value.

[0058] In one embodiment, the receiver 312: receives a resource configuration at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources; and receives an availability indication message corresponding to a subset of the soft resources. In some embodiments, the processor 302: determines whether the availability indication message is valid; and in response to determining that the availability indication message is valid, uses the subset of the soft resources.

[0059] In certain embodiments, the receiver 312: receives first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node at an integrated access and backhaul donor; and receives second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In various embodiments, the transmitter 310: sends a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources; and sends first activation parameters corresponding to the first link to the second integrated access and backhaul node.

[0060] Although only one transmitter 310 and one receiver 312 are illustrated, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be of any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

[0061] Figure 4AFIG. 0 is a schematic block diagram illustrating an embodiment of a system 314 having an IAB system. The system 314 includes a CN 316 and an IAB system 318 connected to the CN 316. The IAB system 318 includes an IAB donor 320 (e.g., a gNB), which includes a CU communicating with an IAB-DU. The IAB system 318 further includes a first IAB node 322 (e.g., an IAB-MT / IAB-DU), a second IAB node 324 (e.g., an IAB-MT / IAB-DU), a third IAB node 326 (e.g., an IAB-MT / IAB-DU), and a fourth IAB node 328 (e.g., an IAB-MT / IAB-DU). As can be understood, the IAB system 318 may include any suitable number of IAB nodes. The system 314 further includes a first UE 330, a second UE 332, a third UE 334, a fourth UE 336, and a fifth UE 338. It should be noted that the system 314 may include any suitable number of UEs. In some embodiments, the IAB-MT may be similar to and / or include the remote unit 102, and the IAB-DU may be similar to and / or include the network unit 104. Additionally, within a node, the IAB-MT and the IAB-DU may be internally connected. As used herein, the following may be used interchangeably: the IAB-MT of a sub-node, the IAB-MT of a node, and / or a sub-IAB-MT. Additionally, as used herein, the following may be used interchangeably: the IAB-DU of a parent node, the IAB-DU of a node, and / or a parent IAB-DU. Additionally, any use herein of a parent IAB node (e.g., or the IAB-DU of an IAB node) may also apply to an IAB donor (e.g., or the IAB-DU of an IAB donor).

[0062] In certain embodiments, an IAB node may receive a resource configuration in which each symbol in a time slot may be downlink (“D”), uplink (“U”), or flexible (“F”). In such an embodiment, flexible symbols may be used in downlink or uplink communication. In various embodiments, an IAB node may receive a configuration indicating whether each symbol in a time slot is hard (“H”), soft (“S”), or not available (“NA”). In such an embodiment, hard symbols may always be available, NA symbols may not be available, and the scheduling availability of soft symbols may be subject to an availability indication (“AI”) from a parent node. In some embodiments, the indication of hard and soft symbols in the configuration may be explicit, and symbols not indicated as hard or soft may be implicitly indicated as not available. As used herein, a parent node may be a first network unit 104 that provides a serving cell for a second network unit 104. Thus, the second network unit 104 may be referred to as a sub-node of the first network unit 104. Additionally, as Figure 4AAs used in, the IAB donor 320 may be the parent node of the first IAB node 322 and the second IAB node 324 (e.g., the IAB donor is the parent node). Additionally, as Figure 4A As used in, the first IAB node 322 may be the parent node of the third IAB node 326 and the fourth IAB node 328 (e.g., the IAB node is the parent node). Additionally, as Figure 4A As used in, the first IAB node 322 and the second IAB node 324 may be the child nodes of the IAB donor 320. Additionally, as Figure 4A As used in, the third IAB node 326 and the fourth IAB node 328 may be the child nodes of the first IAB node 322.

[0063] In some embodiments, a DCI format (e.g., DCI format 2_5) may be used to indicate the availability of soft resources for an IAB node. In such an embodiment, the granularity of the soft resources may be per resource type per child node (e.g., D / U / F - for a particular instance, the soft resources of type D / U / F may be indicated as either all available or all unavailable). Thus, in such an embodiment, the availability indication may be interpreted together with the resource configuration received in advance by the IAB node. As can be understood, the child node may be the node of the IAB-DU that connects its IAB-MT to the parent node. Thus, the parent node (e.g., IAB-DU) provides the serving cell to the child node (e.g., IAB-MT).

[0064] In certain embodiments, the parent node may coordinate the indication of the availability of soft resources for the child node with the resources that the parent node may use for its own communication, the resources indicated to be available for other child nodes, etc. Thus, in such an embodiment, the parent node may be fully aware of the child node's interpretation of the AI (e.g., as seen in DCI format 2_5).

[0065] In some embodiments, if dual connectivity is used and if the parent node of the IAB node does not have a common understanding of the resource configuration for the IAB node, the AI from the parent node may not be correctly interpreted by the IAB node, which may result in a conflict.

[0066] In various embodiments, if dual connectivity is used and if the IAB node receives AIs from more than one parent node (e.g., the AIs from multiple parent nodes are fully consistent), the interpretation and behavior of the IAB node may be defined.

[0067] In certain embodiments, if dual connectivity is used and if the IAB node receives an AI from the parent node and schedules communication with the child node, but the link to the parent node fails before the communication occurs, the scheduling may or may not be effective.

[0068] Figure 4B It is a schematic block diagram of an embodiment of DC in the illustrated system 400. The system 400 includes a CN 402 and an IAB system connected to the CN 402 via an IAB donor 404 (e.g., gNB). The IAB donor 404 includes a CU 406, a DU DU1 408, and a DU DU2 410. The system 400 also includes an IAB-N1 412 (e.g., a parent node), an IAB-N2 414 (e.g., a parent node), an IAB-N3 416 (e.g., a child node and a parent node), and an IAB-N4 418 (e.g., a child node).

[0069] The CN 402 communicates with the CU 406 via a first communication interface 420, the CU 406 communicates with the DU1 408 via a second communication interface 422, the CU 406 communicates with the DU2 410 via a third communication interface 424, the DU1 408 communicates with the IAB-N1 412 via a fourth communication interface 426, the DU2 410 communicates with the IAB-N2 414 via a fifth communication interface 428, the IAB-N1 412 communicates with the IAB-N3 416 via a sixth communication interface 430 (e.g., an MCG link), the IAB-N2 414 communicates with the IAB-N3 416 via a seventh communication interface 432 (e.g., an SCG link), and the IAB-N3 416 communicates with the IAB-N4 418 via an eighth communication interface 434 (e.g., an NR Uu interface). Each of the interfaces 426 and 428 may include multi-hop routing, where each hop includes a link between two network elements 104 not shown in Figure 4B the figure.

[0070] In Figure 4B , the resource configuration of the IAB-N3 416 may be informed to the parent nodes IAB-N1 412 and IAB-N2 414 by the CU 406. However, the parent nodes IAB-N1 412 and IAB-N2 414 may not know which resource configuration is allowed to send a specific DCI format (e.g., DCI format 2_5) to the IAB-N3 416. It may also not know how to handle the resources indicated by the DCI in case of a link failure associated with DCI transmission. In some embodiments, MAC CE messages and / or BAP control PDUs may be used for signaling to enable the parent nodes to provide an availability indication via the DCI. In various embodiments, it should be noted that the parent node may be able to send an AI to the child node without knowing the configuration information of the child node. For example, if the parent node provides full availability of all resources in a time slot to the child node, the parent node can do so without knowing which resources are soft.

[0071] In some embodiments, an IAB node may receive an AI from a master node. In such an embodiment, the AI may include AvailabilityCombinations that may have a structure similar to SlotFormatCombinations. The availability indicator may apply to several time slots, but the timing for the validity of the AI in the DC configuration may be unknown.

[0072] In one example, an IAB node such as IAB-N3 416 may receive an AI from a master node such as IAB-N1 412 in advance over several time slots. Based on the received AI, the IAB node may schedule communication with its own child nodes such as IAB-N4 418 over those time slots. Then, the primary link 430 of the IAB node with the master node may fail, and thus, a secondary node such as IAB-N2 414 may take over the availability indication of the IAB node (e.g., IAB-N3 416). The secondary node may send an AI to the IAB node that is inconsistent with the AI previously sent by the master node.

[0073] In some embodiments, the RRC connection in a multi-hop IAB system may be end-to-end, meaning that the communication of the IAB-MT at the RRC layer may be subject to cumulative multi-hop delays with the IAB donor CU. This can be contrasted with a conventional access link where it is practically guaranteed that the communication of the UE at the RRC layer has reached its destination once it is confirmed at the MAC sublayer.

[0074] In various embodiments, if resource coordination in the DC mode is used in an IAB system, the delay in performing RLF recovery may interrupt the communication through the DC IAB node. This can be particularly applicable to resource coordination (e.g., availability indication) unless lower layer (“L1”) signaling is in place, which enables the IAB node to replace the master node with a secondary node for the purpose of availability indication.

[0075] In some embodiments, dual connectivity may enhance the reliability in a cellular system through diversity and load balancing. This may be particularly applicable in an IAB system where a cell may serve not only the UE but also other IAB nodes that relay the communication with the UE. As can be understood, the reliability enhanced by DC may promote better QoS by reducing connection interruptions and providing seamless connectivity in a dynamic environment.

[0076] Figure 5FIG. 0 is a schematic block diagram illustrating an embodiment of a system 500 including a DC architecture for IAB. The system 500 includes a CN 502 and a DC architecture connected to the CN 502 via an IAB donor 504 (e.g., a gNB). The IAB donor 504 includes a CU 506, a DU DU1 508, and a DU DU2 510. The system 500 further includes an IAB-DU 512 (e.g., a parent node), an IAB-DU 514 (e.g., a parent node), and an IAB-MT / IAB-DU 516 (e.g., a child node).

[0077] The CN 502 communicates with the CU 506 via a first communication interface 518, the CU 506 communicates with the DU1 508 via a second communication interface 520, the CU 506 communicates with the DU2 510 via a third communication interface 522, the DU1 508 communicates with the IAB-DU 512 via a fourth communication interface 524, the DU2 510 communicates with the IAB-DU 514 via a fifth communication interface 526, the IAB-DU 512 communicates with the IAB-MT / IAB-DU 516 via a sixth communication interface 528 (e.g., an MCG link), and the IAB-DU 514 communicates with the IAB-MT / IAB-DU 516 via a seventh communication interface 530 (e.g., an SCG link). Each of the interfaces 524 and 526 may include multi-hop routing, where each hop includes a link between two network elements 104 not shown in Figure 5 FIG.

[0078] In Figure 5 system 500 of FIG., DC may be enabled only when the IAB node is served by a parent node DU connected to a common IAB donor CU-UP.

[0079] In various embodiments, multiplexing resources may be used between backhaul links and between backhaul links and access links in the time domain. In some embodiments, resource configuration and multiplexing may be possible at the OFDM symbol-level granularity. In certain embodiments, the CU may be responsible for topology scope management of semi-static time-domain resource configuration. In various embodiments, local signaling from the parent IAB-DUs 512 and 514 to the IAB-MT in the child IAB node 516 via PDCCH (e.g., DCI format 2_5) may indicate the availability of semi-statically configured resources to the IAB-DU in the child IAB node 516.

[0080] In some embodiments, there may be a semi-static configuration of time resources from the CU to the DU that may be cell-specific. In such embodiments, each time resource in the configuration may include one or more symbols having a downlink, uplink, or flexible attribute and a hard, soft, or unavailable attribute.

[0081] In some embodiments, the D / U / F attribute may determine the direction of communication on the configured resources. In such embodiments, the flexible resources may be configured as downlink or uplink. Further, in such embodiments, the D / U / F pattern of the time resource configuration of the DU may be aligned with the transmission of TDD-UL-DL-common in SIB1 by the DU and the configuration of TDD-UL-DL-dedicated and Slot-Format-Indicator for each UE and MT connected to the DU by the CU.

[0082] In various embodiments, the H / S / NA attribute may be used to improve the flexibility of resource allocation and scheduling in the IAB system. In such embodiments, the hard resources may be available for the IAB-DU to schedule communication with the sub IAB-MT or UE (e.g., downlink or uplink as determined by the D / U / F configuration). Further, in such embodiments, the soft resources may be available only when they are indicated as available by a DCI message (e.g., DCI format 2_5). Further, in such embodiments, the NA resources may not be available for the IAB-DU to schedule any downstream communication, such as uplink or downlink communication with the IAB-MT of the sub-node connected to the IAB-DU.

[0083] In some embodiments, the IAB-DU may use only the resources determined to be available for scheduling downstream communication with the sub IAB-MT and the connected UE. In such embodiments, the IAB-DU may also inform the sub-node via layer 1 signaling about which soft time resources are available. The layer 1 signaling may use the DCI format (e.g., DCI format 2_5) based on the D / U / F attribute of the resources and the cell ID of the sub IAB-DU, using the parameters configured by the CU via RRC.

[0084] In certain embodiments, the AI may have a per-slot D / U / F type granularity and may be interpreted based on the configuration of the sub-node rather than the parent node. Thus, in such embodiments, the parent IAB-DU may be informed by the CU of the resource configuration of its sub IAB-DU.

[0085] In various embodiments, a complete D / U / F + H / S / NA resource configuration for each sub IAB-DU may be provided to the parent IAB node / donor. In some embodiments, the cell specific signal and / or channel configuration of each sub IAB-DU may be provided to the parent IAB node / donor.

[0086] In some embodiments, if a NA or soft resource is configured with cell-specific signals and / or channels, the resource may be considered as if it were a hard resource. In various embodiments, the list of cell-specific signals and / or channels may include: 1) resources for SSB transmission at the DU, including both CD-SSB and non-CD-SSB; 2) configured RACH opportunities for receiving data at the DU; 3) periodic CSI-RS transmission at the DU; and / or 4) scheduling resources for receiving SR at the DU. In some embodiments, the parent node may not need to know the cell-specific signal and / or channel configuration of the child DU.

[0087] In some embodiments, the parent node may be enabled to know the resource configuration information of the child node. In such an embodiment, the resource configuration information at the parent node may be used for the availability indication of the soft resources of the child node.

[0088] In various embodiments, the parent node (e.g., the master node or the secondary node) may be enabled to know the configuration information, and for DC, the secondary node may have to know the configuration information before it can send an AI (e.g., DCI format 2_5) to the child node to avoid conflicts.

[0089] In some embodiments, the same parent node that relays the configuration information to the child node receives the configuration information through the same IAB path. In such an embodiment, the timing for validity may not be an issue. However, with multi-hop non-ideal backhaul, the secondary node may experience different multi-hop delays in receiving the configuration information and may require timing specifications for the validity of the configuration information.

[0090] In some embodiments, two parent nodes of an IAB node have common information about their resource configurations (e.g., D / U / F and H / S / NA).

[0091] In various embodiments, only the master node may send an AI. In such an embodiment, only the master node may be enabled to indicate availability. Additionally, in such an embodiment, if the master link is interrupted (e.g., due to RLF), the IAB node may not be able to use the soft resources until successful RLF recovery or until a new master link is established. This may result in low resource utilization (e.g., especially for FR2 and / or mobile IAB scenarios where RLF may be frequent). Furthermore, in such an embodiment, since the secondary node has no role in determining availability for its child nodes, it may have limited options for resource coordination.

[0092] In some embodiments, information for the AI of a child node may be provided to a secondary node of the child node. In such an embodiment, uplink control signaling may be used such that the child node relays the AI information to the secondary node. The secondary node may not be able to control the AI information, but it can obtain the AI information and use the AI information for resource coordination, such as scheduling communication with other child nodes or UEs.

[0093] Figure 6 FIG. 4 is a schematic block diagram illustrating an embodiment of an IAB DC system 600. The IAB DC system 600 includes a first node 602 (e.g., N1, IAB-DU), a second node 604 (e.g., N2, IAB-DU), a third node 606 (e.g., N3, IAB-MT / IAB-DU), a fourth node 608 (e.g., N4, IAB-MT / IAB-DU), a fifth node 610 (e.g., N5, IAB-MT / UE), a sixth node 612 (e.g., N6, IAB-MT / UE), and a seventh node 614 (e.g., N7, IAB-MT / UE).

[0094] The first node 602 communicates with the third node 606 via a first communication interface 616 (e.g., MCG link), the second node 604 communicates with the third node 606 via a second communication interface 618 (e.g., SCG link), the second node 604 communicates with the fourth node 608 via a third communication interface 620 (e.g., MCG link), the third node 606 communicates with the fifth node 610 via a fourth communication interface 622, the third node 606 communicates with the sixth node 612 via a fifth communication interface 624, the fourth node 608 communicates with the sixth node 612 via a sixth communication interface 626, and the fourth node 608 communicates with the seventh node 614 via a seventh communication interface 628.

[0095] In Figure 6Among them, the third node 606 and the fourth node 608 receive D / U / F+H / S / NA resource configurations and can provide information indicating those resource configurations to the first node 602 and the second node 604. The third node 606 can receive AI from the first node 602 and can relay the AI information to the second node 604. As used herein, AI can mean information conveyed via L1 signaling, while AI information can refer to information that may or may not be conveyed by using signaling similar to L1 signaling. Then, the second node 604 can use this AI information to send other AI to the fourth node 608 in a way that avoids conflicts on resources common between the third node 606 and the fourth node 608. Then, the third node 606 and the fourth node 608 use the AI information to schedule communications with the fifth node 610, the sixth node 612, and the seventh node 614. As can be understood, the details regarding how the relay information is used by the second node 604 (e.g., for sending AI to the fourth node 608) and / or by the fourth node 608 (e.g., scheduling communications with the sixth node 612 and / or the seventh node 614) can be specified by a standard document, can be configured by the system such as via the CU, and / or can be left to the implementation.

[0096] In some embodiments, instead of uplink control signaling from the IAB node to the secondary node, the master node and the IAB-DU of the secondary node can convey information when the backhaul (e.g., ideal backhaul) is available.

[0097] In certain embodiments, two parent nodes can be enabled to send AI. In such embodiments, the behavior of the child IAB node can be defined. If the IAB node receives AI for overlapping resources, at least two behaviors of the child node can be defined according to one of the following: 1) Prioritize the AI from the master node - the AI is sent by two parent nodes and the resources are interpreted as available when indicated as available by the master node and as unavailable when indicated as unavailable by the master node; 2) Combine the AI from the master node and the secondary node - the AI is sent by two parent nodes and the resources are interpreted as available when indicated as available by both the master node and the secondary node, otherwise as unavailable; and 3) Prioritize the earliest and / or latest AI.

[0098] In some embodiments, if the AI is to be ignored by the IAB node, it can be determined that: 1) only the AI for overlapping resources is ignored; or 2) the entire AI message is ignored.

[0099] In various embodiments, if the IAB node receives multiple DCI formats indicating the resource availability of a given time slot, the IAB node may not expect to receive inconsistent information about the resource availability, such as different AI index fields for a given time slot.

[0100] In some embodiments, if the first received AI (e.g., first in time) at least partially overlaps with the second received AI (e.g., second in time), some portions of the first received AI may be valid, some portions of the first received AI may be invalid, some portions of the second received AI may be valid, and / or some portions of the second received AI may be invalid. For example, in one embodiment, the entire first received AI may be considered valid, and a portion of the second received AI that overlaps with the first received AI may be considered invalid (e.g., a portion of the second received AI that does not overlap with the first received AI may be considered valid). As another example, in one embodiment, the entire second received AI may be considered valid, and a portion of the first received AI that overlaps with the second received AI may be considered invalid (e.g., a portion of the first received AI that does not overlap with the second received AI may be considered valid).

[0101] In some embodiments, only one parent node can send AI at a time. In such embodiments, the secondary node can send AI, but only when there is no AI from the primary node. This behavior can be configured by the system, such as by the CU. In some embodiments, the primary link may fail temporarily and the IAB node may not have successfully recovered the failed link or established a new primary link. In such embodiments, the secondary node may be able to be notified that it can send AI to the IAB node. Additionally, in such embodiments, this can be done via UCI signaling, PUCCH control signaling, or MAC signaling. Additionally, in such embodiments, once the secondary node receives the signaling, it can send AI to the IAB node until the failed link is recovered or a new primary link is established. Then, 1) the IAB node sends additional UCI signaling, PUCCH control signaling, or MAC signaling to the secondary node notifying it that it is no longer in need of AI (signaling from the gNB CU can inform the secondary node that AI is not needed); or 2) the secondary node sets a timer for sending AI to the IAB node - this timer can be set appropriately to match the time required for the IAB node to recover or establish the primary link (if the IAB node recovers or establishes the primary link before this timer expires, the IAB node can simply ignore the AI that overlaps with the AI from the primary node or inform the secondary node that the IAB node no longer expects any AI from the secondary node).

[0102] In various embodiments, multiple embodiments described herein can be used together, and if some embodiments are not completely consistent, the CU can determine how to implement the combination of embodiments. For example, it can be determined via RRC configuration whether a secondary node can send AI and / or how an IAB node should interpret overlapping AI. This can be useful because different embodiments can have different behaviors. For example, in a low-load situation where non-overlapping resources can be configured for nearby IAB nodes, AI can be sent by two parent nodes without causing conflicts. However, in a high-traffic situation where higher resource utilization is desired, overlapping soft resources can be configured for several IAB nodes and their availability can be indicated by the parent nodes. In this case, it may be desirable to allow only one parent node to send AI at a time or to specify the behavior for interpreting overlapping AI for more than one parent node. As can be understood, in an IAB system with varying traffic, the above behaviors can be configured semi-statically by the CU.

[0103] In certain embodiments, a node (e.g., the third node 606) receives configurations for MCG and SCG in a primary cell group and a secondary cell group, respectively. In such an embodiment, if a parameter associated with monitoring DCI (e.g., DCI format 2_5) is included in the configuration for MCG, the node monitors DCI from the primary node. Additionally, in such an embodiment, if a parameter associated with monitoring DCI is included in the configuration for SCG, the node monitors DCI from the secondary node.

[0104] In a first embodiment, a parameter associated with monitoring DCI can be used to configure monitoring of the PDCCH to obtain AI.

[0105] In a second embodiment, a parameter associated with monitoring DCI can be scrambled with an AI-RNTI. In such an embodiment, if an AI-RNTI field is included in the MCG configuration, the node assumes that AI can be sent by the MN. Similarly, if an AI-RNTI field is included in the SCG configuration, the node assumes that AI will be sent by the SN.

[0106] In some embodiments, after an available parent node receives an upper layer indication from a node, the parent node can allocate an AI-RNTI to the node and inform the CU.

[0107] In various embodiments, if an AI request and / or a DCI request is used, an AI-RNTI can be configured for both the MCG and the SCG. In such an embodiment, signaling for explicit indication can be used to indicate which parent node is enabled to send an AI. For example, parameter settings such as the following may be used: AI-AllowedIAB-Node: = <IAB-node ID>. As another example, the IAB-node ID can be a cell group ID (e.g., cell group ID = 0 for the MCG and cell group ID = 1 for the SCG). As another example, the ID can be the BAP address of the parent IAB node. In the embodiments described herein, the PCell can be set as the default availability indicator either by specification or by system-wide configuration.

[0108] In certain embodiments, if a node detects an RLF of a link that is allowed and / or determined to send an AI, the node triggers sending an AI request and / or a DCI request via signaling from a layer 1, MAC CE, and / or BAP entity to another link and / or a parent node.

[0109] In some embodiments, if a parent node receives an indication to send an AI and / or a DCI, the parent node informs the CU. Different embodiments can be used to inform the CU. In various embodiments, the CU is not informed immediately, and the problem is handled locally (e.g., between the IAB node and the parent node). Such an embodiment can have a faster response time, especially in a multi-hop IAB system.

[0110] In certain embodiments, signaling is used to permit and / or approve a change in the availability of the indication soft resources of a parent node. This can promote higher overall reliability.

[0111] In some embodiments, local resolution can be enabled to avoid a severe interruption until the permit and / or approval signaling is received by the CU. In various embodiments, a timer can be set, before which the parent node temporarily handles the problem until a new signaling for enabling the availability indication is received from the CU.

[0112] Some configurable embodiments are advantageous because the vulnerability of the system that causes an RLF depends on the resource configuration and the scenario. In certain embodiments, such as in a static system with mostly hard resource configurations, the configurable method enables a waiting period for signaling from the CU. In various embodiments, in a mobile system with variable traffic and mostly soft resource configurations, local temporary resolution can be beneficial.

[0113] In some embodiments, resources that are configured to be available before RLF (e.g., via RRC and / or F1) and / or indicated to be available (e.g., via DCI such as DCI format 2_5 or another AI message) can be used until the node receives a new AI from the second parent node.

[0114] In certain embodiments, resources (e.g., hard resources) that are indicated to be available only via RRC and / or F1 configuration before RLF can be used. However, in such embodiments, the IAB node stops using soft resources indicated to be available via DCI when detecting RLF.

[0115] In various embodiments, the IAB node can avoid scheduling any further communication, but can continue to fulfill a previous schedule by sending or receiving signals on channels such as PDSCH or PUSCH that have already been scheduled. In such embodiments, possible conflicts and / or failures can be handled via the HARQ process and / or other mechanisms.

[0116] In some embodiments, the IAB node can avoid scheduling any communication on soft resources and can also cancel or reject all communications that have already been scheduled on soft resources, such as PDSCH or PUSCH.

[0117] In certain embodiments, (e.g., for a downlink channel such as PDSCH that has already been scheduled on soft resources) the IAB-DU can avoid sending downlink signals to the sub IAB-MT or UE. Thus, in such embodiments, the IAB-MT or UE may not be able to receive and / or decode the signals expected on the scheduled channel, which results in a reception failure that can be handled via the HARQ process and / or other methods. Additionally, in such embodiments, if a channel is scheduled on a combination of hard resources and soft resources, the IAB node avoids sending any signals on either the hard resources or the soft resources.

[0118] In various embodiments, (e.g., for an uplink channel such as PUSCH that has already been scheduled on soft resources) the IAB-DU can enable uplink communication to occur and can receive signals from the sub IAB-MT. In some embodiments, the IAB-DU can use signaling to cancel the uplink communication. Such embodiments can be performed, for example, by deactivating a timer that may expire due to a lack of signaling from the IAB node to the sub IAB-MT, which then informs the IAB-MT that it can avoid sending signals on the uplink channel.

[0119] In some embodiments, it may be determined whether to fulfill, cancel, and / or reject a scheduled communication based on the priority or importance of the communication. In one example, a control channel such as PDCCH or PUCCH may be fulfilled and a shared channel such as PDSCH or PUSCH may be canceled and / or rejected. In another example, a communication of a transport block having a high QoS priority indicated by QCI or a transport block of data having a high priority logical channel may be fulfilled and a communication of a low QoS priority or a low logical channel priority may be canceled and / or rejected. As can be understood, a priority threshold may be used to determine whether to cancel and / or reject the transmission of a transport block. In one example, a downlink communication may be canceled and / or rejected and an uplink communication may be fulfilled. The above various combinations may be part of certain embodiments. In some embodiments, the CU may configure whether to fulfill, cancel, and / or reject a scheduled communication based on the priority or importance of the communication.

[0120] In some embodiments, resources configured as hard may be used as normal, but only resources configured as soft and indicated as available by the parent node may be used until the timer expires. In such an embodiment, the timer may be configured by the CU, may start running once an AI is received from the parent node, may start once an RLF is detected, etc. Additionally, in such an embodiment, the length of the timer may be determined by configuration or specification. Further, in such an embodiment, the resources indicated as available may be used for scheduling downstream communication until the timer expires. In certain embodiments, if the AI message indicates the availability of resources occurring before and after the timer expires, the entire message may be determined to be invalid (e.g., the soft resources indicated as available by the AI message may not be used). In some embodiments, if the AI message indicates the availability of resources occurring before and after the timer expires, the resources occurring before the timer expires may be used (e.g., valid), but the resources occurring after the timer expires may not be used (e.g., invalid). Various behaviors related to the message validity of the timer may be configured by the CU.

[0121] In certain embodiments, an IAB node that receives an AI from a parent node may experience an RLF, which may result in a temporary resource shortage until the link is re - established. Meanwhile, in such an embodiment, the IAB node may be enabled to request AI signaling from another parent node. For example, a MAC CE may be sent to another parent node for a DCI request or an AI request. The MAC CE may be identified by a MAC sub - header having an LCID. Additionally, the MAC CE may have a fixed - size zero bit, or a link (e.g., cell) index may be added to the MAC CE.

[0122] Figure 7FIG. is a schematic block diagram of an embodiment of the BAP control PDU format 700. The BAP control PDU format 700 includes a data or control (“D / C”) bit, a set of PDU type bits (e.g., four bits), and three separate reserved (“R”) bits.

[0123] Some embodiments may reuse the BAP control PDU format 700 to send AI requests and / or DCI requests. In such embodiments, if a parent IAB node (e.g., the second node 604) receives an AI request and / or a DCI request from a child IAB node (e.g., the third node 606), the parent IAB node may be enabled to send an availability indication (e.g., via a DCI message). Additionally, in such embodiments, a new PDU type may be used to signal the AI request.

[0124] Various embodiments may use the reserved bits of the BAP control PDU format 700. In such embodiments, one of the three reserved bits of the BAP control PDU format 700 may be used. For example, if a specific one of the three bits may be set to “1” to indicate that this is an AI request and / or a DCI request.

[0125] Figure 8 FIG. is a schematic flowchart of an embodiment of a method 800 for integrated access and backhaul node configuration. In some embodiments, the method 800 is performed by a device such as the remote unit 102 and / or the network unit 104. In certain embodiments, the method 800 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0126] The method 800 may include receiving 802 at a first integrated access and backhaul node a resource configuration corresponding to a second integrated access and backhaul node, wherein the resource configuration includes information indicating soft resources. In certain embodiments, the method 800 includes obtaining 804 activation parameters corresponding to the second integrated access and backhaul node, wherein the activation parameters include a first value, a second value, or a combination thereof. In some embodiments, the method 800 includes determining 806 whether the activation parameters include the first value. In various embodiments, the method 800 includes sending 808 an availability indication message corresponding to a subset of the soft resources in response to determining that the activation parameters include the first value.

[0127] In some embodiments, a first integrated access and backhaul node provides a serving cell to a second integrated access and backhaul node. In some embodiments, obtaining activation parameters includes receiving activation parameters from an integrated access and backhaul donor (e.g., an integrated access and backhaul donor central unit). In various embodiments, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and obtaining activation parameters includes receiving an availability indication request associated with a link between the second integrated access and backhaul node and the primary node of the second integrated access and backhaul node.

[0128] In one embodiment, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and obtaining activation parameters includes receiving an indication of radio link failure associated with a link between the second integrated access and backhaul node and the primary node of the second integrated access and backhaul node. In some embodiments, obtaining the activation parameters includes receiving a request message from the second integrated access and backhaul node. In some embodiments, the first value is 1, an activation indication, a true indication, or an allow indication, and the second value is 0, a deactivation indication, a false indication, or a disallow indication.

[0129] Figure 9 is a schematic flowchart illustrating another embodiment of a method 900 for integrated access and backhaul node configuration. In some embodiments, the method 900 is performed by a device such as a remote unit 102 and / or a network unit 104. In some embodiments, the method 900 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0130] The method 900 may include receiving 902 a resource configuration at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources. In some embodiments, the method 900 includes receiving 904 an availability indication message corresponding to a subset of the soft resources. In some embodiments, the method 900 includes determining 906 whether the availability indication message is valid. In various embodiments, the method 900 includes using 908 the subset of the soft resources in response to determining that the availability indication message is valid.

[0131] In some embodiments, determining whether the availability indication message is valid includes determining whether the availability indication message is valid based on a configuration. In some embodiments, determining whether the availability indication message is valid includes determining whether the availability indication message is valid based on a radio link failure. In various embodiments, the availability indication message is received from a secondary node of the first integrated access and backhaul node, and the radio link failure is associated with a link between the first integrated access and backhaul node and the secondary node of the first integrated access and backhaul node.

[0132] In one embodiment, determining whether an availability indication message is valid includes determining whether the difference between a first time corresponding to receiving the availability indication message and a second time corresponding to a subset of soft resources is no greater than a threshold. In certain embodiments, the threshold is determined based on the expiration of a timer. In some embodiments, the timer is configured by an integrated access and backhaul donor.

[0133] In various embodiments, the threshold is obtained by configuration. In one embodiment, the threshold is the number of time slots. In certain embodiments, the threshold is the number of symbols.

[0134] In some embodiments, the threshold for determining the validity of an AI message for soft resources is determined based on the subcarrier spacing. In some embodiments, the threshold is reported by an IAB node as a node capability. In various embodiments, the node capability is reported as the number of time slots or symbols for one or more subcarrier spacing values. Then, in such embodiments, the threshold is determined as the number of time slots or symbols associated with the subcarrier spacing associated with an active BWP (e.g., the BWP on which the soft resources are configured). In various embodiments, the threshold is determined based on the availability indication message.

[0135] Figure 10 FIG. 1000 is a schematic flowchart illustrating another embodiment of a method 1000 for integrated access and backhaul node configuration. In some embodiments, the method 1000 is performed by an apparatus such as a remote unit 102 and / or a network unit 104. In certain embodiments, the method 1000 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0136] The method 1000 may include receiving 1002 at an integrated access and backhaul donor (e.g., a central unit of the integrated access and backhaul donor) first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node. In certain embodiments, the method 1000 includes receiving 1004 second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node. In some embodiments, the method 1000 includes sending 1006 a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources. In various embodiments, the method 1000 includes sending 1008 first activation parameters corresponding to the first link to the second integrated access and backhaul node.

[0137] In some embodiments, the first activation parameter is 1, an activation indication, a true indication, or an allow indication. In some embodiments, method 1000 further comprises: receiving fourth information indicating a radio link failure corresponding to the first link; and sending a second activation parameter corresponding to the second link to a third integrated access and backhaul node. In various embodiments, the second activation parameter is 1, an activation indication, a true indication, or an allow indication.

[0138] In one embodiment, method 1000 further comprises sending a third activation parameter corresponding to the first link to a third integrated access and backhaul node. In some embodiments, the third activation parameter is 0, a deactivation indication, a false indication, or a disallow indication. In some embodiments, method 1000 further comprises sending fifth information of a threshold, wherein the threshold is associated with the validity of an availability indication message. In various embodiments, the availability indication message is associated with soft resources.

[0139] In one embodiment, a method comprises: receiving, at a first integrated access and backhaul node, a resource configuration corresponding to a second integrated access and backhaul node, wherein the resource configuration comprises information indicating soft resources; obtaining an activation parameter corresponding to the second integrated access and backhaul node, wherein the activation parameter comprises a first value, a second value, or a combination thereof; determining whether the activation parameter comprises the first value; and in response to determining that the activation parameter comprises the first value, sending an availability indication request message corresponding to a subset of the soft resources.

[0140] In some embodiments, the first integrated access and backhaul node provides a serving cell to the second integrated access and backhaul node.

[0141] In some embodiments, obtaining the activation parameter comprises receiving the activation parameter from an integrated access and backhaul donor (e.g., an integrated access and backhaul donor central unit).

[0142] In various embodiments, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and obtaining the activation parameter comprises: receiving an availability indication request associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node.

[0143] In one embodiment, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and obtaining the activation parameter comprises: receiving an indication of a radio link failure associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node.

[0144] In some embodiments, obtaining the activation parameter comprises receiving a request message from the second integrated access and backhaul node.

[0145] In some embodiments, the first value is 1, an activation indication, a true indication, or an allowance indication, and the second value is 0, a deactivation indication, a false indication, or a non-allowance indication.

[0146] In one embodiment, an apparatus includes: a receiver that receives, at a first integrated access and backhaul node, a resource configuration corresponding to a second integrated access and backhaul node, wherein the resource configuration includes information indicating soft resources; a processor that: obtains activation parameters corresponding to the second integrated access and backhaul node, wherein the activation parameters include a first value, a second value, or a combination thereof; and determines whether the activation parameters include the first value; and a transmitter that, in response to determining that the activation parameters include the first value, transmits an availability indication message corresponding to a subset of the soft resources.

[0147] In certain embodiments, the first integrated access and backhaul node provides a serving cell to the second integrated access and backhaul node.

[0148] In some embodiments, the processor obtaining the activation parameters includes the receiver receiving the activation parameters from an integrated access and backhaul donor (e.g., an integrated access and backhaul donor central unit).

[0149] In various embodiments, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and the processor obtaining the activation parameters includes: the receiver receiving an availability indication request associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node.

[0150] In one embodiment, the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node, and the processor obtaining the activation parameters includes: the receiver receiving an indication of a radio link failure associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node.

[0151] In certain embodiments, the processor obtaining the activation parameters includes the receiver receiving a request message from the second integrated access and backhaul node.

[0152] In some embodiments, the first value is 1, an activation indication, a true indication, or an allowance indication, and the second value is 0, a deactivation indication, a false indication, or a non-allowance indication.

[0153] In one embodiment, a method includes: receiving, at a first integrated access and backhaul node, a resource configuration, wherein the resource configuration includes information indicating soft resources; receiving an availability indication message corresponding to a subset of the soft resources; determining whether the availability indication message is valid; and in response to determining that the availability indication message is valid, using the subset of the soft resources.

[0154] In some embodiments, determining whether an availability indication message is valid includes determining whether the availability indication message is valid based on a configuration.

[0155] In some embodiments, determining whether an availability indication message is valid includes determining whether the availability indication message is valid based on a radio link failure.

[0156] In various embodiments, the availability indication message is received from a secondary node of a first integrated access and backhaul node, and the radio link failure is associated with a link between the first integrated access and backhaul node and the secondary node of the first integrated access and backhaul node.

[0157] In one embodiment, determining whether an availability indication message is valid includes determining whether a difference between a first time corresponding to receiving the availability indication message and a second time corresponding to a subset of soft resources is not greater than a threshold.

[0158] In some embodiments, the threshold is determined based on the expiration of a timer.

[0159] In some embodiments, the timer is configured by an integrated access and backhaul donor.

[0160] In various embodiments, the threshold is obtained through configuration.

[0161] In one embodiment, the threshold is the number of time slots.

[0162] In some embodiments, the threshold is the number of symbols.

[0163] In some embodiments, the threshold is determined based on a subcarrier spacing.

[0164] In various embodiments, the threshold is determined based on the availability indication message.

[0165] In one embodiment, a device includes: a receiver that: receives a resource configuration at a first integrated access and backhaul node, where the resource configuration includes information indicating soft resources; and receives an availability indication message corresponding to a subset of the soft resources; and a processor that: determines whether the availability indication message is valid; and in response to determining that the availability indication message is valid, uses the subset of the soft resources.

[0166] In some embodiments, the processor determining whether the availability indication message is valid includes the processor determining whether the availability indication message is valid based on a configuration.

[0167] In some embodiments, the processor determining whether the availability indication message is valid includes the processor determining whether the availability indication message is valid based on a radio link failure.

[0168] In various embodiments, an availability indication message is received from a secondary node of a first integrated access and backhaul node, and a radio link failure is associated with a link between the first integrated access and backhaul node and the secondary node of the first integrated access and backhaul node.

[0169] In one embodiment, a processor determines whether an availability indication message is valid by: determining whether a difference between a first time corresponding to receiving the availability indication message and a second time corresponding to a subset of soft resources is not greater than a threshold.

[0170] In certain embodiments, the threshold is determined based on the expiration of a timer.

[0171] In some embodiments, the timer is configured by an integrated access and backhaul donor.

[0172] In various embodiments, the threshold is obtained by configuration.

[0173] In one embodiment, the threshold is the number of time slots.

[0174] In certain embodiments, the threshold is the number of symbols.

[0175] In some embodiments, the threshold is determined based on a subcarrier spacing.

[0176] In various embodiments, the threshold is determined based on the availability indication message.

[0177] In one embodiment, a method includes: receiving, at an integrated access and backhaul donor (e.g., a central unit of the integrated access and backhaul donor), first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node; receiving second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node; sending a resource configuration to the first integrated access and backhaul node, the resource configuration including third information indicating soft resources; and sending first activation parameters corresponding to the first link to the second integrated access and backhaul node.

[0178] In certain embodiments, the first activation parameter is 1, an activation indication, a true indication, or an allow indication.

[0179] In some embodiments, the method further includes: receiving fourth information indicating a radio link failure corresponding to the first link; and sending second activation parameters corresponding to the second link to the third integrated access and backhaul node.

[0180] In various embodiments, the second activation parameter is 1, an activation indication, a true indication, or an allow indication.

[0181] In one embodiment, the method further includes sending third activation parameters corresponding to the first link to a third integrated access and backhaul node.

[0182] In certain embodiments, the third activation parameter is 0, a deactivation indication, a false indication, or a non - permission indication.

[0183] In some embodiments, the method further includes sending fifth information of a threshold, where the threshold is associated with the validity of an availability indication message.

[0184] In various embodiments, the availability indication message is associated with soft resources.

[0185] In one embodiment, a device includes: a receiver that, at an integrated access and backhaul donor (e.g., a central unit of the integrated access and backhaul donor), receives first information indicating a first link between a first integrated access and backhaul node and a second integrated access and backhaul node; and receives second information indicating a second link between the first integrated access and backhaul node and a third integrated access and backhaul node; and a transmitter that sends a resource configuration to the first integrated access and backhaul node, where the resource configuration includes third information indicating soft resources; and sends a first activation parameter corresponding to the first link to the second integrated access and backhaul node.

[0186] In certain embodiments, the first activation parameter is 1, an activation indication, a true indication, or a permission indication.

[0187] In some embodiments: the receiver receives fourth information indicating a radio link failure corresponding to the first link; and the transmitter sends a second activation parameter corresponding to the second link to the third integrated access and backhaul node.

[0188] In various embodiments, the second activation parameter is 1, an activation indication, a true indication, or a permission indication.

[0189] In one embodiment, the transmitter sends a third activation parameter corresponding to the first link to the third integrated access and backhaul node.

[0190] In certain embodiments, the third activation parameter is 0, a deactivation indication, a false indication, or a non - permission indication.

[0191] In some embodiments, the transmitter sends fifth information of a threshold, where the threshold is associated with the validity of an availability indication message.

[0192] In various embodiments, the availability indication message is associated with soft resources.

[0193] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Thus, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A method performed by a first integrated access and backhaul node, comprising: receiving a resource configuration corresponding to a second integrated access and backhaul node, wherein the resource configuration includes information indicating soft resources, and wherein the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node; obtaining activation parameters corresponding to the second integrated access and backhaul node by at least one of the following: receiving an availability indication request associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node, or receiving an indication of a radio link failure associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node, wherein the activation parameters include a first value, a second value, or a combination thereof; determining whether the activation parameters include the first value; and responding to determining that the activation parameters include the first value by sending an availability indication message corresponding to a subset of the soft resources.

2. The method according to claim 1, wherein obtaining the activation parameters includes: receiving the activation parameters from an integrated access and backhaul donor.

3. The method according to claim 1, wherein obtaining the activation parameters includes receiving a request message from the second integrated access and backhaul node.

4. A first integrated access and backhaul node, comprising: a receiver that receives a resource configuration corresponding to a second integrated access and backhaul node, wherein the resource configuration includes information indicating soft resources, and wherein the first integrated access and backhaul node is a secondary node of the second integrated access and backhaul node; a processor that: obtains activation parameters corresponding to the second integrated access and backhaul node by at least one of the following: receiving an availability indication request associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node, or receiving an indication of a radio link failure associated with a link between the second integrated access and backhaul node and a primary node of the second integrated access and backhaul node, wherein the activation parameters include a first value, a second value, or a combination thereof; and determines whether the activation parameters include the first value; and a transmitter that, in response to determining that the activation parameters include the first value, sends an availability indication message corresponding to a subset of the soft resources.

5. The first integrated access and backhaul node according to claim 4, wherein the processor obtaining the activation parameters includes the receiver receiving the activation parameters from an integrated access and backhaul donor.

6. The first integrated access and backhaul node according to claim 4, wherein the processor obtaining the activation parameters includes the receiver receiving a request message from the second integrated access and backhaul node.

Images