Method and apparatus for controlling inter-UE cross link interference due to sub-band full duplication in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. This method performed by a user equipment (UE) in a wireless communication system comprises the steps of: receiving, from a base station through radio resource control (RRC) signaling, information configuring a resource set for cross link interference (CLI) measurement and information configuring a report for the CLI measurement; receiving, from the base station, a medium access control (MAC) control element (CE) for activating at least one resource for the CLI measurement; performing the CLI measurement on the at least one resource; and transmitting a report of the CLI measurement to the base station.

Description

Method and device for controlling cross link interference between terminals due to sub-band full duplication in a wireless communication system

[0001] The present disclosure relates to a method for eliminating interference between terminals due to a transmission mode in a mobile communication system.

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

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

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

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

[0006] 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).

[0007] 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 could serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing this technology.

[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for providing these services effectively are required.

[0009] Based on the discussion described above, the present disclosure seeks to provide a method and device for controlling cross link interference between terminals that may occur when considering subband full duplex in a wireless communication system.

[0010] In order to solve the above problems, the present invention provides a method performed by a user equipment (UE) in a wireless communication system, the method including: receiving, from a base station through radio resource control (RRC) signaling, information for setting a resource set for cross link interference (CLI) measurement and information for setting a report for the CLI measurement; receiving, from the base station, a medium access control (MAC) control element (CE) for activating at least one resource for the CLI measurement; performing the CLI measurement on the at least one resource; and transmitting a report of the CLI measurement to the base station.

[0011] The present disclosure can provide a method and device capable of effectively controlling cross link interference between terminals.

[0012] According to an embodiment of the present invention, each cell can reduce interference signals between terminals within the cell.

[0013] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, 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.

[0014] Figure 1 illustrates the structure of a wireless communication system.

[0015] Figure 2 illustrates the wireless protocol structure of a wireless communication system.

[0016] FIG. 3 is a diagram illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 4 illustrates a wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 5 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0019] FIG. 6 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0020] Figure 7 is a diagram for explaining the occurrence of inter-cell CLI (cross link interference) between cells operating a general SBFD (sub-band full duplex).

[0021] FIG. 8 is a diagram for explaining the occurrence of intra-cell inter UE CLI within one cell operating SBFD according to one embodiment of the present disclosure.

[0022] FIG. 9 illustrates a method in which a terminal in one cell transmits CLI-SRS and a terminal in another cell measures CLI-SRS in different cells operating different SBFD settings according to one embodiment of the present disclosure.

[0023] FIG. 10 is a flowchart of a procedure for resolving inter-cell inter-gNB inter UE CLI according to one embodiment of the present disclosure.

[0024] FIG. 11 is a flowchart of a procedure for requesting CLI measurements between inter-cell inter-DUs according to one embodiment of the present disclosure.

[0025] FIG. 12 is a flowchart of a CLI measurement and reporting procedure according to one embodiment of the present disclosure.

[0026] FIG. 13 is a flowchart of a procedure for performing a periodic CLI report when a periodic SRS is set according to one embodiment of the present disclosure.

[0027] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0028] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below 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 solely 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 invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0029] The 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, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0030] Hereinafter, the base station is an entity that performs resource allocation of the 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, the downlink (DL) refers to a wireless transmission path of a signal transmitted from the base station to the terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from the terminal to the base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel form. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure may be applied, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure. It will be appreciated that each block of the processing flow diagrams and combinations of the flow diagrams can be executed by computer program instructions.

[0031] These computer program instructions may be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for performing the functions described in the flowchart block(s). These computer program instructions may also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing apparatus to implement functions in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be installed on a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable data processing apparatus to create a computer-implemented process, so that the instructions executing on the computer or other programmable data processing apparatus can provide steps for performing the functions described in the flowchart block(s).

[0032] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function. In this case, the term '~unit' used in the present embodiment means software or a hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the '~unit' may perform certain roles. However, the '~unit' is not limited to software or hardware. The '~unit' may be configured to be on an addressable storage medium and may be configured to execute one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Also, in an embodiment, the '~ unit' may include one or more processors.

[0033] For convenience of explanation, the present invention uses terms and names defined in the 5GS and NR standards, which are standards defined by the 3rd Generation Partnership Project (3GPP), among the existing communication standards. However, the present invention is not limited to the above terms and names and can be equally applied to wireless communication networks that follow other standards. For example, the present invention can be applied to the 3GPP 5GS / NR (5th generation mobile communication standard).

[0034] Figure 1 illustrates the structure of a wireless communication system.

[0035] Referring to FIG. 1, a wireless access network of an LTE system may be composed of next-generation base stations (Evolved Node Bs) (hereinafter referred to as 'ENBs, Node Bs or base stations') (105, 110, 115, 120), a mobility management entity (MME) (125) and a serving gateway (S-GW) (130). A user equipment (UE or terminal) (135) may access an external network through the ENBs (105 to 120) and the S-GW (130).

[0036] In Fig. 1, ENBs (105 to 120) may correspond to existing Node Bs of a Universal Mobile Telecommunication System (UMTS) system. ENBs are connected to UEs (135) via a wireless channel and may perform more complex roles than existing Node Bs. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, and ENBs (105 to 120) may be responsible for this. One ENB can typically control multiple cells. For example, in order to implement a transmission speed of 100 Mbps, an LTE system may use, for example, Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. Additionally, the LTE system can apply an adaptive modulation and coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel condition of the terminal. The S-GW (130) is a device that provides a data bearer and can create or remove a data bearer according to the control of the MME (125). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.

[0037] Figure 2 illustrates the wireless protocol structure of a wireless communication system.

[0038] Referring to Figure 2, the wireless protocol of the LTE system may be composed of Packet Data Convergence Protocol (PDCP) (205, 240), Radio Link Control (RLC) (210, 235), and Medium Access Control (MAC) (215, 230) in the terminal and ENB, respectively. PDCP may be responsible for operations such as IP header compression / decompression. The main functions of PDCP can be summarized as follows.

[0039] - Header compression and decompression (ROHC only)

[0040] - User data transfer function

[0041] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

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

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

[0044] - 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)

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

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

[0047] Radio Link Control (RLC) (210, 235) can perform ARQ operations, etc. by reconfiguring PDCP packet data units (PDUs) to an appropriate size. The main functions of RLC can be summarized as follows.

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

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

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

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

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

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

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

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

[0056] - RLC re-establishment function

[0057] MAC (215, 230) is connected to multiple RLC layer devices configured in a single terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

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

[0059] - 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)

[0060] - Scheduling information reporting function

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

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

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

[0064] - MBMS service identification function

[0065] - Transport format selection function

[0066] - Padding function

