KR20230047863A - Method and apparatus for multiplexing of integrated access and backhaul node in wireless communication system - Google Patents

Abstract

The present invention relates to a communication technique that combines a 5G communication system with an IoT technology to support a higher data transmission rate after a 4G system and a system thereof. The present invention can be applied to intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on a 5G communication technology and an IoT-related technology. According to an embodiment of the present invention, provided are a transmitting/receiving method through a beam in an integrated access and backhaul (IAB) node and a device thereof.

Description

Apparatus and method for beam operation of IAB node in wireless communication system

The present disclosure relates to a wireless communication system, and specifically, to a method and apparatus for transmitting and receiving through a beam in an integrated access and backhaul (IAB) node.

Efforts are being made to develop an improved 5th generation (5G) communication system or a pre-5G communication system in order to meet the growing demand for wireless data traffic after the commercialization of a 4G (4th generation) communication system. For this reason, the 5G communication system or pre-5G communication system has been called a Beyond 4G Network communication system or a Post LTE system.

In order to achieve a high data rate, the 5G communication system is being considered for implementation in a mmWave band (eg, a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, to improve the network of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and reception interference cancellation etc. are being developed. In addition, in the 5G system, Advanced Coding Modulation (ACM) methods such as FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding) and advanced access technology FBMC (Filter Bank Multi Carrier) ), Non Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network in which humans create and consume information to an Internet of Things (IoT) network in which information is exchanged and processed between distributed components such as things. IoE (internet of everything) technology, in which IoT technology is combined with big data processing technology through connection with a cloud server, etc., is also emerging. In order to implement IoT, technical elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, sensor networks for connection between objects and machine to machine , M2M), and machine type communication (MTC) technologies are being studied. In an IoT environment, an intelligent Internet technology (IT) service that creates new values in human life by collecting and analyzing data generated from connected objects may be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna, and 5G communication technology There is. The application of the cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 5G technology and IoT technology.

Recently, various studies have been conducted to utilize integrated access and backhaul (IAB) technology, and thus, improvement of dual access of IAB nodes is also required.

An embodiment of the present invention is a method of operating a beam of an IAB node when the IAB node supports a multiplexing method (time division multiplexing (TDM), frequency division multiplexing (FDM), and/or spatial division multiplexing (SDM)), and IAB operation method accordingly Its purpose is to provide a node operating method and its device.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

The present invention for solving the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

An embodiment of the present invention may provide a method for operating a beam of an IAB node when the IAB node supports a multiplexing scheme (TDM or FDM and/or SDM), a method for operating the IAB node accordingly, and an apparatus therefor.

The effects obtainable in the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

1 illustrates an example of a wireless communication system in which an integrated access and backhaul (IAB) node is operated according to an embodiment of the present invention.
2 schematically illustrates an example in which resources are multiplexed in a time domain and a frequency domain between an access link and a backhaul link of an IAB node according to an embodiment of the present invention.
3 illustrates an example in which resources are multiplexed in the time domain between an access link and a backhaul link in an IAB node according to an embodiment of the present invention.
4 illustrates an example in which resources are multiplexed in frequency and spatial domains between an access link and a backhaul link in an IAB node according to an embodiment of the present invention.
5 schematically illustrates the structure of an IAB node according to an embodiment of the present invention.
6 illustrates a communication method for simultaneous transmission and reception between a mobile termination (MT) and a distributed unit (DU) in an IAB node in a wireless communication system according to an embodiment of the present invention.
7 illustrates a DU resource type for supporting frequency division multiplexing (FDM) of an IAB node and an operation of an IAB node in a wireless communication system according to an embodiment of the present invention.
8 illustrates a DU beam limiting method for supporting spatial division multiplexing (SDM) of an IAB node and an operation of an IAB node in a wireless communication system according to an embodiment of the present invention.
9 illustrates an MT beam recommendation method and operation of an IAB node for supporting spatial division multiplexing (SDM) of an IAB node in a wireless communication system according to an embodiment of the present invention.
10(a) illustrates an operation of a base station/parent IAB node in a wireless communication system according to an embodiment of the present invention.
10(b) illustrates an operation of an IAB node, which is a self IAB node, in a wireless communication system according to an embodiment of the present invention.
11 illustrates a configuration of a terminal according to an embodiment of the present invention.
12 illustrates a configuration of a base station according to an embodiment of the present invention.
13 illustrates the configuration of an IAB node according to an embodiment of the present invention.

Terms used in the present disclosure are only used to describe a specific embodiment, and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly dictates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by one of ordinary skill in the art described in this disclosure. Among the terms used in the present disclosure, terms defined in general dictionaries may be interpreted as having the same or similar meanings as those in the context of the related art, and unless explicitly defined in the present disclosure, ideal or excessively formal meanings. not be interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware access method is described as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, various embodiments of the present disclosure do not exclude software-based access methods.

Terms related to signals and messages (e.g., radio resource control (RRC) signaling, message, signal, non-access stratum (NAS) message, NAS signaling) used in the following description refer to LTE (3rd Generation Partnership Project (3GPP)) Although described based on terms defined in the long term evolution (NR) or new radio (NR) standards, other terms having equivalent technical meanings may be used. In addition, terms referring to network entities used in the following description (e.g., base station, terminal, communication node, radio node, radio unit, network node) ), master node (MN), secondary node (SN), transmission/reception point (TRP), DU (digital unit), RU (radio unit), RAN node, eNB, gNB, Access and mobility management functions (AMFs), DUs, RUs, CUs, and the like are described for description of embodiments. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

In addition, in the present disclosure, various embodiments are described using terms used in some communication standards (eg, LTE and NR defined by 3GPP). The 3GPP mobile communication system dealt with herein may include both 4th generation (4G, hereinafter referred to as LTE()) and 5th generation (hereinafter referred to as 5G, hereinafter referred to as NR). However, embodiments of the present disclosure are not only 3GPP mobile communication systems, but also other communication systems. Also, it can be easily modified and applied.

In addition, in the present disclosure, the expression of more than or less than is used to determine whether a specific condition is satisfied or fulfilled, but this is only a description to express an example and excludes more or less description. It's not about doing it. Conditions described as 'above' may be replaced with 'exceeds', conditions described as 'below' may be replaced with 'below', and conditions described as 'above and below' may be replaced with 'above and below'.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. At this time, it should be noted that the same components in the accompanying drawings are indicated by the same reference numerals as much as possible. In addition, detailed descriptions of well-known functions and configurations that may obscure the subject matter of the present disclosure will be omitted.

In describing the embodiments in this specification, descriptions of technical contents that are well known in the art to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary description.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is assigned to the same or corresponding component.

Advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, only the present embodiments make the disclosure of the present disclosure complete, and the common knowledge in the art to which the present disclosure belongs It is provided to fully inform the possessor of the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, as an example, '~unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card.

The wireless communication system has moved away from providing voice-oriented services in the early days and, for example, 3GPP's high speed packet access (HSPA), LTE (long term evolution or E-UTRA (evolved universal terrestrial radio access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's high rate packet data (HRPD), UMB (ultra mobile broadband), and IEEE's 802.16e. evolving into a communication system.

As a representative example of the broadband wireless communication system, in an LTE system, an orthogonal frequency division multiplexing (OFDM) method is employed in downlink (DL), and single carrier frequency division multiplexing (SC-FDMA) in uplink (UL) access) method. Uplink refers to a radio link in which a terminal, user equipment (UE) or mobile station (MS) transmits data or control signals to a base station (eNode B or base station (BS)), and downlink refers to a base station It refers to a radio link that transmits data or control signals to this terminal. The multiple access scheme as described above distinguishes data or control information of each user by allocating and operating time-frequency resources to carry data or control information for each user so as not to overlap each other, that is, to establish orthogonality. do.

As a future communication system after LTE, that is, a 5G (or NR) communication system, since it should be able to freely reflect various requirements of users and service providers, services that satisfy various requirements at the same time must be supported. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra reliable low latency communication (URLLC), etc. there is

eMBB aims to provide a data transmission rate that is more improved than that supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, an eMBB must be able to provide a peak data rate of 20 Gbps in downlink and a peak data rate of 10 Gbps in uplink from the perspective of one base station. In addition, the 5G communication system should provide a maximum transmission rate and, at the same time, an increased user perceived data rate of the terminal. In order to satisfy these requirements, improvements in various transmission and reception technologies including a more advanced multi-input multi-output (MIMO) transmission technology are required. In addition, while signals are transmitted using a maximum 20MHz transmission bandwidth in the 2GHz band currently used by LTE, the 5G communication system uses a frequency bandwidth wider than 20MHz in a frequency band of 3 to 6GHz or 6GHz or higher to meet the requirements of the 5G communication system. data transfer rate can be satisfied.

At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires access support for large-scale terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal cost. Since the IoT is attached to various sensors and various devices to provide a communication function, it must be able to support a large number of terminals (eg, 1,000,000 terminals/km ² ) in a cell. In addition, terminals supporting mMTC are likely to be located in shadow areas that are not covered by cells, such as the basement of a building due to the nature of the service, so they require wider coverage than other services provided by the 5G communication system. A terminal supporting mMTC must be configured as a low-cost terminal, and since it is difficult to frequently replace a battery of the terminal, a very long battery life time such as 10 to 15 years is required.

Finally, in the case of URLLC, it is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmaned aerial vehicles, remote health care, emergency situations. A service used for emergency alert or the like may be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC needs to satisfy an air interface latency of less than 0.5 milliseconds, and at the same time has a requirement of a packet error rate of 10 ^-5 or less. Therefore, for a service supporting URLLC, the 5G system must provide a smaller transmit time interval (TTI) than other services, and at the same time, a design that allocates wide resources in the frequency band to secure the reliability of the communication link. matter is required

The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters may be used between services in order to satisfy different requirements of each service.

A term used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network entities, and a term referring to various types of identification information. Etc. are illustrated for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings may be used.

For convenience of description below, the present invention uses terms and names defined in LTE and NR standards, which are the latest standards defined by The 3rd Generation Partnership Project (3GPP) among currently existing communication standards. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards. In particular, the present invention can be applied to 3GPP NR (5th generation mobile communication standard).

In the 5G system, as the frequency band increases (eg, 6 GHz or higher band, especially mmWave band), when the base station transmits and receives data to the terminal, coverage may be limited due to attenuation of the propagation path. The problem of the above coverage limitation can be solved by densely arranging a plurality of relays (or relay nodes) between the base station and the propagation path of the terminal, but accordingly, to install an optical cable for backhaul connection between the relay and the relay The cost problem becomes serious. Therefore, instead of installing optical cables between relays, wideband radio frequency resources available in mmWave are used to transmit and receive backhaul data between relays, thereby solving the cost problem of installing optical cables and using the mmWave band more efficiently.

As described above, a technology for transmitting and receiving backhaul data from a base station and finally transmitting and receiving access data to a terminal via at least one relaying node is called integrated access and backhaul (IAB). A relay node that transmits and receives data from a base station using a backhaul is called an IAB node. At this time, the base station (or may be referred to as gNB, IAB donor, etc.) is composed of a central unit (CU) and a distributed unit (DU), and the IAB node is a distributed unit (DU) and an MT ( mobile termination). The CU manages DUs of all IAB nodes connected to the base station through multi-hop.

The IAB node may use different frequency bands or use the same frequency band when receiving backhaul data from the base station and transmitting access data to the terminal, and when receiving access data from the terminal and transmitting backhaul data to the base station. may be When receiving access data and transmitting backhaul data or using the same frequency band when transmitting access data and receiving backhaul data, the IAB node has a half duplex constraint. Therefore, as a method for reducing the transmission and reception delay due to the unidirectional transmission and reception characteristics of the IAB node, the IAB node transmits backhaul data (eg, a parent IAB node, an IAB node operating as a relay node, and a self) when transmitting a signal. Assuming a situation in which (child) nodes are connected through a wireless backhaul link, uplink data from the MT of the IAB node to the DU of the parent IAB node and downlink data from the DU of the IAB node to the MT of the child IAB node) and the terminal Access data (downlink data from the IAB node to the terminal) may be multiplexed (eg, frequency-division multiplexing (FDM) and/or spatial-division multiplexing (SDM)). A parent node and child for the IAB node (child) node relationship may refer to 3GPP standard TS 38.300 section 4.7 Integrated Access and Backhaul.

