Resource attribute configuration

By receiving and processing the time domain and frequency domain attribute configuration in wireless communication networks, determining resource availability and performing corresponding operations, the problem of inefficiency caused by unknown resource attributes is solved, and efficient management and flexible configuration of resources are achieved.

CN115443628BActive Publication Date: 2024-11-26LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180026432.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-04-02
Filing Date
2021-04-01
Publication Date
2024-11-26
Estimated Expiration
2041-04-01

AI Technical Summary

Technical Problem

In wireless communication networks, resource attributes (time and frequency domain attributes) may be hard, soft or unavailable, resulting in inefficient resource allocation and usage, and the prior art is difficult to effectively manage and indicate resource availability.

Method used

By receiving parameter configurations of time domain and frequency domain attributes, the attributes of the resource are determined, and the availability of the resource is determined based on these attributes, and corresponding operations are performed, such as the following link transmission or uplink reception, using RRC signaling and DCI messages Indicates the availability of resources and implements dynamic configuration and management of resources.

Benefits of technology

It improves resource utilization efficiency, enhances resource allocation flexibility and management capabilities, ensures effective utilization of resources, and adapts to dynamic business needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115443628B_ABST
    Figure CN115443628B_ABST
Patent Text Reader

Abstract

Apparatus, methods and systems for resource attribute configuration are disclosed. A method (2200) includes receiving (2202) a first configuration for a resource. The first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft and / or unavailable. The method (2200) includes receiving (2204) a second configuration for the resource. The second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft and / or unavailable. The method (2200) includes determining (2206) an attribute of the resource based on the time domain attribute and the frequency domain attribute. The attribute is hard, soft and / or unavailable. The method (2200) includes, in response to determining that the attribute is soft: determining (2208) whether the resource is indicated as available; and performing an operation on the resource.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 63 / 004,192, filed on April 2, 2020 by Majid Ghanbarinejad, entitled “APPARATUSES, METHODS, AND SYSTEMS FOR RESOURCE CONFIGURATION AND DUPLEXING ENHANCEMENT ININTEGRATED ACCESS AND BACKHAUL,” which is incorporated herein by reference in its entirety. Technical Field

[0003] The subject matter disclosed herein relates generally to wireless communications and, more particularly, to resource attribute configuration. Background Art

[0004] In some wireless communication networks, resource attributes may be hard, soft, or unavailable. These resource attributes may correspond to a certain domain, but may be unknown for other domains and / or combinations of domains. Summary of the invention

[0005] Methods for configuring resource attributes are disclosed. Devices and systems also perform the functions of these methods. One embodiment of the method includes receiving a first configuration for a resource. The first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft and / or unavailable. In some embodiments, the method includes receiving a second configuration for the resource. The second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft and / or unavailable. In certain embodiments, the method includes determining an attribute for the resource based on the time domain attribute and the frequency domain attribute. The attribute is hard, soft and / or unavailable. In various embodiments, the method includes, in response to determining that the attribute is soft: determining whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource. The operation is downlink transmission and / or uplink reception.

[0006] A device for resource attribute configuration includes a receiver: which receives a first configuration for a resource, wherein the first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft, and / or unavailable; and receives a second configuration for the resource, wherein the second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft, and / or unavailable. In various embodiments, the device includes a processor: which determines an attribute of the resource based on the time domain attribute and the frequency domain attribute, wherein the attribute is hard, soft, and / or unavailable; and, in response to determining that the attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is downlink transmission and / or uplink reception.

[0007] Another embodiment of a method for resource attribute configuration includes receiving a configuration for a symbol. The configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft and / or unavailable. In some embodiments, the method includes receiving a first control message corresponding to a set of frequencies. In various embodiments, the method includes determining a second attribute of a resource on the symbol based on the first attribute and the first control message. The second attribute is hard, soft and / or unavailable. In some embodiments, the method includes, in response to determining that the second attribute is soft: determining whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource. The operation is a downlink transmission and / or an uplink reception.

[0008] Another apparatus for resource attribute configuration includes a receiver that receives a configuration for a symbol, wherein the configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft, and / or unavailable; and receives a first control message corresponding to a set of frequencies. In various embodiments, the apparatus includes a processor that determines a second attribute of a resource on the symbol based on the first attribute and the first control message, wherein the second attribute is hard, soft, and / or unavailable; and, in response to determining that the second attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is a downlink transmission and / or an uplink reception. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 1is a schematic block diagram illustrating an embodiment of a wireless communication system for resource attribute configuration;

[0011] Figure 2 is a schematic block diagram showing an embodiment of an apparatus that can be used for resource attribute configuration;

[0012] Figure 3 is a schematic block diagram showing an embodiment of an apparatus that can be used for resource attribute configuration;

[0013] Figure 4 is a diagram illustrating one embodiment of an IAB system;

[0014] Figure 5 is a diagram illustrating one embodiment of an IAB system having single-panel and multi-panel IAB nodes;

[0015] Figure 6 is a diagram illustrating another embodiment of an IAB system having single-panel and multi-panel IAB nodes;

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

[0017] Figure 8 is a timing diagram illustrating one embodiment of resource configuration in the frequency domain;

[0018] Fig. 9 is a flow chart illustrating one embodiment of a semi-static availability configuration;

[0019] Fig.10 is a flow chart illustrating one embodiment of hard and / or soft configuration;

[0020] Fig.11 is a diagram illustrating one embodiment of a configuration of frequency domain availability;

[0021] Fig.12 is a flow chart illustrating another embodiment of hard and / or soft configuration;

[0022] Fig.13 is a block diagram illustrating one embodiment of activating and indicating frequency domain availability ("F-AI");

[0023] Fig.14 is a diagram illustrating another embodiment of activation and indication of F-AI;

[0024] Fig.15 is a flow chart illustrating one embodiment of a compatible dynamic indication;

[0025] Fig.16 is a diagram illustrating one embodiment of resource allocation in an IAB system;

[0026] Fig.17 is a block diagram illustrating one embodiment of a BWP configuration;

[0027] Fig.18 is a diagram illustrating another embodiment of a BWL configuration;

[0028] Fig.19 is a flow chart illustrating one embodiment of a bandwidth portion based method;

[0029] Fig. 20 is a flow chart illustrating another embodiment of a bandwidth portion based method;

[0030] Fig.21 is a flow chart illustrating one embodiment of an implicit method;

[0031] Fig. 22 is a flow chart illustrating one embodiment of a method for resource attribute configuration; and

[0032] Fig.23 is a flow chart illustrating another embodiment of a method for resource attribute configuration. DETAILED DESCRIPTION

[0033] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.) or a combination of software and hardware aspects, which may be generally referred to herein as a "circuit", "module" or "system". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs a signal for accessing the code.

[0034] Certain functional units described in this specification may be labeled as modules in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including a custom very large scale integration ("VLSI") circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, a programmable array logic, a programmable logic device, or the like.

[0035] Modules can also be implemented with code and / or software to be executed by various types of processors. The identified code module can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as an object, process or function. However, the executable file of the identified module does not need to be physically located together, but can include irrelevant instructions stored in different locations, which, when logically connected together, include the module and realize the described purpose of the module.

[0036] In fact, a code module can be a single instruction or many instructions, and can even be distributed on several different code segments, among different programs and across several memory devices. Similarly, in this article, operating data can be identified and illustrated in a module, and can be embodied in any appropriate form and organized in a data structure of any appropriate type. Operating data can be collected as a single data set, or can be distributed in different locations, including on different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

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

[0038] More specific examples of storage devices (a non-exhaustive list) 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 foregoing. In the context of this document, 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.

[0039] The code for performing the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages ​​including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly languages. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network including a local area network ("LAN") or a wide area network ("WAN"), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0040] References throughout this specification to "one embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly stated, throughout the specification, the occurrence of the phrases "in one embodiment," "in an embodiment," and similar language may, but not necessarily, all refer to the same embodiment, but rather to "one or more but not all embodiments." Unless otherwise expressly stated, the terms "include," "comprise," "have," and variations thereof mean "including but not limited to." Unless otherwise expressly stated, a list of enumerated items does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "a," "an," and "the" also refer to "one or more."

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

[0042] Various aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions / operations specified in the schematic flow charts and / or schematic block diagram blocks or some blocks.

[0043] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in a block or some blocks of the schematic flowchart and / or schematic block diagram.

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

[0045] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible architectures, functions and operations of devices, systems, methods and program products according to different embodiments. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, a fragment or a portion of a code, which includes one or more executable instructions of a code for implementing a specified (multiple) logical function.

[0046] It should also be noted that in some alternative embodiments, the functions marked in the blocks may not occur in the order marked in the drawings. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functionality involved. It is conceivable that other steps and methods are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated drawings.

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

[0048] The description of an element in each figure may refer to the elements of the previous figure. In all figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.

[0049] Figure 1 An embodiment of a wireless communication system 100 for resource attribute configuration is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but one skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

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

[0051] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as and / or may include access points, access terminals, base stations, base stations, node-Bs, evolved node-Bs (“eNBs”), 5G node-Bs (“gNBs”), home node-Bs, relay nodes, devices, core networks, air servers, radio access nodes, access points (“APs”), new radios (“NRs”), network entities, access and mobility management functions (“AMFs”), unified data management (“UDMs”), unified data repositories (“UDRs”), UDM / UDRs, policy control functions (“PCFs”), radio access networks (“RANs”), network slice selection functions (“NSSFs”), operations, administration, and management (“OAMs”), session management functions (“SMFs”), user plane functions (“UPFs”), application functions, authentication server functions (“AUSFs”), security anchor functionality (“SEAFs”), trusted non-3GPP gateway functions (“TNGFs”), or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and the public switched telephone network. These and other elements of the radio access and core networks are not shown, but are generally well known to those of ordinary skill in the art.

[0052] In one embodiment, the wireless communication system 100 conforms to the NR protocol standardized in the Third Generation Partnership Project ("3GPP"), wherein the network unit 104 transmits on the downlink ("DL") using an OFDM modulation scheme, 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. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, an Institute of Electrical and Electronics Engineers ("IEEE") 802.11 variant, a Global System for Mobile Communications ("GSM"), a General Packet Radio Service ("GPRS"), a Universal Mobile Telecommunications System ("UMTS"), a Long Term Evolution ("LTE") variant, a Code Division Multiple Access 2000 ("CDMA2000"), ZigBee, Sigfoxx, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0053] The network unit 104 can serve multiple remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0054] In various embodiments, the remote unit 102 may receive a first configuration for a resource. The first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft and / or unavailable. In some embodiments, the remote unit 102 may receive a second configuration for the resource. The second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft and / or unavailable. In some embodiments, the remote unit 102 may determine the attribute of the resource based on the time domain attribute and the frequency domain attribute. The attribute is hard, soft and / or unavailable. In various embodiments, the remote unit 102 may determine whether the resource is indicated as available in response to determining that the attribute is soft; and, in response to determining that the resource is indicated as available, perform an operation on the resource. The operation is downlink transmission and / or uplink reception. Therefore, the remote unit 102 can be used for resource attribute configuration.

