Method and apparatus for measuring and reporting cross link interference in wireless communication system

Abstract

The present disclosure relates to a method and apparatus for measuring and reporting cross-link interference in a next-generation mobile communication system. A method for measuring and reporting a cross-link interference link of a terminal in a mobile communication system according to one embodiment of the present disclosure may include: receiving measurement configuration information from a base station including measurement settings and reporting settings for a cross-link interference link; performing a measurement of a set measurement object based on the measurement settings for the cross-link interference link; triggering a measurement result reporting procedure for the cross-link interference link based on the reporting settings for the cross-link interference link; and transmitting a measurement result report for the cross-link interference link to the base station.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for measuring and reporting cross-link interference in a next-generation mobile communication system. Background Technology

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation is underway in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0003] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies.

[0005] As the aforementioned developments and advancements in mobile communication systems have enabled the provision of various services, measures to effectively deliver these services are required. More specifically, in a serving cell configured for TDD (time division duplex), a method is needed to receive and utilize interference information regarding cross-links from the terminal in order to dynamically manage TDD resources. The problem to be solved

[0006] One embodiment of the present disclosure may provide a method and apparatus for measuring and reporting cross-link interference in a next-generation mobile communication system. means of solving the problem

[0007] A method for measuring and reporting a cross-interference link of a terminal in a mobile communication system according to one embodiment of the present disclosure may include: receiving measurement configuration information from a base station including measurement settings and reporting settings for a cross-interference link; performing a measurement of a set measurement object based on the measurement settings for the cross-interference link; triggering a measurement result reporting procedure for the cross-interference link based on the reporting settings for the cross-interference link; and transmitting a measurement result report for the cross-interference link to the base station. Brief explanation of the drawing

[0008] Figure 1 is a diagram showing the structure of an LTE system. Figure 2 is a diagram showing the wireless protocol structure in an LTE system. FIG. 3 is a drawing illustrating the structure of a next-generation mobile communication system to which an embodiment of the present disclosure is applied. FIG. 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which an embodiment of the present disclosure can be applied. FIG. 5 is a diagram illustrating cross-link interference when TDD cells are configured in a next-generation mobile communication system to which an embodiment of the present disclosure is applied. FIG. 6 is a diagram illustrating a procedure in which, in an NR system to which an embodiment of the present disclosure is applied, a terminal receives a measurement setting including cross-link interference from a base station and transmits a measurement value report thereon. FIG. 7 is a diagram illustrating a method for measuring and reporting cross-interference links of a terminal according to one embodiment of the present disclosure. FIG. 8 is a diagram illustrating the operation method of a terminal when an event-based measurement report is set for a cross-interference link according to one embodiment of the present disclosure. FIG. 9 is a diagram illustrating a method for measuring and reporting cross-interference links of a base station according to one embodiment of the present disclosure. FIG. 10 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure. FIG. 11 is a block diagram showing the configuration of a base station according to one embodiment of the present disclosure. Specific details for implementing the invention

[0009] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

[0010] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0011] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0012] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Throughout the specification, like reference numerals refer to like components.

[0013] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0014] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.

[0015] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, 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." Furthermore, the components and "parts" may be implemented to operate one or more CPUs within a device or secure multimedia card. In addition, in the embodiments, '~part' may include one or more processors.

[0016] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0017] For convenience of explanation, the present disclosure uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) and NR (New Radio) standards, or terms and names modified therefrom. However, the present disclosure is not limited to these terms and names and may be applied equally to systems conforming to other standards.

[0018] That is, in describing the embodiments of the present disclosure in detail, the communication standards defined by 3GPP will be the primary focus, but the main point of the present disclosure can be applied to other communication systems having a similar technical background with slight modifications without significantly departing from the scope of the present invention, and this will be possible at the judgment of a person with skilled technical knowledge in the technical field of the present disclosure.

[0020] The present disclosure relates to a method and apparatus for receiving interference information regarding a cross-link from a terminal in order to dynamically operate TDD resources in a serving cell configured for time division duplex (TDD). To this end, a series of operations are required in which the terminal measures and reports uplink interference information transmitted by another terminal in a neighboring cell (or cross-link). The interference information may include SRS-RSSP and CLI-RSSI. Reference signal measurement and reporting in an NR system are performed based on a downlink reference signal, which is a signal transmitted by a base station. However, a new procedure is required in which the terminal measures and reports a signal transmitted by another terminal.

[0021] According to one embodiment of the present disclosure, by providing a procedure for measuring uplink signals transmitted by another terminal in a next-generation mobile communication system, such as SRS-RSRP and CLI-RSSI, and reporting the measured values ​​to a base station, the base station can set up dynamic TDD based on the reported measured values. For example, if interference from surrounding cells is strong, the base station can limit TDD uplink allocation to the terminal, thereby achieving improved data quality.

[0023] Figure 1 is a diagram showing the structure of an LTE system.

[0024] Referring to FIG. 1, as illustrated, the wireless access network of the LTE system consists of a plurality of base stations (Evolved Node B, hereinafter eNB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20), an MME (Mobility Management Entity, 1a-25), and an S-GW (Serving-Gateway, 1a-30). A user terminal (User Equipment, hereinafter UE or terminal) (1a-35) connects to an external network through the eNB (1a-05, 1a-10, 1a-15, 1a-20) and the S-GW (1a-30).

[0025] Base stations (Evolved Node B, hereinafter eNB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20) serve as access nodes of a cellular network and provide wireless access to terminals connected to the network. That is, the base stations (1a-05, 1a-10, 1a-15, 1a-20) collect state information such as the buffer status, available transmission power status, and channel status of terminals to service the traffic of users, and perform scheduling to support the connection between the terminals and the core network (CN).

[0026] Additionally, base stations (1a-05, 1a-10, 1a-15, 1a-20) can correspond to the existing Node B of the UMTS (Universal Mobile Telecommunications System). The eNB (1a-35) is connected to the UE (1a-35) via a wireless channel and can perform more complex roles than the existing Node B. In an LTE system, since all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel, a device is required to aggregate status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling; this is handled by the eNB (1a-05, 1a-10, 1a-15, 1a-20). A single eNB can typically control multiple cells. The LTE system uses Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology. In addition, an Adaptive Modulation & Coding (hereinafter referred to as AMC) method is applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal.

[0027] The MME (1a-25) is a device responsible for various control functions as well as mobility management functions for terminals, and is connected to multiple base stations. The S-GW (1a-30) is a device that provides data bearers. The MME (1a-25) and S-GW (1a-30) can perform authentication and bearer management for terminals connected to the network, and process packets received from base stations (1a-05, 1a-10, 1a-15, 1a-20) or packets to be delivered to base stations (1a-05, 1a-10, 1a-15, 1a-20).

