Method for performing communication and device therefor in wireless communication system

Abstract

Disclosed are a method for performing communication and a device therefor in a wireless communication system according to various embodiments. Disclosed are a method and a device therefor, the method involving: receiving configuration information for configuring a first time resource related to sub-band full duplex (SBFD); receiving measurement resource information for a first measurement resource for CLI measurement; and performing measurement on the basis of the measurement resource information. Accordingly, a terminal can more accurately and efficiently perform the CLI measurement operation. In addition, in the present application, sub-band-based CLI measurement is possible instead of general full-duplex-based CLI measurement.

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 terminals to perform CLI measurements 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 the steps of: receiving configuration information for setting a first time resource related to sub-band full duplex (SBFD); receiving measurement resource information for a first measurement resource for cross link interference (CLI) measurement; and performing the CLI measurement based on the measurement resource information; wherein the first measurement resource may include a non-continuous frequency resource in a frequency domain for downlink (DL) subbands in the first time resource.

[0007] Alternatively, the UE is characterized in that it determines that only at least one first measurement resource allocated within the first time resource among the first measurement resources included in the measurement resource information is valid.

[0008] Alternatively, the UE is characterized in that it determines that at least one first measurement resource allocated for the second time resource not related to the SBFD among the first measurement resources included in the measurement resource information is invalid.

[0009] Alternatively, the first measurement resource is characterized in that it is set to have the same period as the period of the first time resource.

[0010] Alternatively, the first measurement resource is characterized in that it further includes a continuous frequency resource in the frequency domain for the UL (Uplink) subband of the first time resource.

[0011] Alternatively, the frequency resource information is characterized in that it further includes configuration information for a resource block set related to the frequency band.

[0012] Alternatively, the measurement resource information is characterized in that it further includes information on a second measurement resource of a second time resource not related to the SBFD.

[0013] Alternatively, the method further includes a step of reporting a result for the measurement based on the value of the measurement being greater than or equal to a specific threshold value, wherein the specific threshold value is set as a first threshold value for the first time resource and a second threshold value for the second time resource.

[0014] Alternatively, the measurement resource is characterized by being an SRS (Sounding Reference Signal) resource and a CLI-RSSI (Received Signal Strength Indicator) resource.

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

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

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

[0018] A method by a base station according to another aspect includes the steps of: transmitting configuration information for setting a first time resource related to sub-band full duplex (SBFD); transmitting measurement resource information for a first measurement resource for CLI measurement; and receiving a measurement report for the CLI measurement; wherein the first measurement resource may include non-contiguous frequency resources in a frequency domain for two DL (Downlink) subbands of the first time resource.

[0019] According to another aspect, a base station performing the above-described method may be provided.

[0020] Various embodiments enable the terminal to perform CLI measurement operations more accurately and efficiently.

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

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

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

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

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

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

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

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

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

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

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

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

[0033] FIG. 13 is a diagram illustrating how a UE sets up CLI measurement resources related to SBFD.

[0034] Figure 14 is a diagram for explaining a method for setting up CLI measurement resources related to SBFD in a base station.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] 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

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

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

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

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

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

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

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

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

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

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

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

[0068] Bandwidth part (BWP)

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

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

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

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

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

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

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

[0076] A terminal that has performed the procedure described above can then perform general uplink / downlink signal transmission procedures, such as receiving a physical downlink control channel signal and / or a physical downlink shared channel signal (S17) and transmitting 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).

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

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

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

[0080] 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0098] CSI-related actions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0116] QCL (quasi-co location)

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

[0118] 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:

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

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

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

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

[0123] L3 CLI Report

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

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

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

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

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

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

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

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

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

[0133] 4> else:

[0134] 5> ifreportQuantityCLIis set tosrs-rsrp:

[0135] 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;

[0136] 5> else:

[0137] 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;

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

[0139] 5> include thesrs-ResourceId;

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

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

[0142] 5> include therssi-ResourceId;

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

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

[0145] Periodic configuration / event trigger

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

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

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

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

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

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

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

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

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

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

[0156] - 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;

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

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

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

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

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

[0162] Beam Management (BM)

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

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

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

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

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

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

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

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

[0171] Full duplex operation for NR

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

[0173] 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 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 growth 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0186] (1) Measurement resource aspect

[0187] 1) About d / f TDD

[0188] - Aggressor: Inter-cell UE

[0189] - HD slot only

[0190] 2) About SBFD

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

[0192] - HD slot & SBFD slot

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

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

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

[0196] (1) Measurement resources

[0197] > SRS-Resource

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

[0199] - For CLI SRS-RSRP measurements

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

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

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

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

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

[0205] -- SRS Port 1

[0206] > CLI-RSSI-Resource

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

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

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

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

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

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

[0213] (2) Measurement / report trigger

[0214] > SRS-RSRP, CLI-RSSI

[0215] > Event triggered or periodical

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

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

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

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

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

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

[0222] > Background

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

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

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

[0226] > Measure resource

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

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

