WO2026010116A1 - Method and apparatus for measuring and reporting cross-link interference in wireless communication system - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. More specifically, the present disclosure relates to a method performed by a terminal in a wireless communication system, wherein the method may comprise the steps of: receiving, from a base station, a radio resource control (RRC) message including configuration information for measurement of cross-link interference (CLI); performing measurement on the basis of the configuration information; and transmitting, to the base station, a report of a result of the measurement via a layer 1 (L1) message.

Description

Method and device for measuring and reporting cross-link interference in wireless communication systems

The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for measuring and reporting cross-link interference in a wireless communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

In addition, standardization of wireless interface architecture/protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture/services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

The present disclosure provides a method and apparatus for measuring and reporting cross-link interference in a wireless communication system, thereby providing a method for a base station to more accurately identify interference caused by cross-link.

The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

A method performed by a terminal of a wireless communication system according to embodiments of the present disclosure may include the steps of receiving an RRC (radio resource control) message including configuration information for measurement of crosslink interference (CLI) from a base station, performing measurement based on the configuration information, and transmitting a report of the measurement result to the base station via an L1 (layer 1) message.

According to an embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

FIG. 1 is a diagram illustrating the structure of a wireless communication system according to embodiments of the present disclosure.

FIG. 2 is a diagram illustrating a user plane wireless protocol structure of a wireless communication system according to embodiments of the present disclosure.

FIG. 3 is a diagram illustrating a control plane wireless protocol structure of a wireless communication system according to embodiments of the present disclosure.

FIGS. 4a, 4b, 4c, and 4d are diagrams illustrating TDD and SBFD communication methods according to embodiments of the present disclosure.

FIGS. 5a and 5b are diagrams illustrating a method for DUs and CUs within the same base station to share TDD pattern information and SBFD pattern information to anticipate inter-cell CLI according to embodiments of the present disclosure.

FIGS. 6A and 6B are diagrams illustrating how CUs of different base stations share TDD pattern information or SBFD pattern information to anticipate inter-cell CLI according to embodiments of the present disclosure.

FIG. 7 is a diagram illustrating a method for a terminal to measure and report CLI using an L3 measurement reporting framework according to embodiments of the present disclosure.

FIG. 8 is a diagram illustrating a method for a terminal to measure and report CLI using an L1 measurement reporting framework according to embodiments of the present disclosure.

FIG. 9 is a diagram illustrating a CLI measurement report triggering event I1 based on one absolute threshold according to embodiments of the present disclosure.

FIG. 10 is a diagram illustrating a CLI measurement report triggering event based on an offset according to embodiments of the present disclosure.

FIG. 11 is a diagram illustrating a CLI measurement report triggering event based on two absolute thresholds according to embodiments of the present disclosure.

FIGS. 12a, 12b and 12c illustrate a method of setting multiple measurement targets in one measurement target resource according to embodiments of the present disclosure.

FIG. 13 is a diagram illustrating the structure of a base station according to embodiments of the present disclosure.

FIG. 14 is a diagram illustrating the structure of a terminal according to embodiments of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

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

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, a detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

In explaining the embodiments of the present disclosure, the main target is New Radio (NR), which is a wireless access network, and the core network, packet core 5G System, or 5G Core Network, or NG Core (Next Generation Core) in the 5G mobile communication standard specified by 3GPP (3rd Generation Partnership Project), a mobile communication standard standardization organization. However, the main gist of the present disclosure can be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this will be possible at the discretion of a person skilled in the art of the present disclosure.

For convenience of explanation, some terms and names defined in the 3GPP standards (standards for 5G, NR, LTE, or similar systems) may be used below. However, the present disclosure is not limited by these terms and names, and can be equally applied to systems conforming to other standards.

Hereinafter, terms used in the description to identify connection nodes, terms referring to network objects (network entities), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms used in the present disclosure, and other terms referring to objects with equivalent technical meanings may be used.

Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be in an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. In addition, in the embodiment, the '~part' may include one or more processors.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

In addition, standardization of radio interface architecture/protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) to simplify random access procedures is also in progress, and standardization of system architecture/services for 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.

Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

FIG. 1 is a diagram illustrating the structure of a wireless communication system according to embodiments of the present disclosure.

Referring to FIG. 1, a wireless access network of a wireless communication system (hereinafter referred to as NR or 5G) may be configured to include a next-generation base station (new radio node B, hereinafter referred to as NR gNB, gNB or base station) (120) and an NR CN (110, new radio core network). A user terminal (new radio user equipment, hereinafter referred to as NR UE or terminal) (150) may access an external network through the NR gNB (120) and the NR CN (110).

In Fig. 1, the NR gNB (120) may correspond to the eNB (140) of the LTE system. The NR gNB (120) is connected to the NR UE (150) via a wireless channel and may provide a service superior to that of the eNB (140). In a wireless communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and the NR gNB (120) may be responsible for this. One NR gNB (120) can typically control multiple cells. In order to implement ultra-high-speed data transmission compared to LTE, a bandwidth greater than the maximum bandwidth of LTE can be used, and beamforming technology can be additionally grafted using the OFDM method as a wireless access technology. In addition, an Adaptive Modulation and Coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal can be applied. The NR CN (110) can perform functions such as mobility support and QoS settings. The NR CN (110) is a device that handles various control functions as well as mobility management functions for terminals and can be connected to multiple base stations. In addition, the wireless communication system can also be linked with the LTE system, and the NR CN (110) can be connected to the MME (130) through a network interface. The MME (130) can be connected to the eNB (140).

FIG. 2 is a diagram illustrating a user plane wireless protocol structure of a wireless communication system according to embodiments of the present disclosure.

Referring to FIG. 2, the user plane wireless protocol of the wireless communication system may be composed of SDAP (211), PDCP (212), RLC (213), MAC (214), and/or PHY (215) in the terminal (210). The base station (220) may be composed of SDAP (221), PDCP (222), RLC (223), MAC (224), and/or PHY (225). In the present disclosure, the term “may be composed of” may be replaced with the term “may include.” For example, the user plane wireless protocol of the wireless communication system may be composed of SDAP (211), PDCP (212), RLC (213), MAC (214), and/or PHY (215) in the terminal (210).

The functions of SDAP (211, 221) may include at least some of the following functions, but are not limited thereto.

- Mapping between a QoS flow and a data radio bearer

- Marking QoS flow ID (QFI) in both DL and UL packets

The main functions of PDCP (212, 222) may include, but are not limited to, some of the following functions.

- Transfer of data (user plane or control plane)

- Maintenance of PDCP sequence numbers (PDCP SNs)

- Header compression and decompression using the ROHC protocol

- Header compression and decompression using EHC protocol

- Compression and decompression of uplink PDCP SDUs (DEFLATE based UDC only)

- Ciphering and deciphering

- Integrity protection and integrity verification

- Timer-based SDU discard

- Routing for split bearers (For split bearers, routing)

- Duplication

- Reordering and in-order delivery

- Out-of-order delivery

- Duplicate discarding

The main functions of RLC (213, 223) may include, but are not limited to, some of the following functions.

- Transfer of upper layer PDUs

- Sequence numbering independent of the one in PDCP (UM and AM)

- Error Correction through ARQ (AM only)

- Segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs

- Reassembly of SDU (AM and UM)

- Duplicate Detection (AM only)

- RLC SDU discard (AM and UM)

- RLC re-establishment

- Protocol error detection (AM only)

The main functions of MAC (214, 224) may include at least some of the following functions, but are not limited thereto.

- Mapping between logical channels and transport channels

- Multiplexing of MAC SDUs from one or more logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels

- Demultiplexing of MAC SDUs belonging to one or more logical channels (demultiplexing of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels)

- Scheduling information reporting

- Error correction through HARQ

- Logical channel prioritization

- Priority handling between overlapping resources of one UE

The PHY layer (215, 225) can encode and modulate upper layer data to generate OFDM symbols, convert them into RF band signals, and transmit them via an antenna. In addition, the PHY layer (215, 225) can demodulate and decode received OFDM symbols and transmit them to the upper layer.

FIG. 3 is a diagram illustrating a control plane wireless protocol structure of a wireless communication system according to embodiments of the present disclosure.