[0067] The physical layer (220, 225) can perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0068] FIG. 3 is a diagram illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0069] Referring to FIG. 3, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 5g) may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (310) and a next-generation radio core network (New Radio Core Network, NR CN) (305). A next-generation radio user equipment (NR UE or terminal) (315) may access an external network through the NR gNB (310) and the NR CN (305).

[0070] In Fig. 3, the NR gNB (310) may correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (315) via a wireless channel and can provide a service superior to that of the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device that collects status information such as the buffer status of the UEs, the available transmission power status, and the channel status and performs scheduling is required, and the NR NB (310) can be in charge of such scheduling. A single NR gNB can control multiple cells. In the next-generation mobile communication system, in order to implement ultra-high-speed data transmission compared to the general LTE, a bandwidth greater than the general maximum bandwidth may be applied. In addition, beamforming technology may be additionally grafted using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. In addition, the next-generation system may apply an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel condition of the terminal. The NR CN (305) may perform functions such as mobility support, bearer setup, and QoS setup. The NR CN is a device that is responsible for various control functions as well as mobility management functions for the terminal and may be connected to multiple base stations. In addition, the next-generation mobile communication system may also be linked with the LTE system, and the NR CN may be connected to the MME (325) through a network interface. The MME may be connected to an eNB (330), which is an LTE base station.

[0071] FIG. 4 illustrates a wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0072] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system is composed of NR Service Data Adaptation Protocol (SDAP) (401, 445), NR PDCP (405, 440), NR RLC (410, 435), NR MAC (415, 430), and NR PHY (420, 425) in the terminal and NR base station, respectively.

[0073] The main functions of NR SDAP (401, 445) may include some of the following functions:

[0074] - Transfer of user plane data

[0075] - Mapping function between QoS flow and data bearer for both DL and UL

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

[0077] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0078] For an SDAP layer device, a terminal can be configured via a Radio Resource Control (RRC) message whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. When the SDAP header is configured, the terminal can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink with a 1-bit indicator for reflecting the Non-Access Stratum (NAS) Quality of Service (QoS) of the SDAP header (e.g., NAS reflective QoS) and a 1-bit indicator for reflecting the Access Stratum (AS) QoS of the SDAP header (e.g., AS reflective QoS). The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

[0079] The main functions of NR PDCP (405, 440) may include some of the following functions:

[0080] - Header compression and decompression (ROHC only)

[0081] - User data transfer function

[0082] - In-sequence delivery of upper layer PDUs

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

[0084] - PDCP PDU reordering for reception

[0085] - Duplicate detection of lower layer SDUs

[0086] - Retransmission function (Retransmission of PDCP SDUs)

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

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

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

[0090] The main functions of NR RLC (410, 435) may include some of the following functions:

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

[0092] - In-sequence delivery of upper layer PDUs

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

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

[0095] - Concatenation, segmentation and reassembly of RLC SDUs

[0096] - Re-segmentation of RLC data PDUs

[0097] - Reordering of RLC data PDUs

[0098] - Duplicate detection function

[0099] - Protocol error detection

[0100] - RLC SDU discard function

[0101] - RLC re-establishment function

[0102] In the above, the in-sequence delivery function of the NR RLC device may refer to the function of sequentially delivering RLC SDUs received from the lower layer to the upper layer. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.

[0103] The in-sequence delivery function of the NR RLC device may include a function to reorder received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by reordering them, a function to report status of lost RLC PDUs to the transmitter, and a function to request retransmission of lost RLC PDUs.

[0104] The in-sequence delivery function of the NR RLC device may include a function to sequentially deliver only the RLC SDUs up to the lost RLC SDU to the upper layer when there is a lost RLC SDU.

[0105] The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received before a predetermined timer starts to the upper layer in sequence, even if there are lost RLC SDUs, if the timer has expired.

[0106] The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to now to the upper layer in order if a predetermined timer has expired, even if there are lost RLC SDUs.

[0107] An NR RLC device can process RLC PDUs in the order they are received and deliver them to an NR PDCP device, regardless of the order of the sequence number (out-of-sequence delivery).

[0108] When an NR RLC device receives a segment, it can receive segments that are stored in a buffer or will be received later, reconstruct them into a complete RLC PDU, and then transmit them to the NR PDCP device.

[0109] The NR RLC layer may not include concatenation functionality, and the functionality may be performed by the NR MAC layer or replaced by the multiplexing functionality of the NR MAC layer.

[0110] In the above, the out-of-sequence delivery function of the NR RLC device may refer to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order. The out-of-sequence delivery function of the NR RLC device may include the function of reassembling and delivering the RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs. The out-of-sequence delivery function of the NR RLC device may include the function of storing and arranging the RLC SN or PDCP SN of the received RLC PDUs to record the lost RLC PDUs.

[0111] NR MAC (415, 430) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

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

[0113] - Multiplexing / demultiplexing of MAC SDUs

[0114] - Scheduling information reporting function

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

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

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

[0118] - MBMS service identification function

[0119] - Transport format selection function

[0120] - Padding function

[0121] The NR PHY layer (420, 425) can perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0122] FIG. 5 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0123] Referring to FIG. 5, the terminal includes an RF (Radio Frequency) processing unit (510), a baseband processing unit (520), a storage unit (530), and a control unit (540).

[0124] The RF processing unit (510) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (510) up-converts the baseband signal provided from the baseband processing unit (520) into an RF band signal and 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 (510) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. Although the terminal is illustrated with only one antenna in FIG. 5, the terminal is not limited thereto, and the terminal may be equipped with multiple antennas. In addition, the RF processing unit (510) may include multiple RF chains. Furthermore, the RF processing unit (510) may perform beamforming. For beamforming, the RF processing unit (510) can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and receive multiple layers when performing MIMO operations.

[0125] The baseband processing unit (520) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (520) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (520) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (510). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (520) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (520) divides the baseband signal provided from the RF processing unit (510) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.

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

[0127] The storage unit (530) stores data such as basic programs, application programs, and configuration information for the operation of the terminal. In particular, the storage unit (530) can store information related to a second access node that performs wireless communication using a second wireless access technology. Furthermore, the storage unit (530) provides the stored data upon request from the control unit (540).

[0128] The control unit (540) controls the overall operations of the terminal. For example, the control unit (540) transmits and receives signals through the baseband processing unit (520) and the RF processing unit (510). In addition, the control unit (540) records and reads data in the storage unit (540). For this purpose, the control unit (540) may include at least one processor. For example, the control unit (540) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. According to various embodiments, the control unit (540) may be configured to perform various operations described below.

[0129] FIG. 6 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0130] As shown in the drawing, the base station is configured to include an RF processing unit (610), a baseband processing unit (620), a backhaul communication unit (630), a storage unit (640), and a control unit (650).