[0229] > Report

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

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

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

[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 subband 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 subbands (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 subbands (or UL bands) (RSSI / RSRP based)

[0272] Existing CLI measurements / reports up to Rel-17 are currently event-based triggered (when RSSI exceeds a certain threshold) or periodically (120ms~30min), and reporting is done based on RSSI in CLI-RSSI resources or based on RSRP in SRS resources. In particular, measurement resources can only be set as periodic resources. In this case, when the gNB performs the SBFD operation (or SFFD operation), the DL and UL are located adjacent to or in the same frequency during the time period when the SBFD operation (or SFFD operation) is performed, so the interference pattern during the SBFD operation (or SFFD operation) may be significantly different from the interference pattern during the time period when the non-SBFD operation (or non-SFFD operation) is performed. However, since the measurement resource for current CLI measurement is a periodic resource, it can have an ID according to the periodicity and be reported based on the ID. In this case, if the cycle of the SBFD (or SFFD) of the gNB is different from the cycle of the CLI measurement resource, the CLI aspect measured by the UE may vary significantly or become different. In addition, since such CLI measurement is reported by performing L3 filtering, the CLI experienced by the UE may not be accurately delivered to the gNB through the CLI report of the UE. In addition, even if the cycle of the CLI measurement resource and the cycle of the SBFD (or SFFD) of the gNB are the same, there may be cases where CLI events are excessively triggered by the CLI in the SBFD (or SFFD). Against this backdrop, the UE may be configured with distinct CLI measurement resources for the time period in which the gNB performs the SBFD operation and the time period in which it does not, and enhancements may be required for the reporting operation accordingly.

[0273] In other words, when considering an environment where the gNB operates in SBFD (or SFFD), the CLI behavior may differ significantly between SBFD slots and non-SBFD slots. This is because the CLI behavior may differ significantly between SBFD slots and non-SBFD slots, considering that CLI is interference from UL to DL and from DL to UL. Therefore, the gNB needs to distinguish CLI measurement resources and set them for the UE according to the time interval during which the SBFD operation is performed (e.g., SBFD time interval) and the time interval during which the non-SBFD operation is performed (e.g., non-SBFD time interval). 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.

[0274] Meanwhile, in the following, it is assumed that the gNB configures / instructs the UE to use different time resources (e.g., a first time resource and a second time resource) that perform different characteristic operations (e.g., an SBFD operation or a non-SBFD operation). Here, the first time resource and the second time resource may be a time interval during which the gNB performs an SBFD operation (hereinafter, an SBFD slot) and a time interval during which the gNB performs a non-SBFD operation (hereinafter, a non-SBFD slot). Alternatively, the first time resource and the second time resource may be a time interval during which the gNB performs an SFFD operation and a time interval during which the gNB performs a non-SFFD operation. Although the SBFD slot and the non-SBFD slot are described below for the convenience of explanation, they are only one embodiment of the first time resource and the second time resource, and can be extended to slots for other purposes.

[0275] CLI measurement report enhancement for SBFD

[0276] Based on the study item results of 3GPP Rel-18 duplex, it can be assumed that the UE can semi-statically receive SBFD configuration (DL / UL subband configuration) from the gNB. A UE with the capability to receive SBFD configuration from the gNB can be defined as an SBFD aware UE. Based on this assumption, Section 1 describes a resource enhancement scheme for CLI measurements, and Section 2 describes an enhancement scheme for reporting CLI measurements.

[0277] 1. CLI measurement resources for SBFD aware UEs

[0278] Since the DL subband and the UL subband are located in adjacent frequencies during the time period in which the gNB performs the SBFD operation, the interference during the time period in which the SBFD operation is performed may differ significantly from the interference during the time period in which the non-SBFD operation is performed. This is because the interference deviation is large depending on whether the SBFD operation is performed, as CLI is interference from the UL subband to the DL subband or from the DL subband to the UL subband. Therefore, the gNB needs to separately configure CLI measurement resources for the UE according to the time period in which the SBFD operation is performed and the time period in which the non-SBFD operation is performed. For example, the UE may be separately configured with CLI measurement resources for the time period in which the gNB performs the SBFD operation and CLI measurement resources for the time period in which the non-SBFD operation is performed. For this purpose, the following methods may be considered.

[0279] (1) Method 1

[0280] In method 1, the UE can receive CLI measurement resources for a time period during which it performs SBFD operations separately from the existing measurement resources from the gNB.

[0281] Method 1 is a method for configuring resources of other signals / channels in a time interval during which the gNB performs the SBFD operation, and may be advantageous in that it can operate based on a method for configuring existing CLI measurement resources. Based on Method 1, the UE can be separately instructed by the gNB of resources for CLI measurement in a time interval during which the SBFD operation is performed. However, if the transmission of a UL signal / channel is instructed by the gNB's scheduling in the CLI measurement resources related to the SBFD operation, the UE can transmit the UL signal / channel without performing CLI measurement in the time resource. Alternatively, even if the UE has been instructed by the gNB of resources for CLI measurement in a time interval during which the SBFD operation is performed by the method described, the UE may want to transmit the UL signal / channel through a UL subband in the CLI measurement resource. In this case, the UE can transmit the UL signal / channel without performing CLI measurement in the CLI measurement resource.

[0282] In this way, the CLI measurement resources for SBFD operation can be set / instructed based on at least one of the following methods.

[0283] 1) Method 1-1: The UE can be configured with discontinuous CLI measurement resources in the frequency domain for the CLI measurement resources set during the time period in which the gNB performs SBFD operation.

[0284] For example, the UE may be configured with CLI measurement resources divided into CLI measurement resources for a time period during which the gNB performs SBFD operations (hereinafter, first CLI measurement resources) and CLI measurement resources for a time period during which the gNB performs non-SBFD operations (hereinafter, second CLI measurement resources). Here, for the first CLI measurement resources, discontinuous measurement resources may be configured in the frequency domain.

[0285] As a method for a UE to set / instruct CLI measurement resources divided into a first CLI measurement resource and a second CLI measurement resource, the first CLI measurement resource and the second CLI measurement resource can be explicitly set / instructed to be divided. Alternatively, the UE can implicitly set a measurement resource located within an SBFD time interval as a first CLI measurement resource and a measurement resource not located within an SBFD time interval as a second CLI measurement resource based on a cycle of the configured SBFD configuration. Here, the cycle of the first CLI measurement resource in a time interval in which the gNB performs an SBFD operation can be the same as the cycle of the time interval in which the gNB performs the SBFD operation.

[0286] For example, in the case of the first CLI measurement resource, the UE may assume / determine discontinuous measurement resources in the frequency domain as measurement resources for CLI measurement of the DL subband, and may assume / determine continuous resources in the frequency domain as measurement resources for CLI measurement of the UL subband. This is because, as illustrated in FIGS. 8 to 12 , the DL subband for SBFD is discontinuous in the frequency domain for UL subband configuration, and the SBFD UL subband is continuous in the frequency domain.

[0287] 2) Method 1-2: Only continuous CLI measurement resources (or, first CLI measurement resources) are configured in the frequency domain, and the UE can determine that CLI measurement resources located in the same time resource are linked CLI measurement resources. Here, the period of the CLI measurement resources is the same as the period of the time interval in which the gNB performs the SBFD operation. Alternatively, the UE can implicitly configure a measurement resource located within the SBFD time interval as the first CLI measurement resource and a measurement resource not located within the SBFD time interval as the second CLI measurement resource based on the period of the configured SBFD configuration. Here, the period of the first CLI measurement resource in the time interval in which the gNB performs the SBFD operation may be the same as the period of the time interval in which the gNB performs the SBFD operation.

