Spatial parameter capability indication

Abstract

Apparatus, methods, and systems are disclosed for spatial parameter capability indication. One method (1600) includes receiving (1602), at a first wireless node, a first control message from a second wireless node. The first control message includes a first indication of a first resource and a first spatial indication. The method (1600) includes determining (1604) whether a second resource overlaps with the first resource in a time domain and whether a time of reception of the first control message is not later than a time threshold. The method (1600) includes transmitting (1606) a second control message to a third device. The second control message includes a second indication of the second resource and a second spatial indication indicating that the first wireless node is capable of simultaneously applying a first spatial parameter and a second spatial parameter.

Description

[0001] This application claims priority to U.S. Patent Application Serial No. 63 / 004,215, titled “APPARATUSES, METHODS, AND SYSTEMS FOR BEAM MANAGEMENT FOR INTEGRATED ACCESS AND BACKHAUL WITH MULTIPLE ANTENNAS,” by Majid Ghanbarinejad, filed April 2, 2020, which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0002] The subject matter disclosed herein relates generally to wireless communication, and more particularly to spatial parameter capability indication. BACKGROUND

[0003] In certain wireless communication networks, it can be desirable to provide capability information to devices. In such networks, it can be desirable to provide the capability information for use within a certain time period. SUMMARY

[0004] Methods for spatial parameter capability indication are disclosed. Apparatuses and systems also perform the functions of these methods. One embodiment of a method includes receiving, at a first wireless node, a first control message from a second wireless node, where the first control message includes a first indication of a first resource and a first spatial indication. In some embodiments, the method includes determining whether a second resource overlaps the first resource in a time domain and a time of reception of the first control message is not later than a time threshold. In various embodiments, the method includes, in response to the second resource overlapping the first resource in the time domain and the time of reception of the first control message being not later than the time threshold, transmitting, to a third device, a second control message, where the second control message includes a second indication of the second resource and a second spatial indication indicating that the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to a second spatial indication.

[0005] An apparatus for spatial parameter capability indication includes a receiver that receives, at a first wireless node, a first control message from a second wireless node, where the first control message includes a first indication of a first resource and a first spatial indication. In various embodiments, the apparatus includes a processor that determines whether a second resource overlaps with the first resource in a time domain and a time of reception of the first control message is not later than a time threshold. In some embodiments, the apparatus includes a transmitter that transmits, to a third device, a second control message in response to the second resource overlapping with the first resource in the time domain and the time of reception of the first control message being not later than the time threshold, where the second control message includes a second indication of the second resource and a second spatial indication that indicates the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to the first spatial indication. BRIEF DESCRIPTION OF DRAWINGS

[0006] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of the scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0007] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for spatial parameter capability indication;

[0008] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for spatial parameter capability indication;

[0009] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for spatial parameter capability indication;

[0010] Figure 4 is a diagram illustrating one example of an integrated access and backhaul (“IAB”) system;

[0011] Figure 5 is a flow diagram illustrating one embodiment of a QCL indication;

[0012] Figure 6 is a diagram illustrating another embodiment of an IAB system;

[0013] Figure 7 is a diagram illustrating yet another embodiment of an IAB system;

[0014] Figure 8 is a diagram illustrating yet another embodiment of an IAB system;

[0015] Figure 9is a schematic block diagram illustrating one embodiment of a wireless channel between a multi-panel node, its parent node, and its child nodes;

[0016] Figure 10 is a flow diagram illustrating one embodiment of early dynamic TCI state indication;

[0017] Figure 11 is a timing diagram illustrating one embodiment of a timeline for early dynamic TCI state indication for a resource set;

[0018] Figure 12 is a timing diagram illustrating one embodiment of a timeline for early dynamic TCI state indication for a channel;

[0019] Figure 13 is a timing diagram illustrating one embodiment of a multi-hop delay for TCI state indication;

[0020] Figure 14 is a flow diagram illustrating one embodiment of semi-static TCI state configuration;

[0021] Figure 15 is a timing diagram illustrating one embodiment of a timeline for semi-static TCI state configuration; and

[0022] Figure 16 is a flow diagram illustrating one embodiment of a method for spatial parameter capability indication. DETAILED DESCRIPTION

[0023] As those skilled in the art will appreciate, the 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, micro-code, etc.) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the embodiments can take the form of a program product embodied in one or more computer readable storage devices having stored thereon computer readable code (i.e., program code) that can be used to program a computer (e.g., a processor) to perform a process. While the program code is being executed by the computer, the computer becomes an apparatus for practicing the embodiments. As used herein, the term “computer readable storage devices” is intended to encompass a non-transitory, tangible computer readable medium that is non-transitory and tangible. The program code can be stored in the computer readable storage devices, which can be any device or devices that is / are non-transitory and tangible, readable by a general or special purpose computer, processor or microprocessor. By way of example and not limitation, computer readable storage devices can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory, tangible computer readable medium that can be used to carry or store desired program code in the form of machine, computer or processor readable code. When the program code stored in the computer readable storage devices (or that can be accessed by the computer readable storage devices) is executed by the computer, a series of operations can be performed.

[0024] Certain of the functional units described in this specification can be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration ("VLSI") circuits or gate arrays

[0025] Modules can also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure or function. Nevertheless, the executables of an identified module need not be physically located together, but can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0026] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data can be identified within the modules and can be expressed in any data language or format including human readable and non-human readable languages. The operational data can be stored in any suitable storage medium, including a storage device, or memory, etc. Where a module or portions of a module are implemented in software, the software portions are stored in one or more computer-readable storage media.

[0027] 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 storing the code. The storage device can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0028] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, 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.

[0029] Code for carrying out operations for embodiments can be any number of lines and can be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and / or machine languages such as assembly languages. The code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter 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 the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0030] Reference throughout this specification to "one embodiment", "an embodiment", or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of 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 mean "one or more but not all embodiments". The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise. The enumeration of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" also mean "one or more", unless expressly specified otherwise.

[0031] Furthermore, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner in one or more embodiments. 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. One skilled in the relevant art will recognize, however, that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments.

[0032] The following description of various aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to 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, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / operations specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0033] The code may also be stored in a storage device that can instruct 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 art including instructions that implement the functions / operations specified in the boxes or some boxes of the schematic flowchart and / or schematic block diagram.

[0034] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, causing a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in the boxes or some boxes of the flowchart and / or block diagram.

[0035] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to different embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0036] It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in a different order than those shown in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0037] Although various arrow types and line types can be employed in the flowcharts and / or block diagrams, these are merely used to direct the flow of the depicted embodiments, and are not intended to limit the scope of the embodiments. Indeed, some arrows or other connectors can be used to indicate enumerated steps of the depicted embodiments. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by special-purpose hardware-based systems that perform the specified functions or operations, or combinations of special-purpose hardware and code.

[0038] The description of elements in each of the figures can refer to elements of the preceding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0039] Figure 1 Embodiments of a wireless communications system 100 for spatial parameter capability indication are depicted. In one embodiment, the wireless communications system 100 includes remote units 102 and network units 104. While a certain number of remote units 102 and network units 104 are depicted in the Figure 1 While a certain number of remote units 102 and network units 104 are depicted in the wireless communications system 100, those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communications system 100.

[0040] In one embodiment, a remote unit 102 can include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smart phone, smart television (e.g., a television connected to the Internet), set-top box, game console, security system (including security cameras), vehicle

[0041] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as and / or may include access point, access terminal, basic, base station, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operations, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the art. Network unit 104 is typically 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 typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, etc. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0042] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0043] The network units 104 can serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domain.

[0044] In various embodiments, a remote unit 102 and / or a network unit 104 can receive, at a first wireless node, a first control message from a second wireless node, where the first control message includes a first indication of a first resource and a first spatial indication. In some embodiments, the remote unit 102 and / or the network unit 104 can determine whether the second resource overlaps with the first resource in a time domain and whether a reception time of the first control message is not later than a time threshold. In various embodiments, the remote unit 102 and / or the network unit 104 can transmit, to a third device, a second control message in response to the second resource overlapping with the first resource in the time domain and the reception time of the first control message being not later than the time threshold, where the second control message includes a second indication of the second resource and a second spatial indication indicating that the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to a second spatial indication. Thus, the remote unit 102 and / or the network unit 104 can be used for spatial parameter capability indication.

[0045] Figure 2 One embodiment of an apparatus 200 that can be used for spatial parameter capability indication is depicted. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, 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 combine into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 can 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 can not include the input device 206 and / or the display 208.

[0046] 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”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform 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.

[0047] In one embodiment, the memory 204 is a computer readable storage medium. In some embodiments, the memory 204 includes both volatile and nonvolatile computer storage media. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 can include RAM, including 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 appropriate non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system and a control algorithm or other controller algorithm that operates on the remote unit 102.

[0048] In one embodiment, the input device 206 can include any known computer input device including a touch panel, a button, 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 touch screen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0049] 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, audible, 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, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or 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 smart watch, smart glasses, a heads-up display, etc. Further, the display 208 can be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

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

[0051] In certain embodiments, the receiver 212 receives, at the first wireless node, a first control message from a second wireless node, where the first control message includes a first indication of first resources and a first spatial indication. In various embodiments, the processor 202 determines whether the second resources overlap with the first resources in a time domain and a time of reception of the first control message is not later than a time threshold. In some embodiments, the transmitter 210 transmits, to a third device, a second control message in response to the second resources overlapping with the first resources in the time domain and the time of reception of the first control message being not later than the time threshold, where the second control message includes a second indication of the second resources and a second spatial indication indicating that the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to the second spatial indication.

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

[0053] Figure 3 One embodiment of an apparatus 300 that can be used for spatial parameter capability indication is depicted. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 can include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It can be appreciated that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 can 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.

[0054] In certain embodiments, the receiver 312 receives, at the first wireless node from a second wireless node, a first control message, where the first control message includes a first indication of a first resource and a first spatial indication. In various embodiments, the processor 302 determines whether the second resource overlaps in a time domain with the first resource and a time of reception of the first control message is not later than a time threshold. In some embodiments, the transmitter 310 transmits, to a third device, a second control message in response to the second resource overlapping in the time domain with the first resource and the time of reception of the first control message being not later than the time threshold, where the second control message includes a second indication of a second resource and a second spatial indication that indicates that the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to the second spatial indication.

[0055] In certain embodiments, IAB can involve specific multiplexing and duplexing schemes and / or time division multiplexing (“TDM”) between upstream communications (e.g., upstream communications with a parent IAB node and / or donor) and downstream communications (e.g., downstream communications with a child IAB node or UE).