Referring to FIG. 3, the control plane wireless protocol of the wireless communication system may be composed of RRC (311), PDCP (312), RLC (313), MAC (314), and/or PHY (315) in the terminal (310). It may be composed of RRC (321), PDCP (322), RLC (323), MAC (324), and/or PHY (325) in the base station (320).

The functions of RRC (311, 321) may include at least some of the following functions.

- Broadcast of System Information related to AS and NAS

- Paging initiated by 5GC or NG-RAN

- Establishment, maintenance, and release of an RRC connection between the UE and NG-RAN, including: Addition, modification, and release of carrier aggregation; Addition, modification, and release of dual connectivity in NR or between E-UTRA and NR.

- Security functions including key management

- Establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs)

- Terminal mobility support (Mobility functions including: Handover and context transfer; UE cell selection and reselection and control of cell selection and reselection; Inter-RAT mobility.)

- QoS management functions

- UE measurement reporting and control of the reporting

- Detection of and recovery from radio link failure

- NAS message transfer (NAS message transfer to/from NAS from/to UE)

The main functions of PDCP (312, 322), RLC (313, 323), MAC (314, 324), and/or PHY (315/325) may follow the example of FIG. 2.

FIGS. 4a, 4b, 4c, and 4d are diagrams illustrating TDD and SBFD communication methods according to embodiments of the present disclosure.

Referring to FIG. 4a, in a wireless communication system, a TDD method may be used to transmit or receive downlink (DL) (401, 402, 403, 406, 407, 408) or uplink (UL) (405, 410) in a frequency band (bandwidth part) used by a base station corresponding to all symbols included in a specific slot. In addition, there may exist special slots (404, 409) having flexible symbols that can be configured to transmit and receive DL from some symbols included in one slot, UL from the remaining part of symbols, and DL or UL from the remaining part of symbols according to instructions from the base station. Of course, there may also exist a flexible slot in which all symbols in one slot are flexible.

Since the TDD method cannot transmit or receive DL and UL simultaneously, there may be a disadvantage in that the interval between DL transmissions or UL transmissions becomes longer. For example, it takes one slot and five symbols from the last DL reception (symbol 8) of the special slot (404) to symbol 0 of slot 5 (406) to receive the next DL. In addition, it takes three slots and 11 symbols from the last UL transmission of slot 4 (405) to symbol 12 of slot 8 (409) to transmit the next UL.

To solve these shortcomings, a subband full duplex (SBFD) method can be introduced in which a subband transmitting DL and a subband transmitting UL exist simultaneously at a specific point in time (slot or symbol), as shown in Fig. 4b.

Referring to Fig. 4b, the SBFD can be composed of a DL subband (421), a UL subband (422), and a guard band (423), and the guard band (422) can be positioned to reduce interference between the DL subband (421) and the UL subband (423). When the number of subbands is configured to be minimal, one DL subband, one UL subband, and one guard band can be configured. In addition, the subband can be configured by using two or more of the same subbands, such as slot 6 (417) or slot 7 (418). This subband configuration is from the perspective of transmission and reception of the base station, and one terminal can only perform DL reception using the DL subband, or only UL transmission using the UL subband.

Referring to FIG. 4c, when a terminal performs transmission (433) in a UL subband, there may be intra-cell UE-to-UE CLI (cross link interference) that causes interference (434) to a terminal performing reception (432) using a DL subband in a nearby frequency of the same slot (431) or symbol.

Referring to FIG. 4d, if the subband settings of the same frequency or adjacent frequencies are different at the same time in different cells (441, 442), inter-cell UE-to-UE CLI may exist in which the transmission (444) of the UL subband interferes (445) with the DL subband (443). Such inter-cell UE-to-UE CLI may occur due to different TDD UL/DL settings in existing TDD communication.

In order to anticipate inter-cell CLI, DU (distributed unit) and CU (central unit) within the same base station, or CU and CU of different base stations can share TDD pattern information, as described below in FIGS. 5 and 6.

FIGS. 5a and 5b are diagrams illustrating a method for DUs and CUs within the same base station to share TDD pattern information and SBFD pattern information to anticipate inter-cell CLI according to embodiments of the present disclosure.

Referring to FIG. 5A, a CU (502) of a base station (501) can serve at least one DU (503, 504), and each DU (503, 504) can serve at least one cell (505, 506, 507, 508). Each cell (505, 506, 507, 508) can have a different TDD or SBFD pattern depending on the service purpose. The TDD pattern or SBFD pattern of the cells being served within one DU can be directly set to the DU or each cell, and this can be set via an OAM (operation and management) interface.

DU (503, 504) can establish an F1AP connection (510, 511) with CU (502) to exchange information through the F1 interface.

FIG. 5b below illustrates F1AP message transmission between one CU (511) and one DU (511). Referring to FIG. 5b, the DU (512) can transmit an F1 SETUP REQUEST message (513) to the CU (511) for F1AP connection, and the CU (511) receiving the F1 SETUP REQUEST (513) can respond with an F1 SETUP RESPONSE (514). When the information of the cell served by the DU is updated (515), the DU (512) can transmit a GNB-DU CONFIGURATION UPDATE message (516) through the F1AP to notify the CU of the change. The DU (512) can recognize when the information of the cell served is updated through the OAM interface.

When information of a neighboring cell is updated (517), the CU (511) can transmit a GNB-CU CONFIGURATION UPDATE message (518) via F1AP to notify the DU (512) of the change. The CU (511) can recognize when information of a neighboring cell is updated via the XnAP interface. The information update of a neighboring cell is described in Fig. 6.

The F1AP message (e.g., F1 SETUP REQUEST (513), GNB-DU CONFIGURATION UPDATE (515)) transmitted by the DU (512) may include at least one piece of Served Cell Information or Neighbor Cell Information. The Served Cell Information may include TDD information and SBFD information of the cell being served by the DU (512) transmitting the F1AP message, and may be expressed in the form of a pattern and period of UL and DL slots or symbols.

The F1AP message transmitted by the CU (511) (e.g., GNB-CU CONFIGURATION UPDATE (516)) may include TDD information of a neighboring cell, SBFD information of a neighboring cell, and may be expressed as a pattern and period of UL and DL slots or symbols.

The pattern and period of UL and DL slots or symbols representing TDD information can be represented as in [Table 1] or [Table 2].

An SBFD slot or symbol can be used only in a DL slot in a TDD scheme, only in an UL slot, only in a flexible symbol, or can be set regardless of the TDD pattern. That is, an SBFD pattern can indicate information belonging to a DL, flexible, or UL slot in TDD.

The pattern, period, and frequency information of UL and DL slots or symbols representing SBFD information may include at least one of the following information.

- Starting number of the slot to be set as SBFD slot and number of consecutive slots

- Setting via bit string of slot to be set as SBFD slot (e.g. if the first bit is 1, the first slot is SBFD slot)

- The starting number of the symbol to be set as the SBFD symbol within one slot (pattern or index) and the number of consecutive symbols.

- Setting via bit string of symbol to be set as SBFD symbol within one slot (pattern or index) (e.g. if first bit is 1, first slot is SBFD slot)

- An indicator indicating whether a symbol within a slot (pattern or index) is to be used as SBFD, non-SBFD, or mixed.

- Pattern information of slots and symbols (e.g., the period or offset at which slots with the same SBFD symbol are repeated)

- Indicator indicating DL, UL subband or guard band

- Information indicating the initial position of consecutive PRBs (e.g. PRB unit indicating the offset between point A and the starting PRB)

- Information indicating the bandwidth of the subband (e.g., number of PRBs, bandwidth in frequency units)

If the TDD or SBFD patterns of the cells being serviced within a DU are different, the DU can verify the TDD or SBFD pattern for each cell through an OAM interface, etc. Through this method, the DU can recognize that the TDD pattern is different for each cell and anticipate inter-cell CLI.

In addition, when the TDD or SBFD patterns of cells of different DUs or cells of different base stations are different, the DU can anticipate inter-cell CLI by recognizing that the TDD or SBFD patterns of the cell being served by the DU and the neighboring cell are different through the TDD or SBFD pattern information received through the F1AP message (518).

If the TDD or SBFD patterns of the cells being served within a CU are different, the CU can identify the TDD or SBFD pattern for each cell through messages (513, 516) transmitted to the F1AP interface. In this way, the CU can recognize that the TDD patterns of the cells served by a DU or different DUs are different, and thus anticipate inter-cell CLI.

