IAB Node Sends MAC CE Message

Abstract

Apparatuses, methods, and systems for transmitting a MAC CE message by an IAB node are disclosed. One method (1700) includes transmitting a MAC CE message at a first IAB node to a second IAB node (1702). The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with a MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Patent Application No. 63 / 229,908, filed on August 5, 2021 in favor of Majid Ghanbarinejad et al., entitled “APPARATUSES, METHODS, AND SYSTEMS FOR POWER HEADROOM SIGNALING IN INTEGRATED ACCESS AND BACKHAUL,” which is incorporated by reference in its entirety herein.

[0002] The subject matter disclosed herein relates generally to wireless communications, and more particularly, to transmission of MAC CE messages by IAB nodes. [Background technology]

[0003] In some wireless communication networks, information corresponding to an IAB system may not be known, and in such networks, the information may need to be provided to the device. Summary of the Invention [Means for solving the problem]

[0004] A method is disclosed for transmitting a MAC CE message by an IAB node. Apparatus and systems also perform the functions of the method. One embodiment of the method includes transmitting a MAC CE message at a first IAB node to a second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell of a DU, or some combination thereof.

[0005] An apparatus for transmitting a MAC CE message by an IAB node includes a transmitter for transmitting a MAC CE message to a second IAB node, the MAC CE message including an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0006] Another embodiment of a method for transmitting a MAC CE message by an IAB node includes transmitting a MAC CE message at a first IAB node to a second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof. The MAC CE message indicates that the parent node applies the range in response to use by the first IAB node of resources associated with the resource configuration, application by the first IAB node of the indicated multiplexing mode, application by the first IAB node of a beam indicated by the at least one uplink beam identifier, or some combination thereof.

[0007] Another apparatus for transmitting a MAC CE message by an IAB node includes a transmitter for transmitting a MAC CE message to a second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell with a DU, or some combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof. The MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying the beam indicated by the at least one uplink beam identifier, or some combination thereof.

[0008] A more particular description of the present embodiments briefly described above will now be expressed by reference to specific embodiments that are shown in the accompanying drawings. The present embodiments will be described and explained with additional particularity and detail through the use of the accompanying drawings, with the understanding that these drawings are only illustrative of some embodiments and therefore should not be considered limiting in scope. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for transmitting MAC CE messages by an IAB node. [Diagram 2]FIG. 2 is a schematic block diagram illustrating an embodiment of an apparatus that may be used by an IAB node to transmit a MAC CE message. [Diagram 3] FIG. 2 is a schematic block diagram illustrating an embodiment of an apparatus that may be used by an IAB node to transmit a MAC CE message. [Figure 4] FIG. 1 is a schematic block diagram illustrating one embodiment of an IAB system in a stand-alone mode. [Diagram 5] FIG. 2 is a schematic block diagram illustrating another embodiment of a system. [Figure 6] FIG. 1 is a schematic block diagram illustrating an embodiment of an IAB system having a single-panel IAB node and a multi-panel IAB node. [Figure 7] FIG. 1 is a schematic block diagram illustrating one embodiment of a type of simultaneous transmit and / or receive operation. [Figure 8] 2 is a block diagram illustrating one embodiment of a single-entry PHR MAC CE. [Figure 9] 1 is a block diagram illustrating one embodiment of a multiple-entry PHR MAC CE where the maximum ServCellIndex of serving cells with configured uplinks is less than 8. FIG. [Figure 10] 13 is a block diagram illustrating another embodiment of a multiple-entry PHR MAC CE where the maximum ServCellIndex of serving cells with configured uplinks is equal to or greater than 8. [Figure 11] FIG. 13 is a code diagram illustrating one embodiment of a PHR-Config IE. [Figure 12] 1 is a block diagram illustrating one embodiment of a system including a target IAB node (N) transmitting to a parent node or IAB donor (PN) upstream of the IAB node and a child node or UE downstream of the IAB node. [Figure 13] FIG. 13 is a code diagram illustrating one embodiment of an RRC configuration IE. [Figure 14]FIG. 1 is a schematic block diagram illustrating an embodiment of a DC architecture having one IAB-CU and / or IAB donor (intra-donor scenario). [Figure 15] FIG. 1 is a schematic block diagram illustrating an embodiment of a DC architecture having multiple IAB-CUs and / or IAB donors (intra-donor scenario). [Figure 16] FIG. 1 is a schematic block diagram of an embodiment of a system illustrating alternative scenarios for concurrent operations. [Figure 17] FIG. 2 is a flow chart illustrating one embodiment of a method for transmitting a MAC CE message by an IAB node. [Figure 18] FIG. 11 is a flow chart diagram illustrating another embodiment of a method for sending a MAC CE message by an IAB node. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] As will be appreciated by those skilled in the art, aspects of the present embodiments may be embodied as a system, apparatus, method, or program product. Thus, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be generally referred to herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmitting. The storage devices may not embody signals. In some embodiments, the storage devices merely employ signals to access the code.

[0011] Some of the functional units described herein may be labeled as modules to more fully emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0012] Modules may also be implemented in code and / or software for execution by various types of processors. An identified module of code may include, for example, one or more physical or logical blocks of executable code, which may be organized, for example, as an object, procedure, or function. Although, the executable files of an identified module need not be physically located together, but may include different instructions stored in various locations that, when logically combined together, comprise the module and achieve a stated purpose for the module.

[0013] Indeed, a module of code may be a single instruction or many instructions and may even be distributed across several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and described herein in modules and may be embodied in any suitable form and organized in any suitable type of data structure. The operational data may be collected as a single data set or distributed across different locations, including across different computer-readable storage devices. If a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

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

[0015] More detailed examples (non-exhaustive list) of storage devices 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 disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this specification, a computer-readable storage medium may 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.

[0016] Code for carrying out operations for the embodiments may be any number of lines and written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine code such as assembly language. The code may run entirely on the user's computer, partially on the user's computer, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server, as a standalone software package. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or wide area network ("WAN"), or a connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider).

[0017] References throughout this specification to "one embodiment," "embodiment," or similar words mean that a particular feature, structure, or characteristic described with respect to this embodiment is included in at least one embodiment. Thus, all occurrences of the phrases "in one embodiment," "in an embodiment," or similar words throughout this specification may, but do not necessarily, refer to the same embodiment and may mean "one or more, but not all, embodiments" unless otherwise specified. The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless otherwise specified. Enumerated listings of items do not necessarily imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more" unless otherwise specified.

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

[0019] Aspects of the present embodiments are described below with reference to schematic flow chart diagrams and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow chart diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flow chart diagrams and / or schematic block diagrams, may be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for performing the functions / acts specified in one or more blocks of the schematic flow chart diagrams and / or schematic block diagrams.

[0020] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the storage device create an article of manufacture that includes instructions that implement the functions / acts specified in one or more blocks of the schematic flow chart illustrations and / or schematic block diagrams.

[0021] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to create a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for performing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.

[0022] The schematic flow chart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow chart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that comprises one or more executable instructions of code for implementing a specified logical function(s).

[0023] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially in parallel, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be devised that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures.

[0024] Various arrow and line types may be employed in the flowcharts and / or block diagrams, but it is understood that they do not limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiments. For example, the arrows may indicate waiting or monitoring periods of unspecified duration between recited steps of the illustrated embodiments. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or a combination of dedicated hardware and code.

[0025] The description of an element in each figure may refer to the element in the succeeding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0026] 1 illustrates an embodiment of a wireless communication system 100 for transmitting a MAC CE message by an IAB node. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Those skilled in the art will recognize that although a certain number of remote units 102 and network units 104 are illustrated in FIG. 1, any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0027] In one embodiment, the remote units 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, gaming consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, modems), airborne vehicles, drones, etc. In some embodiments, the remote units 102 include wearable devices such as smart watches, fitness bands, optical head-mounted displays, etc. Additionally, the remote units 102 may be referred to as subscriber units, mobile, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UEs, user terminals, devices, or other terms used in the art. The remote units 102 may directly communicate with one or more of the network units 104 via UL communication signals. In some embodiments, the remote units 102 may directly communicate with other remote units 102 via sidelink communications.

[0028] The network units 104 may be distributed across a geographical region. In some embodiments, the network units 104 may also be an access point, an access terminal, a base, a base station, a location server, a core network ("CN"), a radio network entity, a Node B, an evolved Node B ("eNB"), a 5G Node B ("gNB"), a home Node B, a relay node, a device, a core network, an air server, a radio access node, an access point ("AP"), a new radio ("NR"), a network entity, an access and mobility management function ("AMF"), a unified data management ("UDM"), a unified data repository ("UDM"). The network unit 104 may be referred to by and / or include one or more of: a Radio Access Function ("RAN"), a User Datagram Protocol (UDM) / User Datagram Protocol (UDR), a Policy Control Function ("PCF"), a Radio Access Network ("RAN"), a Network Slice Selection Function ("NSSF"), an Operation, Administration, and Management ("OAM"), a Session Management Function ("SMF"), a User Plane Function ("UPF"), an Application Function, an Authentication Server Function ("AUSF"), a Security Anchor Functionality ("SEAF"), a Trusted Non-3GPP Gateway Function ("TNGF"), or other terms used in the art. The network unit 104 is generally part of a radio access network including one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the Public Switched Telephone Network, among other networks. These and other elements of the radio access and core networks are not shown, but are generally well known by those skilled in the art.

[0029] In one implementation, the wireless communication system 100 complies with the NR protocol standardized in the 3rd Generation Partnership Project ("3GPP"), where the network unit 104 transmits using an OFDM modulation scheme on the downlink ("DL") and the remote unit 102 transmits on the uplink ("UL") using a Single Carrier Frequency Division Multiple Access ("SC-FDMA") scheme or an Orthogonal Frequency Division Multiplexing ("OFDM") scheme. More generally, however, the wireless communications system 100 may implement a number of other open or proprietary communications protocols, such as WiMAX, Institute of Electrical and Electronics Engineers ("IEEE") 802.11 variants, Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), Universal Mobile Telecommunications System ("UMTS"), Long Term Evolution ("LTE") variants, Code Division Multiple Access 2000 ("CDMA2000"), Bluetooth, ZigBee, Sigfox, among others. This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0030] The network unit 104 may serve a number of remote units 102 in a serving area, e.g., a cell or a cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0031] In various embodiments, the remote unit 102 and / or the network unit 104 may transmit a MAC CE message to the second IAB node. The MAC CE message may include an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with a MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or any combination thereof. Thus, the remote unit 102 and / or the network unit 104 may be used to transmit the MAC CE message by the IAB node.

[0032] In some embodiments, the remote unit 102 and / or the network unit 104 may transmit a MAC CE message at the first IAB node to the second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or any combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmits and DU transmits, MT receives and DU receives, MT transmits and DU receives, MT receives and MT transmits, or any combination thereof. The MAC CE message indicates that the first IAB node uses resources associated with the resource configuration, that the first IAB node applies the indicated multiplexing mode, that the first IAB node applies the beam indicated by the at least one uplink beam identifier, or that the parent node applies the range in response to some combination thereof. Thus, the remote unit 102 and / or the network unit 104 may be used to transmit the MAC CE message by the IAB node.

[0033] 2 illustrates an embodiment of an apparatus 200 that may be used by an IAB node to transmit a MAC CE message. The apparatus 200 includes an embodiment of a remote unit 102. Additionally, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0034] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 202 may 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 a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

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

[0036] The input device 206, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 206 may 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 may be entered 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.

[0037] Display 208, in one embodiment, may include any known electronically controllable display or display device. Display 208 may be designed to output visual, audible, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may 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, and the like to a user. As another non-limiting example, display 208 may include a wearable display, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, display 208 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

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

[0039] In some embodiments, the transmitter 210 transmits a MAC CE message to the second IAB node, the MAC CE message including an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0040] In some embodiments, the transmitter 210 transmits a MAC CE message to the second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof. The MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying the beam indicated by the at least one uplink beam identifier, or some combination thereof.

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

[0042] 3 illustrates an embodiment of an apparatus 300 that may be used to transmit a MAC CE message by an IAB node. The apparatus 300 includes an embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0043] In some embodiments, the transmitter 310 transmits a MAC CE message to the second IAB node, the MAC CE message including an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0044] In some embodiments, the transmitter 310 transmits a MAC CE message to the second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof. The MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying the beam indicated by the at least one uplink beam identifier, or some combination thereof.

[0045] It should be noted that one or more embodiments described herein may be combined in a single embodiment.

[0046] In some embodiments, integrated access and backhaul ("IAB") may be used for new radio ("NR") access technology. IAB technology aims to increase deployment flexibility and lower fifth generation ("5G") rollout costs. Moreover, IAB allows service providers to reduce cell planning and spectrum planning efforts while using wireless backhaul technology.

[0047] In some embodiments, the IAB is not limited to a particular multiplexing and duplexing scheme, but may focus on time division multiplexing ("TDM") between upstream communications (e.g., with a parent IAB node or IAB donor) and downstream communications (e.g., with a child IAB node or UE).

