Method for performing communication in wireless communication system and device therefor

Abstract

Disclosed, according to various embodiments, are a method for performing communication in a wireless communication system and a device therefor. Disclosed is a method and a device therefor, the method comprising: obtaining a measurement related to a measurement resource; determining a priority related to a measurement report including the measurement, on the basis of a priority index related to a channel state information (CSI) report; and performing a transmission procedure of the measurement report on the basis of the priority.

Description

Method for performing communication in a wireless communication system and device therefor

[0001] This relates to a method for a terminal to perform communication in a wireless communication system and a device therefor.

[0002] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communication. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. The introduction of next-generation radio access technologies that take into account enhanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed. For convenience, these technologies are referred to as new RAT or NR in the present invention.

[0004] The technical challenge is to provide a method for performing operations that report measurement information more accurately and efficiently.

[0005] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0006] A method by a UE (User Equipment) according to one aspect includes: obtaining a measurement related to a measurement resource; determining a priority related to a measurement report including the measurement based on a priority index related to a channel state information (CSI) report; and performing a transmission procedure of the measurement report based on the priority; wherein the priority index can be determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured in the measurement resource and a report type of the RSRP.

[0007] Alternatively, the reporting type is characterized by including a first type reporting the RSRP for CSI and a second type reporting the RSRP for CLI (Cross Link Interference).

[0008] Alternatively, based on the measurement report including the RSRP for the CSI, the priority index is determined to be a first value, and based on the measurement report including the RSRP for CLI (Cross Link Interference), the priority index is determined to be a second value greater than the first value.

[0009] Alternatively, based on the measurement report not including RSRP, the priority index is determined as the second value.

[0010] Alternatively, based on the measurement report not including RSRP, the priority index is determined to be a third value greater than the second value.

[0011] Alternatively, based on the measurement report not including RSRP, the priority index is determined as a third value that is less than the second value and greater than the first value.

[0012] Alternatively, based on the overlapping of the measurement report and another measurement report in the time domain, the UE is characterized in that it determines whether to drop the measurement report based on the priority and the priority for the other measurement report.

[0013] Alternatively, the measurement report is characterized in that it includes information on a difference value between a plurality of measurement values ​​for a plurality of CLI measurement resources and a specific measurement value among the plurality of measurement values.

[0014] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the method by the UE described above may be provided.

[0015] According to another aspect, a UE performing the above-described method may be provided.

[0016] According to another aspect, a processing device may be provided for controlling a UE performing the above-described method.

[0017] A method by a base station according to another aspect includes the steps of transmitting measurement resource configuration information for a measurement resource to a UE (User Equipment); and receiving a measurement report including a measurement obtained from the measurement resource; wherein the measurement report is applied with a priority determined based on a priority index related to a CSI (channel state information) report, and the priority index can be determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and a report type of the RSRP.

[0018] According to another aspect, a base station may be provided that performs the method for performing the above-described communication.

[0019] Various embodiments enable a terminal to accurately and efficiently report measurement information to a base station.

[0020] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0021] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0022] Figure 1 shows the structure of an LTE system.

[0023] Figure 2 shows the structure of the NR system.

[0024] Figure 3 shows the structure of a radio frame of NR.

[0025] Figure 4 shows the slot structure of an NR frame.

[0026] FIG. 5 is a diagram for explaining physical channels that can be used in various embodiments and a signal transmission method using the same.

[0027] Figure 6 illustrates a process in which a terminal transmits ACK / NACK via PUSCH.

[0028] Figure 7 shows an example of a CSI-related procedure.

[0029] Figure 8 is a diagram for explaining a method of performing full duplex operation in an NR system.

[0030] FIG. 9 and FIG. 10 are diagrams for explaining SBFD (sub-band full duplex) and SFFD (single frequency full duplex) operations.

[0031] Figures 11 and 12 are diagrams illustrating the CLI environment and scenarios that can be considered in relation to SBFD operation.

[0032] Figure 13 is a diagram illustrating how a UE determines a priority for a CLI report.

[0033] Figure 14 is a diagram for explaining how a base station receives a CLI report from a UE.

[0034] Figure 15 illustrates a communication system applied to the present invention.

[0035] Figure 16 illustrates a wireless device applicable to the present invention.

[0036] Figure 17 shows another example of a wireless device applied to the present invention.

[0037] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0038] Sidelink refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). Sidelink is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0039] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0040] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0041] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0042] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0043] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0044] Figure 1 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0045] Referring to FIG. 1, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0046] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0047] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0048] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0049] Figure 2 shows the structure of the NR system.

[0050] Referring to FIG. 2, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, they are connected to the access and mobility management function (AMF) via the NG-C interface, and to the user plane function (UPF) via the NG-U interface.

[0051] Figure 3 shows the structure of a radio frame of NR.

[0052] Referring to FIG. 3, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0053] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0054] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0055] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0056] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0057] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0058] In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, etc.) can be configured differently across multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as a TU (Time Unit)) consisting of the same number of symbols can be configured differently across the merged cells. In NR, multiple numerologies or SCSs can be supported to support various 5G services. For example, when the SCS is 15 kHz, a wide area in traditional cellular bands can be supported, and when the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. When the SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz may be supported to overcome phase noise.

[0059] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0060] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0061] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0062] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0063] Figure 4 shows the slot structure of an NR frame.

[0064] Referring to Figure 4, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0065] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0066] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0067] Bandwidth part (BWP)

[0068] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the RF on for the entire CC, the terminal battery consumption may increase. Alternatively, when considering multiple use cases (e.g., eMBB, URLLC, MMTC, V2X, etc.) operating within a wideband CC, different numerologies (e.g., sub-carrier spacing) may be supported for each frequency band within the CC. Alternatively, each terminal may have different capabilities for maximum bandwidth. Considering this, the base station can instruct the terminal to operate only in a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and this portion of bandwidth is conveniently defined as a bandwidth part (BWP). A BWP can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to a single numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration).

[0069] Meanwhile, the base station can set multiple BWPs even within a single CC configured for the UE. For example, in the PDCCH monitoring slot, a BWP occupying a relatively small frequency range can be set, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, some UEs can be set to a different BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the spectrum in the middle of the total bandwidth can be excluded, and both BWPs can be set within the same slot. That is, the base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC, and can activate at least one DL / UL BWP among the configured DL / UL BWP(s) at a specific point in time (by L1 signaling or MAC CE or RRC signaling, etc.), and switching to another configured DL / UL BWP can be indicated (by L1 signaling or MAC CE or RRC signaling, etc.), or switching to a predetermined DL / UL BWP when the timer value expires based on a timer. At this time, the activated DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration for the DL / UL BWP in situations such as when the terminal is in the initial access process or before the RRC connection is set up. In such situations, the DL / UL BWP assumed by the terminal is defined as the initial active DL / UL BWP.

[0070] FIG. 5 is a diagram for explaining physical channels that can be used in various embodiments and a signal transmission method using the same.

[0071] Referring to FIG. 5, a terminal that is powered on again after being powered off or that has newly entered a cell performs an initial cell search operation, such as synchronizing with the base station, in step S101. To this end, the terminal receives a Synchronization Signal Block (SSB) from the base station. The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). Based on the PSS / SSS, the terminal synchronizes with the base station and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

[0072] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on physical downlink control channel information (S12).

[0073] Thereafter, the terminal may perform a random access procedure to complete connection to the base station (S13 to S16). To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S14). The terminal may transmit a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal (S16).

[0074] Meanwhile, in addition to the random access process performed in 4 steps as above (4-step RACH, type-1 random access procedure), when the random access process is performed in 2 steps (2-step RACH, type-2 random access procedure), S13 / S15 may be performed as one operation in which the terminal performs transmission (e.g., transmission operation of message A including PRACH preamble and / or PUSCH), and S14 / S16 may be performed as one operation in which the base station performs transmission (e.g., transmission operation of message B including RAR and / or collision resolution information).

[0075] A terminal that has performed the procedure described above can then perform reception of a physical downlink control channel signal and / or a physical downlink shared channel signal (S17) and transmission of a physical uplink shared channel (PUSCH: Physical Uplink Shared Channel) signal and / or a physical uplink control channel (PUCCH: Physical Uplink Control Channel) signal (S18) as a general uplink / downlink signal transmission procedure.

[0076] Control information transmitted from a terminal to a base station is collectively referred to as uplink control information (UCI). UCI includes information such as HARQ-ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CQI (Channel Quality Indication), PMI (Precoding Matrix Indication), and RI (Rank Indication).

[0077] UCI is typically transmitted periodically over the PUCCH, but can also be transmitted over the PUSCH when control information and data must be transmitted simultaneously. Furthermore, terminals can transmit UCI aperiodically over the PUSCH at the request / instruction of the network.

[0078] Figure 6 illustrates a process in which a terminal transmits ACK / NACK via PUSCH.

[0079] Referring to FIG. 6, the terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0, 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 can include the following information:

[0080] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0081] - Time domain resource assignment: K0 (e.g., slot offset), indicates the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., number of OFDM symbols).

[0082] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

[0083] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB)

[0084] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.

[0085] Afterwards, the terminal receives PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when reception of PDSCH is finished in slot #n1 (where, n+K0≤n1), UCI can be transmitted through PUCCH in slot #(n1+K1). Here, UCI may include HARQ-ACK response for PDSCH. In Fig. 6, for convenience, it is assumed that SCS for PDSCH and SCS for PUCCH are the same and slot# n1 = slot# n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0086] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and may consist of 1 bit if spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0087] Whether a UE should perform spatial bundling for a HARQ-ACK response can be configured (e.g., via RRC / higher layer signaling) for each cell group. For example, spatial bundling can be individually configured for each HARQ-ACK response transmitted over the PUCCH and / or each HARQ-ACK response transmitted over the PUSCH.

[0088] Spatial bundling can be supported when the maximum number of TBs (or codewords) that can be received at a time (or scheduled via 1 DCI) in the serving cell is 2 (or more than 2) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than 4 layers can be used for 2-TB transmission, and up to 4 layers can be used for 1-TB transmission. Consequently, when spatial bundling is configured for the cell group, spatial bundling can be performed for serving cells that can schedule more than 4 layers among the serving cells in the cell group. On the serving cell, a UE that wishes to transmit a HARQ-ACK response via spatial bundling can generate the HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits for multiple TBs.

[0089] For example, assuming that a terminal receives a DCI scheduling 2 TB and receives 2 TB via PDSCH based on the DCI, the terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. Consequently, if both the first TB and the second TB are ACK, the terminal reports the ACK bit value to the base station, and if either TB is NACK, the terminal reports the NACK bit value to the base station.

[0090] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with bit value 1. Consequently, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0091] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. These multiple parallel HARQ processes allow DL transmissions to be performed continuously while waiting for HARQ feedback regarding the success or failure of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables such as the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0092] Below, the PUSCH transmission process is described.

[0093] The terminal can detect the PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 can include the following information.

[0094] - Frequency domain resource assignment: Indicates the set of RBs allocated to PUSCH.

[0095] - Time domain resource assignment: Slot offset K2 indicates the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length can be indicated through SLIV (Start and Length Indicator Value) or can be indicated separately.

[0096] Thereafter, the terminal can transmit a PUSCH in slot #(n+K2) according to the scheduling information of slot #n. Here, the PUSCH includes a UL-SCH TB.

[0097] CSI-related actions

[0098] Figure 7 shows an example of a CSI-related procedure.

[0099] The terminal receives configuration information related to CSI from the base station via RRC signaling (710). The configuration information related to CSI may include at least one of CSI-IM (interference management) resource-related information, CSI measurement configuration-related information, CSI resource configuration-related information, CSI-RS resource-related information, or CSI report configuration-related information.