In addition, even when the IAB node receives a signal, backhaul data (downlink data from the DU of the parent IAB node to the MT of the IAB node and uplink data from the MT of the child IAB node to the DU of the IAB node) and access data from the terminal (uplink data from the terminal to the IAB node) may be multiplexed (FDM and/or SDM).

At this time, when the multiplexing method (TDM or FDM and / or SDM) is supported, the beam operation method of the IAB node for cooperation between the IAB node and the parent IAB node, and the use of beams during simultaneous transmission and reception through DU and MT of the IAB node It may be necessary to standardize the operation of DUs and MTs of IAB nodes. Hereinafter, in embodiments of the present disclosure, a method of operating a beam of the IAB node when supporting the multiplexing method (TDM or FDM and/or SDM) and an operation of the IAB node according to the method are provided.

1 is a diagram illustrating an example of a wireless communication system in which an IAB node operates according to an embodiment of the present invention.

Referring to FIG. 1, gNB 101 is a typical base station (eg, eNB or gNB) and may be referred to as a gNB, eNB, base station, donor base station, or donor IAB in the present disclosure. . An IAB donor may refer to an entity serving an IAB node so that an IAB node described later is connected to a core network (eg, an evolved packet core (EPC) or 5G core (5GC)). The IAB donor, as a base station, is a network infrastructure that provides wireless access to terminals. The base station 101 has coverage defined as a certain geographical area based on a distance over which signals can be transmitted. Hereinafter, the term 'coverage' used may refer to a service coverage area in the base station 110 . The base station 101 may cover one cell or multiple cells. Here, a plurality of cells may be distinguished by a supported frequency and a covered sector area.

In addition to the gNB, the base station 101 serving as an IAB donor includes an 'access point (AP)', an 'eNodeB (evolved node B, eNB)', a '5G node (5th generation node)', '5G NodeB (NB)', 'gNB (next generation node B)', 'wireless point', 'transmission/reception point (TRP)', or equivalent technical meaning Branches may be referred to by other terms. In addition, in the case of distributed deployment, the base station 101 includes a centralized unit (CU), a distributed unit (DU), a digital unit (DU), and a radio unit (RU). ), remote radio head (RRH), or other terms having equivalent technical meaning. In FIG. 1 , the IAB donor is described as a gNB 101 as one entity, but may be implemented as distributed entities according to embodiments. For example, the IAB donor may function by being classified into CU and DU.

IAB node #1 (111) and IAB node #2 (121) are IAB nodes that transmit and receive signals through a backhaul link. The IAB nodes 111 and 112 are network entities for wireless access and backhaul connections, and may be deployed to increase coverage. Since the backhaul connection is configured wirelessly, the coverage of the gNB 101, which is an IAB donor, can be increased without installing a wired network. For example, the IAB node #1 111 may be placed around the gNB 101, which is an IAB donor (eg, within a wireless communication radius). IAB node #1 (111) is connected to gNB (101), an IAB donor, through a backhaul link to perform communication, and may perform communication with terminal 2 (112) through a wireless link. In addition, the IAB node #2 121 may be disposed around another node, IAB node #1 111 (eg, within a wireless communication radius). Through the placement of each IAB node, increased coverage can be achieved in high-frequency bands (eg, millimeter wave bands). Each IAB node may perform the function of a relay technique or repeater as well as a multi-hop.

The IAB node may be connected to a parent node and a child node. For example, from the point of view of IAB node #1 (111), gNB (101) will be referred to as a parent node, and IAB node #2 (121) or terminal 2 (112) will be referred to as a child node. can In addition, from the point of view of IAB node #2 (121), IAB node #1 (111) may be referred to as a parent node, and terminal 3 (122) may be referred to as a child node. A link between an IAB node and a parent node is referred to as a parent link, and a link between an IAB node and a child node is referred to as a child link.

A terminal (eg, terminal 1 (102), terminal 2 (112), terminal 3 (122)) is a device used by a user and communicates with the base station 101 or the IAB nodes 111 and 121 through a radio channel. carry out Hereinafter, a radio channel between the terminals 102, 112, and 122 and the base station 101 or between the terminals 102, 112, and 122 and the IAB nodes 111 and 121 is referred to as an access link. In the present disclosure, the terminals 102, 112, and 122 are not only electronic devices used by general users, but also, in some cases, devices that perform machine type communication (MTC) that can be operated without user involvement. can include The terminals 102, 112, and 122 include 'user equipment (UE)', 'mobile station', 'subscriber station', and 'customer premises equipment' other than terminals. , CPE)', 'remote terminal', 'wireless terminal', 'electronic device', or 'vehicle terminal', 'user device' Or it may be referred to as another term having an equivalent technical meaning.

Terminal 1 (102) can transmit and receive access data through the gNB (101) and the access link (103). IAB node # 1 (111) may transmit and receive backhaul data through the gNB (101) and the backhaul link (104). Terminal 2 (112) may transmit and receive access data through the IAB node #1 (111) and the access link (113). The IAB node #2 121 may transmit and receive backhaul data with the IAB node #1 111 through the backhaul link 114. Therefore, IAB node #1 (111) is a parent IAB node of IAB node #2 (121), also referred to as a parent IAB (parent IAB) node, and IAB node #2 (121) is a child of IAB node #1 (111). It is an IAB node, and is referred to as a child IAB (Child IAB) node. Terminal 3 (122) transmits and receives access data (123) with IAB node #2 (121) through an access link (123). In FIG. 1 , the backhaul links 104 and 114 may use wireless backhaul links.

Hereinafter, the present disclosure describes measurement of an IAB node or a donor gNB of a UE.

For the purpose of performing measurement on a donor gNB or IAB node in a neighborhood where device 2 112 or device 3 122 is not a serving IAB node, donor gNB and IAB nodes Coordination of the liver may be necessary. That is, the donor gNB matches the measurement resource of the IAB node with an even number of hop orders, or the measurement resource of an IAB node with an odd number of hop orders. ), it is possible to minimize resource waste for the UE to perform measurement of a neighboring IAB node or IAB base station. Configuration information for the terminal to measure a synchronization signal block (SSB)/physical broadcast channel (PBCH) or channel state information reference signal (CSI-RS) for measurement of a neighboring IAB node from a serving IAB node or base station. may be received through higher layer signaling (higher layer signal, eg: radio resource control (RRC) signaling). If the UE is configured for measurement of a neighboring base station through SSB/PBCH, the UE has a measurement resource of an IAB node having an even number of hop orders or an odd number of hop orders ), at least two SMTCs (SSB/PBCH measurement timing configurations) per frequency can be set for each measurement resource of the IAB node having. The terminal receiving the configuration information may perform measurement of an IAB node having an even number of hop orders in one SMTC, and having an odd number of hop orders in another SMTC. Measurement of the IAB node may be performed.

Hereinafter, the present disclosure describes measurements for an IAB node or other IAB nodes of donor gNBs.

For the purpose of an IAB node performing measurement on a donor gNB or IAB node in another neighborhood, coordination between donor gNBs and IAB nodes may be required. That is, the donor gNB matches the measurement resource of the IAB node with an even number of hop orders, or the measurement resource of an IAB node with an odd number of hop orders. ), it is possible to minimize resource waste for one IAB node to perform measurement of a neighboring IAB node or IAB base station. One IAB node signals, from the serving IAB node or base station, configuration information to measure SSB/PBCH or channel status information-reference signal (CSI-RS) for measurement of neighboring IAB nodes (e.g., upper layer signaling). RRC signaling). If an IAB node receives measurement of a neighboring base station through SSB/PBCH, the IAB node has a measurement resource of an IAB node having an even number of hop orders or an odd number of hop orders ( At least two SSB/PBCH measurement timing configurations (SMTCs) per frequency may be set for each measurement resource of an IAB node having a hop order. The IAB node receiving the setting may perform measurement of an IAB node having an even number of hop orders in one SMTC, and having an odd number of hop orders in another SMTC Measurement of the IAB node may be performed.

2, 3, It will be described in more detail with reference to FIG. 4 .

2 schematically illustrates an example in which resources are multiplexed between an access link and a backhaul link in an IAB node according to an embodiment of the present invention.

Referring to FIG. 2, (a) of FIG. 2 illustrates an example in which resources are multiplexed in the time domain between an access link and a backhaul link in an IAB node. 2(b) shows an example in which resources are multiplexed in the frequency domain between an access link and a backhaul link in an IAB node.

2(a) shows that a backhaul link 203 between a base station and an IAB node or between an IAB node and an IAB node and an access link 202 between a base station and a terminal or between an IAB node and a terminal within a radio resource 201 are time domain multiplexed ( An example of time domain multiplexing (TDM) is shown.

As shown in (a) of FIG. 2, when resources are multiplexed in the time domain between the access link and the backhaul link in the IAB node, data is transmitted and received between the base station and the IAB nodes in the time domain in which the base station or the IAB node transmits and receives data to the terminal. I never do that. In addition, when resources are multiplexed in the time domain between the access link and the backhaul link in the IAB node, the base station or the IAB node does not transmit and receive data to the terminal in the time domain in which data is transmitted and received between the base station and the IAB nodes.

2 (b) shows that a backhaul link 213 between a base station and an IAB node or between an IAB node and an IAB node and an access link 212 between a base station and a terminal or between an IAB node and a terminal within a radio resource 211 are frequency domain multiplexed ( An example of frequency domain multiplexing (FDM) is shown. Therefore, it is possible to transmit and receive data between the base station and the IAB nodes in the time domain in which the base station or the IAB node transmits and receives data to the terminal. However, due to the unidirectional transmission/reception characteristics of IAB nodes, only data transmission in the same direction is possible. For example, in a time domain in which the first IAB node receives data from the terminal, the first IAB node can only receive backhaul data from another IAB node or base station. In addition, in the time domain in which the first IAB node transmits data to the terminal, the first IAB node can only transmit backhaul data to another IAB node or base station.

Although only TDM and FDM have been described among multiplexing techniques in FIG. 2 , spatial domain multiplexing (SDM) is possible between an access link and a backhaul link. Therefore, although it is possible to transmit and receive the access link and the backhaul link at the same time through the SDM, data is transmitted in the same direction even in the SDM due to the unidirectional transmission and reception characteristics of the IAB nodes as in the FDM in FIG. 2 (b) above. only is possible For example, in a time domain in which the first IAB node receives data from the terminal, the first IAB node can only receive backhaul data from another IAB node or base station. In addition, in the time domain in which the first IAB node transmits data to the terminal, the first IAB node can only transmit backhaul data to another IAB node or base station.

Information about which multiplexing technique to use among TDM, FDM, and SDM may be transmitted between the 'IAB node' and the 'base station or upper IAB node' in various ways. According to embodiments, when an IAB node initially accesses a base station or higher IAB node, the IAB node transmits capability information for the multiplexing scheme to the base station or higher IAB node (eg, parent IAB node). can transmit Alternatively, according to embodiments, the IAB node may then send higher layer signaling information (upper layer signal) may receive information about which multiplexing technique to use.

Alternatively, according to embodiments, the IAB node may receive information on which multiplexing technique to use from the base station or higher IAB nodes through the backhaul link after initial access. Alternatively, according to embodiments, after the IAB node transmits the capability information to the base station or higher IAB node, which multiplexing technique to use may be implemented by the IAB node, and the IAB node may determine a specific slot or radio frame ) Alternatively, it may be reported to the base station or higher IAB nodes through backhaul or higher layer signaling information about which multiplexing technique to use during or continuously thereafter.

Although the multiplexing technique between the access link and the backhaul link has been mainly described in FIG. 2 , the same method as multiplexing between the access link and the backhaul link may also be used for multiplexing between the backhaul links. For example, multiplexing of a mobile termination (MT) (backhaul link) and a DU (backhaul link or access link) within an IAB node, which will be described later, is possible by the method described in the example of FIG. 2 .

3 illustrates an example in which resources are multiplexed in the time domain between an access link and a backhaul link in an IAB node according to an embodiment of the present invention.

Referring to FIG. 3, (a) of FIG. 3 illustrates a process in which an IAB node 302 communicates with a parent node 301, a child IAB node 303, and a terminal 304. it did Describing the link between the nodes in more detail, the parent node 301 may transmit a backhaul downlink signal to the IAB node 302 in backhaul downlinks ( _{LP, DL} ) (311). The IAB node 302 may transmit a backhaul uplink signal to a parent node 301 in a backhaul uplink (L _{P, UL} ) (312). The IAB node 302 may transmit an access downlink signal to the terminal 304 on an access downlink ( _{LA, DL} ) (316). The terminal 304 may transmit an access uplink signal to the IAB node 302 on an access uplink ( _LA,UL ) (315). The IAB node 302 transmits a backhaul downlink signal to the child IAB node 303 on the backhaul downlink (L _{C, DL} ) (313), and the IAB child node 303 transmits a backhaul downlink signal (313). ) may transmit a backhaul uplink signal on a backhaul uplink (L _{C, UL} ) (314). In the example of FIG. 3, subscript P means a backhaul link with a parent, subscript A means an access link with a terminal, and subscript C means a backhaul link with a child.

The link relationship of FIG. 3 is described based on the IAB node 302, and from the point of view of the IAB child node 303, the parent node is the IAB node 302, and the IAB child node 303 ) may have another IAB child node under it. In addition, from the perspective of the parent node 301, a child node is the IAB node 302, and another IAB parent node may exist above the parent node 301.