[0048] In various embodiments, the IAB system enhanced resource multiplexing to support simultaneous operation (e.g., transmit and / or receive) in the downstream and upstream by an IAB node includes, as necessary, a) support for simultaneous operation (e.g., transmit and / or receive) of a child link and a parent link of an IAB node (e.g., mobile terminal (“MT”) MT transmit (“TX”) and distributed unit (“DU”) TX, MT TX and DU receive (“RX”), MT RX and DU TX, MT RX and DU RX ... and / or 2) duplexing extensions, such as extensions to IAB node timing modes, downlink ("DL") and / or UL power control, and specification of a command line interface ("CLI") and interference measurements for the backhaul ("BH") link, including support for dual connectivity scenarios specified in the context of 1) IAB node timing modes, downlink ("DL") and / or UL power control, and / or 2) IAB node timing modes, downlink ("DL") and / or UL power control, and specification of a command line interface ("CLI") and interference measurements for the backhaul ("BH") link.

[0049] In some embodiments, extensions to power control in the uplink and / or downlink may be used to help the IAB system enforce a greater number of transmit power constraints, such as power imbalance and total power constraints.

[0050] In some embodiments, a power imbalance constraint may be enforced by a difference in transmit power of signals transmitted by one or more (e.g., collocated) antenna panels, or a difference in receive power of signals received by one or more (e.g., collocated) antenna panels. The power imbalance may be enforced by hardware and may additionally affect beamforming on any or all antenna panels.

[0051] In various embodiments, the total power constraint may be imposed by hardware, radiated power regulations such as Federal Communications Commission ("FCC") regulations, or a combination thereof.

[0052] In some embodiments, there may be conditions under which an IAB node may simultaneously transmit signals to a parent node and / or donor and a child node and / or user equipment ("UE"). In such embodiments, an IAB node may have two constraints on its maximum transmit power to a parent node: 1) one determined by the power headroom ("PH") associated with the total transmit power by the IAB node, and 2) the other determined by the maximum power imbalance between simultaneous transmissions to the parent node and / or donor and the child node and / or UE.

[0053] In various embodiments, a determination may be made as to how information should be conveyed to a parent node and / or donor that performs uplink power control ("UL-PC") on the IAB node's IAB-MT.

[0054] In some embodiments, power headroom reports ("PHRs") may dynamically inform parent nodes and / or donors of variations caused by transmissions to child nodes and / or UEs. However, in such embodiments, 1) there may be changes in power constraints due to transmissions to child nodes and / or UEs, which may be overly dynamic and changing rapidly (e.g., from slot to slot) since not all slots are used for simultaneous transmissions, and 2) an IAB node may transmit to multiple child nodes and / or UEs, and there may be extensions to allow for several downlink power control ("DL-PC") mechanisms to different child nodes and / or UEs as well as adding additional variations to the uplink transmit power constraints.

[0055] In some embodiments, it may be determined whether a legacy UL power control mechanism (e.g., including PHR) is sufficient for an IAB node operating in an enhanced multiplexing mode. It may be supported for an IAB node to indicate information to assist in its UL power control. In various embodiments, it may be determined whether to support an IAB node to indicate assistance information to aid in the UL TX power control of its MT. The assistance information may be 1) a desired TX power, 2) an offset to the baseline PHR, 3) a desired dynamic range, 4) whether assistance information is provided to a parent node, a CU, or both, and / or 5) whether the UL TX power control formula of the MT needs to be changed.

[0056] In some embodiments, there may be a method and system that accommodates PHR signaling.

[0057] FIG. 4 is a schematic block diagram illustrating an embodiment of an IAB system 400 in a standalone mode. The IAB system 400 includes a core network ("CN") 402, an IAB donor 404, an IAB node 406, and a UE 408. The CN 402 is connected to the IAB donor 404 of the IAB system 400 through a backhaul link, which is typically wired. The IAB donor 404 includes a central unit ("CU") that communicates with all distributed units ("DUs") in the system through an F1 interface. The IAB donor 404 is a single logical node that may include a set of functions such as gNB-DU, gNB-CU-CP, gNB-CU-UP, etc. In some deployments, the IAB donor 404 may be divided according to these functions, and all such functions may be either co-located or not co-located. Moreover, each IAB node may be functionally divided into at least a DU and a mobile terminal ("MT"). An MT of an IAB node may be connected to a DU of a parent node, which may be another IAB node or an IAB donor. The Uu link between an MT of an IAB node (referred to as IAB-MT) and a DU of a parent node (referred to as IAB-DU) is referred to as a wireless backhaul link. In a wireless backhaul link, from the functionality point of view, an MT is similar to a UE and a DU of a parent node is similar to a base station in a conventional cellular wireless access link. Thus, a link from an MT to a serving cell, which is a DU of the parent link, is referred to as an uplink and a link in the reverse direction is referred to as a downlink. As used herein, embodiments may refer to an uplink or downlink between IAB nodes, an upstream or downstream link of an IAB node, a link between a node and its parent node, a link between a node and its child node, etc., without direct reference to an IAB-MT, an IAB-DU, a serving cell, etc.

[0058] Each IAB donor or IAB node may serve a UE through an access link. The IAB system may be designed to enable multi-hop communication (e.g., a UE may be connected to a core network through an access link and multiple backhaul links between the IAB nodes and the IAB donors). As used herein, unless otherwise noted, an IAB node may refer to an IAB node or an IAB donor.

[0059] FIG. 5 is a schematic block diagram illustrating another embodiment of a system 500. In particular, FIG. 5 illustrates a functional split between an IAB donor and an IAB node. In this figure, an IAB node or UE can be served by two or more serving cells since it supports dual connectivity ("DC"). The system 500 includes a CN 502, an IAB system 504, and a UE 506. The CU and / or DU ("CU / DU") split is in the IAB donor in the IAB system 504, and the DU / MT split is in the IAB node in the IAB system 504.

[0060] Note that nodes and / or links closer to the IAB donor and / or CN 502 are referred to as upstream nodes and / or upstream links. For example, a parent node of a node of interest is an upstream node of the node of interest, and a link to the parent node is an upstream link to the node of interest. Similarly, nodes and / or links farther from the IAB donor and / or core network are referred to as downstream nodes and / or downstream links. For example, a child node of a node of interest is a downstream node of the node of interest, and a link to the child node is a downstream link to the node of interest.

[0061] Table 1 summarizes the terminology used herein for brevity, as it may appear in a specification.

[0062] [Table 1]

[0063] In some embodiments, "operation" or "communication" may refer to transmission or reception on the uplink (or upstream) or downlink (or downstream). Additionally, the term "concurrent operation" or "concurrent communication" may refer to multiplexed and / or duplexed transmission and / or reception by a node through one or more antennas and / or panels. Concurrent operation may be understood from the context if not explicitly stated.

[0064] In some embodiments, multiple slot formats may be used to allow for greater flexibility.

[0065] In some embodiments, resources may be configured as hard ("H"), soft ("S"), or unavailable ("NA"). Hard resources may be assumed available for scheduling by IAB nodes, NA resources may not be assumed available, and soft resources may be dynamically indicated as available or unavailable. Dynamic availability indication ("AI") for soft resources may be performed by DCI format 2_5 from parent IAB nodes and / or donors, and may have similarity in format and definition to SFI (e.g., DCI format 2_0).

[0066] In various embodiments, resources may be shared between the backhaul and the access link, which may be configured semi-statically by the CU (e.g., an IAB donor at Layer 3) or dynamically by the DU (e.g., a parent IAB node at Layer 1). Multiplexing between the backhaul and access link resources may be TDM, frequency division multiplexing ("FDM"), or may enable time-frequency resource sharing. Furthermore, resources may be allocated strictly (e.g., per node or per link) or in the form of a resource pool.

[0067] In some embodiments, semi-static configuration at Layer 2 or Layer 3 may be allowed to share resources between backhaul and access. Note that the emphasis may be on configuring resources for backhaul vs. access rather than upstream vs. downstream. However, under dynamic scheduling, an IAB node may use resources that are not used by the parent IAB node for backhaul scheduling access links.

[0068] In some embodiments, semi-static resource versus dynamic resource coordination may be used. In various embodiments, flexible ("F") in DCI2_0 and state access ("A") may be used to determine the slot format and sharing of resources may use the access link.

[0069] In some embodiments, the IAB system may be connected to a core network through one or more IAB donors. Further, each IAB node may be connected to the IAB donors and / or other IAB nodes through wireless backhaul links. Each IAB donor and / or each IAB node may also serve UEs.

[0070] 6 is a schematic block diagram illustrating an embodiment of an IAB system 600 having single-panel and multi-panel IAB nodes. The IAB system 600 includes a core network 602, an IAB donor and / or parent IAB node 604, an IAB node 2 (e.g., multi-panel) 606, and an IAB node 1 (e.g., single panel) 608.

[0071] There are various options regarding the structure and multiplexing and / or duplexing capabilities of IAB nodes. For example, each IAB node may have one or more antenna panels, each connected to a baseband unit through a radio frequency ("RF") chain. One or more antenna panels may be able to serve a wide spatial area of ​​interest in the vicinity of the IAB node, or each antenna panel or group of antenna panels may otherwise provide partial coverage, such as a "sector." An IAB node having multiple antenna panels, each serving a separate spatial area or sector, may still be referred to as a single-panel IAB node, since it behaves similarly to a single-panel IAB node for communication in each of the separate spatial areas or sectors.

[0072] In some embodiments, each antenna panel may be half-duplex ("HD"), meaning capable of either transmitting or receiving signals at one time within a frequency band, or full-duplex ("FD"), meaning capable of both transmitting and receiving signals simultaneously within a frequency band. Unlike full-duplex radios, half-duplex radios are widely implemented and used in practice, and may be assumed to be the default mode of operation in wireless systems.

[0073] Table 2 lists various duplexing scenarios of interest where the multiplexing is not constrained to time division multiplexing ("TDM"). Table 2 considers single-panel and multi-panel IAB nodes for various cases of simultaneous transmission and / or reception. Spatial division multiplexing ("SDM") may refer to either transmitting or receiving on the downlink (or downstream) and uplink (or upstream) simultaneously, full duplex ("FD") may refer to simultaneous transmission and reception by the same antenna panel within a frequency band, and multi-panel transmit and receive ("MPTR") may refer to simultaneous transmission and / or reception by multiple antenna panels, where each antenna panel is either transmitting or receiving at one time within a frequency band.

[0074] [Table 2]

[0075] In Table 2, based on the type of concurrent operations and the number of panels at the IAB node, the scenarios are called S1, S2, ..., S8, and the "case" numbers (e.g., A / B / C / D or 1 / 2 / 3 / 4) may follow Figure 7.

[0076] FIG. 7 is a schematic block diagram 700 illustrating one embodiment of a type of simultaneous transmission and / or reception operation. The diagram 700 illustrates a first case 702 (e.g., case number 1, case A, MT TX and DU TX) having an MT 704 and a DU 706, where the MT 704 transmits (708) and the DU 706 transmits (710). Moreover, the diagram 700 illustrates a second case 712 (e.g., case number 2, case B, MT RX and DU RX) having an MT 704 and a DU 706, where the MT 704 receives (714) and the DU 706 receives (716). Furthermore, the diagram 700 illustrates a third case 718 (e.g., case number 3, case C, MT TX and DU RX) having an MT 704 and a DU 706, where the MT 704 transmits (720) and the DU 706 receives (722). Diagram 700 shows a fourth case 724 (e.g., case number 4, case D, MT RX and DU TX) having an MT 704 and a DU 706, where the MT 704 receives (726) and the DU 706 transmits (728). As used herein, the various cases may be referred to by case number, case letter, or description as found in FIG.

[0077] In various embodiments, there may be PHR signaling.

[0078] In some embodiments, there may be power headroom reports defined as found herein. The types of UE power headroom reports are as follows: Type 1 UE power headroom PH valid for Physical Uplink Shared Channel ("PUSCH") transmission occasion i in active UL Bandwidth Part ("BWP") b of carrier f of serving cell c. Type 3 UE power headroom PH valid for SRS transmission occasion i in active UL BWP b of carrier f of serving cell c.

[0079] In some embodiments, the UE determines whether the power headroom reporting for the activated serving cell is based on an actual transmission or a reference format based on higher layer signaling of the configured grant, periodic and / or semi-persistent sounding reference signal transmissions and downlink control information received by the UE up to and including a physical downlink control channel ("PDCCH") monitoring occasion, where the UE detects a first DCI format that schedules an initial transmission of a transport block since the power headroom reporting is triggered if the power headroom reporting is reported on a PUSCH triggered by the first DCI format. Otherwise, the UE determines whether the power headroom reporting is based on an actual transmission or a reference format based on higher layer signaling of the configured grant, and .... proc,2 =T proc,2 based on periodic and / or semi-persistent sounding reference signal transmissions and downlink control information received by the UE, where T proc,2 d 2,1 =1, d 2,2 μ , which corresponds to the subcarrier spacing of the active downlink BWP of the scheduling cell for the configured grant, assuming μ = 0 and when the power headroom report is reported on the PUSCH using the configured grant. DL It is determined using