[0100] - CSI-IM resources can be configured for interference measurement (IM) of the terminal. In the time domain, the CSI-IM resource set can be configured periodically, semi-persistently, or aperiodicly. The CSI-IM resources can be configured as Zero Power (ZP)-CSI-RS for the terminal. The ZP-CSI-RS can be configured separately from the Non-Zero Power (NZP)-CSI-RS.

[0101] - The UE may assume that the CSI-RS resource(s) for channel measurement configured for one CSI reporting and the CSI-IM / NZP CSI-RS resource(s) for interference measurement (when NZP CSI-RS resource(s) are used for interference measurement) are in a QCL relationship with respect to 'QCL-TypeD' per resource.

[0102] - The CSI resource configuration may include at least one of a CSI-IM resource for interference measurement, an NZP CSI-RS resource for interference measurement, and an NZP CSI-RS resource for channel measurement. The CMR (channel measurement resource) may be an NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) may be an NZP CSI-RS for CSI-IM and IM.

[0103] - CSI-RS can be configured for one or more terminals. Different CSI-RS configurations may be provided for each terminal, or the same CSI-RS configuration may be provided to multiple terminals. CSI-RS can support up to 32 antenna ports. CSI-RS corresponding to N (N is 1 or greater) antenna ports can be mapped to N RE locations within a time-frequency unit corresponding to one slot and one RB. When N is 2 or greater, N-port CSI-RS can be multiplexed using CDM, FDM, and / or TDM schemes. CSI-RS can be mapped to REs other than REs to which CORESET, DMRS, and SSB are mapped. In the frequency domain, CSI-RS can be configured for the entire bandwidth, a portion of the bandwidth (BWP), or a portion of the bandwidth. CSI-RS may be transmitted in each RB within the bandwidth for which CSI-RS is configured (i.e., density = 1), or in every second RB (e.g., even or odd RB) (i.e., density = 1 / 2). When CSI-RS is used as a Tracking Reference Signal (TRS), a single-port CSI-RS may be mapped on three subcarriers in each resource block (i.e., density = 3). One or more CSI-RS resource sets may be configured for a UE in the time domain. Each CSI-RS resource set may include one or more CSI-RS configurations. Each CSI-RS resource set may be configured periodically, semi-persistently, or aperiodicly.

[0104] - The CSI report configuration may include configurations for feedback type, measurement resources, report type, etc. The NZP-CSI-RS resource set may be used for the CSI report configuration of the corresponding terminal. The NZP-CSI-RS resource set may be associated with CSI-RS or SSB. In addition, multiple periodic NZP-CSI-RS resource sets may be configured as TRS resource sets. (i) The feedback type may include a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), an SSB Resource block Indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), a Layer 1-Reference Signal Received Strength (RSRP), etc. (ii) Measurement resources may include configurations for downlink signals and / or downlink resources on which the terminal performs measurements to determine feedback information. The measurement resources may be configured as ZP and / or NZP CSI-RS resource sets associated with CSI reporting configurations. The NZP CSI-RS resource set may include a CSI-RS set or an SSB set. For example, L1-RSRP may be measured for a CSI-RS set or an SSB set. (iii) Reporting types may include configurations for a time point at which the terminal performs reporting and an uplink channel, etc. The reporting time point may be configured as periodic, semi-persistent, or aperiodic. Periodic CSI reporting may be transmitted on PUCCH. Semi-persistent CSI reporting may be transmitted on PUCCH or PUSCH based on a MAC CE indicating activation / deactivation. Aperiodic CSI reporting may be indicated by DCI signaling.For example, the CSI request field of an uplink grant may indicate one of several report trigger sizes. Aperiodic CSI reports may be transmitted on the PUSCH.

[0105] The terminal measures CSI based on configuration information related to CSI. CSI measurement may include a procedure of receiving a CSI-RS (720) and computing the received CSI-RS to acquire CSI (730).

[0106] The UE can transmit a CSI report to the base station (740). For the CSI report, the time and frequency resources that the UE can use are controlled by the base station. The CSI (channel state information) can include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, and / or L-SINR.

[0107] The time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic. i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periodicity and slot offset of periodic CSI reporting can be configured by RRC, and refer to the CSI-ReportConfig IE. ii) SP (semi-periodic) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH. In case of SP CSI on short / long PUCCH, the periodicity and slot offset are configured by RRC, and CSI reporting is activated / deactivated by separate MAC CE / DCI. In case of SP CSI on PUSCH, the periodicity of SP CSI reporting is configured by RRC, but the slot offset is not configured by RRC, and SP CSI reporting is activated / deactivated by DCI (format 0_1). For SP CSI reporting on PUSCH, a separate RNTI (SP-CSI C-RNTI) is used. The initial CSI reporting timing follows the PUSCH time domain allocation value indicated in the DCI, and subsequent CSI reporting timings follow the cycle set by RRC. DCI format 0_1 ​​includes a CSI request field and can activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting has the same or similar activation / deactivation mechanism as the data transmission mechanism on the SPS PUSCH.iii) Aperiodic CSI reporting is performed on PUSCH and is triggered by DCI. In this case, information related to the triggering of aperiodic CSI reporting can be transmitted / indicated / configured via MAC-CE. For AP CSI with AP CSI-RS, the AP CSI-RS timing is configured by RRC, and the timing for AP CSI reporting is dynamically controlled by DCI.

[0108] CSI codebooks defined in the NR standard (e.g., PMI codebooks) can be broadly divided into Type I and Type II codebooks. Type I codebooks are primarily targeted at SU (Single User)-MIMO, which supports both high-order and low-order signals. Type II codebooks can primarily support MI-MIMO, which supports up to two layers. Compared to Type I, Type II codebooks can provide more accurate CSI, but may increase signaling overhead. Meanwhile, Enhanced Type II codebooks were introduced to address the CSI overhead shortcomings of existing Type II codebooks. Enhanced Type II codebooks were introduced by reducing the codebook payload by considering frequency-axis correlation.

[0109] CSI reporting via PUSCH can be configured as Part 1 and Part 2. Part 1 has a fixed payload size and is used to identify the number of information bits in Part 2. Part 1 is transmitted in its entirety before Part 2.

[0110] - For Type I CSI feedback, Part 1 contains the RI (if reported), the CRI (if reported), and the CQI of the first code word. Part 2 contains the PMI, and when RI > 4, Part 2 contains the CQI.

[0111] - For Type II CSI feedback, Part 1 contains the RI (if reported), CQI, and an indication of the number of non-zero WB amplitude coefficients per layer of Type II CSI. Part 2 contains the PMI of Type II CSI.

[0112] - For Enhanced Type II CSI feedback, Part 1 contains the RI (if reported), CQI, and the total number of non-zero WB amplitude coefficients for all layers of Enhanced Type II CSI. Part 2 contains the PMI of Enhanced Type II CSI.

[0113] If CSI reporting on PUSCH includes two parts and the CSI payload to be reported is less than the payload size provided by the PUSCH resources allocated for CSI reporting, the UE may omit part of Part 2 CSI.

[0114] Meanwhile, semi-persistent CSI reporting performed in PUCCH format 3 or 4 supports Type II CSI feedback, but only Part 1 of Type II CSI feedback.

[0115] QCL (quasi-co location)

[0116] Two antenna ports are quasi-co-located if the channel properties of one antenna port can be inferred from the channel properties of the other antenna port. The channel properties may include one or more of Delay spread, Doppler spread, Frequency / Doppler shift, Average received power, Received Timing / average delay, and Spatial RX parameters.

[0117] A terminal can configure a list of multiple TCI-State configurations via the upper layer parameter PDSCH-Config. Each TCI-State is associated with one or two DL reference signals and a QCL configuration parameter between the DM-RS port of the PDSCH. The QCL can include qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS. The QCL type can correspond to one of the following:

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

[0119] - 'QCL-TypeB': {Doppler shift, Doppler spread}

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

[0121] - 'QCL-TypeD': {Spatial Rx parameter}

[0122] L3 CLI Report

[0123] L3 CLI reporting can be defined as follows (3GPP TS 38.331).

[0124] 1> if there is at least one applicable CLI measurement resource to report:

[0125] 2> if thereportTypeis set tocli-EventTriggeredorcli-Periodical:

[0126] 3> set themeasResultCLIto include the most interfering SRS resources or most interfering CLI-RSSI resources up tomaxReportCLIin accordance with the following:

[0127] 4> if thereportTypeis set tocli-EventTriggered:

[0128] 5> if trigger quantity is set tosrs-RSRPi.e.i1-Thresholdis set tosrs-RSRP:

[0129] 6> include the SRS resource included in thecli-TriggeredListas defined within theVarMeasReportListfor thismeasId;

[0130] 5> if trigger quantity is set tocli-RSSIi.e.i1-Thresholdis set tocli-RSSI:

[0131] 6> include the CLI-RSSI resource included in thecli-TriggeredListas defined within theVarMeasReportListfor thismeasId;

[0132] 4> else:

[0133] 5> ifreportQuantityCLIis set tosrs-rsrp:

[0134] 6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0135] 5> else:

[0136] 6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0137] 4> for each SRS resource that is included in themeasResultCLI:

[0138] 5> include thesrs-ResourceId;

[0139] 5> setsrs-RSRP-Resultto include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first;

[0140] 4> for each CLI-RSSI resource that is included in themeasResultCLI:

[0141] 5> include therssi-ResourceId;

[0142] 5> setcli-RSSI-Resultto include the layer 3 filtered measured results in decreasing order, ie the most interfering CLI-RSSI resource is included first;

[0143] Additionally, events that trigger L3 CLI reporting can be defined as follows:

[0144] Periodic configuration / event trigger

[0145] - Event A1: Serving becomes better than absolute threshold;

[0146] - Event A2: Serving becomes worse than absolute threshold;

[0147] - Event A3: Neighbor becomes amount of offset better than PCell / PSCell;

[0148] - Event A4: Neighbor becomes better than absolute threshold;

[0149] - Event A5: PCell / PSCell becomes worse than absolute threshold1 AND Neighbor / SCell becomes better than another absolute threshold2;

[0150] - Event A6: Neighbor becomes amount of offset better than SCell;

[0151] - 이벤트 D1: Distance between UE and a reference locationreferenceLocation1becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a reference locationreferenceLocation2becomes shorter than configured thresholddistanceThreshFromReference2;

[0152] - 조건부 이벤트 (CondEvent) A3: Conditional reconfiguration candidate becomes amount of offset better than PCell / PSCell;

[0153] - 조건부 이벤트 (CondEvent) A4: Conditional reconfiguration candidate becomes better than absolute threshold;

[0154] - 조건부 이벤트 (CondEvent) A5: PCell / PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2;

[0155] - Conditional Event (CondEvent) D1: Distance between UE and a reference locationreferenceLocation1becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a reference locationreferenceLocation2of conditional reconfiguration candidate becomes shorter than configured thresholddistanceThreshFromReference2;

[0156] - Conditional Event (CondEvent) T1: Time measured at UE becomes more than configured thresholdt1-Thresholdbut is less thant1-Threshold + duration;

[0157] - Event X1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND NR Cell becomes better than another absolute threshold2;

[0158] - Event X2: Serving L2 U2N Relay UE becomes worse than absolute threshold;

[0159] - For Event I1, the measurement reporting event is based on the CLI measurement result, which can be derived based on SRS-RSRP or CLI-RSSI.

[0160] - Event I1: Interference becomes higher than absolute threshold

[0161] Beam Management (BM)

[0162] The BM process is a process for acquiring and maintaining a set of BS (or transmission and reception point (TRP)) and / or UE beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following processes and terms.

[0163] - Beam measurement: An operation in which a BS or UE measures the characteristics of a received beamforming signal.

[0164] - Beam determination: An operation in which a BS or UE selects its own transmit beam (Tx beam) / receive beam (Rx beam).

