Methods and apparatus for measuring interference in wireless communication systems

By providing beam-related and configuration information through base stations or parent nodes, electronic devices can measure and report interference, thus solving the interference problem between IAB nodes and improving signal quality and system performance.

CN116941196BActive Publication Date: 2026-11-10SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202280020109.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-03-23
Filing Date
2022-03-21
Publication Date
2026-11-10
Estimated Expiration
2042-03-21

AI Technical Summary

Technical Problem

When a mobile terminal (MT) at an Integrated Access and Backhaul (IAB) node transmits uplink backhaul data, it may be interfered with by transmissions from another MT at an IAB node, resulting in a degraded received signal quality.

Method used

By providing beam-related and configuration information through base stations or parent nodes, electronic devices can measure and report interference. The base stations or parent nodes receive and process the interference measurement results to reduce the interference impact between IAB nodes.

Benefits of technology

Effectively measure and reduce interference between IAB nodes to improve signal quality and system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116941196B_ABST
    Figure CN116941196B_ABST
Patent Text Reader

Abstract

A method for an electronic device to report interference of a target signal transmitted from another electronic device to a base station or parent node may include: receiving beam-related information and configuration information for measuring the interference of the target signal from the base station or parent node; determining at least one direction for measuring the interference based on the beam-related information; measuring the interference of the target signal based on the received configuration information and the determined at least one direction; and sending information about the measured interference to the base station or parent node.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments described in this disclosure relate to methods and apparatus for measuring interference in wireless communication systems. Background Technology

[0002] To meet the increasing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, considerable efforts have been made to develop fifth-generation (5G) communication systems, or 5G communication systems. 5G communication systems, or 5G-pre-5G communication systems, are referred to as super 4G network communication systems or post-Long Term Evolution (LTE) systems.

[0003] To achieve high data rates, 5G communication systems are being developed for use in ultra-high frequency bands (millimeter wave) (e.g., the 60 GHz band). To mitigate path loss of radio waves and increase their propagation distance in the ultra-high frequency band, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO are being discussed for use in 5G communication systems.

[0004] To improve the system network, technologies have also been developed for advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation in 5G communication systems.

[0005] In addition, other technologies have been developed for 5G systems, such as hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM), and sliding window superposition coding (SWSC), which are advanced coding modulation (ACM) schemes, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse coded multiple access (SCMA), which are advanced access schemes.

[0006] The Internet has evolved from a human-based connectivity network to an Internet of Things (IoT) network. In human-based networks, people create and consume information, while in IoT networks, distributed configurations, including objects, exchange and process information with each other. The Internet of Everything (IoE) technology has emerged as a combination of IoT technology and technologies that process big data through connections to cloud servers. To realize IoT, sensing technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies are required. Recently, technologies for inter-object connectivity, such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC), have been researched. In the IoT environment, intelligent Internet technology services can be provided to collect and analyze data obtained from interconnected objects, thereby creating new value in human life. Through the convergence and combination of existing information technology (IT) and various industrial applications, IT can be applied to various fields, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0007] Recently, various attempts have been made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as beamforming, MIMO, and array antennas have been used to implement technologies such as sensor networks, M2M communication, and MTC. The use of cloud radio access networks (RAN) as a big data processing technology can also be considered an example of the convergence of 5G and 1oT technologies.

[0008] In addition, various studies have recently been conducted to utilize Integrated Access and Backhaul (IAB) technology. Summary of the Invention

[0009] Technical issues

[0010] When a mobile terminal (MT) of an Integrated Access and Backhaul (IAB) node transmits uplink backhaul data and another MT of an IAB node receives downlink backhaul data, the receiving MT of the IAB node may be interfered with by the transmitting MT of the IAB node. Therefore, a method and apparatus are needed for measuring interference between IAB nodes and reducing its impact.

[0011] Technical solution

[0012] According to embodiments of this disclosure, a method for an electronic device to report interference of a target signal transmitted from another electronic device to a base station or parent node includes: receiving beam-related information and configuration information for measuring interference of the target signal from the base station or parent node; determining at least one direction for measuring the interference based on the beam-related information; measuring the interference of the target signal based on the received configuration information and the determined at least one direction; and sending the measured interference information to the base station or parent node.

[0013] According to embodiments of this disclosure, a method for a base station to obtain measurement results of interference to a target signal transmitted from another electronic device includes: sending beam-related information and configuration information for measuring the interference to the target signal to the electronic device, and receiving from the electronic device information about the interference to the target signal based on at least one direction determined based on the beam-related information and based on the configuration information.

[0014] According to embodiments of this disclosure, an electronic device for reporting interference of a target signal transmitted from another electronic device to a base station or parent node includes: a transceiver configured to transmit or receive signals; and at least one processor connected to the transceiver, wherein the at least one processor is configured to receive beam-related information and configuration information from the base station or parent node, the beam-related information and configuration information being used to measure interference of the target signal, determining at least one direction for measuring the interference based on the beam-related information, measuring the interference of the target signal based on the received configuration information and the determined at least one direction, and transmitting information about the measured interference to the base station or parent node. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating an example of a wireless communication system in which integrated access and backhaul (IAB) nodes operate.

[0016] Figure 2 This is a diagram that schematically illustrates an example of resource multiplexing between backhaul and access links in an IAB node.

[0017] Figure 3 This is a diagram illustrating an example of resource multiplexing in the time domain between backhaul links and access links in an IAB node.

[0018] Figure 4 This is a diagram illustrating an example of resource multiplexing in the frequency or spatial domain between backhaul and access links in an IAB node.

[0019] Figure 5 This is a diagram that schematically illustrates the structure of an IAB node.

[0020] Figure 6This is a diagram illustrating a communication method for simultaneous transmission / reception between a mobile terminal (MT) and a distributed unit (DU) in an IAB node of a wireless communication system according to embodiments of the present disclosure.

[0021] Figure 7 This is a diagram illustrating the transmitter and receiver architecture that supports hybrid beamforming for use in new radio (NR) systems.

[0022] Figure 8a This is a diagram illustrating a detection reference signal (SRS) operation scenario according to an embodiment of the present disclosure.

[0023] Figure 8b This is a diagram illustrating an SRS operation scenario according to another embodiment of the present disclosure.

[0024] Figure 8c This is a diagram illustrating an SRS operation scenario according to another embodiment of the present disclosure.

[0025] Figure 9a This is a diagram used to describe an SRS measurement scenario in an NR system according to an embodiment of the present disclosure.

[0026] Figure 9b Yes, this is a diagram used to illustrate an SRS measurement scenario in an NR system according to another embodiment of this disclosure.

[0027] Figure 10 This is a diagram used to describe an SRS measurement scenario of an IAB node in an NR system according to an embodiment of the present disclosure.

[0028] Figure 11 This is a diagram illustrating the operation of a base station or parent IAB node in a wireless communication system according to an embodiment of the present disclosure.

[0029] Figure 12 This is a diagram illustrating the operation of a terminal or IAB node in a wireless communication system according to an embodiment of the present disclosure.

[0030] Figure 13 This is a diagram illustrating the configuration of a terminal according to an embodiment of the present disclosure.

[0031] Figure 14 This is a diagram illustrating the configuration of a base station according to an embodiment of the present disclosure.

[0032] Figure 15 This is a diagram illustrating the configuration of an IAB node according to an embodiment of the present disclosure. Detailed Implementation

[0033] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals denote the same elements in the drawings. Furthermore, detailed descriptions of known functions and configurations that may obscure key points of the present disclosure will be omitted.

[0034] While describing the embodiments in this specification, descriptions of technical content well-known in the art to which this disclosure pertains and not directly related to this disclosure may be omitted.

[0035] For ease of description, some parts may be exaggerated, omitted, or roughly shown in the accompanying drawings. Furthermore, the dimensions of each part do not perfectly reflect the actual dimensions and are not limited to the dimensions shown.

[0036] The advantages and features of this disclosure and methods for implementing it can be more readily understood by referring to the detailed description and accompanying drawings of the following embodiments. However, this disclosure is not limited to the embodiments described below and can be implemented in various other forms. According to the various embodiments, it will be understood that blocks or combinations of flowcharts in a flowchart can be executed by computer program instructions. These computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and instructions executed via the processor of the computer or programmable data processing apparatus can generate means for implementing the functions specified in the flowchart blocks. The computer program instructions can be stored in a computer-executable or computer-readable storage medium that is capable of directing a computer or another programmable data processing apparatus to perform functions in a particular manner, and the instructions stored in the computer-executable or computer-readable storage medium can also generate a manufacturing item comprising instruction units for performing the functions described in one or more flowchart blocks. Computer program instructions may also be loaded into a computer or other programmable data processing apparatus, and when a series of operations are performed in the computer, the instructions that operate the computer or other programmable data processing apparatus by generating a process executed by the computer may provide operations for performing the functions described in the flowchart blocks (one or more), or the other programmable data processing apparatus may provide operations for performing the functions described in the flowchart blocks (one or more).

[0037] Furthermore, each block can represent a module, segment, or portion of code that includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in a block can occur out of order. For example, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order, depending on the functions involved.

[0038] Here, the term "unit" or "device" as used in the embodiments means a software component or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs a specific function. However, the term "unit" or "device" is not limited to software or hardware. A "unit" or "device" can be configured in an addressable memory medium or can be configured to operate one or more processors. Thus, for example, the term "unit" or "device" can refer to components such as software components, object-oriented software components, class components, and task components, and can include processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functionality provided by components and "units" or "devices" can be associated with a small number of components and "units" or "devices," or can be divided into additional components and "devices." Furthermore, components and "units" or "devices" can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card.

[0039] Wireless communication systems have evolved from early voice-centric services to broadband systems that provide high-speed and / or high-quality packet data services, such as 3GPP's High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE Advanced (LTE-A) and LTE-Pro, 3GPP2's High Rate Packet Data (HRPD) and Ultra Mobile Broadband (UMB), and communication standards such as IEEE 802.16e.

[0040] As a representative example of a broadband wireless communication system, the LTE system employs an Orthogonal Frequency Division Multiplexing (OFDM) scheme in the downlink (DL) and a Single-Carrier Frequency Division Multiple Access (SC-FDMA) scheme in the uplink (UL). UL can be understood as the radio link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (BS) (eNode B), and DL can be understood as the radio link through which the BS transmits data or control signals to the terminal. In this multiple access scheme, the data or control information for each user can be classified such that the time-frequency resources used to transmit the data or control information for each user do not overlap, i.e., orthogonality is established, through the normal allocation and manipulation of data or control information.

[0041] As a post-LTE communication system, fifth-generation (5G) (or new radio (NR)) communication systems must be able to freely reflect the diverse needs of users and service providers; therefore, they need to simultaneously support services that meet various requirements. Services considered for 5G communication systems may include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable low latency communications (URLLC), etc.

[0042] The purpose of eMBB is to provide higher data transmission rates than those supported by LTE, LTE-A, or LTE-Pro systems. For example, in a 5G communication system, from the perspective of a base station, eMBB should be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink. Furthermore, 5G communication systems need to provide increased user-perceived data rates to terminals while delivering peak data rates. To meet this requirement, improvements to various transmit / receive technologies, including further enhancements to multiple-input multiple-output (MIMO) transmission techniques, may be necessary. Moreover, while current LTE systems use up to 20MHz of transmission bandwidth in the 2GHz band, 5G communication systems use bandwidths wider than 20MHz in the 3GHz to 6GHz or greater bands to meet the required data rates.