As illustrated in the example in Figure 4, intra-cell CLI due to SBFD can occur even within a single cell. The UL signal transmitted by any terminal using the UL subband can interfere with any terminal using the DL subband.

FIGS. 6A and 6B are diagrams illustrating how CUs of different base stations share TDD pattern information or SBFD pattern information to anticipate inter-cell CLI according to embodiments of the present disclosure.

Referring to FIG. 6a, the first base station (601) and the second base station (611) are each composed of one CU (602, 612), one DU (603, 613), and one cell (604, 614), and each cell (604, 614) can provide wireless communication services using TDD or SBFD. For convenience of explanation, the first base station and the second base station are described as each composed of one DU and one cell.

The CU (602) of the first base station (601) can establish an XnAP connection to exchange information with the CU (612) of the second base station (611) through the Xn interface (630). Alternatively, the CU (612) of the second base station (611) can establish an XnAP connection to exchange information with the CU (602) of the first base station (601) through the Xn interface (630).

Below, FIG. 6b illustrates XnAP message transmission between a CU (621) of a first base station and a CU (631) of a second base station, and F1AP message transmission between a CU (621) of the first base station and a DU (622) connected to an F1AP, and a CU (631) of the second base station and a DU (632) connected to an F1AP. Referring to FIG. 6b, the CU (621) of the first base station or the CU (631) of the second base station can transmit (623) an XN SETUP REQUEST to establish an XnAP connection, and the CU (631) of the second base station or the CU (621) of the first base station that receives the XN SETUP REQUEST can respond with an XN SETUP RESPONSE (624). In the drawing, it is assumed that the CU (621) of the first base station transmits an XN SETUP REQUEST to the CU (631) of the second base station.

When information on a cell served by the base station is updated (625), the DU (622) of the first base station can notify the CU (621) of the change via the F1AP gNB-DU configuration update (626) message. The method for updating cell information can follow the example of FIG. 5.

When information on a cell served by the base station is updated, the CU (621) of the first base station can transmit an NG-RAN NODE CONFIGURATION UPDATE message (627) to the CU (631) of the second base station via the XnAP to notify the change. Alternatively, when information on a cell served by a counterpart base station to which the XnAP is connected is needed, the CU (621) of the first base station or the CU (631) of the second base station can transmit an NG-RAN NODE CONFIGURATION UPDATE message (628) to request cell information from the second base station (631) or the first base station (621). The second base station or the first base station that receives the NG-RAN NODE CONFIGURATION UPDATE (628) can provide a response or requested information with an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message (629). If the CU (631) of the second base station needs to update the information of the neighboring cell to the DU (632), the information can be indicated by transmitting a gNB-CU configuration update (630) message through the F1AP as in the example of FIG. 5.

These XnAP messages (e.g., XN SETUP REQUEST (623), XN SETUP RESPONSE (624), NG-RAN NODE CONFIGURATION UPDATE (627, 628), NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE (629)) may include at least one Served Cell Information NR. The Served Cell Information NR may include TDD information of a cell being served by the base station transmitting the XnAP message, as shown in [Table 3], and may indicate a pattern and period of UL and DL slots or symbols. The pattern and period of UL and DL slots or symbols may be indicated as shown in [Table 1] or [Table 2].

In addition, if the TDD or SBFD pattern of the cell served by the CU of the first base station (e.g., 621) is different from the TDD or SBFD pattern of the cell served by the CU of another base station (e.g., 631), the CU can anticipate inter-cell CLI by recognizing that the TDD or SBFD pattern of the cell served by the DU and the neighboring cell is different through TDD or SBFD pattern information received through XnAP messages.

FIG. 7 is a diagram illustrating a method for a terminal to measure and report CLI using an L3 measurement reporting framework according to embodiments of the present disclosure.

Referring to FIG. 7, the first base station (701) serves the first terminal (711), and the second base station (731) serves the second terminal (721). The cell in which the first base station (701) serves the first terminal (711) may have a different TDD or SBFD pattern from the cell in which the second base station (731) serves the second terminal (721). In this case, inter-cell CLI or intra-cell CLI may exist, as in the examples of FIG. 5 or FIG. 6.

The first base station (701) can determine whether there is inter-cell CLI or intra-cell CLI by measuring a signal transmitted by the second terminal (721) that is the cause of interference with the first terminal (711) and reporting it to the base station. To this end, the first base station (701) can instruct the first terminal (711) on a method and resources for measuring CLI. The CLI measurement method can be divided into SRS (sounding reference signal) measurement and RSSI (received signal strength indicator) measurement. In the case of SRS measurement, the first terminal (711) can measure the SRS resource transmitted by the second terminal (721) and report the result to the base station. In the case of RSSI measurement, the RSSI of the measurement resource instructed to the first terminal (711) can be measured and the result value can be reported to the base station. In this case, the value measured as RSSI can include the UL signal transmitted by the second terminal (721). There are several ways in which the first terminal (711) reports the measurement result value to the first base station (701): a method using a measurement report triggering event, a method of reporting periodically, or a method using a combination of the two.

The first base station (701) can utilize the L3 measurement reporting framework to measure the CLI of the first terminal (711). At this time, the first terminal (711) can transmit UE capability information (741) to the first base station (701) to transmit capability information indicating that the L3 measurement reporting framework can be utilized, capability information indicating that the CLI can be measured, or a combination of the two. Based on this capability information, the first base station (701) can determine that the first terminal (711) is capable of CLI measurement using the L3 measurement reporting framework.

The second base station (731) can instruct the second terminal (721) to set up transmission of SRS for UL channel estimation of the second terminal (721) through an RRC message (e.g., RRCReconfiguration) (742). Each SRS resource can include srs-Resource, srs-SCS, refServCellIndex, and refBWP, and srs-Resource can include at least one piece of information from among an SRS resource identifier (srs-ResourceId), the number of SRS ports (nrofSRS-ports), a ptrs port index (ptrs-PortIndex), a transmission resource combination (transmissionComb), time axis resource mapping of SRS (resourceMapping), frequency axis resource mapping of SRS (freqDomainPosition, freqDomainShift), frequency hopping information (freqHopping, groupOrSequenceHopping), and a transmission resource type (resourceType).

The second base station (731) can transmit SRS resource information of the second terminal (721) to the first base station (701) through an XnAP message. The information transmitted in the XnAP message (743) may include information included in an RRC message (742) for SRS transmission setup and an identifier (XnAP UEID) of the second terminal (721).

If the first base station (701) and the second base station (731) are the same and the serving cell of the first terminal (711) and the serving cell of the second terminal (721) are serviced by different DUs, each DU can transmit SRS resource information of the second terminal (721) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message can include information included in an RRC message (742) for SRS transmission setup and an identifier (GNB-DU F1AP UEID or GNB-CU F1AP UEID) of the second terminal (721).

If the first base station (701) and the second base station (731) are the same and the serving cell of the first terminal (711) and the serving cell of the second terminal (721) are serviced by the same DU, the DU can transmit SRS resource information of the second terminal (721) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message can include information included in an RRC message (742) for SRS transmission setup and an identifier (GNB-DU F1AP UEID or GNB-CU F1AP UEID) of the second terminal (721).

When the serving cell of the first terminal (711) and the serving cell of the second terminal (721) are the same, the DU can transmit SRS resource information of the second terminal (721) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message can include information included in an RRC message (742) for SRS transmission setup and an identifier of the second terminal (721) (GNB-DU F1AP UEID or GNB-CU F1AP UEID).

The CU of the first base station (701) can know the SRS transmission information of the second terminal (721) through this method. The CU of the first base station (701) can determine the SRS resources that the first terminal (711) should measure.

The L3 measurement reporting framework can specify the objects to be measured and the conditions to be reported through the measurement configuration (MeasConfig). The measurement configuration consists of measObjectToAddModList for adding or changing measurement objects, measObjectToRemoveList for deleting measurement objects, reportConfigToAddModList for adding or changing reporting conditions, reportConfigToRemoveList for deleting reporting conditions, measIdToAddModList for adding or changing measurement identifiers, and measIdToRemoveList for deleting measurement identifiers, as shown in [Table 4].