[0131] The RF processing unit (610) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (610) upconverts the baseband signal provided from the baseband processing unit (620) into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (610) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In FIG. 6, the first access node is illustrated as including only one antenna, but the first access node may have multiple antennas. In addition, the RF processing unit (610) may include multiple RF chains. Furthermore, the RF processing unit (610) may perform beamforming. For beamforming, the RF processing unit (610) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform downlink MIMO operations by transmitting one or more layers.

[0132] The baseband processing unit (620) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (620) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (620) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (610). For example, in the case of OFDM, when transmitting data, the baseband processing unit (620) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (620) divides the baseband signal provided from the RF processing unit (610) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (620) and the RF processing unit (610) transmit and receive signals as described above. Accordingly, the baseband processing unit (620) and the RF processing unit (610) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0133] The backhaul communication unit (630) provides an interface for communicating with other nodes within the network. The backhaul communication unit (630) converts a bit stream transmitted from a primary base station to other nodes, such as auxiliary base stations or core networks, into a physical signal, and converts a physical signal received from other nodes into a bit stream.

[0134] The storage unit (640) stores data such as basic programs, application programs, and configuration information for the operation of the main base station. In particular, the storage unit (640) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. Furthermore, the storage unit (640) can store information that serves as a basis for determining whether to provide or terminate multiple connections to a terminal. Furthermore, the storage unit (640) provides the stored data upon request from the control unit (650).

[0135] The control unit (650) controls the overall operations of the base station. For example, the control unit (650) transmits and receives signals through the baseband processing unit (620) and the RF processing unit (610) or through the backhaul communication unit (630). In addition, the control unit (650) records and reads data from the storage unit (640). For this purpose, the control unit (650) may include at least one processor (or controller). According to various embodiments, the control unit (650) may be configured to perform various operations described below.

[0136] The basic duplexing scheme of Release 15 NR can include time division duplex (TDD) and frequency division duplex (FDD). In particular, in the case of TDD, it includes dynamic TDD, and the base station can operate cell-based semi-static TDD configuration, and transmit DL / UL / flexible indications for each slot and each symbol within that slot in SIB1 (system information block 1). The base station can additionally configure each terminal and additionally indicate that a given flexible symbol can be identified as DL or UL. This allows the DL / UL configuration to be configured differently for each terminal on a symbol-by-symbol basis. Through this scheme, the base station can adaptively schedule UL / DL traffic for each terminal and cell, and in the case of UL, it can also achieve the effect of coverage extension.

[0137] To prepare for these TDD systems, Release 19 introduced an additional duplexing scheme called subband full duplex (SBFD). SBFD, in addition to the existing TDD configuration, allows for separate frequency ranges for the UL subband and DL subband for DL ​​or flexible slots or symbols. Accordingly, for a single SBFD symbol, UL resources can be allocated to a specific terminal in the UL subband, and DL resources can be allocated to a different terminal in the DL subband.

[0138] Accordingly, UL and DL can coexist in one symbol or slot in one cell.

[0139] However, in the case of existing dynamic TDD, if the frame synchronization between cells is not aligned or the TDD settings are different, UL and DL may occur simultaneously, which may result in interference between terminals between cells or between base stations of the cells. In addition, when SBFD is considered, interference may occur between legacy terminals and SBFD-capable terminals within a single cell, and inter-cell interference may also exist. The degree of interference is greater than the interference caused by simple DL / UL settings through existing TDD, and it can change dynamically.

[0140] Figure 7 is a diagram illustrating the occurrence of inter-cell CLI (cross link interference) when operating a typical SBFD. Referring to Figure 7, the UL signal received by Cell 2 from UE 2 may cause interference with the DL signal intended for UE 1 in Cell 1. In this situation where UE 1 receives an unnecessary interference signal from UE 2, UE 1 becomes a victim UE and UE 2 becomes an aggressor UE. Similarly, Cell 2 becomes a victim cell and Cell 1 becomes an aggressor cell.

[0141] In terms of the resources allocated in each cell, the DL resources allocated to UE 1 in Cell 1 exist in the DL subband in the SBFD slot, and the UL resources allocated to UE 2 in Cell 2 span the UL subband and GAP region in the SBFD slot. The resources allocated to the two UEs may overlap in frequency resources and also in time. In such a case, the cases of the victim UE and the aggressor UE in FIG. 7 may occur.

[0142] To address these issues, cells can exchange their semi-static SBFD configuration information, or one cell can forward its semi-static SBFD configuration information to another cell. Based on this semi-static SBFD configuration information, a cell that receives the semi-static SBFD configuration information can recognize that a CLI issue may occur in a specific frequency range (e.g., the upper and GAP regions of the UL subband of Cell 2 and the lower region of the DL subband of Cell 1) at least at a specific time (e.g., slot), and perform CLI handling accordingly. In addition, although the slot-level CLI due to the SBFD configuration can be predicted, the channel itself between terminals that may actually cause interference is not yet known, and since the CLI or the channel that may cause interference may change over time, a process of measuring the signal strength through the channel between specific terminals may be necessary to determine the accurate CLI.

[0143] FIG. 8 is a diagram illustrating the occurrence of intra-cell inter-UE CLI within a cell operating SBFD according to an embodiment of the present disclosure. When legacy terminals and SBFD terminals coexist, legacy terminals will be scheduled according to TDD UL / DL configurations, and SBFD terminals will be scheduled according to SBFD configurations. FIG. 8 illustrates a case where terminals 1, 2, and 3 coexist, terminals 1 and 3 are SBFD terminals, and terminal 2 is a general terminal. In FIG. 8, UE 2 may be scheduled in a DL slot, terminal 1 may be scheduled in a DL subband within an SBFD slot, and terminal 3 may be scheduled in a UL subband within an SBFD slot. If the UL resources of UE 3 and the DL resources of UE 2 partially overlap, and the slots in which each terminal is scheduled are slots at the same time, the UL transmission of UE 3 may interfere with the DL reception of UE 2 within the same cell.

[0144] From the perspective of a legacy terminal, not using all of the frequencies of a given DL slot in the TDD UL / DL configuration of the legacy terminal that overlap with the UL subband of SBFD (e.g., the dotted area in Fig. 8) for the DL / UL subband configured for SBFD terminals in the same cell or to prevent CLI occurrence can drastically reduce spectral efficiency.

[0145] To prevent this from happening, it's necessary to assess the amount of CLI that can occur between terminals within the same cell. This allows for flexible resource allocation between SBFD-configured resources and legacy terminals via TDD configurations, in cases where CLI between specific terminals is minimal or nonexistent.

[0146] Below, the inter-cell CLI handling procedures and intra-cell CLI handling procedures for terminal-to-terminal CLI occurrence are described.