[0043] Furthermore, mMTC is considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To effectively deliver IoT, mMTC is needed for support for large-scale terminal access within a cell, enhanced terminal coverage, improved battery life, and reduced terminal costs. IoT requires the ability to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km). 2 This is because it connects to various sensors and devices to provide communication capabilities. Furthermore, mMTC-enabled terminals are more likely to be located in shadow areas not covered by cell coverage, such as underground within buildings due to the nature of the service; therefore, these terminals require wider coverage than other services provided by 5G communication systems. mMTC-enabled terminals should be configured as inexpensive devices and require very long battery life, such as 10 to 15 years, as it is difficult to frequently replace the terminal's battery.

[0044] Finally, URLLC stands for Cellular Wireless Communication System, which is designed for a specific purpose (mission-critical). For example, URLLC can be understood as a service used in remote control of robots or machines, industrial automation, drones, remote healthcare, or emergency alerts. Therefore, URLLC may require very low latency and very high reliability. For instance, a service supporting URLLC may require an air interface latency of less than 0.5 milliseconds (msec), while also potentially requiring 10... -5 Or even lower packet error rates. Therefore, for services that support URLLC, 5G systems need to provide shorter Transmission Time Intervals (TTIs) than those used for other services, while allocating wide resources in the frequency band to protect reliable communication links.

[0045] The three services of a 5G system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, the services can use different transmission and reception methods and different transmission and reception parameters to meet their different requirements.

[0046] In 5G systems, coverage is limited by propagation path attenuation, and base stations transmit or receive data from terminals in the 6GHz or higher frequency bands, particularly in the millimeter-wave band. While the coverage limitation can be addressed by densely arranging multiple relays (or relay nodes) along the propagation path between base stations and terminals, the cost of installing fiber optic cables for backhaul connections between relays can be significant. Therefore, instead of installing fiber optic cables between relays, the broadband radio frequency resources available in the millimeter-wave band can be used to transmit or receive backhaul data between relays, thus solving the cost problem of fiber optic cable installation and effectively utilizing the millimeter-wave band.

[0047] The technique described above, which involves transmitting / receiving backhaul data between a base station and a terminal using at least one relay node via available radio frequency resources in the millimeter-wave band, can be referred to as Integrated Access and Backhaul (IAB). Here, the relay node that transmits data to / receives data from the base station using wireless backhaul can be referred to as an IAB node. In this case, the base station may include a Central Unit (CU) and a Distributed Unit (DU), and the IAB node may include a DU and a Mobile Terminal (MT). The CU can control all DUs connected to the base station via multi-hop connections. According to various embodiments, the base station can be understood as being the same as or similar to a gNB, an IAB donor, a donor IAB, or a donor base station.

[0048] IAB nodes can use different frequency bands or the same frequency band to simultaneously receive backhaul data from the base station and send access data to the terminal, as well as receive access data from the terminal and send backhaul data to the base station. When using the same frequency band, IAB nodes can have instantaneous one-way transmit / receive characteristics (half-duplex constraint). To reduce transmit / receive delays caused by the half-duplex constraint of IAB nodes, when an IAB node transmits, it can use a method of multiplexing (e.g., frequency division multiplexing (FDM) and / or space division multiplexing (SDM)) backhaul data (e.g., if the parent IAB node, the IAB node operating as a relay node, and the child node are connected via a wireless backhaul link, uplink data from the IAB node's MT to the parent IAB node's DU and downlink data from the IAB node's DU to the child IAB node's MT) and access data to the terminal (downlink data from the IAB node to the terminal). The relationship between the parent and child IAB nodes can be found in Section 4.7 of 3GPP standard TS 38.300, Integration of Access and Backhaul. In this disclosure, a parent IAB node may simply be referred to as a parent node, and a child IAB node may simply be referred to as a child node. In other words, a parent node may be understood as being the same as or similar to a parent IAB node, and a child node may be understood as being the same as or similar to a child IAB node.

[0049] Furthermore, even when the IAB node receives data, the method of multiplexing (FDM and / or SDM) 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) can be used.