[0029] Figure 2 is a diagram showing the wireless protocol structure in an LTE system.

[0030] Referring to FIG. 2, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), and MAC (Medium Access Control 1b-15, 1b-30) at the terminal and eNB, respectively. PDCP (1b-05, 1b-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.

[0032] - Header compression and decompression features (ROHC only)

[0033] - User data transfer function (Transfer of user data)

[0034] - Sequential delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0035] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0036] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0037] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0038] - Encryption and decryption functions (Ciphering and deciphering)

[0039] - Timer-based SDU discard in uplink.

[0041] Radio Link Control (hereinafter referred to as RLC) (1b-10, 1b-35) reconstructs PDCP Packet Data Units (PDUs) into an appropriate size to perform ARQ operations, etc. The main functions of RLC are summarized as follows.

[0043] - Data transfer function (Transfer of upper layer PDUs)

[0044] - ARQ function (Error Correction through ARQ (only for AM data transfer))

[0045] - Concatenation, segmentation, and reassembly functions (Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM data transfer))

[0046] - Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0047] - Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer)

[0048] - Detection function (Duplicate detection (only for UM and AM data transfer))

[0049] - Error detection function (Protocol error detection (only for AM data transfer))

[0050] - RLC SDU deletion function (RLC SDU discard (only for UM and AM data transfer))

[0051] RLC re-establishment function

[0053] MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in a terminal and performs the operation of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

[0055] - Mapping function (Mapping between logical channels and transport channels)

[0056] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)

[0057] - Scheduling information reporting function

[0058] - HARQ function (Error correction through HARQ)

[0059] - Priority handling between logical channels of one UE

[0060] - Priority handling between UEs by means of dynamic scheduling

[0061] - MBMS service identification function

[0062] - Transport format selection function

[0063] - Padding

[0065] The physical layer (1b-20, 1b-25) performs the operation of channel coding and modulating upper layer data, making it into OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0066] Although not shown in FIG. 2, there is a Radio Resource Control (RRC) layer above the PDCP layer of the terminal and the base station, respectively, and this RRC layer can exchange connection and measurement-related setting control messages for wireless resource control.

[0068] FIG. 3 is a drawing illustrating the structure of a next-generation mobile communication system to which an embodiment of the present disclosure is applied.

[0069] Referring to FIG. 3, as illustrated, the wireless access network of a next-generation mobile communication system (5G or NR system) consists of a next-generation base station (New Radio Node B, hereinafter NR NB, NR gNB or NR base station, 1c-10) and an NR CN (New Radio Core Network, or NG CN: Next Generation Core Network, 1c-05). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal, 1c-15) connects to an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0070] In FIG. 3, the NR gNB (1c-10) corresponds to the eNB (Evolved Node B) of the LTE system. The NR gNB (1c-10) is connected to the NR UE (1c-15) via a wireless channel and can provide superior service compared to the existing Node B. In next-generation mobile communication systems, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this is handled by the NR gNB (1c-10). A single NR gNB (1c-10) typically controls multiple cells and consists of a CU (central unit) that oversees control and signaling, and a DU (distributed unit) that is responsible for the transmission and reception of signals. Next-generation mobile communication systems (5G or NR systems) can have a maximum bandwidth greater than the existing maximum bandwidth to achieve ultra-high-speed data transmission compared to LTE systems, and may additionally apply beamforming technology using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology. In addition, Adaptive Modulation & Coding (hereinafter referred to as AMC) can be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (1c-05) performs functions such as mobility support, bearer configuration, and QoS configuration. The NR CN (1c-05) is a device responsible for various control functions as well as mobility management functions for the terminal, and is connected to multiple base stations. Furthermore, the next-generation mobile communication system (5G or NR system) can be interoperable with LTE systems, and the NR CN (1c-05) can be connected to the MME (1c-25) through a network interface.The MME (1c-25) is connected to the existing base station eNB (1c-30).

[0072] FIG. 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which an embodiment of the present disclosure can be applied.

[0073] Referring to FIG. 4, the wireless protocol of a next-generation mobile communication system (5G or NR system) consists of NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) at the terminal and the NR base station, respectively.

[0075] The main functions of NR SDAP(1d-01, 1d-45) may include some of the following functions.

[0077] - User data transfer function (transfer of user plane data)

[0078] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0079] - Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0080] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0082] For SDAP layer devices, the terminal may receive a setting via an RRC message regarding whether to use the SDAP layer device header or the SDAP layer device functions for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0084] The main functions of NR PDCP(1d-05, 1d-40) may include some of the following functions.

[0086] - Header compression and decompression features (ROHC only)

[0087] - User data transfer function (Transfer of user data)

[0088] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0089] - Out-of-sequence delivery of upper layer PDUs

[0090] - Reordering function (PDCP PDU reordering for reception)

[0091] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0092] - Retransmission of PDCP SDUs

[0093] - Encryption and decryption functions (Ciphering and deciphering)

[0094] - Timer-based SDU discard in uplink.

[0096] Here, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or a function of transmitting immediately without considering the order, may include a function of recording lost PDCP PDUs by reordering, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

[0098] The main functions of NR RLC(1d-10, 1d-35) may include some of the following functions.

[0100] - Data transfer function (Transfer of upper layer PDUs)

[0101] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0102] - Out-of-sequence delivery of upper layer PDUs

[0103] - ARQ function (Error Correction through ARQ)

[0104] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0105] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0106] - Reordering function (Reordering of RLC data PDUs)

[0107] - Duplicate detection

[0108] - Error detection function (Protocol error detection)

[0109] - RLC SDU discard function

[0110] RLC re-establishment function

[0112] Here, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in sequence. More specifically, when an original RLC SDU is received divided into multiple RLC SDUs, the system may include a function to reassemble and transmit them, a function to rearrange the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record the lost RLC PDUs by rearranging the order, a function to report the status of the lost RLC PDUs to the transmitting side, a function to request retransmission of the lost RLC PDUs, a function to transmit only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, a function to transmit all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU, and a function to transmit all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.

[0113] At this time, RLC PDUs may be processed in the order they are received (regardless of the order of sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery), or in the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0114] Here, the out-of-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order, and may include the function of reassembling and delivering them when a single RLC SDU is received divided into multiple RLC SDUs, and may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0116] The NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

[0118] - Mapping function (Mapping between logical channels and transport channels)

[0119] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0120] - Scheduling information reporting function

[0121] - HARQ function (Error correction through HARQ)