The measurement target list may include an identifier indicating the measurement target and one or more measObjects indicating information about the measurement target, and each measurement target may be classified as NR, EUTRA, UTRA, SL, CLI, etc. according to its purpose. The measurement target list may be expressed as in [Table 5].

Among these, the CLI measurement target may include resource settings for CLI measurement. Resource types for CLI measurement may be configured as SRS and RSSI, and may include at least one SRS resource or RSSI resource. The CLI measurement target may be represented as shown in [Table 6].

Each SRS resource can include srs-Resource, srs-SCS, refServCellIndex, and refBWP, and srs-Resource can include at least one of the following information: SRS resource identifier (srs-ResourceId), number of SRS ports (nrofSRS-ports), ptrs port index (ptrs-PortIndex), transmission resource combination (transmissionComb), SRS time domain resource mapping (resourceMapping), SRS frequency domain resource mapping (freqDomainPosition, freqDomainShift), frequency hopping information (freqHopping, groupOrSequenceHopping), and transmission resource type (resourceType). Srs-Resource can be represented as shown in [Table 7].

Each RSSI resource can be distinguished by an identifier (rssi-ResourceId) and may include at least one of the SCS of the RSSI resource (rssi-SCS), the starting PRB position and number of the RSSI resource (startPRB, nrofPRBs), the starting symbol position and number of the RSSI resource (startPosition, nrofSymbols), the period and offset of the RSSI resource (rssi-PeriodictyAndOffset), and the frequency reference point cell (refServCellIndex).

A measurement report list may include an identifier indicating a measurement report and one or more reportConfigs indicating measurement report conditions, and each measurement target may be classified as NR, Inter-RAT, SL, etc. according to its purpose. The measurement report list may be represented as shown in [Table 8].

Among these, NR reporting settings may include measurement reporting settings targeting NR. Measurement settings for CLI reporting may include reporting based on measurement report triggering events and periodic reporting. Details on measurement report triggering events are described in FIGS. 9, 10, and 11. If the terminal is configured to report periodically and has measurement results to report, it reports using a measurement report at the set interval (reportInterval). Measurement reports are performed the set number of times (reportAmount). Among the NR reporting settings, CLI reporting settings can be represented as shown in [Table 9].

The first base station can instruct the first terminal to measure the SRS pattern transmitted by the second terminal by transmitting it. The SRS pattern can be transmitted as shown in [Table 7]. The first base station can configure the first terminal by including the SRS pattern in the CLI measurement object (measObjectCLI). In addition, the first base station can instruct the first terminal how to report the measured SRS-RSRP to the first base station by setting the report configuration (reportConfig). The first base station can configure the first terminal to perform measurement by combining measObject and reportConfig as shown in [Table 10]. In addition, the first base station can transmit an RSSI resource to the first terminal and instruct the first terminal to measure RSSI using the resource. The RSSI resource can be transmitted as shown in [Table 6]. The first base station can configure the first terminal by including the RSSI resource in the CLI measurement object (measObjectCLI). Additionally, the first base station can set a report configuration (reportConfig) to the first terminal to instruct it on how to report the measured CLI-RSSI to the first base station.

The first base station (701) can instruct the first terminal (711) on the measurement target and reporting conditions through an RRC message (e.g., RRCReconfiguration) message (744).

The first terminal (711) can perform measurement on a measurement target instructed by the first base station (701) through an RRC message (744).

The first terminal (711) may transmit the measurement result to the base station via an RRC message (e.g., measurement report) (745) when the first base station (701) satisfies the measurement report event or through a periodic measurement report, as instructed via an RRC message (744). The measurement report may include one or more of the following information. The measurement report may be represented as shown in [Table 11].

- Measurement identifier (e.g. measId)

- Measurement results of the serving cell (e.g., measurement results of the cell indicated in servingCellMO)

- CLI measurement results

-- SRS-RSRP measurement results (SRS resource identifier, SRS-RSRP (dBm)), which may be included if a measurement reporting event is satisfied due to SRS-RSRP or if measurement is instructed to be made with SRS-RSRP.

-- CLI-RSSI measurement results (RSSI resource identifier, CLI-RSSI (dBm)), which may be included if a measurement reporting event is satisfied due to CLI-RSSI or if measurement is instructed to be made with SRS-RSRP.

- An indicator indicating the first measurement report to be transmitted after a measurement report event is satisfied.

FIG. 8 is a diagram illustrating a method for a terminal to measure and report CLI using an L1 measurement reporting framework according to embodiments of the present disclosure.

Referring to FIG. 8, the first base station (801) serves the first terminal (811), and the second base station (831) serves the second terminal (821). The cell in which the first base station (801) serves the first terminal (811) may have a different TDD or SBFD pattern from the cell in which the second base station (831) serves the second terminal (821). In this case, inter-cell CLI or intra-cell CLI may exist, as in the examples of FIG. 5 or FIG. 6.

The first base station (801) can determine whether there is inter-cell CLI or intra-cell CLI by measuring a signal transmitted by the second terminal (821) that is the cause of interference with the first terminal (811) and reporting it to the base station. To this end, the first base station (801) can instruct the first terminal (811) on a method and resources for measuring CLI. The CLI measurement method can be divided into SRS (sounding reference signal) measurement and RSSI (received signal strength indicator) measurement. In the case of SRS measurement, the first terminal (811) can measure the SRS resource transmitted by the second terminal (821) and report the result to the base station. In the case of RSSI measurement, the RSSI of the measurement resource instructed to the first terminal (811) can be measured and the result value can be reported to the base station. In this case, the value measured as RSSI can include the UL signal transmitted by the second terminal (821). There are several ways in which the first terminal (811) reports the measurement result value to the first base station (801): a method using a measurement report triggering event, a method of reporting periodically, or a method using a combination of the two.

The first base station (801) can utilize the L1 measurement reporting framework to measure the CLI of the first terminal (811). At this time, the first terminal (811) can transmit UE capability information (841) to the first base station (801) to transmit capability information indicating that the L1 measurement reporting framework can be utilized, capability information indicating that the CLI can be measured, or a combination of the two. Based on this capability information, the first base station (801) can determine that the first terminal (811) is capable of CLI measurement using the L1 measurement reporting framework.

The second base station (831) can instruct the second terminal (821) to set up transmission of SRS for UL channel estimation of the second terminal (821) through an RRC message (e.g., RRCReconfiguration) (842). Each SRS resource can include srs-Resource, srs-SCS, refServCellIndex, and refBWP, and srs-Resource can include at least one piece of information from among an SRS resource identifier (srs-ResourceId), the number of SRS ports (nrofSRS-ports), a ptrs port index (ptrs-PortIndex), a transmission resource combination (transmissionComb), time-axis resource mapping of SRS (resourceMapping), frequency-axis resource mapping of SRS (freqDomainPosition, freqDomainShift), frequency hopping information (freqHopping, groupOrSequenceHopping), and a transmission resource type (resourceType).

The second base station (831) can transmit SRS resource information of the second terminal (821) to the first base station (801) through an XnAP message. The information transmitted in the XnAP message (843) may include information included in an RRC message (842) for SRS transmission setup and an identifier (XnAP UEID) of the second terminal (821).

If the first base station (801) and the second base station (831) are the same and the serving cell of the first terminal (811) and the serving cell of the second terminal (821) are serviced by different DUs, each DU can transmit SRS resource information of the second terminal (821) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message can include information included in an RRC message (842) for SRS transmission setup and an identifier (GNB-DU F1AP UEID or GNB-CU F1AP UEID) of the second terminal (821).

If the first base station (801) and the second base station (831) are the same and the serving cell of the first terminal (811) and the serving cell of the second terminal (821) are serviced by the same DU, the DU can transmit SRS resource information of the second terminal (821) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message can include information included in an RRC message (842) for SRS transmission setup and an identifier (GNB-DU F1AP UEID or GNB-CU F1AP UEID) of the second terminal (821).

When the serving cell of the first terminal (811) and the serving cell of the second terminal (821) are the same, the DU can transmit SRS resource information of the second terminal (821) to the CU through an F1AP message. At this time, the information transmitted in the F1AP message may include information included in an RRC message (842) for SRS transmission setup and an identifier of the second terminal (821) (GNB-DU F1AP UEID or GNB-CU F1AP UEID).