[0055] In some embodiments, the remote unit 102 may receive a configuration for a symbol. The configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft and / or unavailable. In some embodiments, the remote unit 102 may receive a first control message corresponding to a set of frequencies. In various embodiments, the remote unit 102 may determine a second attribute of a resource on the symbol based on the first attribute and the first control message. The second attribute is hard, soft and / or unavailable. In some embodiments, the remote unit 102 may determine whether the resource is indicated as available in response to determining that the second attribute is soft; and, in response to determining that the resource is indicated as available, perform an operation on the resource. The operation is downlink transmission and / or uplink reception. Therefore, the remote unit 102 can be used for resource attribute configuration.

[0056] Figure 2An embodiment of an apparatus 200 that can be used for resource attribute configuration is depicted. Apparatus 200 includes an embodiment of remote unit 102. In addition, remote unit 102 may include processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212. In some embodiments, input device 206 and display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and / or display 208.

[0057] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of 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.

[0058] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. 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 non-volatile computer storage media. For example, memory 204 may include a hard 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 related data, such as an operating system or other controller algorithms operating on remote unit 102.

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

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

[0061] In some embodiments, the display 208 includes one or more speakers for producing sounds. For example, the display 208 can produce an audible alarm or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0062] In some embodiments, the receiver 212: receives a first configuration for a resource, wherein the first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft, and / or unavailable; and receives a second configuration for the resource, wherein the second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft, and / or unavailable. In various embodiments, the processor 202: determines an attribute of the resource based on the time domain attribute and the frequency domain attribute, wherein the attribute is hard, soft, and / or unavailable; and, in response to determining that the attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is downlink transmission and / or uplink reception.

[0063] In some embodiments, the receiver 212: receives a configuration for a symbol, wherein the configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft, and / or unavailable; and receives a first control message corresponding to a set of frequencies. In various embodiments, the processor 202: determines a second attribute of a resource on the symbol based on the first attribute and the first control message, wherein the second attribute is hard, soft, and / or unavailable; and, in response to determining that the second attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is a downlink transmission and / or an uplink reception.

[0064] 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 transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0065] Figure 3 One embodiment of an apparatus 300 that may be used for resource attribute configuration is depicted. The apparatus 300 includes one embodiment of the network unit 104. In addition, 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. It is understood that 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.

[0066] In various embodiments, integrated access and backhaul ("IAB") technology may be used. In such embodiments, IAB technology may be intended to increase deployment flexibility and reduce 5G promotion costs. In addition, IAB technology may enable service providers to reduce cell planning and spectrum planning efforts while using wireless backhaul technology.

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

[0068] In some embodiments, the IAB may operate in a flexible time division duplex ("TDD") mode. In such embodiments, each time slot may be semi-statically configured to contain downlink ("DL" and / or "D") symbols, uplink ("UL" and / or "U") symbols, and flexible ("F") symbols. Each flexible symbol may be configured to be either a DL symbol or a UL symbol at an instance. The DL, UL, and / or F configurations may follow a UL-F-DL pattern (e.g., they may start with a UL symbol and end with a DL symbol), thereby providing flexibility over configurations that only follow a DL-F-UL pattern.

[0069] In various embodiments, in an IAB system, resources may be configured as hard ("H") or soft ("S"), or if not H or S, the resources may be considered unavailable ("NA"). In such embodiments, hard resources may always be available to schedule communications with a UE or child node; soft resources may be potentially available, which may be indicated by DCI signaling; and NA symbols may not be used by an IAB node to schedule its own communications with a UE or child node (however, this does not mean that an IAB node may not use NA symbols to communicate with its parent node, perform measurements on NA symbols, etc.).

[0070] In some embodiments, the D, U, F, H, S and / or NA attributes may be per OFDM symbol (e.g., the granularity for resource configuration with these attributes may be all available frequency resources (e.g., in the active bandwidth portion) on time resources as short as one OFDM symbol). In such embodiments, if soft resources are to be indicated as available or unavailable via DCI signaling, the granularity for availability indication ("AI") may be the resource type in terms of D, U and / or F per slot. That is, all symbols configured as D, L or F in a slot are indicated as available or unavailable. This may indicate a coarser granularity (e.g., substantially all frequency resources on one or several OFDM symbols).

[0071] In some embodiments, simultaneous operation (e.g., transmission and / or reception of signals) in an IAB system may be supported by enhancing resource multiplexing between child nodes and parent nodes. In various embodiments, resource configuration and availability indication may be enabled only in the time domain. In some embodiments, resource configuration and availability indication may be enabled in the frequency domain. In some embodiments, because there are a large number of physical resource blocks ("PRBs") in the frequency domain (e.g., compared to the number of OFDM symbols in a time slot), duplicating the time domain provisions for the frequency domain may not be sufficient.

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

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

[0074] The wireless connection (e.g., 414, 422, 426, 442, 444) between the MT of the IAB node and the DU of the parent node (which may be a Uu link) is referred to as a wireless backhaul link. In the wireless backhaul link, in terms of functionality, the MT is similar to the UE and the DU of the parent node is similar to a base station in a conventional cellular wireless link. Therefore, the link from the MT to the serving cell of the DU as the parent link is referred to as an uplink, and the link in the reverse direction is referred to as a downlink. In the present disclosure, embodiments may simply refer to an uplink or a downlink between IAB nodes, a link between a node and its parent node, a link between a node and its child node, etc., without directly referencing MT, DU, serving cell, etc.

[0075] Each IAB host or IAB node can serve a UE (e.g., 446) through an access link (e.g., 448). An IAB system like the IAB system 400 can be designed to enable multi-hop communication (e.g., a UE can be connected to a core network through an access link and multiple backhaul links between an IAB node and an IAB host). As used herein, unless otherwise stated, an "IAB node" can generally refer to an IAB node or an IAB host, as long as the connection between a CU and a core network is not involved.

[0076] Nodes, links, etc. that are closer to the IAB host and / or core network may be referred to as upstream nodes, links, etc. For example, the parent node of the subject node is the upstream node of the subject node and the link to the parent node is the upstream link relative to the subject node. Similarly, nodes, links, etc. that are farther from the IAB host and / or core network are referred to as downstream nodes, links, etc. For example, the child node of the subject node is the downstream node of the subject node and the link to the child node is the downstream link relative to the subject node.

[0077] Table 1 summarizes the terms used herein.

[0078] Table 1: Terminology

[0079]

[0080] As used herein, "operation" or "communication" may refer to transmission or reception in an uplink (e.g., upstream) or a downlink (e.g., downstream). In addition, the term "simultaneous operation" or "simultaneous communication" may refer to multiplexing and / or duplex transmission and / or reception by a node through one or more antennas and / or panels. The details of simultaneous operation (or concurrent operation) may be understood from the context.

[0081] In various embodiments, dynamic TDD (e.g., in NR) may be used through RRC configuration and lower layer control signaling. Dynamic TDD may enable NR systems to have more flexible slot formats for TDD operation that may be dynamically modified to accommodate changing traffic. RRC signaling may use the various IEs described herein to configure slots for TDD operation.

[0082] TDD-UL-DL-ConfigCommon IE: This information element ("IE") may determine the cell-specific uplink and / or downlink TDD configuration. This IE may contain a period value between 0.5 ms and 10 ms and a reference subcarrier spacing ("SCS"). A slot configuration pattern may be defined within a period (via one or two pattern fields). A period may contain multiple slots. The most general pattern for each period may be a number of downlink slots and symbols at the beginning and a number of uplink symbols and slots at the end. All remaining slots and / or symbols in the middle may be flexible and may be overridden by subsequent UE-specific configurations.

[0083] TDD-UL-DL-ConfigDedicated IE: This IE can determine the UE specific uplink and / or downlink TDD configuration. This IE can configure many slot configurations. Each slot configuration can contain an index based on a period defined by a cell-specific configuration, and a number of downlink and uplink symbols in the slot, which can overload flexible symbols configured by the cell-specific configuration.

[0084] In some embodiments, a resource that is flexible (e.g., not configured as downlink or uplink) through a cell-specific configuration or a UE-specific configuration may be dynamically indicated as a downlink or uplink for a UE or a group of UEs through DCI format 2_0. The corresponding DCI may include a slot format indicator ("SFI") and the index of the slot format table may be configured through RRC signaling. The configuration from the RRC signaling may reference each slot format through an 8-bit number.

[0085] In some embodiments, 56 of the 256 possible values ​​(e.g., indexed 0-55) may be used to define various combinations of slot formats. The general format of each slot format may be DL-F-UL, where the slot format may contain one, two, or all of the three types of symbols with various numbers in a specified order. In such embodiments, more than 41 values ​​(e.g., indexed 56-96) may be used for the UL-F-DL format of IAB to provide further flexibility for IAB nodes, which may start a slot with an uplink symbol followed by a downlink symbol.

[0086] In various embodiments, resources that are not configured or indicated as downlink or uplink through any signaling may be assumed to be reserved, which may enable flexibility for cell management, coexistence, and the like.

[0087] In certain embodiments, time domain allocation parameters k0, k1, k2 may be used and defined herein (eg, in NR).

[0088] PDSCH time domain allocation: The RRC parameter k0 in the RRC information element PDSCH-TimeDomainResourceAllocation may indicate the offset between the time slot containing the DCI scheduling the PDSCH transmission and the time slot containing the PDSCH transmission.

[0089] PDSCH Hybrid Automatic Repeat Request ("HARQ") Feedback Timing: L1 parameter k1 may be provided via the 'PDSCH-to-HARQ_feedback timing indicator' field in DCI formats 1_0 and 1_1 (eg, for scheduling PDSCH transmissions).

[0090] Physical Uplink Shared Channel ("PUSCH") Time Domain Allocation: The RRC parameter k2 in the RRC information element PUSCH-TimeDomainResourceAllocation may indicate the offset between the time slot containing the DCI scheduling the PUSCH transmission and the time slot containing the PUSCH transmission.

[0091] In some embodiments, such as in NR systems, control channels and shared channels may be delivered on a portion of bandwidth configured through RRC and further through MAC and Layer 1.

[0092] In certain embodiments, a UE may be configured with a bandwidth part ("BWP") for the downlink and / or uplink.