[0165] - Beam sweeping: An operation of covering a spatial domain using transmit and / or receive beams over a predetermined time interval in a predetermined manner.

[0166] - Beam report: An operation in which a UE reports information about a beamformed signal based on beam measurement.

[0167] The BM process can be divided into (1) a DL BM process using SSB or CSI-RS, and (2) a UL BM process using SRS (sounding reference signal). In addition, each BM process can include Tx beam sweeping to determine a Tx beam and Rx beam sweeping to determine an Rx beam.

[0168] At this time, the DL BM process may include (1) transmission of beamformed DL RSs (e.g., CSI-RS or SSB) by the BS and (2) beam reporting by the UE.

[0169] Here, the beam report may include preferred DL RS ID(s) and corresponding reference signal received power (RSRP). The DL RS ID may be an SSB Resource Indicator (SSBRI) or a CSI-RS Resource Indicator (CRI).

[0170] Full duplex operation for NR

[0171] FIGS. 8 to 10 are drawings for explaining a method of performing full duplex operation in an NR system.

[0172] 5G is giving rise to new service types, such as XR (Extended Reality), AI-based services, and self-driving cars. These services feature dynamic traffic changes in both DL and UL directions, and require low latency for packet transmission. To support these diverse new use cases, 5G services could experience explosive increases in traffic load. Meanwhile, existing semi-static or dynamic TDD UL / DL configurations may face limitations in transmission delays and interference between operators. Existing FDD schemes may also face limitations in efficient frequency resource utilization in the DL / UL directions. Therefore, the introduction of full-duplex operation within a single carrier is being discussed to achieve low latency and efficient resource utilization in NR.

[0173] Referring to Fig. 8, a method of applying full-duplex operation in an intra-carrier is illustrated. Specifically, the full-duplex operation may be considered as the subband-wise full duplex (SB-FD) method illustrated in Fig. 8 (a) and the spectrum-sharing full duplex (SS-FD) method illustrated in Fig. 8 (b).

[0174] In the case of SB-FD, transmission and reception of DL and UL can be performed using different frequency resources on the same carrier. That is, DL and UL can have different frequency resources for the same time resource. In the case of SS-FD, transmission and reception of DL and UL are performed using the same frequency resources or overlapping frequency resources on the same carrier. That is, DL and UL can be assigned the same or overlapping frequency resources for the same time resource.

[0175] This full-duplex operation can be combined with existing half-duplex operation. For example, in existing half-duplex-based TDD operation, only some time resources can be used for full-duplex operation. In the time resources where full-duplex operation is performed, SB-FD or SS-FD operation can be performed.

[0176] Specifically, referring to FIG. 9, time resources may exist together as time resources operating in HD (half duplex) and as time resources operating in FD (full duplex) such as SB-FD or SS-FD. As illustrated in FIG. 9 (a), the time resources may include some time resources for SB-FD operation and the remaining time resources for HD operation. Alternatively, as illustrated in FIG. 9 (b), the time resources may include time resources for SS-FD operation and the remaining time resources for HD operation. In this case, the unit of the time resources (for SS-FD operation, SB-FD operation, or HD operation) may be a slot or a symbol unit. Meanwhile, in the time resources operating in SB-FD, some frequency resources may be used as DL resources, and some frequency resources may be used as UL resources.

[0177] In the following, frequency resources operating as DL among the entire frequency resources in a time resource operating as FD (e.g., SB-FD operation or SS-FD operation) are defined as DL sub-bands, and frequency resources operating as UL are defined as UL sub-bands.

[0178] In the case of the full-duplex (hereinafter, FD) operation as described above, the FD operation can be performed from both the gNB perspective and the UE perspective. For example, both the gNB and the UE can simultaneously transmit and receive DL / UL using the same or different frequency resources in the same time resource. Alternatively, only the gNB can perform the FD operation (in the same time resource), and the UE can perform the HD operation. The gNB can simultaneously transmit and receive DL and UL using the same or different frequency resources in the same time resource, but the UE can perform only DL reception or UL transmission in a specific time resource. In this case, the gNB can perform the FD operation in a way that performs DL transmission and UL reception for different UEs at the same time point (or, the same time resource).

[0179] The following description generally assumes that the gNB performs FD operations and the UE performs HD operations. However, the description can also be applied to cases where both the gNB and the UE perform FD operations. Based on the above discussion, the following describes in detail how to configure BWP resources for intra-carrier FD operations.

[0180] The introduction of FDR is being discussed in certain scenarios (e.g., 3GPP RAN plenary). There are two main types of FDR being discussed in these scenarios: one is FDR, in which the gNB transmits and receives DL and UL signals (or transmits DL and receives UL) at the same frequency at the same time; and the other is FDR, in which the gNB transmits and receives DL and UL signals (or transmits DL and receives UL) at different frequencies at the same time. Here, different frequencies refer to different frequency resources, but different frequencies within a carrier or spectrum, unlike FDD. In both cases, the UE may or may not support FDR, in which transmission and reception occur at the same time, while in all cases, it is assumed that the gNB transmits and receives at the same time.

[0181] In operating this FDR, the gNB may consider dividing the time intervals into HD (half duplex) and FD (full duplex). These can be broadly categorized into SBFD (sub-band full duplex) and SFFD (single frequency full duplex). The slot configuration and cell resource pattern for these can be considered based on the following example.

[0182] First, SBFD can be considered as shown in Figs. 9 (a) and 10 (a). Specifically, referring to Fig. 10 (a), the subband region of the DL and the subband region of the UL may not overlap each other. In this case, a guard band may exist between the subband region of the DL and the subband region of the UL (example of slot configuration). Alternatively, referring to Fig. 9 (a), the SBFD operation can be performed based on a resource pattern of a cell or a base station. For example, in the resource pattern, a half-duplex (HD) slot / symbol and an SBFD slot / symbol can be TDM'd with each other.

[0183] Alternatively, SFFD may be considered as examples such as those in FIG. 9 (b) and FIG. 10 (b). Specifically, referring to FIG. 10 (b), the subband region of the DL and the subband region of the UL may overlap with each other. Alternatively, referring to FIG. 9 (b), the SFFD operation may be performed based on a resource pattern of a cell or a base station. For example, in the resource pattern, a half-duplex (HD) slot / symbol and an SBFD slot / symbol may be TDM'd with each other.

[0184] SBFD (or SFFD) and dynamic / flexible TDD (hereinafter, d / f TDD) can be considered in the aforementioned cases. Furthermore, TDD configurations between cells or base stations may not be identical. Regarding these two environments, the similarities and differences in CLI aspects are described below.

[0185] (1) Measurement resource aspect

[0186] 1) About d / f TDD

[0187] - Aggressor: Inter-cell UE

[0188] - HD slot only

[0189] 2) About SBFD

[0190] - Aggressor: Intra-cell UE and inter-cell UE

[0191] - HD slot & SBFD slot

[0192] -- If the BWP of the SBFD slot is similar to the HD BWP: Same with HD slot

[0193] -- If BWP of SBFD slot is different from HD BWP: Eg) measurement outside of active BWP, DL / UL sub-band

[0194] In addition, up to Rel-17, the existing CLI (Cross Link Interference) measurement can measure RSRP in SRS resources according to the existing scenario, and RSSI measurement can be possible for CLI-RSSI-resource. SRS resources for CLI purposes have restrictions on the existing resource configuration, and CLI-RSSI-resource is a resource configured for CLI. All of these resources are resources in the time / frequency domain, and the following configurations are possible for CLI up to Rel-17. The resource configuration method related to CLI can be briefly summarized as follows (refer to TS 38.331).

[0195] (1) Measurement resources

[0196] > SRS-Resource

[0197] - DL BWP id can be specified to derive the reference point of an SRS resource. In CLI measurement, it has the characteristic of linking a resource (especially a DL) to a BWP.

[0198] - For CLI SRS-RSRP measurements

[0199] -- Resource type: Only periodic types (resource type = periodic)

[0200] -- Period (Periodicity): slot 1280, 2560 cannot be configured (slot level, 1~ max 640)

[0201] -- Number of symbols, repetition factor: n1

[0202] -- Frequency hopping: b-hop (symbol level hopping) -> b-SRS (BW of SRS) -> frequency position index is constant (unless reconfigured)

[0203] -- Sequence hopping, ptrs port, spatial relation info. -> disabled

[0204] -- SRS Port 1

[0205] > CLI-RSSI-Resource

[0206] - Minimum RB 4, within active DL BW

[0207] -- To eliminate ambiguity in the introduction of Ref. SCS, set min. to 4 (15~120 SCS)

[0208] - Symbols within a slot boundary (see wrt SCS)

[0209] - UE performs CLI-RSSI measurement with SCS of active BWP (regardless of ref. SCS)

[0210] - Periodicity, offset: slot level (1 to max 640)

[0211] - QCL-D with latest received PDSCH and the latest monitored CORESET

[0212] (2) Measurement / report trigger

[0213] > SRS-RSRP, CLI-RSSI

[0214] > Event triggered or periodical

[0215] - i1-event: interference exceeds absolute threshold

[0216] - Report interval: 120ms ~ 30 minutes

[0217] With respect to the resources set according to the above "(1)" and "(2)", the UE can perform CLI measurement, and if the interference measured on the above-described set resources exceeds the absolute threshold (i1-threshold), the UE can perform (periodic) measurement on the set resources, and report the value of the measured interference through L3 signaling. Meanwhile, there is no L1 / L2 signaling for the report related to the CLI. With respect to the existing event-triggered report and periodical report of CLI, they can be set to the UE via RRC. Specifically, the event-triggered report and periodical report can be set as shown in Table 5 and Table 6 below (see TS 38.331).

[0218] CLI-EventTriggerConfigfield descriptionsi1-ThresholdThreshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event i1.eventIdChoice of CLI event triggered reporting criteria.maxReportCLIMax number of CLI measurement resource to include in the measurement report.reportAmountNumberof measurement reports.reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource insrsTriggeredListorrssiTriggeredList, as specified in 5.5.4.1.timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.

[0219] CLI-PeriodicalReportConfigfield descriptionsmaxReportCLIMax number of CLI measurement resource to include in the measurement report.reportAmountNumberof measurement reports.reportQuantityCLIThe CLI measurement quantities to be included in the measurement report.

[0220] Additionally, although not intended for CLI, the existing CSI reporting framework allows measurement / reporting of L1-RSRP / SINR in CSI-RS resources, and the related features are as follows.

[0221] > Background

[0222] - Best beam index is reported via CRI / SSBRI (with L1-RSRP / SINR)

[0223] -- SSBRI: SS / PBCH Block Resource Indicator, CRI: CSI-RS Resource Indicator

[0224] - SINR -> interference of intra-cell UEs

[0225] > Measure resource

[0226] - CSI-RS (periodic / semi-persistent / aperiodic)

[0227] - QCL-D Rx filter (Rx filter with QCL-D)

[0228] > Report

[0229] - UCI -> Periodic (PUCCH) / Semi-persistent (PUSCH or PUCCH) / Aperiodic (PUSCH)

[0230] - UCI mapping order: CRI -> L1-RSRP -> RI -> LI -> Padding bits -> PMI -> CQI (CRI -> L1-RSRP -> RI -> LI -> Padding bits -> PMI -> CQI)

[0231] - Part 1: (CRI / RI / CQI1), Part 2: (PMI / CQI2)