[0080] If the UE is configured with two UL carriers for the serving cell and determines a type 1 power headroom report and a type 3 power headroom report for the serving cell, the UE provides a type 1 power headroom report if both the type 1 power headroom report and the type 3 power headroom report are based on the respective actual transmission or the respective reference transmission, and provides a power headroom report based on the respective actual transmission if either the type 1 report or the type 3 report is based on the respective reference transmission.

[0081] If the UE is configured with an SCG, and if the phr-ModeOtherCG for a CG indicates "virtual", then for power headroom reporting transmitted on a CG, the UE calculates PH assuming that the UE does not transmit PUSCH and / or physical uplink control channel ("PUCCH") on any serving cell of the other CG. For NR-DC, when both MCG and SCG operate either in FR1 or in FR2 and for power headroom reporting transmitted on the MCG or SCG, the UE calculates PH assuming that the UE does not transmit PUSCH / PUCCH on any serving cell of the SCG or MCG, respectively.

[0082] If the UE is configured with an SCG, 1) for purposes of calculating the power headroom for a cell belonging to an MCG, the term "serving cell" in this section refers to the serving cell belonging to the MCG, and 2) for purposes of calculating the power headroom for a cell belonging to an SCG, the term "serving cell" in this section refers to the serving cell belonging to the SCG. The term "primary cell" in this section refers to a PSCell of the SCG.

[0083] If the UE is configured with a PUCCH-SCell, 1) for purposes of calculating the power headroom for a cell belonging to the primary PUCCH group, the term "serving cell" in this section refers to the serving cell belonging to the primary PUCCH group, and 2) for purposes of calculating the power headroom for a cell belonging to the secondary PUCCH group, the term "serving cell" in this section refers to the serving cell belonging to the secondary PUCCH group. The term "primary cell" in this section refers to the PUCCH-SCell of the secondary PUCCH group.

[0084] For a UE configured with EN-DC / NE-DC and capable of dynamic power sharing, when an E-UTRA dual connectivity PHR is triggered, 1) if the duration of the NR slot on the active UL BWP is different from that of the E-UTRA subframe carrying the dual connectivity PHR, the UE provides power headroom for the first NR slot that fully overlaps with the E-UTRA subframe, and 2) if the duration of the NR slot on the active UL BWP is the same as that of the E-UTRA subframe carrying the dual connectivity PHR for asynchronous EN-DC and / or NE-DC, the UE provides power headroom for the first NR slot that overlaps with the E-UTRA subframe.

[0085] In various embodiments, there may be a Type 1 PH report: If the UE determines that the Type 1 power headroom report for the activated serving cells is based on the actual PUSCH transmission, for a PUSCH transmission occasion i on an active UL BWP b of carrier f of serving cell c, the UE calculates the Type 1 power headroom report as follows:

[0086]

number

[0087] However, P CMAX,f,c (i), P O_PUSCH,b,f,c (j),

[0088]

number

[0089] , α b,f,c (j), P.L. b,f,c (q d ), Δ TF,b,f,c (i), and f b,f,c (i,l) is defined.

[0090] If a subcarrier spacing ("SCS") configuration μ1 on an active UL BWP b1 of carrier f1 of serving cell c1 is smaller than an SCS configuration μ2 on an active UL BWP b2 of carrier f2 of serving cell c2, and if the UE provides type 1 power headroom reporting in a PUSCH transmission in a slot on active UL BWP b1 that overlaps with multiple slots on active UL BWP b2, then the UE provides a type 1 power headroom report for a first PUSCH on the first slot, if any, of multiple slots on active UL BWP b2 that completely overlaps with the slot on active UL BWP b1. For the same SCS configuration on an active UL BWP b1 on carrier f1 of serving cell c1 and an active UL BWP b2 on carrier f2 of serving cell c2, if the UE is configured with multiple cells for PUSCH transmission, and if the UE provides type 1 power headroom reporting in a PUSCH transmission in a slot on active UL BWP b1, the UE provides type 1 power headroom reporting for the first PUSCH in a slot on active UL BWP b2 that overlaps with the slot on active UL BWP b1, if any.

[0091] If the UE is configured with multiple cells for PUSCH transmission and provides type 1 power headroom reporting in a PUSCH transmission with PUSCH repetition type B that spans multiple slots on the active UL BWP b1 and overlaps with one or more slots on the active UL BWP b2, the UE provides type 1 power headroom reporting for a first PUSCH on the first slot of the one or more slots on the active UL BWP b2 that overlaps with multiple slots of the nominal repetition on the active UL BWP b1, if any.

[0092] For a UE configured with EN-DC and / or NE-DC and capable of dynamic power sharing, when an E-UTRA dual connectivity PHR is triggered, the UE provides power headroom for the first PUSCH, if any, on the determined NR slot.

[0093] When the UE is configured with multiple cells for PUSCH transmission, 1) the second PUSCH transmission is scheduled according to a DCI format in the PDCCH received in the second PDCCH monitoring occasion, and 2) the second PDCCH monitoring occasion is after the first PDCCH monitoring occasion in which the UE detects the earliest DCI format that schedules the initial transmission of the transport block after the power headroom reporting is triggered, or 3) the second PUSCH transmission is within T' of the first uplink symbol of the first PUSCH transmission. proc,2 =T proc,2 , the UE does not intend to perform a Type 1 power headroom report calculation during a first PUSCH transmission including an initial transmission of a transport block on an active UL BWP b1 of carrier f1 of serving cell c1 and a second PUSCH transmission on an active UL BWP b2 of carrier f2 of serving cell c2 that overlaps with the first PUSCH transmission, where T proc,2 d 2,1 =1, d 2,2 Assuming μ = 0 and if there is a first PUSCH transmission on a configured grant after a power headroom report is triggered, the subcarrier spacing of μ corresponding to the active downlink BWP of the scheduling cell for the configured grant. DL It is determined using

[0094] If the UE determines that the type 1 power headroom reporting for an activated serving cell is based on a reference PUSCH transmission, then for a PUSCH transmission occasion i on an active UL BWP b of carrier f of serving cell c, the UE shall

[0095]

number

[0096] Calculate the Type 1 power headroom report as follows:

[0097]

number

[0098] is calculated assuming maximum power attenuation ("MPR") = 0 dB, A-MPR = 0 dB, and P-MPR = 0 dB. C = 0 dB. MPR, A-MPR, P-MPR, and ΔT C The remaining parameters are defined, where P O_PUSCH,b,f,c (j) and α b,f,c (j) is P O_NOMINAL_PUSCH,f,c (0) and p0-PUSCH-AlphaSetId=0, and PL b,f,c (q d ) is obtained using pusch-PathlossReferenceRS-Id=0 and l=0.

[0099] If the UE is configured with two UL carriers for the serving cell and the UE determines the type 1 power headroom report for the serving cell based on the reference PUSCH transmission, the UE calculates the type 1 power headroom report for the serving cell assuming the reference PUSCH transmission on the UL carrier provided by the pusch-Config. If the UE is provided with pusch-Config for both UL carriers, the UE calculates the type 1 power headroom report for the serving cell assuming the reference PUSCH transmission on the UL carrier provided by the pucch-Config. If the UE is not provided with pucch-Config for any of the two UL carriers, the UE calculates the type 1 power headroom report for the serving cell assuming the reference PUSCH transmission on the non-auxiliary UL carrier.

[0100] In some embodiments, there is a Type 2 PH report.

[0101] In various embodiments, there is a Type 3 PH report. If the UE determines that the Type 3 power headroom report for an activated serving cell is based on an actual SRS transmission, for an SRS transmission occasion i on an active UL BWP b of carrier f of serving cell c, if the UE is not configured for PUSCH transmission on carrier f of serving cell c and resources for SRS transmission are provided by SRS-Resource, the UE shall: PH type3,b,f,c (i,q s )=P CMAX,f,c (i)-{P O_SRS,b,f,c (q s )+10log 10 (2 μ M SRS,b,f,c (i)) + α SRS,b,f,c (q s )·PL b,f,c (q d )+h b,f,c (i)}[dB] Calculate the Type 3 power headroom report as follows, where P CMAX,f,c (i), P O_SRS,b,f,c (q s ), M SRS,b,f,c (i), α SRS,b,f,c (q s ), P.L. b,f,c (q d ), and h b,f,c (i) is defined using the corresponding value provided by SRS-ResourceSet.

[0102] When the UE determines that the Type 3 power headroom reporting for the activated serving cell is based on a reference SRS transmission, for an SRS transmission occasion i on UL BWP b of carrier f of serving cell c, if the UE is not configured for PUSCH transmission on UL BWP b of carrier f of serving cell c and resources for the reference SRS transmission are provided by SRS-Resource, the UE shall:

[0103]

number

[0104] Calculate the Type 3 power headroom report as follows, where q s is the SRS resource set corresponding to SRS-ResourceSetId=0 for UL BWP b, and P O_SRS,b,f,c (q s ), α SRS,f,c (q s ), P.L. b,f,c (q d ), and h b,f,c (i) is defined using the corresponding value obtained from SRS-ResourceSetId=0 for UL BWP b.

[0105]

number

[0106] is MPR=0dB, A-MPR=0dB, P-MPR=0dB, and ΔT C = 0 dB. MPR, A-MPR, P-MPR, and ΔT C is prescribed.

[0107] If the UE is configured with two UL carriers for the serving cell, and the UE determines the type 3 power headroom report for the serving cell based on a reference SRS transmission, and resources for the reference SRS are provided by SRS-Resource, the UE calculates the type 3 power headroom report for the serving cell assuming a reference SRS transmission on the UL carrier provided by pucch-Config. If no pucch-Config is provided to the UE for any of the two UL carriers, the UE calculates the type 3 power headroom report for the serving cell assuming a reference SRS transmission on the non-auxiliary UL carrier.

[0108] In various embodiments, there may be a power headroom report. The power headroom reporting procedure is used to provide the serving gNB with the following information: 1) Type 1 power headroom: difference between nominal UE maximum transmit power and estimated power for UL shared channel ("SCH") ("UL-SCH") transmission per activated serving cell, 2) Type 2 power headroom: difference between nominal UE maximum transmit power and estimated power for UL-SCH and PUCCH transmission on SpCells of other MAC entities (e.g., E-UTRA MAC entities in EN-DC, NE-DC, and NGEN-DC cases), 3) Type 3 power headroom: difference between nominal UE maximum transmit power and estimated power for SRS transmission per activated serving cell, and 4) Maximum Permitted Exposure ("MPE") P-MPR: power backoff to meet MPE FR2 requirements for serving cells operating on FR2.

[0109] In some embodiments, the RRC controls power headroom reporting by configuring the following parameters: 1) phr-PeriodicTimer, 2) phr-ProhibitTimer, 3) phr-Tx-PowerFactorChange, 4) phr-Type2OtherCell, 5) phr-ModeOtherCG, 6) multiplePHR, 7) mpe-Reporting-FR2, 8) mpe-ProhibitTimer, and / or 9) mpe-Threshold.

[0110] In some embodiments, the following events may be triggered to disable the feature: 1) the phr-ProhibitTimer expires or has expired and for at least one activated serving cell of any MAC entity whose active DL BWP is not a dormant BWP, which is used as a path loss criterion since the last transmission of the PHR in this MAC entity when the MAC entity has UL resources for a new transmission, the path loss has changed by more than phr-Tx-PowerFactorChange dB (regardless of whether the path loss criterion has changed in between, the path loss variation for a cell assessed above is between the path loss measured at the current time against the current path loss criterion and the path loss measured at the transmission time of the last transmission of the PHR against the path loss criterion in use at that time - note that the current path loss criterion for this purpose does not include any path loss criterion configured using pathlossReferenceRS-Pos); 2) the phr-PeriodicTimer expires; 3) a power headroom reset by higher layers that is not used to disable the feature. 4) activation of a SCell of any MAC entity with a configured uplink whose firstActiveDownlinkBWP-Id is not set to dormant BWP; 5) addition of a PSCell (e.g. a PSCell is newly added or modified); 6) the MAC entity has UL resources for a new transmission and for any of the activated serving cells of any MAC entity with a configured uplink, there are UL resources allocated for transmission or there is a PUCCH transmission on this cell and the (P-MPR) for this cell is not set to dormant BWP. c5) upon a switch of an activated BWP from a dormant BWP to a non-dormant DL BWP of an SCell of any MAC entity with a configured uplink; 6) upon a switch of an activated BWP from a dormant BWP to a non-dormant DL BWP of an SCell of any MAC entity with a configured uplink; 7) upon a switch of an activated BWP from a dormant BWP to a non-dormant DL BWP of an SCell of any MAC entity with a configured uplink; 8) upon a switch of an activated BWP from a dormant BWP to a non-dormant DL BWP of an SCell of any MAC entity with a configured uplink; A Power Headroom Report ("PHR") may be triggered if any of the following occurs: the measured P-MPR applied to meet the FR2 MPE requirements has changed by more than phr-Tx-PowerFactorChange dB for at least one activated FR2 serving cell since the last transmission of the PHR due to the measured P-MPR applied to meet the MPE requirements being equal to or greater than the phr-Threshold at this MAC entity, referred to as a "P-MPR Report"; MAC entities should avoid triggering a PHR when the required power backoff due to power management is only temporarily reduced (e.g., over up to tens of milliseconds) and should avoid triggering a PHR when a PHR is triggered by other triggering conditions. CMAX,f,c Note that one should avoid reflecting such temporary decreases in the value of / PH.