[0056] In some embodiments, IAB can operate in a flexible time division duplex (“TDD”) mode. In such embodiments, each slot can be semi-statically configured to contain downlink (“DL” and / or “D”) symbols, uplink (“UL” and / or “U”) symbols, and flexible (“F”) symbols. Each flexible symbol can be configured to be a DL symbol or a UL symbol in one example. The DL, UL, and / or F configurations can follow a UL-F-DL pattern (e.g., they can start with a UL symbol and end with a DL symbol), providing flexibility over configurations that follow only a DL-F-UL pattern.

[0057] In various embodiments, in an IAB system, resources can be configured as hard (“H”) or soft (“S”), or if not H or S, the resources can be considered unavailable (“NA”). In such embodiments, a hard resource can always be available for scheduling communications with a UE or child node; a soft resource can be potentially available, which can be indicated by DCI signaling; and a NA symbol can not be usable by an IAB node for scheduling its own communications with a UE or child node (however, this does not mean that the IAB node can not be able to use the NA symbol to communicate with its parent node, perform measurements on the NA symbol, etc.).

[0058] In certain embodiments, the D, U, F, H, S, and / or NA properties can be per OFDM symbol (e.g., the granularity of the resource configuration with these properties can be all available frequency resources on a time resource as short as one OFDM symbol (e.g., in the active bandwidth part)). In such embodiments, if soft resource availability or unavailability is to be signaled by DCI, the granularity for availability indication (“AI”) can be per slot resource type in terms of D, U, and / or F. That is, all symbols in a slot that are configured as D, L, or F are indicated as available or unavailable. This can indicate a coarser granularity (e.g., substantially all frequency resources on one or several OFDM symbols).

[0059] In some embodiments, beam management can present potential issues if uplink and / or upstream transmissions and / or downlink and / or downstream transmissions are not always scheduled in separate time intervals. For example, an IAB node with multiple antenna panels can operate in frequency range 2 (“FR2”), and each antenna panel can be suitable for communication with a parent IAB node, a child IAB node, or a user equipment (“UE”). In various embodiments, if communication with the IAB node is scheduled, the parent node can select an antenna panel and / or beam via transmission configuration indication (“TCI”). In certain embodiments, if one panel is selected for communication with the parent node, another panel can be used for communication with a child node or a UE. In such embodiments, it can be important to inform the IAB node sufficiently in advance about which antenna panels will be used for communication with the parent node.

[0060] In various embodiments, such as in a mobile IAB system in which an IAB node is mounted on top of a public transportation vehicle, the “best” panel for communication with another node (e.g., including a parent node, a child node, or a UE) can change frequently.

[0061] In certain embodiments, such as in a multi-user system in which an IAB node serves different subsets of child nodes at different times, the IAB node can select a different panel for one communication with a child node than for another communication with the same child node.

[0062] In some embodiments, beam management and spatial division multiplexing (“SDM”) can be used in an IAB system.

[0063] Figure 4is a diagram illustrating one embodiment of an IAB system 400. The IAB system 400 includes a network 402 (e.g., a core network) in communication with an IAB donor 404 via a first communication link 406. Further, the IAB system 400 includes a first UE 408 in communication with the IAB donor 404 via a second communication link 410. Further, the IAB system 400 includes a first IAB node 412 in communication with the IAB donor 404 via a third communication link 414. The IAB system 400 also includes a second UE 416 in communication with the first IAB node 412 via a fourth communication link 418. Further, the IAB system 400 includes a second IAB node 420 in communication with the first IAB node 412 via a fifth communication link 422. Further, the IAB system 400 includes a third UE 424 in communication with the second IAB node 420 via a sixth communication link 426.

[0064] As further illustrated in detail, the network 426 is connected to the IAB donor 404 through a backhaul link 428, which can be wired. The IAB donor 404 includes a CU (IAB-CU) 430 and a DU (IAB-DU) 432. The IAB donor 404 communicates with all DUs in the system through an Fl interface. Each IAB node (e.g., 412 and 420) is functionally split into at least an MT (IAB-MT) (e.g., 434, 436) and a DU (IAB-DU) (e.g., 438, 440). The MT of an IAB node connects to the DU of a parent node, which can be another IAB node or the IAB donor 404.

[0065] The wireless connection (e.g., 414, 422, 426, 442, 444) between the MT of an IAB node and the DU of a parent node, which can be a Uu link, is referred to as a wireless backhaul link. In the wireless backhaul link, the MT is similar to a UE in terms of functionality and the DU of a parent node is similar to a base station in a regular cellular wireless link. Thus, the link from the MT to the serving cell of the DU as a parent link is referred to as an uplink, while the link in the reverse direction is referred to as a downlink. In this disclosure, embodiments can simply refer to an uplink or a downlink between IAB nodes, a link between a node and its parent, a link between a node and its child, etc., without directly referring to MTs, DUs, serving cells, etc.

[0066] Each IAB donor or IAB node can serve UEs (e.g., 446) over access links (e.g., 448). An IAB system like IAB system 400 can be designed to enable multi-hop communications (e.g., a UE can connect to a core network through access links and multiple backhaul links between IAB nodes and an IAB donor). As used herein, unless otherwise stated, an “IAB node” can refer to an IAB node or an IAB donor generally, as long as the connection between the CU and the core network is not involved.

[0067] A node, link, etc. that is closer to an IAB donor and / or a core network can be referred to as an upstream node, link, etc. For example, a parent node of a subject node is an upstream node of the subject node and a link to the parent node is an upstream link with respect to the subject node. Similarly, a node, link, etc. that is further from an IAB donor and / or a core network can be referred to as a downstream node, link, etc. For example, a child node of a subject node is a downstream node of the subject node and a link to the child node is a downstream link with respect to the subject node.

[0068] Table 1 summarizes terminology used herein.

[0069] Table 1: Terminology

[0070]

[0071]

[0072] In various embodiments, a wireless backhaul link at a physical layer can be used for timing alignment, inter-node discovery and measurement, resource allocation enhancements, and / or other features.

[0073] In certain embodiments, for beam management of a UE in RRC CONNECTED mode, the following can be performed: beam acquisition and maintenance, beam indication, and / or beam failure recovery.

[0074] In some embodiments, following a beam-based initial access that enables a UE to establish an RRC connection with a gNB, the gNB can configure a beam acquisition and maintenance procedure for the UE through RRC signaling.

[0075] In various embodiments, a UE can be configured with M resource settings. Each of the M resource settings can be configured through a CSI-ResourceConfig IE, and N reporting settings can be configured through a CSI-ReportConfig IE. The UE can perform measurements on reference signals (e.g., CSI-RS or SS / PBCH blocks) transmitted by the gNB on the configured resources indicated by the field of type CSI-ResourceConfig Id in the reporting settings to produce associated reports. The timing of producing and transmitting the reports can be controlled by the network through physical layer, MAC layer, and / or RRC signaling. In addition, periodic reports can be produced and transmitted as configured through RRC signaling, semi-persistent reports can be activated and / or deactivated through MAC signaling, and aperiodic reports can be triggered using a downlink control information (“DCI”) message.

[0076] In certain embodiments, if a gNB intends to indicate a beam for a communication, the gNB can use a transmission configuration indication (“TCI”) parameter, which can indicate a quasi co-location (“QCL”) between a reference signal resource (e.g., a CSI-RS resource or a SS / PBCH block resource) and the DM-RS of an upcoming communication. A ‘Type D’ QCL indication can indicate that the UE is expected to use the same beam it has used to receive and / or transmit a reference signal to receive and / or transmit the upcoming communication.

[0077] Figure 5 One embodiment illustrating how DCI format 1 1 can indicate QCL of a CSI-RS resource ID or SSB index.