[0288] For example, the UE may receive the first CLI measurement resource and the second CLI measurement resource separately, and the gNB may (additionally) indicate a linked measurement resource for the first CLI measurement resource. Here, the linked measurement resource may mean that the two measurement resources are mapped to a single resource ID. In this case, the UE may perform measurement and reporting by treating the linked measurement resource as a single measurement resource. At this time, the indication of the linked measurement resource may be explicitly or implicitly set by the gNB. For example, if the UE is indicated with two measurement resources having different frequencies for the same time resource, the UE may determine the two resources as linked measurement resources. In this case, the two measurement resources may be indicated through one ID (the smallest or largest ID) among the resource IDs for the two measurement resources. Meanwhile, such linked measurement resources may only be applied to the same measurement type, and may not be applied between different measurement types. For example, linked measurement resources may be established / allowed between CLI RSSI resources (or between SRS resources), but establishment of the linked measurement resources may not be permitted between different types (e.g., CLI-RSSI resources and SRS resources). For example, even if two frequency resources located at the same time are established, if the two frequency resources are resources for different measurement types, they may not be determined as linked measurement resources.

[0289] At this time, for the first CLI measurement resource (e.g., CLI measurement resource configured in the time interval during SBFD operation), the UE may determine that the linked measurement resources are resources for CLI measurement in the DL subband, and the unlinked measurement resources are resources for CLI measurement in the UL subband. This is because the DL subband for SBFD is discontinuous in the frequency domain for UL subband configuration, and the SBFD UL subband is continuous in the frequency domain.

[0290] As described above in Method 1-1 and Method 1-2, the UE can receive the first CLI measurement resource and the second CLI measurement resource separately. In particular, if the first CLI measurement resource and the second CLI measurement resource are explicitly indicated to be separately, the following may be considered.