[0147] In the inter-cell CLI handling procedure, the gNB or DU operating each cell can exchange semi-static SBFD configurations with each other. Based on the semi-static SBFD configuration information, the gNB or DU can adjust the scheduling of the UEs operating in its own cell to avoid generating CLIs in neighboring cells. The gNB and / or DU can perform coordinated scheduling based on the semi-static SBFD configuration information.

[0148] The inter-cell CLI handling procedure may include an operation in which the gNB or DU operating each cell shares the inter-cell SBFD configuration, and additionally, an operation in which a terminal in another cell measures a reference signal transmitted by a specific terminal, thereby measuring the CLI provided by the terminal between cells. Based on the CLI measurement results, the gNB or DU operating each cell can identify the inter-terminal relationship and then perform CLI operations such as coordinated scheduling, Tx beam nulling, and UL muting.

[0149] As shown in Figure 8, the intra-cell CLI handling procedure can occur simultaneously in the same cell, where DL transmission and UL reception can overlap, potentially resulting in CLI. To avoid such cases and perform scheduling within cells, a process is required to obtain measurement results through CLI measurements between terminals within the same cell.

[0150] FIG. 9 illustrates a method in which a terminal of one cell transmits a sounding reference signal (CLI-SRS) and a terminal of another cell measures the CLI-SRS in different cells operating different SBFD settings according to one embodiment of the present disclosure.

[0151] In this case, the victim cell (cell 1) can obtain SRS configuration information to be transmitted by a specific terminal (UE 2) from the aggressor cell (cell 2) and instruct its own terminal (UE 1) to perform measurement. This allows base station 1 to identify interference affecting UE 1, a terminal in another cell, due to UL transmission of UE 2.

[0152] In an inter cell CLI handling procedure according to one embodiment, semi-static SBFD configuration information may be exchanged between gNBs or DUs. Time information and frequency information of the semi-static SBFD configuration may be exchanged or provided through the CU via an Xn message if between gNBs, or via an F1 message if between DUs. For the time information, whether a slot is an SBFD slot or not may be included for each consecutive slot during a specific period. For an SBFD slot, information on the SBFD UL / DL subband frequency domain may be linked. Even if it is not an SBFD slot, since some symbols in the slot may be SBFD symbols, the position information of the symbol and the SBFD UL / DL subband frequency domain information of the symbol may be linked.

[0153] The SBFD information can be exchanged between the gNBs or DUs operating each cell. The information exchanged between the gNBs or DUs can additionally include an indicator requesting CLI handling along with the SBFD information. The gNB / DU that received the request indicator can transmit a response message to the requesting gNB / DU through Xn or F1. The response message can include an indicator with a positive meaning (e.g., the receiving cell will handle CLI) or a negative meaning (e.g., the transmitting cell will not be involved in CLI).

[0154] In one embodiment, L1 / L2-based CLI measurements may additionally be performed in the inter-cell CLI handling procedure. The L1 / L2-based CLI measurements may be referred to as L1 / L2 CLI measurements for inter-cell inter-UE CLI.

[0155] Semi-static SBFD configuration is not specific about resource usage at the scheduler level, and the gNB or DU operating each cell cannot accurately perceive the resulting interference level. Therefore, it is necessary to know how strong the CLI is between actual UEs and at what frequency it appears. To this end, an interference measurement method that considers the slot time scale or a shorter time (symbol level) is required. Existing CLI measurement is implemented as an L3-based RRM operation given to the UE. However, in the case of L3, measurement is based on the time average value over a certain period of time, so detailed interference measurement / reporting according to the scheduler time scale (e.g., slot time scale or a shorter time (symbol level)) is not possible.

[0156] Accordingly, L1 / L2-based CLI measurements can be performed. The measurements can occur simultaneously with the transfer or exchange of semi-static SBFD settings in the inter-cell CLI handling procedure. Below, an inter-cell CLI handling procedure in which the transfer or exchange of semi-static SBFD settings and L1 / L2-based CLI measurements are performed simultaneously is described.

[0157] In Step 1, the victim gNB / DU can transmit semi-static SBFD configuration information to the aggressor gNB / DU. The victim gNB / DU can request resource information for CLI measurement from the aggressor gNB / DU, either by including it in the SBFD information transfer message or through a separate Xn message (for inter-gNB information transfer) or F1 message (for inter-DU information transfer). For this purpose, the victim gNB / DU can request SRS resources from the aggressor gNB / DU.

[0158] In Step 2, the aggressor gNB / DU that received the resource information request can forward information about SRS resources that it can allocate to a specific UE to the victim gNB / DU by including it in an Xn or F1 message. The information about this SRS resource may include at least some of the following information:

[0159] - Per SRS-Resource:

[0160] * SRS-resource ID: ID per SRS resource

[0161] * nrofSRS-Ports: Number of ports used when transmitting SRS

[0162] * ptrs-PortIndex, phase tracking RS index

[0163] * transmissionComb,

[0164] * resource mapping(start position, nrofsymbols, repotitionFactor),

[0165] * freqDomainPosition,

[0166] * freqDomainShift,

[0167] * freqHopping info(c-srs, b-srs, b-hop),

[0168] * grouporsequenceHopping,

[0169] * resource type (as below),

[0170] * sequenceId,

[0171] * spatialRelationInfo

[0172] - SCS of this SRS

[0173] In Step 3, the victim gNB / DU that has received the SRS resource information can decide in which of its cells and for which terminal(s) the SRS information will be measured. After the terminal(s) are decided, the victim gNB / DU can request SRS measurement for CLI purposes from the terminal(s). At this time, the victim gNB / DU can change or adjust the information about the SRS resources received from the aggressor gNB / DU to the resources of its own cell where the CLI measurement will be performed. In this process, the victim gNB / DU can configure SRS resources for the terminal based on the resources of the cell (e.g., the victim cell) of the victim gNB / DU where the CLI measurement will be performed. At this time, the SRS resources received from the aggressor gNB / DU can only be configured in an area that overlaps with the channel bandwidth of the victim cell when configuring them for the terminal. In addition, each SRS or CLI resource must be delivered in association with a serving cell index indicating the victim cell. Additionally, each SRS or CLI resource must be associated with and directed to one of the DL BWPs of the corresponding cell. The frequency resources of this DL BWP must include either SRS resources or CLI resources.

[0174] In addition to the SRS resource, the serving cell may instruct the terminal to measure a separate resource for CLI purposes. For example, with respect to this CLI resource, the terminal may be instructed to measure an amount equal to the total received signal strength of a specific resource, at the discretion of the victim gNB / DU, regardless of the aggressor gNB / DU.

[0175] The above resource information can be set by the victim cell to a terminal within the cell. The cell can transmit the following information while requesting CLI measurement to a selected terminal among the connected terminals of the cell.