[0093] For the downlink, the UE may be configured with a set of up to four BWPs (e.g., a DL BWP set) for reception by the UE in the DL bandwidth by the parameter BWP-Downlink or by the parameter initialDownlinkBWP, where the set of parameters is configured by BWP-DownlinkCommon and BWP-DownlinkDedicated. If the UE is not provided with initialDownlinkBWP, the initial DL BWP may be defined by the position and number of consecutive PRBs starting from the PRB with the lowest index and ending at the PRB with the highest index among the PRBs of the control resource set ("CORESET") for the Type0-PDCCH common search space ("CSS") set, and the SCS and cyclic prefix for physical downlink control channel ("PDCCH") reception in the CORESET for the Type0-PDCCH CSS set; otherwise, the initial DL BWP may be provided by initialDownlinkBWP.

[0094] For the uplink, the UE can be configured with a set of up to four BWPs (e.g., UL BWP set) for transmission by the UE in the UL bandwidth via the parameter BWP-Uplink or via the parameter initialUplinkBWP, where the set of parameters is configured via BWP-UplinkCommon and BWP-UplinkDedicated. For operation on a primary cell or on a secondary cell, the initial UL BWP may be provided to the UE via initialUplinkBWP. If the UE is configured with a supplementary UL carrier, the initial UL BWP may be provided to the UE on the supplementary UL carrier via initialUplinkBWP.

[0095] In some embodiments, if the UE has a dedicated BWP configuration, the UE may be provided with a first active DL BWP for reception via firstActiveDownlinkBWP-Id and a first active UL BWP for transmission via firstActiveUplinkBWP-Id on a carrier of the primary cell.

[0096] In various embodiments, for each DL BWP or ULBWP in the DL BWP set or UL BWP set, respectively, the following parameters for the serving cell may be provided to the UE: SCS, cyclic prefix ("CP") length (normal or extended), starting RB and a number of consecutive RBs, an index in the DL BWP set or UL BWP set (e.g., by the corresponding BWP-Id), and a set of BWP common parameters and a set of BWP specific parameters.

[0097] In certain embodiments, BWP switching for a serving cell may be used to activate one inactive BWP and deactivate one active BWP at a time. BWP switching may be controlled by a PDCCH transmission indicating a downlink assignment or uplink grant, by a bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when a random access procedure is initiated. Upon RRC configuration and / or reconfiguration of firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id for a SpCell or activation of an SCell, the DL BWP and / or UL BWP indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively, may be active without receiving a PDCCH transmission indicating a downlink assignment or uplink grant. The active BWP for a serving cell may be indicated by RRC signaling or PDCCH transmission. For unpaired spectrum, the DL BWP may be paired with the UL BWP, and BWP switching may be common to both UL and DL.

[0098] In some embodiments, the bandwidth part indicator field may be configured in DCI format 0_1 ​​or DCI format 1_1 to indicate an active UL BWP or an active DL BWP from a configuration set. In such embodiments, the UE may set the active UL BWP or DL ​​BWP to the indicated UL BWP or DL ​​BWP.

[0099] Figure 5 The IAB system (e.g., IAB network) is illustrated. The IAB system or IAB network can be connected to the core network through one or more IAB hosts. Each IAB node can be connected to the IAB host and / or other IAB nodes through a wireless backhaul link. Each IAB host and / or node can also serve UE.

[0100] Figure 5is a diagram illustrating another embodiment of an IAB system 500. The IAB system 500 includes an IAB network 502 and an IAB host 504 (e.g., a parent IAB node) connected via a first backhaul link 506. The IAB system 500 includes a first UE 508 connected to the IAB host 504 via a second backhaul link 510. In addition, the IAB system 500 includes a first IAB node 512 (e.g., a single-panel node) connected to the IAB host 504 via a third backhaul link 514. In addition, the IAB system 500 includes a second IAB node 516 (e.g., a multi-panel node) connected to the IAB host 504 via a first antenna panel of the IAB node 516 by a fourth backhaul link 518. The IAB system 500 includes a third IAB node 520 (e.g., a child IAB node) connected to the second IAB node 516 by a fifth backhaul link 522 via a second antenna panel of the IAB node 516. In addition, the IAB system 500 includes a second UE 524 connected to the second IAB node 516 by a sixth backhaul link 526 through the first antenna panel or the second antenna panel of the IAB node 516. In addition, the IAB system 500 includes a fourth IAB node 528 (e.g., a sub-IAB node) connected to the first IAB node 512 through a seventh backhaul link 530. The IAB system 500 includes a third UE 532 connected to the first IAB node 512 through an eighth backhaul link 534.

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

[0102] In some embodiments, there may be various options regarding the structure and multiplexing and / or duplexing capabilities of the IAB node. For example, each IAB node may have one or more antenna panels, arrays, and / or subarrays. Each of the one or more antenna panels, arrays, and / or subarrays may be connected to a baseband unit via one or more RF chains. One or more antenna panels may be able to serve the entire spatial region of interest near the IAB node, or each antenna panel or each group of antenna panels may provide partial coverage (e.g., in a sector). An IAB node having multiple antenna panels that each serve a separate spatial region or sector may be referred to as a single-panel IAB node because it behaves similarly to a single-panel IAB node for communicating in each separate spatial region or sector.

[0103] In various embodiments, each antenna panel can be half-duplex ("HD") (e.g., capable of transmitting or receiving signals in a frequency band at one time) or full-duplex ("FD") (e.g., capable of both transmitting and receiving signals in a frequency band simultaneously). Unlike full-duplex radios, half-duplex radios can be implemented and used in practice, and can be assumed to be the default operating mode in a wireless system.

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

[0105] Table 2

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

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

[0108] Figure 7 7 is a diagram illustrating another embodiment of an IAB system 700. The IAB system 700 includes a network 702 and a parent node 704 (e.g., PN) connected by a first backhaul link 706. The IAB system 700 includes an IAB node 708 (e.g., N) connected to the parent node 704 by a second backhaul link 710. The IAB system 700 includes a child IAB node 712 (e.g., CN) connected to the IAB node 708 by a third backhaul link 714. In addition, the IAB system 700 includes a UE 716 connected to the IAB node 708 by a fourth backhaul link 718. Each of the parent node 704, the IAB node 708, and the child node 712 can be a single panel or a multi-panel as described herein.

[0109] In various embodiments, the IAB system may determine whether a resource is available (e.g., configured as hard, soft, or indicated as available). In such embodiments, the granularity of the availability of a resource may be symbols at all frequencies (e.g., within an active BWP). This is true even if the resource is not configured as hard, because it has a periodic signal configured on it, the entire symbol may be considered hard.

[0110] In some embodiments, either all frequency resources on a symbol are available, or none are available. This may be a problem in various embodiments where enhanced duplexing allows FDM between communications (eg, including communications in downstream and upstream).

[0111] In some embodiments, to determine the availability of resources for duplexing, the following methods may be used: 1) an explicit method: this may use new signaling to configure and / or indicate the availability of resources in the frequency domain; and 2) an implicit method: rules may be defined that allow the IAB node to determine the availability of frequency resources.

[0112] In various embodiments, one way to implement FDM between upstream and downstream operations is to explicitly configure resources for each node. Figure 8 As shown, resources are configured in the frequency domain per time slot within a period of multiple time slots.

[0113] Figure 8 800 is a timing diagram illustrating one embodiment of resource configuration over a time domain 802 and a frequency domain 804. Time 802 includes a first time period 806 and a second time period 808 (e.g., the second time period 808 is a repetition of the first time period 806). The first time period 806 includes a first time slot 810, a second time slot 812, and a third time slot 814. In addition, the second time period 808 includes a first time slot 816, a second time slot 818, and a third time slot 820. Figure 8 Illustrated are a PN transmission frequency 822 in a time slot, a guard band 824 occurring between an N transmission frequency and a PN transmission frequency or a CN transmission frequency, an N transmission frequency 826 in a time slot, a CN transmission frequency 828 in a time slot, and an overlap frequency 830.

[0114] exist Figure 8In the semi-static configuration, each resource set is configured for the node and marked accordingly. The configuration is repeated in each time period until it is released or modified. The following can be considered for semi-static configuration: 1) The node can use only the resources configured to be available to it for scheduling downstream communications to and / or from child nodes or UEs - while scheduling upstream communications can be left to the parent node; 2) The granularity in the time domain can be time slots, symbols, etc. - the granularity in the frequency domain can be physical resource blocks ("PRBs"), RBGs, physical resource groups ("PRGs"), etc. - the granularity value can be determined by the specification or configured by the system; 3) The resource configuration can be sent by the IAB host CU and can be based on factors such as the IAB system topology, link quality (e.g., CSI), the traffic on each node strength, QoS of the services on each node, cross-link interference (“CLI”), etc.; 4) The resource configuration for an adjacent IAB node or a next-hop neighbor node (e.g., node N and its parent node PN) may depend on the multiplexing capability of the node—for example: a) if N is only capable of TDM, then the resource sets configured for N and PN may be configured only on separate time resources such as separate time slots, b) if N is capable of FDM via a single half-duplex (“HD”) antenna and / or panel, then non-overlapping resources may be configured for N and PN on the same time resources—such as the same time slot, c) if N d) if N has multiple half-duplex ("HD") antennas and / or panels, overlapping resources can be configured for N and PN on the same time resources, such as the same time slot, and d) if N has full-duplex ("FD") antennas and / or panels, overlapping resources can be configured for N and PN on the same time resources, such as the same time slot; 5) the resource configuration for N and PN can depend on other node capabilities - for example, if N requires a guard band or guard time between upstream and downstream operations, this can be considered in the configuration for N and PN - resources configured for N can be combined with resources configured for PN or CN. Consider guard bands between sources - the required guard bands (e.g., in multiple PRBs for reference subcarrier spacing) or guard times (e.g., in terms of OFDM symbols and / or time slots for reference subcarrier spacing) may depend on the capabilities of the node and may be selected from possible values ​​of the guard band or guard time and / or may depend on the band - a node may indicate its capability information to its PN or CU; and / or 6) overlapping resources may be configured for non-adjacent nodes (e.g., such as PNs and CNs in the second time slot 812 and the second time slot 818) unless the cross-link interference ("CLI") is too high.

[0115] Tables 3 and 4 illustrate methods for CU and DU in the IAB system.

[0116] Table 3: Methods used for CU

[0117]

[0118]

[0119] Table 4: Methods used for DU

[0120]

[0121] Fig. 9 900 is a flowchart illustrating one embodiment of a semi-static availability configuration. Flowchart 900 includes a method for a CU, the method including: receiving 902 or configuring information for topology, routing, channel status ("CSI"), traffic strength, cross-link interference ("CLI"), multi-panel capability ("MP"), minimum guard time (Tmin) and / or minimum guard band ("Fmin"); and sending 904 semi-static resource configurations C, each semi-static resource configuration C including: resource sets (R) in the frequency domain in a time period (T) and a time slot, wherein each resource in the resource set is configured as D, U, F, such that: the size of the resource set and the location of the resource set in the time-frequency grid are determined based on the channel status, traffic strength and / or cross-link interference; and the guard time and guard band between resource sets are determined based on the information of topology (e.g., what node is the parent node of what other node), multi-panel capability, minimum guard time and / or minimum guard band.