[0078] Figure 5is a flowchart 500 illustrating one embodiment of a QCL indication. The flowchart 500 illustrates a DCI format 1 1 502 including a TCI 604 (3 bits) provided to a MAC CE 506 for activation and / or deactivation (e.g., logical channel identifier (“LCID”) = 53). A ControlResourceSet 508 can provide a tci-PresentInDCI 510 to the MAC CE 506 with a TCI 504. The MAC CE 506 can provide a bitmap 512 (e.g., up to 8 bits) to a PDSCH-Config 514. Further, the PDSCH-Config 514 can provide up to M 516 resource settings (e.g., for a TCI-State 520 (e.g., with a TCI-StateID) M can depend on maxNumberConfiguredTCIstatesPerCC 518 {4, 8, 16, 32, 64, 128}. The TCI-State 520 can be provided to a QCL-Info 522, which can indicate a NZP-CSI-RS-Resource 524 (e.g., NZP-CSI-RS-ResourceID) and a SSB-Index 526.

[0079] In some embodiments, beam failure recovery can be specified to enable a UE to recover from a beam failure and continue communication on a newly established beam pair.

[0080] Various frameworks, such as those described herein, can be used for beam management between a fixed IAB node, parent IAB node, and / or donor node and a mobile node and / or child IAB node.

[0081] In certain embodiments, time domain allocation parameters k0, k1, k2 (e.g., in NR) can be used herein and can be defined.

[0082] PDSCH time domain allocation: An RRC parameter k0 in an RRC information element PDSCH-TimeDomainResourceAllocation can indicate an offset between a slot containing DCI scheduling a PDSCH transmission and a slot containing the PDSCH transmission.

[0083] PDSCH hybrid automatic repeat request (“HARQ”) feedback timing: An L1 parameter k1 can be provided by a ‘PDSCH-to-HARQ_feedback timing indicator’ field in DCI formats 1 0 and 1 1 (e.g., for scheduling PDSCH transmissions).

[0084] Physical uplink shared channel (“PUSCH”) time domain allocation: An RRC parameter k2 in the RRC information element PUSCH-TimeDomainResourceAllocation can indicate an offset between a slot containing DCI scheduling a PUSCH transmission and a slot containing the PUSCH transmission.

[0085] In some embodiments, an IAB network can be connected to a core network through one or more IAB hosts. Each IAB node can be connected to an IAB host and / or other IAB nodes through wireless backhaul links. Each IAB host and / or IAB node can also serve UEs.

[0086] Figure 6 is a diagram illustrating another embodiment of an IAB system 600. The IAB system 600 includes an IAB network 602 and an IAB host 604 (e.g., a parent IAB node) connected through a first backhaul link 606. The IAB system 600 includes a first UE 608 connected to the IAB host 604 through a second backhaul link 610. Further, the IAB system 600 includes a first IAB node 612 (e.g., a single-panel node) connected to the IAB host 604 through a third backhaul link 614. Further, the IAB system 600 includes a second IAB node 616 (e.g., a multi-panel node) connected to the IAB host 604 through a fourth backhaul link 618 through a first antenna panel of the IAB node 616. The IAB system 600 includes a third IAB node 620 (e.g., a child IAB node) connected to the second IAB node 616 through a fifth backhaul link 622 through a second antenna panel of the IAB node 616. Further, the IAB system 600 includes a second UE 624 connected to the second IAB node 616 through a sixth backhaul link 626 through the first antenna panel or the second antenna panel of the IAB node 616. Further, the IAB system 600 includes a fourth IAB node 628 (e.g., a child IAB node) connected to the first IAB node 612 through a seventh backhaul link 630. The IAB system 600 includes a third UE 632 connected to the first IAB node 612 through an eighth backhaul link 634.

[0087] Figure 7is a diagram illustrating yet another embodiment of an IAB system 700 with single-panel and multi-panel IAB nodes. The IAB system 700 includes a network 702 and an IAB donor 704 (e.g., a parent IAB node) connected by a first backhaul link 706. The IAB system 700 includes a first IAB node 708 (e.g., a multi-panel node) connected to the IAB donor 704 by a second backhaul link 710 through a first antenna panel of the IAB node 708. The IAB system 700 includes a second IAB node 712 (e.g., a child IAB node) connected to the first IAB node 708 by a third backhaul link 714 through a second antenna panel of the IAB node 708. In addition, the IAB system 700 includes a first UE 716 connected to the first IAB node 708 by a fourth backhaul link 718 through the second antenna panel of the IAB node 708. In addition, the IAB system 700 includes a third IAB node 720 (e.g., a single-panel node) connected to the IAB donor 704 by a fifth backhaul link 722. In addition, the IAB system 700 includes a fourth IAB node 724 (e.g., a child IAB node) connected to the third IAB node 720 by a sixth backhaul link 726. The IAB system 700 includes a second UE 728 connected to the third IAB node 720 by a seventh backhaul link 730.

[0088] In some embodiments, there can be various options regarding the structure of an IAB node and multiplexing and / or duplexing capabilities. For example, each IAB node can have one or more antenna panels, arrays, and / or sub-arrays. Each of the one or more antenna panels, arrays, and / or sub-arrays can be connected to a baseband unit by one or more RF chains. One or more antenna panels can be capable of serving an entire spatial region of interest in the vicinity of the IAB node, or each antenna panel or each group of antenna panels can provide partial coverage (e.g., in a sector). An IAB node with multiple antenna panels each serving a separate spatial region or sector can be referred to as a single-panel IAB node, as it behaves similarly to a single-panel IAB node for communicating in each of the separate spatial regions or sectors.

[0089] In various embodiments, each antenna panel can be half-duplex (“HD”) (e.g., capable of transmitting or receiving signals in a frequency band at a time) or full-duplex (“FD”) (e.g., capable of both transmitting and receiving signals in a frequency band at the same time). Unlike full-duplex radios, half-duplex radios can be implemented and used in practice, and can be assumed as the default mode of operation in wireless systems.

[0090] Table 2 lists different multiplexing scenarios that can be used without multiplexing being limited to time division multiplexing (“TDM”). In Table 2, IAB node 1 (“N1”) is a single-panel IAB node; IAB node 2 (“N2”) is a multi-panel IAB node; spatial division multiplexing (“SDM”) refers to simultaneous transmission or reception on the downlink (or downstream) and uplink (or upstream); full duplex (“FD”) refers to simultaneous transmission and reception in a frequency band by the same antenna panel; and multi-panel transmission and reception (“MPTR”) refers to simultaneous transmission and reception by multiple antenna panels, where each antenna panel transmits or receives at a time in a frequency band.

[0091] Table 2

[0092] Scene IAB-MT IAB-DU type S1 (Case B) N1-DL-RX N1-UL-RX SDM S2 (Case D) N1-DL-RX N1-DL-TX FD S3 (Case A) N1-UL-TX N1-DL-TX SDM S4 (Case C) N1-UL-TX N1-UL-RX FD S5 (Situation B) N2-DL-RX N2-UL-RX SDM S6 (Case D) N2-DL-RX N2-DL-TX MPTR / FD S7 (Case A) N2-UL-TX N2-DL-TX SDM S8 (Case C) N2-UL-TX N2-UL-RX MPTR / FD

[0093] In one example, consider scenario S6, where multi-panel IAB node N2 receives a downlink control information (“DCI”) message (e.g., referred to as DCI1) on a control channel scheduling a physical downlink shared channel (“PDSCH”) transmission (e.g., referred to as PDSCH1) from a parent node to N2. Assume that N2 intends to schedule another downlink channel, referred to as PDSCH2, from N2 to a child node or user equipment. Since N2 has multiple panels, it can schedule both PDSCHs simultaneously through a multi-panel transmission and / or reception (“MPTR”) and / or frequency division multiplexing (“FDM”) scheme in addition to full duplex (“FD”). However, since the panel and / or beam selection for receiving PDSCH1 in N1 depends on the transmission configuration indication (“TCI”) in DCI1, N2 can receive DCI1 sufficiently early to generate and transmit a DCI message (e.g., referred to as DCI2) scheduling PDSCH2. If this condition is not met, it can not be possible to schedule PDSCH2 in a timely manner, which can result in inefficient utilization of hardware.

[0094] Figure 8 FIG. 8 is a diagram illustrating another embodiment of an IAB system 800. The IAB system 800 includes a network 802 and a parent node 804 (e.g., PN) connected by a first backhaul link 806. The IAB system 800 includes an IAB node 808 (e.g., N) connected to the parent node 804 by a second backhaul link 810. The IAB system 800 includes a child IAB node 812 (e.g., CN) connected to the IAB node 808 by a third backhaul link 814. In addition, the IAB system 800 includes a UE 816 connected to the IAB node 808 by a fourth backhaul link 818. Each of the parent node 804, the IAB node 808, and the child node 812 can be single-panel or multi-panel as described herein.

[0095] In various embodiments, the IAB system can determine whether resources are available (e.g., configured as hard, soft, or indicated as available). In such embodiments, the granularity of availability of resources can be a symbol at all frequencies (e.g., within an active bandwidth part (“BWP”)). Even if a resource is not configured as hard, the entire symbol can be considered hard because it has a periodic signal configured on it.

[0096] In some embodiments, either all frequency resources on a symbol are available or none are. This can be problematic in various embodiments where enhanced duplexing allows FDM between communications (e.g., including communications in downstream and upstream).

[0097] In certain embodiments, the system can employ beam management in which the operating frequency is in the millimeter wave band (e.g., frequency range 2 (“FR2”)). In Figure 9 A simplified diagram of a wireless channel between a PN, N, and CN and / or UE is illustrated in FIG. 1.

[0098] Figure 9 is a schematic block diagram 900 illustrating one embodiment of a multi-panel node, its parent node, and its child node, and the wireless channels between them. Specifically, the schematic block diagram 900 includes a first antenna panel for a parent node 902 (PN), a second antenna panel for a child node 904 (CN) (or UE), and an IAB node (N) with a first panel 906 (P1) and a second panel 908 (P2).

[0099] In Figure 9 The PN and CN and / or UE are shown as single-panel nodes in FIG. 1. The IAB node N has two antenna panels P1 and P2. Each antenna panel on the PN, N, and CN and / or UE can be capable of transmitting or receiving signals through multiple beams. The beams of interest for describing certain embodiments include a first beam 910 B1, a second beam 912 B2, a third beam 914 B3, a fourth beam 916 B4, a fifth beam 918 B5, a sixth beam 920 B6, a seventh beam 922 B7, and an eighth beam 924 B8. It is contemplated that each panel can be capable of applying one beam at a given time.

[0100] In various embodiments, to perform beam management, the PN transmits reference signals, such as channel state information reference signals (“CSI-RS”) on one or more CSI-RS resources, while applying different beams on different resources. The N responds by transmitting a channel state information (“CSI”) report including at least one beam index (e.g., a CSI-RS resource index (“CRI”) corresponding to B1) and at least one corresponding channel quality value (e.g., a reference signal received power (“RSRP”)). Since the N has multiple panels, it can report a second CRI corresponding to B2 and a corresponding RSRP. The beam management procedure can be performed as follows: 1) the PN is informed that it can communicate with the N through either B1 or B2; 2) the N knows that it can receive signals transmitted by the PN through B1 on P1 through B3 and through B2 on P2 through B4; and 3) assuming the PN has data to transmit to the N—then the PN transmits DCI scheduling a PDSCH transmission to the N— the DCI can contain a TCI indicating QCL Type D (e.g., spatial QCL) to either B1 or B2— if QCL Type D is indicated to B1, the N can apply B3 on P1 to receive the PDSCH signal on the time and frequency resources specified by the DCI— otherwise, if QCL Type D is indicated to B2, the N can apply B4 on P2 to receive the PDSCH signal. By following the beam acquisition procedure, the TCI indication can be interpreted by the receiver as a beam and / or panel selection.

[0101] In some embodiments, the procedure can be applied to uplink communications (e.g., so that the N transmits signals to the PN in a PUSCH transmission). For uplink beam acquisition, the PN and the N can: 1) use the downlink beams in opposite directions (e.g., a beam transmitted by the PN and a beam received by the N); and 2) perform a separate beam acquisition procedure, including transmission of sounding reference signals (“SRS”) by the N and measurements by the PN— later, the PN can indicate a SRS resource index (“SRI”) in DCI scheduling a PUSCH transmission.

[0102] As can be appreciated, the beam management procedures and communications between the N and the CN and / or UE can be similar to those between the PN and the N. Further, the downlink communications from the N to the CN and / or UE can follow a beam acquisition procedure that includes CSI-RS transmission by the N and {CRI, RSRP} reporting by the CN and / or UE. Further, the uplink communications transmitted from the CN and / or UE to the N can follow a separate beam acquisition procedure that includes SRS transmission by the CN and / or UE and measurements by the N. In certain embodiments, if the N schedules a communication with the CN and / or UE, a QCL Type D indication of B5 or B6 can inform the CN and / or UE that it should apply B7 or B8, respectively, for that communication.

[0103] In various embodiments, to schedule simultaneous communications between the PN-N and N-CN and / or UE links, the N can be informed in advance which panels are selected for uplink communications so that different panels can be selected for downstream communications.