[0176] - Target for CLI measurement (CLI resource configuration):

[0177] For each serving cell, a CLI resource configuration can be provided. This configuration can be conveyed via the RRCReconfiguration message.

[0178] The RS type may be related to at least one of an SRS resource, a CLI-RSSI (received signal strength indicator) resource, or an IMR (interference measurement resource) using CSI-RS.

[0179] The SRS resource refers to the resource to which the SRS signal transmitted by the terminal of the aggressor cell is transmitted, and when measuring for CLI, this becomes the resource that the victim cell filters the SRS transmission resource to as the resource of its own cell. The CLI-RSSI resource refers to the resource for measuring the strength of the received signal measured on a specific resource without a desired signal. The IMR is the resource to which the CSI-RS transmitted by the victim cell is transmitted, and is used to measure the signal strength of signals other than the CSI-RS already known to the resource.

[0180] - As a measuring quantity, this may include SRS-RSRP, CLI-RSSI, and CLI-IMR.

[0181] * SRS-RSRP (reference signal received power): The victim UE can measure the aggressor UE's SRS transmission. The measured quantity is the RSRP of the SRS signal. In additional examples, the reference signal received quality (RSRQ) or RSSI may also be considered.

[0182] This SRS resource can be adapted to either the victim cell's frequency BW (inter-F case) or the same received one (intra-F case). That is, only the SRS included in the resources on the serving cell that indicates the measurement is expressed using a resource index and set to the terminal.

[0183] * CLI-RSSI: The victim UE will measure the aggressor UE's UL transmission plus any interference power on its DL reception resource. That is, CLI-RSSI measures all detected receive power on a specific resource without a desired signal. This resource is determined by the victim gNB, and there may be no explicit exchange of TX resources from the aggressor gNB to the victim gNB.

[0184] * CLI-IMR (interference measurement resource): This is the same concept as IMR in CSI, i.e., NZP CSI-RS for interference meas. In other words, when measuring the CSI-RS signal transmitted by the serving cell, other signals measured in the resource other than the known CSI-RS can be regarded as interference.

[0185] When the RS type and quantity information of each measurement target are given, at least one of the following additional setting information is given.

[0186] -SRS-RSRP: list of SRS-Resource

[0187] * Per SRS-Resource: SRS-resource ID, nrofSRS-Ports, ptrs-PortIndex, transmissionComb, resource mapping(start position, nrofsymbols, repotitionFactor), freqDomainPosition, freqDomainShift, freqHopping info(c-srs, b-srs, b-hop), grouporsequenceHopping, resource type(이후에 설명되는 시간 기반 RS type), sequenceId, spatialRelationInfo

[0188] * SCS of this SRS

[0189] * Ref DL BWP: serving cell(victim cell)'s DL BWP where SRS location can be based on

[0190] * Ref servCellIndex: serving cell index which has above DL BWP

[0191] -CLI-RSSI: list of CLI-RSSI resource

[0192] * Per RSSI-resource: resource ID, SCS, start PRB, nrofPRB, startPosition, nrofSymbols, rssi-PeriodicityAndOffset, refServCellIndex, resource type(periodic, semi-persistent, aperiodic RS임을 지시하는 지시자)

[0193] -CLI-IMR: list of CLI-IMR resource

[0194] -Per CLI-IMR resource: resource ID, and / or resource set ID, resource pattern (subcarrier location, symbol location), CSI frequency occupation, periodicityAndOffset, resource type (periodic or semipersistent)

[0195] When configuring the above-described RSs to a UE, all three types of RS types may be possible for intra-cell inter-UE CLI, but only periodic and / or semi-persistent RS types may be possible for inter-cell CLI. This is because it is practically difficult to signal dynamic SRS configurations between DUs / inter-gNBs.

[0196] Report configuration: For each measurement target, a single report configuration can be linked and transmitted to the terminal. A single report configuration can contain the following information:

[0197] - Serving cell index: A cell in which a CLI resource configuration (measurement target) exists can be indicated by a serving cell index, which means a cell in which a CLI resource to which the report configuration applies exists. If this field is not present, the signal may indicate an spcell.

[0198] - CLI-measurement resource ID: resource set or resource of CLI measurement target

[0199] If a serving cell index and a CLI measurement resource ID are given, the terminal first looks at the serving cell index of the cell group to which the signal is given, finds the CLI resources existing (i.e., configured) in the corresponding serving cell, and then finds the CLI resources indicated by the CLI measurement resource ID among them.

[0200] - reportType: periodic, SP, AP (according to the resource type given)

[0201] * Periodic

[0202] ** Report slot config: This is the configuration information for the reporting point. The location of a symbol within a specific slot can be specified. At this time, the Report slot config can specify the corresponding symbol location based on, for example, the number of slots within the frame, the current frame index, the slot index within the current frame, and the CLI RS periodicity and offset values. For this purpose, the CLI RS periodicity and offset values ​​can be included as the contents of the report slot config.

[0203]

[0204] In the above formula, is the number of slots from frame 0, slot 0 to the current slot (this number never roll over until frame number roll over).

[0205] refers to the number of slots in one frame. You can refer to the table below.

[0206] μ 01410111420221440431480841416016

[0207] means frame number (frame index).

[0208] means the slot index (slot number) within one frame.

[0209] In the above formula, and may mean RRC (CSIResourcePeriodicityAndOffset).

[0210] *** During the report interval, one result value can be reported for each resource ID. If the same resource is repeated during each report interval, one representative value can be determined and reported. The determined representative value can include at least one of the following options:

[0211] **** opt1. max value: The maximum value among the values ​​measured for multiple resources per interval can be the representative value.

[0212] **** opt 2. averaged value: The average value of the values ​​measured for multiple resources per interval can be the representative value.

[0213] **** opt 3, min value: This can be the minimum value among the values ​​measured for multiple resources per interval.

[0214] **** opt 4, the latest value can be reported: The latest value measured for multiple resources per interval can be the representative value.

[0215] *** During the interval, multiple reporting values ​​per indicated resource (set) can also be reported with its ID. Multiple reporting values ​​can include at least one of the following options:

[0216] **** Opt 1. max N best value: For multiple time resources per interval, N of the maximum values ​​can be representative values.

[0217] **** Opt 2. All measured values ​​per resource: For multiple time resources per interval, the measured values ​​of all time resources can be used as the representative value. In this case, the resulting values ​​for each time resource can be reported in the time order of the resource.

[0218] ** PUCCH resource list for CLI report: PUCCH (physical uplink control channel) resource configuration for each report for measurement reporting on the above-described measurement targets. PUCCH resource configuration for each report indicates the Report slot config information mentioned above.