[0122] Flowchart 900 also includes a method for DU, the method including: receiving 906 a semi-static resource configuration C, each semi-static resource configuration C including: a resource set (R) in the frequency domain in a time period (T) and a time slot, wherein each resource in the resource set is configured as D, U or F; receiving 908 an indication of which flexible resources are downlink or uplink; using 910 resources in the resource set for scheduling downlink channels and / or uplink channels for communication with a subnode ("CN") and / or a UE, such that: downlink resources and flexible resources indicated by the downlink are used for scheduling downlink channels, and uplink resources and flexible resources indicated by the uplink are used for scheduling uplink channels; and transmitting 912 a downlink signal on the downlink channel and / or receiving an uplink signal on the uplink channel.

[0123] Fig. 9 The method may implement FDM between signals in the downstream and upstream through one or more antennas and / or panels. Once the IAB node receives the resource configuration, the IAB node considers the associated resources available for scheduling by the IAB node. Therefore, for the IAB node DU, resources are either available or unavailable until the configuration is published or modified. This semi-static configuration may not allow dynamic management of resources, especially in large bandwidths.

[0124] In some embodiments, to improve the flexibility of resource configuration in the frequency domain, the resources available to a node may be configured as H or S as follows: 1) hard resources can always be assumed to be available to the node for scheduling communications; and 2) soft resources cannot be assumed to be available to the node until it is indicated as available through further signaling.

[0125] In various embodiments, once the frequency resources are configured as soft, the availability of the resources in each period may be determined by further signaling. For example, control signaling such as a DCI message may be used to determine which resources are available in the time domain and the frequency domain.

[0126] Certain embodiments may be used to indicate how to apply multi-panel, guard time and guard band constraints while indicating the availability of soft resources.

[0127] In some embodiments, the node receives information about the constraints directly from the child node or from the CU and applies the constraints if the availability and scheduled communications are indicated. An embodiment of the DU method is shown in Table 5.

[0128] Table 5: Methods used for DU

[0129]

[0130] Fig.10 1000 is a flowchart illustrating an embodiment of hard configuration and / or soft configuration. Flowchart 1000 includes a method for a DU, the method including: receiving 1002 a semi-static resource configuration C, each semi-static resource configuration C including: a resource set (R) in the frequency domain in a time period (T) and a time slot, wherein each resource in the resource set is configured as D, U or F, and is also configured as H or S; receiving 1004 information of MP and / or Fmin of CN; receiving 1006 an indication of which flexible resources are downlink or uplink; receiving 1008 F-AI1 from PN; transmitting 1010 F-AI2 to CN; using 10 12 communication with the CN and / or the UE, so that: downlink resources and flexible resources indicated by the downlink are used to schedule downlink channels, uplink resources and flexible resources indicated by the uplink are used to schedule uplink channels, soft resources are used only when available indicated by F-AI1, and resources multiplexed with resources indicated by F-AI2 as available meet the constraints based on the multi-panel capability of the CN and / or the minimum guard band information; and 1014 downlink signals are transmitted on the downlink channel and / or uplink signals are received on the uplink channel.

[0131] In some embodiments, the CU applies constraints in a manner that the DU does not need to be aware of the constraints.

[0132] In some embodiments, resource configuration and indication features are used. In such embodiments, only time domain resource configuration and indication features may be used. However, in other embodiments, frequency domain features may be used to determine whether frequency domain resources such as PRBs are available for each H, S and / or NA symbol configured.

[0133] In various embodiments, the availability of resources on the time-frequency grid may be determined by two values ​​in two fields, and tables such as Table 6 and Table 7 may be used.

[0134] Table 1

[0135] Hard Soft Unavailable Hard Hard Soft Unavailable Soft Soft Soft Unavailable Unavailable Unavailable Unavailable Unavailable

[0136] Table 2

[0137] Hard Soft Unavailable Available Hard Soft Unavailable Unavailable Unavailable Unavailable Unavailable

[0138] In Table 6 and Table 7, each column may represent resource configuration and / or indication in the time domain, and each row may represent resource configuration and / or indication in the frequency domain.

[0139] Table 7 can be used for the remaining embodiments described herein. However, the embodiments can also be extended to Table 6.

[0140] According to Table 7, any symbol, whether it is configured as {D, U, F} or not, can be further configured as available or unavailable for a certain subband and / or set of PRBs in the BWP. The interpretation of the frequency domain configuration and / or indication for H, S and / or NA symbols according to Table 7 can be as follows: H symbol: If the symbol is configured as hard, any part of it configured as available in the frequency domain is regarded as H resources, and any part of it configured as unavailable is regarded as NA resources; S symbol: If the symbol is configured as soft, any part of it configured as available in the frequency domain is regarded as S resources, and any part of it configured as unavailable is regarded as NA resources - soft resources can be subject to availability indication - in addition, any soft resources can be indicated as available in the frequency domain; and NA symbol: If the symbol is configured as unavailable, all frequency domain resources will be regarded as NA resources - as an example behavior rule, further configuration of availability in the frequency domain may not change the symbol from NA.

[0141] In some embodiments, the configuration of frequency domain availability may be considered as a "mask" over the time domain resource configuration.

[0142] Fig.11 1100 is a diagram illustrating one embodiment of a configuration of frequency domain availability in a time slot 1102. The time slot includes hard symbols 1104, soft symbols 1106, and NA symbols 1108. Frequency domain availability 1110 illustrates a specific frequency including hard resources 1112 and soft resources 1114.

[0143] In various embodiments, if resources are configured as soft, they may be indicated by lower layers as available to nodes to be able to allocate resources for scheduling (eg, dynamic indication of availability of soft resources).

[0144] Table 8: Methods used for DU

[0145]

[0146] Fig.12 1200 is a flowchart illustrating another embodiment of hard configuration and / or soft configuration. Flowchart 1200 illustrates a method for a DU, the method comprising: receiving 1202 a semi-static resource configuration C, each semi-static resource configuration C comprising: a time period (T) and a resource set (R) in time and / or frequency, wherein each resource in the resource set is configured as D, U or F, and is also configured as H or S; receiving 1204 information about the MP, Tmin and / or Fmin of the CN; receiving 1206 an indication of which flexible resources are downlink or uplink; receiving 1208 T-AI1 and / or F-AI1 from the PN; transmitting 1210 a second T-AI2 and / or F-AI2 to the CN; using 1212 resources in the resource set for scheduling downlink channels and and / or uplink channels to communicate with the CN and / or the UE, so that: downlink resources and flexible resources indicated by the downlink are used to schedule downlink channels, and uplink resources and flexible resources indicated by the uplink are used to schedule uplink channels, soft resources are used only when they are indicated as available by T-AI1 and / or F-AI1 based on a table specifying joint time-frequency availability, and resources multiplexed with resources indicated as available by T-AI2 and / or F-AI2 meet constraints based on the multi-panel capability of the CN, the minimum guard time and / or the minimum guard band information; and downlink signals are transmitted 1214 on the downlink channel and / or uplink signals are received on the uplink channel.

[0147] In various embodiments, the IAB host CU sends a frequency domain resource configuration to the IAB node DU to implement a non-TDM mode of operation. In some embodiments, lower layer signaling may be used to indicate the availability of resources on the configured soft symbols. Some advantages of such an embodiment may be that it only affects the lower layer specification while the upper layer is compatible with previous versions. As a result, it may be easier to manage resources in a system where some nodes have heterogeneous IAB nodes with different compatibilities. In such an embodiment, frequency domain resource management may be local.

[0148] In some embodiments, resource configuration may be in the time domain (e.g., at symbol level granularity), but control signaling at the physical layer (e.g., L1) may be used to provide an indication of resources in the frequency domain. This may be referred to as a frequency domain availability indication ("F-AI") and may be delivered via a new DCI format (e.g., DCI format 2_6) and / or a control message on a control channel (e.g., PDCCH). The availability indication ("AI") may also be referred to as a time domain availability indication ("T-AI").

[0149] In some embodiments, the F-AI may be a bitmap where each bit indicates availability in one PRB. However, this may use a large overhead, so a smaller granularity may be used. For example, a higher layer configuration may determine the number or group of PRBs as a granularity, such as a resource block group ("RBG"), and then the bitmap in the F-AI may indicate the availability of each RBG.

[0150] In various embodiments, if the granularity at the frequency domain is RBG, it may be noted that the RBG is configured for each node via RRC signaling. In some embodiments, for proper operation, the IAB node N may inform its PN of its RBG size. In some embodiments, the PN may send its RBG size to the N. In one example, the granularity at the frequency domain may be about a different number of PRBs than the RBG size used for scheduling. The frequency domain granularity may be configured and / or determined based on the carrier bandwidth and / or the operating frequency band.

[0151] In some embodiments, the starting PRB and / or RBG and the number of PRBs and / or RBGs may be determined for consecutive F-AIs. In such embodiments, the F-AI message (e.g., DCI format 2_6) may include at least Where M is the number of PRBs and / or RBGs in the active BWP.

[0152] In some embodiments, two different formats of granularity may be defined. In such embodiments, two DCI formats or fields in the DCI may be used to determine which format is used.

[0153] In various embodiments, in addition to DCI signaling, MAC signaling can also facilitate reducing signaling overhead by activating and / or deactivating available frequency resources on top of RRC resource configuration. In such embodiments, MAC CE messages can activate and / or deactivate different frequency resources in a semi-persistent manner. Activation and / or deactivation can be for all CNs, a group of CNs, or one CN. In addition, F-AIDCI can indicate which activated frequency resources are available for each instance.

[0154] In some embodiments, MAC signaling may use a bitmap field to activate and / or deactivate PRBs and / or RBGs. In such embodiments, the F-AI bitmap field indicates whether each of the contiguous partitions activated by MAC signaling is available. Fig.13 An example is illustrated in FIG. Specifically, Fig.13 13 is a block diagram 1300 illustrating one embodiment of F-AI. Block diagram 1300 illustrates RRC signaling 1302, MAC message 1304, and DCI 1306. RRC signaling 1302 configures symbols as soft and the number of PRBs 1308 per RBG is configured as 2. Then, MAC message 1304 activates 3 consecutive partitions of RBG (e.g., inactive partitions—having a value of "0" 1314, activated partitions—activated with a value of "1" 1316). Finally, DCI message 1306 indicates that 2 of the partitions are available (e.g., unavailable partitions—having a value of "0" 1314, available partitions—having a value of "1" 1316). Since there are 3 consecutive partitions activated by MAC message 1304 (e.g., activation bitmap="01101001"), the F-AI bitmap field contains 3 bits (e.g., "101").