[0122] - Priority handling between logical channels of one UE

[0123] - Priority handling between UEs by means of dynamic scheduling

[0124] - MBMS service identification function

[0125] - Transport format selection function

[0126] - Padding

[0128] The NR PHY layer (1d-20, 1d-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0130] FIG. 5 is a diagram illustrating cross-link interference when TDD cells are configured in a next-generation mobile communication system to which an embodiment of the present disclosure is applied.

[0131] Referring to FIG. 5, the effect of cross-link interference (CLI) on operating dynamic TDD scheduling / configuration in LTE and NR systems applicable to the entire present disclosure is illustrated. The present disclosure can be applied to such scenarios. Additionally, from the perspective of a base station, remote interference management (RIM) for a terminal can be performed by receiving and applying measurements of cross-link interference. For example, this can be achieved by applying dynamic TDD scheduling.

[0132] Referring to FIG. 5, a mobile communication network composed of TDD cells may exist in the vicinity. For example, as illustrated in FIG. 5, if a serving cell, gNB 1 (1e-05, or base station 1), to which terminal 1 (1e-15) is connected supports TDD in that cell, a surrounding cell, gNB 2 (1e-10, or base station 2), may also support TDD. At this time, terminal 2 (1e-20) connected to gNB 2 (1e-10) and receiving service may exist. Additionally, the downlink reference signal (1e-25) and data transmission transmitted from base station 1 (1e-05) to terminal 1 (1e-15) may be measured as uplink interference (1e-35) for base station 2 (1e-10). Additionally, the uplink SRS (sounding reference signal) transmission (1e-30) or data transmission transmitted by terminal 2 (1e-20) to base station 2 (1e-30), which is the serving cell of terminal 2 (1e-20), may be received as cross-link interference (1e-40) by a terminal receiving service from another serving cell (base station 1, 1e-05), such as terminal 1 (1e-15). Here, as the measurement value of cross-link interference, SRS-RSRP (SRS received signal received power, the RSRP value for the SRS resource measured by the terminal in the current serving cell against the SRS resource transmitted by the terminal in the surrounding cell), CLI-RSSI (CLI received signal strength indicator, the signal strength measured by the terminal in the current serving cell against all signals transmitted by the terminal in the surrounding cell), etc. According to one embodiment of the present disclosure, cross-link interference information (1e-40) between terminals may be taken into account when measuring cross-link interference.

[0133] The method of setting up and downlink symbols in an NR TDD system differs from that of an LTE system and can be summarized as follows.

[0135] 1) Cell-specific configuration: Flexible uplink and downlink symbol allocation via system information or common RRC signals

[0136] 2) UE-specific configuration: Allocate resources assigned as flexible symbols to uplink or downlink symbols via dedicated RRC messages.

[0137] 3) Setting via group common indication: Change flexible symbols via group-common PDCCH, i.e., SFI (slot format indicator).

[0138] 4) UE-specific indication: Change flexible symbols via UE-specific PDCCH, i.e., DCI (downlink control indicator).

[0140] In other words, in the NR TDD system, symbols for basic uplink transmission, flexible transmission, and downlink transmission supported by the cell are allocated for specific slots, and symbols allocated for flexible transmission can be changed to other transmission methods for each terminal. In this case, a symbol for flexible transmission refers to a flexible symbol that can be designated as a symbol for uplink and downlink transmission by the base station settings. If the corresponding flexible symbol is not changed for other transmission, neither uplink nor downlink transmission occurs for that symbol.

[0141] Referring to FIG. 5, in a cell supported by base station 1 (1e-05), TDD pattern 1 (1e-45, 1e-50, 1e-55) can be set. That is, in a slot consisting of a total of 14 symbols, 6 symbols (1e-45) for downlink transmission, 3 symbols (1e-50) for flexible transmission, and 5 symbols (1e-55) for uplink transmission can be set sequentially. Additionally, in a cell supported by base station 2 (1e-10), TDD pattern 2 (1e-65, 1e-70, 1e-75) can be set. That is, in a slot consisting of a total of 14 symbols, 2 symbols (1e-65) for downlink transmission, 1 symbol (1e-70) for flexible transmission, and 11 symbols (1e-75) for uplink transmission can be set sequentially. In this situation, terminal 1 (1e-15) and terminal 2 (1e-20), each belonging to base station 1 (1e-05) and base station 2 (1e-10), respectively, perform data transmission and reception and reference signal transmission and reception according to the TDD resource information set in each serving cell. A specific downlink section (1e-60) set in terminal 1 (1e-15) may overlap with a specific uplink section (1e-80) of a surrounding cell, and terminal 1 (1e-15), which is located at the edge of the cell, may be affected by interference from the surrounding cell. That is, cross-link interference may be received from terminal 2 (1e-20) during the downlink reception section (1e-60), which may cause a degradation in communication performance. More specifically, the interference signal may affect the downlink signal originally intended to be received, increasing the probability of failure in reception and decoding, and thus lowering the data transmission and reception rate.

[0142] In relation to the problem described above, when a terminal measures SRS-RSRP and CLI-RSSI for the interval (1e-60, 1e-80) in which the base station instructs the terminal to measure cross-link interference and reports the measured values ​​to the base station, the base station can determine the extent of the terminal's cross-link interference in that interval. Based on this, the base station can adjust the scheduling for resource allocation and can adjust the terminal's uplink / downlink transmission slots and symbols through dynamic TDD settings.

[0143] The overall scenario described with reference to Figure 5 is not limited to scenarios between TDD cells, and can be applied in situations where TDD cells and FDD cells are mixed, or in mobile communication networks composed only of FDD cells.

[0145] FIG. 6 is a diagram illustrating a procedure in which, in an NR system to which an embodiment of the present disclosure is applied, a terminal receives a measurement setting including cross-link interference from a base station and transmits a measurement value report thereon.

[0146] Terminal 1 (1f-01), which is in sleep mode (RRC_IDLE), finds a suitable cell during the cell (re)selection step and camps at the corresponding base station (1f-02) (1f-05), and can perform an RRC connection to the base station (1f-02) for reasons such as the occurrence of data to be transmitted (1f-10). Sleep mode is a state in which data cannot be transmitted because it is not connected to the network to save power of the terminal, and a transition to connected mode (RRC_CONNECTED) is required to transmit data. In addition, camping means that the terminal stays at the corresponding cell and receives paging messages to determine whether data is coming over the downlink. When terminal 1 (1f-01) successfully completes the RRC connection procedure with base station (1f-02), terminal 1 (1f-01) transitions to a connection mode (RRC_CONNECTED), and terminal 1 (1f-01) in the RRC connection mode can transmit and receive data with base station (1f-02).