[0111] It should also be noted that if an HARQ process is configured with a cg-RetransmissionTimer, and if the PHR is already included in a MAC Protocol Data Unit ("PDU") for transmission by this HARQ process but has not yet been sent by lower layers, it is up to the UE implementation how to handle the PHR contents.

[0112] When the MAC entity has UL resources allocated for a new transmission, the MAC entity may do the following: 1> if such UL resource is the first UL resource allocated for a new transmission since the last MAC reset, 2> start the phr-PeriodicTimer; 1> If the power headroom reporting procedure determines that at least one PHR has been triggered and not cleared, and 1> If the allocated UL resources can accommodate the MAC CE for the PHR that the MAC entity is configured to transmit as a result of Logical Channel Prioritization ("LCP"), plus its subheader; 2>When multiplePHR with value true is constructed, 3> For each activated serving cell with a configured uplink associated with any MAC entity whose active DL BWP is not a dormant BWP, 4> Obtain a Type 1 power headroom or Type 3 power headroom value for the corresponding uplink carrier for the NR serving cell or the E-UTRA serving cell; 4> This MAC entity has UL resources allocated for transmission on this serving cell, or 4> If another MAC entity, if configured, has UL resources allocated for transmission on this serving cell and phr-ModeOtherCG is set to real by higher layers, 5> Corresponding P CMAX,f,cGets the value for the field from the physical layer, 5>If mpe-Reporting-FR2 is configured and this serving cell operates on FR2 and this serving cell is associated with this MAC entity, 6>Get the value for the corresponding MPE field from the physical layer, 3>If phr-Type2OtherCell with a value of true is configured, 4> If the other MAC entity is an E-UTRA MAC entity, 5> Get the value of Type 2 power headroom for the SpCell of another MAC entity (e.g., E-UTRA MAC entity); 5> If phr-ModeOtherCG is set to real by the upper layer, 6> The corresponding P for the SpCell of the other MAC entity (e.g., the E-UTRA MAC entity) CMAX,f,c Gets the value for the field from the physical layer, 3> instructing the multiplexing and assembly procedure to generate and transmit a multi-entry PHR MAC Control Element ("CE") based on values ​​reported by the physical layer; 2> In other cases (e.g., when a single-entry PHR format is used), 3> Retrieving a Type 1 power headroom value from the physical layer for the corresponding uplink carrier of the PCell; 3> Corresponding P CMAX,f,c Gets the value for the field from the physical layer, 3>If mpe-Reporting-FR2 is configured and this serving cell operates on FR2, 4> Get the value for the corresponding MPE field from the physical layer, 3> instructing the multiplexing and assembly procedure to generate and transmit a single-entry PHR MAC CE based on the values ​​reported by the physical layer; 2> If this PHR report is an MPE P-MPR report, 3> Start or restart the mpe-ProhibitTimer, 3> Clear the triggered MPE P-MPR report for the serving cell, contained in the PHR MAC CE; 2> Start or restart the phr-PeriodicTimer, 2> Start or restart the phr-ProhibitTimer, 2> Clear all triggered PHRs.

[0113] In some embodiments, there may be a single-entry PHR MAC CE. The single-entry PHR MAC CE is identified by a MAC subheader with a Logical Channel Identifier ("ID") ("LCID"). It has a fixed size and consists of two octets defined as follows (e.g., as shown in FIG. 8):

[0114] 8 is a block diagram illustrating one embodiment of a single-entry PHR MAC CE 800. The PHR MAC CE 800 receives P 802, R 804, power headroom ("PH") 806, MPE or R 808, and P 809 across bits 812. CMAX,f,c 810. R 804 is a reserved bit that is set to 0. The PH 806 field indicates the power headroom level. The length of the field is 6 bits. The reported PH 806 and corresponding power headroom levels are shown in Table 3 (e.g., corresponding measurements in dB).

[0115] If P802, i.e., mpe-Reporting-FR2, is configured and the serving cell operates on FR2, the MAC entity shall set this field to 0 if the applicable P-MPR value to satisfy the MPE requirement is less than P-MPR_00, otherwise it shall set this field to 1. If mpe-Reporting-FR2 is not configured or the serving cell operates on FR1, this field shall be set to (e.g., P-MPR cindicates whether power backoff is applied due to power management (as allowed by CMAX,f,c If the P810 field would have had a different value, the P802 field shall be set to 1. CMAX,f,c The PH810 field is used for the calculation of the preceding PH806 field. CMAX,f,c Shows 810. Reported P CMAX,f,c 810 and the corresponding nominal UE transmit power levels are shown in Table 4 (eg, corresponding measured values ​​in dBm).

[0116] If MPE808, i.e. mpe-Reporting-FR2, is configured and the serving cell operates on FR2, and if the P802 field is set to 1, this field indicates the applied power back-off to meet the MPE808 requirements. This field indicates an index into Table 5 and the corresponding measurement of the P-MPR level in dB. The length of the field is 2 bits. If mpe-Reporting-FR2 is not configured, or if the serving cell operates on FR1, or if the P802 field is set to 0, the R bit is present instead.

[0117] [Table 3]

[0118] In some embodiments, there may be a multi-entry PHR MAC CE. The multi-entry PHR MAC CE may be identified by a MAC subheader with an LCID. It has a variable size and contains a bitmap, a Type 2 PH field, and associated PHR fields for the SpCells of other MAC entities. CMAX,f,c The octet containing the field (e.g., if reported), the Type 1 PH field, and the associated P CMAX,f,cIt includes the octet containing the Type X PH field (if reported, for example), and the associated P cell for serving cells other than the PCell indicated in the bitmap. CMAX,f,c It further includes one or more of the octets containing the fields (e.g., if reported), in ascending order based on ServCellIndex, where X is either 1 or 3. The presence of a Type 2 PH field for an SpCell of another MAC entity is configured by phr-Type2OtherCell with a value of true.

[0119] When the maximum ServCellIndex of serving cells with configured uplinks is less than 8, a single octet bitmap is used to indicate the presence of a PH per serving cell, otherwise 4 octets are used.

[0120] The MAC entity determines whether the PH value for the activated serving cell is based on the actual transmission or on the reference format by taking into account the configured grant, the downlink control information being received up to and including the PDCCH occasion, and the first UL grant for a new transmission that can accommodate the MAC CE for the PHR as a result of the LCP is received since the PHR is triggered if the PHR MAC CE is reported for an uplink grant received on the PDCCH, or from the first uplink symbol of the PUSCH transmission minus the PUSCH preparation time if the PHR MAC CE is reported for a configured grant.

[0121] For band combinations in which the UE does not support dynamic power sharing, the UE may set the power headroom fields and P CMAX,f,c The octet containing the power headroom field may be omitted, and the reported value of the power headroom and the P CMAX,f,cdepends on the UE implementation.

[0122] 9 is a block diagram illustrating an embodiment of a multiple entry PHR MAC CE 900 where the maximum ServCellIndex of serving cells with configured uplinks is less than 8. The PHR MAC CE 900 performs the following operations across bit 958: C7902, C6904, C5906, C4908, C3910, C2912, C1914, R916, P918, V920, PH922, MPE or R924, P CMAX,f,c 1 926, P928, V930, PH932, MPE or R934, P CMAX,f,c 2 936, P938, V940, PH942, MPE or R944, P CMAX,f,c 3 946, P948, V950, PH952, MPE or R954, and P CMAX,f,c Includes M956.

[0123] C i For ServCellIndex i, this field indicates the presence of a PH field for the serving cell with ServCellIndex i. i The PH field indicates that the PH field for the serving cell with ServCellIndex i is reported. iThe PH field indicates that the PH field for the serving cell with ServCellIndex i is not reported. For each R, there is a reserved bit set to 0. For each V, this field indicates whether the PH value is based on the real transmission or the reference format. For a type 1 PH, a V field set to 0 indicates a real transmission on the PUSCH and a V field set to 1 indicates that the PUSCH reference format is used. For a type 2 PH, a V field set to 0 indicates a real transmission on the PUCCH and a V field set to 1 indicates that the PUCCH reference format is used. For a type 3 PH, a V field set to 0 indicates a real transmission on the SRS and a V field set to 1 indicates that the SRS reference format is used. Additionally, for type 1, type 2, and type 3 PH, a V field set to 0 indicates that the associated PRS reference format is used. CMAX,f,c A V field set to 1 indicates the presence of an octet containing the associated P CMAX,f,c This indicates that the octet containing the MPE field and the octet containing the MPE field are omitted.

[0124] For each PH, this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom level (e.g., the corresponding measurement in dB for the NR serving cell is specified, and the corresponding measurement in dB for the E-UTRA serving cell is specified).

[0125] For each P, if mpe-Reporting-FR2 is configured and the serving cell operates on FR2, the MAC entity shall set this field to 0 if the applicable P-MPR value to satisfy the MPE requirement is less than P-MPR_00, otherwise to 1. If mpe-Reporting-FR2 is not configured or the serving cell operates on FR1, this field shall be set to the value (e.g., P-MPR cIf power backoff due to power management was not applied, the MAC entity shall CMAX,f,c The P field shall be set to 1 if the field would have had a different value.

[0126] Each P CMAX,f,c For , if present, this field represents the P for the NR serving cell used for the calculation of the preceding PH field. CMAX,f,c , and P for the E-UTRA serving cell CMAX,c or

[0127]

number

[0128] Shows.

[0129] For each MPE, if mpe-Reporting-FR2 is configured and the serving cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet the MPE requirements. This field indicates the index and the corresponding measurement of the P-MPR level in dB. The length of the field is 2 bits. If mpe-Reporting-FR2 is not configured, or the serving cell operates on FR1, or the P field is set to 0, the R bit is present instead.

[0130] 10 is a block diagram illustrating another embodiment of a multiple-entry PHR MAC CE 1000 in which the maximum ServCellIndex of serving cells with configured uplinks is equal to or greater than 8. The PHR MAC CE 1000 includes C71002, C61004, C51006, C41008, C31010, C21012, C11014, R1016, C 15 1018, C 14 1020, C13 1022, C 12 1024, C 11 1026, C 10 1028, C91030, C81032, C 23 1034, C 22 1036, C 21 1038, C 20 1040, C 19 1042, C 18 1044, C 17 1046, C 16 1048, C 31 1050, C 30 1052, C 29 1054, C 28 1056, C 27 1058, C 26 1060, C 25 1062, C 24 1064, P1066, V1068, PH1070, MPE or R1072, P CMAX,f,c 1 1074, P1076, V1078, PH1080, MPE or R1082, P CMAX,f,c 2 1084, P1086, V1088, PH1090, MPE or R1092, P CMAX,f,c 3 1093, P1094, V1095, PH1096, MPE or R1097, and P CMAX,f,c Includes M1098.

[0131] In various embodiments, there may be a PHR-Config. Figure 11 is a code diagram illustrating one embodiment of a PHR-Config information element ("IE") 1100. The PHR-Config IE 1100 is used to configure parameters for power headroom reporting based on Table 6.

[0132] [Table 6]

[0133] FIG. 12 is a block diagram illustrating one embodiment of a system 1200 including a target IAB node (N) 1202 transmitting 1203 to a parent node or IAB donor (PN) 1204 upstream of the IAB node via an upstream link 1206, and a child node or UE 1208 on a downstream link 1210 of the IAB node.

[0134] In FIG. 12, an IAB node 1202 transmits signals to a parent IAB node and / or donor 1204 and a child IAB node or UE 1208 .

[0135] In some embodiments, 1) the IAB node 1202 may be connected to multiple parent nodes and / or child nodes / UEs, 2) the IAB node 1202 may comprise multiple IAB-MTs and / or multiple IAB-DUs, 3) the parent node 1204, the IAB node 1202, and the child node 1208 may be referred to as the PN, N, and CN, respectively, and 4) the IAB-DU or the PN, the IAB-MT of the N, the IAB-DU of the N, and the IAB-MT of the CN may be referred to as the PN-DU, N-MT, N-DU, and CN-MT, respectively.

[0136] In various embodiments, there may be methods and systems for enhanced power headroom reporting. In some embodiments, the PHR transmission from the IAB node N to the parent node PN is triggered by an event related to the downstream of the IAB node (e.g., related to a cell served by the N-DU or a link between the N-DU and the CN-MT). If the event is related to the N-DU without reference to a particular child node or UE served by the N-DU, the method may be referred to as "per-cell" or "cell-based". However, if the event is related to a link between the N-DU and a particular child node CN-MT or UE, the method may be referred to as "per-link" or "link-based". As found herein, the description of some embodiments may be expressly expressed in terms of per-cell or per-link. However, this is not intended to limit the scope, and in some implementations, the per-link method may be implemented on a per-cell basis, or vice versa, even if not explicitly stated in the present embodiment.

[0137] In some embodiments, the power control parameters for calculating the power headroom value or the power headroom offset value, etc., may be determined based on parameters or events related to the downstream cell or downstream link of the IAB node N. For example, the P c,max The value of may change due to changes in the downstream link (between the N-DU and the CN-MT) or the downstream cell (served by the N-DU). This change may then trigger a PHR transmission or another transmission to the parent node (PN-DU) or alternatively to the IAB-CU.