[0232] As described above, when considering an environment in which the gNB operates in SBFD (or SFFD), the CLI behavior may differ significantly between SBFD slots and non-SBFD slots. This is because, considering that CLI is interference from UL to DL and from DL to UL, the deviation in CLI behavior between SBFD slots and non-SBFD slots may be large. Therefore, the gNB needs to distinguish CLI measurement resources and set them to the UE for each time period in which the SBFD operation is performed (e.g., SBFD time period) and each time period in which the non-SBFD operation is performed (e.g., non-SBFD time period). In addition, the existing UE behavior related to CLI reporting can report measurement results including information on N (=maxReportCLI) resources with the most severe interference when CLI reporting is triggered by an event or periodicity. In addition, the threshold of the existing event I1 (Interference becomes higher than absolute threshold) can be set to a single value (i1-threshold) for each of RSRP and RSSI, and any resource ID can be included and reported when the event is triggered. In this context, enhancements may be required in the resource configuration for existing CLI measurements and in the reporting operation of measurements according to the resource configuration. Below, a method for improving the resource configuration and reporting operation for CLI measurements in relation to SBFD is described in detail.

[0233] Figures 11 and 12 are diagrams illustrating the CLI environment and scenarios that can be considered in relation to SBFD operation.

[0234] The CLI environment and scenarios that can be considered in relation to SBFD operation are as follows.

[0235] -> For SBFD settings,

[0236] - SBFD operation is only set within RRC configuration D / F (downlink / flexible).

[0237] - RRC-configured uplinks are aligned across gNBs (similar to CLI in d / f TDD)

[0238] -> OOB (Out-Of-Band) emissions are considered (measurable only with RSSI)

[0239] -> Coexistence

[0240] - SBFD / non-SBFD gNB in ​​the network (coexistence scenario)

[0241] - SBFD / non-SBFD UE within the cell

[0242] For example, referring to FIGS. 11 and 12, a gNB performing SBFD operation and a gNB performing non-SBFD operation can coexist within a network. For example, in the case of FIG. 11, Scenario 1 below may be considered, and in the case of FIG. 12, Scenario 2 below may be considered.

[0243] (1) Scenario 1

[0244] -> gNB-to-gNB CLI

[0245] - [inter-gNB] Aggressor gNB performing non-SBFD operation & victim gNB performing SBFD operation

[0246] -- The victim gNB can measure on the UL subband (+DL subband) (e.g., the victim gNB can measure gNB-to-gNB CLI on the UL subband)

[0247] -- SBFD UE connected to the victim gNB on the UL subband (+DL subband) can measure gNB-to-gNB CLI.

[0248] -> [intra-gNB][OOB] Self-interference of gNB

[0249] - When a DL signal is transmitted (based on RSSI), the UE in the cell can measure it in the UL subband.

[0250] -> UE-to-UE CLI

[0251] - [inter-cell UE] Attack on SBFD cell SBFD UE & damage to non-SBFD cell SBFD / non-SBFD UE

[0252] -- Damage to non-SBFD cells in UL subbands (RSRP / RSSI based) can be measured by SBFD / non-SBFD UEs.

[0253] - [intra-cell UE][OOB] Attack of SBFD cell SBFD UE and damage of SBFD cell SBFD UE

[0254] -- Measurement possible by the affected SBFD UE in the DL subband (RSSI based)

[0255] - [Intra-cell UE] Attack on SBFD cell SBFD UE & Damage to SBFD cell non-SBFD UE

[0256] -- Measurements by victim non-SBFD UEs in UL subbands (or DL / UL bands) are possible (RSSI / RSRP based).

[0257] (2) Scenario 2

[0258] -> gNB-to-gNB CLI

[0259] - [inter-gNB] non-SBFD operating attacker gNB & SBFD operating victim gNB

[0260] -- Measurement possible by the damaged gNB in ​​the UL subband (+DL subband)

[0261] -- Measurement possible by SBFD UE of victim gNB in ​​UL subband (+DL subband) (RSSI based)

[0262] - [intra-gNB][OOB] Self-Interference of gNB

[0263] -- Measurement by UE of cell for UL sub-band possible when DL signal is transmitted (RSSI based)

[0264] -> UE-to-UE CLI

[0265] - [inter-cell UE] Attack of SBFD cell Damage to SBFD UE & non-SBFD cell (SBFD / non-SBFD) UE

[0266] -- Damage in UL sub-band (SBFD / non-SBFD) measurable by UE (RSRP / RSSI based)

[0267] - [intra-cell UE][OOB] Attacking SBFD UE within the SBFD cell & Damaged SBFD UE within the SBFD cell

[0268] -- Measurement possible by the affected SBFD UE in the DL subband (RSSI based)

[0269] --- RSRP-based (partial SRS)

[0270] - [intra-cell UE] Attack SBFD UE within SBFD cell & Damage non-SBFD UE within SBFD cell

[0271] -- Measurement possible by non-SBFD UEs in UL sub-bands (or UL bands) (RSSI / RSRP based)

[0272] Against this backdrop, the introduction of L1 / L2 CLI measurement / reporting was discussed in the Rel-18 DE study and described in TR 38.858 as a candidate technology for CLI handling in DE. However, specific methods or details were not discussed. Therefore, the introduction of L1 / L2 CLI measurement / reporting is likely driven by the following motivations.

[0273] First, CLI resources need to be modified based on SBFD / non-SBFD configurations. Because the periodicity of CLI measurement resources may not always match the periodicity of SBFD / non-SBFD slots, separate CLI measurement resources that match these may be required. In particular, if SBFD / non-SBFD CLI resources are not separated into separate resources, the following issues may arise in addition to the flexibility of resource configuration.

[0274] Since the CLI resources of the SBFD slot will be smaller than those of the non-SBFD slot, the RSSI (dBm) may be very different even in the same CLI environment, but the threshold for the existing event trigger reporting is indicated as a single value. In particular, if the CLI environments are different (the RSSI between the CLI resources of the SBFD slot and the CLI resources of the non-SBFD slot may be even more different). In addition, in order to apply the CLI suppression / avoidance scheme (e.g., spatial domain / coordinated scheduling), the gNB needs to identify the CLI environment in a timely manner.

[0275] In addition, it is described below that L1 / L2 CLI measurement / reporting can be performed by reusing the existing CSI framework. In this context, the CSI framework-based L1 / L2 CLI may consider the following approaches. A method of adding a configuration for CLI to the CSI reporting configuration (e.g., Periodic / Semi-periodic / Aperiodic CLI-RSSI resources and / or SRS resources, report quantity (CLI-RSSI, SRS-RSRP)) may be considered. For example, the UE may additionally obtain a configuration for CLI measurement / reporting from the CSI reporting configuration from the gNB. At this time, the UE may report the measurement results measured in the resource for CLI measurement to the base station via UCI based on the configuration for CLI measurement / reporting (e.g., report configuration ID for CLI) obtained from the CSI reporting configuration. Alternatively, if it is assumed that the existing CLI measurement / reporting operates event-based, event-based L1 / L2 CLI reporting may be introduced. In this case, CLI measurement reports may be triggered by UEs unknown to the gNB. Furthermore, a method for setting / determining the priority between existing CSI reports and CLI reports is required, and this is further detailed below.

[0276] Furthermore, in the following, it may be considered to distinguish and receive SBFD slots / symbols (or first time resources) and non-SBFD slots / symbols (or second time resources) based on the configuration / configuration information from the gNB. For example, the first time resource may be an SBFD slot / symbol or a time period in which the gNB performs an SBFD operation, and the second time resource may be a non-SBFD slot / symbol or a time period in which the gNB does not perform an SBFD operation (e.g., an HD operation time period). The UE may receive configuration information for the first time resources with such different characteristics (e.g., time resource information related to the SBFD operation) from the gNB. Meanwhile, in the following, the proposed invention defines time resources distinguished according to whether they are time periods related to the FDR operation of the base station as the first time resource and / or SBFD slot, the second time resource and / or non-SBFD slot for the convenience of explanation, but other terms other than the defined terms may of course be applied.

[0277] L1L2 CLI measurement report based on CSI framework

[0278] Up to Rel-17, existing CLI measurement / reporting was event-triggered (when the received signal strength indicator (RSSI) exceeds a certain threshold) or performed periodically (120ms to 30min). At this time, the UE can measure and report RSSI using CLI-RSSI resources, or measure and report RSRP (reference signals received power) using SRS (Sounding Reference Signal). Considering the SBFD operation of the gNB, the CLI resource may need to be changed according to the SBFD / non-SBFD configuration. For example, since the periodicity of the CLI measurement resource may not always match the periodicity of the SBFD / non-SBFD slot / symbol, the gNB needs to configure a separate CLI measurement resource with a period corresponding to the period of the SBFD slot / symbol. If the SBFD / non-SBFD CLI resources are not separated as separate resources, the following problems may occur in addition to the flexibility of resource configuration. Since the CLI resources of the SBFD slot will be smaller than those of the non-SBFD slot, the RSSI (dBm) may be very different even in the same CLI environment, but the threshold for the existing event trigger reporting is indicated as a single value. In particular, if the CLI environments are different, the RSSI between the CLI resources of the SBFD slot and the CLI resources of the non-SBFD slot may be even more different. In addition, in order to apply the CLI suppression / avoidance scheme (e.g., spatial domain / coordinated scheduling), the gNB needs to identify the CLI environment in a timely manner. Due to these issues, the UE needs to enhance the CLI measurement / reporting based on L1 / L2, which is different from the existing one.For example, an attempt could be made to enhance CLI measurement / reporting based on the existing UE CSI reporting framework, aligning L1 / L2-based CLI measurement / reporting with the underlying UE. In this case, to eliminate ambiguity in UE behavior when CLI and CSI reporting coexist, priority rules between UCI for CLI and UCI for CSI need to be newly defined.

[0279] In the following, considering L1 / L2-based CLI reporting based on the CSI framework, Section 1 describes a reporting method of L1 / L2 CLI to minimize the amount of information for L1 / L2-based reporting, and Section 2 details a method for setting priority rules between CSI reporting and CLI reporting.

[0280] 1. Differential report for L1 / L2 CLI

[0281] The existing CLI reporting is L3-based, and the UE can perform measurements on the configured measurement resources, then perform L3 filtering on the measurement values ​​to report on the measurement information. In this context, when introducing L1 / L2-based CLI reporting based on the CSI framework, it may be important to coexist with L3 CLI reporting. For example, if a UE is configured for L1 / L2 CLI reporting while performing L3-based CLI reporting using the existing method, the UE can perform reporting on time-varying and fast CLI environments for CLI environments that L3-based CLI reporting does not support through L1 / L2 CLI reporting. Alternatively, only L1 / L2-based CLI reporting may be performed instead of L3 CLI reporting.

[0282] Against this backdrop, while new metrics may be introduced for L1 / L2 CLI reporting, coexistence with L3-based CLI reporting may be important when reusing existing metrics. Alternatively, coexistence with CSI reporting may be important when L1 / L2-based CLI reporting replaces L3 CLI reporting. Furthermore, since L1 / L2 CLI reporting is L1 / L2 signaling, minimizing the overhead of CLI reporting may be key. When reporting multiple measurement results in a single report, the overhead of CLI reporting can be reduced while maintaining the measurement results by reporting the differences between the multiple measurement results. The most important consideration in introducing such difference reporting is which measurement value is used as the basis for reporting the differences between the multiple measurement results. For example, the reference value for which the difference value is calculated must be defined to reduce the overhead of CLI reporting and prevent misunderstanding between the gNB and the UE regarding the CLI reporting. Below, we will explain the method in detail.

[0283] (1) Proposal 1

[0284] In Proposal 1, the UE can report the difference value for L1 / L2 CLI reports based on L3 CLI reports.

[0285] The UE can perform L3 CLI measurements / reports according to existing operations, and additionally perform L1 / L2 CLI measurements / reports. In this case, the UE can report the difference between L1 / L2 CLI measurements based on previously reported L3 CLI measurements. This approach has the advantage of reducing the overhead of L1 / L2 CLI reporting while preventing misunderstandings between the gNB and the UE.