[0104] In certain embodiments, panel and / or beam indications in FR2 can be used to inform panel selection. In such embodiments, a first option can be to leave things to implementation without standard specification, a second option can include defining rules for the PN to transmit scheduling DCI sufficiently in advance, or a third option can include defining signaling to enable beam indications sufficiently in advance.

[0105] The first option can leave things to implementation without standard specification for informing about panel selection. For example, the PN can always transmit DCI sufficiently in advance to inform the N in a timely manner and give it enough time to schedule other communications with the CN and / or UE. As another example, in a saturated traffic configuration, the N can predict what panels will be used in upcoming transmissions. As another example, in a light traffic scenario, the N can continue to schedule its own communications, and if panels and / or beams collide, the N can disregard one of the communications and handle the error through HARQ.

[0106] In the first option, the decision about which scheduled communication is accepted and which scheduled communication is disregarded can depend on: 1) Quality of Service (“QoS”): the decision about which transport block is given higher priority is based on QoS criteria (e.g., as made by a QoS Class Indicator (“QCI”); and / or 2) HARQ Redundancy Version (“RV”): the decision about which transport block is given higher priority is based on HARQ RV (e.g., a transport block with a higher HARQ RV can be given priority).

[0107] In the second option, rules can be defined in the standard specification that cause the parent node to schedule the communication and indicate the QCL sufficiently in advance. For example, for downlink transmission, since N needs sufficient time to receive and decode the DCI from PN and continue transmitting the DCI to CN and / or UE, PN can set the higher layer parameter k0 to a value greater than or equal to a minimum threshold time.

[0108] The minimum threshold time for PN to transmit the scheduling DCI in advance can be the minimum time for N to receive and decode the DCI and produce its own scheduling DCI. This can be set as a constant by the standard or set as an IAB node capability. This capability can be similar to timeDurationForQCL. The parameters in Table 3 can be specified by the standard or can be reported as a capability by the IAB node.

[0109] Table 3

[0110]

[0111] The parameter of Table 3 can be distinguished from timeDurationForQCL since it can include the time duration for the IAB node to produce the DCI, which includes processing rather than applying the beam (e.g., spatial filter), which can take less time to run.

[0112] The threshold for the parameter k0 can be set to the minimum time for N to decode the DCI plus the minimum time for N to transmit its own DCI in advance. That is: k0_min(PN): = T_min(N) + k0_min(N). In this equation, k0_min(PN) is the minimum value of k0 for PDSCH transmission from PN, T_min(N) is timeDurationForQCL2 for N, and k0_min(N) is the minimum value of k0 for PDSCH from N.

[0113] Consider the following two examples: 1) 2-hop system PN - N - UE: PN schedules PDSCH transmission and N schedules PDSCH transmission for the UE - since N can schedule PDSCH transmission for the UE with k0 = 0, one can set k0_min(N): = 0 - then, k0_min(PN) depends only on the minimum decoding time for N, which can be set as a constant T_min(N): = T_min; and 2) 3-hop system PN - N - CN - UE: {PN, N, CN} schedule PDSCH transmission for {N, CN, UE}, respectively - then, the minimum for k0 takes the following recursive form: k0_min(PN): = T_min(N) + k0_min(N), k0_min(N): = T_min(CN) + k0_min(CN). Since CN can schedule PDSCH transmission for the UE with k0 = 0, one can set k0_min(CN): = 0. Thus: k0_min(N): = T_min(CN), k0_min(PN): = T_min(N) + T_min(CN). Assuming T_min(N): = T_min(CN): = T_min, one obtains the following: k0_min(CN): = 0, k0_min(N): = T_min, k0_min(PN): = 2 x T_min.

[0114] As can be appreciated, the recursive rule can be extended to larger hop numbers. For example, in an m-hop IAB system Nm -... - N1 - N0 - UE, assuming all values of the minimum DCI decoding time are exactly the same, we have: k0_min(N0): = 0, k0_min(N1): = T_min,..., k0_min(Nm): = m x T_min.

[0115] In certain embodiments, analog beamforming can not be used (e.g., if the carrier frequency is in frequency range 1 (“FR1 ”)). If analog beamforming is not used, one can set k0_min(N0) to 0. However, if analog beamforming is used (e.g., for frequency range 2 (FR2)), the UE can use an additional T_min(UE) to decode the DCI and apply the appropriate beam (e.g., QCL Type D) as indicated in the TCI. If T_min(UE) = T_min, one can infer that all k0_min values will increase by the value of T_min (e.g., k0_min(N0): = T_min, k0_min(N1): = 2 x T_min,..., k0_min(Nm): = (m + 1) x T_min).

[0116] As can be appreciated, a similar approach can be applied to uplink communications or a combination of downlink and uplink communications in which the value of k2 can be used. The above calculations can be extended to S5, S6, S7, and S8.

[0117] S5: PN transmits PDSCH transmission to N; N receives PUSCH transmission from CN: k0_min(PN): = T_min(N) + k2_min(N), k2_min(N): = T_min(CN) + k0_min(CN).

[0118] S6: PN transmits PDSCH transmission to N; N transmits PDSCH transmission to CN: k0_min(PN): = T_min(N) + k0_min(N), k0_min(N): = T_min(CN) + k0_min(CN).

[0119] S7: PN receives PUSCH transmission from N; N transmits PDSCH transmission to CN: k2_min(PN): = T_min(N) + k0_min(N), k0_min(N): = T_min(CN) + k2_min(CN).

[0120] S8: PN receives PUSCH transmission from N; N receives PUSCH transmission from CN: k2_min(PN): = T_min(N) + k2_min(N), k2_min(N): = T_min(CN) + k2_min(CN).

[0121] In a third option, there can be new signaling for beam indication. As can be appreciated, the problem with the second option is that the PN can not have all the scheduling information k0 slots in advance. Instead, the PN can be able to determine only the QCL indication in advance, while leaving other scheduling information to a later time. Thus, in the third option, there can be new signaling that enables the N to have the beam indication information sufficiently in advance.

[0122] In a first embodiment of the third option, there can be a new DCI format that carries part of the scheduling information (e.g., including TCI or spatial relation information) instead of the full scheduling information. For example, a new DCI format 1_2 can be used that includes a subset of the fields of DCI format 1_1 including the ‘Transmission Configuration Indication’ (“TCI”) field. The presence of the new DCI format or certain fields in the new DCI format can be determined by a higher layer parameter. In certain embodiments, because this DCI (e.g., early DCI) can be used for other purposes, the higher layer parameter tci-PresentInDCI can also apply to this new DCI format.

[0123] Table 4 illustrates one embodiment of a method for an IAB node N for the first embodiment of the third option.

[0124] Table 4: Method for an IAB node N

[0125]

[0126] Figure 10 is a flowchart 1000 illustrating one embodiment of early dynamic TCI state indication. The method for an IAB node N of flowchart 1000 includes the IAB node N receiving 1002 a DCI including a TCI state indication T1 for upstream communication on a resource set R1; N obtaining 1004 beam and / or panel information B1 associated with the TCI state T1.

[0127] The method for an IAB node N further includes N considering 1006 the possibility of multiplexing communication by beam and / or panel B2 with beam and / or panel B1 (e.g., selecting a beam and / or panel B2 that can be multiplexed with B1). The following constraints can apply for FDM and / or SDM: 1) MPTR: FDM is possible if the antenna panels used for B1 and B2 are different; 2) SDM and / or HD: FDM is possible if the antenna panels used for B1 and B2 are the same, the beams used for B1 and B2 are the same, and the communication is either both transmission or both reception; 3) SDM and / or FD: FDM is possible if the antenna panels used for B1 and B2 are the same and the beams used for B1 and B2 are the same; and / or 4) FDM is possible if B1 and B2 are the same or substantially overlap (e.g., using the same or different antenna panels, for the same antenna panel, the power difference between upstream and downstream transmission can need to be considered as well as the maximum power reduction (“MPR”) and / or A-MPR due to internal modulation due to simultaneous transmission).

[0128] The method for an IAB node N further includes N selecting 1008 a TCI state T2 associated with beam and / or panel B2. In addition, N transmits 1010 a DCI indicating the TCI state T2 for downstream communication on a resource set R2 FDM with R1. The DCI can be: 1) a regular format (e.g., DCI format 1_1) if scheduling for a child IAB node or UE; or 2) a new format for a child IAB node.

[0129] Figure 11 is a timing diagram illustrating one embodiment of a timeline 1100 for early dynamic TCI state indication for a resource set. The timeline 1100 includes a PN time 1102, a N time 1104, and a CN time 1106.

[0130] In Figure 11In the middle, the PN transmits a DCI 1110 to the IAB node N. The DCI 1110 contains information about a set of resources Rl 1112 and a TCI indication 1114 Tl (e.g., a TCI state for Rl). The difference between the DCI 1110 and a DCI format 1_1 is that the DCI 1110 does not contain all the scheduling information for the upstream communication of N. Instead, the DCI 1110 conveys the necessary information to indicate the antenna panel and / or beam for potential communication on the channel 1116 Hl that can or can not use all the resources in the set of resources 1112 Rl.

[0131] Upon receiving the DCI 1110 from the PN, N can proceed to schedule a channel 1117 H2 for downstream communication with a CN or a UE. The scheduling can or can not precede a DCI 1118 that determines a set of resources 1120 R2 and a TCI state 1122 T2. The selection of the TCI state 1122 T2 for communication on 1117 H2 can satisfy a spatial constraint between the resources in 1120 R2 and / or 1117 H2 and the resources in 1112 Rl.

[0132] Meanwhile, the PN can also schedule a communication channel 1114 Hl to communicate with N via a DCI 1126.

[0133] Furthermore, a standard specification can determine a minimum time 1128 that an IAB node needs to transmit a DCI in advance. This threshold can be recursively calculated based on the number of hops and the minimum time needed to decode a DCI by each node. The threshold can be calculated by higher layers based on node capabilities. N can schedule a communication channel 1117 H2 via a DCI 1130.

[0134] Figure 11 The two-stage scheduling method of the disclosure can be similar to the two-stage sidelink control information (“SCI”) format for NR sidelink. For example, a new DCI format can be transmitted on a physical downlink control channel (“PDCCH”) as the first stage, but a second DCI format can be transmitted on a PDSCH as the second stage. In such embodiments, the second stage DCI can not need to be blindly decoded in a search space, but instead, the receiver can need to decode the second stage DCI contained in the PDSCH payload according to the information obtained from the first stage DCI.

[0135] In Figure 11 the DCI indicates a TCI state from which a subset is selected by a later DCI for scheduling a set of resources for a channel. In certain embodiments, the DCI can indicate a TCI state for all the resources on which a channel is scheduled by a later DCI, as shown in Figure 12 ​