[0291] - The UE may consider the first CLI measurement resource configured by the gNB (e.g., the first CLI measurement resource configured in the time interval during which the gNB performs a non-SBFD operation) as invalid if the first CLI measurement resource is located in the time interval during which the gNB performs a non-SBFD operation. Here, the UE deeming the first CLI measurement resource as invalid may mean that it does not perform measurement on the corresponding measurement resource. If the measurement resource determined to be invalid is a periodic resource, the UE may not determine the measurement resource, which was once determined to be invalid, as invalid for all periods, but may determine whether it is valid for each period. For example, if a periodic first CLI measurement resource is configured, the UE may determine the validity of the first CLI measurement resource based on whether it is located in the time interval during which the gNB performs the SBFD operation for each period. This method may have the advantage of increasing the scheduling flexibility of the CLI resource of the gNB because it rules out by a rule without considering the period of the measurement resource.

[0292] (2) Method 2

[0293] For Method 2, the UE can determine the first CLI measurement resource (or new measurement resource) by combining the existing measurement resource and SBFD configuration, without separately configuring the first CLI measurement resource (e.g., CLI measurement resource for the time interval during which the gNB performs the SBFD operation). For example, the UE can configure / be instructed to configure the first CLI measurement resource (e.g., CLI measurement resource located in the time interval during which the gNB performs the SBFD operation instructed from the gNB) based on the methods described below.

[0294] 1) Method 2-1: The UE may determine that the resources set in the time interval during which the gNB performs the SBFD operation are separate CLI measurement resources for the CLI measurement resources previously set. For example, the UE may determine / assume that the CLI measurement resources set in the SBFD slot interval among the existing CLI measurement resources are CLI measurement resources set separately for the SBFD slot (e.g., the first CLI measurement resource).

[0295] For example, the UE may determine that measurement resources existing in the time interval during which the gNB performs SBFD operation among the existing configured CLI measurement resources are new resources with separate resource IDs, and may operate based on each resource ID (e.g., a separately configured / mapped resource ID for the first CLI measurement resource) in the future event-triggered reporting and periodic reporting settings. An advantage of this method may be that the gNB can easily manage CLI in SBFD slots and CLI in non-SBFD slots separately.

[0296] 2) Method 2-2: The UE can use the CLI measurement resources set previously, but can determine that the measurement resources set during the time period in which the gNB performs SBFD operation are additionally set as separate CLI resources.

[0297] For example, the UE may keep the existing configured CLI measurement resources as they are, and determine that the CLI resources existing in the time interval in which the gNB performs the SBFD operation are new resources with an additional resource ID. In this case, the UE may also operate based on each resource ID (the additional resource ID) when configuring event-triggered reporting and periodic reporting in the future. This method may have the advantage that the gNB can manage the CLI in the non-SBFD slot and the SBFD slot in the existing CLI manner by integrating them, and it may be easy to additionally manage the CLI measurement resources in the SBFD slot.

[0298] Meanwhile, even if the first CLI measurement resource is instructed by the gNB, if the UE is instructed to transmit a UL signal / channel by scheduling of the gNB on the first CLI measurement resource, the UE may transmit the UL signal / channel without performing CLI measurement on the time resource. Alternatively, even if the UE is instructed by the gNB to use the first CLI measurement resource in a time interval in which the UE performs the SBFD operation by the method described, if the UE wants to transmit a UL signal / channel through a UL subband on the first CLI measurement resource, the UE may transmit the UL signal / channel without performing CLI measurement on the first CLI measurement resource.

[0299] The UE can be configured to receive CLI measurement resources for the time intervals in which the gNB performs SBFD operation and the time intervals in which the gNB performs non-SBFD operation based on the above-described methods 1 and 2. Alternatively, the UE can be configured to receive CLI measurement resources for the time intervals in which the gNB performs SBFD operation and CLI measurement resources (i.e., rel-16 CLI resources) configured by the existing method separately. For the differentiated CLI measurement resources, the UE can separately receive from the gNB the maximum number of resources that can be included in a single report. For example, two parameters such as MaxReportCLI and MaxReportCLI_SBFD can be configured.

[0300] 2. CLI events for CLI reporting of SBFD aware UEs

[0301] The existing UE behavior for CLI reporting can be event-based or periodic, as described in certain scenarios (see 3GPP TS 38.331, 38.133, 38.214). In this case, the UE can report the measurement results for the N (=maxReportCLI) most interfering resources to the gNB via L3 signaling. In addition, the existing event I1 threshold (Interference becomes higher than absolute threshold) is set to a single value (i1-threshold) for each of RSRP (Reference Signal Received Power) and RSSI (Received Signal Strength Indicator), and any resource ID can be included and reported when measurement reporting is triggered by an event.

[0302] As described in Section '1', the gNB can configure separate CLI measurement resources for the time period of SBFD operation and the time period of non-SBFD operation to the UE, considering the different CLI aspects. In this case, the UE can be event-triggered based on the same threshold if it uses the existing reporting mechanism. Since the CLI aspects of SBFD CLI measurement resources and non-SBFD CLI measurement resources are different (or, even if the CLI aspects are not different), if the measurement metric is RSSI, they may have different RSSIs depending on the size of the time / frequency resources of the resource. Therefore, in the case of RSSI-based event-triggered reporting by reusing the existing reporting mechanism, too frequent event triggers may occur, or reports on CLI measurement resources for non-SBFD may not be reported to the gNB. In the following, methods to solve such problems are proposed.