[0286] For example, if the UE has already reported L3 CLI measurement values ​​to the gNB, the UE may report L1 / L2 CLI reports based on the most recently reported L3 CLI measurement values ​​to the gNB. Here, the CLI measurement reports may include measurement values ​​of CLI-RSSI and / or measurement values ​​of SRS-RSRP. In this case, the L1 / L2 CLI-RSSI reports may include a value for the difference between the largest value among the L3 CLI-RSSI reported measurement values ​​and the L1 / L2 CLI-RSSI measurement values, or a value for the difference between the largest value among the L3 SRS-RSRP reported measurement values ​​and the L1 / L2 SRS-RSRP measurement values. Alternatively, the L1 / L2 CLI-RSSI report that the UE reports to the gNB may include a value for the difference between the measurement value reported for the CLI-RSSI resource with the lowest or highest index among the L3 CLI-RSSI reported measurement values ​​and the L1 / L2 CLI measurement values, or a value for the difference between the measurement value reported for the SRS resource with the lowest or highest index among the reported L3 SRS-RSRP measurement values ​​and the L1 / L2 CLI measurement values. On the other hand, if the UE does not report the L3 CLI report to the gNB, since there is no value reported to the gNB, the UE may report the L1 / L2 SRS-RSRP or L1 / L2 CLI-RSSI value itself instead of the above-mentioned difference value.

[0287] Alternatively, the UE may consider performing L1 / L2 CLI reporting using some of the mapping tables for measurement reports used for existing L3-based CLI reporting from the gNB. For example, existing L3-based reporting reports report corresponding reported values ​​based on mapping tables for different measurement reports that have been agreed upon in advance for SRS-RSRP and CLI-RSSI, respectively. The specific mapping tables can be defined as in Tables 7 and 8 below (see 3GPP TS 38.133).

[0288] Reported valueMeasured quantity valueUnitSRS-RSRP_0SRS-RSRP<-140dBmSRS-RSRP_1-140≤ SRS-RSRP<-139dBmSRS-RSRP_2-139≤ SRS-RSRP<-138dBmSRS-RSRP_3-138≤ SRS-RSRP<-137dBmSRS-RSRP_4-137≤ SRS-RSRP<-136dBm......SRS-RSRP_95-46≤ SRS-RSRP<-45dBmSRS-RSRP_96-45≤ SRS-RSRP<-44dBmSRS-RSRP_97-44≤ SRS-RSRPdBmSRS-RSRP_98InfinityNote: 'Infinity' means that UE cannot detect SRS due to too strong signal to measure.

[0289] Reported valueMeasured quantity valueUnitCLI-RSSI_00CLI-RSSI < -100dBmCLI-RSSI_01-100 ≤ CLI-RSSI < -99dBmCLI-RSSI_02-99 ≤ CLI-RSSI < -98dBm.......CLI-RSSI_74-27 ≤ CLI-RSSI < -26dBmCLI-RSSI_75-26 ≤ CLI-RSSI < -25dBmCLI-RSSI_76-25 ≤ CLI-RSSIdBm

[0290] Referring to Tables 7 and 8, 99 rows are defined for SRS-RSRP and 77 rows are defined for CLI-RSSI, so L1 / L2 CLI reporting according to Tables 7 and 8 may include a 7-bit reporting value. In order to reduce the overhead for the reporting value, L1 / L2 CLI reporting needs to be performed based on a part of a measurement report mapping table (e.g., Table 7 or Table 8) according to the measurement value reported in the most recent L3 CLI report. For example, the UE may determine the measurement report mapping table including the measured quantity value in the most recently reported L3-based CLI report to the gNB by prior agreement or contract, or may perform L1 / L2 CLI reporting based on the measurement report mapping table including the measured quantity value of the most recently reported L3-based CLI report as instructed by the gNB. Alternatively, the gNB may instruct the UE to use some of the measurement report mapping tables for L1 / L2 CLI reporting through signaling such as RRC / MAC-CE / DCI, and the UE may perform L1 / L2 CLI reporting based on the instructed measurement report mapping tables. Such measurement report mapping tables used for L1 / L2 CLI reporting may be characterized by having a limited number of rows of 2^N so that reporting is based on N bits. Here, the value of N may be a value determined by prior agreement in consideration of the UCI payload.

[0291] For example, the reported value corresponding to the largest value among the values ​​reported in the latest L3 CLI report that the UE reported to the gNB may be SRS-RSRP_95 (e.g., reported SRS-RSRP value greater than or equal to -46 dBm and less than or equal to -45 dBm), or CLI-RSSI_74 (e.g., reported CLI-RSSI value greater than or equal to -27 dBm and less than or equal to -26 dBm), and a 3-bit report value may be reported for each of SRS-RSRP or CLI-RSSI reported in L1 / L2 CLI reports. In this case, the UE may perform L1 / L2 CLI reporting based on a mapping table (Table 9) that is part of the SRS-RSRP measurement report mapping table including SRS-RSRP_95, or a mapping table that is part of the CLI-RSSI measurement report mapping table including CLI-RSSI_74 (Table 10). For example, in the case of L1 / L2 SRS-RSRP reporting, as defined in Table 9, a mapping table may be used in which newly defined report values ​​are mapped to adjacent measurement values ​​centered on the measurement value corresponding to SRS-RSRP_95 in Table 7 (-46 dBm or more and -45 dBm or less).

[0292] Reported valueMeasured quantity valueUnitSRS-RSRP_0SRS-RSRP<-49dBmSRS-RSRP_1-49 ≤ SRS-RSRP<-48dBmSRS-RSRP_2-48 ≤ SRS-RSRP<-47dBmSRS-RSRP_3-47 ≤ SRS-RSRP<-46dBmSRS-RSRP_4-46 ≤ SRS-RSRP<-45dBmSRS-RSRP_5-45 ≤ SRS-RSRP<-44dBmSRS-RSRP_6-44 ≤ SRS-RSRPdBmSRS-RSRP_7InfinityNote: 'Infinity' means that UE cannot detect SRS due to too strong signal to measure.

[0293] Reported valueMeasured quantity valueUnitCLI-RSSI_0CLI-RSSI < -31dBmCLI-RSSI_1-31 ≤ CLI-RSSI < -30dBmCLI-RSSI_2-30 ≤ CLI-RSSI < -29dBmCLI-RSSI_3-29 ≤ CLI-RSSI < -28dBmCLI-RSSI_4-28 ≤ CLI-RSSI < -27dBmCLI-RSSI_5-27 ≤ CLI-RSSI < -26dBmCLI-RSSI_6-26 ≤ CLI-RSSI < -25dBmCLI-RSSI_7-25 ≤ CLI-RSSIdBm

[0294] Alternatively, the UE may perform reporting based on a table configured as part of the SRS-RSRP measurement report mapping for L1 / L2 CLI reporting, or a table configured as part of the CLI-RSSI measurement report mapping. In this case, the gNB may indicate to the UE a specific mapping table (a mapping table in which report values ​​are defined by measurement value ranges, as in Tables 7 to 10) that is unrelated to the L3 CLI report most recently reported by the UE to the gNB, and the UE may report L1 / L2 CLI based on the specific mapping table indicated by the gNB. This may be useful when there is a large difference between the L3 CLI measurement value recently reported by L3 filtering and the L1 / L2 CLI measurement value without applying L3 filtering.

[0295] At this time, the UE may perform L1 / L2-based CLI reporting without performing L3-based CLI reporting to the gNB. In this case, the UE may perform L1 / L2-based CLI reporting based on a measurement report mapping table for existing L3-based measurement reporting, or may perform L1 / L2-based CLI reporting based on a default measurement report mapping table agreed upon in advance.

[0296] (2) Proposal 2

[0297] For Proposal 2, the UE may report the difference value for the remaining L1 / L2 CLI measurements based on the most severe measurement value among the CLI measurements included in the L1 / L2 CLI report within a single report. For example, Proposal 2 may be for a case where L3-based CLI measurements / reports are replaced with the L1-based CLI measurements / reports.

[0298] When L1 / L2 based CLI reporting is introduced, the UE may report RSSI or RSRP only for a single measurement resource, but different RSSIs or RSRPs may also be reported for multiple measurement resources. Alternatively, to support configuration flexibility, multiple RSSIs or RSRPs measured at different times for a single measurement resource may be configured to be reported. In this reporting method, similar to the beam RSRP / SINR reporting method of the existing CSI reporting, the UE may include multiple measurement results in a single CLI report. In this case, the difference value for the remaining values ​​based on the dominant (severe) CLI may be reported.

[0299] For example, the content to be included in the report that the UE transmits to the gNB as L1 / L2 CLI report may include CLI 1, CLI 2 and CLI 3, and CLI 2 may be the most dominant (highest RSRP or RSSI, or highest except infinity). In this case, the UE may transmit the resource ID (or resource index) measured by CLI 2 and the absolute quantity value of CLI 2 via a bitmap or direct instruction, and for the remaining CLIs 1 and 3, the difference value between the absolute quantity value of CLI 2 and the absolute value of CLI 1, and the difference value (quantity) between the absolute value of CLI 2 and the absolute value of CLI 3 (if the resource measured by CLI 2 is different, the resource IDs / indexes measured by CLI 1 and CLI 3 are also reported). However, this method can only be applied within CLIs corresponding to the same measurement metric. For example, the method of Proposal 2 can be applied only within RSSI measurements for CLI-RSSI resources or only within RSRP measurements for SRS resources.

[0300] 2. CSI reporting priority for CLI reporting

[0301] The priority rules for CSI reporting of existing UEs are defined as shown in Table 11 below (see 3GPP TS 38.214 section 5.2.5).

[0302]

[0303] Referring to Table 11, when UL channels / signals for multiple CSI reports collide (e.g., when multiple CSI reports overlap in the time domain), the UE may transmit only the UL channel / signal for one CSI report or multiplex and report / transmit multiple CSI reports based on the priorities defined in Table 11. Here, the multiple CSI reports can all be transmitted on the resources (time / frequency / space) configured / instructed by the base station. Therefore, the base station has no problem applying the above priority rule. However, when reporting the CSI framework-based L1 / L2 CLI report to UCI, the following two problems may occur. Meanwhile, the y, k, c, and s can be defined as priority indices, and the Pri iCSI The smaller the value, the higher the priority, and the Pri iCSI The higher the value of Pri, the lower the priority may be. For example, the above Pri iCSI A measurement report with a small value of Pri iCSI The value of may take precedence over a relatively large measurement report.

[0304] First, since all priority rules in Table 11 above are applied only to CSI reports based on the base station's configuration / instruction (e.g., the y value of the priority rules is defined only for CSI reports based on the base station's configuration / instruction), they cannot be directly applied to the newly added CSI framework-based L1 / L2 CLI reports.

[0305] Second, when the CSI framework-based L1 / L2 CLI report includes the event-triggered CLI report, the base station cannot know whether the event-triggered L1 / L2-based CLI report is performed, because only the UE knows whether an event has occurred (until the report is made). Therefore, even if the first problem is solved, it is difficult for the base station to receive UL signals (e.g., UCI) by applying the priority rule. For example, the base station must perform reception of UL signals by applying the priority rule assuming that the event-triggered L1 / L2-based CLI report has been performed, or must perform reception of UL signals by applying the priority rule assuming that the event-triggered L1 / L2-based CLI report has not been performed. In consideration of these problems, the following Proposals 2-1, 2-2, and 2-3 are proposed.

[0306] (1) Proposal 1-1

[0307] For Proposal 1-1, CLI reports may have a lower priority than all existing CSI reports. For example, the y value of CLI reports may be set to 4 in the priority formula above. If a CLI report conflicts with another UL signal (e.g., UCI for CSI reports) other than a CSI report, the CLI report may always be dropped. This may resolve ambiguity in UCI piggybacking or UCI multiplexing.