[0136] Figure 12 is a timing diagram illustrating one embodiment of a timeline 1200 for early dynamic TCI state indication for a channel. The timeline 1200 includes a PN time 1202, an N time 1204, and a CN time 1206.

[0137] In Figure 12 , the PN transmits a DCI 1210 to the IAB node N. The DCI 1210 contains information about a resource set H1 1212 and a TCI indication 1214 T1 (e.g., TCI state for H1). After receiving the DCI 1210 from the PN, N can proceed to schedule a channel 1216 H2 for downstream communication with a CN or a UE. The scheduling can or can not precede a DCI 1218 that determines a resource set 1220 H2 and a TCI state 1222 T2. Meanwhile, the PN can also schedule a communication channel 1212 H1 for communication with N via a DCI 1224. Furthermore, a standard specification can determine a minimum time 1226 that an IAB node needs to transmit a DCI in advance. This threshold can be recursively calculated based on the minimum time needed for each node to decode a DCI and the number of hops. The threshold can be calculated by higher layers based on node capabilities. N can schedule a communication channel 1220 H2 via a DCI 1228.

[0138] In Figure 11 and Figure 12 , the DCI indicating the TCI state can use a new DCI format, while the DCI scheduling the channel can have a new format or an existing format. In some embodiments, if the DCI scheduling the channel indicates the TCI state (e.g., using DCI format 1_1 while the higher layer parameter tci-PresentInDCI is enabled), the receiver can ignore a certain parameter.

[0139] In certain embodiments, each of the upstream channel H1 and the downstream channel H2 can be a downlink channel such as a PDSCH transmission or an uplink channel such as a PUSCH transmission. In such embodiments, there can be the following possible cases: 1) H1 is downlink, H2 is uplink, N is single-panel; 2) H1 is downlink, H2 is uplink, Ni is multi-panel; 3) H1 is downlink, H2 is downlink, N is single-panel; 4) H1 is downlink, H2 is downlink, N is multi-panel; 5) H1 is uplink, H2 is downlink, N is single-panel; 6) H1 is uplink, H2 is downlink, Ni is multi-panel; 7) H1 is uplink, H2 is uplink, N is single-panel; and 8) H1 is uplink, H2 is uplink, N is multi-panel.

[0140] For H1 is downlink, H2 is uplink, N is single-panel (e.g., scenario S1): N can need to receive downlink signals from PN and receive uplink signals from CN when applying one set of spatial parameters (e.g., one beam) on a single panel. Thus, N can indicate TCI state in its first DCI to CN that needs to apply similar spatial reception parameters as needed to be applied according to the spatial reception parameters applied by the TCI state indicated through the first DCI from PN. In addition, N can run proper power control and timing alignment procedures for simultaneous reception of signals.

[0141] For H1 is downlink, H2 is uplink, N is multi-panel (e.g., scenario S5): N can receive downlink signals from PN and receive uplink signals from CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by the TCI state in its first DCI from PN, N can indicate the separate panel or panel set and put the associated TCI state in its first DCI to CN.

[0142] For H1 is downlink, H2 is downlink, N is single-panel (e.g., scenario S2): The single panel on N can be capable of full-duplex operation.

[0143] For H1 is downlink, H2 is downlink, N is multi-panel (e.g., scenario S6): N can receive downlink signals from PN and transmit downlink signals to CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by the TCI state in its first DCI from PN, N can indicate the separate panel or panel set and put the associated TCI state in its first DCI to CN.

[0144] For H1 is uplink, H2 is downlink, N is single-panel (e.g., scenario S3): If applying one set of spatial parameters (e.g., one beam) on a single panel, N can need to transmit uplink signals to PN and transmit downlink signals to CN. Thus, N can indicate TCI state in its first DCI to CN that needs to apply similar spatial transmission parameters as needed to be applied according to the spatial transmission parameters applied by the TCI state indicated through the first DCI from PN. In addition, N can run proper power control and timing alignment procedures for simultaneous reception of signals.

[0145] For H1 is uplink, H2 is downlink, N is multi-panel (e.g., scenario S7): N can transmit uplink signals to PN and downlink signals to CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by the TCI state in its first DCI from PN, N can need to indicate a separate panel or panel set and place the associated TCI state in its first DCI to CN.

[0146] For H1 is uplink, H2 is uplink, N is single-panel (e.g., scenario S4): The single panel on N can be capable of full-duplex operation.

[0147] For H1 is uplink, H2 is uplink, N is multi-panel (e.g., scenario S8): N can transmit uplink signals to PN and receive uplink signals from CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by the TCI state in its first DCI from PN, N can indicate a separate panel or panel set and place the associated TCI state in its first DCI to CN.

[0148] It should be noted that multi-panel nodes can also be capable of single-panel operation. For example, in scenarios S1 and S3, if the set of spatial parameters on the panel or panel set allows the node to communicate in both H1 and H2, the node can still indicate the TCI state to the child node and can use any additional panels for other simultaneous operations.

[0149] In some embodiments, IAB node N can not receive information about the set of resources R1 and can select TCI state T2 with associated beam and / or panel B2 based on beam and / or panel B1 corresponding to TCI state T1. In certain embodiments, IAB node N can receive multiple possible TCI states T1 and can select TCI state T2 with associated beam and / or panel B2 based on (e.g., compatible with) beam and / or panel B1 corresponding to each TCI state T1.

[0150] In various embodiments, the IAB node N can indicate a preferred set of TCI states (e.g., RS associated with TCI states received with good RSRP at the same time as giving flexibility for the IAB node N to use one of the TCI states from the preferred set for selecting a TCI state T2 for downstream communication concurrently with upstream communication) to the PN. The PN can select at least one TCI state T1 from the preferred set of TCI states for communicating with the IAB node N. In one example, the preferred set of TCI states can be indicated in a CSI report or MAC CE and can have a signal quality (e.g., RSRP) of the associated RS for each TCI state or a subset of TCI states in the preferred set of TCI states. In another example, the PN can configure RSRP thresholds and / or a minimum set size for the preferred set of TCI states. In an additional example, the TCI state T1 selected from the preferred set of TCI states can not be transmitted before the new DCI format and can be transmitted with the scheduling information. In some embodiments, some of the TCI states in the preferred set of TCI states can be configured but not activated. The PN can activate some of the TCI states from the TCI states in the preferred set of TCI states.

[0151] In a second embodiment of the third option, if the higher layer parameter tci-PresentInDCI is enabled in the control resource set (“CORESET”) configuration, the TCI state can be indicated in the DCI format 1 1 scheduling PDSCH transmission. If present, the TCI state indication can be 3 bits, indicating at most one of 8 TCI states. Each TCI state can be configured by higher layers and activated by a MAC control element (“CE”) message. If more than 8 TCI states are configured, the MAC CE message can be used to activate at most 8 of the TCI states at a time, such that each of the activated TCI states can be indexed by 3 bits. In one embodiment, the TCI state or spatial relation (e.g., using SRI) can be used for uplink and indicated in the uplink DCI format (e.g., DCI format 0 1) used to schedule PUSCH transmission.

[0152] In certain embodiments, an enhanced duplex can be enabled using an activation feature. If multiple TCI states are configured, they can be used based on a CSI process. Each TCI state can be associated (e.g., at an IAB node) with operation of an antenna and / or panel (e.g., from a set of antennas and / or panels) and a beam (e.g., from a set of beams on an antenna and / or panel). In some embodiments, an activated TCI state can be associated with a different antenna and / or panel. In such embodiments, the IAB node does not know what antennas and / or panels can be selected for upstream communication with a parent node. This can not allow the IAB node to schedule downstream communication with child nodes or UEs.

[0153] In various embodiments, if all activated TCI states are associated with one antenna and / or panel, the IAB node can know that other antennas and / or panels will not be used for upstream communication, which enables the IAB node to use them for downstream communication. It should be noted that TCI state activation can be semi-persistent (e.g., a TCI state remains valid until another MAC CE message is received by the IAB node modifying the set of activated TCI states or until the TCI state expires by a timer or a connection change).

[0154] In some embodiments, it can not be known how to ensure that activated TCI states are associated with a subset of antennas and / or panels of another subset of antennas and / or panels enabled for downstream communication, and the timing of activation and / or deactivation can be unknown.

[0155] In certain embodiments, there can be a groupBasedBeamReporting feature as shown in Table 5.

[0156] Table 5

[0157]

[0158] In various embodiments, if groupBasedBeamReporting is configured and set to ‘enabled’, a UE can report indices of two different reference signals that can be received simultaneously through two and / or multiple antennas and / or panels or through the same beam on a single antenna and / or panel.

[0159] In some embodiments, the L1-RSRP associated with the weaker of the two reference signals can be reported differently relative to the L1-RSRP associated with the stronger reference signal. In such embodiments, this can facilitate enabling enhanced duplex in the case that an IAB node reports two reference signals, each received through a separate antenna and / or panel. Table 6 illustrates one embodiment of a method for an IAB node N.

[0160] Table 6: Method for IAB node N

[0161]

[0162] The method of Table 6 can have two drawbacks. A first drawback of the method of Table 6 can be that the number of activated TCI states is limited. Indeed, if the parent IAB node receives in a report configured with groupBasedBeamReporting set to ‘enabled’ multiple pairs of two resource and / or beam indices, the relationship between the resource indices of each pair can be specified by the standard but can not be specified across the report. Thus, if the PN would guarantee that the multi-panel N can be able to identify unused antennas and / or panels, the TCI states associated with only one report can be activated. This can limit the flexibility and performance of the system for scheduling and beam management. A second drawback of the method of Table 6 can be that the IAB node can report beams received through multiple antennas and / or panels or through one beam on a single antenna and / or panel. Thus, the effectiveness of the method of Table 6 can depend on the voluntary cooperation of the N without knowing in advance whether the PN intends to use this for duplex enhancement purposes. An explicit indication to the N can be helpful.

[0163] In certain embodiments, it can be noted that the RRC configuration comes from the IAB donor CU, which can not be able to implement the intention of the IAB node to perform FDM and / or SDM and to configure CSI resources, CSI reports and TCI states accordingly. An explicit indication to the CU can be helpful.

[0164] In various embodiments, the group-based beam reporting method can be extended to enable reporting of two or more subsets of beams if each subset is associated with a separate antenna and / or panel.