In the above, the backhaul uplink/downlink signal and the access uplink/downlink signal are data and control information, a channel for transmitting data and control information, a reference signal necessary for decoding data and control information, or reference signals for knowing channel information. may include at least one of them.

3(b) shows an example in which all of the above links are multiplexed in the time domain. In the example of FIG. 3, backhaul downlink (L _P,DL ) 311, backhaul downlink (L _C,DL ) 313, access downlink ( _LA,DL ) 316, and access uplink (LA _{) ,UL} ) 315, backhaul uplink (L _C,UL ) 314, and backhaul uplink ( _LP,UL ) 312 are multiplexed in time order. The precedence relationship of the links provided in the example of FIG. 3 is an example, and any precedence relationship can be applied regardless.

Since the above links are multiplexed in the time domain in chronological order, this time division method transmits signals from the parent node 301 to the child IAB node 303 via the IAB node 302, In addition, it can be seen that this multiplexing method takes the most time to transmit the signal to the terminal. Therefore, as a method for reducing the latency when transmitting a signal from the parent node 301 to the terminal, multiplexing backhaul links and backhaul links or backhaul links and access links in the frequency domain or in the spatial domain A method of multiplexing and transmitting at the same time may be considered.

4 illustrates an example in which resources are multiplexed in frequency and spatial domains between an access link and a backhaul link in an IAB node according to embodiments of the present invention.

In FIG. 4, a method for reducing time delay by multiplexing backhaul links and backhaul links or backhaul links and access links in the frequency domain or in the spatial domain is described.

Referring to FIG. 4, similarly to FIG. 3, in (a) of FIG. It illustrates the process of communication. Describing the link between nodes in more detail, the parent node 401 may transmit a backhaul downlink signal to the IAB node 402 on backhaul downlinks (L _{P, DL} ) (411). The IAB node 402 may transmit a backhaul uplink signal to the parent node 401 on a backhaul uplink (L _{P, UL} ) (412). The IAB node 402 may transmit an access downlink signal (LA _{, DL} ) to the terminal 404 (416), and the terminal 404 may transmit an access downlink (LA, DL) to the IAB node 402 _{. UL} ) may transmit an access uplink signal (415). The IAB node 402 may transmit a backhaul downlink signal (413) to the child IAB node 403 in the backhaul downlink (L _{C, DL} ), and the IAB child node 403 may transmit the IAB node ( (414) _. In the example of FIG. 4 described above, subscript P means backhaul link with parent, subscript A means access link with terminal, and subscript C means backhaul link with child.

The link relationship in FIG. 4 is described based on the IAB node 402, and from the point of view of the IAB child node 403, the parent node is the IAB node 402, and the IAB child node 403 ) may have another IAB child node under it. In addition, from the perspective of the parent node 401, a child node is the IAB node 402, and another IAB parent node may exist above the parent node 401.

In the above, the backhaul uplink/downlink signal and the access uplink/downlink signal are data and control information, a channel for transmitting data and control information, a reference signal necessary for decoding data and control information, or reference signals for knowing channel information. may include at least one of them.

In (b) of FIG. 4, an example of multiplexing in the frequency domain or spatial domain is shown.

As described above, since the IAB node has unidirectional transmission and reception characteristics at a moment, signals that can be multiplexed in the frequency domain or multiplexed in the spatial domain are limited. For example, considering the unidirectional transmission/reception characteristics of the IAB node 402, links that can be multiplexed in the time domain in which the IAB node can transmit include a backhaul uplink (L _P,UL ) 412 and a backhaul downlink (L _{C , DL} ) 413 and an access downlink ( _{LA, DL} ) 416 may exist. Therefore, the links (ie, backhaul uplink (L _{P, UL} ) 412, backhaul downlink (L _{C, DL} ) 413, and access downlink (L _{A, DL} ) 416) are used in the frequency domain. In the case of multiplexing in the spatial domain or in the resource domain 421, the IAB node 402 can transmit all of the links in the same time domain. In addition, links that can be multiplexed in the time domain in which the IAB node 402 can receive include a backhaul downlink (L _P,DL ) 411, a backhaul uplink (L _C,UL ) 414, and an access uplink. (L _{A, UL} ) 415 and the like. Therefore, the links (ie, backhaul downlink (L _{P, DL} ) 411, backhaul uplink (L _{C, UL} ) 414, and access uplink (L _{A, UL} ) 415) are used in the frequency domain. In case of multiplexing in the spatial domain or in the resource domain 422, the IAB node 402 can receive all of the links in the same time domain.

The multiplexing of the links provided in the embodiment of FIG. 4 is just one example, and it goes without saying that only two links among three links multiplexed in the frequency or spatial domain can be multiplexed. That is, the IAB node can transmit/receive signals by multiplexing some of the multiplexable links.

Next, the structure of the IAB node will be described.

In order to support various services such as large-capacity transmission, low-latency high-reliability, or large-capacity machine-to-machine communication devices in 5G systems and to reduce capital expenditures (CAPEX), various types of base station structures optimal for service requirements are being studied. In order to reduce CAPEX and effectively handle interference control in the 4G LTE system, the data processing unit of the base station and the wireless transmission/reception unit (or remote radio head, RRH) are separated, the data processing unit processes it centrally, and only the wireless transmission/reception unit is placed at the cell site Cloud RAN (C-RAN) structure has been commercialized. In the C-RAN structure, an optical link of a common public radio interface (CPRI) standard is generally used when baseband digital IQ (in-phase quadrature) data is transmitted from a base station data processor to a wireless transceiver. When data is transmitted through such a wireless transceiver, a large amount of data capacity is required. For example, 614.4 Mbps is required when sending 10 MHz IP (internet protocol) data, and 1.2 Gbps data rate is required when sending 20 MHz IP data. Therefore, in the 5G RAN structure, in order to reduce the enormous load of the optical link, the base station is divided into a central unit (CU) and a distributed unit (DU), and functional split is applied to the CU and DU to design a variety of structures. are doing 3GPP is in the process of standardizing various functional split options between CU and DU, and options for functional split are divided by function between protocol layers or within protocol layers. ) 1 to option 8, there are a total of 8 options. Among these options, the structures considered first in the current 5G base station structure are option 2 and option 7. In option 2, RRC and packet data convergence protocol (PDCP) are located in the CU, and radio link control (RLC), medium access control (MAC), physical layer (PHY) and radio frequency (RF) are located in the DU. In option 7, the RRC, PDCP, RLC, MAC, and upper PHY layers are located in the CU, and the lower PHY layer is located in the DU. Through the functional split as described above, it is possible to have a structure having deployment flexibility in which NR network protocols are separated and moved between CUs and DUs. Through this structure, flexible hardware implementation provides a cost-effective solution, and the separation structure between CU and DU enables coordination of load management, real-time performance optimization, and NFV (network functions virtualization) / SDN (software defined network) , and the configurable functional split has the advantage of being applicable to various applications (variable latency in transmission).

Accordingly, the structure of the IAB node considering the above functional split will be described with reference to FIG. 5 .

5 schematically illustrates the structure of an IAB node according to an embodiment of the present invention.

Referring to FIG. 5, gNB 501 is composed of CUs and DUs, and IAB nodes have a terminal function (hereinafter referred to as MT) for transmitting and receiving data in a backhaul link with a parent node, and a child node and It consists of a base station function (hereinafter referred to as a DU) for transmitting and receiving data on a backhaul link. In FIG. 5, IAB node #1 (502) is wirelessly connected to gNB (501) by one hop, and IAB node #2 (503) is wirelessly connected to gNB (501) by two hops via IAB node #1 (502). It is connected.

As shown in FIG. 5, the CU of the gNB 501 includes not only the DU of the gNB 501 but also all IAB nodes wirelessly connected to the gNB 501, that is, IAB node #1 502 and IAB node #2. DUs of 503 may be controlled (511, 512). The CU of the gNB 501 sends a DU (at least one of the DU of the gNB 501, the DU of the IAB node #1 502, and the DU of the IAB node #2 503) to the DU of the IAB node below it. Radio resources may be allocated to transmit/receive data with the MT. The allocation of the radio resources may be transmitted to the DU through an upper layer signal such as system information or RRC information or a physical layer signal using an F1 application protocol (F1AP) interface. The F1AP may refer to the 3GPP TS 38.473 standard. In this case, the radio resource may be composed of a downlink time resource, an uplink time resource, a flexible time resource, and the like.

Hereinafter, configuration of radio resources for the TDM will be described in detail based on IAB node #2 (503). In particular, configuration of radio resources according to embodiments of the present disclosure may be applied when resources are multiplexed within one carrier in the time domain between an access link and a backhaul link in an IAB node in FIG. 3 . In addition, configuration of radio resources according to embodiments of the present disclosure may be applied even when multiplexing backhaul links and backhaul links or backhaul links and access links in frequency domains of different carriers in FIG. 4 .

The downlink time resource is a resource for transmitting downlink control/data and signals to an MT of an IAB node below the DU of the IAB node #2 503. The uplink time resource is a resource for the DU of the IAB node #2 503 to receive an uplink control/data signal from the MT of the lower IAB node. The flexible time resource is a resource that can be used as a downlink time resource or an uplink time resource by the DU, and the flexible ( flexible) How time resources are to be used can be dictated. Upon receiving the downlink control signal, the MT of the subordinate IAB node determines whether the flexible time resource is used as a downlink time resource or an uplink time resource. If the downlink control signal is not received, the MT of the lower IAB node does not transmit/receive. That is, the MT does not monitor or decode downlink control channels in the above resources or measure signals in the above resources. In the above resources, the MT does not perform transmit/receive operations. That is, the MT does not monitor or decode downlink control channels in the above resources or measure signals in the above resources.

For the downlink time resource, uplink time resource, and flexible time resource, two different types (or three different types including the not always available time resource) are transmitted from the CU of the gNB 501. Can be directed to DU.

The first type is a soft type, and the CU of the gNB 501 provides soft type downlink time resources, uplink time resources, and flexible time resources to the DU of IAB node # 2 503 F1AP (interface between CU and DU). At this time, IAB node #1 (502), which is the parent IAB (or DU of the parent IAB) of IAB node #2 (503), is a child for the set soft-type resources. ) Explicitly (e.g., DCI format by) or implicitly. That is, IAB node #2 (503) (or DU of IAB node #2 (503)) is instructed that a specific resource can be utilized by IAB node #1 (502) (or DU of IAB node #1 (502)). In this case, the DU of IAB node #2 (503) can utilize the resource for data transmission/reception with the MT of the lower IAB node. That is, the DU of the IAB node #2 503 may perform transmission in the case of a downlink resource or reception in the case of an uplink resource by utilizing the resource. If it is indicated that the resource cannot be utilized, the IAB node #2 503 cannot utilize the resource for data transmission/reception with the MT of the lower IAB node. That is, the DU of the IAB node #2 503 cannot be transmitted or received using the resource.