[0303] (1) Method 1: The UE may be configured with multiple thresholds for CLI measurements for the purpose of event trigger reporting. For example, the gNB may configure the UE with multiple thresholds for SRS-RSRP and / or multiple thresholds for CLI-RSSI.

[0304] Since there is no connection between resources and events for CLI measurement, the UE may explicitly receive from the gNB a mapping relationship with measurement resources corresponding to a plurality of configured thresholds, or may implicitly receive a mapping relationship based on a mapping relationship based on a prior rule or agreement. A method for explicitly receiving such a mapping relationship from the gNB may be a method for receiving a plurality of thresholds that are distinguished according to the measurement resource type. For example, the gNB may set / instruct the UE to receive at least one of a threshold for SRS-RSRP related to non-SBFD, a threshold for SRS-RSRP related to SBFD, a threshold for CLI-RSSI related to non-SBFD, and a threshold for CLI-RSSI related to SBFD. For example, different thresholds may be set for different types of measurement resources (e.g., non-SBFD SRS resources, SBFD SRS resources, non-SBFD CLI-RSSI resources, SBFD CLI-RSSI resources), and the UE may not apply different thresholds to measurement resources of the same type, but may apply different thresholds to measurement resources of different types. For example, for a UE, an SRS resource (or non-SBFD SRS resource) related to a non-SBFD operation for CLI measurement, a CLI-RSSI resource (or non-SBFD CLI-RSSI resource) related to a non-SBFD operation, an SRS resource (or SBFD SRS resource) related to an SBFD operation, and a CLI-RSSI resource (or SBFD CLI-RSSI resource) related to an SBFD operation are configured, and a threshold can be independently set for each of the SRS resource (or non-SBFD SRS resource) related to a non-SBFD operation, the CLI-RSSI resource (or SBFD CLI-RSSI resource) related to an SBFD operation, and the SRS resource (or non-SBFD SRS resource) related to an SBFD operation.

[0305] 1) Method 1-1: The UE may determine that a trigger condition for a measurement report is satisfied when multiple thresholds are set for multiple measurement resources of different types, and a measurement value for at least one measurement resource among the multiple measurement resources exceeds / is greater than the corresponding threshold.

[0306] For example, the UE may be configured with a first CLI measurement resource (e.g., an SBFD SRS resource, an SBFD CLI-RSSI resource) for a time period during which an SBFD operation is performed, and a second CLI measurement resource (e.g., a non-SBFD SRS resource, a non-SBFD CLI-RSSI resource) for a time period during which a non-SBFD operation is performed, from the gNB. In this case, when event trigger reporting is configured for each of the SBFD SRS resource, the SBFD CLI-RSSI resource, the non-SBFD SRS resource, and the non-SBFD CLI-RSSI resource, the UE may be configured with a plurality of thresholds (i1-threshold for SBFD SRS resource, i1-threshold for SBFD CLI-RSSI resource, i1-threshold for non-SBFD SRS resource, and i1-threshold for non-SBFD CLI-RSSI resource) from the gNB. If one or more of these events are triggered, the UE may determine that a CLI measurement report has been triggered and report a configured maximum number of CLI measurement results to the gNB. This may be similar to the behavior of the UE's existing event-based triggered CLI reporting. This reporting method may allow the gNB to more actively monitor CLI for different interference environments between SBFD and non-SBFD operating time periods.

[0307] 2) Method 1-2: The UE may determine that the measurement report trigger condition is satisfied only when the threshold set for a measurement resource of a specific measurement / resource type is exceeded in relation to the multiple thresholds set.

[0308] For example, the UE may be configured with a first CLI measurement resource (e.g., an SBFD SRS resource, an SBFD CLI-RSSI resource) for a time period during which the SBFD operation is performed by the gNB, and a second CLI measurement resource (e.g., a non-SBFD SRS resource, a non-SBFD CLI-RSSI resource) for a time period during which the SBFD operation is not performed. The UE may be configured with a plurality of thresholds (i1-threshold for SBFD SRS resource, i1-threshold for SBFD CLI-RSSI resource, i1-threshold for non-SBFD SRS resource, and i1-threshold for non-SBFD CLI-RSSI resource) by the gNB. If all events configured for the plurality of measurement resource types (e.g., an event when interference exceeding the corresponding threshold for each resource type is measured) are judged as conditions for triggering reporting, too frequent reporting may be triggered, and reporting of measurements that are relatively unimportant from the gNB's perspective may continue. Here, an event can be defined as a case where the measured value for each measurement resource exceeds / is above the corresponding threshold, as described above. Therefore, some of the configured events can be treated as events that do not trigger reporting. For convenience of explanation, events that do not trigger reporting are defined as "event_dummy," and events that trigger reporting in the conventional manner are defined as "event_real."