[0155] In some embodiments, the MAC message includes more than one bitmap field, each field activating a number of PRBs and / or RBGs. The F-AI bitmap field then indicates whether contiguous or non-contiguous partitions activated by each bitmap field in the MAC message are available. Fig.14 An example is illustrated in FIG. Specifically, Fig.14 1400 is a diagram illustrating another embodiment of activation and indication of F-AI. Block diagram 1400 illustrates RRC signaling 1402, a first MAC message 1404, a second MAC message 1406, and a DCI 1408. RRC signaling 1402 configures symbols as soft and the number of PRBs 1410 per RBG is configured as 2. Then, the first MAC message 1404 and the second MAC message 1406 activate 2 partitions of the RBG, each partition having a separate bitmap field (e.g., inactive partition—having a value 1416 of "0", activated partition—activated with a value 1418 of "1"). Finally, DCI message 1408 indicates that 1 of the partitions is available (e.g., unavailable partition—having a value 1416 of "0", available partition—having a value 1418 of "1"). Since there are 2 partitions activated by the MAC message (eg, Activation Bitmap="01000001" and "00101000"), the F-AI Bitmap field contains 2 bits (eg, "10"). This embodiment provides more flexibility at the expense of greater MAC overhead.

[0156] In various embodiments, the resource granularity of F-AI can be set to S-DL, S-UL and / or SF per slot. In such embodiments, one F-AI field (a bitmap or another format of field) applies to all frequency domain resources on each of the following: 1) all soft downlink symbols in a slot; 2) all soft uplink symbols in a slot; and / or 3) all soft flexible symbols in a slot.

[0157] In some embodiments, since F-AI increases overhead, the following items can be used to reduce overhead: 1) not all soft symbols may be indicated as available in the frequency domain - or for this reason, time slots that may or may not be indicated as available in the frequency domain may be distinguished by configuration - if a time slot is not configured for F-AI, the time slot may be treated similarly to time slots in other configurations; 2) not all time slots have all types of D, U and / or F symbols - therefore, if a time slot does not have a certain type of symbol, the F-AI of that type may be omitted - for example, assuming that the standard specification determines that the F-AI in the DCI will be indicated in the following order: downlink, uplink, flexible - then, if the time slot does not have any uplink symbols, the F-AI will have two fields for downlink and flexible symbols, respectively; and / or 3) a new DCI format may be defined to have one or both of T-AI and F-AI.

[0158] Table 9: Methods for DU

[0159]

[0160]

[0161] Fig.151500 is a flowchart illustrating an embodiment of a compatible dynamic indication. Flowchart 1500 may be for a method for a DU, the method comprising: receiving 1502 a semi-static resource configuration C, each semi-static resource configuration C comprising: a time period (T) and a resource set (R) in the time domain, wherein each resource in the resource set is configured as D, U or F, and is also configured as H or S; receiving 1504 information indicating the MP, Tmin and / or Fmin of the CN; receiving 1506 an indication of which flexible resources are downlink or uplink; receiving 1508 T-AI1 from the PN and / or receiving 1508 F-AI1 from the PN; transmitting 1510 a second T-AI2 to the CN and / or transmitting a second F-AI2 to the CN; using 1512 resources in the resource set for scheduling downlink channel and / or uplink channel for communicating with CN and / or UE, so that: downlink resources and flexible resources indicated by the downlink are used to schedule downlink channels, uplink resources and flexible resources indicated by the uplink are used to schedule uplink channels, soft resources are used only when they are available indicated by T-AI1 and F-AI1 based on the rule of specifying joint time-frequency availability, and resources multiplexed with resources indicated as available by T-AI2 and / or F-AI2 meet constraints based on information indicating the multi-panel capability of CN, minimum guard time and / or minimum guard band; and transmitting 1514 downlink signals on the downlink channel and / or receiving uplink signals on the uplink channel.

[0162] In some embodiments, FDM and / or SDM enhancement between upstream and downstream can be achieved through bandwidth part ("BWP") signaling. In such embodiments, the CU configures and / or activates different BWPs for different nodes so that the transmission and reception in the configured and / or activated BWPs meet the multiplexing constraints of the nodes. In such embodiments: 1) TDM constraints may include Tmin; and / or 2) FDM and / or SDM constraints may include Fmin and / or multi-panel and / or duplex constraints.

[0163] In various embodiments, to configure and / or activate the BWP, the CU may obtain certain information (e.g., as described above) through signaling, configuration, and / or pre-configuration. The configuration and / or pre-configuration information may be received from a node, received from a network, stored on a static memory such as a read-only memory ("ROM"), pre-configured by an operator, and the like. In such embodiments, the information may be provided according to standard specifications and / or methods agreed upon between vendors and / or operators. As may be appreciated, any method described herein may be used in any embodiment described herein to receive information.

[0164] In some embodiments, if the configuration and / or activation is static, resources may be wasted due to dynamic traffic and / or dynamic topology. As can be appreciated, cellular data traffic can be dynamic and bursty, and since aggregate traffic shows self-similar and heavy-tailed properties, it can be expected that aggregate traffic at each IAB node is dynamic and bursty at different time scales. At a smaller time scale, a new file transfer can be an example of an event that triggers a significant load change. At a larger time scale, peak hour city traffic can introduce load changes compared to other times of the day.

[0165] In some embodiments, even if the IAB nodes are static, the IAB system topology may be subject to changes. One reason for a topology change may be a temporary failure of an IAB node. Another reason for a topology change may be an intentional topology change of the network and / or CU to adapt to new traffic conditions.

[0166] In various embodiments, each node may require different amounts of resources at different times, which can be controlled by changing the BWP. In some embodiments, up to four BWPs can be configured for each direction of downlink and uplink, and switching between bandwidth parts is possible through RRC reconfiguration, MAC CE signaling, or DCI.

[0167] In some embodiments, a problem with BWP switching in an IAB system may be that the balance among frequency resources provided for different IAB nodes needs to be maintained by the entity that performs the BWP switching, which may be the IAB host CU in the case of using RRC configuration or the parent IAB-DU in the case of using MAC CE or DCI signaling.

[0168] In various embodiments, the CU may be able to collect appropriate information for multiple IAB nodes and signal BWP switching. In such embodiments, the latency to perform this operation may be too large. In addition, in such embodiments, in order to react to traffic changes more quickly, lower layer signaling may be used and the IAB node may be enabled to control the BWP switching.

[0169] In some embodiments, N may want to switch BWPs in order to communicate with the child IAB-MTs. However, in such embodiments, multiplexing constraints in multi-hop systems may further increase and restrict the choice of IAB nodes in the downstream direction.

[0170] Fig.1616 is a diagram illustrating one embodiment of resource allocation in an IAB system. Diagram 1600 includes a first example 1602, a second example 1604, a third example 1606, and a fourth example 1608. Each of the first example 1602, the second example 1604, the third example 1606, and the fourth example 1608 includes a first node N1 1610, a second node N2 1612, a third node N3 1614, and a fourth node N4 1616.

[0171] exist Fig.16 In the example, N1 is the parent node of N2 and N3, and N4 is the child node of N2. For simplicity, it is assumed that each node shares the same resources between DL BWP and UL BWP, so the resulting Fig.16 Shown as undirected. Even if a node is multi-panel, the panels can be constrained to use non-overlapping resources.

[0172] Therefore, in the first example 1602, if the resource is used for link L12 1618, it cannot be used for link L13 1620 and vice versa. Similarly, if the resource is used for link L12 1618, it cannot be used for link L24 1622 and vice versa. In addition, there is cross link interference between each of N2 and N4 and N3. Therefore, each resource in the time-frequency grid can be used only by one of link L12, L13 and L24, as shown in the second example 1604, the third example 1606 and the fourth example 1608 by the link 1624 used.

[0173] exist Fig.16 In the example, N2 can control the BWP activation of L24 in a way that the active BWP for L24 does not overlap with the active BWP for L12. However, N2 does not have the information of the active BWP on L13 or cannot control the active BWP on L13. Therefore, there is a possibility of excessive CLI from N3 on N2 and / or N4 or vice versa.

[0174] In some embodiments, since the IAB node is not aware of all BWP configurations, multi-hop IAB topologies, CLIs, etc., if the BWP is switched, the IAB node may not be able to meet different constraints. In some embodiments, the IAB host CU may be enabled to send additional information for switching the BWP along with the BWP configuration. By obtaining this information, for example, the IAB node may be able to react to signaling for BWP switching from the parent IAB-DU by signaling for BWP switching to the child IAB-MT. In various embodiments, the IAB node may be able to select a BWPID for the child IAB-MT upon receiving the BWP combination ID from the parent IAB-DU.

[0175] In some embodiments, each IAB node receives a subset of BWPIDs that it can indicate for downstream communications with child IAB-MTs, where the subset is associated with a BWP ID in the upstream direction with a parent IAB-DU. Then, if BWP1 is active in the upstream, the IAB node can activate BWP2 for the downstream only if BWP2 is in the subset of BWP IDs associated with BWP1.

[0176] Fig.17 1700 is a block diagram illustrating one embodiment of a BWP configuration. The diagram 1700 includes a link diagram 1702 including a first node N1 1704, a second node N2 1706, a third node N3 1708, and a fourth node N4 1710. Fig.17 1700 , N1 is the parent node of N2 and N3, and N4 is the child node of N2. In addition, link graph 1702 includes link L12 1712, link L13 1714, and link L24 1716. In addition, block diagram 1700 illustrates BWP 1718 for L13, BWP 1720 for L24, and BWP 1722 for L12 over available bandwidth 1724. BWP 1718, 1720, and 1722 include BWP "0" 1726, "1" 1728, "2" 1730, and "3" 1732.

[0177] exist Fig.17 In the embodiment, each child node of the parent node (eg, each link) is configured with at most 4 BWPs. It can be assumed that the uplink BWP and the downlink BWP occupy the same frequency resources. However, the method is also applicable to asymmetric BWP configurations in the downlink and uplink.

[0178] Can Fig.17 As can be seen in the figure, some BWP combinations work (e.g., (0,0,0), (1,2,1), and (2,3,2)), where the value in each tuple represents the BWP ID for L13, L24, and L12, respectively. However, other BWP combinations may not work (e.g., (1,2,3) results in an overlap between the BWPs for L13 and L12).

[0179] In some embodiments, the IAB node may receive the information shown in Table 10 for BWP activation.

[0180] Table 10

[0181]

[0182] It should be noted that the information in Table 10 may be received through configuration from the CU, which may be included in a BWP configuration message or received in a separate configuration message.