[0138] In various embodiments, an event or parameter related to a downstream link or downstream cell of an IAB node may be subject to signaling or other action by a parent node of the IAB node, in some embodiments, a first parent node that performs the signaling or other action may be different from a second parent node of the IAB node with which the power headroom or other power control parameter is associated.

[0139] In some embodiments, there may be a PHR triggering event. In some embodiments, PHR signaling from the N-MT to the PN-DU is triggered based on an event related to the N-DU.

[0140] In various embodiments, the N-MT may send the PHR to the PN-DU when the N-DU receives a DL power adjustment message from the CN-MT. In such embodiments, the PHR may include a value of PH that is determined based on the value of the power adjustment in the power adjustment message.

[0141] In some embodiments, when the N-DU receives a DL power adjustment message from the CN-MT, the N may determine whether the N-DU applies a power adjustment in response to the message. If yes, the N-MT may send a PHR to the PN-DU, where the PHR comprises a PH value determined based on the power adjustment determined based on the DL power adjustment message.

[0142] In one example, the N-MT may send a PHR to the PN-DU when the N-DU adjusts and / or updates the N-DU transmit power by an amount greater than a predetermined or configured power adjustment value, or when the power headroom of the N-MT (e.g., PH based on the N-MT reference PUSCH transmission) changes by an amount greater than a predetermined or configured power adjustment value due to the N-DU transmit power adjustment, or when the maximum output power of the N-MT (e.g., configured maximum output power, or a component of configured maximum output power, such as MPR (e.g., IAB-MPR) due to simultaneous transmissions in the N-MT and N-DU) changes by an amount greater than a predetermined or configured power adjustment value due to the N-DU transmit power adjustment. In another example, the PHR may include a value of PH determined based on the value of the N-DU transmit power or the value of the power adjustment to the N-DU transmit power.

[0143] In one embodiment, 1) the CN-MT sends a DL power control message to the N-DU, where the DL power control message includes a requested value for power change ΔP1, 2) the N-DU sends a response message to the CN-MT, where the response message includes an authorized and / or accepted value for power change ΔP2 (which may or may not be equal to the requested value for power change ΔP1), and / or 3) the N-MT sends a PHR to the PN-DU, where the value of PH in the PHR may be calculated or updated based on the requested value for power change ΔP1 and / or the authorized / accepted value for power change ΔP2. Alternatively, in a similar manner, N may send a DL power control message to the CN-MT, where the DL power control message includes a requested value for power change ΔP1, and / or DL A new value of may then be calculated based on ΔP1 and / or ΔP2, and N-MT is then calculated based on P DL , and sends a PHR based on the new value of

[0144] In another embodiment, when the N-DU receives a DL power adjustment message from the CN-MT, the N may determine whether the N-DU applies a power adjustment in response to the message. If yes, the N-MT may send a control message to the PN-DU, where the control message includes a UL transmit power parameter determined based on the power adjustment determined based on the DL power adjustment message.

[0145] In some embodiments, the UL transmit power parameter is set to P based on the power change for downlink transmission by the N-DU. c,max In another embodiment, the UL transmit power parameter is used to determine the value of P c,max or another power control parameter in the simultaneous operation mode.

[0146] In various embodiments, 1) the CN-MT sends a DL power control message to the N-DU, where the DL power control message includes a requested value for power change ΔP1, 2) the N-DU sends a response message to the CN-MT, where the response message includes an authorized and / or accepted value for power change ΔP2 (which may or may not be equal to the requested value for power change ΔP1), and / or 3) the N-MT sends a control message to the PN-DU, where the control message includes a UL transmit power parameter that is calculated or updated based on the requested value for power change ΔP1 and / or the authorized and / or accepted value for power change ΔP2. Alternatively, in a similar manner, N may send a downlink power P DL A new value of may then be calculated based on ΔP1 and / or ΔP2, and N-MT is then calculated based on P DL transmit a control message including a value of the UL transmit power parameter based on the new value of

[0147] In some embodiments, the control message may be an L1 control message, such as an uplink control information ("UCI") message transmitted on a PUCCH or a PUSCH.

[0148] In some embodiments, when an N-MT receives an availability indication ("AI") message for an N-DU soft resource, the N-MT may transmit a PHR for a PUSCH or SRS that overlaps with the N-DU soft resource.

[0149] In various embodiments, rather than transmitting a PHR including a value of PH, the N-MT may transmit a control message that complements or augments the power headroom reporting process. By following such an embodiment, overly frequent transmission of PHRs may be avoided. Complementing signaling may be referred to herein as Complementary Power Headroom Reporting ("C-PHR"). The C-PHR message may be an L1 control message, such as a UCI message or a MAC message. The C-PHR message may include a value of PH, e.g., a value of ΔPH, which may be the difference between a value reported in a recent PHR to a parent node and a PH value calculated based on a condition or associated with a condition or resource. In general, the value of ΔPH may be positive, zero, or negative. Upon receiving a C-PHR including a value of ΔPH, the parent node may apply the value of PH+ΔPH (or the value of PH-ΔPH) to the IAB node transmitting the C-PHR and associated with the condition or resource. ΔPH may be referred to as a PH offset. In some embodiments, reporting a positive value of ΔPH, a negative value of ΔPH, or a zero value of ΔPH to a parent node may be omitted.

[0150] It should be noted that combinations of the various embodiments described herein may be made. In some embodiments, a triggering event that is considered less frequent may trigger a PHR transmission, and a triggering event that is considered more frequent may trigger a C-PHR transmission. For example, a DL power adjustment by the N-DU, which may follow a power adjustment message from the CN-MT, may trigger a PHR transmission, and an AI message for resources may trigger a C-PHR transmission.

[0151] In various embodiments, the value of PH or ΔPH may be associated with a condition or resource, or may be triggered based on a triggering event associated with the condition or resource.

[0152] In some embodiments, the value of PH or ΔPH may be associated with an N-DU resource or condition, or may be triggered by an event associated with an N-DU resource or condition, which resource, condition, or triggering event may be referred to as a "cell-by-cell."

[0153] In another embodiment, the value of PH or ΔPH may be associated with a CN-MT resource or condition, or may be triggered by an event associated with a CN-MT resource or condition, which resource, condition, or triggering event may be referred to as a "link unit."

[0154] In yet another embodiment, the value of PH or ΔPH may be associated with N-DU and CN-MT resources or conditions, or may be triggered by an event associated with N-DU and CN-MT resources or conditions, which resources, conditions, or triggering events may be referred to as "cell-link units."

[0155] In some embodiments, a resource may be addressed by an ID, such as a configuration ID, contained in an associated resource configuration IE.

[0156] In various embodiments, the value of PH or ΔPH may be associated with a multiplexing mode, such as case A, case B, case C, or case D multiplexing, at the IAB node transmitting the PHR or C-PHR.

[0157] According to embodiments of the present disclosure, a parent node may maintain multiple values ​​of PH and / or ΔPH associated with an IAB node, a DU cell of the IAB node, a child node served by the DU cell of the IAB node, etc. As a result, a PHR or C-PHR may include multiple values ​​of PH and / or ΔPH.

[0158] In some embodiments, when a PHR or C-PHR transmission is triggered, the PHR or C-PHR may include multiple values ​​of PH and / or ΔPH, each of which may or may not have changed compared to the last associated PHR or C-PHR transmission.

[0159] In some embodiments, when a PHR or C-PHR transmission is triggered, the PHR or C-PHR may include one or more values ​​of PH and / or ΔPH associated with the change in the PH value relative to the corresponding value since the last associated PHR or C-PHR transmission.

[0160] In another embodiment, when a PHR or C-PHR transmission is triggered, the PHR or C-PHR may include one or more values ​​of PH and / or ΔPH associated with a change in PH value above or below some threshold value relative to the corresponding value in the last associated PHR or C-PHR transmission.

[0161] The embodiments herein may be enabled by configuration from a higher layer, such as a Radio Resource Control ("RRC") entity terminated in the IAB-CU. In some embodiments, one or more RRC IEs may configure behavior at the IAB node based on any of the embodiments found herein. The IEs may be sent to the IAB node over a higher layer interface, such as an F1 interface.

[0162] In various embodiments, communication of RRC IEs from the IAB-CU to the IAB node may follow IAB capability signaling. For example, the IAB-CU may configure the IAB node to perform methods found herein if the IAB node reports to the IAB-CU, e.g., via an RRC message after establishing an RRC connection, that 1) the IAB node is capable of performing enhanced power control, enhanced UL power control, enhanced DL power control, enhanced duplexing, Case A multiplexing, etc., or 2) the IAB node has a single antenna panel, multiple antenna panels, constraints on transmit or receive power imbalance, etc.

[0163] In some embodiments, the signaling may be referred to as configuring an IAB node. Thus, in some embodiments, an IAB node may be configured to perform the methods found herein. In various embodiments, 1) an IAB node may perform the methods without configuration, and instead follow standard specifications for all or part of the proposed signaling and behavior, or 2) the signaling or behavior may be determined in whole or in part by lower layer signaling, such as L1 / L2 signaling, without configuration from higher layers.

[0164] FIG. 13 is a code diagram illustrating one embodiment of an RRC configuration IE 1300.

[0165] According to the example Abstract Syntax Notation ("ASN") One ("ASN.1") code of Figure 13, the extended PHR, C-PHR, etc. may be configured by an IE such as PHR-Config that includes additional parameters that may determine whether extended PHR signaling should be performed.

[0166] In some embodiments, a new IE such as IAB-TriggerBasedOnDU, which may be sent separately or included in the PHR-Config IE, may communicate additional information on how to perform enhanced signaling related to the PHR, C-PHR, etc. This configuration IE may indicate additional details on the format of the control message for the C-PHR, thresholds for PHR offsets due to downstream events or parameters, thresholds on Pc,max changes, etc.

[0167] If a threshold value for the PHR offset is indicated, the IAB node may be required to transmit the associated PHR or C-PHR only if the offset is not less than the threshold. If a threshold value for the Pc,max value (or a value for another power control parameter, as described below) is indicated, the IAB node may be required to report a change in the Pc,max value (or a value for another power control parameter) only if the change is not less than the threshold. Other threshold values ​​may be configured to determine the behavior at the IAB node.

[0168] In some embodiments, the PHR offset may be reported to a parent node or IAB-CU (e.g., in a C-PHR) only if the PHR offset is below a threshold. Then, the IAB node sends the PHR if the PHR offset is above a threshold. The threshold may be indicated by configuration.

[0169] In various embodiments, a PHR offset may be reported to a parent node or IAB-CU (e.g., in a C-PHR) only if the PHR offset is associated with some resources or a duration less than a threshold. The IAB node then transmits a PHR if the PHR offset is associated with some resources or a duration greater than a threshold. The threshold may be indicated by configuration.

[0170] In some embodiments, a change in value for a power control parameter, such as Pc,max, may be reported to the IAB node or IAB-CU only if the change in value is below a threshold, where the IAB node sends a PHR if the change in value is above the threshold, which may be indicated by configuration.

[0171] In some embodiments, a downstream event or a parameter related to a downstream parameter may trigger a PHR transmission, a C-PHR transmission, calculation of a new value for a power control parameter, etc. In any of the embodiments herein, there may be an additional condition for the associated resources in the upstream and the associated resources in the downstream to be time overlapping ("TOL") (e.g., overlapping in the time domain due to configuration, occurrence, OFDM numerology mismatch between upstream and downstream, timing mismatch between upstream and downstream, etc.).

[0172] For example, the PH and associated PHR values ​​may be associated with an UL signal or channel, such as a PUSCH or an SRS. The UL signal or channel may occur on a first (e.g., upstream) resource (or resource set) configured for an N-MT. On the other hand, resource attributes, such as D / U / F attributes, H / S / NA attributes, availability indications for soft resources, etc., may be indicated for a second (e.g., downstream) resource (or resource set) configured for an N-DU. Then, the condition for performing the method found herein may be for the first resource (or resource set) and the second resource (or resource set) to overlap in time. However, in some specifications, the TOL resource may be referred to as the same resource, or alternatively, may be implicitly referred to.

[0173] In some embodiments, the condition for performing the methods herein may be based on the co-location of the N-MT and the N-DU. This co-location may be signaled to another entity, such as a parent node or an IAB-CU, or may be realized by the implementation. If the co-location is signaled, the information in the signaling may be used for power control configuration for the methods described herein.

[0174] In some embodiments, such as for enhanced power control based on resource attributes in an IAB node, resources may be referenced for brevity without explicitly referring to TOL relationships or co-location conditions between the resources. However, it should be noted that time overlap between the resource of interest and another resource recognized by the IAB nodes MT and DU, and / or co-location between MT and DU may be additional conditions for the method to be performed by the IAB node.

[0175] In various embodiments, the power headroom value is calculated and reported based on downstream resources.