A method of indicating the availability of the above-mentioned soft type resource by a downlink control information (DCI) format will be described in more detail. The DCI in this embodiment may include an availability indicator for indicating the availability of one or more consecutive upward or downward or flexible symbols.

In order to receive DCI according to the DCI format, the IAB node #2 503, together with the cell ID (identification) of the DU of the IAB node #2 503 in advance, the DCI format ( format) for at least one of the location information of the availability indicator indicating the availability of the IAB node # 2, a table indicating the utilization of time resources corresponding to a plurality of slots, and a mapping relationship between the availability indicators. Information may be received by a higher layer signal from a CU or parent IAB. Values (or indicators) indicating utilization of consecutive uplink symbols, downlink symbols, or flexible symbols within one slot and the meanings of the values (or indicators) may be configured as shown in Table 1 below.

[Table 1]

When the above availability indicator is instructed to the IAB node #2 (503) by the DCI format from the parent IAB and the IAB node #2 (503) receives the indication, the IAB node #2 As a method of interpreting the relationship between the downlink, uplink, or flexible time resource set in the DU of 503 from the CU to the IAB DU and the above-described utilization, the following method may be considered.

In the first method, the number of values indicating the availability included in the availability indicator included in the DCI format of the IAB DU is a slot including a soft type consisting of consecutive symbols set by the CU It is a method that is expected to match the number. According to this method, the IAB DU can determine that the utilization is applied only to slots including soft types.

In the second method, the number of values indicating the availability included in the availability indicator included in the DCI format of the IAB DU is the number of all slots set by the CU, that is, hard / soft )/NA (non-available) type is expected to match the number of all slots. Meanwhile, in this embodiment, the IAB DU may determine that the utilization is applied only to a slot including a soft type, and to a slot including only a hard or NA type without a soft type, the above indicated It can be judged that usability is not applied.

In the first and second methods, the meaning of the value indicating the availability of the IAB DU can be expected to match the downlink resource, uplink resource, or flexible resource set by the CU. For example, when only downlink soft resources or downlink hard resources exist in a slot, it can be expected that only a value of 1 is indicated in [Table 1] for the IAB DU. Therefore, it can be expected that the IAB DU does not indicate values including utilization of uplink soft resources among the values in [Table 1].

In addition, the IAB DU may determine that it is possible to indicate whether a downlink resource or an uplink resource is available in addition to a value indicating that flexible resources are available, at least in flexible resources set by the CU. For example, in the case of flexible soft resources or flexible hard resources, the DU of the IAB node can be expected to indicate a value of 1 or 2 instead of a value of 4 in [Table 1] above. there is. In this case, the DU of the IAB node #2 uses only the uplink or downlink according to the instructions of the parent IAB, instead of the flexible resource being utilized upward or downward by the determination of the IAB node #2. It can be judged that it is possible.

In addition, the IAB DU can be expected to indicate a value of 0 in [Table 1] in any hard/soft or NA (non-available) resource set by the CU. In this case, the IAB DU determines that resource utilization is not possible in the hard / soft resources previously set by the CU, and until it is indicated that it can be utilized by the DCI format later. As in the case of a resource type that is not always available set by the CU, it is considered that the above resource cannot be utilized for data transmission/reception between the DU of IAB node #2 (503) and the MT of the lower IAB node. Afterwards, when it is indicated that it can be used again by the DCI format, the DU of the IAB node # 2 can use the resource as received by the DCI format by setting the CU.

The second type is a hard type, and the above resources are always utilized between the DU and the MT. That is, the DU of IAB node #2 (503) can be transmitted when the resource is a downlink time resource, regardless of the MT transmission and reception operation of the IAB node #2 (503), and received when the resource is an uplink resource can be performed. If the resource is a flexible resource, the DCI format indicating whether the flexible resource is a downlink resource or an uplink resource by the determination of the IAB DU (i.e., to the MT of the lower IAB node) to match) can be transmitted or received.

The third type is a type that is always not used or always non-available, and the above resources cannot be used by the DU of the IAB node #2 (503) for data transmission and reception with the MT.

The above types may be received together when a downlink time resource, an uplink time resource, a flexible time resource, and a reserved time resource are received as upper signals from a CU to a DU.

Referring to FIG. 5, the DU of the gNB 501 performs a normal base station operation, and the DU controls the MT of the IAB node #1 502 to perform scheduling to transmit and receive data (521). . The DU of IAB node #1 (502) performs a normal base station operation, and the DU controls the MT of IAB node #2 (503) to perform scheduling to transmit and receive data (522).

According to an embodiment, a DU may indicate radio resources to transmit/receive data with MTs of IAB nodes below it based on radio resources allocated from the CU. The radio resource configuration may be transmitted to the MT through system information, higher layer signals, or physical layer signals. In this case, the radio resource may include a downlink time resource, an uplink time resource, a flexible time resource, a reserved time resource, and the like. The downlink time resource is a resource for transmitting a downlink control/data signal to an MT of an IAB node below the DU. The uplink time resource is a resource for receiving an uplink control/data signal from an MT of an IAB node at a lower level of the DU. The flexible time resource is a resource that can be used as a downlink time resource or an uplink time resource by the DU, and the flexible time resource is transmitted to the MT of the lower IAB node by the downlink control signal of the DU. ) can indicate how time resources will be used. Upon receiving the downlink control signal, the MT determines whether the flexible time resource is used as a downlink time resource or an uplink time resource. If the downlink control signal is not received, the MT does not perform a transmission/reception operation. That is, the MT does not monitor or decode downlink control channels in the above resources or measure signals in the above resources.

The downlink control signal may be signaled to the MT as a combination of a higher layer signal and a physical layer signal, and the MT may receive the signaling and determine a slot format in a specific slot. The slot format may basically start with a downlink symbol, have a flexible symbol in the middle, and end with an uplink symbol at the end (eg, a structure having a sequence of D-F-U). In the case of using only the above slot format, the DU of the IAB node can perform downlink transmission at the start of the slot, but the MT of the IAB node is set to the above slot format (ie, D-F-U structure) from the parent IAB Therefore, uplink transmission cannot be performed at the same time (corresponding to slot format indexes 0 to 55 in [Table 2] below). Therefore, starting with an uplink symbol, a flexible symbol is located in the middle, and finally a downlink symbol Slot formats configured to end may be exemplified as shown in Table 2 below (corresponding to slot format indexes 56 to 96 in Table 2 below). The slot format illustrated in [Table 2] below is transmitted to the MT using the downlink control signal, and can be configured by the CU using the F1AP for the DU.

[Table 2]

Reserved time resources (e.g., 97 to 254) are resources in which the DU cannot transmit/receive data with the lower MT, and the MT does not transmit/receive operations in the resource. That is, the MT does not monitor or decode downlink control channels in the above resources or measure signals in the above resources.

Accordingly, MTs in one IAB node are controlled by DUs in upper IAB nodes to receive scheduling and transmit/receive data, and DUs in the same IAB nodes are controlled by the CU of the gNB 501. Therefore, since the MT and DU in one IAB are controlled by different entities, it is difficult to coordinate in real time.

6 is a diagram for explaining a communication method for simultaneous transmission and reception between an MT and a DU in an IAB node in a wireless communication system according to an embodiment of the present invention.

In FIG. 6, simultaneous transmission and reception between an MT and a DU in one IAB node means that the MT transmits or receives within the same time resource by the multiplexing method (FDM or SDM) described in FIG. 2 or described in FIGS. 7 and 8 at the same time. Receive means that the DU transmits or receives.

Referring to FIG. 6, a first case 601 illustrates that both MTs and DUs transmit respective signals within one IAB node. In the first case 601, the signal transmitted by the MT of the IAB node may be received by the DU of the parent IAB node or base station through the backhaul uplink as described in FIGS. 3, 4, and/or 5. In addition, in the first case 601, the signal transmitted by the DU of the IAB node at the same time (ie, the same time resource) is transmitted through the backhaul downlink as described in FIGS. 3, 4, and/or 5. It can be received by the node's MT or by the access terminal through the access downlink.

The second case 602 shows that both MTs and DUs within one IAB node receive respective signals. In the second case 602, the signal received by the MT of the IAB node may be a signal transmitted from a DU of a parent IAB node or a base station through a backhaul downlink as described in FIGS. 3, 4, and/or 5. In addition, in the second case 602, the signal received by the DU of the IAB node at the same time (ie, the same time resource) is transmitted to the MT of the IAB node through the backhaul uplink as described in FIGS. 3, 4, and 5. , or may be a signal transmitted by an access terminal through an access uplink.

The third case 603 shows that both the MT and the DU in the IAB node receive or transmit their respective signals. That is, in the third case 603, the MT in the IAB node can receive its own signal, and at the same time, the DU in the IAB node can transmit its own signal. In the third case 603, the signal received by the MT of the IAB node may be a signal transmitted from a DU of a parent IAB node or a base station through a backhaul downlink as described in FIGS. 3, 4, and/or 5. In addition, in the third case 603, the signal transmitted by the DU of the IAB node at the same time (ie, the same time resource) is transmitted through the backhaul downlink as described in FIGS. 3, 4, and/or 5. It can be received by the node's MT or by the access terminal through the access downlink.

The fourth case 604 shows that both the MT and the DU in the IAB node transmit or receive respective signals. That is, in the fourth case 604, the MT in the IAB node can transmit its own signal, and at the same time, the DU in the IAB node can receive its own signal. In the fourth case 604, the signal transmitted by the MT of the IAB node may be received by the DU of the parent IAB node or base station through the backhaul uplink as described in FIGS. 3, 4, and/or 5. In addition, in the fourth case 604, the signal received by the DU of the IAB node at the same time (ie, the same time resource) is transmitted through the backhaul uplink as described in FIGS. 3, 4, and/or 5. It may be a signal transmitted by an MT of a node or transmitted by an access terminal through an access uplink.

In the present disclosure, in the first case 601 and / or the second case 602, in a situation in which both MT and DU transmit or receive signals within one IAB node, a method for setting a DU resource type and a parent IAB node accordingly And embodiments of the procedure of the IAB node are provided. Hereinafter, embodiments of the present disclosure may be applied to the third case 603 and the fourth case 604 as well as the first case 601 and the second case 602 .

7 is a diagram for explaining a DU resource type for FDM support of an IAB node and an operation of an IAB node in a wireless communication system according to an embodiment of the present invention.

Referring to FIG. 7, when DU and MT resources of an IAB node are multiplexed by FDM, transmission/reception interference occurs between DUs and MTs of an IAB node because the DUs and MTs of an IAB node transmit and receive at the same time in adjacent frequency resources at the same time. do. A guard frequency domain for mitigating the transmission/reception interference may be considered. Depending on whether the guard frequency domain is generated by the DU of the IAB node or the DU of the parent IAB node, the DU resource type of the IAB node in the frequency / time domain and the corresponding operation of the DU and MT of the IAB node this can be different Therefore, a DU resource type setting method, a guard frequency generation method, the guard frequency generation method, and DU and MT operations of an IAB node according to DU resource types in the frequency-time domain will be described with reference to FIG. 7 .

Hereinafter, the present disclosure discloses DU resource type configuration in the frequency-time domain.

According to an embodiment, the CU of the gNB may allocate radio resources to the DU so that the DU can transmit/receive data with an MT of an IAB node below it. The allocation of the radio resources may be transmitted to the DU through an upper layer signal such as system information or RRC information or a physical layer signal using an F1 application protocol (F1AP) interface. In this case, the radio resource may include a downlink frequency-time resource, an uplink frequency-time resource, and/or a flexible frequency-time resource. Unlike the radio time resource that utilizes the entire band within one carrier described in FIG. 5, a specific frequency (eg, at least one physical resource block (PRB) or one or more PRBs within one carrier) is an allocation unit on a frequency. The resource may be set in the frequency domain (eg, at least one slot) and in the frequency domain (eg, at least one or more slots). In the following resources, frequency-time is omitted for convenience.