The CU of the first base station (801) can know the SRS transmission information of the second terminal (821) through this method. The CU of the first base station (801) can determine the SRS resources that the first terminal (811) should measure.

The first base station (801) can use the L1 measurement reporting framework for CLI measurement. The first base station (801) can instruct the first terminal (811) to measure the SRS pattern transmitted by the second terminal (821) by transmitting it. The SRS pattern can be transmitted as shown in [Table 7]. The first base station (801) can configure the first terminal (811) by including the SRS pattern in the CSI measurement target (CSI-MeasConfig). The CSI measurement configuration can be configured for the purpose of measuring non-zero power (NZP) CSI-RS (channel state information reference signal), CSI-IM (channel state information interference management), SSB, Scell, LTM, etc. The CSI-MeasConfig can be represented as shown in [Table 12].

To add or change CLI measurement reporting settings, the CLI measurement settings can be represented in the form of a list containing at least one CLI measurement setting, for example, as follows:

cli-CSI-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCLI-CSI-ReportConfigurations)) OF CLI-CSI-ReportConfig

maxNrOfCLI-CSI-ReportConfiguration is the maximum number of CLI measurement reporting configurations that can be configured on one terminal, for example, 48.

CLI-CSI-ReportConfig represents a CLI measurement configuration that is reported as a single CSI, and may contain one or more of the following information:

- cli-CSI-ReportConfigId: An identifier that distinguishes the CLI measurement configuration, the maximum value of which can be equal to maxNrOfCLI-CSI-ReportConfiguration.

- cli-ResourcesForChannelMeasurement: Represents CLI measurement resources.

- cli-ReportConfigType: This is a setting for CLI measurement reporting, and can be at least one of periodic, semiPersistentOnPUCCH, semiPersistentOnPUSCH, aperiodic, or event-based.

- cli-ReportContent: You can specify what to include in the CLI measurement report.

cli-ResourcesForChannelMeasurement represents at least one measurement resource to be measured, and may include an identifier that distinguishes the measurement target (e.g., cli-CSI-ResourceConfigId) and a set of at least one measurement resource (e.g., cli-CSI-ResourceSet). This set may be in the form of a list that includes one or more measurement resources that are configured with some or all of the information included in SRS-ResourceConfigCLI or RSSI-ResourceConfigCLI as an example in FIG. 7.

cli-CSI-ResourceSet can indicate SRS resources or RSSI resources to be measured, and the included information can be similar to measObjectCLI of [Table 6]. In addition, the first base station (801) can indicate TCI (transmission configuration indication)-StateId to indicate a beam to be measured by the first terminal (811). TCI-StateId is an identifier of a TCI-state that indicates an antenna port that has a QCL (quasi co-located) relationship with a specific channel (e.g., a reference signal) transmitted by the base station. That is, by indicating an antenna port that has a QCL relationship for a specific beam transmitted by the base station, the terminal can be instructed to measure a CLI resource through an antenna port that receives the corresponding beam.

cli-ReportConfigType can indicate the resource on which the first terminal (811) will transmit the CSI report, and can be divided into periodic indicating a periodic resource, semiPersistentOnPUCCH indicating a periodic resource transmitted on PUCCH, the transmission of which can be started or stopped by the instruction (e.g., DCI or MAC CE) of the first base station (801), semiPersistentOnPUSCH indicating a periodic resource transmitted on PUSCH, the transmission of which can be started or stopped by the instruction (e.g., DCI or MAC CE) of the first base station (801), aperiodic indicating a resource transmitted once by the instruction (e.g., DCI or MAC CE) of the first base station (801), and event-based indicating a resource that the terminal can transmit when a specific L1 measurement report event is satisfied. cli-ReportConfigType can be represented as shown in [Table 13].

As an example, the event-based configuration may include resources for the terminal to transmit CSI when an L1 measurement report event is satisfied, and may include, for example, one or more of the following information:

- Periodic resources (e.g., information contained in periodic, semiPersistentOnPUCCH, semiPersistentOnPUSCH, aperiodic)

- RACH resources for notifying the base station of event-based UE CSI reports (e.g., contention-free RACH or contention-based RACH resources, which may be in the form of RACH-ConfigDedicated or RACH-ConfigCommon).

Additionally, in an event-based setup, the configuration for a measurement reporting event may include one or more of the following information:

- The type of event (e.g., an event where the measured interference signal exceeds a threshold)

- Parameter settings for each event

-- The time of the measurement window to use when measuring L1 (e.g., measurement values after the window time has passed since the measurement may not be used)

-- Number of measurement instances (e.g., if the number of samples measured within the measurement window is not equal to the number of instances, the measurement value may not be used)

-- Threshold or offset and hysteresis for comparison with the measured signal

-- Time to trigger the measurement report (e.g. time to trigger)

-- Setting to send a measurement report when the measurement conditions are no longer met (e.g. reportonleave)

-- Setting to include additional indicators in the measurement report when the measurement conditions are first met.

The types of events are described in detail in Figures 9, 10, and 11 below.

As an example, cli-ReportContent may indicate what to include in a CLI measurement report, and may include one or more of the following information:

- nrOfReportedInterference: How many CLI measurement results can be included in the CSI at most.

- nrOfReportedBeam: How many beam measurement results can be included in the CSI at most?

- spCellInclusion: Whether to include spcell measurement results in CSI

- reportTriggeredBeam: In case of event-based, only the beam that triggered the L1 measurement report event is included in the CSI.

The first terminal (811) may transmit the measurement result to the first base station (801) via an L1 message (e.g., CSI) (845) when the first base station (801) satisfies a measurement report event or via a periodic measurement report, as instructed by the first base station (801) via an RRC message (844). The CSI including the CLI measurement result may include at least one or more of the following information.

Measurement ID: This can represent the identifier of the resource for which measurement is set, and can be the same as cli-CSI-ReportConfigId.

SRS resource ID: It can represent the identifier of the measured SRS, and can express a range such as maxNrofSRS-Resources as 6 bits, for example.

SRS-RSRP: It can represent the RSRP of the measured SRS, for example, as 7 bits, from -140 dBm or less to -44 dBm or more, and up to infinity where the SRS cannot be measured in a situation where the signal is too strong, in units of 1 dBm.

RSSI resource ID: It can represent the identifier of the measured RSSI, and can express a range such as maxNrofCLI-RSSI-Resources as 6 bits, for example.

CLI-RSSI: It can represent the RSRP of the measured RSSI, for example, with 7 bits, it can represent from -100 dBm or less to -25 dBm or more in units of 1 dBm.

Rx beam info: It can be represented by TCI-state ID, for example, 6 bits for PDCCH and QCL, and 7 bits for PDSCH and QCL.

Tx beam info: Tx beam information of spcell, for example, it can be 8 bits.

Cell Index: Can indicate the cell index of spcell or scell.

SSB index: It can indicate the SSB index of the measured cell.

SRS or RSSI Indicator: An indicator that indicates whether the measurement result included in CSI is SRS-RSRP or CSI-RSSI.

SSB-RSRP: It can represent the RSRP of the measured SSB, for example, in 1 dBm units from -140 dBm or less to -44 dBm or more as 7 bits, and up to infinity where the SSB-RSRP cannot be measured in situations where the signal is too strong.

CSI-RS-RSRP: It can represent the RSRP of the measured CSI-RS, for example, it can be expressed in units of 1 dBm from -140 dBm or less to -44 dBm or more as 7 bits, and up to infinity where the CSI-RS-RSRP cannot be measured in a situation where the signal is too strong.

An indicator indicating that this is the first CSI transmitted after satisfying a measurement report event.

The first terminal (811) can transmit information equivalent to a measurement report using CSI to the MAC CE, and the first base station (801) can transmit an instruction to use the MAC CE to the RRC, the MAC CE, or the DCI. When instructed by the RRC, the first base station (801) can instruct the first terminal (811) to start measuring and reporting of the measurement resources set by the RRC through the MAC CE or the DCI, and the started measurement report can continue until the first base station (801) stops it using the MAC CE or the DCI, or releases the setting using the RRC. The first terminal (811) can perform the L1 measurement report to the MAC CE using the MAC CE, which can be distinguished by a logical channel ID (LCID) or an e-LCID.