[0165] In some embodiments, a message from the IAB node N to the parent node PN can indicate a subset of TCI states associated with an antenna and / or panel or a group of antennas and / or panels from the multiple antennas and / or panels. For example, a MAC CE message can include a bitmap or the like to indicate to the PN a subset of TCI states associated with an antenna and / or panel or a group of antennas and / or panels. If the PN activates the TCI states associated with the subset of multiple antennas and / or panels, the N can infer that any other antennas and / or panels are not activated for upstream communication and can be used for scheduling downstream communication.

[0166] In certain embodiments, one message can contain information of the association of one or more subsets of TCI states with one or more antennas and / or panels.

[0167] It should be noted that in a multi-hop IAB system, there can be a multi-hop delay in dynamic indication, activation, and / or semi-static indication of TCI states (e.g., referred to as TCI state indication) that can be related to a parameter similar to timeDurationForQCL3. One embodiment of timeDurationForQCL3 is shown in Table 7.

[0168] Table 7

[0169]

[0170] In various embodiments, if a TCI state indication is transmitted by a node to a downstream node within a period T adv the maximum number of hops that information can propagate is approximately equal to:

[0171] In this equation, D1 and D3 are timeDurationForQCL and timeDurationForQCL3, respectively.

[0172] Figure 13 is a timing diagram 1300 illustrating one embodiment of multi-hop delay for TCI state indication. Timing diagram 1300 illustrates a node 1302 N1, a node 1304 N2, a node 1306 N3, and a node 1308 N4. The nodes can include one or more of an IAB-DU 1310 and an IAB-MT 1312. Further, timing diagram 1300 illustrates a time 1314 for N1, a time 1316 for N2, a time 1318 for N3, and a time 1320 for N4.

[0173] In Figure 13 , (N1, N2, N3) are the parent nodes of (N2, N3, N4), respectively. N2 needs a minimum time 1322 D3 to receive a TCI state indication T1 from a message 1324 and to generate and transmit a TCI state indication T2 according to a message 1326. Similarly, N3 needs a minimum time 1328 D3 to receive T2 from message 1326 and to generate and transmit a TCI state indication T3. However, N3 can recognize that N4 will not be left enough time 1330 (D1) to decode and apply the beam for the TCI state indication or transmit its own TCI state indication (D3). Thus, this avoids transmitting T3. As a result, a sequence of TCI state indications starting with T1 propagates two hops within a period 1332 T adv before a TX and / or RX resource 1334 starts. Thus, the N3-N4 link can not benefit from the TCI state indication.

[0174] To solve this problem, N1 should transmit T advSet to a value long enough. The minimum value can be configured by the CU as it is the entity that can be informed of the topology information and capability information.

[0175] In some embodiments, the CU or PN DU can indicate to the N via control signaling that the feature will be used for SDM. This embodiment can be combined with other embodiments.

[0176] In various embodiments, the CU indicates to the N that the reporting configuration with groupBasedBeamReporting set to ‘enabled’ will enable SDM. The indication can be sent by the higher layer based on capability information provided to the CU via signaling or offline (e.g., by pre-configuration).

[0177] In certain embodiments, an explicit indication and / or request (e.g., capability signaling) can be defined for IAB nodes (e.g., PN, N) and provided to the CU of the node that is capable of and / or interested in SDM. If able to be received by both the PN and the N, the CU can take this information into account for configuration.

[0178] In some embodiments, the CU can receive the SDM capability information of the IAB node via signaling or by offline methods. The CU can then use this information in such embodiments to set the parameter in the reporting configuration showing that the IAB node can use separate panels for the group-based beam reporting associated with the reporting configuration.

[0179] As can be appreciated, the H1 and H2 resources can need to be separated in the frequency domain.

[0180] In various embodiments, the IAB node N can need to schedule the downstream communication in advance to enable the child node CN to decode the DCI and apply the parameters. For example, the minimum duration for the indication of the QCL can be timeDurationForQCL. However, the N can receive from the PN a MAC CE message activating another subset of TCI states that changes the subset of antennas and / or panels available for the downstream communication.

[0181] In certain embodiments, once the N receives from the PN a MAC CE message changing the subset of activated TCI states for the upstream communication, it can transmit its own MAC CE message changing the subset of activated TCI states for the downstream communication.

[0182] In some embodiments, the appropriate timing for applying the TCI activation and / or deactivation signaling can be used. For example, the TCI activation and / or deactivation message can only be applicable to the enhanced duplex IAB node after X slots, where X is an integer parameter configured by the higher layer.

[0183] In various embodiments, the beam indication can be made semi-static for some or all resources. The signaling for the beam indication can be controlled by the MAC layer.

[0184] In certain embodiments, a set of resources can be semi-statically configured with one or more TCI states to pre-inform the IAB node N about the set and / or range of possibilities for TCI indication in upcoming communications in the set of resources. This information can enable N to use other frequency resources on the semi-statically configured symbols for its own downlink transmissions to the CN or UEs.

[0185] Table 8 illustrates one embodiment of a method for an IAB node N.

[0186] Table 8: Method for an IAB node N

[0187]

[0188] Figure 14 is a flowchart 1400 illustrating one embodiment of semi-static TCI state configuration. The flowchart 1400 illustrates one embodiment of a method for an IAB node N, including the IAB node N receiving 1402 a configuration including an association set of a set of resources R1 and a TCI state T1. Further, MAC signaling can activate and / or deactivate TCI states from the set of TCI states, in this case T1 is the set of activated TCI states. R1 and T1 can be associated with upstream communications with respect to N.

[0189] N obtains 1404 beam and / or panel information B1 associated with the TCI state T1.

[0190] Then, N considers 1406 the possibility of multiplexing communications through beam and / or panel B2 with beam and / or panel B1 (e.g., selecting beam and / or panel information B1 from T1). The following constraints can apply for FDM and / or SDM: 1) MPTR: FDM is possible if the antenna panels used for B1 and B2 are different; 2) SDM and / or HD: FDM is possible if the antenna panels used for B1 and B2 are the same, the beams used for B1 and B2 are the same, and both communications are transmission or reception; 3) SDM and / or FD: FDM is possible if the antenna panels used for B1 and B2 are the same and the beams used for B1 and B2 are the same.

[0191] Next, N selects 1408 a TCI state T2 associated with beam and / or panel B2. Finally, N transmits 1410 an indication of the TCI state T2 to communicate on a resource R2 FDMed with R1.

[0192] In certain embodiments, the IAB node can need to consider inter-panel interference in the MPTR based on its own capabilities. Details of how to use the capability information can be left to implementation.

[0193] Figure 15 is a timing diagram illustrating one embodiment of a timeline 1500 for semi-static TCI state configuration. The timeline 1500 includes a PN time 1502, an N time 1504, and a CN time 1506.

[0194] In Figure 15 , the IAB node N receives a semi-static configuration 1508 including a set of resources R1 1510. The semi-static configuration 1508 can further include a set of TCI states. If more than one TCI state is configured for the set of resources 1510 (e.g., T0 and T1), a MAC message 1512 can activate or deactivate a TCI state from the set after a time period 1513. In this example, the MAC message 1512 activates the TCI state T1 corresponding to an antenna panel, which allows N to know in advance which other antenna panel it has available for downstream communication.

[0195] N can then proceed to schedule a channel 1516 H2 on resources 1518 R2 FDM with R1 via DCI 1514 for downstream communication with a CN or UE. The TCI state T2 indicated in the DCI 1514 is associated with an antenna panel that is not associated with T1.

[0196] Meanwhile, the PN can also schedule a communication channel 1522 H1 on R1 via DCI 1520 to communicate with N.

[0197] In Figure 15 , each of the upstream channel 1522 H1 and the downstream channel 1516 H2 can be a downlink channel such as a PDSCH or an uplink channel such as a PUSCH. In such embodiments, there can be the following possible cases: 1) H1 is downlink, H2 is uplink, N is single panel; 2) H1 is downlink, H2 is uplink, N is multi-panel; 3) H1 is downlink, H2 is downlink, N is single panel; 4) H1 is downlink, H2 is downlink, N is multi-panel; 5) H1 is uplink, H2 is downlink, N is single panel; 6) H1 is uplink, H2 is downlink, N is multi-panel; 7) H1 is uplink, H2 is uplink, N is single panel; and 8) H1 is uplink, H2 is uplink, N is multi-panel.

[0198] For H1 is downlink, H2 is uplink, N is single-panel (e.g., scenario S1): If one spatial parameter set (e.g., one beam) is applied on one panel, N can need to receive downlink signals from PN and receive uplink signals from CN. Thus, N can indicate TCI states in DCI to CN that need to apply similar spatial reception parameters as the spatial reception parameters applied according to the TCI states activated by the MAC CE message from PN only. In addition, N can run proper power control and timing alignment procedures for simultaneous reception of signals.

[0199] For H1 is downlink, H2 is uplink, N is multi-panel (e.g., scenario S5): N can receive downlink signals from PN and receive uplink signals from CN through different panels or panel sets. Thus, once N determines the panel or panel set activated by TCI states in the MAC CE message from PN, N can indicate the separate panel or panel set and put the associated TCI states in DCI to CN.

[0200] For H1 is downlink, H2 is downlink, N is single-panel (e.g., scenario S2): The single panel on N can be capable of full-duplex operation.

[0201] For H1 is downlink, H2 is downlink, N is multi-panel (e.g., scenario S6): N can receive downlink signals from PN and transmit downlink signals to CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by TCI states in the MAC CE message from PN, N can indicate the separate panel or panel set and put the associated TCI states in DCI to CN.

[0202] For H1 is uplink, H2 is downlink, N is single-panel (e.g., scenario S3): If one spatial parameter set (e.g., one beam) is applied on one panel, N can need to transmit uplink signals to PN and transmit downlink signals to CN. Thus, N can indicate TCI states in DCI to CN that need to apply similar spatial transmission parameters as the spatial transmission parameters applied according to the TCI states activated by the MAC CE message from PN only. In addition, N can run proper power control and timing alignment procedures for simultaneous reception of signals.

[0203] For H1 is uplink, H2 is downlink, N is multi-panel (e.g., scenario S7): N can transmit uplink signals to PN and transmit downlink signals to CN through different panels or panel sets. Thus, once N determines the panel or panel set activated by the TCI state in the MAC CE message from PN, N can indicate the separate panel or panel set and place the associated TCI state in the DCI to CN.

[0204] For H1 is uplink, H2 is uplink, N is single-panel (e.g., scenario S4): The single panel on N can be capable of full-duplex operation.