Similar to the radio time resource, information on three types of downlink resources, uplink resources, and / or flexible resources (or at least one of the three types) is indicated from the CU to the DU of the IAB node It can be.

The first type is a soft type, and the CU of the gNB assigns soft-type downlink resources, uplink resources, and / or flexible resources to the DUs of the IAB node F1AP (interface between CU and DU) can be set using At this time, the parent IAB of the IAB node (or the DU of the parent IAB) is the child IAB (or the DU of the child IAB) for the set soft-type resources Whether the above resources are utilized (available) or not utilized (not available) may be explicitly (eg, by DCI format) or implicitly indicated to the IAB node. That is, when a specific resource is indicated to be available by the parent IAB of the IAB node (or the DU of the parent IAB), the DU of the IAB node uses the resource for data transmission and reception with the MT of the lower IAB node can be utilized In addition, the DU of the IAB node may perform transmission in the case of a downlink resource or reception in the case of an uplink resource by utilizing the resource. If it is indicated that the resource cannot be utilized, the IAB node cannot utilize the resource for data transmission/reception with the MT of the subordinate IAB node. That is, the DU of the IAB node cannot be transmitted or received using the resource.

Hereinafter, the present disclosure discloses a method of indicating the availability of the soft type of resource by a DCI format. The DCI format in this embodiment may include an availability indicator for indicating availability of one or more consecutive upward or downward or flexible symbols.

In order for the IAB node to receive the DCI format, the location of the availability indicator indicating the availability of the IAB node in the DCI format together with the cell ID of the DU of the IAB node in advance Information on at least one of information, a table indicating utilization of resources corresponding to a plurality of frequency-times, and a mapping relationship between utilization indicators may be received by a higher layer signal from a CU or a parent IAB. can

The second type is a hard type, and the above resources are always utilized between the DU and the MT. That is, the DU of the IAB node can be transmitted when the resource is a downlink time resource, and can be received when the resource is an uplink resource, regardless of the transmission/reception operation of the MT of the IAB node. If the resource is a flexible resource, the DCI format indicating whether the flexible resource is a downlink resource or an uplink resource by the determination of the IAB DU (that is, to the MT of the lower IAB node) to match), transmission or reception may be performed on the resource.

The third type is a NA (always not used or always non-available) type, and the DU of the IAB node cannot be used for data transmission/reception with the MT.

The above types may be received together when a downlink resource, an uplink resource, a flexible resource, and a reserved resource are received as higher signals from a CU to a DU.

Hereinafter, the present disclosure discloses a method for generating a guard frequency according to a DU resource type and DU and MT operations of an IAB node.

In a first method, a method in which the guard frequency is generated by a DU of an IAB node that is a child IAB node of a base station/parent IAB node is disclosed. The first diagrams 701 to 713 of FIG. 7 show that the hard type 701, soft type 702, and NA type 703, which are the DU resource types of the IAB node, are frequency-time It shows what is set in the area. At this time, it is assumed that the DU of the IAB node determines that the soft type 702 resource is not utilized. Resources 711 that DUs of IAB nodes actually use for data transmission and reception and resources 713 that MTs of IAB nodes actually use for data transmission and reception with the base station/parent IAB node may exist within the above types of resources. At this time, a guard frequency region 712 for mitigating the influence of DU transmission/reception of the IAB node on MT transmission/reception of the IAB node may be set in a hard type 701 resource. The time-frequency resource in the hard type 701 is a resource that the DU of the IAB node can utilize regardless of the influence of the MT of the IAB node, and the remaining time-frequency resources excluding the hard type 701 In the area, that is, the soft type (702) determined that the IAB DU is not utilized, and the NA (703) type that is not available for the IAB DU, there is no interference effect on data transmission and reception between the MT of the IAB node and the base station/parent IAB node The above guard frequency region may be set within a hard type 701 resource under the responsibility of the DU of the IAB node. For example, as illustrated, when hard type 701 resources, soft type 702 resources, and NA type 703 resources are sequentially set in the frequency domain, the guard frequency domain 712 corresponds to the hard type 701 ) between the soft type 702 resource and the hard type 701 resource.

The second diagrams 721 to 733 of FIG. 7 show that the hard type 721, soft type 722, and NA type 723, which are the DU resource types of the IAB node, are frequency-time Another example set in the area is shown. At this time, it is assumed that the DU of the IAB node determines that the soft type 722 resource is utilized. Resources 731 that DUs of IAB nodes actually use for data transmission and reception and resources 733 that MTs of IAB nodes actually use for data transmission and reception with the base station/parent IAB node may exist within the above types of resources. At this time, the guard frequency region 732 for mitigating the effect of the DU transmission and reception of the IAB node on the MT transmission and reception of the IAB node is set within a soft type 722 resource determined that the DU of the IAB node is utilized It can be. The time-frequency resource in the soft type 722 is a resource that the DU of the IAB node can utilize without affecting the MT of the IAB node, and the hard type 721 and the soft type In the remaining time-frequency domain except for 722, that is, the type of NA 723 that is not available for IAB DU, the above guard frequency domain is set to IAB Under the responsibility of the DU of the node, it may be set in a soft type 722 resource determined to be utilized by the DU of the IAB node. For example, as illustrated, when hard type 721 resources, soft type 722 resources, and NA type 723 resources are sequentially set in the frequency domain, the guard frequency domain 732 corresponds to the hard type 721 ) and the soft type 722 resource, it may be set in the soft type 722 resource.

In summary, in the scheme in which the guard frequency is generated by the DU of the IAB node, which is a child IAB node of the base station/parent IAB node in the first method, the DU of the IAB node is a hard type resource within the same time-frequency Data can be transmitted and received without considering the influence of the IAB node operating on the MT. However, in order to mitigate an interference effect on the MT of an IAB node operating in a different time-frequency, a guard frequency may be set within the hard type resource.

Next, the DU of the IAB node can transmit and receive data without affecting the MT of the IAB node operating within the same time-frequency in the soft type resource determined to be utilized. The fact that the MT of the IAB node is not affected can be explained in the following case. That is, the MT of the IAB node does not transmit/receive during the frequency time resource of the DU of the IAB node. Alternatively, transmission/reception of the MT of the IAB node does not change due to transmission/reception during the frequency time resource of the DU of the IAB node. Alternatively, the MT of the IAB node receives a DCI format indicating that a soft type resource is available. However, in order to mitigate the influence of interference on MTs of IAB nodes operating in other time-frequencies other than hard-type resources, a guard frequency may be set within soft-type resources determined to be utilized. .

In the second method, a method in which the guard frequency is generated by a base station/parent IAB node that transmits and receives an MT of an IAB node, which is a self IAB node, will be described. The third diagrams 751 to 763 of FIG. 7 show that the hard type 751, soft type 752, and NA type 753, which are the DU resource types of the IAB node, are frequency-time It shows what is set in the area. At this time, it is assumed that the DU of the IAB node determines that the soft type 752 resource is not utilized. Resources 761 that DUs of IAB nodes actually use for data transmission and reception and resources 763 that MTs of IAB nodes actually use for data transmission and reception with the base station/parent IAB node may exist within the above types of resources. In this case, a guard frequency region 762 for mitigating the influence of DU transmission/reception of the IAB node on MT transmission/reception of the IAB node may be set in a soft type 752 resource. The time-frequency resource in the hard type 751 is a resource that the DU of the IAB node can utilize for transmission and reception without considering the influence on the MT of the IAB node. The DU of the IAB node is in the time-frequency domain except for the hard type 751 due to transmission and reception within the hard type 751, that is, soft in which it is determined that the IAB DU is not utilized. The interference effect on data transmission/reception between the MT of the IAB node and the base station/parent IAB node is not considered in resources of type 752 and NA (753) that are not available for the IAB DU. Accordingly, the guard frequency region 762 may be set within the soft type 752 resource under the responsibility of the DU of the base station/parent IAB node so as not to have the influence of the interference. For example, as illustrated, when hard type 751 resources, soft type 752 resources, and NA type 753 resources are sequentially set in the frequency domain, the guard frequency domain 762 corresponds to the hard type 751 ) and the soft type 752 resource, it may be set in the soft type 752 resource.

The fourth diagrams 771 to 783 of FIG. 7 show that the hard type 771, soft type 772, and NA type 773, which are the DU resource types of the IAB node, are frequency-time Another example set in the area is shown. At this time, it is assumed that the DU of the IAB node determines that the soft type 772 resource is utilized. Resources 781 that DUs of IAB nodes actually use for data transmission and reception and resources 783 that MTs of IAB nodes actually use for data transmission and reception with the base station/parent IAB node may exist within the above types of resources. At this time, the guard frequency region 782 for mitigating the influence of the DU transmission and reception of the IAB node on the MT transmission and reception of the IAB node is determined to be unavailable to the DU of the IAB node. Can be set in the NA type 783 resource there is. The time-frequency resource in the soft type 772 is a resource that the DU of the IAB node can utilize without affecting the MT of the IAB node. The DU of the IAB node is the remaining time-frequency domain except for the hard type 771 due to transmission and reception within the soft type 772, that is, the NA 783 type that is not available for the IAB DU. The interference effect on data transmission/reception between the MT of the IAB node and the base station/parent IAB node is not considered. Therefore, the guard frequency region 783 may be set within the NA type 773 resource under the responsibility of the DU of the base station/parent IAB node so as not to have the influence of the interference. For example, as illustrated, when hard type 771 resources, soft type 772 resources, and NA type 773 resources are sequentially set in the frequency domain, the guard frequency domain 782 corresponds to the soft type 772 ) between the NA type 773 resource and the NA type 773 resource.

In summary, in the method in which the guard frequency is generated by the DU of the base station/parent IAB node that transmits and receives the MT of the IAB node in the second method, the DU of the IAB node is the same time-frequency in a hard type resource Data can be transmitted and received without considering the influence of the IAB node operating within the MT. However, the influence of interference on the MT of an IAB node operating in a different time-frequency is not considered, and the base station/parent IAB node within the soft type resource determined to be unused to mitigate the interference. can set the guard frequency.

Hereinafter, in the present disclosure, data can be transmitted and received without affecting the MT of the IAB node operating within the same time-frequency in a soft type resource determined to be utilized by the DU of the IAB node. However, the DU of the IAB node does not consider the influence of interference on the MT of the IAB node operating in other time-frequency except for the soft type and hard type resources. In order to mitigate the interference, the base station/parent IAB node may set a guard frequency within the NA type resource set as available.

The guard frequency setting method may be limited to a case where a guard frequency is required, and the guard frequency setting may be coordinated between an IAB node and a base station/parent IAB node. That is, when a guard frequency setting is required (or when an IAB node reports that it has the ability to utilize FDM), the IAB node informs the base station/parent IAB node that the guard frequency is required by a higher layer signal (eg, RRC signaling, MAC CE)/physical signal (eg DCI)/backhaul signal, and the base station/parent IAB node may indicate the guard frequency setting as a higher signal/physical signal/backhaul signal.

Which method to use may be determined by the standard, and whether to use the first method or the second method is determined by a DU of a base station/parent IAB node by an upper signal/physical signal or a backhaul signal to an IAB node, which is a self IAB node. can be directed. The IAB node may apply the guard frequency setting method upon receiving the indication. Alternatively, it is also possible to use both the first method and the second method to maximally remove the influence of interference by setting guard frequencies by the IAB node and the base station/parent IAB nodes, respectively.

The guard frequency set by the first method or the second method may be transmitted and received as an upper signal/physical signal/backhaul signal and shared between the IAB node and the base station/parent IAB node.

In the first method or the second method, an allocation position in the frequency domain of a DU resource type may be as follows. A hard type, a soft type, and an NA type are sequentially set by the CU in the order of low or high indexes of the frequency (PRB), so that the IAB node can receive the setting. Among the soft types, the soft type determined to be utilized by the IAB DU may be located after the hard type, and the soft type determined not to be utilized by the IAB DU may be located before the NA type. CU configuration or DCI format of the base station/parent IAB node is indicated so that the IAB node can receive the configuration and instruction.