[0147] A terminal in connected mode (RRC_CONNECTED) may be commanded to transmit and receive data through a newly connected cell / base station after a handover from another cell / base station as it moves into or out of the cell. To this end, the base station may provide a setting instructing a measurement of another frequency / cell (L3 measurement: downlink reference signal such as CSI-RS or SSB) via an RRC message (1f-15). Such measurement instructions may include targets, conditions, parameters, etc., that cause the terminal to report measurement results to the base station. Furthermore, in one embodiment of the present disclosure, the operation is characterized by receiving and performing a setting for measurement and reporting of cross-link interference described in FIG. 5, in addition to reporting through measurement of the existing downlink reference signal. In step 1f-15, the base station may provide measurement setting information (measConfig) to the terminal, and such setting information may include setting information related to CLI measurement and reporting in addition to the existing downlink reference signal measurement setting and reporting. Additionally, measurement configuration information (measConfig) may include measurement object settings (measObject), report settings (reportConfig), measurement identifier settings (measID) associated with the measurement object and reporting method, and settings indicating the types of values ​​to be measured (quantityConfig). MeasConfig signaling is indicated in the following ASN.1 for reference.

[0148]

[0149] The following describes the configuration information regarding cross-link interference in more detail. Refer to the MO-related ASN.1 below.

[0150]

[0151] 1. Setting the Measurement Object

[0152] First, regarding the Measurement Object (MO) configuration, there may be a method of reusing the measObjectNR currently used for measurement configuration in NR (first MO configuration method) and a method of using a new measObject for CLI measurement (e.g., measObject-CLI) (second MO configuration method).

[0153] The first MO configuration method can provide resource configuration information for measuring existing downlink reference signals (CSI-RS, SSB). Examples include frequency information for the measurement, sub-carrier spacing (SCS) information, smtc (SS / PBCH block Measurement Timing Configuration) settings, configuration information for beam measurement, reference signal type information, and black cell / white cell lists. If the measObjectNR described above is used as is for CLI measurement configuration, both conditions may be required.

[0155] - Omit configuration information (parameters) included in measObjectNR that is not necessary for CLI-specific (measurement) settings. (Since all field (parameter) settings included in measObjectNR are OPTIONAL, they can be omitted by adding conditions if they are for CLI measurement.)

[0156] - Added field (parameter) settings for CLI measurements to measObjectNR; from an ASN.1 perspective, new parameters can be added by extending existing settings. The aforementioned new setting information may include SRS resource settings, etc.

[0158] Furthermore, CLI measurements will be taken from the serving cell's downlink resources, which means measuring interference that conflicts with the serving cell's downlink resources. To achieve this, resources within a specific time-frequency range within the active downlink bandwidth part (BWP) must be allocated for CLI measurements. In other words, this means that only SCS resources, such as the active downlink BWP, can be measured. As a configuration condition for this, the measObjectNR where the CLI measurement is set must always be associated with the serving cell (servingCellMO). Refer to the field description below.

[0159]

[0160] In the second MO configuration method, a new MO may be used solely for CLI measurement, or a new MO may be used that can be universally applied to measure signals other than the downlink reference signal. Examples of measuring these other signals may include uplink delay measurements. In other words, the newly used measObject can be defined to include other types of MO or to perform reporting differently from the existing method. The new type of reporting may be in the form of transmitting log data. Furthermore, when using a new MO by applying the second MO configuration method, information regarding which serving cell the MO is associated with may be required. That is, additional information regarding which cell the configured MO is synchronized with may be necessary. This is because it is necessary to configure how the reference SFN of the MO to be measured is defined and how synchronization with other measurement frequencies is set. To achieve this, the following methods may be used.

[0162] - 2nd MO Setting Method-1: Add a condition to ensure that newly used MOs are always associated with the serving cell to which the corresponding settings apply (i.e., set fields such as frequency and SCS for new MOs to be associated with the serving cell, and add a condition to associate the MO with the servingCellMO).

[0163] - 2nd MO Setting Method-2: Add serving cell information to which the MO applies (cell index, or all cells synchronized with the corresponding frequency, etc.) within the newly used MO setting. In other words, if the corresponding CLI measurement setting is included, configure the MO per serving cell.

[0165] In addition, regarding the configuration of the Measurement Object, another consideration is how to add parameters for CLI measurement-related settings. This disclosure describes methods for adding CLI measurement parameters through the following two methods.

[0167] - Method for configuring CLI measurement parameters (1st method): Directly add configuration information for resources (such as SRS resources) for CLI measurement within the MO. This method extends the existing information element (IE) when using measObjectNR to explicitly specify the additional information required for SRS resource configuration. SRS resource configuration may include the number of ports through which SRS is transmitted, frequency domain resource information and frequency hopping, and the transmission method of the SRS resource (periodic, semi-periodic, non-periodic). This includes information on how the SRS resource to be measured is transmitted through which time-frequency resources.

[0168] - Method for setting second CLI measurement parameters: A method of indicating configuration information (such as SRS resources) for CLI measurement set within the MO by referring to existing SRS configurations (SRS-Config). That is, configuration information (such as SRS resources) for CLI measurement can be indicated by including index information (srs-ResourceId) for an SRS resource (SRS-Resource) or by using index information (srs-ResourceSetId) for an SRS-ResourceSet in which an SRS resource set is configured. To this end, when the base station provides SRS-Config in RRCReconfiguration, the SRS-Resource or SRS-ResourceSet configuration containing the SRS-Resource setting configured for CLI measurement may include information that a specific SRS resource (or an SRS resource included in the corresponding SRS resource set) is a resource setting for SRS measurement (CLI measurement) rather than a setting for SRS transmission. This information may be indicated through a 1-bit indicator (CLI measurement indicator). If such an indicator is missing, it can be determined as configuration information for SRS transmission.

[0169] .

[0170] In both of the methods for adding the two CLI measurement parameters described above, a single MO may include multiple SRS resource configuration information, or multiple SRS resource configuration information may be included in one or multiple SRS resource set information.

[0172] 2. Measurement Report Settings

[0173] In the measurement object configuration step described above, when an MO for CLI measurement is configured, the terminal measures the resources configured in that MO. At this time, it must be determined how the measurement results for that MO will be reported to the base station, and such reporting conditions and methods may be included in the measurement report configuration. Additionally, the measurement report configuration may be configured in association with a specific MO (the MO on which CLI measurement is configured). Below, measurement reporting methods according to one embodiment are described.