[0205] For H1 is uplink, H2 is uplink, N is multi-panel (e.g., scenario S8): N can transmit uplink signals to PN and receive uplink signals from CN through different panels or panel sets. Thus, once N determines the panel or panel set indicated by the TCI state in the MAC CE message from PN, N can indicate the separate panel or panel set and place the associated TCI state in the DCI to CN.

[0206] It should be noted that multi-panel nodes can be capable of single-panel operation. For example, in scenarios S1 and S3, if the set of spatial parameters on the panel or panel set enables the node to communicate in both H1 and H2, the node can still indicate the TCI state to the child node and can use any additional panels for other simultaneous operations.

[0207] Further, it should be noted that various embodiments can be extended to systems with greater hop counts. For example, in a multi-hop system N1-N2-N3-N4, where (N1, N2, N3) are the parent nodes of (N2, N3, N4), respectively, N1 can send a semi-static TCI state indication T1 to N2 and N2 can send a semi-static TCI state indication T2 to N3 according to the information obtained from T1. Then, N3 can send a TCI state indication T3 to N4 through DCI or through another semi-static signaling.

[0208] Certain embodiments herein can be described with a focus on scenario S6 (e.g., downlink from PN to N and downlink from N to CN and / or UE). However, any embodiment (e.g., such as multi-panel scenarios S5-S8) can use elements of other embodiments.

[0209] For S5: N can receive PDSCH transmissions from PN and PUSCH transmissions from CN and / or UE. Thus: k0_min(PN): = T_min(N) + k2_min(N), k2_min(N): = T_min(CN) + k0_min(CN).

[0210] For S6: N can receive PDSCH transmissions from PN and transmit PDSCH transmissions to CN and / or UE. Thus: k0_min(PN): = T_min(N) + k0_min(N), k0_min(N): = T_min(CN) + k0_min(CN).

[0211] For S7: N can transmit PUSCH transmissions to PN and transmit PDSCH transmissions to CN and / or UE. Thus: k2_min(PN): = T_min(N) + k0_min(N), k0_min(N): = T_min(CN) + k2_min(CN).

[0212] For S8: N can transmit PUSCH transmissions to PN and receive PUSCH transmissions from CN and / or UE. Thus: k2_min(PN): = T_min(N) + k2_min(N), k2_min(N): = T_min(CN) + k2_min(CN).

[0213] Further embodiments can include the following:

[0214] For S5: N can receive H1 = PDSCH from PN and receive H2 = PUSCH from CN and / or UE. Thus, R1 can be selected from resources configured as downlink and R2 can be selected from resources configured as uplink. For example, the corresponding DCI formats can be Format 1_0 and / or 1_1 and Format 0_0 and / or 0_1, respectively.

[0215] For S6: N can receive H1 = PDSCH from PN and transmit H2 = PDSCH to CN and / or UE. Thus, R1 can be selected from resources configured as downlink and R2 can be selected from resources configured as downlink. For example, the corresponding DCI formats can be Format 1_0 and / or 1_1 and Format 1_0 and / or 1_1, respectively.

[0216] For S7: N can transmit H1 = PUSCH to PN and transmit H2 = PDSCH to CN and / or UE. Thus, R1 can be selected from resources configured as uplink and R2 can be selected from resources configured as downlink. For example, the corresponding DCI formats can be Format 0_0 and / or 0_1 and Format 1_0 and / or 1_1, respectively.

[0217] For S8: N can transmit H1 = PUSCH to PN and receive H2 = PUSCH from CN and / or UE. Thus, R1 can be selected from resources configured as uplink and R2 can be selected from resources configured as uplink. For example, the corresponding DCI formats can be Format 0_0 and / or 0_1 and Format 0_0 and / or 0_1, respectively.

[0218] In some embodiments, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel can be hardware used to transmit and / or receive radio signals at frequencies below 6 GHz (e.g., frequency range 1 (“FR1”)) or above 6 GHz (e.g., frequency range 2 (“FR2”) or millimeter wave (“mmWave”)). In certain embodiments, an antenna panel can include an array of antenna elements. Each antenna element can be connected to hardware such as a phase shifter that enables a control module to apply spatial parameters for transmission and / or reception of signals. The resulting radiation pattern can be referred to as a beam, which can or can not be unimodal and can allow a device to amplify signals transmitted or received from a spatial direction.

[0219] In various embodiments, an antenna panel can or can not be virtualized into antenna ports. An antenna panel can be connected to a baseband processing module through a radio frequency (“RF”) chain for each transmission (e.g., egress) and reception (e.g., ingress) direction. The capabilities of a device in terms of the number of antenna panels, their duplexing capabilities, their beamforming capabilities, etc. can or can not be transparent to other devices. In some embodiments, the capability information can be communicated via signaling or can be provided to a device without the need for signaling. If the information is usable by other devices such as a CU, the information can be used for signaling or local decision making.

[0220] In some embodiments, a UE antenna panel can be a physical or logical antenna array of a set of antenna elements or antenna ports that includes a common or effective portion of a shared radio frequency ("RF") chain (e.g., in-phase and / or quadrature ("I / Q") modulators, analog-to-digital ("A / D") converters, local oscillators, phase shift networks). A UE antenna panel or UE panel can be a logical entity with physical UE antennas mapped to the logical entity. The mapping of physical UE antennas to logical entities can depend on the UE implementation. Communication (e.g., reception or transmission) on a subset of the antenna elements or antenna ports (e.g., active elements) of at least the antenna panel that are activated for radiating energy can require biasing or energizing of the RF chain, which results in current consumption or power consumption in the UE associated with the antenna panel (e.g., including power amplifier and / or low noise amplifier ("LNA") power consumption) associated with the antenna elements or antenna ports. The phrase "activated for radiating energy" as used herein is not intended to be limited to transmission functionality, but also includes reception functionality. Thus, an antenna element activated for radiating energy can be coupled to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, either simultaneously or sequentially, or in general can be coupled to a transceiver to perform its intended functionality. Communication on the activated elements of the antenna panel enables generation of a radiation pattern or beam.

[0221] In certain embodiments, depending on the UE's own implementation, a "UE panel" can have at least one of the following functionalities as an operational role of an antenna group unit for independently controlling its transmit ("TX") beams, an antenna group unit for independently controlling its transmit power, and / or an antenna group unit for independently controlling its transmit timing. The "UE panel" can be transparent to the gNB. For certain conditions, the gNB or network can assume that the mapping between the UE's physical antennas and logical entities "UE panels" can not change. The conditions can include, for example, until the next update or report from the UE or a duration of time that the gNB assumes the mapping will not change. The UE can report its UE capabilities regarding "UE panels" to the gNB or network. The UE capabilities can include at least the number of "UE panels." In one embodiment, the UE can support UL transmission from one beam per panel. In the multiple panel case, more than one beam (e.g., one beam per panel) can be used for UL transmission. In another embodiment, more than one beam per panel can be supported and / or used for UL transmission.

[0222] In some embodiments, an antenna port can be defined such that a channel over which a symbol on the antenna port is communicated can be inferred from a channel over which another symbol on the same antenna port is communicated.

[0223] In certain embodiments, two antenna ports are said to be quasi co-located (“QCL”) if a large scale property of the channel conveying symbols on one antenna port can be inferred from the channel conveying symbols on another antenna port. The large scale properties can include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (“RX”) parameters. Two antenna ports can be QCL with respect to a subset of the large scale properties, and different subsets of the large scale properties can be indicated by a QCL type. For example, a qcl-Type can take one of the following values: 1) ‘QCL-TypeA’: {Doppler shift, Doppler spread, average delay, delay spread}; 2) ‘QCL-TypeB’: {Doppler shift, Doppler spread}; 3) ‘QCL-TypeC’: {Doppler shift, average delay}; and 4) ‘QCL-TypeD’: {spatial Rx parameters}.

[0224] In various embodiments, the spatial RX parameters can include one or more of: angle of arrival (“AoA”), dominant AoA, average AoA, angular spread, power angular spectrum (“PAS”) of AoA, average angle of departure (“AoD”), PAS of AoD, transmit and / or receive channel correlation, transmit and / or receive beamforming, and / or spatial channel correlation.

[0225] In some embodiments, an “antenna port” can be a logical port that can correspond to a beam (e.g., produced by beamforming) or can correspond to a physical antenna on a device. In certain embodiments, a physical antenna can be mapped directly to a single antenna port, where the antenna port corresponds to the actual physical antenna. In various embodiments, a set of physical antennas, a subset of physical antennas, an antenna set, an antenna array, or an antenna subarray can be mapped to one or more antenna ports after applying complex weightings and / or cyclic delays to signals on each physical antenna. The set of physical antennas can have antennas from a single module or panel or from multiple modules or panels. The weightings can be fixed as in antenna virtualization schemes such as cyclic delay diversity (“CDD”). The process for deriving an antenna port from a physical antenna can be specific to device implementation and transparent to other devices.

[0226] In various embodiments, a transmission configuration indicator (“TCI”) state associated with a target transmission can indicate a quasi co-location relationship between the target transmission (e.g., a target RS for a demodulation reference signal (“DM-RS”) port of the target transmission during a transmission occasion) and a source reference signal (e.g., a synchronization signal block (“SSB”), a channel state information reference signal (“CSI-RS”), and / or a sounding reference signal (“SRS”)) with respect to a quasi co-location type parameter indicated in the corresponding TCI state. A device can receive a configuration of multiple transmission configuration indicator states of a serving cell for transmissions on the serving cell (e.g., between a parent IAB-DU and an IAB-node MT).

[0227] In some embodiments, spatial relationship information associated with a target transmission can indicate a spatial setup between the target transmission and a reference RS (e.g., an SSB, a CSI-RS, and / or an SRS). For example, a UE can transmit the target transmission with a same spatial domain filter used to receive the reference RS (e.g., a DL RS such as an SSB and / or a CSI-RS). In another example, a UE can transmit the target transmission with a same spatial domain transmission filter used for transmission of the RS (e.g., an UL RS such as an SRS). A device can receive a configuration of multiple spatial relationship information configurations for a serving cell for transmissions on the serving cell.

[0228] As described herein, an entity can be referred to as an IAB node. As can be appreciated, embodiments referring to an IAB node can also refer to an IAB donor (which is an IAB entity that connects a core network to an IAB network).

[0229] Different steps described herein for different embodiments can be interchanged.

[0230] Each configuration described herein can be provided by one or more configurations. In some embodiments, an earlier configuration described herein can provide a subset of parameters, whereas a later configuration can provide another subset of parameters. In certain embodiments, a later configuration can override values provided by an earlier configuration or a pre-configuration.