8 is a diagram for explaining a DU beam limiting method for SDM support of an IAB node and an operation of an IAB node in a wireless communication system according to an embodiment of the present invention.

Referring to FIG. 8, in the case of multiplexing DU and MT resources of an IAB node by SDM, the upper part of FIG. It is a diagram schematically illustrating transmission and reception of data using beams 811, 812, and 813 in the spatial domain, that is, by utilizing a spatial multiplexing method in which simultaneous transmission and reception is performed using different beams between the MT and MT.

As described above, when the base station/parent IAB node 801 and the IAB nodes 802 and 803, which are child IAB nodes, transmit and receive data using beams 811, 812, and 813 in the spatial domain, the DU 803 of the IAB node ) transmits data using the beam 813, the MT 802 of the IAB node transmits data using the beam 812, and the DU of the base station / parent IAB node 801 transmits the beam 811 Assume a situation in which data transmitted by the MT 802 of the IAB node is received using In this case, a specific beam among transmission beams 813 of the DU 803 of the IAB node may interfere with a specific beam among reception beams 811 of the DU of the base station/parent IAB node 801 . In order to reduce the interference effect, the DU of the base station / parent IAB node 801 may limit the use of transmission beams 813 of the DU 803 of the IAB node that may have the above interference effect ( 851), signaling for the limiting beam 851 may be transmitted to the IAB nodes 802 and 803. The IAB nodes 802 and 803 receive the signaling, and the DU 803 of the IAB node can transmit data using the remaining transmission beams in addition to the limited beam 851 from the signaling.

Next, resources for applying the limited beam will be described. The resource may be a time resource to which simultaneous transmission and reception is applied, or may be applied to a specific time resource regardless of simultaneous transmission and reception.

[How to direct and apply a limited beam to time resources]

In the first embodiment (Alt1), the time resource indicated by the time domain multiplexing resource (radio resource configuration for TDM in FIG. ), and simultaneous transmission and reception is possible only in time resources indicated by simultaneous transmission and reception, that is, frequency domain multiplexing resources (radio resource configuration for FDM support in FIG. 7). A limited beam may be applied only to time resources capable of simultaneous transmission and reception. In addition, simultaneous transmission and reception may not be supported in a time resource for which time domain multiplexing is indicated. Also, the limited beam may not be applied to the time domain where time domain multiplexing resources are indicated. Therefore, in the first embodiment, instead of an explicit indication of time resources capable of simultaneous transmission and reception, time resources capable of simultaneous transmission and reception are remaining time resources excluding the time resources indicated for time domain multiplexing, and the base station/parent IAB node 801 and It is also possible to be referred to the IAB nodes 802 and 803.

In the second embodiment (Alt2), simultaneous transmission and reception and simultaneous transmission and reception are performed regardless of time domain multiplexing resources (radio resource configuration for TDM in FIG. 5) or frequency domain multiplexing resources (radio resource configuration for FDM support in FIG. 7). A time domain in which this does not occur is signaled (a higher level signal or a backhaul signal) from the base station/parent IAB node 801, simultaneous transmission and reception is possible only in time resources indicated for simultaneous transmission and reception, and limited beams are available in time resources in which simultaneous transmission and reception are possible. can be applied

Although the case where the limited beam is applied only to time resources in which simultaneous transmission and reception is possible has been described in the first and second embodiments, an area in which simultaneous transmission and reception is not possible, for example, in the first embodiment, a time domain in which time domain multiplexing resources are indicated The limited beam may also be applied to . At this time, the type and number of restricted beams may be different between areas where simultaneous transmission and reception is possible or areas where simultaneous transmission and reception is not possible, and information on beams restricted in the areas where simultaneous transmission and reception is possible and areas where simultaneous transmission and reception is not possible Signaling including may be directed by the base station/parent IAB node 801 to the IAB nodes 802 and 803.

[How to operate IAB DU beam limiting]

First, the IAB nodes 802 and 803 transmit SSB and CSI-RS-related beam information for transmission to lower-order terminals or other lower-order IAB nodes, that is, the beam-related including SSB index and CSI-RS resource ID. Information (or TCI status) may be reported to the base station/parent IAB node 801 through an upper signal/backhaul signal. The above beam related information or (or TCI state) may include the following information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB), QCL It may include information on whether the type is type A, type B, type C, or type D.

Next, the base station/parent IAB node 801 transmits the SSB and CSI-RS transmitted by the IAB nodes 802 and 803 to lower terminals or other lower IAB nodes based on the SSB and CSI-RS related beam information. RS may be measured, and based on the measured value, which Tx beams should be restricted may be determined.

Finally, the base station/parent IAB node 801 may transmit the determined beam restriction information to the IAB nodes 802 and 803.

[Limited Beam Instruction Method]

First, a method in which the base station/parent IAB node 801 instructs the MT 802 of the IAB node about beam information usable for data and signal transmission/reception will be described.

The base station/parent IAB node 801 may set up to 128 TCI (transmission configuration indication) states for the MT 802 of the IAB node through upper signal/backhaul signal to the IAB nodes 802 and 803. there is. The TCI state may include the following beam-related information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

-The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB), It may include information about whether the QCL type is type A, type B, type C, or type D.

Next, the base station/parent IAB node 801 transmits up to 8 TCI states out of up to 128 TCI states to the IAB nodes 802 and 803 through the MAC CE signal/backhaul signal through the MT 802 of the IAB node. can be activated for

The base station/parent IAB node 801 may instruct the IAB nodes 802 and 803 of at least one or more TCI states among the up to eight activated TCI states through a physical signal. The MT 802 of the IAB node may transmit and receive data and signals through at least one specific beam according to at least one or more indicated TCI states.

Next, a method in which the base station/parent IAB node 801 instructs the DU 803 of the IAB node of the limited beam information, that is, beam information that cannot be used for data and signal transmission/reception, will be described.

In the first embodiment, the base station/parent IAB node 801 sends the IAB nodes 802 and 803 up to M transmission configuration indication (TCI) status for the DU 803 of the IAB node through a higher-level signal/backhaul signal ( state) can be set. The beams in the maximum M TCI state settings are SSB and CSI-RS-related beam information from the IAB nodes 802 and 803 to the base station/parent IAB node 801 described in [IAB DU Beam Limitation Operation Method]. s, that is, within beams based on the beam information including SSB index and CSI-RS resource ID.

The TCI state may include the following beam-related information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

-The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB), It may include information about whether the QCL type is type A, type B, type C, or type D.

Next, the base station / parent IAB node 801 transmits the DU 803 of the IAB node to the IAB nodes 802 and 803 with up to N TCI states among up to M TCI states through MAC CE signals / backhaul signals. can be activated for

The base station/parent IAB node 801 may instruct the IAB nodes 802 and 803 of at least one TCI state among the activated maximum N TCI states through a physical signal, respectively. The DU 803 of the IAB node may transmit/receive data and signals through the remaining beams excluding at least one specific beam according to at least one or more indicated TCI states.

In the second embodiment, the base station / parent IAB node 801 is related to the SSB and CSI-RS from the IAB nodes 802 and 803 to the base station / parent IAB node 801 described in [DU beam limiting operation method] Based on the beam information including the SSB index and the CSI-RS resource ID, a MAC CE signal/backhaul signal indicating whether to limit the beam may be configured. For example, the number of TCI states of the beam information including the SSB index and CSI-RS resource ID transmitted from the IAB nodes 802 and 803 to the base station / parent IAB node 801 through MAC CE signals / backhaul signals The number and order of TCI states of the beam information including whether or not the beam is limited and the order is transmitted from the base station/parent IAB node 801 to the IAB nodes 802 and 803 through the MAC CE signal/backhaul signal can match If the beam information in the MAC CE signal/backhaul signal transmitted from the base station/parent IAB node 801 to the IAB nodes 802 and 803 is composed of up to M TCI states, each M TCI state Non-limiting or limiting can be indicated with a 1-bit indicator, such as “0” or “1”, for beam limitation. The DU 803 of the IAB node may transmit/receive data and signals through remaining beams excluding the limited beam indicated in the MAC CE signal/backhaul signal.

Upper signal/MAC CE signal/physical signal/backhaul signal indicating beam information that the base station/parent IAB node 801 can use for data and signal transmission/reception to the MT 802 of the IAB node and the base station/parent IAB node Upper signal/MAC CE signal/physical signal/backhaul signal indicating limited beam information, that is, beam information that cannot be used for data and signal transmission/reception, to the DU 803 of the IAB node by 801 is configured, respectively. , 803), or configured in one signal and received simultaneously by the IAB nodes 802 and 803.

[Procedure of IAB node according to restricted beam indication and DU resource type]

Next, the DU 803 of the IAB node applies the beam restriction indicated by the base station/parent IAB node 801 based on the DU resource type (DU resource type for TDM in FIG. 5 or DU resource type for FDM in FIG. 7). Please explain how to do it.

First, a method of applying the beam restriction indication of the IAB node to the hard type DU resource will be described.

As a first embodiment, when the DU resource type is hard, the DU 803 of the IAB node may not apply the beam restriction indicated by the base station/parent IAB node 801. That is, in the hard resource type, the DU 803 of the IAB node can transmit/receive data with lower terminals and lower IAB nodes using all beam directions regardless of the indicated beam restriction. In the hard type resource, since the DU 803 of the IAB node can transmit and receive data without considering the effect on data transmission and reception between the MT 802 of the IAB node and the base station/parent IAB node 801, the first implementation As in the example, it may make sense not to apply beam restrictions in hard-type resources.

As a second embodiment, even if the DU resource type is hard, the DU 803 of the IAB node may apply the beam restriction indicated by the base station/parent IAB node 801. That is, in the hard resource type, the DU 803 of the IAB node can transmit/receive data with lower terminals and lower IAB nodes using beams other than the restricted beams according to the indicated beam restriction. The second embodiment may be appropriate when the above beam restriction is applied regardless of the DU resource type to maximize data transmission and reception between the MT 802 of the IAB node and the base station/parent IAB node 801.

Next, a method of applying the beam restriction indication of the IAB node to the soft-type DU resource will be described.

As a first embodiment, when the DU resource type is soft, the DU 803 of the IAB node is instructed by the base station/parent IAB node 801 only when it is explicitly or implicitly determined that the soft resource can be utilized. Beam restriction can be applied by the DU 803 of the IAB node. When it is determined that the soft resource can be utilized explicitly or implicitly, at least one of the following conditions is satisfied.

- (Condition 1) The MT 802 of the IAB node does not transmit or receive at the same time as the DU 803 of the IAB node transmits or receives. That is, condition 1 is a case where there is no scheduling to transmit/receive a DU at the same time as the DU is transmitted/received from the base station/parent IAB node 801.

- (Condition 2) Since the transmission/reception direction of the DU (803) of the IAB node coincides with the transmission/reception direction of the MT (802) of the IAB node to maintain the unidirectional transmission/reception characteristic, the transmission/reception direction of the DU (803) of the IAB node is This is a case in which transmission/reception of the MT 802 of the IAB node is not affected.

- (Condition 3) When the MT 802 of the IAB node receives an indication that soft resources are available for the DU 803 of the IAB node from the base station/parent IAB node 801.

If at least one condition as described above is satisfied, the DU 803 of the IAB node may transmit/receive data with the lower terminal and lower IAB nodes using the remaining beams except for the limited beam according to the indicated beam restriction. .

As a second embodiment, when the DU resource type is soft, it is determined that the DU 803 of the IAB node can utilize the soft resource explicitly or implicitly, and in fact, the MT 802 of the IAB node The DU 803 of the IAB node may apply the beam restriction indicated by the base station/parent IAB node 801 only when it is determined that there is data transmission/reception with the parent IAB node 801 . For example, in the first embodiment above (condition 1), the DU 803 of the IAB node uses all beam directions regardless of the indicated beam restriction to transmit and receive data with lower terminals and lower IAB nodes. there is.