[0309] For example, when a specific event (or event_dummy) occurs that does not trigger a measurement report, the UE may record / store information about measurements from the start to the end of the specific event, and when a measurement report is performed due to a reason for another measurement report (e.g., periodic measurement report, and / or when the conditions of event_actual are satisfied), the stored / recorded measurement results related to the specific event may also be included in the measurement report and reported together. In this way, when the measurement result for the event_dummy is also reported together, the UE may determine (treat / consider) the measurement result of the event_dummy as the highest CLI measurement and include it in the report. In this case, the measurement result for the event_dummy can always be reported to the gNB, and the gNB can completely understand the measurement report related to the event_dummy configured in the UE. Or, conversely, when the measurement result for the event_dummy is also reported together, the UE may determine the measurement result of the event_dummy as the lowest CLI measurement and include it in the report. In this case, the measurement results of the event_dummy can be reported only when the UE is not experiencing severe CLI, and the gNB can additionally have the advantage of understanding the CLI environment of the UE without breaking the existing mechanism.

[0310] (2) Method 2

[0311] For method 2, the UE can always assume that there is a setting for event trigger for a specific CLI measurement resource received from the gNB, even if there is no setting for event trigger in the reporting configuration for the specific CLI measurement resource.

[0312] For example, when a UE receives an SBFD CLI measurement resource for CLI measurement in an SBFD slot, there may not be a separate setting for the reporting configuration (e.g., periodic or event-triggered) for the SBFD CLI measurement resource. In this case, the UE may assume / judge that a virtual event based on a threshold determined by prior agreement is set. This method has the advantage that the gNB can actively perform CLI monitoring for the SBFD slot even without setting a separate ReportConfigNR ID as in the existing CLI reporting. Here, the ID of the ReportConfigNR may be set within the same ID pool as the reporting configuration for handover and / or cell quality monitoring (e.g., IDs related to various reporting methods and reporting configurations such as handover, cell quality measurement, etc. may be shared), and the maximum value of the ID may be 64.

[0313] FIG. 13 is a diagram illustrating how a UE sets up CLI measurement resources related to SBFD.

[0314] As described above in Section 1, a CLI measurement resource (hereinafter, a first measurement resource) for measuring CLI related to SBFD can be set / allocated for a UE that can recognize a time interval / time resource in which a base station performs an operation related to SBFD. In this case, the UE can perform CLI measurement based on the first measurement resource for the SBFD time interval. Hereinafter, a method for setting the first measurement resource for measuring CLI in the SBFD time interval / time resource for the UE as described above will be described in more detail. Meanwhile, even if the contents described below are not explicitly described, the methods suggested in the above-described “1. CLI measurement resource for SBFD aware UE” and / or “2. CLI event for CLI reporting of SBFD aware UE” can be naturally applied.

[0315] Referring to FIG. 13, a UE may receive configuration information for setting a first time resource related to sub-band full duplex (SBFD) (S131). As described above, the configuration information may include information on time resources on which the base station performs SBFD operations, and frequency resource information on DL sub-bands and / or UL sub-bands set for the time resources. Here, the configuration information may also be provided through SIB1 of the base station, as described above.

[0316] Next, the UE can receive measurement resource information for the first measurement resource for CLI (Cross Link Interference) measurement (S133). As described above, the base station can separately configure the first measurement resource and the second measurement resource for time resources (e.g., non-SBFD slots / symbols) in which the SBFD operation is not performed. Here, the first measurement resource can include at least one frequency resource that is continuous in the frequency domain and at least one frequency resource that is not continuous in the frequency domain. In this case, the UE can determine that at least one frequency resource that is not continuous in the frequency domain is a CLI measurement resource allocated for the DL subbands of the SBFD, and can determine that at least one frequency resource that is continuous in the frequency domain is a CLI measurement resource allocated for the UL subband of the SBFD. For example, the UE can distinguish whether the first measurement resource is a resource for a DL subband or a resource for a UL subband based on whether the frequency resource is continuous in the frequency domain even without a separate instruction. In this case, the UE can perform measurement and reporting by treating the non-contiguous frequency resources in the frequency domain for the DL subbands as a single measurement resource.

[0317] Additionally, as described above, the first measurement resource may be a Sounding Reference Signal (SRS) resource and a Received Signal Strength Indicator (CLI-RSSI) resource.

[0318] Alternatively, the first measurement resource may be set to have the same period as the period of the first time resource. For example, the first measurement resource may be set to have the same period as the period of the time interval in which the SBFD operation is performed. Alternatively, when the measurement resource information configures a plurality of first measurement resources, the UE may determine that only the first measurement resources located within the first time resource among the plurality of first measurement resources are valid measurement resources. For example, the UE may determine that the first measurement resources allocated to a second time resource (e.g., a time resource in which the SBFD operation is not performed) other than the first time resource among the plurality of first measurement resources included in the measurement resource information are invalid. In this case, the UE may perform CLI measurement only for the at least one valid first measurement resource.