[0219] * SP (semi-persistent) report on PUCCH: PUCCH resource configuration information for measurement reporting on the above-set measurement target.

[0220] Report slot config, and PUCCH CLI resource list same as Periodic case

[0221] * SP report on PUSCH

[0222] Report slot config, same as Periodic case

[0223] * SP on UL MAC CE (new type)

[0224] Report slot config same as Periodic case. In this case, since MAC operates on a cell group, information indicating which serving cell the CLI measurement is performed on can be added compared to reporting on PUSCH (physical uplink shared channel) / PUCCH. The information can include at least one of a serving cell index, and / or a resource (set) ID among the measurement targets in the CLI measurement configuration, and / or an ID indicating the report configuration, or an index (Id) indicating an instance according to the combination of the measurement target and the report configuration.

[0225] * AP report (aperiodic report)

[0226] Report slot offset

[0227] - reportQuantity

[0228] At least one of SRS-RSRP, CLI-RSSI, or IMR.

[0229] - Report content

[0230] The terminal can collect and transmit measurement results corresponding to the target quantity to the network for the set ID or resource ID indicated in the report configuration. If the above ID is configured to report as a single value or multiple values, the terminal can collect and report as a single value or multiple values, as appropriate for each case.

[0231] The above RS types can be temporally repeated in periodic, semi-persistent, or aperiodic forms. The format of the corresponding measurement result report can also be determined based on the RS's temporal type. The following table explains the possible report types according to RS type.

[0232] Resource ConfigurationReport ConfigurationRS ConfigurationPeriodic reportSemi-Persistent reportAperiodic reportPeriodic RSNo dynamictriggering / activationReporting on PUCCH: Triggering by MAC CEReporting on PUSCH:Triggering by DCITriggered by DCI, additionally by MAC CESemi Persistent RSNot SupportedReporting on PUCCH: Triggering by MAC CEReporting on PUSCH:Triggering by DCITriggered by DCI, additionally by MAC CEAperiodic RSNot SupportedNot SupportedTriggered by DCI, additionally by MAC CE

[0233] According to the above table, if RS is periodic, the report type can also be periodic, semi-persistent, or aperiodic report.

[0234] If RS is semi-persistent, report type can be semi-persistent or aperiodic.

[0235] If RS is aperiodic RS, report type can only be aperiodic.

[0236] The above measurement target setting and report configuration can be set to a terminal by linking one measurement target and one report configuration. When setting to a terminal, an ID for indicating an instance of the CLI measurement configuration that combines the measurement target ID or the report configuration ID or a specific measurement target and a specific report configuration can be introduced. After setting, the ID, particularly the ID of a specific report configuration or the ID of the combined instance, can be used in DL / UL signals for dynamic activation / deactivation and measurement result report signals. Such measurement target and report configuration can be transmitted from the network to the terminal via RRCReconfiguration.

[0237] The basic operation is that the terminal starts measuring immediately upon receiving the CLI measurement resource given in the RRCReconfiguration message and proceeds with reporting according to the reporting options.

[0238] After the above setup, the terminal can perform operations for measurement and reporting, and additional signals are proposed for more efficient resource use and energy use of the terminal.

[0239] 1. SP RS activation / deactivation DCI or DL ​​MAC CE:

[0240] 1-A. This is used to start and / or stop measurement and / or reporting of CLI measurement resources given to RRC. Depending on the purpose, it may include at least one of the following pieces of information.

[0241] 1-Ai. May contain directives indicating activation or deactivation.

[0242] 1-A-ii. Serving cell ID: ID of the serving cell performing the CLI measurement.

[0243] 1-A-iii. DL BWD ID: ID of the DL BWD that contains the resource performing the CLI measurement.

[0244] 1-A-iv. ID of the resource (set) that is the target of activation or deactivation.

[0245] 1-Av. TCI state ID: For each resource, a TCI state ID associated with its transmission.

[0246] 1-A-vi. Type of RS and quantity combination: Indicator indicating SRS-RSRP or CLI-RSSI, CSI-IMR

[0247] 1-B. The above DCI / DL MAC CE may use a separate DCI / DL MAC CE depending on the RS type. In this case, the type of the RS and quantity combination may be omitted.

[0248] 2. SP RS reporting on PUCCH activation / deactivation DCI or DL ​​MAC CE:

[0249] 2-A. This is a signal to initiate or terminate a semi-persistent report when measurements are being made on CLI measurement resources given via RRC. Depending on the purpose, it may include at least one of the following pieces of information.

[0250] 2-Ai. May contain directives indicating activation or deactivation.

[0251] 2-A-ii. Serving cell ID: ID of the serving cell performing the CLI measurement and / or reporting.

[0252] 2-A-iii. UL BWP ID: The ID of the UL BWP containing the resources to be used when performing the corresponding CLI measurement report. PUCCH resources must be configured for this BWP.

[0253] 2-A-iv. CLI meas / report instance ID (or report configuration ID): One of the IDs of the CLI measurement and reporting instance configured in RRC. This means that the measurement and reporting corresponding to this ID is to be performed via the PUCCH through the UL BWP of the serving cell.

[0254] 3. AP report trigger state subselection DL MAC CE:

[0255] 3-A. This is to select the subset of CLI measure / report configurations

[0256] 3-B. After selecting these, additionally DCI can further choose the final one configuration.

[0257] 3-C. Necessary information:

[0258] 3-Ci. Serving Cell ID: ID of the serving cell that contains the CLI measurement target resource to which the AP report is applied.

[0259] 3-C-ii. DL BWP ID: DL BWP for which the MAC CE applies as the code point of the DCI BWP indicator field. In other words, it refers to a specific DL BWP among the serving cells that have CLI measurement target resources to which the AP report is applied.

[0260] 3-C-iii. L1 measurement / report ID list to be selected as a subset member. This ID would be in Aperiodic Trigger stateList(as in legacy CSI report case) or in new CLI measure / report configuration list.

[0261] 4. DCI for AP report

[0262] 4-A. Indicates the CLI measurement / report instance ID to be down-selected based on the above AP report trigger state subselection signal.

[0263] 4-B. In this case, the report can be transmitted via PUSCH.

[0264] 4-C. This is to finally select the CLI meas / report configuration for AP report within the subset of IDs in MAC CE AP report trigger subselection

[0265] 4-D. Necessary information

[0266] 4-Di. CLI meas / report configuration(instance) ID to be down selected

[0267] 5. DCI for SP report on PUSCH

[0268] 5-A. to indicate the PUSCH reporting on the concerned CLI meas / report

[0269] 5-B. Necessary information

[0270] 5-Bi. CLI meas / report configuration(instance) ID: CLI measurement / report configuration instance for SP report

[0271] 5-B-ii. UL BWP ID: UL BWP with PUSCH resources set for SP reporting.