[0175] A. Periodic Report Configuration

[0176] ◆ New reference signal types for CLI measurements can be defined within PeriodicalReportConfig. Specifically, the existing IE can be extended to use rsType-v16xy for SRS-RSRSP and CLI-RSSI, and the period and the number of reports within the period can be included. Fields from the existing IE that are reusable can be reused, and only those requiring new configuration (e.g., rsType-v16xy) can be added. Refer to the existing ASN.1 structure below.

[0177]

[0178] B. Event-based reporting setup: The following two methods are possible

[0179] ◆ 1. Event-Based Reporting Method: Using New Event-Based Reporting for CLI Measurement Reporting

[0180] ● New Event (S1): When SRS-RSRP among the measurements associated with MO exceeds the set threshold:

[0181] The new event (S1) may have the same procedure as the existing A1 event, but a dedicated event may be used because the type of reference signal being measured is different. Refer to the existing A1 event below. That is, the new event (eventS1) may have the same parameters as the A1 event, but the type of reference signal applied to the a1-Threshold and the range of the threshold may differ. In other words, the existing MeasTriggerQuantity can be redefined and reused, or a new MeasTriggerQuantity can be defined and used exclusively for CLI measurements. This is because the threshold range of the RSRP applied to the existing downlink CSI-RS and SSB may differ from the threshold range of the RSRP applied to the uplink SRS. Additionally, a new mapping table and index may be used for mapping SRS-RSRP measurements to thresholds.

[0182]

[0183] In addition, regarding a new event (S1), depending on the number and method of reporting when multiple SRS resources are set, the following method for reporting event-based SRS resource measurements may be considered.

[0185] i) Multiple SRS Reporting Method 1: A method of reporting based on the measurement values ​​of each established SRS resource:

[0186] If at least one of the SRS resources configured in the MO exceeds a threshold and triggers a measurement report, the report may include measurement values ​​for all SRS resources included in the MO, or may include measurement values ​​only for the SRS resource that triggered the event.

[0187] ii) Multiple SRS Reporting Method 2: A method of reporting based on the average value of all configured SRS resources:

[0188] If the average of the measurements of the SRS resources configured in the MO exceeds a threshold and triggers a measurement report, the report may include the measurements for all SRS resources included in the MO, or it may include only the average measurement of the SRS resource that triggered the event.

[0190] In addition, a 1-bit indicator for selecting the above multiple SRS reporting first method and multiple SRS reporting second method may also be used.

[0191] ● New Event (S2): When SRS-RSRP among the measurements associated with MO is smaller than the set threshold:

[0192] In the case of a new event (S2), a new event (S2) (refer to the existing A2 event procedure) can be generated in the same way as the new event (S1) described above, and the contents described in the new event (S1) can be applied as is. However, according to one embodiment, the new event (S2) is not used, and a reportOnLeave function can be added to the new event (S1) described above. In this case, if the conditions of the new event (S1) are satisfied but subsequently the conditions of the new event (S1) are no longer satisfied, the new event (S2) can be replaced by performing a report on the new event (S1) again. This is because if the measured SRS-RSRP value is smaller than a specific threshold, the measurement value of the terminal that reported it may not be very important information from the base station's perspective. Additionally, if the new event (S2) is used, the burden on the terminal may increase due to frequent reporting of measurement values.

[0194] ◆ 2nd Event-Based Reporting Method: Extending the existing event-based reporting procedure and applying it to CLI measurement reporting

[0195] ● Reuse of Existing Event (A1): If the procedures applied to the existing Event A1 can be applied directly to CLI measurement reporting, reusing the existing A1 event procedures can be advantageous from a signal processing perspective. As shown in the ASN.1 example for the A1 event described above, existing parameters can be applied directly to CLI measurement and event reporting. To do this, it is necessary to verify whether SRS-RSRP can be applied to triggerQuantity (MeasTriggerQuantity). If the existing parameters can be applied to CLI measurement and event reporting, the RSRP mapping value within MeasTriggerQuantity must be applicable to SRS-RSRP when CLI measurement values ​​are set. As previously explained, since the range of parameters set based on downlink reference signals may differ from the range of parameters that must be set based on uplink SRS signals, the first event-based reporting method may be applied if these ranges differ.

[0196] ● When measuring CLI and reporting events, the issue of reusing Event A2 can be considered. In this case, the method for reusing Event A1 described above can be applied even when the threshold is below a certain level. However, as previously explained, Event A2 may not be used, and a reportOnLeave function can be added to the A1 event described above. In this case, if the conditions for Event A1 are satisfied but subsequently no longer are, Event A2 can be replaced by re-reporting the A1 event. This is because if the measured SRS-RSRP value is lower than a specific threshold, the measurement value reported by the terminal may not be of significant importance from the base station's perspective. Additionally, using Event A2 could increase the burden on the terminal due to frequent reporting of measurement values.

[0198] Terminal 1 (1f-01), having received the measurement value setting information described above, can send a confirmation message to the base station (1f-02) indicating that the setting information has been successfully received (1f-20). To this end, an RRCReconfigurationComplete message may be used. In step 1f-25, terminal 1 (1f-01) can perform data transmission and reception with the base station (1f-02). Additionally, in step 1f-30, terminal 1 (1f-01) starts a measurement of the measurement resources of the measurement targets (1f-31, 1f-32, 1f-33, 1f-34, 1f-35) that include the serving cell and CLI measurements set in step 1f-20. In step 1f-25, terminal 1 (1f-01) measures cell-level measurement results for MOs where downlink reference signals are set, measures the set SRS-RSRP and CLI-RSSI signals for MOs associated with CLI measurements, and determines the reporting conditions set by the base station (1f-02). The reporting conditions set by the base station (1f-02) may be set differently depending on whether it is within the frequency or between frequencies. In particular, for the inter-frequency channel measurement setting, carrier frequency information indicating the corresponding frequency is required. In step 1f-35, terminal 1 (1f-01) can trigger a measurement reporting procedure in accordance with the set measurement reporting conditions. At this time, the measurement reporting can be periodic reporting and event-based reporting. Detailed reporting settings may follow the reporting settings described in step 1f-15 of FIG. 6. In step 1f-40, terminal 1 (1f-01) can report the measurement results to the base station via an RRC message. These report messages may include serving cell and neighboring cell measurements and CLI measurements. That is, the report message may contain all serving cell and neighboring cell measurements and CLI measurements, or may include each of these measurements separately.