As a third embodiment, when the DU resource type is soft, and it is determined that the DU 803 of the IAB node can utilize the soft resource explicitly or implicitly, the base station / parent IAB node 801 indicates Beam restriction may not be applied by the DU 803 of the IAB node in the above resources. That is, the DU 803 of the IAB node can transmit/receive data with lower terminals and lower IAB nodes in the resource using all beam directions regardless of the indicated beam restriction.

As a fourth embodiment, when the DU resource type is soft, the DU 803 of the IAB node can always apply the beam restriction indicated by the base station/parent IAB node 801 in the above resource. That is, the DU 803 of the IAB node can transmit/receive data with the lower terminal and lower IAB nodes in the above resource using the remaining beams except for the limited beam according to the indicated beam restriction.

As a fifth embodiment, when the DU resource type is soft, the MT 802 of the IAB node communicates with the base station/parent IAB node 801 based on scheduling or higher configuration from the base station/parent IAB node 801. The DU 803 of the IAB node may apply the beam restriction indicated by the base station/parent IAB node 801 only when it is determined that there is data transmission/reception.

As a sixth embodiment, when the DU resource type is soft, the MT 802 of the IAB node communicates with the base station/parent IAB node 801 based on scheduling or higher configuration from the base station/parent IAB node 801. The DU 803 of the IAB node may apply the beam restriction indicated by the base station/parent IAB node 801 only when data transmission/reception actually occurs.

As a seventh embodiment, when the DU resource type is soft, only when the DU 803 of the IAB node actually transmits and receives data, the beam restriction indicated by the base station/parent IAB node 801 is transmitted to the DU of the IAB node. 803 is applicable in the above resources. That is, the DU 803 of the IAB node can transmit/receive data with the lower terminal and lower IAB nodes in the above resource using the remaining beams except for the limited beam according to the indicated beam restriction.

It is also possible to combine and use two or more embodiments of the method of applying the beam restriction indication of the IAB node to the soft type DU resource.

As another embodiment, when the DU 803 of the IAB node transmits and receives an essential channel or signal regardless of the DU resource type, the indicated beam restriction may not be applied. For example, when the DU 803 of the IAB node transmits an SS/PBCH block, transmits a PDCCH for SIB1 transmission, transmits a periodic CSI-RS, or receives a PRACH or SR, regardless of the indicated beam restriction Data can be transmitted and received with lower terminals and lower IAB nodes using all beam directions.

9 illustrates an MT beam recommendation method and an operation of an IAB node for supporting spatial division multiplexing (SDM) of an IAB node in a wireless communication system according to an embodiment of the present invention.

Referring to FIG. 9, when DU and MT resources of an IAB node are multiplexed by SDM, the upper part of FIG. That is, it is a diagram schematically showing transmission and reception of data using beams 911, 912, and 913 in the spatial domain.

9, two situations to which the embodiments proposed in the present invention can be applied will be described. First, as a first situation, as described above, when the base station/parent IAB node 901 and the IAB nodes 902 and 903, which are child IAB nodes, transmit and receive data using beams 911, 912, and 913 in the spatial domain, DU 903 of the IAB node transmits data using beam 913, MT 902 of IAB node receives data using beam 912, and DU of base station/parent IAB node 901 may assume a situation in which data is transmitted to the MT 902 of the IAB node using the beam 911. At this time, a specific beam among the transmit beams 913 of the DU 903 of the IAB node is one of the receive beams 912 of the MT 902 of the IAB node receiving data from the DU of the base station/parent IAB node 901. It can have an interference effect on a specific beam. In order to reduce the influence of the interference and receive data by selecting beams having a good channel environment, the MT 902 of the IAB node selects recommendation beams 951 that can be used for data reception among the remaining beams excluding the beams affected by the interference. ) may be signaled to the base station/parent IAB node 901. The base station/parent IAB node 901 may transmit data to the MT 903 of the IAB node using an appropriate beam from the recommendation beams 951 included in the signaling.

As a second situation, when the base station/parent IAB node 901 and the IAB nodes 902 and 903, which are child IAB nodes, transmit and receive data using beams 911, 912, and 913 in the spatial domain, the IAB The DU 903 of the node receives data using the beam 913, the MT 902 of the IAB node transmits the data using the beam 912, and the DU of the base station/parent IAB node 901 It is assumed that data transmitted by the MT 902 of the IAB node is received using the beam 911. At this time, a specific beam among the transmission beams 912 of the MT 902 of the IAB node may interfere with a specific beam among the reception beams 913 of the DU 903 of the IAB node. In order to reduce the effect of the interference and transmit data by selecting beams having a good channel environment, the MT 902 of the IAB node selects recommendation beams 951 that can be used for data transmission among the remaining beams excluding the beams affected by the interference. ) may be signaled to the base station/parent IAB node 901. The base station/parent IAB node 901 may select an appropriate beam from the recommendation beams 951 included in the signaling and schedule data transmission to the MT 903 of the IAB node.

Next, resources for applying the recommended beam will be described. The resource may be a time resource to which simultaneous transmission and reception is applied, or may be applied to a specific time resource regardless of simultaneous transmission and reception.

[How to direct and apply the recommended beam to time resources]

In the first embodiment (Alt1), the time resource indicated by the time domain multiplexing resource (radio resource configuration for TDM in FIG. ), and simultaneous transmission and reception is possible only in time resources indicated by simultaneous transmission and reception, that is, frequency domain multiplexing resources (radio resource configuration for FDM support in FIG. 7). The recommended beam may be applied only to time resources capable of simultaneous transmission and reception. In addition, simultaneous transmission and reception may not be supported in a time resource for which time domain multiplexing is indicated. Also, the recommended beam may not be applied to the time domain where time domain multiplexing resources are indicated. Therefore, in the first embodiment, instead of an explicit indication of time resources capable of simultaneous transmission and reception, time resources capable of simultaneous transmission and reception are remaining time resources excluding the time resources indicated for time domain multiplexing, and the base station/parent IAB node 901 and It is also possible to be referred to the IAB nodes 902 and 903.

In the second embodiment (Alt2), simultaneous transmission and reception and simultaneous transmission and reception are performed regardless of time domain multiplexing resources (radio resource configuration for TDM in FIG. 5) or frequency domain multiplexing resources (radio resource configuration for FDM support in FIG. 7). A time domain in which this does not occur is signaled (higher level signal or backhaul signal) from the base station/parent IAB node 901, simultaneous transmission and reception is possible only in time resources indicated for simultaneous transmission and reception, and a beam recommended in time resources in which simultaneous transmission and reception is possible. this may apply.

Although the case where the recommended beam is applied only to time resources capable of simultaneous transmission and reception has been described in the first and second embodiments above, the area in which simultaneous transmission and reception is not possible, for example, the time when time domain multiplexing resources are indicated in the first embodiment The recommended beam may also be applied to the area. At this time, the type and number of recommended beams may vary between areas where simultaneous transmission and reception is possible or areas where simultaneous transmission and reception is not possible, and the recommended beams in the areas where simultaneous transmission and reception are possible and areas where simultaneous transmission and reception are not possible Signaling including information about the IAB nodes 902 and 903 may be reported or transmitted to the base station/parent IAB node 901.

[How to operate IAB MT beam recommendation]

First, the base station/parent IAB node 901 may set the TCI state including possible transmit/receive beam information for the MT 902 of the IAB node to the IAB nodes 902 and 903 through an upper signal/backhaul signal. The TCI state may include the following beam related information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

-The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB, reference If the signal is SRS, it may include SRS resource ID information, UL BWP ID information) and information about whether the QCL type is type A, type B, type C, or type D.

Next, the base station/parent IAB node 901 may activate a specific TCI state among the TCI states for the MT 902 of the IAB node through a MAC CE signal/backhaul signal to the IAB nodes 902 and 903.

The IAB nodes 902 and 903 select the MT 902 of the IAB node and the DU of the IAB node among the TCI states set through the above signal/backhaul signal or specific TCI states activated through the MAC CE signal/backhaul signal. In step 903, the recommended reception beam or the recommended transmission beam may be determined in consideration of the interference situation or the channel condition.

Finally, the IAB nodes 902 and 903 may transmit the determined beam recommendation information to the base station/parent IAB node 901.

If the IAB nodes 902 and 903 select a reception beam to be recommended or a transmission beam recommended based on the TCI states set through the upper signal / backhaul signal and report it to the base station / parent IAB node 901, The base station/parent IAB node 901 may select and activate beams to be activated among the reported recommendation beams through a MAC CE signal/backhaul signal. The base station/parent IAB node 901 may indicate at least one or more TCI states between the activated TCI states to the IAB nodes 802 and 803 through physical signals. The MT 902 of the IAB node may transmit and receive data and signals through at least one specific beam according to at least one or more indicated TCI states.

[Recommended beam instruction method]

First, a method for the IAB nodes 902 and 903 to report recommended downlink reception beam information to the base station/parent IAB node 901 will be described.

In the first embodiment, the IAB nodes 902 and 903 may transmit recommended downlink reception beam information to the base station/parent IAB node 901 through reports of CRI-RSRP and ssb-index-RSRP, which are uplink control information. In this case, the number of recommended downlink depth beam information may be defined in the standard, and may be transmitted from the base station/parent IAB node 901 to the IAB nodes 902 and 903 in advance through an upper signal/or a backhaul signal, or It may be transmitted to the base station/parent IAB node 901 through the number of TCI states included in each of the CRI-RSRP and ssb-index-RSRP. The CRI-RSRP or ssb-index-RSRP may each include 7 bits of recommended downlink reception beam information as much as the number of the recommended downlink depth beam information, and sequentially 7 bits, 4 bits, 4 bits, 4 bits, … It may include as many pieces of recommended downlink reception beam information as the number of recommended downlink depth beam information.

In the second embodiment, the IAB nodes 902 and 903 may transmit recommendation downlink reception beam information to the base station/parent IAB node 901 through an upper signal/MAC CE signal/backhaul signal.

The above information may include the following beam related information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

-The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB), It may include information about whether the QCL type is type A, type B, type C, or type D. Alternatively, when the IAB nodes 902 and 903 select a reception beam to be recommended based on the TCI states set by the base station/parent IAB node 901 through the upper signal/backhaul signal and report it to the base station/parent IAB node 901 , If the beam information in the MAC CE signal/backhaul signal is composed of up to M TCI states, a 1-bit indicator such as “0” or “1” indicates whether to recommend a Rx beam for each of the M TCI states. You can instruct not recommend and recommend with . In addition, according to an embodiment, the number and order of TCI states set by the base station/parent IAB node 901 may be used to determine beam information in the MAC CE signal/backhaul signal including information to be recommended by the IAB nodes 902 and 903. The number and order of TCI states may be identical.

Next, a method of reporting recommended uplink transmission beam information from the IAB nodes 902 and 903 to the base station/parent IAB node 901 will be described.

In the first embodiment, the IAB nodes 902 and 903 may transmit recommendation uplink transmission beam information to the base station/parent IAB node 901 by reporting CRI-RSRP and ssb-index-RSRP, which are uplink control information. In this case, the CRI-RSRP and ssb-index-RSRP reports including the recommended uplink transmission beam information may be separate reports from the CRI-RSRP and ssb-index-RSRP reporting the recommended downlink reception beam information.

At this time, the number of recommended uplink transmission beam information may be defined in the standard, and may be transmitted from the base station/parent IAB node 901 to the IAB nodes 902 and 903 in advance through an upper signal/or a backhaul signal, or It may be transmitted to the base station/parent IAB node 901 through the number of TCI states included in each of the CRI-RSRP and ssb-index-RSRP. The CRI-RSRP or ssb-index-RSRP may each include 7 bits of recommended uplink transmission beam information as much as the number of the recommended uplink transmission beam information, and in order, 7 bits, 4 bits, 4 bits, 4 bits, … It may include as many pieces of recommended uplink transmission beam information as the number of recommended uplink transmission beam information.

In the second embodiment, the IAB nodes 902 and 903 may transmit recommendation uplink transmission beam information to the base station/parent IAB node 901 through an upper signal/MAC CE signal/backhaul signal.

The above information may include the following beam related information.

- TCI state ID

- At least one piece of QCL (quasi-co-location) information