[0272] 6. CLI measurement report

[0273] 6-A. Periodic reports can be transmitted via PUCCH.

[0274] 6-B. The SP report can be transmitted via PUCCH or PUSCH through the signal of the SP report on PUCCH or PUSCH.

[0275] 6-C. AP report can be transmitted via PUSCH through AP report DCI.

[0276] 6-D. For transmission methods other than those described above, UL MAC CE may be introduced. In this case, an indication to transmit via UL MAC CE may be added to the signal indicating the proposed AP or SP report.

[0277] 6-E. Each report instance may contain the following information:

[0278] 6-Ei. CLI measurement / report instance ID or CLI report configuration ID: Indicates the CLI measurement instance or CLI report configuration ID for which a measurement request is received and reported.

[0279] 6-E-ii. Measurement results (i.e., values ​​of the quantity indicated in the report configuration) can be stored as representative values ​​(single or multiple) for each ID of the resource or resource set being measured in the report interval.

[0280] 6-E-iii. If reported via UL MAC CE, it may include the index of the serving cell in which the corresponding measurement resources (CLI resources) are configured.

[0281] In Step 4, the terminal performs CLI measurements using the above settings and reports the results to the network. The network, i.e., the victim gNB / DU, can then refer to the CLIs that the terminals may experience and perform CLI handling operations as needed.

[0282] In an embodiment of the intra-cell CLI measurement procedure, CLI can occur between terminals within the same cell. Therefore, a corresponding terminal-to-terminal CLI measurement procedure is proposed. In this case, the signal from the network instructing the terminal to perform CLI measurement and reporting is applied as is. Instead, there is no need to exchange semi-static SBFD configuration information or SRS configuration information between gNBs or DUs.

[0283] FIG. 10 is a flowchart of a procedure for resolving inter-cell inter-gNB inter UE CLI according to an embodiment of the present disclosure. Referring to FIG. 10, semi-static SBFD configuration information (intended) and TDD UL / DL configuration information can be provided or exchanged between gNBs (e.g., gNB1 and gNB2 to each other) by including them in Xn messages. Generally, gNBs can be divided into victim gNBs and aggressor gNBs, but regardless, one gNB can transmit the information to another gNB. Additionally, the messages transmitted between gNBs can include an indicator requesting CLI handling.

[0284] The gNB receiving the message can determine, based on the above information, which of its cells will have CLI. In addition, if the gNB receiving the message wishes to perform CLI handling, it can include an indication that it will perform CLI handling in the corresponding Xn response message and transmit it to the gNB that requested CLI handling.

[0285] A gNB (e.g., gNB2 in FIG. 10) that has received the TDD and SBFD configuration information may determine an aggressor UE of a potential inter UE CLI based on the received information, and may decide to request SRS transmission to the corresponding UE. When the configuration information for the SRS transmission is transmitted to the corresponding UE (e.g., UE 2 in FIG. 10), the UE may perform SRS transmission. In addition, the gNB (e.g., gNB2 in FIG. 10) that has been requested to handle CLI may transmit the SRS configuration information and its own cell's TDD UL / DL configuration information and semi-static SBFD configuration information to the gNB (e.g., gNB1 in FIG. 10) that has requested CLI handling via an Xn message.

[0286] The gNB that received the Xn message and requested CLI handling can determine the terminal to perform CLI measurement based on the received information and perform a CLI measurement request based on the SRS settings received from the terminal.

[0287] FIG. 11 is a flowchart of a procedure for requesting CLI measurements between inter-cell inter-DUs according to one embodiment of the present disclosure.

[0288] First, if CU 1 or DU 1 decides to resolve CLI at its own discretion, DU 1 can transmit the intended TDD DL / UL information and semi-static SBFD configuration information, including the identity information of the corresponding cell and the identity of the cell that is the target of the CLI request (e.g., PCI and / or AFRCN and / or CGI and / or the corresponding gNB ID), to CU 1. At this time, the F1 message can be used.

[0289] CU 1, which has received the above information, can transmit the source cell, target cell, TDD DL / UL information, and SBFD information to the CU of the target cell in an Xn message based on the target cell identity.

[0290] CU 2, which has received the above information, can determine DU 2 based on the received target cell information and transmit the information received by CU 2 to the determined DU 2. At this time, the F1 message is used. DU 2 can receive the F1 message from CU 2 and decide to perform CLI handling. When DU 2 decides to perform CLI handling, DU 2 can decide the terminal to which SRS will be transmitted. DU 2 can also decide the SRS resources accordingly. DU 2 can generate SRS resource configuration information.

[0291] When DU 2 transmits the configuration information of the determined SRS resource and the information of the corresponding terminal (UE F1AP ID) to CU 2, CU 2 stores the SRS resource configuration information in an RRCReconfiguration message for the corresponding terminal and transmits it to DU 2, and DU 2 can transmit this to terminal 2.

[0292] Terminal 2, which has received SRS resource configuration information, can perform SRS transmission based on the SRS resource configuration information.

[0293] At the same time, CU 2 can transmit to CU 1, which requested CLI handling, via an Xn message, including SRS configuration information, TDD UL / DL configuration information of its own target cell, and semi-static SBFD configuration information.

[0294] Thereafter, CU 1 and DU 1 can use the received SRS configuration information as CLI measurement information of terminal 1 to request measurement and reporting from the terminal. The SRS configuration information received by CU 1 and DU 1 can be used for the following operations.

[0295] FIG. 12 is a flowchart of a CLI measurement and reporting procedure according to one embodiment of the present disclosure. The CLI measurement and reporting procedure of FIG. 12 may be performed between a terminal and a gNB or between a terminal and a DU. FIG. 12 is a diagram illustrating a case where a semi-persistent report is configured and the RSRP of an SRS signal is configured to be measured.

[0296] Once the gNB / DU determines the UE, it can forward the CLI measurement / reporting settings to the UE. This information can be included in the RRCReconfiguration message. This message can include information corresponding to the previously mentioned measurement target and report configuration.

[0297] A terminal that receives an RRCReconfiguration message can transmit an RRCReconfigurationComplete message to the gNB / DU.

[0298] When the network (e.g., gNB / DU) transmits an SP resource activation signal to the UE (e.g., via DCI or DL ​​MAC CE), the UE can measure the corresponding SRS resource from then on. When the UE performs SRS resource measurement and receives an SP reporting on PUCCH instruction (e.g., via DCI or DL ​​MAC CE), the UE reports the measured CLI result to the base station at the configured report time instant from then on. According to the report setting, the measurement report is transmitted to the base station via PUCCH, and the result value can be updated and transmitted according to the report time instant according to the given interval.