[0199] In step 1f-40, if Terminal 1 (1f-01) performs event-based reporting, the report message may include measurements for all SRS resources included in the MO, or only measurements for the SRS resource that triggered the event. The values ​​used for the measurement report may be actual measurements or average values ​​for the configured SRS resources. Additionally, the measurement report may not include measurements for the serving cell defined in the existing NR system. In the NR system, the terminal is always required to report measurements for the serving cell. Since SRS measurement and reporting are not closely related to serving cell measurements, the base station may ignore serving cell measurements even if it receives them (in the case of the terminal, it may include arbitrary values ​​in the serving cell measurements for reporting). In this case, the new Report configuration, ReportConfigNR-CLI, may be used instead of the existing ReportConfigNR. Alternatively, when reporting CLI measurements, the requirement may be restricted to always report measurements for the serving cell as well.

[0200] Subsequently, in step 1f-45, the base station (1f-02) can interpret the measurement value based on the measurement value received from terminal 1 (1f-01) and apply the interpretation result to network operation. For example, the interpretation result can be applied to a handover procedure and dynamic TDD scheduling.

[0202] FIG. 7 is a diagram illustrating a method for measuring and reporting cross-interference links of a terminal according to one embodiment of the present disclosure.

[0203] Previously, Figure 6 illustrated the entire procedure for measuring and reporting cross-interference links from a system perspective, and Figure 7 illustrated the operation from a terminal perspective.

[0204] A connected terminal can receive measurement settings from a base station in the 1g-05 stage. These measurement settings may include measObject, reportConfig, measID, quantitiConfig, etc. In particular, MO settings determine which signal should be measured through which resource. MO settings can be configured to use CSI-RS and SSB, which are types of existing downlink reference signals, as measurement objects, and may also include measurement information for CLI, including SRS-RSRP and CLI-RSSI. MO settings for CLI may consider the following matters, and for detailed information and explanation, refer to FIG. 6.

[0206] - Use existing MO or use new MO for CLI measurement

[0207] - Method for including SRS resource configuration information for CLI (list all in MO or include SRS resource configuration index to be measured)

[0208] - How to associate a set MO with a serving cell

[0209] Additionally, the measurement settings received in step 1g-05 may additionally include reporting settings, and in particular, may include reporting conditions associated with MO for CLI. This disclosure focuses on event-based reporting, and for detailed information and description, refer to FIG. 6.

[0210] - Event definition for cases where SRS-RSRP measurement exceeds threshold: Reuse existing A1 event or use new S1 event

[0211] - Number of reporting and method when multiple SRS resources are configured

[0212] ■ How to report only the measures for the SRS resource that triggered the event, or to report all measures for the configured SRS resources

[0213] ■ Methods where the measured value follows the actual SRS-RSRP value or uses the average of the measurements of the configured SRS resources

[0214] ■ How to use a threshold range different from the thresholds used for existing RS measurements and event triggering (SRS only), and how to use new CLI measurement reporting settings through this.

[0216] In step 1g-10, the terminal performs a measurement for the configured MO according to the measurement setting received in step 1g-05. In step 1g-10, if there is an MO setting associated with CLI, the terminal measures the SRS resources configured in the MO, and in this case, performs a measurement on the time-frequency resources within the active downlink BWP.

[0217] In step 1g-15, the terminal checks the reporting conditions for the measured CLI measurement, and if the reporting conditions are satisfied, prepares to report the measured value by including it in the measurement results. Depending on the measurement reporting conditions, both periodic reporting and event-based reporting are possible, and in the case of event reporting, if the measured value exceeds a threshold based on SRS-RSRP, the reporting procedure can be triggered by reusing an A1 event or using a new S1 event.

[0218] In step 1g-20, the measurement results, which are the measurements generated in step 1g-15, are stored in an RRC message and transmitted to the base station. Subsequently, the terminal can perform a handover or resource reconfiguration according to the RRCReconfiguration message transmitted by the base station.

[0220] FIG. 8 is a diagram illustrating the operation method of a terminal when an event-based measurement report is set for a cross-interference link according to one embodiment of the present disclosure.

[0221] In step 1h-05, the terminal receives an event-based measurement reporting configuration associated with an MO that includes configuration information for CLI measurement. The event-based measurement reporting configuration associated with the MO may be received by including the measurement configuration information in the RRCReconfiguration message. For details regarding the configuration information, refer to the description of step 1f-15 in Fig. 6. Fig. 8 is a diagram illustrating the case where event-based measurement reporting is configured for an MO for CLI measurement. In step 1h-10, the terminal can trigger an event-based reporting procedure based on whether the measurement value (SRS-RSRP) for the SRS resource in the configured CLI measurement MO exceeds a threshold value. The event-based reporting procedure can operate like an existing A1 event, and the threshold value applied can reuse the value defined in the existing A1 event or be redefined to a value with a new range. This is because the RSRP ranges of the uplink reference signal and the downlink reference signal may be applied differently. If a new RSRP range is used, it can be redefined as a range for SRS-RSRP measurements and applied only to CLI measurements, specifically SRS-RSRP mapping. Additionally, a new event (e.g., S1) can be introduced instead of reusing the A1 event, and the entire procedure can be applied as is to the A1 procedure. In particular, the ReportOnLeave setting and operation can also be introduced as is, which allows the introduction of the A2 event (or S2 event) to be omitted. The A2 and S2 events are triggered when the measured SRS-RSRP value falls below a threshold, and while the A2 and S2 events may be used in one embodiment, similar functions can be replaced by the A1 (S1) event and ReportOnLeave.

[0222] In step 1h-15, if the CLI measurement result satisfies a specific event condition based on the measurement result from step 1h-10, the terminal triggers the measurement value reporting procedure and stores the measurement value. In step 1h-20, the terminal may behave differently depending on the reporting method configured for the terminal. That is, if the MO configured for CLI measurement includes multiple SRS resource configurations (explicitly including information on the SRS resource to be measured or including an index of the SRS resource to be measured), the terminal may use the measurement value applied to event triggering as a value based on the actual measurement value or the average measurement value. If it is configured to report based on the actually measured SRS-RSRP, the terminal proceeds to step 1h-25 and includes the actually measured CLI measurement values ​​in the measurement results. At this time, it may include only the measurement information for the SRS resource that triggered the event, or it may include measurement information for all SRS resources included in the configured MO. Additionally, the measurement information may include the SRS-RSRP value by default, and the CLI-RSSI value may also be included. In step 1h-30, if the leaving condition for the event is satisfied, the terminal re-reports the event (1h-35). The following are the entering condition and leaving condition for the A1 event, and these conditions can be applied to the event as they are. If the leaving condition is not satisfied in step 1h-30, no separate action is performed.

[0224] Inequality A1-1 (Entering condition)