[0231] In various embodiments, a configuration can be provided by radio resource control (“RRC”) signaling, medium access control (“MAC”) signaling, physical layer signaling such as a downlink control information (“DCI”) message, and / or other means. Further, in such embodiments, a configuration can include a pre-configuration or semi-static configuration provided by a standard, a vendor, a network, and / or an operator. Each parameter value received by a configuration or indication can override a previous value of a similar parameter.

[0232] As can be appreciated, the embodiments described herein can be applicable to any wireless system, wireless relay node, and / or other type of wireless communication entity.

[0233] In some embodiments, certain beams on one panel can cause significant interference to another panel, and thus, certain combinations of beams can be avoided. Such issues can be avoided by using early TCI indication transmitted to N2.

[0234] In various embodiments, the embodiments described herein can change based on paired spectrum. As used herein, “HARQ-ACK” can collectively represent an acknowledgement (“ACK”) and a negative acknowledgement (“NACK”). An ACK can mean that a transport block (“TB”) was received correctly, whereas a NACK (or NAK) can mean that the TB was received incorrectly.

[0235] Figure 16 FIG. 15 is a flow diagram illustrating one embodiment of a method 1500 for spatial parameter capability indication. In some embodiments, the method 1500 is performed by an apparatus, such as the remote unit 102 and / or the network unit 104. In certain embodiments, the method 1500 can be performed by a processor executing program code, for example, a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0236] In various embodiments, the method 1600 includes receiving 1602, at a first wireless node, a first control message from a second wireless node, wherein the first control message includes a first indication of a first resource and a first spatial indication. In some embodiments, the method 1600 includes determining 1604 whether a second resource overlaps in a time domain with the first resource and whether a time of reception of the first control message is not later than a time threshold. In various embodiments, the method 1600 includes, in response to the second resource overlapping in the time domain with the first resource and the time of reception of the first control message being not later than the time threshold, transmitting 1606 a second control message to a third device, wherein the second control message includes a second indication of the second resource and a second spatial indication indicating that the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and a second spatial parameter according to the second spatial indication.

[0237] In certain embodiments, the time threshold is determined based on a minimum duration for decoding, by the first wireless node, the first control message, encoding the second control message, and transmitting the second control message. In some embodiments, the time threshold is equal to a time of the first resource minus the minimum duration. In various embodiments, the time threshold is equal to a time of the second resource minus the minimum duration.

[0238] In one embodiment: the first spatial indication is a first transmission configuration indicator state and the first resource is a downlink resource; or the first spatial indication is a first spatial relation information parameter and the first resource is an uplink resource. In certain embodiments: the second spatial indication is a second transmission configuration indicator state and the second resource is a downlink resource; or the second spatial indication is a second spatial relation information parameter and the second resource is an uplink resource. In some embodiments, the capability is determined based on a number of antenna panels at the first wireless node.

[0239] In various embodiments, the capability is determined based on whether the first wireless node includes full duplex capability. In one embodiment, the capability is determined based on whether the first resource and the second resource overlap in a frequency domain. In certain embodiments, the capability is further determined based on whether the first spatial parameter is equal to the second spatial parameter.

[0240] In some embodiments, the second wireless node provides a first serving cell for the first wireless node and the first wireless node provides a second serving cell for a third wireless node. In various embodiments, the method further includes: performing a first operation on the first resource while applying the first spatial parameter, wherein the first operation includes a first transmission to the second wireless node and a first reception from the second wireless node; and performing a second operation on the second resource while applying the second spatial parameter, wherein the second operation includes a first transmission to the third wireless node and a second reception from the third wireless node.

[0241] In one embodiment, a method includes: receiving, at a first wireless node, a first control message from a second wireless node, wherein the first control message includes a first indication of a first resource and a first spatial indication; determining whether a second resource overlaps with the first resource in a time domain and a reception time of the first control message is not later than a time threshold; and in response to the second resource overlapping with the first resource in the time domain and the reception time of the first control message being not later than the time threshold, transmitting a second control message to a third device, wherein the second control message includes a second indication of the second resource and a second spatial indication that indicates the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and applying a second spatial parameter according to the second spatial indication.

[0242] In certain embodiments, the time threshold is determined based on a minimum duration for decoding, by the first wireless node, the first control message, encoding the second control message, and transmitting the second control message.

[0243] In some embodiments, the time threshold is equal to a time of the first resource minus the minimum duration.

[0244] In various embodiments, the time threshold is equal to a time of the second resource minus the minimum duration.

[0245] In one embodiment: the first spatial indication is a first transmission configuration indicator state and the first resource is a downlink resource; or the first spatial indication is a first spatial relation information parameter and the first resource is an uplink resource.

[0246] In certain embodiments: the second spatial indication is a second transmission configuration indicator state and the second resource is a downlink resource; or the second spatial indication is a second spatial relation information parameter and the second resource is an uplink resource.

[0247] In some embodiments, the capability is determined based on a number of antenna panels at the first wireless node.

[0248] In various embodiments, the capability is determined based on whether the first wireless node includes full duplex capability.

[0249] In one embodiment, the capability is determined based on whether the first resource and the second resource overlap in a frequency domain.

[0250] In certain embodiments, the capability is further determined based on whether the first spatial parameter is equal to the second spatial parameter.

[0251] In some embodiments, the second wireless node provides a first serving cell for the first wireless node, and the first wireless node provides a second serving cell for the third wireless node.

[0252] In various embodiments, the method further includes: performing a first operation on the first resource while applying the first spatial parameter, wherein the first operation includes a first transmission to the second wireless node and a first reception from the second wireless node; and performing a second operation on the second resource while applying the second spatial parameter, wherein the second operation includes a first transmission to the third wireless node and a second reception from the third wireless node.

[0253] In one embodiment, an apparatus includes: a receiver that receives, at a first wireless node, a first control message from a second wireless node, wherein the first control message includes a first indication of a first resource and a first spatial indication; a processor that determines whether a second resource overlaps with the first resource in a time domain and a reception time of the first control message is not later than a time threshold; and a transmitter that transmits, in response to the second resource overlapping with the first resource in the time domain and the reception time of the first control message being not later than the time threshold, a second control message to a third device, wherein the second control message includes a second indication of the second resource and a second spatial indication that indicates the first wireless node is capable of simultaneously applying a first spatial parameter according to the first spatial indication and applying a second spatial parameter according to the second spatial indication.

[0254] In certain embodiments, the time threshold is determined based on a minimum duration for decoding, by the first wireless node, the first control message, encoding, and transmitting the second control message.

[0255] In some embodiments, the time threshold is equal to a time of the first resource minus the minimum duration.

[0256] In various embodiments, the time threshold is equal to a time of the second resource minus the minimum duration.

[0257] In one embodiment: the first spatial indication is a first transmission configuration indicator state and the first resource is a downlink resource; or the first spatial indication is a first spatial relation information parameter and the first resource is an uplink resource.

[0258] In certain embodiments: the second spatial indication is a second transmission configuration indicator state and the second resource is a downlink resource; or the second spatial indication is a second spatial relation information parameter and the second resource is an uplink resource.

[0259] In some embodiments, the capability is determined based on a number of antenna panels at the first wireless node.

[0260] In various embodiments, the capability is determined based on whether the first wireless node includes full duplex capability.

[0261] In one embodiment, the capability is determined based on whether the first resource and the second resource overlap in a frequency domain.

[0262] In certain embodiments, the capability is further determined based on whether the first spatial parameter is equal to the second spatial parameter.

[0263] In some embodiments, the second wireless node provides a first serving cell for the first wireless node, and the first wireless node provides a second serving cell for a third wireless node.

[0264] In various embodiments, the processor: performs a first operation on the first resource while applying the first spatial parameter, wherein the first operation includes a first transmission to the second wireless node and a first reception from the second wireless node; and performs a second operation on the second resource while applying the second spatial parameter, wherein the second operation includes a first transmission to the third wireless node and a second reception from the third wireless node.

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

Claims

1. An apparatus for wireless communication, the apparatus comprising a first integrated access and backhaul (IAB) node, the apparatus further comprising: processor; and A memory, coupled to the processor, the processor being configured to cause the device to: Receive from the second IAB node the quasi-co-located QCL indication and the Media Access Control (MAC) control element (CE) of the first resource set; and For the IAB distribution unit IAB-DU of the IAB node, determine whether communication is performed based on the QCL indication and whether the second resource set associated with the communication overlaps with the first resource set in time.

2. The apparatus according to claim 1, wherein, The second IAB node is the parent node of the first IAB node.

3. The apparatus according to claim 1, wherein, The MAC CE further includes a Transmission Configuration Indicator (TCI) status associated with the IAB mobile terminal (IAB-MT) of the IAB node.

4. The apparatus according to claim 1, wherein, The resource set is configured via Radio Resource Control (RRC) signaling.

5. The apparatus according to claim 1, wherein, The communication is transmission, reception, or a combination thereof.

6. A method at a first integrated access and backhaul IAB node, the method comprising: Receive the quasi-co-located QCL instruction and the Media Access Control (MAC) control element CE of the first resource set from the second IAB node; as well as For the IAB distribution unit IAB-DU of the IAB node, determine whether communication is performed based on the QCL indication and whether the second resource set associated with the communication overlaps with the first resource set in time.

7. The method according to claim 6, wherein, The second IAB node is the parent node of the first IAB node.

8. The method according to claim 6, wherein, The MAC CE further includes a Transmission Configuration Indicator (TCI) status associated with the IAB mobile terminal (IAB-MT) of the IAB node.

9. The method according to claim 6, wherein, The resource set is configured via Radio Resource Control (RRC) signaling.

10. The method according to claim 6, wherein, The communication is transmission, reception, or a combination thereof.

11. An apparatus for wireless communication, the apparatus comprising a first integrated access and backhaul (IAB) node, the apparatus further comprising: processor; and A memory, coupled to the processor, the processor being configured to cause the device to: Receive Media Access Control (MAC) control element (CE) from the parent node, wherein the MAC CE indicates a Quasi-Co-located QCL indication and a first resource set; as well as For the IAB Distribution Unit (IAB-DU) of the IAB node, determine whether to perform a transmission, reception, or a combination thereof based on at least a portion of the QCL indication, and whether the second resource set associated with the transmission, reception, or combination thereof overlaps with the first resource set in time.

12. The apparatus according to claim 11, wherein, The MAC CE further includes a Transmission Configuration Indicator (TCI) state associated with the IAB mobile terminal (IAB-MT) of the IAB node, and the processor causes the device to make a determination based further on the TCI state.

Images