[0308] For example, when an event for L1 / L2-based CLI reporting is introduced, the gNB may not know whether an event has occurred, or may not know how many CLI measurements are included in a top-X CLI report (e.g., reporting X CLI measurements in descending order). In this case, the gNB needs to apply priority rules to all households to receive it. Therefore, the burden on the gNB can be reduced by applying the method proposed in Proposal 1-1.

[0309] (2) Proposal 1-2

[0310] Proposal 1-2 may be a way to redefine CLI reporting for existing priority rules when there is no ambiguity about whether L1 / L2 CLI reporting has occurred (e.g., when CLI reporting is performed by the base station's configuration rather than event-triggered reporting). For example, in the case of L1 / L2 CLI reporting instructed by the gNB, there may be no ambiguity about whether CLI reporting has occurred. Alternatively, even if event-triggered L1 / L2 CLI reporting is introduced, there may be no ambiguity about whether CLI reporting has occurred if the gNB knows whether L1 / L2 CLI events have occurred through a separate report from the UE, or if L1 / L2 CLI reporting is always reported only on specific resources. In such cases, priority rules according to at least one of the methods of Proposals 1-2a to 1-2h below may be defined.

[0311] Here, CLI reporting, unlike CSI reporting, may include dominant CLI measurements and non-dominant CLI measurements. In the case of existing L3-based CLI reporting, the UE may report on the N most severe CLI measurement resources (and / or N measurement values) at the time of CLI reporting. For example, the UE may report to the base station information on the N highest CLI measurement values ​​and the corresponding N measurement resources among the multiple CLI measurement values ​​measured on the multiple CLI measurement resources at the time of CLI reporting. Based on this reporting method / reporting characteristic, different priorities may be introduced for dominant CLI and non-dominant CLI among the methods of Proposals 1-2a to 1-2h below.

[0312] For example, for a total of X CLI measurements reported by a UE, different priority rules may be applied between the dominant or severe (e.g., the CLI measurement with the highest RSRP or RSSI) K (or N) CLI measurements (e.g., top-K CLI) and the remaining XK CLI measurements. For example, it may be considered that the top-K CLI measurements follow Proposal 1-2a, the XK CLI measurements follow Proposal 1-2f, and so on. Alternatively, the top-K CLI measurements may follow one of the proposed methods described below, and the XK CLI measurements may be checked to see whether they can be reported by including them in the PUSCH / PUCCH carrying CSI / CLI. If XK CLI measurements can be included in the PUSCH / PUCCH, the XK CLI measurements can be multiplexed and transmitted on the PUSCH / PUCCH, and if the XK CLI measurements cannot be included in the PUSCH / PUCCH, the XK CLI measurements can be dropped. At this time, in the proposed method described later, etc., the number K of CLI measurements to be reported by the UE by checking the priority with the CSI report may be indicated by the gNB through RRC / MAC-CE / DCI, etc., or may be a value determined by a prior agreement (or rule).

[0313] 1) Proposal 1-2a

[0314] Proposal 1-2a could be a way to give CLI reports a higher priority than all existing CSI reports by introducing a new parameter i in the formula of the priority rule in Table 11.

[0315] For example, the mathematical expression 1 below, which is the formula for the priority rule of the CSI report in Table 11, can be modified as in mathematical expression 2. In this case, the CLI report can have the i value set to 0, and the existing CSI report can be set to i=1. In this case, the CLI report can always be reported with priority over the CSI report in case of a conflict with another CSI report.

[0316] [Mathematical Formula 1]

[0317] Pri iCSI (y,k,c,s)= 2·N cells ·M s ·y+N cellls ·M s ·k+M s ·c+s

[0318] [Equation 2]

[0319] Pri iCSI (i,y,k,c,s)=8·N cells ·M s ·i +2·N cells ·M s ·y+N cellls ·M s ·k+M s ·c+s

[0320] This is because the UE is the subject of measurement for UE-to-UE CLI (e.g., CLI between UE and UE), and the gNB can determine the UE-to-UE CLI solely by relying on the UE's report. Therefore, the CLI report (or UE-to-UE CLI report) may be a more important or valuable report than the existing CSI report. In addition, the channel change of the UE according to the CLI situation must be reported quickly to the gNB so that the gNB can perform appropriate scheduling and / or CLI suppression techniques in response to such channel change. In this respect, the CLI report needs to be reported with higher priority than the CSI report.

[0321] 2) Proposal 1-2b

[0322] For Proposal 1-2b, the y value for CLI reporting in Equation 1 for the priority rule for CSI defined in Table 11 can be set to 0. In this case, CLI reporting has the same priority as the existing AP (aperiodic) CSI reporting on PUSCH.

[0323] For example, in Equation 1, the y value can be set to 0 for CLI reporting. AP (aperiodic) CSI reporting in the existing PUSCH is a dynamic reporting method that is triggered on demand by the base station as needed. In comparison, CLI reporting has similar properties to the existing AP CSI reporting except that the triggering entity changes from the base station to the UE, except that it is CLI instead of CSI. Therefore, CLI reporting can be set to the same priority as AP CSI reporting, which corresponds to the highest priority of the existing CSI reporting, and the priority can be finally determined through values ​​such as k, c, and s.

[0324] 3) Proposal 1-2c

[0325] For Proposal 1-2c, CLI reporting may have a lower priority than AP CSI reporting transmitted on PUSCH and a higher priority than SP (Semi-periodic) CSI transmitted on PUSCH.

[0326] For example, CLI reporting may have the y value set to 1 in the above-described mathematical expression 1, and SP CSI transmitted on PUSCH, SP CSI transmitted on PUCCH, and periodic CSI transmitted on PUCCH may have the y values ​​set to 2, 3, and 4, respectively. Since L1 / L2 CLI reporting may be likely to operate together with the existing L3 CLI reporting, L1 / L2 CLI reporting may be operated based on a dynamic reporting method in which reporting is triggered on demand as needed, similar to the existing AP CSI reporting. However, since the base station is traditionally the entity that manages the UL resources of all UEs in a cell and provides settings / instructions to the UEs, it may be appropriate for dynamic CSI reporting triggered by the base station to have priority over CLI reporting. In addition, although the SP CSI transmitted on PUSCH is dynamically triggered by the base station, it can be periodically reported multiple times before deactivation. Therefore, it may be appropriate for CLI reports, which are dynamically reported by an event occurrence or by an instruction from the gNB, to take precedence over SP CSI transmitted on PUSCH.

[0327] 4) Proposal 1-2d

[0328] For Proposal 1-2d, CLI reporting can have the same priority as SP CSI reporting on PUSCH, with the y value set to 1 in Equation 1 of the priority rule for CSI.

[0329] For example, CLI reporting can be prioritized by setting the y value in Equation 1 to 1. Both L1 / L2 CLI reporting and AP / SP CSI reporting on the existing PUSCH can be dynamic reporting methods that are triggered on demand as needed. On the other hand, SP CSI reporting on the existing PUCCH is triggered / activated by MAC-CE, and thus may have lower dynamic properties than AP / SP CSI reporting on the PUSCH that is triggered based on DCI. For example, MAC-CE is higher layer information than DCI and thus may take more time to decode. Therefore, the priority of CLI reporting can be set to be the same as that of SP CSI reporting on the PUSCH, but higher than that of SP CSI reporting on the PUCCH.

[0330] 5) Proposal 1-2e

[0331] In Proposal 1-2e, CLI reporting has the same priority as SP CSI reporting on PUCCH by setting the y value in Equation 1 for the priority rule for CSI reporting to 2.

[0332] For example, CLI reporting may have the y value in Equation 1 set to 2. CLI reporting, AP / SP CSI reporting on the existing PUSCH, and SP CSI reporting on the PUCCH are all dynamic reporting methods that are triggered on demand as needed. On the other hand, P (Periodic) CSI reporting on the existing PUCCH does not have an on-demand reporting property because the CSI reporting is set semi-statically in a way that is set by an RRC signal. Therefore, the priority of CLI reporting may be set to be the same as that of SP CSI reporting on the PUCCH, but may be set higher than that of P CSI reporting on the PUCCH.

[0333] 6) Proposal 1-2f

[0334] In Proposal 1-2f, CLI reporting can have the same priority as P CSI reporting on PUCCH by setting the y value of Equation 1 for the priority rule for CSI reporting to 3.

[0335] For example, CLI reporting may have the y value set to 3 in the priority formula above. CLI reporting, the existing AP / SP CSI reporting on PUSCH, and SP CSI reporting on PUCCH are all dynamic reporting methods that are triggered on demand as needed. However, since the base station is traditionally the entity that manages the UL resources of all UEs in the cell and provides configuration / instruction to the UEs, it may be desirable for dynamic CSI reporting configured / triggered by the base station to have priority over CLI reporting. In addition, P CSI on PUCCH is a semi-static CSI report configuration although the base station is the triggering entity, and does not have an on-demand reporting property, so its utility may be reduced. Therefore, CLI reporting may be set to the same priority as P CSI reporting on PUCCH.

[0336] 7) Suggestion 1-2g

[0337] In Proposal 1-2g, CLI reporting can reuse the existing UL channel setup method for CSI feedback, and reuse the priorities corresponding to the existing UL channel setup method for CSI feedback.

[0338] When event-triggered CLI reporting is introduced, a definition of L1 / L2 events is required. Existing L3-based event-triggered reporting has start and end conditions for events, and measurement results are reported during the time between them. Similarly, when events for L1 / L2 CLI reporting are introduced, start / end conditions can be introduced by inheriting events of the same concept (e.g., from the time when a preset threshold is exceeded to the time when it falls below the threshold), and L1 / L2-based CLI reporting can be performed continuously from the start to the end. However, existing L3-based CLI measurements are smoothed by L3 filtering, so an abrupt end to an event during the start and end conditions, or an abrupt restart after the event end, may not be expected. In contrast, L1-based measurement reports (e.g., L1-RSRP, L1-SINR) apply L1 filtering, and the L1 filtering can be based on the UE implementation. Accordingly, in the case of L1 / L2 CLI reporting, it may be a report based on a measurement result to which L1 filtering is applied according to the UE implementation. In this case, a one-time event, rather than an event with start and end conditions, may be considered. For example, a one-time event may be considered when a single measurement instance or an L1-filtered measurement result exceeds a set threshold N times in a row. Here, the value of N may be a value that the gNB notifies the UE via RRC / MAC-CE / DCI, or is determined by a definition of a pre-agreed L1 / L2 CLI event. In this context, the following examples may be considered for events without end conditions that trigger CLI reporting and events with start and end conditions.

[0339] For example, for events without termination conditions (or, if a separate event is reported to the gNB), CLI reporting may have y in Equation 1 set to 0, which is the same priority as AP CSI reporting in the existing PUSCH.

[0340] Alternatively, if there is a start and an end of an event, the CLI report may have y in Equation 1 set to 1, which is the same priority as the SP CSI report in the existing PUSCH. Alternatively, if there is a start and an end of an event, the CLI report may have y in Equation 1 set to 2, which is the same priority as the SP CSI report in the existing PUCCH.

[0341] Alternatively, if resources are set for P CSI on PUCCH for CLI reporting and the UE can report CLI only when an event occurs, CLI reporting can have the y value set to 3 in Equation 1, which is the same priority as P CSI reporting on the existing PUCCH.

[0342] 8) Proposal 1-2h

[0343] The above-described proposals have redefined the y value in the existing priority equation 1 for CLI reporting, but in Proposal 1-2h, the priority between CLI reporting and existing CSI reporting may be determined by the k value for the same y value. To this end, the priority determination methods according to the following Alts may be considered. For example, in the following, it may be assumed that the y value of CLI reporting is determined according to periodicity (and / or whether it is transmitted on PUSCH or PUCCH), similar to the CSI reporting.