[0319] Alternatively, as described above, the UE may derive the first measurement resource and the second measurement resource based on the time interval of the time resources related to the SBFD (e.g., SBFD slot / symbol) and the existing CLI measurement resource (or default CLI measurement resource). For example, the UE may determine a CLI measurement resource located within the SBFD time interval among the default CLI measurement resources as the first measurement resource, and determine the remaining default CLI measurement resources excluding the first measurement resource as the second measurement resource.

[0320] Next, the UE can perform CLI measurements based on the measurement resource information (S135). The CLI measurements / reports can be triggered periodically as described above, or event-based. In the latter case, the CLI measurements / reports can be triggered upon the satisfaction of an event when the RSRP measurement value or RSSI measurement value measured from the first measurement resource exceeds a specific threshold (i1), as described above.

[0321] Alternatively, the measurement resource information may further include information for setting a first threshold value for the first time resource and a second threshold value for the second time resource. Here, the first threshold value and the second threshold value may be threshold conditions for event-based CLI reporting. For example, as in Method 1 of Section 2, an i1-threshold for event-based reporting may be set for each resource type, and CLI measurement reporting may be triggered based on the i1-threshold for each resource type. Here, the resource type may include an SBFD SRS resource type, an SBFD CLI-RSSI resource type, a non-SBFD SRS resource type, or a non-SBFD CLI-RSSI resource type as described above. For example, the first measurement resource may be an SBFD SRS resource type or an SBFD CLI-RSSI resource type, and the second measurement resource may be a non-SBFD SRS resource type or a non-SBFD CLI-RSSI resource type. In this case, as in Method 1-2 of Section 2, event-based reporting may be activated for at least one of the resource types, and event-based reporting may be deactivated for the remaining resource types. Here, measurement values ​​measured in the measurement resource of the deactivated resource type may be included in and reported in another measurement report. In this case, the measurement values ​​measured in the measurement resource of the deactivated resource type may always be reported in the other measurement report, assuming that they have the highest measurement value. Alternatively, as in Method 2 of Section 2, even if there is no setting related to an event trigger for the first measurement resource, the UE may assume / determine that the CLI report for the first measurement resource is always event-triggered by a predefined default threshold.

[0322] Figure 14 is a diagram for explaining a method for setting up CLI measurement resources related to SBFD in a base station.

[0323] Referring to FIG. 14, the base station may transmit configuration information including information on a first time resource, which is a time interval during which the base station performs a sub-band full duplex (SBFD) operation (S141). As described above, the configuration information may include information on time resources during which the base station performs the SBFD operation, and frequency resource information on DL sub-bands and / or UL sub-bands configured for the time resources. Here, the configuration information may also be provided through SIB1 of the base station as described above.

[0324] Next, the base station can transmit measurement resource information for the first measurement resource for CLI (Cross Link Interference) measurement to the UE (S143). As described above, the base station can separately set the first measurement resource and the second measurement resource for time resources (e.g., non-SBFD slots / symbols) in which the SBFD operation is not performed. Here, the first measurement resource can include at least one frequency resource that is contiguous in the frequency domain and at least one frequency resource that is not contiguous in the frequency domain. In this case, the base station may not clearly distinguish and instruct the UE about the frequency resources for the DL subband for CLI measurement and the frequency resources for the UL subband. In this case, the base station can expect that the UE will determine that the at least one frequency resource that is not contiguous in the frequency domain is a CLI measurement resource allocated for the DL subbands of the SBFD, and that the at least one frequency resource that is contiguous in the frequency domain is a CLI measurement resource allocated for the UL subband of the SBFD. At this time, the base station can receive a measurement report from the UE by treating the non-contiguous frequency resources in the frequency domain for the DL subbands as a single measurement resource. Meanwhile, as described above, the first measurement resource may be an SRS (Sounding Reference Signal) resource and a CLI-RSSI (Received Signal Strength Indicator) resource.

[0325] Alternatively, the first measurement resource may be set to have the same period as the period of the first time resource. For example, the first measurement resource may be set to have the same period as the period of the time interval in which the SBFD operation is performed. This is so that the base station can clearly identify the CLI measurement value for the interference pattern for the time interval in which the SBFD operation is performed. In this respect, the base station can expect that the UE will only perform valid CLI measurements for the first measurement resource located within the first time resource.

[0326] Alternatively, the base station may expect that the UE will distinguish the first measurement resource and the second measurement resource for the second time resource not related to the SBFD operation based only on the transmission of the configuration information. For example, the base station may expect that the UE will be able to derive the first measurement resource and the second measurement resource based on the time interval of the SBFD-related time resources (e.g., SBFD slots / symbols) and the existing CLI measurement resource (or default CLI measurement resource).

[0327] Next, the base station can receive a CLI measurement report related to SBFD based on the measurement resource information (S145). At this time, the CLI measurement / report can be triggered periodically as described above or event-based. In the latter case, the CLI measurement / report can be triggered upon satisfaction of the event when the RSRP measurement value or RSSI measurement value measured from the first measurement resource exceeds a specific threshold (i1) as described above.