[0225] Ms - Hys > Thresh

[0226] Inequality A1-2 (Leaving condition)

[0227] Ms + Hys < Thresh

[0229] If multiple SRS resource settings are included in the MO configured for CLI measurement in step 1h-20 (explicitly including information on the SRS resource to be measured or including an index of the SRS resource to be measured), the terminal may use the measurement value applied to event triggering as a value based on the average measurement value rather than the actual measurement value. If such a setting is applied, the terminal proceeds to step 1h-40 and may include the average value of the measurement value in the measurement result, rather than including the actual measured CLI values. Even in this case, it may include only the measurement information for the SRS resource that triggered the event, or include measurement information for all SRS resources included in the configured MO. Additionally, the measurement information may include the SRS-RSRP value by default, and the CLI-RSSI value may also be included. In step 1h-45, if the leaving condition for the event is satisfied, the terminal re-reports the event (1h-50). The following are the entering condition and leaving condition for the A1 event, and these conditions may be applied to the event as they are. If the leaving condition is not satisfied in step 1h-45, no separate action is performed.

[0231] Inequality A1-1 (Entering condition)

[0232] Ms - Hys > Thresh

[0233] Inequality A1-2 (Leaving condition)

[0234] Ms + Hys < Thresh

[0236] FIG. 9 is a diagram illustrating a method for measuring and reporting cross-interference links of a base station according to one embodiment of the present disclosure.

[0237] FIG. 9 includes the details of a base station creating and transmitting a measurement setting for CLI measurement to a terminal, and for details, refer to the relevant description in FIG. 6.

[0238] If an RRC-connected terminal exists, the base station can provide measurement setting information to the terminal through RRC settings to apply to subsequent terminal mobility and scheduling. In this disclosure, the part related to CLI measurement is described in detail, and in FIG. 9, general technology is omitted and only the CLI measurement part is described.

[0239] First, in step 1i-05, the base station may generate measurement setting information for CLI measurement, and this setting information may include MO settings that include SRS resource settings. The MO settings in step 1i-05 may use the existing measObjectNR as is, or introduce a new MO (measObjectNR-CLI) and include CLI-only settings. For these MO settings, refer to the description of step 1f-15 in FIG. 6.

[0240] Subsequently, in step 1i-10, the base station may generate setting information for reporting in the measurement setting information for CLI measurement. At this time, periodic reporting and event-based measurement reporting may be set separately, and the setting information for reporting may include parameters related to the conditions and methods required for reporting. For such setting information for reporting, refer to the description of step 1f-15 in FIG. 6.

[0241] The base station receives the measurement configuration information set in steps 1i-05 and 1i-10 and transmits the configuration information for CLI measurement and reporting to the terminal via an RRCReconfiguration message. At this time, the measurement configuration procedure in the NR system may be applied, and the terminal receiving this can perform CLI measurement and reporting according to the information transmitted by the base station. In step 1i-20, the base station receives the measurement results included in the measurement report transmitted by the terminal. The measurement results include CLI measurement results according to the reporting conditions associated with the MO related to the configured CLI measurement. In step 1i-25, if the received measurement report is a measurement result for the serving cell and surrounding cells associated with the existing downlink received signal, the base station proceeds to step 1i-30 and can determine a handover based on the received measurement values. Additionally, in step 1i-35, the base station can perform the handover procedure.

[0242] However, if the measurement report received in step 1i-25 is a measurement result associated with the CLI measurement value, the base station may proceed to step 1i-40 and decide to dynamically allocate TDD resources based on the measurement result. Additionally, in step 1i-45, the base station may perform dynamic TDD scheduling directly or perform scheduling within existing resources to reduce interference. In this case, dynamic TDD resource scheduling means that if the CLI measurement result from the terminal indicates that cross-link interference is significant in the corresponding DL measurement resource, that resource is not changed from a TDD resource to an uplink transmission resource. Furthermore, resources with low interference may be changed to uplink transmission resource time.

[0244] FIG. 10 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.

[0245] Referring to FIG. 10, the terminal includes an RF (Radio Frequency) processing unit (1j-10), a baseband processing unit (1j-20), a storage unit (1j-30), and a control unit (1j-40).

[0246] The RF processing unit (1j-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1j-10) up-converts the baseband signal provided by the baseband processing unit (1j-20) into an RF band signal, transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1j-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. Although only one antenna is shown in the drawing, the terminal may be equipped with multiple antennas. Additionally, the RF processing unit (1j-10) may include multiple RF chains. Furthermore, the RF processing unit (1j-10) may perform beamforming. For beamforming, the RF processing unit (1j-10) can adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation.

[0247] The baseband processing unit (1j-20) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1j-20) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1j-20) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1j-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (1j-20) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. Additionally, upon receiving data, the baseband processing unit (1j-20) divides the baseband signal provided by the RF processing unit (1j-10) into OFDM symbol units, restores the signals mapped to subcarriers through a fast Fourier transform (FFT) operation, and then restores the received bit sequence through demodulation and decoding.