[0344] -> Alt 1: CLI Report > Legacy CSI Reporting Carrying L1-RSRP / L1-SINR > Legacy CSI Reporting Not Carrying L1-RSRP / L1-SINR

[0345] CLI reports are about the CLI situation experienced by the UE for UE-to-UE, and if not reported to the gNB, the gNB may not be able to understand the information. Therefore, the priority of CLI reports may be higher than that of RI / PMI / CQI reports. In addition, CLI reports may be set to a higher priority than Legacy CSI reports that carry L1-RSRP / L1-SINR, which correspond to existing / legacy beam reports.

[0346] Here, the UE is the subject of CLI measurements, and thus can best grasp the time-varying / current status of CLI. Therefore, CLI reports may be more valid and useful than legacy CSI reports (pre-configured by the base station). For this reason, it may be reasonable to prioritize CLI reports over legacy CSI reports carrying L1-RSRP / L1-SINR in the event of a collision.

[0347] -> Alt 2: Legacy CSI reporting carrying L1-RSRP / L1-SINR > CLI reporting > Legacy CSI reporting without L1-RSRP / L1-SINR

[0348] If CLI reports do not report the CLI situation for UE-to-UE experienced by the UE to the gNB, the gNB cannot identify such CLI situation. Therefore, the CLI reports need to be given a higher priority than the Rank Indicator (RI) / Pre-coding Matrix Indicator (PMI) / Channel Quality Indicator (CQI) reports. However, the CLI reports need to be given a lower priority than the Legacy CSI reports carrying L1-RSRP / L1-SINR corresponding to existing / legacy beam reports. This is because, traditionally, the eNB is the entity that manages the UL resources of all UEs in the cell and provides configuration / instruction to the UEs, so it may be desirable for the beam reports configured / triggered by the eNB to have a higher priority than the CLI reports.

[0349] -> Alt 3: Legacy CSI reporting carrying L1-RSRP / L1-SINR > Legacy CSI reporting without L1-RSRP / L1-SINR > CLI reporting

[0350] CLI reports may be prioritized lower than Legacy CSI reports carrying L1-RSRP / L1-SINR and Legacy CSI reports not carrying L1-RSRP / L1-SINR. This is because, traditionally, the base station is the entity that manages UL resources of all UEs in the cell and provides configuration / instructions to the UEs, so it is desirable for CSI reports configured / triggered by the base station to have priority over CLI reports.

[0351] Meanwhile, the above-described Alt. 1, 2 and 3 can be changed from the mathematical expression 1 for the existing priority to the mathematical expression 3 below as new k values ​​are introduced.

[0352] [Equation 3]

[0353] PriiCSI (y,k,c,s)=3·N cells ·M s ·y+N cellls ·M s ·k+M s ·c+s

[0354] -> Alt 4: Legacy CSI reporting carrying L1-RSRP / L1-SINR = CLI reporting > Legacy CSI reporting without L1-RSRP / L1-SINR

[0355] CLI reports can be set to the same priority as CSI reports carrying the existing L1-RSRP / L1-SINR. For example, CLI reports are also considered / judged as a type of beam report, so CLI reports have the same priority as CSI reports carrying the existing L1-RSRP / L1-SINR in comparison of k values, and can have a higher priority than RI / PMI / CQI. In addition, CLI reports can be combined with other proposals described above to introduce priority differences with existing CSI reports at the y value level or the i value level. Alternatively, priority differences between CLI reports and existing CSI reports can be established at the i, y, c or s value levels.

[0356] -> Alt 5: Legacy CSI reporting carrying L1-RSRP / L1-SINR > Legacy CSI reporting without L1-RSRP / L1-SINR = CLI reporting

[0357] CLI reports can be reused by setting the same priority (at the k value level) as legacy CSI reports that do not accompany L1-RSRP / L1-SINR, thereby reusing the existing priority implementation. However, CLI reports can be prioritized differently at different priority value levels (e.g., different i, y, c, or s value levels) than legacy CSI reports that do not accompany L1-RSRP / L1-SINR.

[0358] Alternatively, CLI reports may be prioritized lower than Legacy CSI reports carrying L1-RSRP / L1-SINR, but lower than Legacy CSI reports not carrying L1-RSRP / L1-SINR. This is because, traditionally, the eNB is the entity that manages UL resources of all UEs in a cell and provides configuration / instructions to the UEs, so it is desirable for eNB-configured / triggered CSI reports to have priority over CLI reports.

[0359] (2) Proposal 2

[0360] In Proposal 2, separate reporting settings for L1 / L2 CLI reporting could be introduced, and priorities at the reporting settings level could be introduced.

[0361] The above-described Proposals 1-1 and 1-2 assume and describe the existing CLI reporting as existing CSI reporting and introduce priority rules within the CSI reporting configuration. Alternatively, a separate CSI reporting configuration for L1 / L2 CLI reporting could be introduced, similar to the L1 trigger mobility introduced in Rel-18. This method is the simplest for implementing CLI reporting into existing CSI reporting, and has the advantage of easily resolving conflicts between CLI reporting and CSI reporting by introducing priority at the reporting configuration level since they are different reporting configurations.

[0362] For example, a CLI-ReportConfig IE containing measurement resources for L1 / L2 CLI measurements may be introduced. In this case, the configuration ID for the CLI report may be indicated in CSI-AperiodicTriggerStateList and / or CSI-SemiPersistentOnPUSCH-TriggerStateList, so that CLI reporting based on the CSI reporting framework may be performed. Thereafter, priority rules according to the reporting configuration level may be introduced. CSI reports configured by the existing LTM-CSI-ReportConfig may have a higher priority than CSI reports configured by CSI-ReportConfig. Therefore, the following Alts may be considered for the CSI report (or CLI report) configured by CLI-ReportConfig.

[0363] ->Alt. 2-1: CSI report configured withLTM-CSI-ReportConfig> CSI report configured withCSI-ReportConfig> CSI report configured withCLI-ReportConfig

[0364] - This is because, traditionally, the base station is the entity that manages the UL resources of all UEs within the cell and issues configuration / instructions to the UEs, so it is desirable for the CSI report configured / triggered by the base station to have priority over the CLI report.

[0365] ->Alt. 2-2: CSI report configured withLTM-CSI-ReportConfig> CSI report configured withCLI-ReportConfig> CSI report configured withCSI-ReportConfig

[0366] - CLI reports are about the UE-to-UE CLI situation experienced by the UE, and the gNB cannot understand this information without reporting it. Furthermore, since the UE is the subject of CLI measurements, it can be the first to understand / better understand the time-varying / current status of CLI. Therefore, CLI reports can be more valid / utilizable than existing CSI reports (pre-configured by the base station). In this regard, if a conflict occurs between existing CSI reports and CLI reports, CLI reports can be configured to take precedence over CSI reports.

[0367] Figure 13 is a diagram illustrating how a UE determines a priority for a CLI report.

[0368] As described above, L1 / L2 CLI reporting may be introduced instead of L3 CLI reporting in relation to CLI reporting. In this case, L1 / L2 CLI reporting may be performed based on the existing L1 / L2 CSI reporting framework as described in Sections 1 and 2, and the values ​​of y and k (e.g., priority index) in Equation 1 may be defined to determine which report to prioritize when there is overlap between CLI reporting and CSI reporting. Hereinafter, a method for setting / determining the priority for CLI reporting will be described in more detail. In addition, the method proposed in "1. Differential report for L1 / L2 CLI" and / or "2. CSI reporting priority for CLI reporting" may be naturally applied even if the contents described below are not explicitly described.

[0369] Referring to FIG. 13, the UE can obtain measurements related to measurement resources (S131). For example, the UE can measure RSRP, RSSI, or SINR (Signal to Interference plus Noise Ratio) for signals received from the measurement resources. Here, the measurement resources can include CLI measurement resources (SRS or CLI RSSI resources) and CSI measurement resources, and can be provided from the base station through CSI resource configuration parameters / information.

[0370] Next, the UE may determine a priority associated with a measurement report including the measurement based on a priority index associated with a CSI (channel state information) report (S133). Here, the priority may be a priority according to Table 11 and / or Equation 1 for determining priorities among CSI reports as described above. In addition, the priority index may be y, k, c, s in Equation 1, wherein y is a priority index set based on the periodicity of the CSI report / CLI report and / or the reporting channel, k is a priority index set based on whether the measurement report includes a measurement value for RSRP / SINR and / or a report type for which measurement of the RSRP is requested, c may be a serving cell index, and s may be a configuration ID associated with the report.

[0371] For example, with respect to CLI reporting, the priority index k may be determined based on whether the measurement report includes Reference Signal Receiver Power (RSRP) measured in the measurement resource and the report type of the RSRP. Here, the report type of the RSRP may be divided into a first type that reports the RSRP for CSI and a second type that reports the RSRP for CLI (Cross Link Interference). In this case, if the RSRP included in the measurement report is an RSRP for the first type (e.g., beam measurement for CSI reporting), the k may be determined / set to a first value. Here, the first value may be 0 as defined in Table 11. Or, in this case, if the RSRP included in the measurement report is an RSRP for the second type (e.g., a CSI report including an RSRP measured for CLI reporting), the k may be determined / set to a second value. Here, the second value may be 1 as suggested in Table 11 and Section 2 Proposal 1-2h alt 2, or 2 as suggested in Section 2 Proposal 1-2h alt3. Alternatively, the k value for the CLI report including RSRP for the second type, such as Section 2 Proposal 1-2h alt5, may be set / determined to be 1, which is the same as the k value for the measurement report (e.g., report for PMI, CQI, RI, etc.) that does not include the RSRP. Alternatively, the k value for the CLI report including RSRP for the second type, such as Section 2 Proposal 1-2h alt2, may be set / determined to be 1, and the k value for the measurement report (e.g., report for PMI, CQI, RI, etc.) that does not include the RSRP may be set / determined to be 2.Alternatively, the k value for CLI reports including RSRP for the second type, such as alt3 of proposal 1-2h of section 2, may be set / determined to 2, and the k value for measurement reports not including RSRP (e.g., reports for PMI, CQI, RI, etc.) may be set / determined to 1.

[0372] For example, the existing k value is a value set to 0 or 1 depending on whether a measurement value for RSRP or SINR is included in a measurement report (e.g., a CSI report). However, as described above, in determining the k value, additional consideration needs to be given to a measurement report including RSRP for CSI and a measurement report including RSRP for CLI (measured based on SRS, which is a measurement resource) due to the introduction of L1 CLI reporting. To this end, unlike the existing case where k is set to 0 if the measurement report includes the RSRP, the proposed invention can set / determine the k value to 0 for a measurement report including RSRP for CSI and to 1 for a measurement report including RSRP for CLI. Here, the k value can be set to 1 for a measurement report that does not include RSRP, in the same way as for a measurement report including RSRP for CLI.

[0373] Alternatively, as in alt1 of proposal 1-2h in section 2, the k value for a measurement report (or CSI report) including RSRP for the second type may be set to 0, the k value for a measurement report (or CSI report) including RSRP for the first type may be set to 1, and the k value for a measurement report (or CSI report) including RSRP may be set to 2. As in alt3 of proposal 1-2h in section 2, the k value for a measurement report (or CSI report) including RSRP for the first type may be set to 0, the k value for a measurement report (or CSI report) including RSRP may be set to 1, and the k value for a measurement report (or CSI report) including RSRP may be set to 2.

[0374] Alternatively, as proposed in Proposals 1-1 and / or 1-2a to 1-2g of Section 2, the above-described y value for the CLI report may be set / determined based on the periodicity of the measurement report and the channel through which it is transmitted.