In order to release the CLI measurement configuration from the first terminal, the RRC message transmitted by the first terminal (811) may include a configuration (e.g., a list) including at least one CLI measurement configuration identifier to be released, and may have the following form, for example:

cli-CSI-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCLI-CSI-ReportConfigurations)) OF CLI-CSI-ReportConfigId

FIG. 9 is a diagram illustrating a CLI measurement report triggering event I1 based on one absolute threshold according to embodiments of the present disclosure.

If a slot or symbol in which a terminal affected by CLI (victim UE) receives DL and a slot or symbol in which a terminal causing CLI (aggressor UE) transmits UL are located at the same time and at a close frequency, CLI may occur in which the UL signal transmitted by the aggressor UE interferes with the DL signal of the victim UE, and the victim UE can measure the SRS transmitted by the aggressor UE or measure the signal strength (e.g., CLI-RSSI) for the time and frequency resources where interference is expected and report this to the base station to check for interference.

The measurement target can be set as in the example of Fig. 7 or Fig. 8 depending on whether the L3 or L1 measurement reporting framework is used, and if multiple measurement resources are included in one measurement target, the measurement results of all indicated measurement targets can be used to determine whether an event is satisfied. The measured SRS-RSRP or CLI-RSSI can be a linear average value of the values measured by each measurement resource for the measurement target as in the examples of Fig. 7 and Fig. 8, and can follow the values defined by 3GPP TS 38.215 and 3GPP TS 38.133.

The measurement report triggering event I1 may satisfy (921) the entering condition if the measured SRS-RSRP or CLI-RSSI (901) exceeds the absolute threshold (902), and may satisfy (924) the leaving condition if the measured SRS-RSRP or CLI-RSSI (901) is less than the absolute threshold (902). At this time, the absolute threshold (902) may be set differently for SRS and RSSI, and may be indicated by setting i1-Threshold to SRS-RSRP or CLI-RSSI. The terminal may transmit (923) a measurement report to the base station if the measurement report triggering event satisfies the entering condition for a continuous time (time to trigger, TTT) (922). TTT is a unit of time and may be, for example, a unit of slot, symbol, or ms.

Specifically, the entering condition can be expressed by the relationship Mi > Thresh + Hys, where the measured SRS-RSRP or CLI-RSSI (Mi) (901) exceeds the absolute threshold (Thresh) (902) plus the Hysteresis (Hys) (903). The leaving condition can be expressed by the relationship Mi < Thresh - Hys, where the measured SRS-RSRP or CLI-RSSI (Mi) (901) is less than the absolute threshold (Thresh) (902) minus the Hysteresis (Hys) (904). Mi and Thresh can be in units of dBm, and Hys can be in units of dB.

Hysteresis and Threshold, TTT can be instructed by the base station to the terminal through an RRC message (e.g., RRCReconfiguration), and can be included in reportConfigNR of Fig. 7 when performing measurement and reporting using the L3 measurement reporting framework. When performing measurement and reporting using the L1 measurement reporting framework, they can be included in the event-based configuration of Fig. 8.

A measurement report may be an RRC message, a MAC CE, or a CSI, depending on whether the L3 or L1 measurement reporting framework is used. The measurement report may follow the examples in FIG. 7 or FIG. 8.

FIG. 10 is a diagram illustrating a CLI measurement report triggering event based on an offset according to embodiments of the present disclosure.

If the slot or symbol in which the victim UE receives the DL and the slot or symbol in which the aggressor UE transmits the UL are located at the same time and at a close frequency, CLI may occur in which the UL signal transmitted by the aggressor UE interferes with the DL signal of the victim UE, and the victim UE can measure the SRS transmitted by the aggressor UE or measure the signal strength (e.g., RSSI) for the time and frequency resources where interference is expected and report it to the base station to check for interference. At this time, a relative measurement of the interference source is possible by measuring and comparing both the resource where interference exists and the reference resource.

The measurement target can be set as in the example of Fig. 7 or Fig. 8 depending on whether the L3 or L1 measurement reporting framework is used, and if multiple measurement resources are included in one measurement target, the measurement results of all indicated measurement targets can be used to determine whether an event is satisfied. The measured SRS-RSRP or CLI-RSSI can be a linear average value of the values measured by each measurement resource for the measurement target as in the examples of Fig. 7 and Fig. 8, and can follow the values defined by 3GPP TS 38.215 and 3GPP TS 38.133.

The base station can instruct the victim UE on a specific resource (slot or symbol) (1031) and a resource (1032) on which to measure CLI in order to set up a CLI measurement report triggering event based on an offset. The victim UE can compare the SRS-RSRP or CLI-RSSI of these two resources (1031, 1032), and if there is a difference greater than the offset, it can perform measurement and report to the base station using the L1 or L3 measurement reporting framework. The base station can determine that the resource for which measurement was instructed has CLI based on the measurement report.

The base station may indicate to the victim UE a resource that serves as a comparison reference for comparing two resources. This resource may be set as in the example of measObjectCLI in FIG. 7 when using the L3 measurement reporting framework. Alternatively, this resource may be set as in cli-CSI-ResourceSet in FIG. 8 when using the L1 measurement reporting framework. The base station may include in the information indicating the resource an indicator indicating that the resource is a reference for a CLI measurement report triggering event based on an offset. Alternatively, the identifier of the resource (e.g., srs-ResourceID or rssi-ResourceID) that serves as a reference for setting the CLI measurement report triggering event based on an offset (e.g., reportConfig in FIG. 7 or CLI-CSI-ReportConfig in FIG. 8) may be included.

The terminal can measure and compare the SRS-RSRP or CLI-RSSI of a reference resource and a measurement target resource. The measurement target resource may be at least one SRS resource (e.g., srs-Resource or SRS-ResourceListConfigCLI) or at least one RSSI resource (RSSI-ResourceConfigCLI or RSSI-ResourceListConfigCLI). The terminal can determine that a measurement report triggering event is satisfied if the difference (1003, 1011) between the measurement result (1002) of the reference resource and the measurement result (1001) of the measurement target resource exceeds the offset (1006).

Specifically, the entering condition (1021) can be expressed as a relationship Mi - Hys > Mr + Off, where the value obtained by subtracting the Hysteresis (Hys) from the SRS-RSRP or CLI-RSSI (Mi) (1001) measured at the target resource (1032) exceeds (1005) the offset (Off) of the SRS-RSRP or CLI-RSSI (Mr) (1002) measured at the reference resource (1031). The leaving condition (1024) can be expressed as a relationship Mi + Hys < Mr + Off, where the value obtained by adding the Hysteresis (Hys) to the SRS-RSRP or CLI-RSSI (Mi) measured at the target resource (1032) is less than (1007) the offset (Off) of the SRS-RSRP or CLI-RSSI (Mr) measured at the reference resource (1031).

At this time, additional offsets can be applied to Mi and Mr, and can be different for each SRS resource and RSSI resource being measured. For example, an offset (Oi) of -3 dB can be applied to the resource being measured (1032), an offset (Or) of -3 dB can be applied to the reference measurement resource (1031), or both. That is, the entering condition can be Mi + Oi - Hys > Mr + Or + Off, and the leaving condition (1024) can be Mi + Oi + Hys < Mr + Or + Off. Instead of indicating multiple settings for applying different Offsets to different resources through Oi or Or, they can be indicated with a single setting.

If the Entering condition (1021) is continuously satisfied (1022) during the TTT, the terminal may transmit a measurement report to the base station (1023). The measurement report may be an RRC message, a MAC CE, or a CSI, depending on whether the L3 or L1 measurement reporting framework is used. The measurement report may follow the examples of FIG. 7 or 8. In addition to the information exemplified in FIG. 7 or 8, a measurement report using L3 or L1 may include the following information.

- An indicator indicating SRS-RSRP or CLI-RSSI measured from the reference resource.

FIG. 11 is a diagram illustrating a CLI measurement report triggering event based on two absolute thresholds according to embodiments of the present disclosure.

If the slot or symbol in which the victim UE receives the DL and the slot or symbol in which the aggressor UE transmits the UL are located at the same time and at a close frequency, CLI may occur in which the UL signal transmitted by the aggressor UE interferes with the DL signal of the victim UE. The victim UE can check for interference by measuring the SRS transmitted by the aggressor UE or measuring the signal strength (e.g., RSSI) for the time and frequency resources where interference is expected and reporting this to the base station. At this time, the impact on the interference source can be evaluated by measuring and comparing both resources where interference exists and resources where interference does not exist.