[0050] When the MT of an IAB node (e.g., IAB#1) receives a signal from the DU of its parent IAB node, interference may occur in the signal received by the MT of the IAB node due to transmissions from the MT of an access terminal or another IAB node (e.g., IAB#2) to the donor base station or the DU of another parent IAB node. In this disclosure, this interference may be referred to as MT-MT interference. Furthermore, when the MT of an IAB node (IAB#1) receives a signal from the DU of its parent IAB node, interference may occur in the signal received by the MT of the IAB node due to transmissions from the DU of another parent IAB node to the access terminal or the MT of another IAB node. In this disclosure, this interference may be referred to as DU-MT interference.

[0051] Furthermore, when the DU of IAB node (IAB#1) receives a signal from the MT of the access terminal or a child IAB node, interference may occur in the signal received by the DU of the IAB node due to transmissions from the DU of another parent IAB node to the MT of another IAB node. In this disclosure, this interference may be referred to as DU-DU interference. Additionally, when the DU of IAB node (IAB#1) receives a signal from the MT of the access terminal or a child IAB node, interference may occur in the signal received by the DU of the IAB node due to transmissions from the MT of the access terminal or another IAB node (IAB#2) to the DU of the donor base station or another parent IAB node. In this disclosure, this interference may be referred to as MT-DU interference.

[0052] Figure 1 This is a diagram illustrating an example of a wireless communication system operating an IAB node.

[0053] exist Figure 1 In this context, gNB 101 represents a base station, but is not limited to this, and can be understood as the same as or similar to an eNB, base station, donor base station, and donor IAB. IAB node #1111 and IAB node #2121 are IAB nodes that transmit / receive backhaul data in the millimeter-wave band. First terminal (UE 1) 102 can transmit / receive access data to / from gNB 101 via access link 103. IAB node #1111 can transmit / receive backhaul data to / from gNB 101 via backhaul link 104. Second terminal (UE 2) 112 can transmit / receive access data to / from IAB node #1111 via access link 113. IAB node #2121 can transmit / receive backhaul data to / from IAB node #1111 via backhaul link 114. IAB node #1111 can be understood as a higher-level IAB node than IAB node #2121 and is referred to as the parent IAB node. IAB node #2121 can be understood as a lower-level IAB node than IAB node #1111, and is referred to as a child IAB node. Third terminal (UE 3) 122 can send / receive access data to / from IAB node #2121 via access link 123. Figure 1 In this context, backhaul links 104 and 114 can use wireless backhaul links.

[0054] Next, the measurements for the terminals used in the IAB node and gNB will be described.

[0055] According to various embodiments, coordination between the gNB and IAB nodes may be required so that a terminal (e.g., a second terminal 112 or a third terminal 122) can perform measurements on a gNB that is not a serving IAB node or on a neighboring IAB node. The gNB can match measurement resources for IAB nodes with an even-hop order or for IAB nodes with an odd-hop order, and thus, resource waste can be reduced when the terminal performs measurements with respect to a gNB or a neighboring IAB node. For measuring neighboring IAB nodes, the terminal can receive configuration information for measuring the Synchronization Block (SSB) / Physical Broadcast Channel (PBCH) or for Channel State Information Reference Signal (CSI-RS) from the serving IAB node or base station via higher-layer signaling (higher-layer signaling). When the terminal is configured to perform measurements on a neighboring base station via the SSB / PBCH, the terminal can be configured to have at least two SSB / PBCH Measurement Timing Configurations (SMTCs) for each frequency of measurement resources for IAB nodes with an even-hop order or for measurement resources for IAB nodes with an odd-hop order. Upon receiving configuration information, the terminal can perform measurements on IAB nodes with an even-numbered hop order in one SMTC and on IAB nodes with an odd-numbered hop order in another SMTC.

[0056] Next, the measurement for another IAB node or gNB will be described.

[0057] Coordination between gNB and IAB nodes may be necessary for an IAB node to perform measurements on a gNB or neighboring IAB nodes. The gNB can match measurement resources for IAB nodes with an even-hop order or an odd-hop order, thus reducing resource waste when an IAB node performs measurements on a gNB or neighboring IAB nodes. For measuring neighboring IAB nodes, an IAB node can receive configuration information for measuring SSB / PBCH or CSI-RS from its parent IAB node or base station via higher-layer signaling. The parent IAB node can be referred to as the serving cell of the IAB node or the serving IAB node of the IAB node. When an IAB node is configured to perform measurements on neighboring base stations via SSB / PBCH (also known as SSB), the IAB node can be configured to have at least two SMTCs per frequency for the measurement resources of IAB nodes with an even-hop order or IAB nodes with an odd-hop order. After receiving the configuration, an IAB node can perform measurements on IAB nodes with an even-numbered hop order in one SMTC and on IAB nodes with an odd-numbered hop order in another SMTC.

[0058] Next, we will refer to Figures 2 to 4The backhaul links between base stations and IAB nodes or between IAB nodes, and the access links between base stations and terminals or between IAB nodes and terminals, are multiplexed in the radio resources in the IAB technology proposed in this disclosure.

[0059] Figure 2 This is a diagram that schematically illustrates an example of resource multiplexing between backhaul and access links in an IAB node.

[0060] Figure 2 (a) is a diagram illustrating an example of time-domain resource multiplexing between backhaul and access links in an IAB node. Figure 2 (b) is a diagram illustrating an example of frequency domain multiplexing of resources between access links and backhaul links in an IAB node.

[0061] Figure 2 (a) illustrates an example of performing time-domain multiplexing (TDM) on backhaul links 203 between base stations and IAB nodes or between IAB nodes and access links 202 between base stations and terminals or between IAB nodes and terminals in radio resource 201. Figure 2 As shown in (a), when resources are multiplexed in the time domain between the access link and the backhaul link in an IAB node, no data is sent / received between the base station and the IAB node in the time domain when the base station or the IAB node sends / receives data to / from the terminal, and no data is sent / received between the base station and the IAB node in the time domain when the base station or the IAB node sends / receives data to / from the terminal.

[0062] Next, Figure 2 (b) illustrates an example of performing frequency domain multiplexing (FDM) on backhaul links 213 between a base station and an IAB node or between IAB nodes and access links 212 between a base station and a terminal or between an IAB node and a terminal in radio resource 211. Data can be transmitted / received between a base station and an IAB node in the time domain when the base station or IAB node transmits / receives data to / from a terminal; however, due to the half-duplex constraint of IAB nodes, data transmission is possible only in the same direction. For example, a first IAB node may receive backhaul data from another IAB node or base station only in the time domain when the first IAB node receives data from a terminal. Furthermore, a first IAB node may transmit backhaul data to another IAB node or base station only in the time domain when the first IAB node transmits data to a terminal.

[0063] exist Figure 2 The examples only illustrate TDM and FDM multiplexing schemes, but spatial domain multiplexing (SDM) between access and backhaul links is also possible. In this case, simultaneous transmission / reception via SDM can be achieved on both the access and backhaul links, but... Figure 2Similar to FDM in (b), even in SDM, due to the half-duplex constraint of IAB nodes, data transmission can only occur in the same direction. For example, the first IAB node may only receive backhaul data from another IAB node or base station in the time domain when the first IAB node receives data from the terminal. Furthermore, the first IAB node may only transmit backhaul data to another IAB node or base station in the time domain when the first IAB node transmits data to the terminal.

[0064] When an IAB node initially connects to a base station or a higher-level IAB node, it can send information to the base station or higher-level IAB node regarding which multiplexing scheme—TDM, FDM, or SDM—will be used. In other words, the IAB node can send capability information about the multiplexing scheme to the base station or higher-level IAB node (e.g., the parent IAB node). Alternatively, the IAB node can receive information about the multiplexing scheme to be used from the base station or higher-level IAB node via higher-level signaling information (higher-level signals), such as system information or Radio Resource Control (RRC) information. Alternatively, the IAB node can receive information about the multiplexing scheme to be used from the base station or higher-level IAB node via a backhaul link after initial access. Alternatively, the IAB node can determine the multiplexing scheme to be used after sending capability information to the base station or higher-level IAB node. In this case, the IAB node can report to the base station or higher-level IAB node via backhaul or higher-level signaling information which multiplexing scheme will be used during a specific time slot, specific radio frame, or specific interval, and subsequently report that multiplexing scheme continuously and repeatedly.

[0065] exist Figure 2 The example primarily describes the multiplexing scheme between access links and backhaul links, but multiplexing between backhaul links can use the same scheme as between access links and backhaul links. For example, the multiplexing of the backhaul link of the MT and the backhaul link or access link of the DU in an IAB node (described below) can be achieved by... Figure 2 The solution described in the example is used to implement this.

[0066] Next, Figure 3 This is a diagram illustrating an example of time-domain resource multiplexing between backhaul links and access links in an IAB node.

[0067] Figure 3 (a) illustrates the communication process between IAB node 302 and its parent node 301, child node 303, and terminal 304. The links between nodes are described in detail; parent node 301 can communicate via the backhaul downlink L. P,DL In step 311, a backhaul downlink signal is sent to IAB node 302, and IAB node 302 can also send a backhaul uplink signal on L. PUL Node 312 sends a return uplink signal to parent node 301. IAB node 302 can access downlink L. A,DL 316 sends an access downlink signal to terminal 304, and terminal 304 can access the uplink L. A,UL Node 315 sends an access uplink signal to IAB node 302. IAB node 302 can then send an access uplink signal on the backhaul downlink L. C,DL 313 sends a backhaul downlink signal to child node 303, and child node 303 can send a backhaul uplink signal on L. C,UL 314 sends a return uplink signal to IAB node 302. Figure 3 In this context, the subscript P indicates the backhaul link with the parent node, the subscript A indicates the access link with the terminal, and the subscript C indicates the backhaul link with the child node.

[0068] It has already been described based on IAB node 302 Figure 3 The link relationships are defined, and from the perspective of child node 303, the parent node is IAB node 302, and there may be another child node not shown below child node 303. Furthermore, from the perspective of parent node 301, the child node is IAB node 302, and there may be another parent node not shown above parent node 301.

[0069] The backhaul uplink / downlink signals and access uplink / downlink signals may include at least one of data and control information, a channel for transmitting data and control information, or a reference signal required for decoding data and control information or a reference signal for determining channel information.

[0070] Figure 3 (b) shows an example where all links are multiplexed in the time domain. Figure 3 In the example, the backhaul downlink L is arranged in chronological order. P,DL 311, Backhaul downlink L C,DL 313, access downlink L A,DL 316, accessing uplink L A,UL 315, Return Uplink L C,UL 314 and return uplink L P,UL 312 is multiplexed. However, the order of the links is not limited to this, and multiplexing can be performed in another order.

[0071] Because the links are multiplexed sequentially in the time domain, signals can be transmitted from parent node 301 to child node 303 via IAB node 302, and the total time required to transmit the signal to the terminal may be longer than in another multiplexing scheme. To reduce the waiting time when the signal is finally transmitted from parent node 301 to the terminal, a method of simultaneous transmission by multiplexing at least some backhaul links or at least some backhaul links and access links in the frequency or spatial domain can be considered.

[0072] Figure 4 This is a diagram illustrating an example of resource multiplexing in the frequency or spatial domain between backhaul links and access links in an IAB node.

[0073] Reference Figure 4 Describe a method for multiplexing at least some of the backhaul links or at least some of the backhaul links and access links in the frequency domain or spatial domain to reduce latency.

[0074] First, similar to Figure 3 , Figure 4 (a) illustrates the communication process between IAB node 402 and its parent node 401, child node 403, and terminal 404. The links between nodes are described in detail; parent node 401 can communicate via the backhaul downlink L. P,DL In step 411, a backhaul downlink signal is sent to IAB node 402, and IAB node 402 can also send a backhaul uplink signal on L. P,UL In node 412, a return uplink signal is sent to parent node 401. IAB node 402 can then access downlink L. A,DL 416 sends an access downlink signal to terminal 404, and terminal 404 can access the uplink L. A,UL Node 415 sends an access uplink signal to IAB node 402. IAB node 402 can then send an access uplink signal on the backhaul downlink L. C,DL 413 sends a backhaul downlink signal to child node 403, and child node 403 can send a backhaul uplink signal on L. C,UL In node 414, a return uplink signal is sent to node 402 of the IAB. Figure 4 In this context, the subscript P indicates the backhaul link with the parent node, the subscript A indicates the access link with the terminal, and the subscript C indicates the backhaul link with the child node.

[0075] It has already been described based on IAB node 3402 Figure 4 The link relationships are defined, and from the perspective of child node 403, the parent node is IAB node 402, and there may be another child node not shown below child node 403. Furthermore, from the perspective of parent node 401, the child node is IAB node 402, and there may be another parent node above parent node 401 that is not shown.

[0076] The backhaul uplink / downlink signals and access uplink / downlink signals may include at least one of data and control information, a channel for transmitting data and control information, or a reference signal required for decoding data and control information or a reference signal for determining channel information.

[0077] Next, Figure 4 (b) shows an example of multiplexing in the frequency or spatial domain.

[0078] As mentioned above, because IAB nodes have instantaneous half-duplex constraints, the signals that can be multiplexed in the frequency or spatial domain may be limited. For example, considering the half-duplex constraint of IAB node 402, signals that can be multiplexed in the time domain and can be... Figure 4 The link transmitted by IAB node 402 can be limited to the backhaul uplink L. P,UL 412. Backhaul downlink L C,DL 413 and access downlink L A,DL 416. Therefore, when the link is multiplexed in the frequency domain or spatial domain, IAB node 402 can simultaneously transmit the backhaul uplink L. P,UL 412. Backhaul downlink L C,DL 413 and access downlink L A,DL 416, as shown by reference numeral 421 in the attached figure. Furthermore, links that can be multiplexed in the time domain and can be received by IAB node 402 can be limited to backhaul downlink L. P,DL 411, Return Uplink L C,UL 414 and access uplink L A,UL 415. Therefore, when the link is multiplexed in the frequency domain or spatial domain, IAB node 402 can simultaneously receive the backhaul downlink L. P,DL 411, Return Uplink L C,UL 414 and access uplink L A,UL 415, as shown in the attached figure 422.

[0079] exist Figure 4 The link multiplexing provided in the embodiments is merely an example, and the type and number of multiplexed links are not limited to this. Figure 4 As shown in the diagram. Clearly, of the three links multiplexed in the frequency or spatial domain, only two can be multiplexed. In other words, IAB node 402 can transmit or receive signals by multiplexing only some of the multiplexable links.

[0080] Next, the structure of the IAB node will be described.

[0081] To reduce communication network capital expenditure (CAPEX) and support various services in 5G systems (such as high-capacity transmission and low-latency, high-reliability or large-scale IoT devices), various base station architectures optimized for service requirements are being investigated. In 4G LTE systems, to reduce CAPEX and effectively handle interference control, the Cloud Radio Access Network (C-RAN) architecture has been commercialized. In this architecture, the base station's data processor and radio transceiver (Remote Radio Head (RRH)) are separated, with the data processor handling data centrally and the radio transceiver placed within the cell site. In the C-RAN architecture, optical links of the Common Radio Interface (CPRI) standard are typically used to transmit baseband digital in-phase quadrature (IQ) data from the data processor to the base station's radio transceiver. Large data capacities are required when data is transmitted to the radio transceiver. For example, a transmission rate of 614.4 Mbps is required when transmitting 10 MHz of Internet Protocol (IP) data, while a transmission rate of 1.2 Gbps is required when transmitting 20 MHz of IP data. Therefore, in 5G RAN architecture, base stations are designed with various structures by dividing them into Central Units (CUs) and Distributed Units (DUs) and applying functional partitioning to the CUs and DUs, in order to reduce the heavy load on optical links. In 3GPP, various functional partitioning options between CUs and DUs are standardized, and there are a total of eight options for functional partitioning, from Option 1 to Option 7, based on functional partitioning between or within protocol layers. The structures considered first in current 5G base station architectures are Options 2 and 7. In Option 2, the RRC layer and Packet Data Convergence Protocol (PDCP) layer are located in the CU, while the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, Physical (PHY) layer, and Radio Frequency (RF) layer are located in the DU. In Option 7, RRC, PDCP, RLC, MAC, and higher PHY layers are located in the CU, while lower PHY layers are located in the DU. This functional partitioning allows for a flexible layout with separation and transmission of NR network protocols between CUs and DUs. Therefore, cost-efficient solutions can be provided through flexible hardware implementation, and load management and tuning for real-time performance optimization can be achieved through a decoupled architecture between CU and DU. Furthermore, Network Functions Virtualization (NFV) / Software-Defined Networking (SDN) is possible, and configurable function splitting can be applied to various application examples (regarding variable latency of transport).

[0082] Reference Figure 5 Describe the structure of IAB nodes that take this functional decomposition into account. Figure 5 This is a diagram that schematically illustrates the structure of an IAB node.

[0083] exist Figure 5In this context, gNB 501 includes a CU and a DU, and the IAB node includes an MT and a DU. The MT is configured to perform terminal functions for sending / receiving data with a parent node in the backhaul link, and the DU is configured to perform base station functions for sending / receiving data with a child node in the backhaul link. The terminal functions of the IAB node, i.e., the MT of the IAB node, can substantially follow the NR standard procedures applicable to access terminals. For example, the NR standard procedures associated with the initial and random access procedures, as well as the configuration and instruction procedures for data transmission / reception, followed by the access terminal, can be applied to the MT. The MT of the IAB node can access the DU of the parent node (i.e., the serving cell corresponding to the DU) according to the standard procedures, receive configuration and instructions from the DU of the parent node and the CU of the base station, and send / receive data by sending relevant messages.

[0084] exist Figure 5 In this configuration, IAB node #1 502 is wirelessly connected to gNB 501 via a single hop, and IAB node #2 503 is wirelessly connected to gNB 501 via IAB node #1 502 via a two-hop connection.

[0085] like Figure 5 As shown, the CU of gNB 501 can control not only the DU of gNB 501, but also the DUs of all IAB nodes (i.e., IAB node #1 502 and IAB node #2 503) wirelessly connected to gNB 501 (operations 511 and 512). The CU of gNB 501 can allocate radio resources to the DU, allowing the DU to transmit / receive data together with the MT of the lower IAB node. Radio resources can be allocated by sending radio resources to the DU via physical layer signals or higher layer signals (e.g., system information or RRC information) through the interface of the F1 Application Protocol (F1AP). F1AP can refer to the 3GPP TS 38.473 standard. Here, radio resources can include downlink time resources, uplink time resources, or flexible time resources.

[0086] The configuration of radio resources will be described in detail below based on IAB node #2 503. Downlink time resources are used for transmitting downlink control / data and signals from the DU of IAB node #2 503 to the MT of the lower IAB node. Uplink time resources are used for receiving uplink control / data and signals from the MT of the lower IAB node by the DU of IAB node #2. Flexible time resources are resources that can be used by the DU as either downlink or uplink time resources, and the downlink control signal of the DU can instruct the MT of the lower IAB node how to use the flexible time resources. Upon receiving a downlink control signal, the MT of the lower IAB node can determine whether to use the flexible time resources as downlink or uplink time resources. When no downlink control signal is received, the MT of the lower IAB node does not perform transmit / receive operations. In other words, the MT may not monitor the downlink control channel in the resource, or may not measure the signal in the resource. For downlink time resources, uplink time resources, and flexible time resources, two different types (or three different types including NA time resources) can be indicated from CU to DU.

[0087] The first type is soft type, and the CU of gNB 501 can utilize soft type downlink time resources, uplink time resources, or flexible time resources to configure the DU of IAB node #2503 using F1AP (the interface between the CU and DU). Here, for the configured soft type resources, IAB node #1 502, as the parent node of IAB node #2 503, can explicitly (e.g., via downlink control indicator (DCI) format) or implicitly indicate whether the resource of IAB node #2 503, as a child node, is available or unavailable. When a specific resource is indicated to be available, IAB node #2 503 (e.g., the DU of IAB node #2 503) can use the specific resource to perform data transmission / reception together with the MT of the lower IAB node. In other words, when the resource is a downlink resource, the DU of IAB node #2 503 can perform transmission by using the resource, or when the resource is an uplink resource, the DU of IAB node #2 503 can perform reception by using the resource. When a specific resource is indicated to be unavailable, IAB node #2 503 cannot use the resource for data transmission / reception with the MT of the lower IAB node. In other words, the DU of IAB node #2 503 may not be able to use the resource to transmit or receive.

[0088] The method for indicating the availability of soft-type resources using a DCI format will now be described in detail. The DCI format according to embodiments may include availability indicators for indicating the availability of one or more consecutive uplinks, downlinks, or flexible symbols.

[0089] To receive the DCI format, IAB node #2 503 can receive at least one of the following information in advance via higher-layer signals from the CU or parent node, along with the cell ID of the DU of IAB node #2 503: the location information of the availability indicator in the DCI format indicating the availability of IAB node #2, a table indicating the availability of time resources corresponding to multiple time slots, and the mapping relationship of availability indicators. The value (or indicator) indicating the availability of consecutive uplink symbols, downlink symbols, or flexible symbols in a time slot, and the meaning of the value (or indicator), can be shown in Table 1 below.

[0090] [Table 1]

[0091]

[0092] When this availability indicator is indicated from the parent node to IAB node #2 503 via DCI format and IAB node #2 503 receives the indication, the following method can be considered as the method by which IAB node #2 503 interprets the availability in relation to the downlink, uplink, or flexible time resources configured from the CU.

[0093] The first method is to include the same number of availability indicators in the availability indicator included in the expected DCI format of the IAB node #2 503 as the number of soft-type slots configured by the continuous symbols configured by the CU. According to this method, the IAB DU can determine that availability is applied only to slots that include soft types.

[0094] The second method is that the number of availability indicators included in the availability indicator in the expected DCI format of IAB node #2 503 is the same as the number of all time slots configured in the CU, i.e., the number of all time slots including soft type, hard type, or unavailable (NA) type. Simultaneously, according to this embodiment, the DU of IAB node #2 503 can determine that availability is applied only to time slots including soft type, and that the indicated availability is not applied to time slots that only include hard type or NA type without soft type.

[0095] In both the first and second methods, the DU of IAB node #2 503 can be expected to indicate a value whose meaning matches the downlink resources, uplink resources, or flexible resources configured in the CU. For example, when only downlink soft resources or downlink hard resources exist in the time slot, the DU of IAB node #2 503 can be expected to indicate only value 1 in Table 1. Therefore, the DU of IAB node #2 503 can be expected not to have a value indicating the availability of uplink soft resources included in the values ​​in Table 1.

[0096] Furthermore, the DU of IAB node #2 503 can determine, in addition to the value indicating the availability of flexible resources, whether downlink or uplink resources are available among the flexible resources configured by at least the CU. For example, for flexible soft resources or flexible hard resources, the DU of IAB node #2 503 can be expected to indicate value 1 or 2 in Table 1 instead of value 4. In this case, the DU of IAB node #2 503 can determine whether to use flexible resources only for uplink or only for downlink based on the indication of the parent node, rather than based on the determination of IAB node #2 503 itself.

[0097] Furthermore, the DU of IAB node #2 503 can anticipate that the value 0 in Table 1 can be indicated even in any soft, hard, or NA resource configured by the CU. In this case, the DU of IAB node #2 503 can determine that the resource is not available for existing soft or hard resources configured by the CU. Similarly, as in the case of an NA resource type configured by the CU, the DU of IAB node #2 503 can assume that the resource cannot be used by the DU of IAB node #2 503 for data transmission / reception with the MT of the lower IAB node unless the resource is subsequently indicated to be available by the DCI format. Then, when the resource is indicated to be available again by the DCI format, as configured by the CU and received by the DCI format, the DU of IAB node #2 503 can use the resource.

[0098] The second type is hard type, and the resource is always used between DU and MT. In other words, the DU of IAB node #2503 can perform transmission when the resource is a downlink time resource and reception when the resource is an uplink resource, regardless of the transmission / reception operation of the MT of IAB node #2503. When the resource is a flexible resource, transmission or reception can be performed based on the determination of the DU of IAB node #2503 (i.e., matching the DCI format indicating whether the flexible resource of the lower IAB node's MT is a downlink resource or an uplink resource).

[0099] The third type is unused or NA type, and the DU of IAB node #2 503 does not use resources to send / receive data with MT.

[0100] When downlink time resources, uplink time resources, flexible time resources, or reserved time resources are received from the CU to the DU via a higher signal, these types are received together.

[0101] Reference Figure 5 The DU of gNB 501 performs normal base station operations, and the DU can schedule data transmission / reception by controlling the MT of IAB node #1 502 (operation 521). The DU of IAB node #1 502 performs normal base station operations, and the DU can schedule data transmission / reception by controlling the MT of IAB node #2 503 (operation 522).

[0102] Based on the radio resources allocated from the CU, the DU can instruct the radio resources used to transmit / receive data with the MT of the lower IAB node. The configuration of radio resources can be sent to the MT via system information, higher-layer signals, or physical layer signals. Here, radio resources can include downlink time resources, uplink time resources, flexible time resources, or reserved time resources. Downlink time resources are resources used to transmit downlink control / data signals from the DU to the MT of the lower IAB node. Uplink time resources are resources used by the DU to receive uplink control / data signals from the MT of the lower IAB node. Flexible time resources are resources that can be used by the DU as either downlink or uplink time resources, and the downlink control signals of the DU can instruct the MT of the lower IAB node how to use the flexible time resources. Upon receiving a downlink control signal, the MT can determine whether to use the flexible time resource as a downlink time resource or an uplink time resource. When no downlink control signal is received, the MT may not perform a transmit / receive operation. In other words, the MT may not monitor or decode the downlink control channel in the resource, or may not measure the signal in the resource.

[0103] Downlink control signals can be used to notify the MT in a combination of higher-layer and physical-layer signals. The MT can receive the signaling and determine the time slot format in a specific time slot. The time slot format can generally be configured to begin and end with a downlink symbol, with flexible symbols in between. The configuration of the time slot format can be understood, for example, as a structure with a DFU sequence. When using only this time slot format, the DU of the IAB node can perform downlink transmissions from the beginning of the time slot, but because the MT of the IAB node is configured by the parent node using the time slot format (i.e., the DFU structure), it may be difficult to perform uplink transmissions simultaneously. Such details are shown in time slot format indices 0 to 55 in Tables 2 to 5. A time slot format configured to begin and end with a downlink symbol, with flexible symbols in between, can also be considered. Such details are shown in time slot format indices 56 to 96 in Tables 2 to 5. The time slot formats shown in Tables 2 to 5 can be sent to the MT using downlink control signals and can be configured in the DU from the CU using F1AP.

[0104] [Table 2]

[0105]

[0106] [Table 3]

[0107]

[0108] [Table 4]

[0109]

[0110] [Table 5]

[0111]

[0112] Reserved time resources are resources where the DU cannot transmit / receive data with a lower MT, and where the MT does not perform transmit / receive operations. In other words, the MT may not monitor or decode the downlink control channel in the resource, or may not measure the signal in the resource.

[0113] The MT in an IAB node can be controlled by the DU in a higher IAB node and send / receive data via receive scheduling, and the DU in an IAB node can be controlled by the CU of the gNB 501. In other words, the MT and DU in an IAB can be controlled by different entities and may be difficult to coordinate in real time.

[0114] Figure 6 This is a diagram illustrating a communication method for simultaneous transmission / reception between the MT and DU in an IAB node of a wireless communication system according to embodiments of the present disclosure. Figure 6 In the description, simultaneous transmission / reception between the MT and DU in the IAB node can represent simultaneous transmission / reception according to... Figure 2 The multiplexing scheme described herein is MT for transmitting or receiving and DU for transmitting or receiving.

[0115] Reference Figure 6 The first embodiment 601 illustrates that both the MT and DU transmit their respective signals within an IAB node. In the first embodiment 601, the signal transmitted by the MT of the IAB node can be received by the DU of the parent node or base station via the backhaul uplink, such as... Figures 3 to 5 As shown. Meanwhile, in the first embodiment 601, the signal sent by the DU of the IAB node can be received by the MT of the child node via the backhaul downlink, or by the access terminal via the access downlink, as shown. Figures 3 to 5 As shown.

[0116] The second embodiment 602 illustrates that both the MT and DU receive their respective signals within an IAB node. In the second embodiment 602, the signal received by the MT of the IAB node can be a signal transmitted from the DU of the parent node or base station via the backhaul downlink, such as... Figures 3 to 5 As shown. Furthermore, in the second embodiment 602, the signal received by the DU of the IAB node can be a signal sent by the MT of the child node via the backhaul uplink or by the access terminal via the access uplink, such as... Figures 3 to 5 As shown.

[0117] The third embodiment 603 illustrates that the MT and DU in the IAB node receive or transmit their respective signals. In other words, in the third embodiment 603, the MT in the IAB node can receive its signal, while the DU in the IAB node can transmit its signal. The signal received by the MT of the IAB node in the third embodiment 603 can be a signal transmitted from the DU of the parent node or base station via the backhaul downlink, such as... Figures 3 to 5 As shown. Furthermore, in the third embodiment 603, the signal sent by the DU of the IAB node can be received by the MT of the child node via the backhaul downlink, or by the access terminal via the access downlink, as shown. Figures 3 to 5 As shown.

[0118] The fourth embodiment 604 illustrates the MT and DU in an IAB node transmitting or receiving their respective signals. In other words, in the fourth embodiment 604, the MT in the IAB node can transmit its signal, and simultaneously, the DU in the IAB node can receive its signal. In the fourth embodiment 604, the signal transmitted by the MT of the IAB node can be received by the DU of the parent node or base station via the backhaul uplink, such as... Figures 3 to 5As shown. Furthermore, in the fourth embodiment 604, the signal received by the DU of the IAB node can be a signal sent by the MT of the child node via the backhaul uplink or by the access terminal via the access uplink, such as... Figures 3 to 5 As shown.

[0119] Next, the operation of the access terminal transmitting a sounding reference signal (SRS) in the NR will be described. As mentioned above, the MT of the IAB node can substantially follow standard procedures applicable to the access terminal. Therefore, unless otherwise stated, the operation of the access terminal presented in the accompanying drawings or embodiments described in this disclosure can be applied in the same or similar way to the MT of the IAB node, and the operation of the base station can be considered as the operation of the parent node or donor base station.

[0120] Unlike LTE, which operates in 6 GHz or lower frequency bands, NR can extend its operating scenarios to higher frequency bands up to 100 GHz. Channel attenuation increases exponentially with frequency band, thus requiring technologies to overcome this attenuation in higher frequency bands.

[0121] Beamforming is a representative technique for effectively overcoming attenuation in high-frequency bands without significantly increasing the number of base stations required in NR systems compared to existing technologies (LTE / LTE-A). For example, when an NR system in the 4 GHz to 6 GHz band supports up to four multi-beams to ensure coverage similar to that of an LTE / LTE-A system in the 2 GHz to 2.5 GHz band, a coverage extension of approximately 3 dB can be achieved. Furthermore, the spacing between antennas required for beamforming is proportional to the carrier wavelength; therefore, the antenna array factor can be significantly improved as the band increases. Thus, when the NR system's band is 6 GHz or higher, coverage extension of tens to hundreds of times can be achieved by using tens to hundreds of antenna elements. However, when applying existing channel estimation and reporting, along with existing transmission mechanisms, to such a large number of antenna elements, the complexity of the terminal or base station and the channel reporting burden can increase impractically.

[0122] In this respect, the NR system considers a hybrid beamforming structure.

[0123] Figure 7 This is a diagram illustrating a transmitter and receiver architecture that supports hybrid beamforming and can be used in NR systems.

[0124] refer to Figure 7 The left diagram includes the transmitter structure, via N T ×L-dimensional digital precoding (e.g., digital baseband processing 710), information about the L MIMO layers from the first layer (layer #1) 700 to the Lth layer (layer #L) 705 can be distributed from the transmitter (e.g., base station (gNB)) to the Lth layer (panel #1 or RF chain #1) 715 to the Lth layer (layer #L) 705.N T panel (panel #N) T Or RF chain #N T )720 of N T Each panel (or RF chain) can be used. Digital precoding can be performed in the baseband. The signals assigned to panels 715 and 720 are then converted into analog signals by a digital-to-analog converter (DAC) and up-converted to a carrier frequency band fc. The up-converted signals can then be formed into a transmit beam in a specific direction by a transmit (TX) analog beamforming unit 725 and transmitted through the antenna elements. Here, from the terminal's viewpoint, the antenna elements of panels 715 and 720 can be virtualized and treated as a single antenna port by transmitting the analog beam, and the terminal does not need to perform channel estimation on individual antenna elements.

[0125] refer to Figure 7 The diagram on the right includes a receiver structure. The receiver, such as a terminal, can receive wireless signals from multiple receive beams using NR panels (or RF chains) 735 to 740, each panel including multiple antenna elements. Here, the receive beam in a specific direction can be applied by a receive (RX) analog beamforming unit 730 to the wireless signals received through the antenna elements of each of the panels 735 to 740. The received signal after beamforming can be down-converted to baseband and then converted to a digital signal by an analog-to-digital converter (ADC). The digital signal is then transmitted via an L×N... R A digital equalizer (e.g., digital baseband processing 745) distributes information to the L MIMO layers from the first layer (layer #1) 750 to the Lth layer (layer #L) 755.

[0126] In this hybrid beamforming system, when the number of antenna elements for each transmit panel is KT and the number of antenna elements for each receive panel is KR, the channel estimation complexity is reduced by a factor of 1 / (KTKR) compared to an all-digital precoding system.

[0127] The reduction in channel estimation complexity of hybrid beamforming systems is a result of applying appropriate transmit or receive beams by the transmit or receive panel. Therefore, in real-world environments, technologies are needed for transmitters or receivers to obtain information about the appropriate transmit / receive beams or their directions.

[0128] In the downlink, the transmit / receive beam direction can be determined according to the following process.

[0129] First, the base station determines candidate transmit beam directions and transmits multiple SSBs or CSI-RS resources from CSI-RS resources to the terminal using these candidate transmit beam directions. The base station can receive reports from the terminal regarding the index of preferred SSBs or preferred CSI-RS resources and obtain information about the terminal's preferred transmit beam direction. Here, the base station may not explicitly notify the terminal of the transmit beam candidate direction information. Next, the terminal can receive downlink signals by applying different receive beams to resources that use the same transmit beam, and determine the preferred transmit beam direction by comparing the reception quality of the receive beams. The terminal can report the preferred receive beam direction and preferred transmit beam direction for downlink to the base station, and the base station can schedule downlink and perform transmissions by referring to the referenced receive and transmit beam directions reported by the terminal.

[0130] Here, the determination of the preferred receive beam direction and paired transmit beam directions, or the quality of received downlink data, may be affected by interference from terminals (or another IAB node) from the same cell or different cells. As mentioned above, at the beginning of this disclosure, the interference can be MT-MT interference, DU-MT interference, DU-DU interference, or MT-DU interference. Therefore, this disclosure proposes a method for a terminal (or the MT of an IAB node) receiving downlink data to measure interference with respect to a specific receive beam direction and report the measurement results to the base station (or donor base station or parent node).

[0131] In the uplink, it is difficult for a terminal to determine the overall network situation. Therefore, when a terminal arbitrarily determines the uplink beam direction, the cell transmission capacity may be adversely affected. Therefore, the base station can instruct the terminal on information regarding beam direction, precoding information, or information regarding the analog beam to be used when transmitting uplink channels (e.g., Physical Random Access Channel (PRACH)) or reference signals (e.g., SRS).

[0132] In the uplink, RACH, SRS, or the uplink (UL) demodulation reference signal (DMRS) can be considered as uplink beam training signals used to determine the uplink beam orientation. Therefore, RACH and UL DMRS are not periodic. The base station can use SRS measurements to detect the preferred uplink beam orientation.

[0133] In addition to SRS configuration information, the NR system can use additional information fields, such as SRS resource activation / deactivation signaling, and can support periodic, semi-persistent, and aperiodic SRS transmissions. Depending on the SRS transmission type (e.g., periodic, semi-persistent, or aperiodic SRS transmission), some information fields of the SRS configuration information can be omitted.

[0134] Furthermore, in NR systems, cell-specific SRS configurations are not applied; instead, UE-specific SRS configurations can be provided to offer flexibility.

[0135] For periodic SRS transmissions that apply UE-specific SRS configurations, for example, the slot offset and SRS period can be used for each terminal, determined based on higher-layer parameters available through RRC configuration. In other words, in NR systems, slot-based SRS time resources can be configured instead of SRS subframes.

[0136] Because the subcarrier spacing (SCS) of the data channel supports various parameter sets in NR systems, SRS transmission is configured based on time slots. For example, in an NR system, the SCS of the data channel can be 15 kHz, 30 kHz, 60 kHz, or 120 kHz. Therefore, by using time slot-based SRS periods, the base station can use SRS periods that are scalable according to the parameter set. Furthermore, another feature of time slot-based SRS period configuration is that SRS transmissions are distinguishable within each symbol.

[0137] In other words, NR uses SRS periods at the time slot unit level, instead of differentiating one or two symbols in the uplink pilot time slot (UpPTS) of the subframe unit as in LTE. Therefore, the NR system can assign one, two, or four symbols for SRS transmission within a single time slot, and can assign time slot-level SRS periods regardless of the number of symbols. Furthermore, unlike LTE, NR can support SRS periods of up to 640 time slots to accommodate wider periods.

[0138] In NR systems, for periodic SRS transmissions, the same SRS configuration table can be assigned to each terminal for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD). The SRS configuration tables for FDD and TDD may include columns indicating the SRS period and time slot offset. In NR systems, 0.5 / 1 / 2 / 5 / 10 ms are supported as UL / DL configuration switching periods, and 15 / 30 / 60 / 120 kHz are supported as the SCS for the data channel. Therefore, considering the number of time slots that can be allocated within the UL / DL configuration switching period, SRS periods that are multiples of 1 / 2 / 4 / 8 / 16 time slots can be additionally configured.

[0139] In an NR system, a terminal can receive one or more SRS resource sets via higher-layer signaling. Each SRS resource set includes one or more SRS resources, and its maximum number K can be determined based on the UE's capabilities. The use of SRS resource sets can be configured for beam management, codebook, non-codebook, or antenna switching, and the SRS resource sets can be configured according to the configured use. For example, when SRS use is configured for antenna switching, one SRS resource set can be configured for each of multiple SRS resource sets, and the number of SRS resources included in the SRS resource set can vary depending on the antenna switching method. SRS resources from different SRS resource sets that have the same time-domain operation within the same bandwidth portion (BWP) can be used simultaneously.

[0140] In aperiodic SRS, at least one information field within the DCI field can be used to select at least one from the SRS resource set.

[0141] The following shows the SRS parameters configured semi-statically by higher-level signaling.

[0142] -sRS-ResourceId: Indicates the SRS resource configuration identifier.

[0143] -nrofSRS-Ports: Indicates the number of SRS ports.

[0144] -resourceType: Indicates whether the SRS transmission is periodic, semi-persistent, or aperiodic.

[0145] -periodicityAndOffset-p (or periodicityAndOffset-sp): Indicates the slot-level SRS period and slot offset for periodic or semi-persistent SRS resources. SRS resources in the same SRS resource set can have the same slot-level period. For aperiodic configuration SRS resource sets, the slot-level offset is defined by slotOffset as a higher-level parameter.

[0146] -resourceMapping: Defines the OFDM symbol position of an SRS resource within a time slot. It can include startPosition, indicating the start OFDM symbol in the SRS resource; nrofSymbols, indicating the number of consecutive OFDM symbols available for SRS transmission; and repetitionFactor, indicating SRS repetition.

[0147] -freqHopping: Provides parameters for SRS frequency hopping.

[0148] -freqDomainPosition,freqDomainShift: Used to determine the frequency domain location of the SRS resource.

[0149] -transmissionComb: Includes parameters used to generate the SRS sequence to be transmitted on the SRS resource.

[0150] -sequenceId: Indicates the SRS sequence ID.

[0151] -SpatialRelationInfo: Provides configuration for the beam direction or spatial relationship between the reference RS and the target SRS. This configuration is set as the reference RS along with the serving cell ID, CSI-RS index, and transmitted SRS information (resource ID and uplink BWPID) from one of the SSB indices received from the specific serving cell, and therefore the target SRS can be transmitted using the same spatial transmission filter (or beam direction) as the spatial filter used to receive or transmit the reference RS.

[0152] In an NR-MIMIO system, the base station sends configuration information to the terminal for SRS transmission to support hybrid beamforming. The terminal can transmit multiple SRSs in different directions using the configuration information. The base station informs the terminal of rank information determined based on the received SRSs, transmission precoding information for the uplink, and / or the SRS transmit beam direction (i.e., the SRS index), and the terminal can transmit uplink transmission signals based on the information obtained from the base station.

[0153] Figure 8a , Figure 8b and Figure 8c This is a diagram illustrating various operational scenarios of SRS. (Refer to...) Figures 8a to 8c Describe the operational process during SRS transmission.

[0154] refer to Figure 8a The gNB 803 can be configured as a UE 800 with beaming in one direction. In this disclosure, a gNB configured with beaming / precoding in one direction may include not applying beaming / precoding or applying wide beaming. When the SRS transmission type is periodic SRS or semi-persistent SRS, the UE 800 can transmit SRS 807 based on the SRS period and slot offset, and when the SRS transmission type is aperiodic SRS, the UE 800 can transmit SRS 807 based on an SRS request 805 within the DCI (a defined time after the SRS request is detected). Here, additional information for beaming / precoding may not be required for the transmission of SRS 807.

[0155] Reference Figure 8bThe serving cell's gNBs 813 and 814 can be configured with a UE 810 having beamforming in one or more directions, and the UE 810 can transmit one or more SRS 817 and SRS 818 beamformed in one or more directions. Here, each gNB can be a Transmit / Receive Point (TRP), and when assuming the MT of the IAB node replaces the UE, each TRP can be the TRP of the parent node or donor base station. For example, beamforming of SRS#0 817 can be performed in the direction of gNB 813, and beamforming of SRS#1 818 can be performed in the direction of gNB 814. Here, SRS#0 817 and SRS#1 818 can be configured to have corresponding SRS resources and / or antenna ports. In this respect, with Figure 8a In different situations, gNB 813 and gNB 814 can indicate SRS requests and SRS beam / precoding information 815 to UE 810.

[0156] refer to Figure 8c The gNB 823 can be configured with UE 820 beams in different directions, and UE 820 can transmit multiple SRS 827, SRS 828, and SRS 829 beams formed in different directions. For example, the gNB 823 can configure UE 820 to transmit SRS#0 827, SRS#1 828, and SRS#2 829 by applying different beam / precoding to UE 820. Therefore, stable communication can be performed through beam / precoding diversity even when UE 820 has high mobility.

[0157] For example, UE 820 can provide channel information to gNB 823 via SRS#2 829 at time A, and via SRS#0 827 at time A+α. In this respect, compared to... Figure 8a In different situations, gNB 823 can indicate SRS request and SRS beam / precoding information 825 to UE 820.

[0158] The foregoing primarily describes SRS transmission from an uplink channel / signal transmitted from a terminal; however, this disclosure can be applied in the same or similar way to another uplink channel / signal, such as PRACH or UL DMRS, just as it is applied to SRS transmission.

[0159] The NR standard includes techniques to support duplex flexibility in paired spectrum (for FDD) and unpaired spectrum (for TDD), and is specifically designed to use a dynamic TDD approach. In multi-cell environments, when dynamic resource allocation is allowed for each cell, cross-link interference (CLI) can occur between the uplink and downlink. In systems supporting dynamic TDD, the duration configured by base station A in the downlink can overlap in the time domain with the duration configured by base station B in the uplink. In this case, uplink signals (e.g., SRS) transmitted by terminal B in the cell of neighboring base station B may interfere with terminal A receiving downlink signals in the cell of base station A, and this interference is called UE-to-UE CLI. This UE-to-UE CLI degrades the data reception quality of terminal A, thus requiring a technique to mitigate UE-to-UE CLI. Similarly, CLI caused by MT-to-MT, DU-to-MT, DU-to-DU, and MT-to-DU interference can occur as described above, even in the case of operating IAB nodes.

[0160] To mitigate UE-to-UE CLI interference, each terminal can perform interference measurement and L3 level reporting, and the base station can perform dynamic UL / DL resource allocation based on the interference measurement reports from the terminals.

[0161] Various measurement methods can be considered for the terminal to measure interference, such as CLI. The first method is the SRS Reference Signal Received Power (RSRP) method for measuring the RSRP from the SRS, and the second method is the CLI Received Signal Strength Indicator (RSSI) method for measuring the received power of interference in a specific resource. When the terminal measures the SRS-RSRP, it can receive SRS measurement configuration information, similar to SRS configuration information, from the base station of the serving cell. The SRS measurement information may include information for measuring interference in a specific beam direction. The terminal can measure the SRS for a specific beam direction based on the SRS measurement configuration information and obtain the interference measurement results for each beam direction. The following will describe in detail, with reference to Figures 9 and 10, how the base station instructs the measurement of interference in a specific beam direction, and how the terminal measures and reports the interference in that specific beam direction according to this instruction.

[0162] Figure 9a and Figure 9b This is a diagram describing the SRS measurement in the NR system.

[0163] Figure 9a The scenario shown is for SRS measurement between adjacent UE 900 and UE 901 in different cells.

[0164] refer to Figure 9aConsider two adjacent gNBs, 905 and 915, with UE A 900 and UE B 901 respectively connected to gNB 905 and gNB 915. UE A 900 is connected to gNB A 905, and UE B 901 is connected to gNB B 915. In other words, gNB A 905 is the serving base station for UE A 900, and gNB B 915 is the serving base station for UE B 901. Here, gNB A 905 can be configured via higher-layer signaling or instructed by physical channel signals to send SRS 903, and UE A 900 can send SRS 903 in response to configuration or instructions from gNB A 905. Figure 9a For convenience, SRS is transmitted in one beam direction, but various SRS transmission schemes, including embodiments that transmit SRS through multiple beam directions, can be applied. Figure 9a .

[0165] Simultaneously, gNB B 915 can configure UE B 901 to measure SRS 903 in multiple beam directions via higher-layer signaling, and UE B 901 can measure SRS 903 transmitted by UE A 900 according to the SRS measurement configuration provided from gNB B 915. UE B 901 can measure SRS 903 in multiple beam directions and report the measurement results of SRS 903 to gNB B 915. Multiple configuration information required for reporting the measurement results (e.g., parameters indicating at least transmission resources and transmission time) can be provided to UE B 901 from gNB B 915 via higher-layer signaling. Figure 10 Specific embodiments of this disclosure will then be described, such as a configuration for performing interference measurements in multiple beam directions, a method for measuring interference via the configured beam directions, and a method for reporting the measured interference.

[0166] Figure 9b The scenario shown is for SRS measurements between adjacent UEs 910 and 911 within a cell.

[0167] Reference Figure 9b Consider UE A 910 and UE B 911 connected to a gNB 925. UE A 910 is connected to the gNB 925, and UE B 911 is connected to the gNB A 925. Here, the gNB A 925 can be configured via higher-layer signaling or instructed via physical channel signals to send SRS 913, and UE A 910 can send SRS 913 in response to configuration or instructions from the gNB A 925. Figure 9bFor convenience, SRS is transmitted in one beam direction, but various SRS transmission schemes, including embodiments that transmit SRS through multiple beam directions, can be applied to... Figure 9b .

[0168] Simultaneously, gNB A 925 can configure UE B 911 to measure SRS CLI via higher-layer signaling, and UE B 911 can measure SRS 913 transmitted by UE A 910 according to the SRS measurement configuration provided from gNB A 925. UE B 911 can measure SRS 913 in multiple beam directions and report the measurement results of SRS 913 to gNB A 925. Multiple configuration pieces of information required for reporting the measurement results (e.g., parameters indicating at least transmission resources and transmission time) can be provided to UE B 911 from gNB A 925 via higher-layer signaling. Figure 10 Specific embodiments of this disclosure will then be described, such as a configuration for performing interference measurements in multiple beam directions, a method for measuring interference via the configured beam directions, and a method for reporting the measured interference.

[0169] Figure 10 This is a diagram describing the SRS measurements of the IAB nodes in the NR system. Figure 10 The scenario shown is for SRS measurements between adjacent IAB nodes 1001 and 1002 in different cells.

[0170] Reference Figure 10 When two different IAB nodes 1001 and 1002 are adjacent to each other, the case of transmitting SRS and measuring SRS interference between the IAB nodes is considered. In embodiments of this disclosure, the transmission of SRS or measurement of SRS interference by IAB nodes is described; however, unless otherwise stated, embodiments of this disclosure may determine that a specific RS is transmitted by the DU or MT of an IAB node, and that the DU or MT of the IAB node is configured to receive and measure and report RS interference.

[0171] Although not shown, IAB node A 1001 can wirelessly connect to a donor base station or parent node. For ease of description, the donor base station or parent node to which IAB node A 1001 connects can be referred to as gNB A. IAB node B 1002 can wirelessly connect to gNB A, or wirelessly connect to a donor base station or parent node different from gNB A. For ease of description, the donor base station or parent node different from gNB A can be referred to as gNB B. Here, gNB A can be configured via higher-layer signaling or instructed by physical channel signals for IAB node A 1001 to transmit SRS1011. IAB node A 1001 can transmit SRS1011 according to the configuration or instructions from gNB A. Figure 10 For convenience, SRS is transmitted in one beam direction, but various SRS transmission schemes, including embodiments that transmit SRS through multiple beam directions, can be applied in the same or similar way. Figure 10 .

[0172] Simultaneously, the gNB B can configure the IAB node B 1002 via higher-layer signaling to measure SRS CLI in multiple beam directions. The IAB node B 1002 can measure SRS1011 transmitted by the IAB node A 1001 according to the SRS measurement configuration provided from the gNB B. The IAB node B 1002 can measure SRS1021 in multiple beam directions and report the measurement results of SRS1021 to the gNB B. For example, parameters indicating at least transmission resources and transmission time can be provided from the gNB B to the IAB node B 1002 via higher-layer signaling. Specific embodiments of this disclosure will now be described, such as configurations for performing interference measurements in multiple beam directions, methods for measuring interference via the configured beam directions, and methods for reporting the measured interference.

[0173] <Report on Preferred Transmit and Receive Beam Directions in Multiple Beam Directions>

[0174] The base station can obtain the preferred transmit or receive beam directions for each SSB, RS, and channel from the terminal. Information regarding the transmit and receive beam directions can be obtained indirectly from the terminal by mapping the SSB receive beam direction to the corresponding PRACH transmit beam direction, or by obtaining reports of the preferred transmit and receive beam directions for each RS or channel from the terminal. These reports can be transmitted from the terminal to the base station via the uplink control channel or the uplink data channel.

[0175] <Configuration for interferometry in multiple beam directions>

[0176] As a first method, at least one specific receive beam direction for interference measurement can be included in a higher configuration of the resource configuration that includes the RS for interference measurement. For example, when the RS for interference measurement is an SRS, the SpatialRelationInfo parameter in the SRS resource configuration for interference measurement can include information about the receive beam direction, enabling interference measurement to be performed via a specific receive beam direction. This information can be used, along with a specific serving cell ID, to configure one of the SSB index received from the serving cell, the CSI-RS index, and the transmitted SRS information (resource ID and uplink BWP ID) as a reference RS. Interference with the target SRS can be measured using the same spatial filter (or beam direction) used when receiving or transmitting the reference RS. Alternatively, the reference RS can be configured as the reference RS used in the PDCCH received by the serving cell. Specifically, the reference RS can be configured as an RS corresponding to type d in qcl-Type, where type d corresponds to the quasi-co-address (QCL) assumption of the lowest index CORESET (e.g., the lowest CORESET ID in the CORESET ID configured in the controlResourceSetId parameter) in the active downlink BWP of the serving cell. Interference with the target SRS can be measured using the same spatial filter (or beam direction) used when transmitting or receiving the reference RS. Alternatively, the reference RS can be configured as the reference RS used in the PDSCH received by the serving cell. Specifically, when the terminal does not configure any CORESET in the active downlink BWP of the serving cell, the reference RS can be configured as an RS configured with qcl-Type corresponding to type d in the active TCI state of the lowest index applicable to the PDSCH in the active downlink BWP of the serving cell. Interference with the target SRS can be measured using the same spatial filter (or beam direction) used when transmitting or receiving the reference RS. Alternatively, by configuring a specific RS not mentioned above or an RS used for the channel as a reference RS, interference with the target SRS can be measured by using the same spatial filter (or beam direction) used when receiving or transmitting the reference RS.

[0177] As a second method, information regarding the specific receive beam direction used for interference measurement can be included in the downlink control information of the downlink control channel. The base station can transmit the downlink control channel by including the specific receive beam direction information for interference measurement, and the terminal can receive the downlink control channel and obtain the information regarding the specific receive beam direction for interference measurement within the downlink control information. The terminal can then measure the interference based on the specific receive beam direction.

[0178] By configuring multiple receive beam directions from the base station to the terminal via a higher signal for interference measurement, beam direction information can be indicated via the downlink control channel for all or a partial set of the multiple receive beam directions. The multiple receive beam directions may include configuring one of the SSB index, CSI-RS index, and transmitted SRS information (resource ID and uplink BWP ID) as a reference RS, as described in the first method, or configuring a reference RS associated with PDCCH or PDSCH reception in the first method.

[0179] Interferometric measurement methods in multi-beam directions

[0180] The terminal can receive beam direction configuration for interference measurement from the base station, and measure the interference received by the terminal based on the beam direction. (See Figure 9 or...) Figure 10 As shown, when measuring interference received in a specific beam direction, a terminal or IAB node can generate interference measurement results for each receiving beam direction. For example, when the receiving beam directions configured in a terminal are A, B, and C, and interference is measured in each beam direction according to time intervals (configured via a higher signal or defined by a standard specification), the terminal can avoid mixing interference received in A, B, and C. In other words, a measurement result for beam direction A can be generated using only the interference received in A, a measurement result for beam direction B can be generated using only the interference received in B, and a measurement result for beam direction C can be generated using only the interference received in C. Examples of methods for generating measurement results may include averaging the measurements received in each cycle.

[0181] Next, when an IAB node (specifically, its MT) measures interference in multiple beam directions, transmit / receive collisions may occur between the IAB node's DU and MT, potentially adversely affecting interference measurements (and causing significant delays). Transmit / receive collisions may also occur between the IAB node's DU and MT when the IAB node reports half-duplex constraints to the donor base station or parent node, and methods to mitigate the impact on interference measurements in this situation will be described. See detailed reference. Figure 10 When the MT of IAB node A 1001 transmits SRS1011 in time slot i, the transmission of MT may conflict with the reception of uplink data (or uplink control channel / uplink RS) by the DU of IAB node A 1001 in time slot i. Even if time slot i is configured as hard type and the DU of IAB node A 1001 has a higher transmit / receive priority than MT, IAB node A 1001 can still prioritize the transmission of SRS1011 by MT. Furthermore, in Figure 10 In time slot i, when the MT of IAB node B 1002 receives and measures SRS1021, the MT's reception may conflict with the transmission of downlink data (or downlink control channel / downlink RS) by the DU of IAB node B 1002 in time slot i. Even if time slot i is configured as hard-type and the DU of IAB node B 1002 has a higher transmission / reception priority than the MT, IAB node B 1002 can still prioritize the reception and measurement of SRS1021 by the MT.

[0182] <Report on Interference Measurement Results Measured in Multiple Beam Directions>

[0183] Terminals or IAB nodes can report information about interference measurement results measured in multiple beam directions to base stations, donor base stations, or parent nodes. Interference measurement information may include interference measurement result values, the receive beam direction in which the interference result was measured, and / or the transmit beam direction associated with the receive beam direction. Information about interference measurement results can be sent to base stations or IAB nodes via uplink data channels or uplink control channels. The time and resource configuration required to receive measurement result reports from base stations, donor base stations, or parent nodes can be determined.

[0184] Interference Measurement Method When Beam Direction for Interference Measurement is Not Configured

[0185] The terminal can receive beam direction configuration for interference measurement from the base station and measure the interference received by the terminal based on the beam direction. However, when the terminal does not receive beam direction configuration for interference measurement, the terminal's operation on the beam for interference measurement can be defined as follows. As a first method, the terminal can measure interference in all directions instead of a specific beam direction. Here, the terminal can generate measurement results for all beam directions received and measured by the terminal. Examples of methods for generating measurement results could include averaging the measured values ​​received per cycle regardless of the beam direction. As a second method, the specific beam direction (or default beam direction) for which the terminal wants to measure interference can be defined or predetermined in the standard specification and indicated to the terminal from the base station. For example, one of the SSB index, CSI-RS index, or transmitted SRS information (resource ID and uplink BWP ID) described in the first method of <Configuration for Interference Measurement in Multiple Beam Directions> can be defined as a reference RS in the standard specification or predetermined as a reference RS and indicated to the terminal from the base station. Alternatively, a reference RS associated with PDCCH or PDSCH reception in the first method can be defined or predetermined according to standard specifications, and the reference RS can be indicated from the base station to the terminal.

[0186] Figure 11This is a diagram illustrating the operation of a base station or parent IAB node in a wireless communication system according to an embodiment of the present disclosure.

[0187] Reference Figure 11 In operation 1101, according to embodiments of the present disclosure, the base station or parent IAB node (or parent node) can receive interference measurement-related information from the terminal or IAB node and send necessary information to the terminal or IAB node. The interference measurement-related information may include, for example, information about the preferred transmit or receive beam direction of the terminal. The necessary information may include, for example, at least one of the following: interference measurement configuration information in multiple beam directions, information about the direction of a specific receive beam, parameters indicating transmission resources for the RS (e.g., SRS) used for interference measurement, parameters indicating the transmission time of the RS (e.g., SRS) used for interference measurement, parameters indicating resources required for measurement result reporting, parameters indicating the time required for measurement result reporting, or information about the default beam direction. In operation 1102, according to embodiments of the present disclosure, the base station or parent IAB node can receive measured interference information.

[0188] Figure 12 This is a diagram illustrating the operation of a terminal or IAB node in a wireless communication system according to an embodiment of the present disclosure.

[0189] Reference Figure 12 In operation 1201, the terminal or IAB node can send information related to interference measurement to the base station or parent IAB node (or parent node) and receive required information from the base station or parent IAB node. The information related to interference measurement may include, for example, information about the preferred transmit or receive beam direction of the terminal. Required information may include, for example, at least one of the following: interference measurement configuration information, information about the direction of a specific receive beam, parameters indicating transmission resources for the RS (e.g., SRS) used for interference measurement, parameters indicating the transmission time of the RS (e.g., SRS) used for interference measurement, parameters indicating the resources required for measurement result reporting, parameters indicating the time required for measurement result reporting, or information about the default beam direction. In operation 1202, according to embodiments of this disclosure, the terminal or IAB node can measure interference by referring to the required information for interference measurement. In operation 1203, according to embodiments of this disclosure, the terminal or IAB node can report information about the measured interference measurement results to the base station or parent IAB node.

[0190] Figure 13 and Figure 14 Configurations of a terminal and a base station for implementing embodiments of this disclosure are shown respectively. Furthermore, Figure 15The configuration of the IAB node device is shown. The transmission / reception method of the base station (donor base station) for transmitting / receiving with the IAB node via mmWave in the backhaul link when transmitting / receiving signals through the IAB node in the 5G communication system described in the embodiments is shown, as well as the transmission / reception method of the terminal for transmitting / receiving with the IAB node in the access link. Furthermore, the configurations of the base station, terminal, and IAB node can operate according to their respective embodiments to perform the transmission / reception methods.

[0191] Figure 13 This is a diagram illustrating the configuration of a terminal according to an embodiment of the present disclosure.

[0192] refer to Figure 13 The terminal 1300 disclosed herein may include a terminal processor 1301, a terminal transceiver 1302, and a memory 1303. According to various embodiments, the configuration of the terminal 1300 is not limited to... Figure 13 For example, terminal 1300 may include additional components not shown, and some components may be implemented in a different manner than those shown. For example, terminal transceiver 1302 may be implemented as a terminal transmitter and a terminal receiver.

[0193] Terminal processor 1301 can be based on the above Figures 1 to 12 Each or a combination of embodiments of this disclosure controls a series of processes that terminal 1300 can operate. For example, according to embodiments of this disclosure, terminal processor 1301 can control the transmission / reception of an access link with a base station or IAB node. According to various embodiments, terminal processor 1301 can be understood as a processor. Terminal transceiver 1302 can transmit / receive signals to / from a base station. The signals may include at least one of control information and data. In this regard, terminal transceiver 1302 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency. Furthermore, terminal transceiver 1302 can receive signals via a wireless channel and output them to terminal processor 1301, and transmit signals output from terminal processor 1301 via a wireless channel. Memory 1303 may store data processed by terminal processor 1301 or transmitted by terminal transceiver 1302.

[0194] Figure 14 This is a diagram illustrating the configuration of a base station (donor base station) according to an embodiment of the present disclosure.

[0195] refer to Figure 14 The base station 1400 disclosed herein may include a base station processor 1401, a base station transceiver 1402, and a memory 1403. According to various embodiments, the configuration of the base station 1400 is not limited to... Figure 14For example, base station 1400 may include additional components not shown, and some components may be implemented in a different manner than those shown. For example, base station transceiver 1402 may be implemented as a base station transmitter and a base station receiver.

[0196] The base station processor 1401 can be based on the above Figures 1 to 12 Each or a combination of embodiments of this disclosure controls a series of processes that the base station 1400 can operate. For example, according to embodiments of this disclosure, the base station processor 1401 can control access link transmission / reception and backhaul link transmission / reception with IAB nodes. According to various embodiments, the base station processor 1401 can be understood as a processor. The base transceiver 1402 can transmit / receive signals to / from terminals or IAB nodes. These signals may include at least one of control information and data. In this regard, the base transceiver 1402 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency. Furthermore, the base transceiver 1402 can receive signals via a wireless channel and output them to the base station processor 1401, and transmit signals output from the base station processor 1401 via a wireless channel. The memory 1403 can store data processed by the base station processor 1401 or transmitted by the base transceiver 1402.

[0197] Figure 15 This is a diagram illustrating the configuration of an IAB node according to an embodiment of the present disclosure.

[0198] refer to Figure 15 The IAB node 1500 disclosed herein may include a base station function processor 1501, a base station function transceiver 1502, and a memory 1503 for transmitting / receiving with a lower (or child) IAB node via a (wireless) backhaul link. Furthermore, the IAB node may include a terminal function processor 1511, a terminal function transceiver 1512, and a memory 1513 for initial access to a higher (or parent) IAB node and / or donor base station, transmitting / receiving higher-layer signals before backhaul link transmission / reception, and transmitting / receiving with the higher (or parent) IAB node and donor base station via a (wireless) backhaul link. According to various embodiments, the configuration of the IAB node 1500 is not limited to... Figure 15For example, IAB node 1500 may include additional components not shown, and some components may be implemented in a different manner than those shown. For example, terminal function transceiver 1502 may be implemented as a terminal function transmitter and a terminal function receiver, and base station function transceiver 1502 may be implemented as a base station function transmitter and a base station function receiver. Memory 1503 may store data processed by base station function processor 1501 or transmitted through base station function transceiver 1502. Memory 1504 may store data processed by terminal function processor 1511 or transmitted through terminal function transceiver 1512.

[0199] According to the embodiments of this disclosure described above, the base station function processor 1501 of the IAB node can control a series of processes, enabling the IAB node to operate like a base station and, for example, to perform the functions of the DU of the IAB node. For example, according to embodiments of this disclosure, the base station function processor 1501 can control the transmission / reception of the access link with the terminal and the transmission / reception of the backhaul link with the lower IAB node. According to embodiments of this disclosure, the base station function transceiver 1502 can be referred to as a first transceiver. The first transceiver can transmit / receive signals to / from the lower (or sub) IAB node and the terminal. These signals may include at least one of control information and data. In this regard, the first transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency. Furthermore, the first transceiver can receive signals via a wireless channel and output them to the base station function processor 1501, and transmit signals output from the base station function processor 1501 via a wireless channel.

[0200] According to the embodiments of this disclosure described above, the terminal function processor 1511 of an IAB node can control a series of processes that enable a lower (or child) IAB node to operate like a terminal for sending / receiving data with a donor base station or a higher (or parent) IAB node, and can, for example, perform the MT functions of the aforementioned IAB node. For example, according to embodiments of this disclosure, the terminal function processor 1511 can control the sending / receiving of data with the donor base station and / or the higher (or parent) IAB node via a (wireless) backhaul link. According to embodiments of this disclosure, the terminal function transceiver 1512 can be referred to as a second transceiver. The second transceiver can send / receive signals to / from the donor base station and the higher IAB node. These signals may include at least one of control information and data. In this regard, the second transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency. Furthermore, the second transceiver can receive signals via a wireless channel and output them to the terminal function processor 1511, and transmit signals output from the terminal function processor 1511 via a wireless channel.

[0201] At the same time, including Figure 15 The base station function processor 1501 and the terminal function processor 1511 of the IAB node can be integrated and implemented as an IAB node processor. In this case, the IAB node processor can jointly control the functions of DU and MT within the IAB node. The base station function processor 1501, the terminal function processor 1511, and the IAB node processor can be implemented as at least one processor. The first transceiver and the second transceiver can be provided separately or can be implemented as an integrated transceiver.

[0202] According to embodiments of this disclosure, a method performed by an electronic device to report interference of a target signal transmitted from another electronic device to a base station or parent node includes: receiving configuration information and beam-related information for measuring interference of the target signal from the base station or parent node; determining at least one direction for measuring the interference based on the beam-related information; measuring the interference of the target signal based on the received configuration information and the determined at least one direction; and sending information about the measured interference to the base station or parent node.

[0203] According to an embodiment, beam-related information may be included in resource configuration information for electronic devices received from a base station or parent node. According to an embodiment, the method may further include: determining a reception direction of at least one reference signal based on the beam-related information; and determining at least one direction for measuring interference based on the determined reception direction of the at least one reference signal.

[0204] According to an embodiment, beam-related information can be included in downlink control information received from a base station or parent node.

[0205] According to an embodiment, information about the measured interference may include at least one interference measurement result for each of at least one direction. According to an embodiment, for each of at least one direction, the at least one interference measurement result may include the average value of values ​​measured over a specified period.

[0206] According to an embodiment, the electronic device may be an integrated access and backhaul (IAB) node including a distributed unit (DU) and a mobile terminal (MT), and at a first time point, the receiving operation of the MT for measuring interference may have a higher priority than the transmitting operation of the DU.

[0207] According to embodiments of this disclosure, a method performed by a base station to obtain measurement results of interference to a target signal transmitted from another electronic device includes: sending beam-related information and configuration information for measuring the interference to the target signal to the electronic device, and receiving from the electronic device information about the interference to the target signal based on at least one direction determined based on the beam-related information and based on the configuration information.

[0208] According to an embodiment, beam-related information can be included in resource configuration information for an electronic device, which is then sent to the electronic device. According to an embodiment, the receiving direction of at least one reference signal can be determined based on the beam-related information, and at least one direction can be determined based on the determined receiving direction of the at least one reference signal.

[0209] According to an embodiment, beam-related information can be included in the downlink control information sent to the electronic device.

[0210] According to an embodiment, information about the measured interference may include at least one interference measurement result for each of at least one direction. According to one embodiment, for each of at least one direction, the at least one interference measurement result may include an average of values ​​measured over a specified period.

[0211] According to embodiments of this disclosure, an electronic device for reporting interference of a target signal transmitted from another electronic device to a base station or parent node includes: a transceiver configured to transmit or receive signals; and at least one processor connected to the transceiver, wherein the at least one processor is configured to receive configuration information and beam-related information for measuring interference of the target signal from the base station or parent node, determine at least one direction for measuring the interference based on the beam-related information, measure the interference of the target signal based on the received configuration information and the determined at least one direction, and transmit information about the measured interference to the base station or parent node.

[0212] According to an embodiment, beam-related information may be included in downlink control information received from a base station or parent node, or in resource configuration information for electronic devices.

[0213] The embodiments of this disclosure are provided merely to facilitate the description of the technical content of this disclosure and to promote understanding of this disclosure, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that various modifications can be made based on this disclosure. Furthermore, the embodiments of this disclosure can be combined with each other as needed.

Claims

1. A method for a terminal in a wireless communication system to perform cross-link interference (CLI) measurement, the method comprising: Receive higher-layer signaling from the base station, the higher-layer signaling including configuration information for one or more Sound Reference Signal-Reference Signal Received Power (SRS-RSRP) measurement resources; Determine whether parameters are configured in the configuration information for the one or more SRS-RSRP measurement resources, the parameters including information associated with one or more receive beams for the CLI measurement; In the case where the configuration information for the one or more SRS-RSRP measurement resources includes parameters that include information associated with one or more receiving beams for the CLI measurement: Identify the receiving beams for the CLI measurement resources based on the indication of the information associated with the one or more receiving beams used for the CLI measurement; Based on the CLI measurement resources, and by performing the CLI measurement through the identified receiving beam; and In the case where the parameters including information associated with one or more receive beams for the CLI measurement are not configured in the configuration information for the one or more SRS-RSRP measurement resources: The received beam used for the CLI measurement resources is identified as a beam associated with Physical Downlink Control Channel (PDCCH) reception or Physical Downlink Shared Channel (PDSCH) reception; Based on the CLI measurement resources, the CLI measurement is performed using the identified receiving beam; Send a CLI measurement report to the base station, wherein the CLI measurement report includes at least one CLI measurement result.

2. The method as described in claim 1, wherein, The CLI measurement report also includes information about the received beam, which is associated with the corresponding CLI measurement result, for each of at least one CLI measurement result.

3. The method as described in claim 1, wherein, The identified receiving beam for the CLI measurement resource is a receiving beam for receiving a reference signal, and the identification of the receiving beam is based on the information associated with one or more receiving beams for the CLI measurement, or based on the beam associated with the PDCCH reception or the PDSCH reception.

4. The method of claim 3, wherein, The reference signal is configured as a quasi-co-located QCL type D and corresponds to the QCL assumption of the control resource set CORESET, which has the lowest index in the active downlink bandwidth portion (BWP) of the cell.

5. The method of claim 1, wherein, The at least one CLI measurement result includes the average value of the received beam measured for the time period, which is associated with the at least one CLI measurement result.

6. A method for a base station in a wireless communication system to receive a cross-link interference (CLI) measurement report from a terminal, the method comprising: Determine whether to configure parameters in the configuration information for one or more probe reference signal-reference signal received power (SRS-RSRP) measurement resources, the parameters including information associated with one or more receive beams used for CLI measurements; Send higher-layer signaling to the terminal, the higher-layer signaling including the configuration information for the one or more SRS-RSRP measurement resources; as well as Receive a CLI measurement report from the terminal, wherein the CLI measurement report includes at least one CLI measurement result; When the configuration information for the one or more SRS-RSRP measurement resources includes parameters that include information associated with one or more receiving beams for the CLI measurement, the CLI measurement is performed via a receiving beam for the CLI measurement resource, the receiving beam being indicated by information associated with the one or more receiving beams for the CLI measurement. If the parameters including information associated with one or more receive beams for the CLI measurement are not configured in the configuration information for the one or more SRS-RSRP measurement resources, the CLI measurement is performed by a receive beam associated with the Physical Downlink Control Channel (PDCCH) reception or the Physical Downlink Shared Channel (PDSCH) reception.

7. The method of claim 6, wherein, The CLI measurement report also includes information about the beam, which is associated with the corresponding CLI measurement result, for each of at least one CLI measurement result.

8. The method of claim 6, wherein, The at least one CLI measurement result includes the average value of the received beam measured for the time period, which is associated with the at least one CLI measurement result.

9. A terminal for performing cross-link interference (CLI) measurements in a wireless communication system, the terminal comprising: transceiver; At least one processor is connected to the transceiver; as well as At least one memory, communicatively coupled to the at least one processor, the memory storing instructions that are executed by the at least one processor to cause the terminal to perform: Receive higher-layer signaling from the base station, the higher-layer signaling including configuration information for one or more Sound Reference Signal-Reference Signal Received Power (SRS-RSRP) measurement resources; Determine whether parameters are configured in the configuration information for the one or more SRS-RSRP measurement resources, the parameters including information associated with one or more receive beams for the CLI measurement; In the case where the configuration information for the one or more SRS-RSRP measurement resources includes parameters that include information associated with one or more receiving beams for the CLI measurement: Identify the receiving beams for the CLI measurement resources based on the indication of the information associated with the one or more receiving beams used for the CLI measurement; Based on the CLI measurement resources, and by performing the CLI measurement through the identified receiving beam; and In the case where the parameters including information associated with one or more receive beams for the CLI measurement are not configured in the configuration information for the one or more SRS-RSRP measurement resources: The received beam used for the CLI measurement resources is identified as a beam associated with Physical Downlink Control Channel (PDCCH) reception or Physical Downlink Shared Channel (PDSCH) reception; Based on the CLI measurement resources, the CLI measurement is performed using the identified receiving beam; Send a CLI measurement report to the base station, wherein the CLI measurement report includes at least one CLI measurement result.

10. The terminal as described in claim 9, wherein, The CLI measurement report also includes information about the received beam, which is associated with the corresponding CLI measurement result, for each of at least one CLI measurement result.

11. The terminal as claimed in claim 9, wherein, The identified receiving beam for the CLI measurement resource is a receiving beam for receiving a reference signal, and the identification of the receiving beam is based on the information associated with one or more receiving beams for the CLI measurement, or based on the beam associated with the PDCCH reception or the PDSCH reception.

12. The terminal as claimed in claim 11, wherein, The reference signal is configured as a quasi-co-located QCL type D and corresponds to the QCL assumption of the control resource set CORESET, which has the lowest index in the active downlink bandwidth portion (BWP) of the cell.

13. The terminal as described in claim 9, wherein, The at least one CLI measurement result includes the average value of the received beam measured for the time period, which is associated with the at least one CLI measurement result.

Citation Information

Patent Citations

  • Uplink (UL) beam management enhancement for full-duplex systems

    WO2020237650A1