-The above QCL information includes cell ID, bandwidth part (BWP) ID, reference signal information (eg, CSI-RS ID information when the reference signal is CSI-RS, SSB index information when the reference signal is SSB, reference If the signal is SRS, it may include SRS resource ID, UL BWP ID) and information about whether the QCL type is type A, type B, type C, or type D. Alternatively, when the IAB nodes 902 and 903 select a transmission beam to be recommended based on the TCI states set by the base station/parent IAB node 901 through a higher signal/backhaul signal and report it to the base station/parent IAB node 901 , If the beam information in the MAC CE signal/backhaul signal is composed of up to M TCI states, a 1-bit indicator such as “0” or “1” indicates whether to recommend transmission beams for each of the M TCI states. You can instruct not recommend and recommend with . In addition, according to an embodiment, the number and order of TCI states set by the base station/parent IAB node 901 may be used to determine beam information in the MAC CE signal/backhaul signal including information to be recommended by the IAB nodes 902 and 903. The number and order of TCI states may be identical.

10(a) illustrates an operation of a base station/parent IAB node in a wireless communication system according to an embodiment of the present invention.

Referring to (a) of FIG. 10, in step 1001, the base station/parent IAB node (eg, the parent IAB shown in FIG. 8 and/or FIG. 9) transmits information related to TDM, FDM, or SDM. It can transmit to the IAB node and receive necessary information from the IAB node. As described above, the above information includes information necessary for switching to TDM, FDM or SDM, information necessary for supporting TDM, FDM or SDM, information necessary for simultaneous transmission and reception, and an IAB node and a base station/parent IAB node transmitting a beam. It may include information necessary for operation, information related to restricted beams and recommendation beams, and the like. The information required to support TDM, FDM, or SDM includes radio resource allocation information including DU resource type, information related to soft-type resource utilization, information on the need for guard frequencies, information on guard frequency configuration methods, It may include TCI state setting information, DU resource type setting information for specific beams corresponding to the TCI state, and / or setting information about whether or not the DU can be used, restricted beams and recommended beams, etc. there is.

1002 In step 1002, the base station/parent IAB node may transmit and receive backhaul data to and from the IAB node by applying TDM, FDM or SDM.

10(b) illustrates an operation of an IAB node, which is a self IAB node, in a wireless communication system according to an embodiment of the present invention.

Referring to (b) of FIG. 10 , in step 1011, the IAB node may receive information related to TDM, FDM, or SDM from the base station/parent IAB node and transmit necessary information to the base station/parent IAB node. As described above, the above information includes information necessary for switching to TDM, FDM or SDM, information necessary for supporting FDM or SDM, information necessary for simultaneous transmission and reception, and information necessary for the IAB node and the base station/parent IAB node to operate the beam. It may include necessary information, information related to the restriction beam and the recommendation beam, and the like. The information required to support TDM, FDM, or SDM includes radio resource allocation information including DU resource type, information related to soft-type resource utilization, information on the need for guard frequencies, information on guard frequency configuration methods, It may include TCI state setting information, DU resource type setting information for specific beams corresponding to the TCI state, and / or setting information about whether or not the DU can be used, restricted beams and recommended beams, etc. there is.

In step 1012, the IAB node may transmit and receive backhaul data to a base station/parent IAB node by applying TDM, FDM, or SDM.

To perform the above embodiments of the present disclosure, FIGS. 11 and 12 illustrate a transmitter, a receiver, and a processor of a terminal and a base station, respectively. The transmitter and receiver may be referred to as a transceiver. 13 also shows the arrangement of an IAB node. In the 5G communication system described in the above embodiments, when transmitting and receiving signals in a backhaul link or an access link through an IAB node, a base station (donor base station) and an IAB node that transmit and receive signals in the backhaul link and the IAB node through mmWave A transmission/reception method of a terminal performing transmission/reception in an access link is shown, and to perform this, transmitters, receivers, and processors of a base station, a terminal, and an IAB node may each operate according to an embodiment.

11 is a diagram showing the configuration of a terminal according to an embodiment of the present invention.

Referring to FIG. 11 , a terminal of the present disclosure may include a processor 1101, a receiver 1102, and a transmitter 1103.

The processor (or control unit or processing unit) 1101 may control a series of processes in which the terminal may operate according to each or combination of the above-described embodiments of the present invention of FIGS. 1 to 10 . For example, transmission and reception of an access link with an IAB node according to embodiments of the present disclosure may be differently controlled. The receiver 1102 and the transmitter 1103 may be collectively referred to as a transceiver or transceiver in an embodiment of the present disclosure. The transceivers 1102 and 1103 may transmit and receive signals to and from the base station. The signal may include at least one of control information and data. To this end, the transceivers 1102 and 1103 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. there is. In addition, the transceivers 1102 and 1103 may receive a signal through a wireless channel, output the signal to the processor 1101, and transmit the signal output from the processor 1101 through a wireless channel.

12 is a diagram showing the configuration of a base station (Donor base station) according to an embodiment of the present invention.

Referring to FIG. 12 , a base station of the present disclosure may include a processor 1201, a receiver 1202, and/or a transmitter 1203.

The processor (or control unit or processing unit) 1201 may control a series of processes so that the base station operates according to each or combination of the above-described embodiments of the present invention of FIGS. 1 to 10 . For example, transmission and reception of a backhaul link and transmission and reception of an access link with an IAB node according to embodiments of the present disclosure may be differently controlled. The receiver 1202 and the transmitter 1203 may be collectively referred to as a transceiver or transceiver in an embodiment of the present disclosure. The transceivers 1202 and 1203 may transmit and receive signals with a terminal or a child IAB node. The signal may include at least one of control information and data. To this end, the transceivers 1202 and 1203 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. Also, the transceivers 1202 and 1203 may receive signals through a radio channel, output the signals to the processor 1201, and transmit signals output from the processor 1201 through a radio channel.

13 illustrates the configuration of an IAB node according to an embodiment of the present invention.

Referring to FIG. 13, according to an embodiment of the present invention, an IAB node is a base station function control unit (or processing unit, processor) of an IAB node for transmitting and receiving with a child IAB node through a (wireless) backhaul link. 1301, a base station function receiver 1302, and a base station function transmitter 1303. In addition, the IAB node initially accesses the upper (parent) IAB node and/or donor base station, transmits and receives higher layer signals before transmitting and receiving through the backhaul link, and connects to the upper (parent) IAB node and donor base station (wireless) ) A terminal function control unit (or processing unit, processor) 1311, a terminal function receiver 1312, and a terminal function transmitter 1313 of the IAB node for transmission and reception through a backhaul link.

The base station function controller 1301 of the IAB node can control a series of processes so that the IAB node can operate like a base station according to the above-described embodiment of the present disclosure. For example, the DU of the IAB node described above function can be performed. For example, the base station function controller 1301 may differently control transmission and reception of a backhaul link with a lower IAB node and transmission and reception of an access link with a terminal according to an embodiment of the present disclosure. The base station function receiver 1302 and the base station function transmitter 1303 may be collectively referred to as a first transceiver or a first transceiver in an embodiment of the present disclosure. The first transceiver may transmit and receive signals to and from lower (sub) IAB nodes and terminals. The signal may include at least one of control information and data. To this end, the first transceiver may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. In addition, the first transceiver may receive a signal through a radio channel, output the signal to the base station function controller 1301, and transmit the signal output from the base station function controller 1301 through a radio channel.

The terminal function control unit 1311 of the IAB node performs a series of operations such that the lower (child) IAB node can operate like a terminal for data transmission and reception with the Donor base station or the upper (parent) IAB node according to the above-described embodiment of the present disclosure. It can control the process and, for example, it can perform the function of the MT of the IAB node described above. For example, the terminal function controller 1311 may differently control transmission and reception through a (wireless) backhaul link with a donor base station and/or an upper (parent) IAB node according to an embodiment of the present disclosure. The terminal function receiver 1312 and the terminal function transmitter 1313 may be collectively referred to as a second transceiver or a second transceiver in an embodiment of the present disclosure. The second transceiver may transmit/receive signals with a donor base station and an upper IAB node. The signal may include at least one of control information and data. To this end, the second transceiver may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting its frequency. In addition, the second transceiver may receive a signal through a wireless channel, output the signal to the terminal function controller 1311, and transmit the signal output from the terminal function controller 1311 through a wireless channel.

Meanwhile, the base station function controller 1301 of the IAB node included in the IAB node of FIG. 13 and the terminal function controller 1311 of the IAB node may be integrated with each other and implemented as an IAB node controller. In this case, the IAB node controller 1300 can control the functions of the DU and MT together in the IAB node. The base station function controller 1301, the terminal function controller 1311, and the IAB node controller may be implemented by at least one processor. The first transceiver and the second transceiver may be provided respectively or implemented as an integrated transceiver.

A beam described in this specification means a spatial flow of a signal in a wireless channel, and is formed by one or more antennas (or antenna elements), and this formation process is referred to as beamforming. It can be. According to various embodiments, an antenna array in which a plurality of antenna elements are densely packed may be used, and at this time, a shape (ie, coverage) according to signal gain may have a direction. A beam used for transmission of a signal may be referred to as a transmission beam or a beam used for reception of a signal may be referred to as a reception beam. That is, as an implementation example, an IAB node may include an antenna array for MT or an antenna array for DU.

When the IAB node transmits a signal in the direction of the transmission beam, the signal gain of the device may increase. When a signal is transmitted using a transmission beam, the signal may be transmitted through a spatial domain transmission filter of a signal transmitting side, that is, a transmitting end. When a signal is transmitted using a plurality of transmission beams, the transmitter may transmit the signal while changing a spatial domain transmission filter. For example, when transmitting using the same transmission beam, the transmitting end may transmit the signal through the same spatial domain transmission filter. For example, when the MT of the IAB node receives CSI-RSs for Rx beam search (eg, 3GPP TS 38.214 repetition = 'on'), the IAB node uses the same spatial domain transmission filter (same CSI-RSs) It can be assumed that it is transmitted through a spatial domain transmission filter).

When the IAB node receives a signal in the direction of the receive beam, the signal gain of the device may increase. When a signal is transmitted using a reception beam, the signal may be received through a spatial domain reception filter of a signal receiving side, that is, a receiving end. For example, when an IAB node simultaneously receives several signals transmitted using different beams, the IAB node receives the signals using a single spatial domain receive filter, or multiple simultaneous signals. The signals may be received using multiple simultaneous spatial domain receive filters.

In addition, as a signal transmitted using a beam in the present specification, a reference signal may be used. For example, the reference signal may be a demodulation-reference signal (DM-RS) or a channel state information-signal (CSI-RS). reference signal), synchronization signal/physical broadcast channel (SS/PBCH), and sounding reference signal (SRS). In addition, as a configuration for each reference signal, an indicator such as a CSI-RS resource or an SRS-resource may be used, and this configuration may include information associated with a beam. Beam-related information refers to whether a corresponding configuration (eg, CSI-RS resource) uses the same spatial domain filter as another configuration (eg, another CSI-RS resource within the same CSI-RS resource set) or different It may mean whether a spatial domain filter is used, or which reference signal is quasi-co-located (QCL), and if so, what type (eg, QCL type A, B, C, or D). QCL types can be defined as follows.

- 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

- 'QCL-TypeB': {Doppler shift, Doppler spread}

- 'QCL-TypeC': {Doppler shift, average delay}

- 'QCL-TypeD': {Spatial Rx parameter}

In this specification, according to various embodiments, the IAB node may measure the quality of a beam to obtain cell quality and quality per duplex. The IAB node can obtain beam quality based on CSI-RS or SS/PBCH block.

On the other hand, the embodiments of the present disclosure disclosed in the present specification and drawings are only presented as specific examples to easily explain the technical content of the present disclosure and help understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other modifications based on the present disclosure are possible. In addition, each of the above embodiments can be operated in combination with each other as needed.

Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

Such programs (software modules, software) may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other It can be stored on optical storage devices, magnetic cassettes. Alternatively, it may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

In addition, the program is provided through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a communication network consisting of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in singular or plural numbers according to the specific embodiments presented. However, the singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should not be defined by the scope of the claims described below as well as those equivalent to the scope of these claims.

Claims (1)

A control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images