The measurement target can be set as in the example of Fig. 7 or Fig. 8 depending on whether the L3 or L1 measurement reporting framework is used, and if multiple measurement resources are included in one measurement target, the measurement results of all indicated measurement targets can be used to determine whether an event is satisfied. The measured SRS-RSRP or CLI-RSSI can be a linear average value of the values measured by each measurement resource for the measurement target as in the examples of Fig. 7 and Fig. 8, and can follow the values defined by 3GPP TS 38.215 and 3GPP TS 38.133.

The base station can instruct the victim UE on a specific resource (slot or symbol) (1131) and a resource (1132) on which to measure CLI in order to set up a CLI measurement reporting triggering event based on two absolute thresholds.

This resource may be the same as measObjectCLI of FIG. 7 when using the L3 measurement reporting framework. Alternatively, this resource may be the same as cli-CSI-ResourceSet of FIG. 8 when using the L1 measurement reporting framework. The base station may include an indicator in the information indicating the resource that indicates that the resource (1131) is a reference for a CLI measurement reporting triggering event based on two absolute thresholds. Alternatively, the base station may include an identifier (e.g., srs-ResourceID or rssi-ResourceID) of the resource (1131) that is a reference for a configuration of a CLI measurement reporting triggering event based on two absolute thresholds (e.g., reportConfig of FIG. 7 or CLI-CSI-ReportConfig of FIG. 8).

The terminal can measure the SRS-RSRP or CLI-RSSI of the reference resource and the measurement target resource and compare them with a threshold. The measurement target resource may be at least one SRS resource (e.g., srs-Resource or SRS-ResourceListConfigCLI) or at least one RSSI resource (RSSI-ResourceConfigCLI or RSSI-ResourceListConfigCLI). The terminal can determine that the measurement report triggering event is satisfied if both the condition that the measurement result of the reference resource is less than a first threshold and the condition that the measurement result of the measurement target resource exceeds a second threshold are satisfied. If the SRS-RSRP or CLI-RSSI (1101) of the reference resource (1131) is less than the first threshold (1103) and the SRS-RSRP or CLI-RSSI (1111) of the measurement target resource (1132) exceeds the second threshold (1113), the victim UE can perform measurement and reporting to the base station using the L1 or L3 measurement reporting framework. The base station can determine that the resource that instructed the measurement has a CLI based on the measurement report.

Specifically, the entering condition can be expressed as the relationship Mr < Thres1 - Hys, where the SRS-RSRP or CLI-RSSI (Mr) (1101) measured from the reference resource (1131) is less than the first threshold minus the Hysteresis (Hys) (1104), and the entering condition can be expressed as the relationship Mi > Thres2 + Hys, where the SRS-RSRP or CLI-RSSI (Mi) (1111) measured from the measurement target resource (1132) is greater than the second threshold plus the Hysteresis (Hys) (1112). The terminal can determine that it is an entering condition only when both of these conditions are satisfied (1121, 1122). The leaving condition can be expressed as the relationship Mr > Thres1 + Hys, where the SRS-RSRP or CLI-RSSI (Mr) (1101) measured from the reference resource (1131) exceeds the first threshold plus the Hysteresis (Hys) (1102), and can be expressed as the relationship Mi < Thres2 - Hys, where the SRS-RSRP or CLI-RSSI (Mi) (1111) measured from the measurement target resource (1132) is less than the second threshold minus the Hysteresis (Hys) (1114). If at least one of these two conditions is satisfied, it can be determined as a leaving condition.

At this time, additional offsets can be applied to Mi and Mr, and can be different for each SRS resource and RSSI resource being measured. For example, an offset (Oi) of -3 dB can be applied to the resource (1132) being measured, an offset (Or) of -3 dB can be applied to the resource (1131) being measured, or both. That is, the entering condition can be Mr + Or + Hys < Thres1 and Mi + Oi - Hys > Thres2, and the leaving condition can be Mr + Or - Hys > Thres1 and Mi + Oi + Hys < Thres2. Instead of indicating multiple settings to apply different Offs to different resources through Oi or Or, you can indicate them with a single setting.

If the Entering condition is continuously satisfied during TTT (1123), the terminal may transmit a measurement report to the base station (1124). In addition to the information exemplified in FIG. 7 or FIG. 8, a measurement report using L3 or L1 may include the following information.

An indicator indicating SRS-RSRP or CLI-RSSI measured from a reference resource.

FIGS. 12a, 12b, and 12c illustrate a method of setting multiple measurement targets in one measurement target resource according to embodiments of the present disclosure.

Looking at the structure of the measurement target resource as an example in Fig. 7 or Fig. 8, a list including at least one SRS or RSSI resource can be set.

Referring to Fig. 12a, the measurement target resources can be configured across multiple frequencies and times. For example, as shown in Fig. 12a, three different measurement resources ({1201, 1202}, {1211, 1212}, {1221, 1222}) can be included in one measurement target. In this case, the measurement result value can be used as a linear average of the SRS-RSRP or CLI-RSSI values measured for the corresponding measurement target resources, which has undergone L1 filtering. L1 filtering operates as a UE implementation and can be expressed as a linear average of values measured over a specific period of time, for example. When the measurement value is reported to the base station using the L1 measurement reporting framework, the value included in the CSI or the value used to check whether the measurement report triggering event has been satisfied can be an L1 filtered value. In addition, when reporting measurement values to the base station using the L3 measurement reporting framework, the values used in the L3 of the terminal may be values included in the measurement report or values for checking whether the measurement report triggering event is satisfied, which may be values obtained by applying a filter coefficient to the values received through L1 filtering. The values obtained through L3 filtering with the filter coefficient applied can be expressed as Fn = (1 - a) * Fn-1 + a * Mn. Fn is the result of L3 filtering, a is the filter coefficient, Fn-1 is the value obtained through the previous L3 filtering, and Mn is the value most recently received from L1. For example, if the filter coefficient is 0, there may be no correlation between the previous value received from L1 and the latest value, and the closer the filter coefficient is to 1, the more weight is placed on the previous result value.

Referring to FIG. 12b, measurement result 1203 may be a measurement result obtained by measurement target resource 1201, measurement result 1204 may be a measurement result obtained by measurement target resource 1202, measurement result 1213 may be a measurement result obtained by measurement target resource 1211, measurement result 1214 may be a measurement result obtained by measurement target resource 1212, measurement result 1223 may be a measurement result obtained by measurement target resource 1221, and measurement result 1224 may be a measurement result obtained by measurement target resource 1222. When L1 or L3 filtering is applied to these measurement results, a result value based on measured values such as 1231 may be used. In addition, when the number of measurement target resources is more, the deviation of SRS-RSRP or CLI-RSSI measured for each resource may increase. This deviation may affect the virtual threshold value (1232) for using the measurement result. The virtual threshold value (1232) may be used to determine whether CLI exists when the base station receives a measurement report, or to determine whether the terminal satisfies the measurement report triggering event. That is, when the measurement result values of each measurement target resource (e.g., 1203 and 1204, 1213 and 1214, 1223 and 1224) are used separately (1232, 1233, 1234) and the measurement result values (1231) measured by targeting all measurement target resources may have deviations, which may result in unintended results in determining whether CLI exists or whether the measurement report triggering event is satisfied.

Therefore, in order to measure multiple resources individually, multiple measurement target resources need to be set up, rather than setting up multiple SRS or RSSI resources for a single measurement target. However, the maximum number of measurement targets that can be set, maxNrofObjectId, is 64, which may be sufficient for existing TDD-based CLI measurements, but may not be enough for SBFD-based CLI measurements to diversify the measurement targets.

For example, referring to FIG. 12c, the resources that the victim UE needs to measure can be variously subdivided (1251, 1252, 1253, 1254) in time and frequency resources depending on the configuration of the subband of the serving cell (1241) and the neighboring cell (1242) of the victim UE, subcarrier spacing, BWP, etc.

To solve this, you can use a method to make maxNrofObjectId larger than the existing 64.

Alternatively, a method may be used to set up multiple SRS or RSSI resources for a single measurement target, each with an indicator that identifies it as a different measurement target.