[0183] In some embodiments, through appropriate configuration from the IAB host CU, a balance can be maintained between frequency resources available to different IAB nodes.

[0184] In various embodiments, configuration from the IAB host CU may be expected to meet constraints introduced by capability information such as minimum guard band, multi-panel and / or duplex capabilities, CSI and CLI information, etc. The capability information may be obtained through signaling or other means.

[0185] In certain embodiments, a large number of combinations are possible due to the simple topology and proper configuration. Fig.18 Another example is illustrated that has similar BWP configurations for different links but does not have similar BWP configurations for IAB systems with different topologies.

[0186] Fig.18 1800 is a diagram illustrating another embodiment of a BWP configuration. The diagram 1800 includes a link diagram 1802 including a first node N1 1804, a second node N2 1806, a third node N3 1808, and a fourth node N4 1810. Fig.18 1824, N1 is the parent node of N2 and N3, and N4 is the child node of N2. In addition, link diagram 1802 includes link L12 1812, link L23 1814, and link L34 1816. In addition, block diagram 1800 illustrates BWP 1818 for L12, BWP 1820 for L23, and BWP 1822 for L34 over available bandwidth 1824. BWP 1818, 1820, and 1822 include BWP "0" 1826, "1" 1828, "2" 1830, and "3" 1832.

[0187] In this example, the IAB node receives the information indicated in Table 11 and Table 12 for BWP activation.

[0188] Table 3

[0189]

[0190] Table 4

[0191]

[0192] In some embodiments, some useful combinations are not possible, which may result in wasted bandwidth or reduced flexibility. For example, with the above configuration, the BWP ID combination (0,1,1) is not possible, and if the CU intends to allow this combination, the combination (1,1,2) will not be possible.

[0193] Therefore, in various embodiments, the combination of different BWPs is determined and numbered by a BWP combination ID. This can be performed by the CU and the information can be sent to the IAB node. Then, for BWP activation, the BWP combination ID can be sent in addition to or instead of the BWPID. In some embodiments, the IAB node can efficiently activate the BWP without requiring each IAB node to obtain knowledge of the topology, node capabilities, CLI, etc. that may only be commonly available at the CU.

[0194] According to various embodiments, the IAB node may receive the information found in Table 13.

[0195] Table 13

[0196]

[0197] In Table 13, a BWP combination such as BWP combination ID 0 may be considered a default value, which may then be used to determine a default BWP ID for each of the nodes and / or links.

[0198] It should be noted that not all combinations need to be assigned a combination ID. For example, a combination ID is not assigned for the combination (2,0,1) because it may result in a large waste of bandwidth. The CU is therefore able to maintain a balance between resource utilization, node capabilities, CLI, etc. by defining appropriate BWPs and BWP combinations and without the need to continuously manage BWP activation in a completely centralized manner. The number of combination IDs may determine the bit width of the DCI or MAC control element ("CE") message that carries the BWP combination ID.

[0199] For simplicity, it may be assumed that the link is symmetric between uplink and downlink and the BWP ID may be associated with the link.In some embodiments, the DL BWP and UL BWP of a link between two nodes may not occupy the same resources and the BWP ID may be equivalently associated with a sub-IAB node or more specifically a sub-MT.

[0200] In some BWP-based methods, the IAB node may select a BWP from many BWPs that are configured by the CU and indicated or selected downward by the CU or parent node. However, if the IAB node has multiple options for selecting a BWP, it may consider other criteria for bandwidth portion selection. For example, if the IAB node may try to avoid selecting a downstream BWP that overlaps with an active upstream BWP in resources. If the attempt is unsuccessful and the overlap cannot be avoided, the IAB node may transmit an error message to the parent node and / or to the CU to inform them of the overlap. Then, in response, the parent node may activate a different BWP for the IAB node, or the CU may change the BWP configuration to avoid overlap.

[0201] In various embodiments, the IAB node may need to support a greater number of BWPs than four. The maximum number of BWPs may be a node capability that may be reported for each of the downlink direction and the uplink direction. Therefore, the number of bits in the DCI field for BWP switching may be made flexible or a maximum of four active BWPs may be down-selected by signaling (e.g., MAC CE signaling), and then the DCI field selects one of the down-selected BWPs.

[0202] In some embodiments, if there is a BWP switch via DCI, provisions may be made to accommodate error conditions. Since the DCI may fail to be received by the IAB node, if no communication is received from the parent IAB node for a period of time, an indication is given that a default BWP is to be used. However, the default BWP for the IAB-MT may need to be changed to avoid conflict with the active BWP with the parent IAB-DU. For this purpose, each BWP may be associated with a subset of the BWP IDs in the downstream as a default BWP. Then, if a BWP switch to a new BWP1 occurs via the parent IAB-DU and if the current default BWP for the child IAB-MT is not in the subset of the BWP IDs associated with BWP1, the IAB node may signal the child IAB-MT to change its default BWP to a new BWP2 in the subset.

[0203] In some embodiments, the IAB node may select a BWP for the IAB-DU based on the BWP for the IAB-MT. The BWP may be selected based on minimum overlap with the IAB-MT BWP and / or configured by the PN based on a lookup table and / or determined based on a predefined rule or pattern (e.g., based on the IAB-MT BWP ID and / or the IAB node ID).

[0204] Table 14: Methods used for CU

[0205]

[0206] Table 15: Methods for DU

[0207]

[0208] Fig.191900 is a flowchart illustrating one embodiment of a method based on bandwidth parts. Flowchart 1900 includes a method for a CU, the method including: receiving 1902 or configuring information of topology, routing, CSI, traffic intensity, CLI, MP and / or Fmin; receiving 1904 information indicating bandwidth part capabilities of an IAB node; and sending 1906 configurations C, each configuration C including: a bandwidth part identifier (ID), information of a bandwidth part (B), and a subset of bandwidth part IDs (I) associated with B, such that: the location of the bandwidth part in the frequency domain is determined based on at least one of channel status, traffic intensity and / or cross-link interference; guard bands between bandwidth parts are determined based on information about topology (e.g., what node is the parent node of what other node), multi-panel capabilities and / or minimum guard bands; and the number of bandwidth configurations for an IAB node is constrained by the bandwidth part capabilities of the IAB node.

[0209] Flowchart 1900 includes a method for a DU, the method including: sending 1908 information indicating bandwidth part capabilities of an IAB node; receiving 1910 configurations C, each configuration C including: a bandwidth part identifier (ID), information of a bandwidth part (B), and a subset of bandwidth part IDs (I) associated with B; receiving 1912 a first message indicating a first bandwidth part B1 by indicating the associated bandwidth part identifier ID1; and transmitting 1914 a second message including a second bandwidth part B2 by indicating the associated bandwidth part identifier ID2, wherein ID2 is in the subset of BWP ID I1 associated with B1.

[0210] Table 16: Methods used for CU

[0211]

[0212]

[0213] Table 17: Methods for IAB nodes

[0214]

[0215] Fig. 20is a flow chart 2000 illustrating another embodiment of a bandwidth portion based method. Flowchart 2000 includes a method for a CU, the method including: receiving 2002 or configuring information of topology, routing, CSI, traffic intensity, CLI, MP and / or Fmin; receiving 2004 information indicating bandwidth part capabilities of an IAB node; sending 2006 configurations C, each configuration C including: a bandwidth part identifier ("ID") and information of a bandwidth part (B), such that: a location of the bandwidth part in the frequency domain is determined based on information of channel status, traffic intensity and / or cross-link interference; a guard band between bandwidth parts is determined based on information of topology (e.g., what node is the parent of what other node), multi-panel capabilities and / or minimum guard band; and the number of bandwidth configurations for the IAB node is constrained by the bandwidth part capabilities of the IAB node; and sending 2008 configurations D, each configuration D including: a list of bandwidth part combination identifiers (J) and bandwidth part IDs (I), such that: a bandwidth part associated with the list of bandwidth part IDs satisfies constraints based on cross-link interference, topology (e.g., what node is the parent of what other node), multi-panel capabilities and / or minimum guard band.

[0216] Flowchart 2000 also includes a method for an IAB node, the method including: sending 2010 information about bandwidth part capabilities of the IAB node; receiving 2012 configurations C, each configuration C including: a bandwidth part identifier (ID) and information about a bandwidth part (B); receiving 2014 configurations D, each configuration D including: a bandwidth part combination identifier (J) and a list of bandwidth part IDs (I); receiving 2016 a first message including a first bandwidth part B1 by indicating the associated bandwidth part identifier ID1; receiving 2018 the bandwidth part combination identifier J1; transmitting 2020 a second message including a second bandwidth part B2 by indicating the associated identifier ID2, wherein ID2 is in the list of bandwidth part identifiers included by the bandwidth part configuration having the bandwidth part combination identifier J1; and transmitting 2022 the bandwidth part combination identifier J1.

[0217] In some embodiments, although the explicit indication is simple, it may impose signaling overhead. Therefore, an implicit method may be adopted as an alternative or supplement to the explicit method for indicating frequency domain availability.

[0218] In some embodiments, an example of implicit indication is that unless the IAB node has a full-duplex antenna, it may avoid transmitting or receiving signals on the same resource simultaneously on the same antenna and / or panel. In such embodiments: 1) Single-panel node: the node must avoid transmitting or receiving signals on the same resource simultaneously; 2) Multi-panel node - if the simultaneous operation is to be performed by different antenna panels and cross-panel interference is not an issue, the node must only allow transmission or reception of signals on the same resource.

[0219] In various embodiments, if a PN of an IAB node N schedules communications on resources that are otherwise available to N, the PN may need to mark the scheduled resources as NA and avoid scheduling communications with its own CN or UE on the NA resources.

[0220] In some embodiments, the timing of scheduling may be problematic. In the "typical" case where the PN schedules a channel to communicate with the N in a time slot by transmitting DCI format 1_0 and / or DCI format 1_1 in the PDCCH of the same time slot. In such embodiments, the N does not have enough time to receive the DCI and decode it; recognize that some otherwise available resources are occupied for communication with the PN; and then avoid scheduling its own communication on those resources. Therefore, the PN can transmit the scheduling DCI sufficiently in advance to inform the N in a timely manner.

[0221] In some embodiments, the minimum time that a PN transmits a scheduled DCI in advance is the minimum time that N receives and decodes the DCI and generates its own scheduled DCI. This may be set as a constant by the standard, configuration, or otherwise set as an IAB node capability. This capability may be similar to timeDurationForQCL. However, because timeDurationForQCL may include the time to apply spatial parameters according to the indicated QCL, a new parameter shown in Table 18 may be used. This parameter may be specified by the standard or may be reported by the IAB node as a capability.

[0222] Table 18

[0223]