[0375] Next, the UE may perform a transmission procedure of the measurement report based on the above priority (S135). For example, a time-domain overlap (or collision) may occur between the measurement report and another measurement report (e.g., a CSI report including CLI measurement information and another CSI report). In this case, the UE may compare the priority determined for the CLI report (or the CSI report including CLI measurement information) as described above with the priorities of the other measurement reports to determine whether to give priority to the CLI measurement report or to drop it. For example, if there is an overlap between a first measurement report including RSRP for CLI and a second measurement report including RSRP for CSI, the UE may drop the first measurement report with a lower priority and transmit / report the second measurement report with a higher priority.

[0376] Alternatively, if the measurement report includes measurement values ​​for multiple CLI measurement resources, the UE may report the measurement report to the base station including differences between a specific reference measurement value and the remaining measurement values, as in Proposal 1 and / or Proposal 2 of Section 1. Here, the specific reference measurement value may be determined based on the most recent L3 CLI reported measurement value, as described in Proposal 1 of Section 1, or may be determined as the highest value among the measurement values ​​(L1 CLI measurement values) for the multiple CLI measurement resources.

[0377] Figure 14 is a diagram for explaining how a base station receives a CLI report from a UE.

[0378] Referring to FIG. 14, the base station can transmit CSI resource configuration information that sets CLI measurement resources (e.g., SRS or CLI RSSI resources) and CSI measurement resources to the UE (S141).

[0379] Next, the base station can receive the measurement report transmitted from the UE based on the priority among the measurement reports (S143). For example, the base station can receive the measurement report transmitted by applying the priority according to Table 11 and / or Equation 1 for determining the priority among the CSI reports. Here, the priority index for determining the priority may be y, k, c, s in Equation 1, wherein y is a priority index set based on the periodicity of the CSI report / CLI report and / or the reporting channel, k is a priority index set based on whether the measurement report includes a measurement value for RSRP / SINR and / or a report type for which the measurement of the RSRP is requested, c may be a serving cell index, and s may be a configuration ID related to the report. For example, the base station can expect / predict that the measurement report will be reported from the UE by applying the priority described below.

[0380] For example, with respect to CLI reporting, the priority index k may be determined based on whether the measurement report includes Reference Signal Receiver Power (RSRP) measured in the measurement resource and the report type of the RSRP. Here, the report type of the RSRP may be divided into a first type that reports the RSRP for CSI and a second type that reports the RSRP for CLI (Cross Link Interference). In this case, if the RSRP included in the measurement report is an RSRP for the first type (e.g., beam measurement for CSI reporting), the k may be determined / set to a first value. Here, the first value may be 0 as defined in Table 11. Or, in this case, if the RSRP included in the measurement report is an RSRP for the second type (e.g., a CSI report including an RSRP measured for CLI reporting), the k may be determined / set to a second value. Here, the second value may be 1 as suggested in Table 11 and Section 2 Proposal 1-2h alt 2, or 2 as suggested in Section 2 Proposal 1-2h alt3. Alternatively, the k value for the CLI report including RSRP for the second type, such as Section 2 Proposal 1-2h alt5, may be set / determined to be 1, which is the same as the k value for the measurement report (e.g., report for PMI, CQI, RI, etc.) that does not include the RSRP. Alternatively, the k value for the CLI report including RSRP for the second type, such as Section 2 Proposal 1-2h alt2, may be set / determined to be 1, and the k value for the measurement report (e.g., report for PMI, CQI, RI, etc.) that does not include the RSRP may be set / determined to be 2.Alternatively, the k value for CLI reports including RSRP for the second type, such as alt3 of proposal 1-2h of section 2, may be set / determined to 2, and the k value for measurement reports not including RSRP (e.g., reports for PMI, CQI, RI, etc.) may be set / determined to 1.

[0381] For example, the existing k value is a value set to 0 or 1 depending on whether a measurement value for RSRP or SINR is included in a measurement report (e.g., a CSI report). However, as described above, in determining the k value, additional consideration needs to be given to a measurement report including RSRP for CSI and a measurement report including RSRP for CLI (measured based on SRS, which is a measurement resource) due to the introduction of L1 CLI reporting. To this end, unlike the existing case where k is set to 0 if the measurement report includes the RSRP, the proposed invention can set / determine the k value to 0 for a measurement report including RSRP for CSI and to 1 for a measurement report including RSRP for CLI. Here, the k value can be set to 1 for a measurement report that does not include RSRP, in the same way as for a measurement report including RSRP for CLI.

[0382] Alternatively, as in alt1 of proposal 1-2h in section 2, the k value for a measurement report (or CSI report) including RSRP for the second type may be set to 0, the k value for a measurement report (or CSI report) including RSRP for the first type may be set to 1, and the k value for a measurement report (or CSI report) including RSRP may be set to 2. As in alt3 of proposal 1-2h in section 2, the k value for a measurement report (or CSI report) including RSRP for the first type may be set to 0, the k value for a measurement report (or CSI report) including RSRP may be set to 1, and the k value for a measurement report (or CSI report) including RSRP may be set to 2.

[0383] Alternatively, as proposed in Proposals 1-1 and / or 1-2a to 1-2g of Section 2, the above-described y value for the CLI report may be set / determined based on the periodicity of the measurement report and the channel through which it is transmitted.

[0384] Alternatively, the measurement report may include information related to measurement values ​​for a plurality of CLI measurement resources. For example, the measurement report may include information about differences between a specific reference measurement value and the remaining measurement values ​​as set forth in Proposal 1 and / or Proposal 2 of Section 1. Here, the specific reference measurement value may be determined based on the most recent L3 CLI reported measurement value to the base station as described in Proposal 1 of Section 1, or may be determined as the highest value among the measurement values ​​(L1 CLI measurement values) for the plurality of CLI measurement resources.

[0385] In this way, the proposed invention can effectively report L1 CLI reports using the CSI framework without defining new settings for L1 CLI reports. Alternatively, the proposed invention can resolve ambiguity in UE operations for L1 CLI reports and L1 CSI reports by clearly defining priorities between L1 CLI reports and CSI reports. Alternatively, the proposed invention can minimize the increase in overhead of CLI measurement reports in L1 / L2 signaling by reporting multiple CLI measurement values ​​based on differences between the multiple CLI measurement values ​​based on a specific CLI measurement value.

[0386] Examples of communication systems to which the invention applies

[0387] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0388] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0389] Figure 15 illustrates a communication system applied to the present invention.

[0390] Referring to FIG. 15, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0391] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0392] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0393] Examples of wireless devices to which the present invention is applied

[0394] Figure 16 illustrates a wireless device applicable to the present invention.

[0395] Referring to FIG. 16, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 15.

[0396] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0397] According to one example, the first wireless device (100) or UE may include a processor (102) and a memory (104) connected to the RF transceiver. The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 8 to 14.

[0398] Specifically, the processor (102) can control the RF transceiver (106) to obtain a measurement related to a measurement resource, determine a priority related to a measurement report including the measurement based on a priority index related to a channel state information (CSI) report, and perform a transmission procedure of the measurement report based on the priority. Here, the priority index can be determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured in the measurement resource and a report type of the RSRP.

[0399] Alternatively, a processing device including a processor (102) and a memory (104) may be configured. In this case, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the UE (100) to: obtain a measurement related to a measurement resource, determine a priority related to a measurement report including the measurement based on a priority index related to a channel state information (CSI) report, and perform a transmission procedure of the measurement report based on the priority. Here, the priority index may be determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured in the measurement resource and a report type of the RSRP.

[0400] Alternatively, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the proposed methods described with reference to FIGS. 8 to 14 may be configured.

[0401] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0402] According to one example, the second wireless device (200) or base station may include a processor (202) and a memory (204) connected to the RF transceiver. The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 8 to 14.

[0403] Specifically, the processor (202) can control the transceiver (206) or the RF transceiver to transmit measurement resource configuration information for a measurement resource to a UE (User Equipment), and receive a measurement report including a measurement obtained from the measurement resource. Here, the measurement report is applied with a priority determined based on a priority index related to a CSI (channel state information) report, and the priority index can be determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the report type of the RSRP.

[0404] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0405] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0406] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0407] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0408] Examples of wireless devices to which the present invention is applied

[0409] Figure 17 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0410] Referring to FIG. 17, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 16 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 17. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 16. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0411] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 15, 100a), a vehicle (Fig. 15, 100b-1, 100b-2), an XR device (Fig. 15, 100c), a portable device (Fig. 15, 100d), a home appliance (Fig. 15, 100e), an IoT device (Fig. 15, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 15, 400), a base station (Fig. 15, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0412] In FIG. 17, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0413] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0414] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0415] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0416] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0417] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0418] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0419] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. In the method using UE (User Equipment), A step of obtaining a measurement related to a measurement resource; A step of determining a priority associated with a measurement report including the measurement based on a priority index associated with a CSI (channel state information) report; and A step of performing a transmission procedure of the measurement report based on the above priority; A method in which the above priority index is determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the report type of the RSRP.

2. In paragraph 1, A method characterized in that the above reporting type includes a first type reporting the RSRP for CSI and a second type reporting the RSRP for CLI (Cross Link Interference).

3. In paragraph 1 Based on the above measurement report including the RSRP for the CSI, the priority index is determined to be a first value, A method, characterized in that the priority index is determined to be a second value greater than the first value, based on the measurement report including the RSRP for CLI (Cross Link Interference).

4. In paragraph 3, A method characterized in that the priority index is determined as the second value based on the measurement report not including RSRP.

5. In paragraph 3, A method characterized in that, based on the above measurement report not including RSRP, the priority index is determined to be a third value greater than the second value.

6. In paragraph 3, A method characterized in that, based on the above measurement report not including RSRP, the priority index is determined to be a third value that is less than the second value and greater than the first value.

7. In paragraph 1, A method characterized in that, based on the overlapping of the above measurement report and another measurement report in the time domain, the UE determines whether to drop the measurement report based on the priority and the priority for the other measurement report.

8. In paragraph 1, A method characterized in that the above measurement report includes information on a difference value between a plurality of measurement values ​​for a plurality of CLI measurement resources and a specific measurement value among the plurality of measurement values.

9. A non-transitory computer-readable storage medium recording commands for performing the method described in paragraph 1.

10. In UE (User Equipment), RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to obtain a measurement related to a measurement resource, determines a priority related to a measurement report including the measurement based on a priority index related to a CSI (channel state information) report, and performs a transmission procedure of the measurement report based on the priority. The above priority index is determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the reporting type of the RSRP.

11. In paragraph 10, A UE characterized in that the above reporting type includes a first type reporting the RSRP for CSI and a second type reporting the RSRP for CLI (Cross Link Interference).

12. In paragraph 10, A UE, characterized in that the first measurement resource is set to have the same period as the period of the first time resource.

13. In a processing device that controls UE (User Equipment), at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said UE: Obtain a measurement related to a measurement resource, determine a priority related to a measurement report including the measurement based on a priority index related to a CSI (channel state information) report, and perform a transmission procedure of the measurement report based on the priority, A processing device wherein the priority index is determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the report type of the RSRP.

14. In the method by the base station, A step of transmitting measurement resource setting information for measurement resources to UE (User Equipment); and A step of receiving a measurement report including measurements obtained from the above measurement resource; The above measurement report is applied with a priority determined based on a priority index related to the CSI (channel state information) report, The above priority index is determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the report type of the RSRP.

15. At the base station, RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to transmit measurement resource setting information for the measurement resource to the UE (User Equipment), and receives a measurement report including measurements obtained from the measurement resource. The above measurement report is applied with a priority determined based on a priority index related to the CSI (channel state information) report, The above priority index is determined based on whether the measurement report includes RSRP (Reference Signal Receiver Power) measured from the measurement resource and the report type of the RSRP.

Images