An indicator indicating a configuration for measuring each measurement target resource can be used when a base station indicates a measurement target resource or measurement target to a terminal in the examples of FIG. 7 or FIG. 8. When the base station configures L1 or L3 measurement targets to a terminal via RRC, the base station may include an indicator indicating that multiple measurement targets are included in one measurement target, or may include an indicator indicating to measure each of one or more measurement resources (e.g., SRS-Resource or RSSI-Resource). For example, when using the L3 measurement reporting framework, if the corresponding indicator is included in SRS-ResourceListConfigCLI or RSSI-ResourceListConfigCLI, it may mean to instruct to measure each of all measurement targets existing in the corresponding list. Or, when using the L1 measurement reporting framework, if the corresponding indicator is included in cli-ResourcesForChannelMeasurement, it may mean to instruct to measure each of all measurement resources existing in the corresponding configuration. As another example, if each measurement resource (e.g., SRS-ResourceConfigCLI and RSSI-ResourceConfigCLI of the L3 measurement reporting framework, or cli-CSI-ResourceConfig of the L1 measurement reporting framework) includes the corresponding directive, it can mean that measurement is to be performed only for the measurement resources that include the corresponding directive. In addition, even if the corresponding directive is included, all measurement resources indicated by the measurement target can be measured as before.

When these indicators are included and set, the L1 of the terminal can determine that multiple measurement resources within a single measurement target are different measurement targets. The L1 of the terminal can additionally include an identifier (e.g., SRS-ResourceId or RSSI-ResourceId) of the measurement target in the measurement results transmitted to L3, so as to inform L3 that the measurement results transmitted from L1 to L3 are different measurement targets.

For example, if the base station instructs the terminal to measure the first RSSI resource and the second RSSI resource within a single measurement target, the L1 of the terminal can use the result values measured with the first RSSI resource and the result values measured with the second RSSI resource, respectively, to determine whether a measurement report event is satisfied or as result values included in a measurement report. In addition, as before, the result of measuring all RSSI resources can be used to determine whether a measurement report event is satisfied or as result values included in a measurement report.

The terminal may indicate in the measurement report whether each resource being measured has been measured. For example, if the resource that triggered the measurement report or the resource included in the measurement report is resource 1251 of FIG. 12c, an indicator indicating that it is resource 1251 (e.g., SRS-ResourceId or RSSI-ResourceId, or an index indicating the order in which it is included in the list) may be additionally included in the measurement report (e.g., measurement report or CSI).

FIG. 13 is a diagram illustrating the structure of a base station according to embodiments of the present disclosure.

The base station may include a transceiver (1305), a control unit (1310), and a storage unit (1315). The transceiver (1305), the control unit (1310), and the storage unit (1315) may operate according to the communication method of the base station described above. The network device may also correspond to the structure of the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. For example, the base station may include a transceiver (1305) and a control unit (1310). In addition, the transceiver (1305), the control unit (1310), and the storage unit (1315) may be implemented in the form of a single chip.

The transceiver (1305) is a general term for the receiving unit and the transmitting unit of the base station, and can transmit and receive signals with terminals, other base stations, or other network devices. At this time, the transmitted and received signals may include control information and data. The transceiver (1305) may transmit system information to the terminal, for example, and may transmit a synchronization signal or a reference signal. To this end, the transceiver (1305) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts a received signal. However, this is only one embodiment of the transceiver (1305), and the components of the transceiver (1305) are not limited to the RF transmitter and RF receiver. The transceiver (1305) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (1305) can receive a signal through a communication channel (e.g., a wireless channel) and output it to the control unit (1310), and transmit the signal output from the control unit (1310) through the communication channel. In addition, the transceiver (1305) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a terminal, another base station, or another entity through a wired or wireless network.

The storage unit (1315) can store programs and data required for the operation of the base station. In addition, the storage unit (1315) can store control information or data included in signals acquired from the base station. The storage unit (1315) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (1315) can store at least one of information transmitted and received through the transceiver unit (1305) and information generated through the control unit (1310).

In the present disclosure, the control unit (1310) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (1310) may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (1310) may control the signal flow between each block to perform operations according to the flowchart described above.

FIG. 14 is a diagram illustrating the structure of a terminal according to embodiments of the present disclosure.

The terminal may include a transceiver (1405), a control unit (1410), and a storage unit (1415). The transceiver (1405), the control unit (1410), and the storage unit (1415) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. For example, the terminal may include a transceiver (1405) and a control unit (1410). In addition, the transceiver (1405), the control unit (1410), and the storage unit (1415) may be implemented in the form of a single chip.

The transceiver (1405) is a general term for the receiving unit and the transmitting unit of the terminal, and can transmit and receive signals with a base station, another terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. The transceiver (1405) may, for example, receive system information from the base station and may receive a synchronization signal or a reference signal. To this end, the transceiver (1405) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (1405), and the components of the transceiver (1405) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1405) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (1405) can receive a signal through a wireless channel and output it to the control unit (1410), and transmit the signal output from the control unit (1410) through the wireless channel. In addition, the transceiver (1405) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

The storage unit (1415) can store programs and data necessary for the operation of the terminal. In addition, the memory (1415) can store control information or data included in signals obtained from the terminal. The storage unit (1415) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

In the present disclosure, the control unit (1410) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (1410) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (1410) may control the signal flow between each block to perform operations according to the flowchart described above.

While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims (15)

In a method performed by a terminal of a wireless communication system, A step of receiving an RRC (radio resource control) message including configuration information for measurement of CLI (crosslink interference) from a base station; A step of performing measurement based on the above setting information; and A method comprising the step of transmitting a report of the results of the measurement to the base station via an L1 (layer 1) message. In the first paragraph, The above setting information includes first information about the event that triggers the report, The above method, Further comprising a step of identifying satisfaction of the event based on the first information, A method wherein satisfaction of the above event is identified based on a comparison of a value measured by the above measurement with a threshold value. In the first paragraph, The above setting information includes second information about the measurement target, A method wherein the second information includes a CSI (channel state information) measurement setting for indicating a measurement target. In the third paragraph, A method wherein the above measurement target includes a resource for a sounding reference signal (SRS) or a resource for a received signal strength indicator (RSSI). In a method performed by a base station of a wireless communication system, A step of transmitting an RRC (radio resource control) message including configuration information for measuring CLI (crosslink interference) to a terminal; and A method comprising the step of receiving a report of the result of the measurement from the terminal via an L1 (layer 1) message. In paragraph 5, The above setting information includes first information about the event that triggers the report, A method wherein the above event is identified based on a comparison of a value measured by the above measurement with a threshold value. In paragraph 5, The above setting information includes second information about the measurement target, A method wherein the second information includes a CSI (channel state information) measurement setting for indicating a measurement target. In paragraph 7, A method wherein the above measurement target includes a resource for a sounding reference signal (SRS) or a resource for a received signal strength indicator (RSSI). In the terminal of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Receive an RRC (radio resource control) message from a base station that includes configuration information for measuring crosslink interference (CLI), Perform measurements based on the above setting information, and A terminal configured to transmit a report of the results of the measurement to the base station via an L1 (layer 1) message. In paragraph 9, The above setting information includes first information about the event that triggers the report, The control unit is further set to identify satisfaction of the event based on the first information, The terminal, wherein satisfaction of the above event is identified based on a comparison of the value measured by the above measurement with a threshold value. In paragraph 9, The above setting information includes second information about the measurement target, A terminal, wherein the second information includes a CSI (channel state information) measurement setting for indicating a measurement target. In Article 11, The above measurement target is a terminal including a resource for SRS (sounding reference signal) or a resource for RSSI (received signal strength indicator). In a base station of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Transmitting an RRC (radio resource control) message containing configuration information for measuring CLI (crosslink interference) to the terminal, and A base station configured to receive a report of the results of the measurement from the terminal via an L1 (layer 1) message. In Article 13, The above setting information includes first information about the event that triggers the report and second information about the measurement target, The above event is based on a comparison of the measured value with a threshold value, A base station, wherein the second information includes a CSI (channel state information) measurement setting for indicating a measurement target. In Article 13, The above measurement target is a base station including a resource for SRS (sounding reference signal) or a resource for RSSI (received signal strength indicator).