[0224] In some embodiments, there may be FDM for PDSCH transmissions from PN to N and PDSCH transmissions from N to CN and / or UE. Because N needs sufficient time to receive and decode DCI from PN and then continue to send DCI to CN and / or UE, the higher layer parameter k0 of N may be set to a value not less than a minimum threshold, which is equal to timeDurationForAI of N plus the minimum duration required for N to transmit its own DCI in advance.

[0225] That is: k0_min(PN):=T_min(N)+k0_min(N).

[0226] In this equation, k0_min(PN) is the minimum value of k0 for PDSCH from PN, T_min(N) is the timeDurationForAI of N, and k0_min(N) is the minimum value of k0 for PDSCH from N.

[0227] In one example, there is a 2-hop system PN-N-UE. In this example, PN schedules PDSCH transmission for N, and N schedules PDSCH transmission for UE. Since N can schedule PDSCH transmission for UE in case of k0=0, the setting of k0_min(N):=0 can be made. Then, k0_min(PN) depends only on the minimum decoding time for N, which can be set to a constant T_min(N):=T_min.

[0228] In another example, there is a 3-hop system PN-N-CN-UE. In this example, {PN, N, CN} can schedule PDSCH transmission for {N, CN, UE} respectively. Then, the minimum value of k0 takes the following recursive form: k0_min(PN):=T_min(N)+k0_min(N) and k0_min(N):=T_min(CN)+k0_min(CN).

[0229] Since CN can schedule PDSCH transmission for UEs with k0=0, k0_min(CN) can be set to 0. Therefore: k0_min(N) = T_min(CN), and k0_min(PN) = T_min(N) + T_min(CN)

[0230] For simplicity, assuming that T_min(N):=T_min(CN):=T_min, the following results can be obtained: k0_min(CN):=0, k0_min(N):=T_min and k0_min(PN):=2×=2in.

[0231] This recursive rule can be extended to a larger number of hops. For example, in an m-hop IAB system Nm-.-N1-N0-UE, assuming that all minimum DCI decoding times have the same value, the following exists: k0_min(N0):=0, k0_min(N1):=T_min,..., k0_min(Nm):=m min,...

[0232] A similar approach may be applied to uplink communications or a combination of downlink and uplink communications, where the value of k2 may need to be further considered. The above calculations can be extended to the following.

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

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

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

[0236] PN receives PUSCH transmission from N; N receives PUSCH from CN: k2_min(PN):=T_min(N)+k2_min(N) and k2_min(N):=T_min(CN)+k2_min(CN).

[0237] Table 19 illustrates the method for CU.

[0238] Table 19: Methods for CU

[0239]

[0240] Fig.21 is a flowchart 2100 diagram illustrating an embodiment of an implicit method 2100 for a CU, comprising: receiving 2102 or configuration information including topology, MP and / or timeDurationForAI (T_min) from a set {N} of IAB nodes; and sending 2104 configurations C to {N}, each configuration including: values ​​of k0 and k2, so that: information on which node is the PN or CN of node N in {N} is obtained from the topology information, and the k0 and k2 values ​​of {PN, N, CN} of each node N in {N} follow a specified equation with a T_min value.

[0241] 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 radio signals at frequencies below 6 GHz (e.g., frequency range 1 ("FR1") 0 or above 6 GHz (e.g., frequency range 2 ("FR2") or millimeter wave ("mmWave")). In some embodiments, the antenna panel may include an array of antenna elements. Each antenna element may be connected to hardware such as a phase shifter that enables a control module to apply spatial parameters for transmission and / or reception of signals. The resulting radiation pattern may be referred to as a beam, which may or may not be unimodal and may allow the device to amplify signals transmitted or received from a spatial direction.

[0242] In various embodiments, the antenna panels may or may not be virtualized as antenna ports. The antenna panels may be connected to the baseband processing module via a radio frequency ("RF") chain for each transmission (e.g., egress) and reception (e.g., ingress) direction. The capabilities of the device in terms of the number of antenna panels, their duplex capabilities, their beamforming capabilities, etc. may or may not be transparent to other devices. In some embodiments, the capability information may be transmitted via signaling or may be provided to the device without the need for signaling. If the information is available to other devices, such as a CU, the information may be used for signaling or local decision making.

[0243] In some embodiments, a UE antenna panel may be a physical or logical antenna array comprising a collection 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 having physical UE antennas mapped to logical entities. The mapping of physical UE antennas to logical entities may depend on 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) of the antenna panel that are active for radiating energy may require biasing or powering of the RF chain, which results in current consumption or power consumption associated with the antenna panel in the UE (e.g., including power consumption of power amplifiers and / or low noise amplifiers ("LNA") associated with the antenna elements or antenna ports). The phrase "active for radiating energy" as used herein is not intended to be limited to transmit functionality, but also includes receive functionality. Thus, the antenna elements active for radiating energy may be coupled simultaneously or sequentially to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, or generally to a transceiver to perform its intended functionality. Communication over the active elements of the antenna panel enables the generation of a radiation pattern or beam.

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

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

[0246] In certain embodiments, two antenna ports may be considered to be quasi-co-located ("QCL") if large-scale properties of a channel over which symbols on one antenna port are communicated can be inferred from a channel over which symbols on the other antenna port are communicated. Large-scale properties may include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive ("RX") parameters. Two antenna ports may be quasi-co-located with respect to a subset of large-scale properties, and different subsets of large-scale properties may be indicated by a 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}.

[0247] 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.

[0248] 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 a device. In some embodiments, a physical antenna may be directly mapped 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 group, 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 group 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 process for deriving antenna ports from physical antennas may be specific to the device implementation and transparent to other devices.

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

[0250] In some embodiments, the spatial relationship information associated with the target transmission may indicate a spatial setting 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 using 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 using the same spatial domain transmission filter used for transmission of RS (e.g., UL RS such as SRS). The UE may receive a configuration of multiple spatial relationship information configurations for a serving cell for transmission on the serving cell.

[0251] As described herein, the entity may be referred to as an IAB node. As may be appreciated, embodiments referring to an IAB node may also refer to an IAB host (which is an IAB entity that connects the core network to the IAB network).

[0252] The different steps described herein for different embodiments may be interchanged.

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

[0254] In various embodiments, the configuration may be provided via radio resource control ("RRC") signaling, medium access control ("MAC") signaling, physical layer signaling such as downlink control information ("DCI") messages, and / or other means. Furthermore, in such embodiments, the configuration may include a pre-configured or semi-static configuration provided by a standard, vendor, network, and / or operator. Each parameter value received via a configuration or indication may override a previous value of a similar parameter.

[0255] As can be appreciated, the embodiments described herein may be applicable to wireless relay nodes and / or other types of wireless communication entities.

[0256] It should be noted that the availability indication ("AI") in the time domain may be specified and / or predetermined. Furthermore, the time domain availability indication ("T-AI") may refer to the AI ​​in full or in part as specified and / or predetermined.

[0257] In some embodiments, vendors that manufacture IAB systems and / or devices and operators that deploy IAB systems and / or devices are able to negotiate the capabilities of the systems and / or devices. In some embodiments, some of the information described may require signaling between entities and may be readily available to the devices. For example, by storing information on a storage unit such as a read-only memory ("ROM"), if hardware and / or software of an IAB system and / or device or other entity is created in a network, a proprietary signaling method is used to exchange information, information is provided through configuration and / or pre-configuration, or information is otherwise considered. In this example, the exchange of information can be extended to embodiments in which information is obtained by other methods.

[0258] In various embodiments, the embodiments described herein may vary based on paired spectrum. As used herein, "HARQ-ACK" may collectively represent a positive acknowledgement ("ACK") and a negative acknowledgement ("NACK"). An ACK may mean that a transport block ("TB") was received correctly, whereas a NACK (or NAK) may mean that a TB was received in error.

[0259] Fig. 22is a flow chart illustrating one embodiment of a method 2200 for resource attribute configuration. In some embodiments, the method 2200 is performed by a device such as the remote unit 102. In some embodiments, the method 2200 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.

[0260] In various embodiments, the method 2200 includes receiving 2202 a first configuration for a resource. The first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft, and / or unavailable. In some embodiments, the method 2200 includes receiving 2204 a second configuration for the resource. The second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft, and / or unavailable. In certain embodiments, the method 2200 includes determining 2206 an attribute of the resource based on the time domain attribute and the frequency domain attribute. The attribute is hard, soft, and / or unavailable. In various embodiments, the method 2200 includes, in response to determining that the attribute is soft: determining 2208 whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource. The operation is a downlink transmission and / or an uplink reception.

[0261] In some embodiments: determining the attribute as hard in response to the time domain attribute being hard and the frequency domain attribute being hard; determining the attribute as soft in response to the time domain attribute being soft and the frequency domain attribute being unavailable; or the time domain attribute being unavailable and the frequency domain attribute being soft; and determining the attribute as unavailable in response to the time domain attribute being unavailable or the frequency domain attribute being unavailable. In some embodiments: determining the attribute as hard in response to the time domain attribute being hard; or the time domain attribute being soft and the frequency domain attribute being hard; determining the attribute as soft in response to the time domain attribute being soft and the frequency domain attribute being soft; and determining the attribute as unavailable in response to the time domain attribute being unavailable; or the time domain attribute being soft and the frequency domain attribute being unavailable. In various embodiments, determining that the resource is indicated as available includes determining that the time domain availability indication, the frequency domain availability indication, or a combination thereof indicates that the resource is available.

[0262] In one embodiment, the time domain availability indication, the frequency domain availability indication, or a combination thereof is received no later than a time threshold, the time threshold being determined based on an ability to perform decoding of the first control message, encoding of the second control message, transmitting the second control message, or some combination thereof. In certain embodiments, the method 2200 further includes, in response to determining that the attribute is hard, performing an operation on the resource. In some embodiments, the method 2200 further includes, in response to determining that the attribute is unavailable, refraining from performing an operation on the resource.

[0263] Fig.23 is a flow chart illustrating another embodiment of a method 2300 for resource attribute configuration. In some embodiments, the method 2300 is performed by a device such as the remote unit 102. In some embodiments, the method 2300 may be performed by a processor running program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0264] In various embodiments, the method 2300 includes receiving 2302 a configuration for a symbol. The configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft, and / or unavailable. In some embodiments, the method 2300 includes receiving 2304 a first control message corresponding to a set of frequencies. In various embodiments, the method 2300 includes determining 2306 a second attribute of a resource on the symbol based on the first attribute and the first control message. The second attribute is hard, soft, and / or unavailable. In some embodiments, the method 2300 includes, in response to determining that the second attribute is soft: determining 2308 whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource. The operation is a downlink transmission and / or an uplink reception.