[0176] In one embodiment, the attribute of a downstream resource is a D / U / F attribute (e.g., whether the resource is downlink, uplink, or flexible). If the resource is downlink, the power associated with transmission on the resource (to a child node or UE) may be used to calculate a power headroom value. If the resource is uplink, the power associated with reception on the resource (from a child node or UE) may be used to calculate a power imbalance value, which may then be used to calculate a power headroom value. If the resource is flexible, 1) the resource may be assumed to be downlink as a worst case, 2) the resource may be assumed to be uplink, and / or 3) the resource may not be considered as downlink if it does not meet the power constraint as signaled to the parent node by the last PHR report.

[0177] In another embodiment, the attribute of the downstream resource is an H / S / NA attribute (e.g., whether the resource is a hard resource, a soft resource, or an unavailable resource). If the resource is hard, the power associated with the resource is taken into account to calculate the power headroom value. If the resource is unavailable, the power associated with the resource is not taken into account to calculate the power headroom value. If the resource is soft, 1) the power associated with the resource is not taken into account to calculate the power headroom value, 2) the power associated with the resource is taken into account to calculate the power headroom value, 3) the power associated with the resource is taken into account to calculate the power headroom value if the resource is indicated as available, and / or 4) the power associated with the resource is taken into account to calculate the power headroom value if the resource is indicated as available before a time threshold, where the time threshold may be obtained based on the time of the resource and the time of receipt of an associated availability indication message indicating whether the resource is available.

[0178] In some embodiments, the N-MT receives information of a reference set of N-DU DL transmission parameters to be used for the N-MT's virtual PH calculation (e.g., PH based on N-MT reference PUSCH transmission and N-DU DL reference transmission parameters). In addition, the N-MT may receive information of a maximum transmit power difference between the N-MT transmit power value and the N-DU transmit power value (e.g., in the case of simultaneous transmission on the N-MT and N-DU). In the case of virtual PHR, the N-MT determines the virtual power headroom based on the reference set of N-DU DL transmission parameters, the reference set of N-MT UL transmission parameters, and the maximum transmit power difference. In one example, the configured maximum output power of the N-MT is determined based on the maximum transmit power difference between the N-MT transmit power and the N-DU transmit power.

[0179] In some embodiments, the power headroom value is calculated and reported based on upstream resources.

[0180] In one embodiment, the attribute of an upstream resource is a D / U / F attribute (e.g., whether the resource is downlink, uplink, or flexible). If the resource is downlink, the power associated with receiving on the resource (from the parent node) may not be used to calculate the power imbalance value. If the resource is uplink, the power associated with transmitting on the resource (to the parent node) may be used to calculate the power headroom value, which may then be used to calculate the power headroom value. If the resource is flexible, 1) the resource may be assumed to be downlink, 2) the resource may be assumed to be uplink as a worst case, and / or 3) the resource may not be considered as uplink if it does not meet the power constraint as signaled to the parent node by the last PHR report.

[0181] In another embodiment, the attribute of the upstream resource is an H / S / NA attribute (e.g., whether the resource is a hard resource, a soft resource, or an unavailable resource). If the resource is hard, the power associated with the resource is taken into account to calculate the power headroom value. If the resource is unavailable, the power associated with the resource is not taken into account to calculate the power headroom value. If the resource is soft, 1) the power associated with the resource is not taken into account to calculate the power headroom value, 2) the power associated with the resource is taken into account to calculate the power headroom value, 3) the power associated with the resource is taken into account to calculate the power headroom value if the resource is indicated as available, and / or 4) the power associated with the resource is taken into account to calculate the power headroom value if the resource is indicated as available before a time threshold, where the time threshold may be obtained based on the time of the resource and the time of receipt of an associated availability indication message indicating whether the resource is available.

[0182] In some embodiments, whether to send a PHR may further depend on spatial / beam constraints and / or timing alignment constraints of the IAB-MT TOL resources.

[0183] The extended PHR or C-PHR, according to embodiments herein, may include an indication of a dynamic range value, such as a preferred dynamic range (e.g., the maximum transmit power difference between the N-MT transmit power and the N-DU transmit power in case of simultaneous transmission on N-MT and N-DU). In various embodiments, the dynamic range value may be reported in a separate message, such as a control message, associated with the PHR or C-PHR. The association rules (for multiple values ​​of the dynamic range) and message formats may be similar to those proposed for the extended PHR or C-PHR, according to embodiments herein.

[0184] In various embodiments, the triggering event or the calculation of PH or ΔPH may be based on an indication of MT-DU colocation, such as colocation between the N-DU and the N-MT. Additionally or alternatively, the N-DU and N-MT may share antennas and / or RF hardware to trigger PHR or C-PHR transmission, the calculation of a new value of PH or ΔPH, or the calculation of related parameters, such as power control parameters. The MT-DU colocation indication may be in the form of, for example, a capability parameter, in a configuration from the network / CU or in a message from the IAB nodes comprising the IAB-MT and IAB-DU.

[0185] The extended PHR or C-PHR, according to embodiments found herein, may additionally or alternatively include an indication of an adjacent channel leakage ratio ("ACLR") value. Alternatively, the ACLR value may be reported in a separate message, such as a control message associated with the PHR or C-PHR. The association rules (for multiple values ​​of dynamic range) and message formats may be similar to those proposed for the extended PHR or C-PHR according to embodiments herein.

[0186] In some embodiments, the extended PHR or C-PHR may include an indication of the value of the MPR (e.g., IAB-MPR or IAB-P-MPR) resulting from simultaneous transmission on N-MT and N-DU. Alternatively, the value of the MPR may be reported in a separate message, such as a control message associated with the PHR or C-PHR. The association rules and message formats (e.g., for multiple values ​​of the dynamic range) may be similar to those proposed for the extended PHR or C-PHR according to embodiments described herein.

[0187] In some embodiments, in order for the parent node PN-DU to apply different power control parameters, such as different values ​​of PH, ΔPH, dynamic range, MPR, and ACLR, the parent node may be informed of relevant information for dynamic switching, such as resource configuration, by the IAB-CU. In some implementations, the configuration associated with the N-DU and / or CN-MT may be shared with the PN via the F1 interface. The parent node PN may then dynamically apply different power control parameters based on the information of the configuration associated with the N-DU and / or CN-MT.

[0188] In various embodiments, the IAB-CU may indicate power constraints to the parent node associated with resources for the N-DU, the CN-MT, transmissions from the N-DU to the CN-MT, transmissions from the N-DU to the CN-MT, etc.

[0189] In some embodiments, the N-MT transmits a legacy PHR associated with a time division multiplexing ("TDM") mode. However, a switch to a concurrent operation mode, such as Case A multiplexing, may trigger a PHR transmission.

[0190] In some embodiments, the N-MT transmits a legacy PHR associated with the TDM mode. However, a switch to a concurrent operation mode such as Case A multiplexing may trigger a C-PHR transmission, and the C-PHR may include a value of ΔPH (e.g., a PH offset).

[0191] In various embodiments, the N-MT transmits legacy PHRs associated with TDM modes as well as extended PHRs and / or C-PHRs associated with concurrent operation modes such as Case A multiplexing. A parent node PN-DU receiving the PHRs and / or C-PHRs may then apply PH and / or PH offset value information when the associated multiplexing mode is applied at the IAB node N. The application of the multiplexing mode may further depend on D / U / F and / or H / S / NA attributes associated with resources configured for the N-DU (e.g., cell-based) and / or CN-MT (e.g., link-based) information, which may be obtained by the parent node from the IAB-CU.

[0192] In some embodiments, if the downstream resources of the IAB node N (e.g., resources used for communication between the N-DU and the CN-MT) are soft resources, the application of power control parameters such as the PH of the PH offset may further depend on the availability of soft resources, which may be indicated by an AI message from the same parent node or a different parent node.

[0193] 14 shows an example IAB system with DC in an IAB node, where the parent node of the IAB node is configured by one IAB donor. This architecture is sometimes called an intra-donor scenario.

[0194] 14 is a schematic block diagram illustrating an embodiment of a DC architecture 1400 having one IAB-CU and / or IAB donor (intra-donor scenario). The DC architecture 1400 includes a CN 1402, an IAB donor 1404, a first parent node 1406, a second parent node 1408, and an IAB node 1410.

[0195] Figure 15 illustrates dual connectivity at an IAB node, where each parent node may be configured by a different IAB donor. This architecture is sometimes referred to as the donor-to-donor scenario.

[0196] 15 is a schematic block diagram illustrating an embodiment of a DC architecture 1500 having multiple IAB-CUs and / or IAB donors (intra-donor scenario). The DC architecture 1500 includes a CN 1502, a first IAB donor 1504, a second IAB donor 1506, a first parent node 1508, a second parent node 1510, and an IAB node 1512.

[0197] In some embodiments, there may be 1) a physical layer ("L1") connection over a Uu link connecting the IAB-MT of an IAB node to the serving IAB-DU of a parent node, 2) a media access control ("MAC") sublayer of the link layer ("L2"), 3) RRC at Layer 3, 4) higher layer interfaces, and 5) others.

[0198] It should be noted that an IAB node in an IAB system may be configured with an IAB-CU of an IAB donor, which may be connected to the IAB node via multiple hops (e.g., wireless links) via an F1 interface.

[0199] As used herein, physical layer signaling and link layer signaling (e.g., including MAC signaling) may be referred to as “lower layer” signaling, dynamic signaling, L1 / L2 signaling, etc. For example, unless an embodiment or implementation specifies the term “lower layer” to refer to specific signaling, such as a DCI message or a MAC message, lower layer signaling may refer to a DCI message on the PDCCH, a UCI message on the PUCCH or PUSCH, a MAC message, or a combination thereof.

[0200] Moreover, as used herein, signaling by RRC and / or over interfaces such as F1 and Xn may be referred to as "higher layer" signaling, higher layer configuration, or configuration. For example, higher layer signaling or configuration may refer to RRC IEs, F1AP IEs, XnAP IEs, etc.

[0201] In some embodiments, a DCI message indicating attributes for downstream resources of the IAB-MT may trigger a PHR or C-PHR transmission, and the DCI message may be transmitted by a first parent node, and the PHR is sent to a second parent node. Alternatively, upon receiving the DCI message, the IAB node may calculate new values ​​for the power control parameters, and then transmit a PHR or C-PHR with information of the newly calculated power control parameters if the power control parameters change by any value, or alternatively by a value above a threshold.

[0202] In various embodiments, the DCI message may be an AI message that includes values ​​of AI for downstream resources in the time and / or frequency domain. The downstream resources may refer to resources configured for operation (e.g., transmission and / or reception) by the N-DU, the CN-MT, or both.

[0203] For example, consider an IAB node N that is served by two parent nodes PN1 and PN2. In one implementation, the master node PN1 may send an AI message to N, with an availability value for a downstream resource. This may trigger a PHR or C-PHR transmission to the secondary node PN2 associated with that resource, or an action on that resource.

[0204] In another implementation, the secondary node PN2 may send an AI message to N, which includes an availability value for a downstream resource, which may trigger a PHR or C-PHR transmission to the master node PN1 associated with that resource, or an action on that resource.

[0205] FIG. 16 is a schematic block diagram illustrating an embodiment of a system 1600 illustrating an alternative scenario for concurrent operation. The system 1600 includes parent node 1 1602, parent node 2 1604, IAB node 1605, child node 1606, and UE 1608 using upstream backhaul links 1610 and 1612 and downstream backhaul links 1614 and 1616. In FIG. 16, each of the backhaul links and access links in the upstream and downstream of the IAB nodes may have resources that do not overlap (e.g., not filled in) with resources used in other links. However, some resources (e.g., shaded) on one link may overlap with resources on one or more other links in the time domain, frequency domain, and / or spatial domain. In particular, when resources overlap in the time domain, methods for concurrent operation may be applied.

[0206] In various embodiments, references are made to the references since methods similar to those proposed therein are applicable for multiplexing between upstream links (eg, DC scenarios).

[0207] In various embodiments, time overlapping ("TOL") resources such as TOL symbols are referred to, although standard specifications may use different terms for overlapping resources or may simply refer to the "same" resources. Moreover, TOL resources may be defined or configured for different entities, such as different IAB nodes, IAB-MTs, and IAB-DUs of IAB nodes. In some embodiments, there may be cases with different numerologies where a symbol in a first operation and / or configuration may not have the same length in time as a symbol in a second operation and / or configuration. In some embodiments, there may be cases with timing misalignment, whether intentional or due to error due to employing different timing alignments.

[0208] In some embodiments, the TOL as a relationship between two resources is commutative (e.g., if a first resource and / or symbol A overlaps in time with a second resource and / or symbol B, then B is also TOL with A). In some embodiments, there may be a symbol in a first operation and / or configuration and a TOL symbol in a second operation and / or configuration.

[0209] In some embodiments, a type of resource may be used to allow IAB nodes to perform simultaneous operations based on either a best effort manner or otherwise. This type of resource may be referred to as DL+UL, which may or may not be interpreted as a flexible (F) symbol.

[0210] In various embodiments, the DL+UL symbol may be realized by using new values ​​in addition to DL, UL, and F. This may require changing the structure of some messages.