[0299] The network, i.e., the gNB / DU, can receive the result value and determine the level of CLI delivered to the terminal according to the corresponding SRS resource. If this level is weak, the gNB / DU may not perform separate CLI handling. However, if the level is significant, the gNB / DU may perform separate CLI handling. For example, the gNB / DU may change the scheduling. Referring to Figure 12, the gNB / DU may avoid scheduling DL resources within the indicated SRS resources for CLI.

[0300] FIG. 13 is a flowchart of a procedure for performing a periodic CLI report when a periodic SRS is set according to one embodiment of the present disclosure.

[0301] The base station can transmit the SRS resource measurement and reporting settings for CLI to the terminal by including them in the RRCReconfiguration message.

[0302] In this configuration, if the type of SRS resource is periodic and the reporting configuration is set to perform periodic reporting, or if there is no separate reporting configuration type, the terminal can periodically report the measurement result of the SRS resource. The measurement operation is possible after receiving the RRCReconfiguration message. For example, the terminal that has received the RRCReconfiguration message can transmit an RRCReconfigurationComplete message and measure the designated CLI SRS resource. The reporting configuration includes a PUCCH resource configuration used for report transmission. Since the index of the cell containing the PUCCH resource is also included, the result is reported through the corresponding cell.

[0303] The terminal uses the above settings to report the measurement results through the PUCCH resources set at each report time instant.

[0304] Based on these results, the base station can recognize the level of the measured CLI and perform the necessary CLI handling operations. Specifically, the base station can check the level of SRS power, and if the level of SRS power is sufficiently high, it can avoid scheduling DL resources within the SRS resources indicated for the CLI.

[0305] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0307] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0308] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present invention.

[0309] In the specific embodiments of the present invention described above, components included in the invention are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in plural may be composed of singular elements, or even components expressed in singular may be composed of plural elements.

[0310] While the detailed description of the present invention has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention 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

1. In a method performed by a terminal (user equipment, UE), A step of receiving, from a base station, information for setting up a resource set for CLI (cross link interference) measurement and information for setting up a report for the CLI measurement through RRC (radio resource control) signaling; A step of receiving, from the base station, a MAC (medium access control) CE (control element) for activating at least one resource for the CLI measurement; performing the CLI measurement on at least one resource; and A method comprising the step of transmitting a report of the CLI measurement to the base station.

2. In claim 1, Information for setting up a resource set for the above CLI measurement includes information about a resource type indicating one of periodic, semi-persistent, or aperiodic, and A method for setting up a report for the above CLI measurement, wherein the information includes information on a measurement quantity indicating SRS (sounding reference signal)-RSRP (reference signal received power) or CLI-RSSI (received signal strength indicator).

3. A method according to claim 1, wherein the MAC CE includes at least one of an indicator for activating or deactivating at least one of measurement or reporting, a serving cell ID (identifier), a bandwidth part (BWP) ID, an ID of a resource set for the CLI measurement, or a transmission configuration indicator (TCI) ID.

4. In claim 1, The above CLI measurement is based on the UL (uplink) resource setting related to interference from the terminal's cell and other cells, and The above UL resource setting is a method of transmitting to the CU (central unit) of the base station via the Xn interface or the F1 interface.

5. In a method performed by a base station, A step of transmitting, to a user equipment (UE), information for setting up a resource set for CLI (cross link interference) measurement and information for setting up a report for the CLI measurement through RRC (radio resource control) signaling; A step of transmitting, to the terminal, a MAC (medium access control) CE (control element) for activating at least one resource for the CLI measurement; and A method comprising the step of receiving, from the terminal, a report of the CLI measurement performed on the at least one resource.

6. In claim 5, Information for setting up a resource set for the above CLI measurement includes information about a resource type indicating one of periodic, semi-persistent, or aperiodic, and A method for setting up a report for the above CLI measurement, wherein the information includes information on a measurement quantity indicating SRS (sounding reference signal)-RSRP (reference signal received power) or CLI-RSSI (received signal strength indicator).

7. A method according to claim 5, wherein the MAC CE includes at least one of an indicator for activating or deactivating at least one of measurement or reporting, a serving cell ID (identifier), a bandwidth part (BWP) ID, an ID of a resource set for the CLI measurement, or a transmission configuration indicator (TCI) ID.

8. In claim 5, The above CLI measurement is based on the UL (uplink) resource setting related to interference from the terminal's cell and other cells, and The above UL resource setting is a method of receiving the CU (central unit) of the base station via the Xn interface or the F1 interface.

9. In the terminal (user equipment, UE), At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, so that the terminal: Receive information for setting up a resource set for CLI (cross link interference) measurement and information for setting up a report for the CLI measurement from a base station through RRC (radio resource control) signaling, Receive from the base station a MAC (medium access control) CE (control element) for activating at least one resource for the CLI measurement, Performing the CLI measurement on at least one resource, and A terminal that transmits a report of the CLI measurement to the base station.

10. In claim 9, Information for setting up a resource set for the above CLI measurement includes information about a resource type indicating one of periodic, semi-persistent, or aperiodic, and Information for setting up a report for the above CLI measurement is a terminal including information on a measurement quantity indicating SRS (sounding reference signal)-RSRP (reference signal received power) or CLI-RSSI (received signal strength indicator).

11. A terminal according to claim 9, wherein the MAC CE includes at least one of an indicator for activating or deactivating at least one of measurement or reporting, a serving cell ID (identifier), a bandwidth part (BWP) ID, an ID of a resource set for the CLI measurement, or a transmission configuration indicator (TCI) ID.

12. In claim 9, The above CLI measurement is based on the UL (uplink) resource setting related to interference from the terminal's cell and other cells, and The above UL resource setting is transmitted to the CU (central unit) of the base station through the Xn interface or the F1 interface.

13. At the base station, At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor so that the base station: Transmitting information for setting up a resource set for CLI (cross link interference) measurement and information for setting up a report for the CLI measurement to a terminal (user equipment, UE) through RRC (radio resource control) signaling, Transmitting to the terminal a MAC (medium access control) CE (control element) to activate at least one resource for the CLI measurement, and A base station configured to receive, from the terminal, a report of the CLI measurement performed on the at least one resource.

14. In claim 13, Information for setting up a resource set for the above CLI measurement includes information about a resource type indicating one of periodic, semi-persistent, or aperiodic, and Information for setting up a report for the above CLI measurement is a base station including information on a measurement quantity indicating SRS (sounding reference signal)-RSRP (reference signal received power) or CLI-RSSI (received signal strength indicator).

15. A base station according to claim 13, wherein the MAC CE includes at least one of an indicator for activating or deactivating at least one of measurement or reporting, a serving cell ID (identifier), a bandwidth part (BWP) ID, an ID of a resource set for the CLI measurement, or a transmission configuration indicator (TCI) ID.

Images