[0265] In some embodiments: in response to the first attribute being hard, determining the second attribute as hard; in response to the first attribute being soft and the frequency of the resource being in a set of frequencies, determining the second attribute as soft; and in response to the first attribute being unavailable, determining the second attribute as unavailable. In some embodiments, the method 2300 further includes, in response to determining that the second attribute is hard, performing an operation on the resource. In various embodiments, the method 2300 further includes, in response to determining that the second attribute is unavailable, refraining from performing an operation on the resource.

[0266] In one embodiment, a method includes: receiving a first configuration for a resource, wherein the first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft, unavailable, or some combination thereof; receiving a second configuration for the resource, wherein the second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft, unavailable, or some combination thereof; determining an attribute of the resource based on the time domain attribute and the frequency domain attribute, wherein the attribute is hard, soft, unavailable, or some combination thereof; and, in response to determining that the attribute is soft: determining whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource, wherein the operation is a downlink transmission, an uplink reception, or a combination thereof.

[0267] In certain embodiments: determining an attribute as hard in response to the time domain attribute being hard and the frequency domain attribute being hard; determining an attribute as soft in response to: the time domain attribute being soft and the frequency domain attribute being unavailable; or the time domain attribute being unavailable and the frequency domain attribute being soft; and determining an attribute as unavailable in response to the time domain attribute being unavailable or the frequency domain attribute being unavailable.

[0268] In some embodiments: determining an attribute as hard in response to: the time domain attribute is hard; or the time domain attribute is soft and the frequency domain attribute is hard; determining an attribute as soft in response to the time domain attribute is soft and the frequency domain attribute is soft; and determining an attribute as unavailable in response to: the time domain attribute is unavailable; or the time domain attribute is soft and the frequency domain attribute is unavailable.

[0269] In various embodiments, determining that the resource is indicated as available includes determining that a time domain availability indication, a frequency domain availability indication, or a combination thereof indicates that the resource is available.

[0270] In one embodiment, a time domain availability indication, a frequency domain availability indication, or a combination thereof is received no later than a time threshold, the time threshold being determined based on an ability to perform decoding of a first control message, encoding of a second control message, transmission of a second control message, or some combination thereof.

[0271] In some embodiments, the method further includes, in response to determining that the attribute is hard, performing an operation on the resource.

[0272] In some embodiments, the method further includes, in response to determining that the attribute is unavailable, refraining from performing the operation on the resource.

[0273] In one embodiment, an apparatus includes: a receiver, which: receives a first configuration for a resource, wherein the first configuration includes a first parameter indicating a time domain attribute associated with the resource, and the time domain attribute is hard, soft, unavailable, or some combination thereof; and receives a second configuration for the resource, wherein the second configuration includes a second parameter indicating a frequency domain attribute associated with the resource, and the frequency domain attribute is hard, soft, unavailable, or some combination thereof; and a processor, which: determines an attribute of the resource based on the time domain attribute and the frequency domain attribute, wherein the attribute is hard, soft, unavailable, or some combination thereof; and, in response to determining that the attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is a downlink transmission, an uplink reception, or a combination thereof.

[0274] In certain embodiments: determining an attribute as hard in response to the time domain attribute being hard and the frequency domain attribute being hard; determining an attribute as soft in response to: the time domain attribute being soft and the frequency domain attribute being unavailable; or the time domain attribute being unavailable and the frequency domain attribute being soft; and determining an attribute as unavailable in response to the time domain attribute being unavailable or the frequency domain attribute being unavailable.

[0275] In some embodiments: determining an attribute as hard in response to: the time domain attribute is hard; or the time domain attribute is soft and the frequency domain attribute is hard; determining an attribute as soft in response to the time domain attribute is soft and the frequency domain attribute is soft; and determining an attribute as unavailable in response to: the time domain attribute is unavailable; or the time domain attribute is soft and the frequency domain attribute is unavailable.

[0276] In various embodiments, the processor determining that the resource is indicated as available includes the processor determining that a time domain availability indication, a frequency domain availability indication, or a combination thereof indicates that the resource is available.

[0277] In one embodiment, a time domain availability indication, a frequency domain availability indication, or a combination thereof is received no later than a time threshold, the time threshold being determined based on an ability to perform decoding of a first control message, encoding of a second control message, transmission of a second control message, or some combination thereof.

[0278] In some embodiments, the processor, in response to determining that the attribute is hard, performs an operation on the resource.

[0279] In some embodiments, the processor refrains from performing the operation on the resource in response to determining that the attribute is unavailable.

[0280] In one embodiment, a method includes: receiving a configuration for a symbol, wherein the configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft, unavailable, or some combination thereof; receiving a first control message corresponding to a set of frequencies; determining a second attribute of a resource on the symbol based on the first attribute and the first control message, wherein the second attribute is hard, soft, unavailable, or some combination thereof; and, in response to determining that the second attribute is soft: determining whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performing an operation on the resource, wherein the operation is a downlink transmission, an uplink reception, or a combination thereof.

[0281] In some embodiments: in response to the first attribute being hard, the second attribute is determined to be hard; in response to the first attribute being soft and the frequency of the resource being in a set of frequencies, the second attribute is determined to be soft; and in response to the first attribute being unavailable, the second attribute is determined to be unavailable.

[0282] In some embodiments, the method further includes, in response to determining that the second attribute is hard, performing an operation on the resource.

[0283] In various embodiments, the method further includes, in response to determining that the second attribute is unavailable, refraining from performing the operation on the resource.

[0284] In one embodiment, an apparatus includes: a receiver, which: receives a configuration for a symbol, wherein the configuration includes a parameter indicating a first attribute associated with the symbol, and the first attribute is hard, soft, unavailable, or some combination thereof; and receives a first control message corresponding to a set of frequencies; and a processor, which: determines a second attribute of a resource on the symbol based on the first attribute and the first control message, wherein the second attribute is hard, soft, unavailable, or some combination thereof; and, in response to determining that the second attribute is soft: determines whether the resource is indicated as available; and, in response to determining that the resource is indicated as available, performs an operation on the resource, wherein the operation is a downlink transmission, an uplink reception, or a combination thereof.

[0285] In some embodiments: in response to the first attribute being hard, the second attribute is determined to be hard; in response to the first attribute being soft and the frequency of the resource being in a set of frequencies, the second attribute is determined to be soft; and in response to the first attribute being unavailable, the second attribute is determined to be unavailable.

[0286] In some embodiments, the processor, in response to determining that the second attribute is hard, performs an operation on the resource.

[0287] In various embodiments, the processor refrains from performing the operation on the resource in response to determining that the second attribute is unavailable.

[0288] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.

Claims

1. An apparatus for wireless communication, the apparatus comprising an integrated access and backhaul (IAB) node, the apparatus further comprising: include: processor; as well as a memory coupled to the processor, the processor being configured to cause the apparatus to: receiving a first configuration associated with a symbol, wherein the first configuration includes a first indication of whether the symbol is hard, soft, or unusable; receiving a second configuration associated with a set of resource blocks (RBs) on the symbol, wherein the second configuration includes a second indication of whether the set of RBs is hard, soft, or unavailable; An IAB distribution unit (IAB-DU) for the IAB node determines whether to perform communication on the set of RBs in the symbol based at least in part on the first indication and the second indication, wherein the communication is transmission, reception, or a combination thereof.

2. The device according to claim 1, in, The processor is configured to further cause the apparatus to: receiving a downlink control indication (DCI) or a medium access control (MAC) including a third indication, the third indication indicating availability or unavailability; as well as For the IAB-DU, it is further determined based on the third indication whether to perform communication on the RB set in the symbol.

3. The device according to claim 2, in, In response to the following situation, determining to perform communication on the set of RBs in the symbol: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates that it is available.

4. The device according to claim 2, in, In response to the following situation, determining not to perform communication on the set of RBs in the symbol: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates unavailable.

5. The device according to claim 2, in, The MAC includes a bitmap field associated with a plurality of RB sets including the RB set, and a bit in the bitmap field indicates whether the RB set is available.

6. The device according to claim 2, in, The DCI includes an availability indication DCI message from a parent node of the IAB node.

7. The device according to claim 1, in, The first configuration is a time domain configuration.

8. The device according to claim 1, in, The second configuration is a frequency domain configuration.

9. A method at an integrated access and backhaul (IAB) node, the method include: receiving a first configuration associated with a symbol, wherein the first configuration includes a first indication of whether the symbol is hard, soft, or unusable; receiving a second configuration associated with a set of resource blocks (RBs) on the symbol, wherein the second configuration includes a second indication of whether the set of RBs is hard, soft, or unavailable; an IAB distribution unit (IAB-DU) for the IAB node, determining whether to perform communication on the set of RBs in the symbol based at least in part on the first indication and the second indication, The communication is transmission, reception or a combination thereof.

10. The method according to claim 9, further comprising: include: receiving a downlink control indication (DCI) or a medium access control (MAC) including a third indication, the third indication indicating availability or unavailability; as well as For the IAB-DU, it is further determined based on the third indication whether to perform communication on the RB set in the symbol.

11. The method according to claim 10, in, The IAB-DU is determined to perform communication on the set of RBs in the symbol in response to: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates that it is available.

12. The method according to claim 10, in, The IAB-DU is determined not to be communicated on the set of RBs in the symbol in response to: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates unavailable.

13. The method according to claim 10, in, The MAC includes a bitmap field associated with a plurality of RB sets including the RB set, and a bit in the bitmap field indicates whether the RB set is available.

14. The method according to claim 9, in, The first configuration is a time domain configuration.

15. The method according to claim 9, in, The second configuration is a frequency domain configuration.

16. An apparatus for wireless communication, the apparatus comprising an integrated access and backhaul (IAB) node, the apparatus further comprising: include: processor; as well as a memory coupled to the processor, the processor being configured to cause the apparatus to: receiving a time domain configuration associated with a symbol, wherein the time domain configuration includes a first indication of whether the symbol is hard, soft, or unusable; receiving a frequency domain configuration associated with a set of resource blocks (RBs) on the symbol, wherein the frequency domain configuration includes a second indication of whether the set of RBs is hard, soft, or unavailable; receiving a downlink control indication (DCI) or a medium access control (MAC) including a third indication, the third indication indicating availability or unavailability; as well as An IAB distribution unit (IAB-DU) for the IAB node determines whether to perform transmission, reception, or a combination thereof on the RB set in the symbol based on the first indication, the second indication, and the third indication.

17. The device according to claim 16, in, The IAB-DU is determined to perform transmission, reception, or a combination thereof on the set of RBs in the symbol in response to: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates that it is available.

18. The device according to claim 16, in, In response to the following situation, the IAB-DU is determined not to be transmitted, received, or a combination thereof on the RB set in the symbol: The first indication indicates that the symbol is soft; The second indication indicates that the RB set is soft; as well as The third indication indicates unavailable.