[0248] The baseband processing unit (1j-20) and the RF processing unit (1j-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (1j-20) and the RF processing unit (1j-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (1j-20) and the RF processing unit (1j-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (1j-20) and the RF processing unit (1j-10) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular network (e.g., LTE), etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2 NRHz, NRHz) and millimeter wave (e.g., 60 GHz) bands.

[0249] The storage unit (1j-30) stores data such as basic programs, application programs, and configuration information for the operation of the terminal. In particular, the storage unit (1j-30) can store information related to a second connection node that performs wireless communication using the second wireless connection technology. Additionally, the storage unit (1j-30) provides the stored data upon the request of the control unit (1j-40).

[0250] The control unit (1j-40) controls the overall operations of the terminal. For example, the control unit (1j-40) transmits and receives signals through the baseband processing unit (1j-20) and the RF processing unit (1j-10). Additionally, the control unit (1j-40) writes and reads data to and from the storage unit (1j-40). To this end, the control unit (1j-40) may include at least one processor. For example, the control unit (1j-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.

[0252] FIG. 11 is a block diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0253] As illustrated in FIG. 11, the base station is configured to include an RF processing unit (1k-10), a baseband processing unit (1k-20), a backhaul communication unit (1k-30), a storage unit (1k-40), and a control unit (1k-50).

[0254] The RF processing unit (1k-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1k-10) up-converts the baseband signal provided by the baseband processing unit (1k-20) into an RF band signal, transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1k-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in the drawing, the first connection node may be equipped with multiple antennas. Additionally, the RF processing unit (1k-10) may include multiple RF chains. Furthermore, the RF processing unit (1k-10) may perform beamforming. For beamforming, the RF processing unit (1k-10) may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform down-to-down MIMO operation by transmitting one or more layers.

[0255] The baseband processing unit (1k-20) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1k-20) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1k-20) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1k-10). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (1k-20) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (1k-20) divides the baseband signal provided by the RF processing unit (1k-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operations, and then restores the received bit sequence through demodulation and decoding. The baseband processing unit (1k-20) and the RF processing unit (1k-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (1k-20) and the RF processing unit (1k-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0256] The backhaul communication unit (1k-30) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (1k-30) converts a bit sequence transmitted from the main base station to other nodes, such as an auxiliary base station or a core network, into a physical signal, and converts a physical signal received from other nodes into a bit sequence.

[0257] The storage unit (1k-40) stores data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (1k-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (1k-40) can store information that serves as a criterion for determining whether to provide multiple connections to the terminals or to disconnect them. Furthermore, the storage unit (1k-40) provides the stored data upon the request of the control unit (1k-50).

[0258] The control unit (1k-50) controls the overall operations of the main station. For example, the control unit (1k-50) transmits and receives signals through the baseband processing unit (1k-20) and the RF processing unit (1k-10) or through the backhaul communication unit (1k-30). Additionally, the control unit (1k-50) writes and reads data to and from the storage unit (1k-40). To this end, the control unit (1k-50) may include at least one processor.

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

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

[0262] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0263] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0265] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0266] Meanwhile, the embodiments disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of this disclosure and to aid in understanding this disclosure, and are not intended to limit the scope of this disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of this disclosure are possible. Furthermore, each embodiment may be combined and operated with one another as needed. For example, parts of one embodiment of this disclosure and another embodiment may be combined with each other. Additionally, other variations based on the technical concept of the embodiments described above may be implemented in other systems, such as LTE systems, 5G or NR systems.

Claims

Claim 1 A method for a user device to measure and report cross-link interference (CLI) in a wireless communication system comprises: receiving a measurement configuration including a CLI measurement object from a base station; performing a measurement on at least one CLI measurement resource of the CLI measurement object; identifying a first measurement value for a CLI measurement resource among the at least one CLI measurement resource; and transmitting a measurement report for a CLI measurement resource among the at least one CLI measurement resource to the base station when an event-based CLI measurement report is set and a triggering condition associated with exceeding a threshold for the CLI measurement resource is satisfied based on the first measurement value, wherein the CLI measurement object includes information regarding the at least one CLI measurement resource and an index of at least one serving cell associated with the at least one CLI measurement resource. Claim 2 A method according to claim 1, wherein the threshold is a value associated with the at least one CLI measurement resource. Claim 3 A method according to claim 1, comprising: identifying a second measurement value for a CLI measurement resource among at least one CLI measurement resource; and transmitting a measurement report for a CLI measurement resource when an event-based CLI measurement report is set and a leaving condition associated with being less than a threshold is satisfied for the CLI measurement resource based on the second measurement value. Claim 4 A method according to claim 3, further comprising: a step of identifying that the triggering condition is satisfied based on the value obtained by subtracting hysteresis from the first measurement value exceeding the threshold; and a step of identifying that the exit condition is satisfied based on the value obtained by adding the hysteresis to the second measurement value being less than the threshold. Claim 5 A method according to claim 1, wherein the step of performing the measurement comprises the step of performing the measurement on all of the at least one CLI measurement resources of the CLI measurement object. Claim 6 delete Claim 7 A method according to claim 1, wherein the at least one CLI measurement resource comprises at least one of a sounding reference signal (SRS) resource or a resource for measuring cross-link interference-received signal strength indication (CLI-RSSI). Claim 8 A method according to claim 1, wherein the measurement report comprises at least one of SRS-RSRP (sounding reference signal-reference signal received power) or CLI-RSSI (cross link interference-received signal strength indication). Claim 9 A method according to claim 1, wherein the step of transmitting the measurement report comprises the step of transmitting a measurement report regarding the serving cell of the user terminal to the base station. Claim 10 A method according to claim 1, further comprising the step of periodically transmitting the measurement report to the base station. Claim 11 A user equipment for measuring and reporting cross-link interference (CLI) in a wireless communication system, wherein the user equipment comprises: a transceiver; and at least one processor, wherein the at least one processor receives a measurement configuration including a CLI measurement object from a base station, performs a measurement on at least one CLI measurement resource of the CLI measurement object, identifies a first measurement value for a CLI measurement resource among the at least one CLI measurement resource, and controls the transceiver to transmit a measurement report on the CLI measurement resource among the at least one CLI measurement resource to the base station when an event-based CLI measurement report is configured and a triggering condition associated with exceeding a threshold for the CLI measurement resource based on the first measurement value is satisfied, wherein the CLI measurement object includes information regarding the at least one CLI measurement resource and an index of at least one serving cell associated with the at least one CLI measurement resource. Claim 12 A user terminal according to claim 11, wherein the threshold is a value associated with the at least one CLI measurement resource. Claim 13 A user terminal according to claim 11, wherein the at least one processor identifies a second measurement value for the CLI measurement resource among the at least one CLI measurement resources and controls the transceiver to transmit a measurement report for the CLI measurement resource when the event-based CLI measurement report is set and a leaving condition associated with being less than a threshold is satisfied for the CLI measurement resource based on the second measurement value. Claim 14 A user terminal according to claim 13, wherein the at least one processor is configured to identify that the triggering condition is satisfied based on the value obtained by subtracting hysteresis from the first measurement value exceeding the threshold, and to identify that the exit condition is satisfied based on the value obtained by adding the hysteresis to the second measurement value being less than the threshold. Claim 15 A user terminal according to claim 11, wherein the at least one processor is configured to perform measurements on all of the at least one CLI measurement resources of the CLI measurement object. Claim 16 delete Claim 17 A user terminal according to claim 11, wherein the at least one CLI measurement resource comprises at least one of a sounding reference signal (SRS) resource or a resource for measuring cross-link interference-received signal strength indication (CLI-RSSI). Claim 18 A user terminal according to claim 11, wherein the measurement report comprises at least one of SRS-RSRP (sounding reference signal-reference signal received power) or CLI-RSSI (cross link interference-received signal strength indication). Claim 19 A user terminal according to claim 11, wherein the at least one processor is configured to control the transceiver to transmit a measurement report regarding the serving cell of the user terminal to the base station. Claim 20 A user terminal according to claim 11, wherein the at least one processor is configured to control the transceiver to periodically transmit the measurement report to the base station.

Images