[0211] In some embodiments, DL+UL symbols may be realized by separate signaling. An example of separate signaling is the TDD-UL-DL-ConfigDedicated2-r17 IE as described in some embodiments herein. If such a new IE is used, it may be treated similarly to "TDD-Config" in the table of scenarios for DL-UL contention resolution. Similar principles may be used, for example, to introduce a control message with a structure similar to that of the SFI.

[0212] In some embodiments, the configurations and signaling described herein may include parameters indicating a beam to be applied for transmission or reception, a transmit power to be applied for transmission, a timing alignment method to be applied for transmission or reception, etc. Moreover, a beam may refer to a spatial filter for transmission or reception by a node on an antenna panel or antenna port.

[0213] In some embodiments, a beam may be referred to by terms such as spatial filters or spatial parameters. Transmission and / or reception of a signal using a beam may refer to application of a spatial filter (or spatial parameters) similar to that of another transmission and / or reception of another signal. "Determining" a beam may follow a beamforming training process that includes transmission and / or reception of a reference signal by applying different beams and performing measurements on the signal. "Indicating" a beam may refer to sending a message to another node, the message including beam / spatial filter information in the form of a transmit configuration instruction ("TCI"), including spatial quasi-collocation ("QCL") or QCL type D, spatial relationship parameters, etc.

[0214] In various embodiments, the transmit power may be determined or indicated by signaling, which may be semi-static, such as by RRC configuration and / or control messages such as MAC CE messages or DCI / L1 messages. The transmit power control may apply to uplink transmissions, downlink transmissions, or both, which may be determined by standards, configuration, and / or control signaling.

[0215] In some embodiments, the timing alignment method may be determined or indicated by signaling. The signaling may be semi-static, such as by RRC configuration and / or control messages such as MAC CE messages or DCI / L1 messages. In some embodiments, the timing alignment method may be determined by the duplexing / multiplexing case. For example, case A (e.g., simultaneous transmission) at a node may automatically trigger a timing alignment mode based on "case 6" timing alignment where transmissions are aligned, while case B (e.g., simultaneous reception) at a node may automatically trigger a timing alignment mode based on "case 7" timing alignment where receptions are aligned. Whether and how a timing alignment method is triggered or applied may be determined by standards, configuration, and / or control signaling.

[0216] In some embodiments, the configuration may be an RRC configuration that the IAB node (or UE) may receive from the IAB-CU. The configuration may include resources allocated for reference signals, signaling to trigger transmission of the reference signals, parameters for the reference signals, such as beam / spatial relationships and transmit powers.

[0217] In some embodiments, the reference signal for interference assessment may be any reference signal based on which interference may be measured. For example, a channel state information reference signal ("CSI-RS") may be used for the downlink (e.g., when interference by IAB-DU is to be measured), while a sounding reference signal ("SRS") may be used for the uplink (e.g., when interference by IAB-MT or UE is to be measured). Other types of reference signals are not excluded. When a reference signal is transmitted, it may be received by other nodes (e.g., IAB nodes or UEs) to measure reference signal received power ("RSRP"), reference signal received quality ("RSRQ"), etc. An alternative to the reference signal may be any other transmission based on which interference or received signal power may be calculated, such as a received signal strength indicator ("RSSI").

[0218] Various types of reference signals may be specified for New Radio ("NR"), which may be used as a starting point for implementing the embodiments herein. In NR, reference signals may be periodic, semi-persistent, or aperiodic. Periodic reference signals are transmitted as long as the RRC configuration for the reference signal is valid. Semi-persistent reference signals are configured by RRC IEs, but their transmission is controlled by MAC CE signaling. Aperiodic reference signals are configured by RRC IEs, but their transmission is triggered by physical layer and / or Layer 1 ("L1") signaling (e.g., DCI messages). In all those cases, the RRC configuration includes a parameter indicating which resources are allocated to the reference signal, but additional MAC CE or DCI signaling may further activate / deactivate or trigger the transmission of the reference signal.

[0219] In various embodiments, a parent node or another local node may signal to perform one of the methods found herein based on information such as IAB node capabilities, number of panels, type of concurrent operation (which may itself be determined by resource configuration and resource multiplexing, e.g.,), IAB node mobility, history of success or failure related to duplexing / multiplexing type, etc.

[0220] In some embodiments, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel may be hardware used to transmit and / or receive wireless signals at frequencies below 6 GHz (e.g., Frequency Range 1 ("FR1")), above 6 GHz (e.g., Frequency Range 2 ("FR2")), or millimeter wave ("mmWave"). In some embodiments, an antenna panel may include an array of antenna elements, each connected to hardware, such as a phase shifter, that allows a control module to apply spatial parameters for the transmission and / or reception of signals. The resulting radiation pattern may be referred to as a beam, which may or may not be single mode, and may allow a device (e.g., UE, node) to amplify signals transmitted or received from one or more spatial directions.

[0221] In various embodiments, the antenna panels may or may not be virtualized as antenna ports. The antenna panels may be connected to a baseband processing module through a radio frequency ("RF") chain for each transmit (e.g., egress) and receive (e.g., ingress) direction. The capabilities of the devices with respect to some antenna panels, their duplexing capabilities, their beamforming capabilities, etc. may or may not be transparent to other devices. In some embodiments, the capability information may be communicated via signaling or may be provided to the devices without the need for signaling. If the information is available to other devices, it may be used for signaling or local decision making.

[0222] In some embodiments, a UE antenna panel may be a physical or logical antenna array that includes a set of antenna elements or antenna ports that share a common or significant portion of a radio frequency ("RF") chain (e.g., in-phase and / or quadrature ("I / Q") modulator, analog-to-digital ("A / D") converter, local oscillator, phase shift network). A UE antenna panel or UE panel may be a logical entity with physical UE antennas mapped to logical entities. The mapping of physical UE antennas to logical entities may be up to the UE implementation. Communicating (e.g., receiving or transmitting) on ​​at least a subset of the antenna elements or antenna ports (e.g., active elements) that are active to radiate energy of the antenna panel may require biasing or powering up of the RF chain, which results in a current drain or power consumption in the UE associated with the antenna panel (e.g., including the power consumption of a power amplifier and / or low noise amplifier ("LNA") associated with the antenna element or antenna port). As used herein, the phrase "active to radiate energy" is not intended to be limited to a transmitting function, but also encompasses a receiving function. Thus, the antenna elements that are active to radiate energy may be coupled, either simultaneously or sequentially, to a transmitter for transmitting radio frequency energy, or to a receiver for receiving radio frequency energy, or may generally be coupled to a transceiver to perform its intended functionality. Communication among the active elements of the antenna panel allows for the generation of a radiation pattern or beam.

[0223] In some embodiments, depending on the implementation of the UE itself, the "UE panel" may have at least one of the following functionalities as operational roles of the antenna group unit for independently controlling its transmit ("TX") beam, the antenna group unit for independently controlling its transmit power, and / or the antenna group unit for independently controlling its transmit timing: The "UE panel" may be transparent to the gNB. For some conditions, the gNB or network may assume that the mapping between the UE's physical antennas to the logical entity "UE panel" may not change. For example, the conditions may include until the next update or report from the UE, or may include a duration of time over which the gNB assumes no change in the mapping. The UE may report its UE capabilities regarding the "UE panel" to the gNB or network. The UE capabilities may include at least the number of "UE panels". In one embodiment, the UE may support UL transmission from one beam in the panel. With multiple panels, more than one beam (e.g., one beam per panel) may be used for UL transmission. In other embodiments, more than one beam per panel may be supported and / or used for UL transmission.

[0224] In some embodiments, antenna ports may be defined such that the channel through which a symbol on an antenna port is communicated can be estimated from the channel through which another symbol on the same antenna port is communicated.

[0225] In some embodiments, two antenna ports are said to be quasi-collocated ("QCL") if the large-scale characteristics of the channel through which symbols on one antenna port are communicated can be estimated from the channel through which symbols on another antenna port are communicated. The large-scale characteristics may include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive ("RX") parameters. The two antenna ports may be quasi-collocated with respect to a subset of the large-scale characteristics, and different subsets of the large-scale characteristics may be indicated by the QCL-Type. For example, qcl-Type may 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}. Other QCL types may be defined based on a combination of one or more large-scale properties.

[0226] In various embodiments, the spatial RX parameters may 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.

[0227] In some embodiments, QCL-TypeA, QCL-TypeB, and QCL-TypeC may be applicable for all carrier frequencies, while QCL-TypeD may only be applicable at higher carrier frequencies (e.g., mmWave, Frequency Range 2 ("FR2") and above) where the UE may not be able to perform omni-directional transmission (e.g., the UE would need to form a beam for directional transmission). For QCL-TypeD between two reference signals A and B, reference signal A is considered to be spatially co-located with reference signal B, and the UE may assume that reference signals A and B may be received using the same spatial filter (e.g., using the same RX beamforming weights).

[0228] In some embodiments, an "antenna port" may be a logical port that may correspond to a beam (e.g., resulting from beamforming) or may correspond to a physical antenna on the device. In some embodiments, a physical antenna may map directly to a single antenna port, where the antenna port corresponds to an 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 may be mapped to one or more antenna ports after applying complex weights and / or cyclic delays to the signals on each physical antenna. A physical antenna set may have antennas from a single module or panel, or from multiple modules or panels. The weights may be fixed, as in antenna virtualization schemes such as cyclic delay diversity ("CDD"). The procedure used to derive antenna ports from physical antennas may be device implementation specific and transparent to other devices.

[0229] In some embodiments, a transmission configuration indicator ("TCI") state ("TCI-state") associated with a target transmission may indicate parameters for configuring a quasi-co-location relationship between the target transmission (e.g., a target RS of a demodulation ("DM") reference signal ("RS") ("DM-RS") port of the target transmission during a transmission occasion) and a source reference signal (e.g., a synchronization signal block ("SSB"), a CSI-RS, and / or a sounding reference signal ("SRS")) for the quasi-co-location type parameter indicated in the corresponding TCI state. The TCI indicates which reference signals are used as QCL sources and what QCL characteristics may be derived from each reference signal. A device may receive configuration of multiple transmission configuration indicator states for a serving cell for transmission on the serving cell. In some embodiments, the TCI state includes at least one source RS for providing a basis (e.g., UE assumption) for determining a QCL and / or a spatial filter.

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

[0231] In various embodiments described herein, the entities are referred to as IAB nodes, but the same embodiments may apply to IAB donors (e.g., IAB entities connecting a core network to an IAB network) with minimal or no modifications. Moreover, different steps described for different embodiments may be reordered. Furthermore, each configuration may actually be provided by one or more configurations. An earlier configuration may provide a subset of parameters and a later configuration may provide another subset of parameters. In some embodiments, a later configuration may take precedence over values ​​provided by an earlier configuration or a pre-configuration.

[0232] In some embodiments, the configuration may be provided by radio resource control ("RRC") signaling, media access control ("MAC") signaling, physical layer signaling such as downlink control information ("DCI") messages, combinations thereof, or other methods. The configuration may include pre-configuration or semi-static configuration provided by a standard, by a vendor, and / or by the network and / or operator. Each parameter value received through configuration or instruction may take precedence over previous values ​​for similar parameters.

[0233] In various embodiments, despite frequent references to IAB, the embodiments herein may be applicable to wireless relay nodes and other types of wireless communication entities. Furthermore, Layer 1 ("L1") and / or Layer 2 ("L2") control signaling may refer to control signaling at Layer 1 (e.g., the physical layer) or Layer 2 (e.g., the data link layer). In particular, L1 and / or L2 control signaling may refer to L1 control signaling, such as DCI messages or uplink control information ("UCI") messages, L2 control signaling, such as MAC messages, or a combination thereof. The format and interpretation of L1 and / or L2 control signaling may be determined by a standard, a configuration, other control signaling, or a combination thereof.

[0234] It should be noted that any parameter described in this disclosure may in practice appear in the signaling or specifications as a linear function of that parameter.

[0235] In various embodiments, vendor-manufactured IAB systems and / or devices, as well as businesses deploying IAB systems and / or devices, may be allowed to negotiate the capabilities of the systems and / or devices. This may mean that some of the information expected to require signaling between entities may be readily available to the devices, for example, by storing the information on a memory unit such as a read-only memory ("ROM"), exchanging the information by proprietary signaling methods, providing the information by (pre-)configuration, or otherwise taking the information into account when creating the hardware and / or software of the IAB systems and / or devices or other entities in the network. In some embodiments, the embodiments described herein that include exchanging information may be extended to similar embodiments in which the information is obtained by other embodiments.

[0236] Additionally, embodiments used for the IAB Mobile Terminal ("MT") ("IAB-MT") may be employed by the UE as well. If an embodiment uses a capability that is not supported by a legacy UE, an enhanced UE may be used to handle that capability. In this case, the UE may be referred to as an enhanced UE or an IAB-enhanced UE and may convey its information of its extended capabilities to the network for correct configuration and operation.

[0237] As used herein, a node or wireless node may refer to an IAB node, an IAB-DU, an IAB-MT, a UE, a base station ("BS"), a gNode B ("gNB"), a transmit receiving point ("TRP"), an IAB donor, etc. The embodiments herein with emphasis on the types of nodes are not intended to be limiting in scope.