[0328] Alternatively, the measurement resource information may further include information for setting a first threshold value for the first time resource and a second threshold value for the second time resource. Here, the first threshold value and the second threshold value may be threshold conditions for event-based CLI reporting. As described above, the measurement resource information may set an i1-threshold for each resource type. The resource types may include an SBFD SRS resource type, an SBFD CLI-RSSI resource type, a non-SBFD SRS resource type, and a non-SBFD CLI-RSSI resource type as described above. Alternatively, the base station may specify / indicate in advance a resource type for which an event of actual CLI measurement / reporting is triggered among the resource types.

[0329] In this way, the proposed invention can effectively report accurate measurement information on interference patterns for the SBFD time interval to the base station by separately setting CLI measurement resources with a cycle corresponding to the time interval during which the SBFD operation is performed. Alternatively, the proposed invention can effectively prevent CLI measurement / reporting from being excessively triggered by separately setting threshold values ​​related to CLI measurement events corresponding to the time interval during which the SBFD operation is performed.

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

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

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

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

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

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

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

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

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

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

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

[0341] According to an example, the first wireless device (100) or the first base station 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.

[0342] Specifically, the processor (102) controls the RF transceiver (106) to receive configuration information for setting a first time resource related to sub-band full duplex (SBFD), receive measurement resource information for a first measurement resource for CLI measurement, and perform measurement based on the measurement resource information. Here, the first measurement resource may include non-contiguous frequency resources in a frequency domain for two DL (Downlink) subbands of the first time resource.

[0343] 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: receive configuration information for setting a first time resource related to sub-band full duplex (SBFD), receive measurement resource information for a first measurement resource for CLI measurement, and perform measurement based on the measurement resource information. Here, the first measurement resource may include non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

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

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

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

[0347] Specifically, the processor (202) can control the transceiver (206) or the RF transceiver to transmit configuration information for setting a first time resource related to sub-band full duplex (SBFD), transmit measurement resource information for the first measurement resource for CLI measurement, and receive a measurement report for the CLI measurement. Here, the first measurement resource can include non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

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

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

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

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

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

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

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

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

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

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

[0358] 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 incorporated as a new claim through a post-application amendment.

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

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

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

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

[0363] 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 receiving configuration information for setting a first time resource related to SBFD (sub-band full duplex); A step of receiving measurement resource information for a first measurement resource for CLI (Cross Link Interference) measurement; and A step of performing the CLI measurement based on the above measurement resource information; A method wherein the first measurement resource comprises a discontinuous frequency resource in the frequency domain for DL ​​(Downlink) subbands in the first time resource.

2. In paragraph 1, A method characterized in that the UE determines that only at least one first measurement resource allocated within the first time resource among the first measurement resources included in the measurement resource information is valid.

3. In paragraph 1 A method characterized in that the UE determines that at least one first measurement resource allocated for a second time resource not related to the SBFD among the first measurement resources included in the measurement resource information is invalid.

4. In paragraph 1, A method, characterized in that the first measurement resource is set to have the same period as the period of the first time resource.

5. In paragraph 1, A method, characterized in that the first measurement resource further includes a continuous frequency resource in the frequency domain for the UL (Uplink) subband of the first time resource.

6. In paragraph 1, A method, characterized in that the measurement resource information further includes information on a second measurement resource of a second time resource not related to the SBFD.

7. In paragraph 6, Further comprising a step of reporting the result of the measurement based on the value of the measurement being greater than or equal to a specific threshold value; A method, characterized in that the specific threshold value is set as a first threshold value for the first time resource and a second threshold value for the second time resource.

8. In paragraph 1, A method, characterized in that the above measurement resources are SRS (Sounding Reference Signal) resources and CLI-RSSI (Received Signal Strength Indicator) resources.

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 receive configuration information for setting a first time resource related to SBFD (sub-band full duplex), receives measurement resource information for a first measurement resource for CLI measurement, and performs measurement based on the measurement resource information. A UE wherein the first measurement resource comprises non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

11. In paragraph 10, A UE characterized in that among the first measurement resources included in the above measurement resource information, only at least one first measurement resource allocated within the first time resource is valid.

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: Receive configuration information for setting a first time resource related to SBFD (sub-band full duplex), receive measurement resource information for a first measurement resource for CLI measurement, and perform measurement based on the measurement resource information, A processing device, wherein the first measurement resource comprises non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

14. In the method by the base station, A step of transmitting configuration information for setting a first time resource related to SBFD (sub-band full duplex); A step of transmitting measurement resource information for a first measurement resource for CLI measurement; and A step of receiving a measurement report for the above CLI measurement; A method wherein the first measurement resource comprises non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

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 configuration information for setting a first time resource related to SBFD (sub-band full duplex), transmit measurement resource information for a first measurement resource for CLI measurement, and receive a measurement report for the CLI measurement. A base station, wherein the first measurement resource comprises non-contiguous frequency resources in the frequency domain for two DL (Downlink) subbands of the first time resource.

Images