[0238] In some embodiments, it may be used to perform measurements for beam training on reference signals. In some embodiments, the measurements may be performed on resources that are not necessarily configured for the reference signals, but rather the node may measure received signal power, obtain RSSI, etc.

[0239] In various embodiments, phrases such as Case C multiplexing or Case D multiplexing are merely a matter of nomenclature. Instead, Case C multiplexing may be identified by an uplink transmission by the IAB-MT of the node and an uplink reception by the IAB-DU of the node. Similarly, Case D multiplexing may be identified by a downlink reception by the IAB-MT of the node and a downlink transmission by the IAB-DU of the node. Generally, depending on the node capabilities, such as multi-panel, and / or the full-duplex capabilities of the IAB node, one or more of the defined multiplexing cases may be operational at a given moment. For example, if an IAB node transmits an uplink signal to a parent node while transmitting signals to and receiving signals from a child node, the IAB node may be performing Case A multiplexing and Case C multiplexing simultaneously. It should therefore be noted that the method described herein is not bound to a particular multiplexing case. Different steps / elements described in the proposed method may be mixed and matched to achieve different multiplexing cases, without any explicit mention of how the information obtained by measurement and signaling may be used.

[0240] In some embodiments, a beam designation is referred to. In practice, a beam designation may refer to a designation of a reference signal by ID or indicator, a resource associated with a reference signal, spatial relationship information comprising information of a reference signal, or a counterpart of a reference signal (e.g., for beam correspondence).

[0241] As used herein, Hybrid Automatic Repeat Request ("HARQ") ACK "HARQ-ACK" may collectively refer to positive acknowledgement ("ACK") and negative acknowledgement ("NACK" or "NAK"). An ACK means that a transport block ("TB") is received correctly, and a NACK (or NAK) means that a TB is received in error.

[0242] 17 is a flow chart diagram illustrating one embodiment of a method 1700 for transmitting a MAC CE message by an IAB node. In some embodiments, the method 1700 is performed by an apparatus such as the remote unit 102 and / or the network unit 104. In some embodiments, the method 1700 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0243] In various embodiments, the method 1700 includes transmitting 1702 a MAC CE message at the first IAB node to the second IAB node, The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0244] In some embodiments, the second IAB node is a parent node of the first IAB node, and the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. In some embodiments, the range is indicated by a combination of a maximum transmit power value and a transmit power offset value. In various embodiments, the resource configuration is provided by an RRC entity.

[0245] In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration. In some embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using the associated frequency resources. In some embodiments, the multiplexing mode comprises MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof.

[0246] In various embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the indicated multiplexing mode. In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying a beam indicated by the at least one uplink beam identifier. In some embodiments, the MAC CE message is associated with a third IAB node, the third IAB node being a child node of the first IAB node.

[0247] 18 is a flow chart diagram illustrating another embodiment of a method 1800 for transmitting a MAC CE message by an IAB node. In some embodiments, the method 1800 is performed by an apparatus such as the remote unit 102 and / or the network unit 104. In some embodiments, the method 1800 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0248] In various embodiments, the method 1800 includes transmitting (1802) a MAC CE message at a first IAB node to a second IAB node. The MAC CE message includes an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof. The second IAB node is a parent node of the first IAB node. The MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node. The range is indicated by a combination of a maximum transmit power value and a transmit power offset value. The multiplexing mode includes MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof. The MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying the beam indicated by the at least one uplink beam identifier, or some combination thereof.

[0249] In one embodiment, an apparatus comprising a first IAB node, the apparatus further comprising a transmitter for transmitting a MAC CE message to a second IAB node, the MAC CE message comprising an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0250] In some embodiments, the second IAB node is a parent node of the first IAB node, and the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node.

[0251] In some embodiments, the range is indicated by a combination of a maximum transmit power value and a transmit power offset value.

[0252] In various embodiments, the resource configuration is provided by an RRC entity.

[0253] In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration.

[0254] In some embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using the associated frequency resource.

[0255] In some embodiments, the multiplexing mode comprises MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof.

[0256] In various embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the indicated multiplexing mode.

[0257] In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the beam indicated by the at least one uplink beam identifier.

[0258] In some embodiments, the MAC CE message is associated with a third IAB node, where the third IAB node is a child node of the first IAB node.

[0259] In one embodiment, a method in a first IAB node, the method comprising transmitting a MAC CE message to a second IAB node, the MAC CE message comprising an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association with an MT of the first IAB node, a second indication of association with a cell of a DU of the first IAB node, or some combination thereof.

[0260] In some embodiments, the second IAB node is a parent node of the first IAB node, and the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node.

[0261] In some embodiments, the range is indicated by a combination of a maximum transmit power value and a transmit power offset value.

[0262] In various embodiments, the resource configuration is provided by an RRC entity.

[0263] In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration.

[0264] In some embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node using the associated frequency resource.

[0265] In some embodiments, the multiplexing mode comprises MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof.

[0266] In various embodiments, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the indicated multiplexing mode.

[0267] In one embodiment, the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the beam indicated by the at least one uplink beam identifier.

[0268] In some embodiments, the MAC CE message is associated with a third IAB node, where the third IAB node is a child node of the first IAB node.

[0269] In one embodiment, an apparatus comprising a first IAB node, the apparatus further comprising a transmitter for transmitting a MAC CE message to a second IAB node, the MAC CE message comprising an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof, the second IAB node being a parent node of the first IAB node, the MAC CE message indicating a range of transmit power for an uplink from the first IAB node to the second IAB node, the range being indicated by a combination of the maximum transmit power value and the transmit power offset value, the multiplexing mode comprising MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof, and the MAC CE message further comprises a transmitter for transmitting a MAC CE message to a second IAB node, the MAC CE message comprising an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of the first IAB node with a cell for a DU, or some combination thereof, the second IAB node being a parent node of the first IAB node, The CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying a beam indicated by the at least one uplink beam identifier, or some combination thereof.

[0270] In one embodiment, a method in a first IAB node, the method comprising: transmitting a MAC CE message to a second IAB node, the MAC CE message comprising an ID associated with a resource configuration, a transmit power offset value, a maximum transmit power value, information corresponding to a multiplexing mode, at least one uplink beam identifier, a first indication of association of the first IAB node with a MT, a second indication of association of a DU of the first IAB node with a cell, or some combination thereof, the second IAB node being a parent node of the first IAB node, the MAC CE message indicating a range of transmit power for an uplink from the first IAB node to the second IAB node, the range being indicated by a combination of a maximum transmit power value and a transmit power offset value, the multiplexing mode comprising MT transmit and DU transmit, MT receive and DU receive, MT transmit and DU receive, MT receive and MT transmit, or some combination thereof, and The CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration, the first IAB node applying the indicated multiplexing mode, the first IAB node applying a beam indicated by the at least one uplink beam identifier, or some combination thereof.

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

[0272] 100 Wireless communication system 102 Remote Unit 104 Network Unit 200 equipment 202 Processor 204 Memory 206 Input Devices 208 Display 210 Transmitter 212 Receiver 300 equipment 302 Processor 304 Memory 306 Input Devices 308 Display 310 Transmitter 312 Receiver 400 IAB System 402 Core Network (CN) 404 IAB Donors 406 IAB Node 408 UE 500 Systems 502 Core Network (CN) 504 IAB System 506UE 600 IAB System 602 Core Network 604 IAB Donors / Parent IAB Nodes 606 IAB Node 2 608 IAB Node 1 702 First Case 704 MT 706DU 712 Second Case 718 Third Case 724 Fourth Case 1200 System 1202 IAB Node (N) 1203 Send 1204 Parent Node or IAB Donor (PN) 1206 Upstream Link 1208 Child Node or UE 1210 downstream link 1400 DC Architecture 1402CN 1404 IAB Donor 1406 First Parent Node 1408 Second Parent Node 1410 IAB Node 1500 DC Architecture 1502CN 1504 First IAB Donor 1506 Second IAB Donor 1508 First Parent Node 1510 Second Parent Node 1512 IAB nodes 1600 System 1602 Parent Node 1 1604 Parent Node 2 1605 IAB Node 1606 Child Nodes 1608 UE 1610 Upstream Backhaul Link 1612 Upstream Backhaul Links 1614 downstream backhaul links 1616 downstream backhaul links

Claims

1. a first integrated access and backhaul (IAB) node, at least one memory; at least one processor coupled to the at least one memory; The at least one processor is configured to cause the first IAB node to transmit a Media Access Control (MAC) Control Element (CE) message to a second IAB node, the MAC CE message comprising: An identifier (ID) associated with the resource configuration, transmit power offset value, maximum transmit power value, information corresponding to the multiplexing mode; at least one uplink beam identifier; a first indication of association of the first IAB node with a mobile terminal (MT); a second indication of association with a cell of a distributed unit (DU) of the first IAB node; or a combination thereof, First IAB node.

2. 2. The first IAB node of claim 1, wherein the second IAB node is a parent node of the first IAB node, and the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node.

3. 3. The first IAB node of claim 2, wherein the range is indicated by a combination of the maximum transmit power value and the transmit power offset value.

4. The first IAB node of claim 1 , wherein the resource configuration is provided by a radio resource control (RRC) entity.

5. 3. The first IAB node of claim 2, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration.

6. 3. The first IAB node of claim 2, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node using an associated frequency resource.

7. The multiplexing mode is The MT transmits and the DU transmits; The MT receives and the DU receives; The MT transmits and the DU receives; The MT receives and the MT transmits; or a combination thereof, The first IAB node of claim 1.

8. 3. The first IAB node of claim 2, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the indicated multiplexing mode.

9. The first IAB node of claim 2, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying a beam indicated by the at least one uplink beam identifier.

10. The first IAB node of claim 1 , wherein the MAC CE message is associated with a third IAB node, and the third IAB node is a child node of the first IAB node.

11. A first integrated access and backhaul (IAB) node method, comprising: sending a Media Access Control (MAC) Control Element (CE) message to a second IAB node, the MAC CE message comprising: An identifier (ID) associated with the resource configuration, transmit power offset value, maximum transmit power value, information corresponding to the multiplexing mode; at least one uplink beam identifier; a first indication of association of the first IAB node with a mobile terminal (MT); a second indication of association with a cell of a distributed unit (DU) of the first IAB node; or a combination thereof, method.

12. 12. The method of claim 11, wherein the second IAB node is a parent node of the first IAB node, and the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node.

13. The method of claim 12 , wherein the range is indicated by a combination of the maximum transmit power value and the transmit power offset value.

14. The method of claim 11 , wherein the resource configuration is provided by a radio resource control (RRC) entity.

15. a first integrated access and backhaul (IAB) node, at least one memory; at least one processor coupled to the at least one memory; The at least one processor is further configured to cause the first IAB node to transmit a Media Access Control (MAC) Control Element (CE) message to a second IAB node, the MAC CE message comprising: An identifier (ID) associated with the resource configuration, transmit power offset value, maximum transmit power value, information corresponding to the multiplexing mode; at least one uplink beam identifier; a first indication of association of the first IAB node with a mobile terminal (MT); a second indication of association with a cell of a distributed unit (DU) of the first IAB node; or a combination thereof, the second IAB node is a parent node of the first IAB node; the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node; the range is indicated by a combination of the maximum transmit power value and the transmit power offset value; The multiplexing mode is The MT transmits and the DU transmits; The MT receives and the DU receives; The MT transmits and the DU receives; The MT receives and the MT transmits; or a combination thereof, the MAC CE message the first IAB node using resources associated with the resource configuration; the first IAB node applies the indicated multiplexing mode; the first IAB node applying a beam indicated by the at least one uplink beam identifier; or a combination thereof indicates that the parent node applies the range in response to First IAB node.

16. A method for a first integrated access and backhaul (IAB) node, comprising: sending a Media Access Control (MAC) Control Element (CE) message to a second IAB node, the MAC CE message comprising: An identifier (ID) associated with the resource configuration, transmit power offset value, maximum transmit power value, information corresponding to the multiplexing mode; at least one uplink beam identifier; a first indication of association of the first IAB node with a mobile terminal (MT); a second indication of association with a cell of a distributed unit (DU) of the first IAB node; or a combination thereof, the second IAB node is a parent node of the first IAB node; the MAC CE message indicates a range of transmit power for an uplink from the first IAB node to the second IAB node; the range is indicated by a combination of the maximum transmit power value and the transmit power offset value; The multiplexing mode is The MT transmits and the DU transmits; The MT receives and the DU receives; The MT transmits and the DU receives; The MT receives and the MT transmits; or a combination thereof, the MAC CE message the first IAB node using resources associated with the resource configuration; the first IAB node applies the indicated multiplexing mode; the first IAB node applying a beam indicated by the at least one uplink beam identifier; or a combination thereof indicates that the parent node applies the range in response to method.

17. The method described in claim 16, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node using resources associated with the resource configuration.

18. The method described in claim 17, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node using the associated frequency resource.

19. The multiplexing mode: The MT transmits and the DU transmits; The MT receives and the DU receives; The MT transmits and the DU receives; The MT receives and the MT transmits; or a combination thereof, 17. The method of claim 16.

20. The method described in claim 16, wherein the MAC CE message indicates that the parent node applies the range in response to the first IAB node applying the indicated multiplexing mode.

Images